Database Info

I think I may have messed up putting a new ROM on my phone

So I'm still extremely new to rooting/ROMS/ODIN etc. Well I finally decided to throw caution to the wind and attempt to root and install Slim Bean on my phone. Honestly I think because most help sites can't keep up to date with all the current ROM updates and what not that I may have messed something up. Also, before anyone rips my head off, I tried to post this question in the developers thread but I'm still to new. Anyways here's what I did:
Downloaded ODIN v1.85, SkyrocketCWMrecovery.tar, Slim Gapps and Slim-i727-3.1.0-OFFICIAL
I first ran ODIN (left all the check boxes alone as they appear when you start up), chose PDA, and chose SkyrocketCWMrecovery.tar to install.
Preformed install and rebooted my phone, everything works fine
Put Slim Gapps and Slim I727-3.1.0 onto my Internal SDCard
Disconnected phone from USB and started CWM (the version CWM is v5.0.2.6)
I wiped data/factory reset and under mounts and storage format/system
Then I installed Slim I727-3.1.0 and Gapps
I rebooted my phone and it starts loading, gets to the slim bean screen and stops
I've also tried Cyanogenmod 9.1 and 10. 9.1 does the same thing Slim bean does and 10 gets an Status 7 error, Installation aborted. I've read so many posts about this but nothing has seemed to fix my issue, at this point I would happily go back to a stock phone (I wish I'd just backed it up when I had the chance, live and learn I guess)
If someone can please help me, I'd really appreciate it.

Why using a Old Reciovery?
Head to ClockworkMod v6.0.2.7 Touch v14.4.6
Download the Latest Touch Recovery File and put it on your Sd Card and flash it Via Recovery.
After that Boot into Recovery
Format system (usually in mounts and storage menu option) X3
Format data X3
wipe data and cache partition X3
After that Flash the Rom.
In case if the Issue still persists revert back to Stock and Try Again..

manu44 said:
Why using a Old Reciovery?
Head to ClockworkMod v6.0.2.7 Touch v14.4.6
Download the Latest Touch Recovery File and put it on your Sd Card and flash it Via Recovery.
After that Boot into Recovery
Format system (usually in mounts and storage menu option) X3
Format data X3
wipe data and cache partition X3
After that Flash the Rom.
In case if the Issue still persists revert back to Stock and Try Again..
Click to expand...
Click to collapse
Ok, I got it to flash to the new version (the website I was using had the download for the old version I was using). However, when I try to wipe data and cache partition it tries to preform the action but it just sits on the screen saying formatting data....
I tried just loading cyanogenmod 10 on there and see if I got lucky, with the new version I can get the zip file to install but when I tried to reboot I get to the cyanogenmod screen and it just sits there..... any ideas?

You have to start learning doing things in the "correct" and "safe" way ..
1.Leave all other websites and stick here for the flashing and roms and what not.
2.Never use ODIN for anything ever (except for flashing stock ROM)
3.An exception also for using ODIN is the bone stock phone , you'll need ODIN to just flash a custom recovery in .tar format (this is usually just done once , even if a new recovery comes out , you update it also from a custom recovery) , once your device has a custom recovery (and a recent one) do everything from there as the custom recovery enables you to do everything from inside the recovery ..
4.Learn from the stickies here on the skyrocket section .

drkreign said:
Ok, I got it to flash to the new version (the website I was using had the download for the old version I was using). However, when I try to wipe data and cache partition it tries to preform the action but it just sits on the screen saying formatting data....
I tried just loading cyanogenmod 10 on there and see if I got lucky, with the new version I can get the zip file to install but when I tried to reboot I get to the cyanogenmod screen and it just sits there..... any ideas?
Click to expand...
Click to collapse
Ill recommend you to Flash Back to Stock Rom and then Try again.. with the Latest Recovery file

manu44 said:
Ill recommend you to Flash Back to Stock Rom and then Try again.. with the Latest Recovery file
Click to expand...
Click to collapse
Awesome, my phones back. As for trying again, I'm thinking I may skip that lol. I came from a jailbroken Iphone to trying this on my android but the android is 10x more complicated (read: way more options/routes to go to do the same thing, which is way to confusing for the first timers). Thanks for all your help!

mahanddeem said:
You have to start learning doing things in the "correct" and "safe" way ..
1.Leave all other websites and stick here for the flashing and roms and what not.
2.Never use ODIN for anything ever (except for flashing stock ROM)
3.An exception also for using ODIN is the bone stock phone , you'll need ODIN to just flash a custom recovery in .tar format (this is usually just done once , even if a new recovery comes out , you update it also from a custom recovery) , once your device has a custom recovery (and a recent one) do everything from there as the custom recovery enables you to do everything from inside the recovery ..
4.Learn from the stickies here on the skyrocket section .
Click to expand...
Click to collapse
Again, still new, but I don't think I used ODIN for anything other than installing the CWM recovery and even doing that (notably was directed to an older version) the ROMs wouldn't take. Even after upgrading the CWM to most updated version it still failed to get any version of cyan 9-10 or slim bean to work, all of them get to their respective screens and load. I even got tired, went to bed and 7 hours later the phone still wouldn't boot.
As far as I can tell I did everything this website has said to do, unless you can point me to something otherwise? Not to be rude, just trying to figure out where I would have messed up, but I just can't see where I'd have messed up OTHER than running a old version of CWM. But even that was corrected with an update and still I received the same results.

drkreign said:
Again, still new, but I don't think I used ODIN for anything other than installing the CWM recovery and even doing that (notably was directed to an older version) the ROMs wouldn't take. Even after upgrading the CWM to most updated version it still failed to get any version of cyan 9-10 or slim bean to work, all of them get to their respective screens and load. I even got tired, went to bed and 7 hours later the phone still wouldn't boot.
As far as I can tell I did everything this website has said to do, unless you can point me to something otherwise? Not to be rude, just trying to figure out where I would have messed up, but I just can't see where I'd have messed up OTHER than running a old version of CWM. But even that was corrected with an update and still I received the same results.
Click to expand...
Click to collapse
Also, not sure if anyone else is having this issue but when I try to format cache, either using wipe data/cache partition or going under mounts and storage format cache it locks up. Does data just fine but cache is a no go. I'd mention this in the development section but not enough post counts.

mahanddeem said:
4.Learn from the stickies here on the skyrocket section .
Click to expand...
Click to collapse
+1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Always read the stickies. Always read the stickies. Always read the stickies.
This is a magical mantra, if typed three times it comes true))

If you're having trouble with cwm, try flashing twrp. I find that it is easier to use for the basics.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

If your recovery is up to date and its just bootlooping after flashing, reboot into recovery and wipe cache & dalvik cache.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

Cyanogen Mod 6.0 for OPPO R7 PLUS

I apologize if this is posted, but we now have an official build of Marshmallow for our Oppo r7 Plus (F) Variant. link attachedhttp://download.cyanogenmod.org/?type=nightly&device=r7plus

Excellent! I am going to test it right now and will report!!!!
Update: I was on ColorOS, flashed cm13 recovery and done factory reset, formatting cache is taking around 8 minutes, is that normal?
Flashing ARM64 opengapps for 6.0 end up with error: E:Installation error in /sideload/package.zip (Status 255) - seems like recovery problem as many people report this issue. I only dont know if TWRP will work with CM13 rom

Personally I'm using a 12.1 recovery at the moment. The 13.0 recovery is still WIP AFAIK.
Gesendet von meinem R7plusf mit Tapatalk

Ok, will try cm12.1 recovery, what about gapps? Which one to use? Btw I have done factory reset again, flashed cm13 rom only, phone rebooted and loading apps (total of 87 I think), then done reboot, then only showing blue android logo for very long time, like 10 minutes followed with another "starting apps" screen with 21 left or so, now another reboot with blue android logo. Is this normal for MM roms? Still not finished.
EDIT: after another 5 minutes same screen appears with saying starting android... 21 apps left, blue android logo when done - seems to be as bootloop as it is going nowhere from here.
CM13 rom flashed fine over TWRP, flashing gaaps now seems to be alright as well (open_gapps-arm64-6.0-mini-20151218).

Very exited, good job

so far I am getting the boot-loop also. will wait to here what Nexus5-32GB will post (if any success with the cyanogen recovery) before reverting back

Sadly "Androis is starting... Starting apps" is last message I can see, the soft reboot then followed wit this bootloop. Same when flashed with and without gapps from TWRP, cm12.1 and cm13 recoveries.
When doing factory reset in CM12.1 recovery I get this:
-- Wiping data...
Formating /data...
E:Failed to start /data/data/org.cyanogenmod.audiofx
Formating /cache...

Guy's I got it to boot up and install so far everything seems to work okay (Minus minor distortion when automatically switching to landscape, portrait and at start up) . I am going to post a picture if I can. I believe the issues arise when we try updating to Marshmallow from lollipop and we have made major modifications. (for example I had lolli viper and a host of other customization's). I had to do a factory reset wipe and format. I then installed a backup that was untouched bone dry cyanogen mod (no g apps yet). let that boot-up and rebooted into recovery. I then downloading the nightly form (today) the 18th from the website with the marshmallow G-apps. Pushed to my sd card, wiped cache and installed the nightly and installed the correct marshmallow G-apps (ARM 64 6.0) right away. After this,I rebooted phone (it will take a while; almost as long as it did when the first nightly for lollipop came out and we flashed from color OS). It's up and running on my phone. I also still have and used the twrp recovery.

Nexus5-32GB said:
Sadly "Androis is starting... Starting apps" is last message I can see, the soft reboot then followed wit this bootloop. Same when flashed with and without gapps from TWRP, cm12.1 and cm13 recoveries.
When doing factory reset in CM12.1 recovery I get this:
-- Wiping data...
Formating /data...
E:Failed to start /data/data/org.cyanogenmod.audiofx
Formating /cache...
Click to expand...
Click to collapse
check out my post after this (well before now)

coled3 said:
Guy's I got it to boot up and install so far everything seems to work okay (Minus minor distortion when automatically switching to landscape, portrait and at start up) . I am going to post a picture if I can. I believe the issues arise when we try updating to Marshmallow from lollipop and we have made major modifications. (for example I had lolli viper and a host of other customization's). I had to do a factory reset wipe and format. I then installed a backup that was untouched bone dry cyanogen mod (no g apps yet). let that boot-up and rebooted into recovery. I then downloading the nightly form (today) the 18th from the website with the marshmallow G-apps. Pushed to my sd card, wiped cache and installed the nightly and installed the correct marshmallow G-apps (ARM 64 6.0) right away. After this,I rebooted phone (it will take a while; almost as long as it did when the first nightly for lollipop came out and we flashed from color OS). It's up and running on my phone. I also still have and used the twrp recovery.
Click to expand...
Click to collapse
going to give this a go, but I was doing factory reset and format as well, is that mean the factory reset doesnt work as it should? Flashing cm 12 rom first to be able to boot to cm13 rom later is very strange way when you think about it

Nexus5-32GB said:
going to give this a go, but I was doing factory reset and format as well, is that mean the factory reset doesnt work as it should? Flashing cm 12 rom first to be able to boot to cm13 rom later is very strange way when you think about it
Click to expand...
Click to collapse
indeed i agree 100%. I really think it boils down to if we have any customization. I had the same error (in regards to the audio FX) You should try installing a fresh clean cyanogen nightly without g-apps or any mods. Let it boot-up and try the steps i mentioned. do you have an audio customization or any that might have changed something (it shouldn't matter but I'm considering any and everything)? If this is the case the recovery might need tweaking as that would mean somehow or someway it doesn't allow us to properly wipe and format (another consideration). I really hope you and everybody else can also update. I'm trying to upload screenshots of my phone

coled3 said:
indeed i agree 100%. I really think it boils down to if we have any customization. I had the same error (in regards to the audio FX) You should try installing a fresh clean cyanogen nightly without g-apps or any mods. Let it boot-up and try the steps i mentioned. do you have an audio customization or any that might have changed something (it shouldn't matter but I'm considering any and everything)? If this is the case the recovery might need tweaking as that would mean somehow or someway it doesn't allow us to properly wipe and format (another consideration). I really hope you and everybody else can also update. I'm trying to upload screenshots of my phone
Click to expand...
Click to collapse
I was on ColorOS while ago, went to TWRP and done manual wipe of Dalvik, System, Data and Cache. Installed latest cm12.1 rom without any gapps and let it boot up to home screen. Went back to TWRP and done same wipe as before. Installed cm13 without any gapps and this time I got little further than ussualy, I could see message "finishing boot" but again end up in bootloop as before. So no luck in my case...
About the error in TWRP: yes I was using viper4android before and it seems the TWRP recovery doesnt wipe the device right way - well actually not even CM recoveries can I think.

Nexus5-32GB said:
I was on ColorOS while ago, went to TWRP and done manual wipe of Dalvik, System, Data and Cache. Installed latest cm12.1 rom without any gapps and let it boot up to home screen. Went back to TWRP and done same wipe as before. Installed cm13 without any gapps and this time I got little further than ussualy, I could see message "finishing boot" but again end up in bootloop as before. So no luck in my case...
About the error in TWRP: yes I was using viper4android before and it seems the TWRP recovery doesnt wipe the device right way - well actually not even CM recoveries can I think.
Click to expand...
Click to collapse
The events you listed I went through the same exact sequence. Keep trying it took for me; after a painstaking install experience of course. Also you're right Cyanogen recovery doesn't allow full wipe and install.

coled3 said:
The events you listed I went through the same exact sequence. Keep trying it took for me; after a painstaking install experience of course. Also you're right Cyanogen recovery doesn't allow full wipe and install.
Click to expand...
Click to collapse
As I never give up :victory: I am flashing stock rom now - via stock recovery. Will try flash twrp and install cm13 straight after full wipe of ColorOS then. There is basiclly nothing more I can do really...
EDIT: same bootloop after "finishing boot" screen. Hope developers will be happy from this research

Nexus5-32GB said:
As I never give up :victory: I am flashing stock rom now - via stock recovery. Will try flash twrp and install cm13 straight after full wipe of ColorOS then. There is basiclly nothing more I can do really...
EDIT: same bootloop after "finishing boot" screen. Hope developers will be happy from this research
Click to expand...
Click to collapse
let me know if it ends up working. I also had to hold power button to restart a couple of times after installing 13 and eventually took. Fingers crossed for you!!!!! "GO NEXUS.. GO ..GO.. GO NEXUS " HEHE

coled3 said:
let me know if it ends up working. I also had to hold power button to restart a couple of times after installing 13 and eventually took. Fingers crossed for you!!!!! "GO NEXUS.. GO ..GO.. GO NEXUS " HEHE
Click to expand...
Click to collapse
am not gonna mess with restarts and so on. What I just did was, I installed the cm12.1 and tried to run system update which downloaded the cm13 rom and flashed it in twrp ending with same bootloop. I dont really know how devs could make this working on their phones at all.

Nexus5-32GB said:
As I never give up :victory: I am flashing stock rom now - via stock recovery. Will try flash twrp and install cm13 straight after full wipe of ColorOS then. There is basiclly nothing more I can do really...
EDIT: same bootloop after "finishing boot" screen. Hope developers will be happy from this research
Click to expand...
Click to collapse
pls help me with the stock recovery ..before flashing stock recovery should i clean wipe using twrp..what all should i select for a clean wipe..i had issues with flashing stock recovery..when i selected wipe data and cache in oppo stock recovery it wipes for a secnd and then swithc off..could not get beyond that..after many twrp boot loops now i have a cm12 working ..but battery is very poor..so i want to go back to stock..please tell the steps..

Nexus5-32GB said:
am not gonna mess with restarts and so on. What I just did was, I installed the cm12.1 and tried to run system update which downloaded the cm13 rom and flashed it in twrp ending with same bootloop. I dont really know how devs could make this working on their phones at all.
Click to expand...
Click to collapse
Well, I took my 12.1 installation without any wipe, went to CM recovery from 12.1, installed my (self compiled at that time) build + opengapps (it's important to install those before booting M for the first time), booted, done. I don't have any /system mods though.
I guess I'll try the nightly and see what happens there. Did anybody of you get a logcat of the failed boot attempts?
Gesendet von meinem R7plusf mit Tapatalk

unni84kollam said:
pls help me with the stock recovery ..before flashing stock recovery should i clean wipe using twrp..what all should i select for a clean wipe..i had issues with flashing stock recovery..when i selected wipe data and cache in oppo stock recovery it wipes for a secnd and then swithc off..could not get beyond that..after many twrp boot loops now i have a cm12 working ..but battery is very poor..so i want to go back to stock..please tell the steps..
Click to expand...
Click to collapse
Just follow this quide with flashing twrp, only instead of twrp flash the stock recovery image. http://forum.xda-developers.com/showpost.php?p=63189590&postcount=5 Sorry, there is only boot command, you should type "fastboot flash recovery stock.recovery.img" - when "stock.recovery.img" is a filename of your stock recovery downloaded on your computer.
No need for wipe when installing recovery. I recon to install stock recovery and then install stock ColorOS from it, let it boot, install twrp later and do what you want then.

Looks like it's broken for everyone. I tried multiple recoverys, full wipes including /system and no joy. Guess we'll just have to wait!

TWRP infinitely installs a ROM

I didn't know where to post this so i am posting it here.
I tried to flash the latest version of CrDroid some hours ago and although the installation began with no errors, the whole thing got stuck on an infinite installation of the ROM. The log displayed "Patching system image unconditionaly."
After about 30 minutes i just lost faith and held down power button to force a reboot. Then, TWRP got reset to the screen which you see when you first flash TWRP, the one ascing about wether to keep system read only or not.
I will post screenshots too as soon as i figure out how to do it
.

Set it back to RW mode from RO mode. If it constantly turns back to RO, try reflashing the recovery image.
If you are lucky enough to abruptly abort a ROM installation, you will be able to atleast use the device. I had aborted a nandroid restore and my entire data partition was corrupted.
In any case you should post it in the appropriate ROM thread.

Make sure system is mounted writable, wipe system, data, and caches, and flash... it's that simple. If it fails use another ROM.
BTW, it is usually useful to tell which device (specifically), what ROM/Gapps, what version of TWRP, etc... the devil is usually in the details, the more the better.

Yeah i forgot about that, im new here. So, its the latest version of TWRP and the ROM was the latest version of crDroid (April 17th). Anyways, me being extremely stubborn as usual, I tried flashing the ROM through FlashFire and the problem is still there. By the way I did mount everything and it doesnt get better. I dont care anyways i'll just return to some other Nougat ROM. Thanks for replying though!

mike.... said:
Yeah i forgot about that, im new here. So, its the latest version of TWRP and the ROM was the latest version of crDroid (April 17th). Anyways, me being extremely stubborn as usual, I tried flashing the ROM through FlashFire and the problem is still there. By the way I did mount everything and it doesnt get better. I dont care anyways i'll just return to some other Nougat ROM. Thanks for replying though!
Click to expand...
Click to collapse
Weird... We can pretty much guarantee nothing is working in TWRP though, or at least it's not processing even the boot image of your ROM or the device wouldn't boot.
What is bootloader status?

OnePlus One - Won't boot RR , boot loop happens

Hi!
A while back I had some issues with the phone, it was when I was supposed to boot it, it always took 2 tries. It always got stuck, then had to long press the lock key to hard reboot it, then it worked fine. This prevented me from doing a factory reset (in hope to fix (what I later found out was) a media rescan etc). Tried to root it, something happened and it wouldn't boot anymore. Yiti yata and the phone wouldn't boot. Finally I got it back to life with some guide on here and I used whatever 4.4.4 I downloaded.
The software wouldn't find any "normal" update phone updates, so I figured I would try Resurrection Remix 7.1.x (.2 I think it was). At first I got just that it failed with some 2.x twrp version. Updated to TWRP 3.1.x.x (3.1.1.0 if I guess). Now I got to know that it was a TZ error (ERROR 7) from TWRP. This happened to my "RR-N-v5.8.3-20170718-bacon-Official.zip" file. I managed to get around it by doing this: https://forum.xda-developers.com/showthread.php?t=2522762. So I could get this installed, sort of I think. The problem now was that it would show the very first oneplus boot screen for around 20 ish seconds, before it would reboot in a boot loop.
So I tried to install some other CM Lineage Os nightly thing (they said install that and then RR), but that didn't work either. This post was the one I donwloaded from (install this first, then RR should work).
I tried doing this both on TWRP 2.8.6.0 and 3.1.1.0 since I saw some post about the modem not being right from versions newer than 2.8.6.0.
Looking around a bit more I saw in some post someone talking about firmware..? Does this matter anything, also how is this different from the recovery or ROM? (new to this stuff)
In short, last working version of Android I had on there was 4.4.4 (think I followed this post). Using a Mac currently and have no problem with flashing, entering fastboot or recovery.
My procedure when I tried to install RR was:
Install the TWRP 3.1.1.0 or 2.8.6.0 (since I did it several times).
Wipe everything (Have nothing of value on the phone) cache, system, internal storage, dalvik and data. Also did a factory reset (from TWRP) before if that matters.
Copied RR and Gapps 7.1 ARM (not arm64) over.
Installed RR, wiped cache/dalvik. (or linear/cm (post above^^) when I tried that)
Installed Gapps, wiped cache/dalvik.
Boot loop.
Also tried with/without emptying cache/dalvik also chose to install both zips at once.
So can anyone clue in how I can proceed to get RR 7.1 onto my OPO? Any help is very much appreciated
I'm sorry if this wasn't the best post. Have an immense headache at the moment

wahlmat said:
Hi!
A while back I had some issues with the phone, it was when I was supposed to boot it, it always took 2 tries. It always got stuck, then had to long press the lock key to hard reboot it, then it worked fine. This prevented me from doing a factory reset (in hope to fix (what I later found out was) a media rescan etc). Tried to root it, something happened and it wouldn't boot anymore. Yiti yata and the phone wouldn't boot. Finally I got it back to life with some guide on here and I used whatever 4.4.4 I downloaded.
The software wouldn't find any "normal" update phone updates, so I figured I would try Resurrection Remix 7.1.x (.2 I think it was). At first I got just that it failed with some 2.x twrp version. Updated to TWRP 3.1.x.x (3.1.1.0 if I guess). Now I got to know that it was a TZ error (ERROR 7) from TWRP. This happened to my "RR-N-v5.8.3-20170718-bacon-Official.zip" file. I managed to get around it by doing this: https://forum.xda-developers.com/showthread.php?t=2522762. So I could get this installed, sort of I think. The problem now was that it would show the very first oneplus boot screen for around 20 ish seconds, before it would reboot in a boot loop.
So I tried to install some other CM Lineage Os nightly thing (they said install that and then RR), but that didn't work either. This post was the one I donwloaded from (install this first, then RR should work).
I tried doing this both on TWRP 2.8.6.0 and 3.1.1.0 since I saw some post about the modem not being right from versions newer than 2.8.6.0.
Looking around a bit more I saw in some post someone talking about firmware..? Does this matter anything, also how is this different from the recovery or ROM? (new to this stuff)
In short, last working version of Android I had on there was 4.4.4 (think I followed this post). Using a Mac currently and have no problem with flashing, entering fastboot or recovery.
My procedure when I tried to install RR was:
Install the TWRP 3.1.1.0 or 2.8.6.0 (since I did it several times).
Wipe everything (Have nothing of value on the phone) cache, system, internal storage, dalvik and data. Also did a factory reset (from TWRP) before if that matters.
Copied RR and Gapps 7.1 ARM (not arm64) over.
Installed RR, wiped cache/dalvik. (or linear/cm (post above^^) when I tried that)
Installed Gapps, wiped cache/dalvik.
Boot loop.
Also tried with/without emptying cache/dalvik also chose to install both zips at once.
So can anyone clue in how I can proceed to get RR 7.1 onto my OPO? Any help is very much appreciated
I'm sorry if this wasn't the best post. Have an immense headache at the moment
Click to expand...
Click to collapse
Calm down.
You're right about that firmware thing,that is the one causing issue when you're trying to flash RR 5.8.3 over KitKat.
This is because the firmware that kitkat comes with,is old and don't support newer android versions,that's because it is made for KitKat only.
Always use latest Twrp(https://dl.twrp.me/bacon/).
Make sure you don't edit any zip like what you did with the Rom zip earlier(devs don't post non-working zips),I'm sure you've a backup of your non-edited zip,if not,re-download the zip.
Now boot into latest twrp,wipe everything except internal storage.
Firmware: https://drive.google.com/file/d/0BxysuRdzsJeWeW9JbTNwaUJKb1E/view?usp=drivesdk
Flash the above zip,then without wiping anything flash rom zip(unedited) then flash google apps package(opengapps.org)(optional).
Reboot.It should boot fine now.
Good luck!

Mr.Ak said:
Calm down.
You're right about that firmware thing,that is the one causing issue when you're trying to flash RR 5.8.3 over KitKat.
This is because the firmware that kitkat comes with,is old and don't support newer android versions,that's because it is made for KitKat only.
Always use latest Twrp(Can't post links withing 10 posts apparently...).
Make sure you don't edit any zip like what you did with the Rom zip earlier(devs don't post non-working zips),I'm sure you've a backup of your non-edited zip,if not,re-download the zip.
Now boot into latest twrp,wipe everything except internal storage.
Firmware:
Flash the above zip,then without wiping anything flash rom zip(unedited) then flash google apps package(Can't post links withing 10 posts apparently...)(optional).
Reboot.It should boot fine now.
Good luck!
Click to expand...
Click to collapse
Thank you so much! Got it working on 1st try with what you provided! Seems like the firmware thing was the bad guy in this scenario. A little interest, what specifically is the firmware in this case? Either way, rocking RR now and I'm really grateful

wahlmat said:
Thank you so much! Got it working on 1st try with what you provided! Seems like the firmware thing was the bad guy in this scenario. A little interest, what specifically is the firmware in this case? Either way, rocking RR now and I'm really grateful
Click to expand...
Click to collapse
I'm glad you got it up and running.
Here are some FAQs:
What is a Firmware? What is Modem?
- Firmware is the whole package of proprietary partitions of your device, modem itself is a NON-HLOS file responsible for your device's communications over Wi-Fi, Mobile Networks and other such stuff.
So what is the difference between firmware and ROM then?
- Firmware is the responsible partition for IMEIs, the modemst partitions hold your IMEI, persist holds your Mac addresses etc.
ROM is only a combination​ of system.img and boot.img (kernel)
What to restore if I loose my IMEI?
- Both the modemst partitions (IMP: considering you took a backup of them before)
What is the default firmware? (default= firmware which comes with the latest CM/ LineageOS 14.1 weeklies)
- c6-00241

Thanks a lot, once again

Help!
I'm not sure of all the specifics on my oneplus one but I accidentally updated the wrong update from my nightly bacon.. it now is stuck in Boot Loop I can get to the fastboot screen (it gets stuck there too) and I can get to the recovery, etc (but it is not the usual screen with all the folders (it was rooted).. it is now just four options in Cyanogenmod recovery.. none work. I do not want to lose my data :crying: .. Sadly my techy is not available to save me! Please help this untechy Cali Girl! I've googled and researched and its still like a foreign language.. Thank you!!

HisMuse said:
I'm not sure of all the specifics on my oneplus one but I accidentally updated the wrong update from my nightly bacon.. it now is stuck in Boot Loop I can get to the fastboot screen (it gets stuck there too) and I can get to the recovery, etc (but it is not the usual screen with all the folders (it was rooted).. it is now just four options in Cyanogenmod recovery.. none work. I do not want to lose my data :crying: .. Sadly my techy is not available to save me! Please help this untechy Cali Girl! I've googled and researched and its still like a foreign language.. Thank you!!
Click to expand...
Click to collapse
I am not 100% sure, but I would say, boot into fastboot, flash something like TWRP recovery, then you will be able to access the device files from the recovery. Just reflashing the boot shouldn't mess up anything as far as I am concerned. After that (when you've grabbed all the files you want), flash the newest firmware the guy linked above and install your latest 7.0 ROM

wahlmat said:
I am not 100% sure, but I would say, boot into fastboot, flash something like TWRP recovery, then you will be able to access the device files from the recovery. Just reflashing the boot shouldn't mess up anything as far as I am concerned. After that (when you've grabbed all the files you want), flash the newest firmware the guy linked above and install your latest 7.0 ROM
Click to expand...
Click to collapse
I can get phone to fastboot but it just stays on the screen that says fastboot.. do I need a computer?

HisMuse said:
I can get phone to fastboot but it just stays on the screen that says fastboot.. do I need a computer?
Click to expand...
Click to collapse
Yes you do. You need that + some software. Check out some "install custom recovery oneplus one" guides, you should be able to find something. Are you on Mac or Windows?

Yes I'm on Windows 10.. I tried removing battery overnight as well .. its not boiling hot anymore but still stuck in bootloop.

HisMuse said:
Yes I'm on Windows 10.. I tried removing battery overnight as well .. its not boiling hot anymore but still stuck in bootloop.
Click to expand...
Click to collapse
Download the Samsung ADB driver or whatever it was called, then flash a new recovery for it. There are multiple guides for doing that. After that you should be able to transfer your files to your pc while being in recovery mode

[Help Thread][Oneplus 7] Ask Any Question, Noob Friendly

This thread has been created
for
Questions & Answers/Troubleshooting
Specific to
Oneplus 7
Please feel free to share issues, questions and offer help. Noob questions are welcomed.
It is always best to use the Thanks button , in lieu of simply posting "Thank you".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please keep discussion focused, on questions pertaining to this Device
List of supporters​​@strongst​​​
To those seeking help: Please don't bombard the supporters with PMs asking for help. Instead, ask your question here in the thread so others can benefit from the solution to your problem as well. If you want to be sure someone particular gets notified of your question, put his / her username directly after an @.​If you have ROM related questions, post in the relevant ROM Q&A thread (if there is one) or directly in the ROM development thread. Thank you!​​Supporters: If you want to be put on or off the list, just make a request here in the thread!​Before posting anything, I strongly advise you to read​
XDA Forum Rules
[GUIDE] - XDA New User Guide - Getting started on XDA
XDA Tour
​Specific Threads and Guides for Oneplus 7​
[GUIDE][OP7][9.0/10.0] Unlock Bootloader | TWRP | Root with Magisk | Update
Repository of Oneplus 7 Stock Roms(use in search function too)
Oneplus 7 TWRP Recovery
Oneplus 7 MSM Tool OxygenOS(Unbrick tool)
Oneplus 7 MSM Tool HydrogenOS(Unbrick tool)
Extract boot.img from Rom zip to get stock recovery and kernel
Feedback towards Oneplus over OP7 pro thread(builds are nearly identical)
OnePlus 7 & 7 Pro Cross Device Development
​​Please look for a similar thread when visiting another device forum.
If you would like to create a [Help Thread] please Click Here. ​

Hello, I'm coming from several years of closed source Exynos Samsung. Struggle to get custom roms is a real pain. In addition, my love for bloatware, including big bro G apps/framework, is notoriously plunging to zero. So OP7 is gonna be my soon next phone.
Q: has anyone performed any deep clean of bloat and/or Google apps/framework on this model? Can it be done? In what %? Does it break anything natively working on OP7?
I know about the Tomatot, just what experience gives this process.
ps: I have a really bad OCD when reading com.google.abcdx
Nah, I'm good, just hate big brothers who spy on us.

w41ru5 said:
Hello, I'm coming from several years of closed source Exynos Samsung. Struggle to get custom roms is a real pain. In addition, my love for bloatware, including big bro G apps/framework, is notoriously plunging to zero. So OP7 is gonna be my soon next phone.
Q: has anyone performed any deep clean of bloat and/or Google apps/framework on this model? Can it be done? In what %? Does it break anything natively working on OP7?
I know about the Tomatot, just what experience gives this process.
ps: I have a really bad OCD when reading com.google.abcdx
Nah, I'm good, just hate big brothers who spy on us.
Click to expand...
Click to collapse
You can freeze/debloat nearly everything on OxygenOS without any impact compared to Samsung. I'm also debloat nearly everything from Google which comes pre-installed. But it's only minor compared to other OS.
Oneplus is one of the cleanest OS around and near to stock.

strongst said:
You can freeze/debloat nearly everything on OxygenOS without any impact compared to Samsung. I'm also debloat nearly everything from Google which comes pre-installed. But it's only minor compared to other OS.
Oneplus is one of the cleanest OS around and near to stock.
Click to expand...
Click to collapse
Right, thanks.
Steps: unlock bootloader, twrp, root Magisk, Tomatot, test.

w41ru5 said:
Right, thanks.
Steps: unlock bootloader, twrp, root Magisk, Tomatot, test.
Click to expand...
Click to collapse
Yeah, exactly. You can also have a look at xXx https://forum.xda-developers.com/on...agisk-rom-xxx-nolimits-7-0-speed-ram-t3933927 :good:

strongst said:
Yeah, exactly. You can also have a look at xXx https://forum.xda-developers.com/on...agisk-rom-xxx-nolimits-7-0-speed-ram-t3933927 :good:
Click to expand...
Click to collapse
Interesting concept. Thanks!

Hi guys. it would be good to add the two threads of MsmDownloadTool. The original that installs HydrogenOS and the other thread of a partner that puts OOS.
MsmDownloadTool HydrogenOS: https://forum.xda-developers.com/oneplus-7/how-to/unbrick-tool-oneplus-7-msmtool-hydrogen-t3953240
MsmDownloadTool OOS: https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325
---------- Post added at 04:57 PM ---------- Previous post was at 04:53 PM ----------
Another question, when using MsmDownloadTool you have to start the phone in EDL mode. This mode has a duration of 10 seconds, then the phone restarts. Any user who has used this tool can claim to restart in EDL mode after 10 seconds, but if you press Start, do you keep EDL mode by installing the ROM Stock?

Hello friends, I have a doubt, in other phones, when I wanted to put a clean ROM, even if it was the Stock, I always did it from TWRP:
1. Wipe / Advanced Wipe / and marked: Dalvik / ART Cache, System and Data.
2. Flash ROM OOS.
My questions are:
a) Has anyone tried to do that Wipe System? and can you confirm if you can then install the OOS ROM or cause problems and make brick ?.
b) Can you also do Wipe Vendor with Wipe System without causing brick?
Thank you and see if someone has done those steps and takes me out of doubt.

tURkOsANsE said:
Hello friends, I have a doubt, in other phones, when I wanted to put a clean ROM, even if it was the Stock, I always did it from TWRP:
1. Wipe / Advanced Wipe / and marked: Dalvik / ART Cache, System and Data.
2. Flash ROM OOS.
My questions are:
a) Has anyone tried to do that Wipe System? and can you confirm if you can then install the OOS ROM or cause problems and make brick ?.
b) Can you also do Wipe Vendor with Wipe System without causing brick?
Thank you and see if someone has done those steps and takes me out of doubt.
Click to expand...
Click to collapse
Why should you brick the phone when you wipe system /vendor and then flashing those partitions again when flashing OxygenOS?

strongst said:
Why should you brick the phone when you wipe system /vendor and then flashing those partitions again when flashing OxygenOS?
Click to expand...
Click to collapse
I have already read it several times in the forum, and they say that then you have to install ROM by fastboot. That's why I ask, in case a partner did it and it worked. when I updated on other ROM phones, instead of directly flashing the new ROM, first to wipe system and cache and then install the ROM update. to make a "semi-clean" installation. And now I don't know if it could be done by doing wipe system and vendor before installing.

Hello,
I ran into an issue today.
1- I downloaded the update through the phones updater. (9.5.8 BA. Full ZIP (2Go))
2- I went into TWRP and flashed latest twrp unofficial installer.
3- I flashed magisk
4- I rebooted into twrp, latest unofficial
5- Flashed OTA file from .OTA folder.
6- Flashed latest TWRP unofficial installer
7- Flashed magisk
=> stuck in bootloop.
Only fix was to go into twrp and manually select the other Slot, which worked thank god.
Anyone has a clue what I did wrong?

Nobody07 said:
Hello,
I ran into an issue today.
1- I downloaded the update through the phones updater. (9.5.8 BA. Full ZIP (2Go))
2- I went into TWRP and flashed latest twrp unofficial installer.
3- I flashed magisk
4- I rebooted into twrp, latest unofficial
5- Flashed OTA file from .OTA folder.
6- Flashed latest TWRP unofficial installer
7- Flashed magisk
=> stuck in bootloop.
Only fix was to go into twrp and manually select the other Slot, which worked thank god.
Anyone has a clue what I did wrong?
Click to expand...
Click to collapse
Hi guys, I put the steps I did to update when it is in OOS Stock with TWRP and Magisk, I did it from version 9.5.7 to 9.5.8 without problems, I do the method of installing everything in both slots, although there are people who only do it in a slot. I put what I did and it worked for me:
1. Backup with TWRP
2. Go to TWRP Reboot and see which slot you are in (then install it in the other slot).
3. In the first slot:
3.1. Go to Wipe Advanced and do Wipe Cache / Dalvik
3.2. OOS flashing
3.3. TWRP flashing
3.4. Flashing Magisk
4. Reboot TWRP
5. Change to second slot (go to Reboot and select the other slot:
5.1. Go to Wipe Advanced and do Wipe Cache / Dalvik
5.2. OOS flashing
5.3. TWRP flashing
5.4. Flashing Magisk
6. OPTIONAL: Change from Slot to the first (to go to Reboot and click on the other), I like to always work in the A, but that is a taste.
7. Reboot System.
PD: I use TWRP Blu_Spark:
https://github.com/engstk/android_device_oneplus_guacamole_unified_TWRP/releases/tag/v9.103
TWRP dev message: https://forum.xda-developers.com/showpost.php?p=79905872&postcount=29

tURkOsANsE said:
Hi guys, I put the steps I did to update when it is in OOS Stock with TWRP and Magisk, I did it from version 9.5.7 to 9.5.8 without problems, I do the method of installing everything in both slots, although there are people who only do it in a slot. I put what I did and it worked for me:
1. Backup with TWRP
2. Go to TWRP Reboot and see which slot you are in (then install it in the other slot).
3. In the first slot:
3.1. Go to Wipe Advanced and do Wipe Cache / Dalvik
3.2. OOS flashing
3.3. TWRP flashing
3.4. Flashing Magisk
4. Reboot TWRP
5. Change to second slot (go to Reboot and select the other slot:
5.1. Go to Wipe Advanced and do Wipe Cache / Dalvik
5.2. OOS flashing
5.3. TWRP flashing
5.4. Flashing Magisk
6. OPTIONAL: Change from Slot to the first (to go to Reboot and click on the other), I like to always work in the A, but that is a taste.
7. Reboot System.
PD: I use TWRP Blu_Spark:
https://github.com/engstk/android_device_oneplus_guacamole_unified_TWRP/releases/tag/v9.103
TWRP dev message: https://forum.xda-developers.com/showpost.php?p=79905872&postcount=29
Click to expand...
Click to collapse
Sooooo what you are saying is you flash on both slots so that both are ****ed if there is an issue?
Very smart.
With my issue I couldn't flash second slot anyway since I lose access to data.
Edit: Same issue with local update followed by twrp install through magisk.

Nobody07 said:
Sooooo what you are saying is you flash on both slots so that both are ****ed if there is an issue?
Very smart.
With my issue I couldn't flash second slot anyway since I lose access to data.
Edit: Same issue with local update followed by twrp install through magisk.
Click to expand...
Click to collapse
I put what I did and I had no problem. something you would do differently so that I don't let you install it:good:

Is there any news of pixel experience for oneplus 7??

Nobody07 said:
Sooooo what you are saying is you flash on both slots so that both are ****ed if there is an issue?
Very smart.
With my issue I couldn't flash second slot anyway since I lose access to data.
Edit: Same issue with local update followed by twrp install through magisk.
Click to expand...
Click to collapse
SO following on my issue, my suspicion is that there is something wrong on my slot A.
Slot B is where my current usable setup is. When installing an update it goes into slot A and it fails whatever I try.
My question would be, how can I copy my exact configuration of slot B to slot A, to try updating again?
Thank you !

Nobody07 said:
SO following on my issue, my suspicion is that there is something wrong on my slot A.
Slot B is where my current usable setup is. When installing an update it goes into slot A and it fails whatever I try.
My question would be, how can I copy my exact configuration of slot B to slot A, to try updating again?
Thank you !
Click to expand...
Click to collapse
Not sure what do you try there. Its much easier and safe to factory reset the whole phone and try to update it. Maybe you should also use MSMTool to go stock if nothing works.
Trust me it's a lot faster to backup your data and reset your phone before trying to copy slots.:good:

Kollachi said:
Not sure what do you try there. Its much easier and safe to factory reset the whole phone and try to update it. Maybe you should also use MSMTool to go stock if nothing works.
Trust me it's a lot faster to backup your data and reset your phone before trying to copy slots.:good:
Click to expand...
Click to collapse
I'm not going to share my whole life here, but that is not an option for now. I can't copy to my phone, and I can't install any tool on the computer I use.
Also it was stock before I flashed the actual 9.5.6. So chances are going back to stock would trigger the exact same thing. It had H2O on slot A when it arrived and OOS on slot B if I recall.
Whatever I am not able to do any of this right now, so copying over from slot B to A would be a good option if it was possible.

Nobody07 said:
I'm not going to share my whole life here, but that is not an option for now. I can't copy to my phone, and I can't install any tool on the computer I use.
Also it was stock before I flashed the actual 9.5.6. So chances are going back to stock would trigger the exact same thing. It had H2O on slot A when it arrived and OOS on slot B if I recall.
Whatever I am not able to do any of this right now, so copying over from slot B to A would be a good option if it was possible.
Click to expand...
Click to collapse
So you rather risk to lose all your data if you play with partitions and slots?
If there is no chance to backup data and reset the phone I wouldn't do anything for now. Hope you'll find a way to fix your problem.:good:

Kollachi said:
So you rather risk to lose all your data if you play with partitions and slots?
If there is no chance to backup data and reset the phone I wouldn't do anything for now. Hope you'll find a way to fix your problem.:good:
Click to expand...
Click to collapse
I guess I will just have to wait then.
What is your advice to be the more effective when it comes to backing up everything and putting it back again?
Can I just restore data + Internal storage + all the other partitions and it will be the exact same? If so should I first restore the data and then flash the ROM, or the other way around?
Thanks
Edit: Is there a possibility to only "reset" one slot?