What I was trying to do: I have a stock 4.4.2 AT&T GS3 that I wanted to root, and then install Cyanogen Mod.
What I did: I flashed Auto-Root with Odin 3.10, restarted and then flashed TWRP 2.8. I then booted to TWRP and attempted to wipe/format the phone but it showed some errors along the way, I think it was something having to do being unable to mount the SD card. I then rebooted into recovery and flashed CM12 and slim Google Apps zip. When it was flashing both I got a string of errors but it said it was successful.
Where I'm at now: When I try turning the phone on (without holding any buttons down) it attempts to boot straight to the TWRP but gets stuck at the blue TeamWin screen. I'm able to get to download mode by holding down the appropriate buttons. I'm wondering if there's anything I can flash from Odin to resolve this.
I also realized I have unbacked up photos on the device, I don't think the format was successful, is there any way to recover those?
Thanks
To recover the pictures, try re-installing TWRP, boot into TWRP, and mount the partitions. Connect the phone to your computer and copy your pictures.
TWRP
I have had this happen before. Try using Odin to flash an older version of TWRP, uncheck reboot after flash and then when it is done, do a battery pull. This has gotten me back into a working TWRP to restore my previous setup. Note: You made need to go back to 2.6. Once you have gotten back up and running flash to the current TWRP with the app.
Just rooted my phone and now after i flashed TWRP and I boot to TWRP the touchscreen becomes unresponsive. I'm now stuck in TWRP not knowing what to do. Any ideas? Everything worked just fine up until now.
Edit. Fixed now. Did a force reset and booted to recovery again and now it works. Strange...
Karl-Johan said:
Just rooted my phone and now after i flashed TWRP and I boot to TWRP the touchscreen becomes unresponsive. I'm now stuck in TWRP not knowing what to do. Any ideas? Everything worked just fine up until now.
Click to expand...
Click to collapse
Power plus Volume up will reboot the phone
power plus volume down to enter the bootloader then recovery
Do I need to backup my system if I dont intend to flash custom rom? How do I make a backup if needed?
You make a Backup in twrp Recovery. Be sure you installed
Twrp 2.8.6.4 beta. Its always better to make a Backup.
I made a backup of boot and system sections, is that enough or should i backup data section to? Its gonna be quite large since i got alot of stuff installed.
Gonna flash Viper later, all i have to do is a wipe of system cache and dalvik and then flash boot. Img from Viper and then flash viper zip-file. Phone is rooted and s-off.
Yesterday I decided to root my Nexus 7 2013 Wifi running stock 6.0.1 (build MOB30X). I first unlocked the bootloader, then immediately after that I flashed TWRP (twrp-3.0.2-0-flo.img). When I booted up, it would got stuck on a loop with TWRP running OpenRecoveryScript, saying something about unable to mount /data and renaming something, then reboot into TWRP again.
I did some research and it seemed I had to use a multirom TWRP version instead, so I went ahead and flashed it. Now I can go into TWRP, but when booting up I got stuck in the booting animation (the four spinning circles)
How can I fix this?
chinhodado said:
Yesterday I decided to root my Nexus 7 2013 Wifi running stock 6.0.1 (build MOB30X). I first unlocked the bootloader, then immediately after that I flashed TWRP (twrp-3.0.2-0-flo.img). When I booted up, it would got stuck on a loop with TWRP running OpenRecoveryScript, saying something about unable to mount /data and renaming something, then reboot into TWRP again.
I did some research and it seemed I had to use a multirom TWRP version instead, so I went ahead and flashed it. Now I can go into TWRP, but when booting up I got stuck in the booting animation (the four spinning circles)
How can I fix this?
Click to expand...
Click to collapse
Just run these two commands:
Code:
fastboot format cache
fastboot format userdata
Don't worry, you have lost all your data already while unlocking it.
The first boot and the booting animation will be initially longer than usual.
Incidentally, no need to use multirom-TWRP anymore because TWRP v3+ has been properly updated.
I actually solved this myself before k23m's reply by flashing the stock rom (MOB30X), then completed the initial setup, then reflashed TWRP (twrp-3.0.2-0-flo.img, not the multirom version). After that I booted up then restarted into recovery but then realized that TWRP had been wiped (only the android with the red triangle showing). So I re-flashed TWRP again and this time rebooted directly into recovery, and renamed the file recovery-from-boot.p into recovery-from-boot.backup. Then I flashed su and all went well.
k23m said:
Just run these two commands:
Code:
fastboot format cache
fastboot format userdata
Don't worry, you have lost all your data already while unlocking it.
The first boot and the booting animation will be initially longer than usual.
Incidentally, no need to use multirom-TWRP anymore because TWRP v3+ has been properly updated.
Click to expand...
Click to collapse
Thank you for the hint!
I recently bought an Oneplus 3 and wanted to root it, I succesfully unlocked my bootloader but when I try to flash TWRP and then load into the recovery mode the phone shows the oneplus logo for a few seconds and then turns itself off (even though ADB said it was succesfully flashed), when I reboot and go into recovery in brings me to the stock recovery.
Does anyone know how to fix this?
EDIT:
I previously had TWRP running on my Oneplus 3, at the first boot of TWRP I selected 'Read Only' because I saw that in a video, I couldn't flash a certain rom thats why I tought I had to update my TWRP, does this have something to do with it?
Anyone?
Don't let it boot into system. Fastboot TWRP, unplug your phone, boot into recovery manually (power + volume down).
In TWRP, select reboot system and it will apply a fix before it reboots and it should stick then.
Stock
krabman said:
Don't let it boot into system. Fastboot TWRP, unplug your phone, boot into recovery manually (power + volume down).
In TWRP, select reboot system and it will apply a fix before it reboots and it should stick then.
Click to expand...
Click to collapse
Can this be apply on other devices? Because I am having the same problem
kelvinchinedu said:
Can this be apply on other devices? Because I am having the same problem
Click to expand...
Click to collapse
This is universal: After flashing OEM ROM, don't boot into system. Boot into recovery, you will get into TWRP and from there boot into system. Or after flashing OEM ROM, flash Magisk and then boot into system.
kelvinchinedu said:
Can this be apply on other devices? Because I am having the same problem
Click to expand...
Click to collapse
Yeah, what he said. You can reboot recovery from TWRP and TWRP will patch it or you can flash magisk and it will do the work. What you can't do is flash TWRP and then boot directly to system because the stock recovery will be restored. Realistically do both, reboot recovery and then flash magisk for the win. I congratulate you on searching BTW, this thread is more than 2 years old. You may want to consider perusing the appropriate section for your other device. If it's a newer device with AB you will have some specific procedures to follow relating to that.
Used the search, used google, couldn't find any concrete answers
I am on Android N - unlocked bootloader - rooted via magisk, One Plus 3.
Could I do the following?
use TWRP to make a Nandroid Backup (System+Data+Boot) of my current set-up
then, manually flash (using twrp) Android O
find out I don't particularly like it
Go back to TWRP and Nandroid Restore back to Android N, as if no update ever happened
Or will there be issues?
Thanks
I do that with freedomos. 2.17(N)>3.1(O)>2.17. I restore nandroid and reflash rom
xGOGI said:
I do that with freedomos. 2.17(N)>3.1(O)>2.17. I restore nandroid and reflash rom
Click to expand...
Click to collapse
Should have mentioned I'm using stock rom.
So I'd restore the nandroid via twrp, and I should be good to go?
arthritis said:
Used the search, used google, couldn't find any concrete answers
I am on Android N - unlocked bootloader - rooted via magisk, One Plus 3.
Could I do the following?
use TWRP to make a Nandroid Backup (System+Data+Boot) of my current set-up
then, manually flash (using twrp) Android O
find out I don't particularly like it
Go back to TWRP and Nandroid Restore back to Android N, as if no update ever happened
Or will there be issues?
Thanks
Click to expand...
Click to collapse
There won't be any issue. You are alright with the procedure. Just make sure you use the correct twrp recovery for oreo coz if you use the non compatible recovery then you won't be able to boot into recovery once the oreo is flashed and you are forced to go with the stock recovery
Process I followed when I tried oreo last week
Take nandroid of all options available except system image. (system, data, bootloader, firmware, efs, etc.) on nougat twrp.
Do factory reset(wipe everything except internal storage) then flash oreo twrp image. Perform reboot. (no OS warning on reboot option screen will appear) just ignore it. It will boot to recovery even without the OS.
Once booted back to new recovery(oreo twrp)
Flash oreo stock zip and again flash oreo twrp image and reboot to recovery(this time the device will get stuck with a black screen and white LED). Don't panic, just force reboot the device and go to recovery again to flash magisk/supersu. Reboot to OS
Enjoy oreo
To go back to nougat
Reboot to recovery.
Perform factory reset as mentioned above.
Restore everything except bootloader, cache and dalvik cache
Flash nougat twrp recovery. Reboot to system.
Happy flashing.
Edit : use blu sparks recovery for nougat backup.
maxs8007 said:
There won't be any issue. You are alright with the procedure. Just make sure you use the correct twrp recovery for oreo coz if you use the non compatible recovery then you won't be able to boot into recovery once the oreo is flashed and you are forced to go with the stock recovery
Process I followed when I tried oreo last week
Take nandroid of all options available except system image. (system, data, bootloader, firmware, efs, etc.) on nougat twrp.
Do factory reset(wipe everything except internal storage) then flash oreo twrp image. Perform reboot. (no OS warning on reboot option screen will appear) just ignore it. It will boot to recovery even without the OS.
Once booted back to new recovery(oreo twrp)
Flash oreo stock zip and again flash oreo twrp image and reboot to recovery(this time the device will get stuck with a black screen and white LED). Don't panic, just force reboot the device and go to recovery again to flash magisk/supersu. Reboot to OS
Enjoy oreo
To go back to nougat
Reboot to recovery.
Perform factory reset as mentioned above.
Restore everything except bootloader, cache and dalvik cache
Flash nougat twrp recovery. Reboot to system.
Happy flashing.
Edit : use blu sparks recovery for nougat backup.
Click to expand...
Click to collapse
Thank you for the detailed procedure.
maxs8007 said:
There won't be any issue. You are alright with the procedure. Just make sure you use the correct twrp recovery for oreo coz if you use the non compatible recovery then you won't be able to boot into recovery once the oreo is flashed and you are forced to go with the stock recovery
Process I followed when I tried oreo last week
Take nandroid of all options available except system image. (system, data, bootloader, firmware, efs, etc.) on nougat twrp.
Do factory reset(wipe everything except internal storage) then flash oreo twrp image. Perform reboot. (no OS warning on reboot option screen will appear) just ignore it. It will boot to recovery even without the OS.
Once booted back to new recovery(oreo twrp)
Flash oreo stock zip and again flash oreo twrp image and reboot to recovery(this time the device will get stuck with a black screen and white LED). Don't panic, just force reboot the device and go to recovery again to flash magisk/supersu. Reboot to OS
Enjoy oreo
To go back to nougat
Reboot to recovery.
Perform factory reset as mentioned above.
Restore everything except bootloader, cache and dalvik cache
Flash nougat twrp recovery. Reboot to system.
Happy flashing.
Edit : use blu sparks recovery for nougat backup.
Click to expand...
Click to collapse
Thank you
Hi @maxs8007
thanks for the instructions. I did all that to get back to my nougat rom (PureFusion) and all seem good and phone booted fine. But i am stuck on login screen after booted up. I tried my correct password several times but to no avail. anyway reset my password without factory resetting again?
Thanks for the advise.
sqlpro said:
Hi @maxs8007
thanks for the instructions. I did all that to get back to my nougat rom (PureFusion) and all seem good and phone booted fine. But i am stuck on login screen after booted up. I tried my correct password several times but to no avail. anyway reset my password without factory resetting again?
Thanks for the advise.
Click to expand...
Click to collapse
Go to twrp - advanced - file manager - go to root folder - data - system - and delete files with .key extension. There will be 2 files delete both and reboot.
maxs8007 said:
Go to twrp - advanced - file manager - go to root folder - data - system - and delete files with .key extension. There will be 2 files delete both and reboot.
Click to expand...
Click to collapse
Thank you very much and that worked. I am back in the system.
BTW in your original instructions I had to re flash rom after restoring twrp backup otherwise it didn't boot and stuck at rom animation.
sqlpro said:
Thank you very much and that worked. I am back in the system.
BTW in your original instructions I had to re flash rom after restoring twrp backup otherwise it didn't boot and stuck at rom animation.
Click to expand...
Click to collapse
Thanks for pointing out, I must have forgot to add it. I'll update again.
Hi @maxs8007
I ran into this issue again today! after unlocking as per instructions yesterday and am back into phone and re-set the pin and all good. But today i had to reboot the phone and same issue again , cant login on the lock screen!! i tried deleting those files again but to no avail!!
any ideas before factory reset and loose my data ? Thanks.
sqlpro said:
Hi @maxs8007
I ran into this issue again today! after unlocking as per instructions yesterday and am back into phone and re-set the pin and all good. But today i had to reboot the phone and same issue again , cant login on the lock screen!! i tried deleting those files again but to no avail!
any ideas before factory reset and loose my data ? Thanks.
Click to expand...
Click to collapse
This should not have happened, anyways delete all those files which I've highlighted in the image below. This will reset the lock settings.
Oh sorry I forgot to attach the file. Here it is.
maxs8007 said:
There won't be any issue. You are alright with the procedure. Just make sure you use the correct twrp recovery for oreo coz if you use the non compatible recovery then you won't be able to boot into recovery once the oreo is flashed and you are forced to go with the stock recovery
Process I followed when I tried oreo last week
Take nandroid of all options available except system image. (system, data, bootloader, firmware, efs, etc.) on nougat twrp.
Do factory reset(wipe everything except internal storage) then flash oreo twrp image. Perform reboot. (no OS warning on reboot option screen will appear) just ignore it. It will boot to recovery even without the OS.
Once booted back to new recovery(oreo twrp)
Flash oreo stock zip and again flash oreo twrp image and reboot to recovery(this time the device will get stuck with a black screen and white LED). Don't panic, just force reboot the device and go to recovery again to flash magisk/supersu. Reboot to OS
Enjoy oreo
To go back to nougat
Reboot to recovery.
Perform factory reset as mentioned above.
Restore everything except bootloader, cache and dalvik cache
Flash nougat twrp recovery. Reboot to system.
Happy flashing.
Edit : use blu sparks recovery for nougat backup.
Click to expand...
Click to collapse
Hi, OP here. Thanks for this guide.
Unfortunately, it did not work out for me.
Take nandroid of all options available except system image. (system, data, bootloader, firmware, efs, etc.) on nougat twrp.
Done
Do factory reset(wipe everything except internal storage)
Wiped fine although I got an error of not being able to wipe 'USB-OTG' or whatever it's called. I ignored it and moved on.
then flash oreo twrp image.
I googled oreo twrp image and got an img file with filename "TWRP-Oreo-OnePlus-3-3T". When I installed the img, it asked the options to choose Boot, System, or Recovery - so I chose System.
Then I rebooted and went back to recovery.
Flash oreo stock zip
flash oreo twrp image
Done
reboot to recovery(this time the device will get stuck with a black screen and white LED). Don't panic, just force reboot the device and go to recovery again to flash magisk/supersu.
This is where it ends. I get stuck at the OnePlus loading screen and forced reboot into twrp and flashed magisk. Once I boot up the OS, I get stuck at the OnePlus logo and that's it.
I actually re-did ALL of the steps again (in case I made a mistake) and still, the same issue. No progression.
Once I gave up on Oreo, I decided to go restore my nandroid
Reboot to recovery. Perform factory reset as mentioned above.
Wiped
Restore everything except bootloader, cache and dalvik cache
Here's the issue:
I press Restore (I uncheck both bootloader and cache, but there's no option for a specific dalvik cache- unless I'm not looking hard enough?) and I get the 255 Error.
Flash nougat twrp recovery. Reboot to system.
I tried to ignore that error and flash the twrp recovery.
Rebooted and it took me to fastboot. Regardless of I keep trying to reboot system it won't work.
I actually made two separate nandroid backups (the same 'everything except system image' as you've described) in case one of the backups was corrupted. Both backups ended up with the same error.
I got too tired of all these errors and just found a stock recovery and ROM and flashed it back. Now, all my apps and settings are gone. To be honest, I just want my phone back to where it was with Nougat.
Can anyone assist me?
@maxs8007, Like I said I did that already but nope still same issue. It wouldn't let me do matter what I did.
---------- Post added at 04:59 AM ---------- Previous post was at 04:54 AM ----------
arthritis said:
Hi, OP here. Thanks for this guide.
Unfortunately, it did not work out for me.
Take nandroid of all options available except system image. (system, data, bootloader, firmware, efs, etc.) on nougat twrp.
Done
Do factory reset(wipe everything except internal storage)
Wiped fine although I got an error of not being able to wipe 'USB-OTG' or whatever it's called. I ignored it and moved on.
then flash oreo twrp image.
I googled oreo twrp image and got an img file with filename "TWRP-Oreo-OnePlus-3-3T". When I installed the img, it asked the options to choose Boot, System, or Recovery - so I chose System.
Then I rebooted and went back to recovery.
Flash oreo stock zip
flash oreo twrp image
Done
reboot to recovery(this time the device will get stuck with a black screen and white LED). Don't panic, just force reboot the device and go to recovery again to flash magisk/supersu.
This is where it ends. I get stuck at the OnePlus loading screen and forced reboot into twrp and flashed magisk. Once I boot up the OS, I get stuck at the OnePlus logo and that's it.
I actually re-did ALL of the steps again (in case I made a mistake) and still, the same issue. No progression.
Once I gave up on Oreo, I decided to go restore my nandroid
Reboot to recovery. Perform factory reset as mentioned above.
Wiped
Restore everything except bootloader, cache and dalvik cache
Here's the issue:
I press Restore (I uncheck both bootloader and cache, but there's no option for a specific dalvik cache- unless I'm not looking hard enough?) and I get the 255 Error.
Flash nougat twrp recovery. Reboot to system.
I tried to ignore that error and flash the twrp recovery.
Rebooted and it took me to fastboot. Regardless of I keep trying to reboot system it won't work.
I actually made two separate nandroid backups (the same 'everything except system image' as you've described) in case one of the backups was corrupted. Both backups ended up with the same error.
I got too tired of all these errors and just found a stock recovery and ROM and flashed it back. Now, all my apps and settings are gone. To be honest, I just want my phone back to where it was with Nougat.
Can anyone assist me?
Click to expand...
Click to collapse
Buddy from my experience the whole thing too finicky and am thinking just factory reset and stick with stock rom. I wasted so much time already. Everytime I get different error, probably recoveries still not fully compatible with Oreo.
sqlpro said:
@maxs8007, Like I said I did that already but nope still same issue. It wouldn't let me do matter what I did.
---------- Post added at 04:59 AM ---------- Previous post was at 04:54 AM ----------
Buddy from my experience the whole thing too finicky and am thinking just factory reset and stick with stock rom. I wasted so much time already. Everytime I get different error, probably recoveries still not fully compatible with Oreo.
Click to expand...
Click to collapse
Could you please tell me what error you get on the lock screen? Could you post an image so that I can get a better idea of what's happening with your device? Also could you please confirm which files have you deleted? This time you need to delete 5 files which are related to lock screen setting and those are the only files responsible for lock settings on the device. I'm somewhat confused because I never ran into such issue while I did the oreo thing
If you have decided to flash stock then just make a backup of data partition so that you won't loose your data and you can easily restore it via twrp.
---------- Post added at 01:06 AM ---------- Previous post was at 12:42 AM ----------
arthritis said:
I googled oreo twrp image and got an img file with filename "TWRP-Oreo-OnePlus-3-3T". When I installed the img, it asked the options to choose Boot, System, or Recovery - so I chose System.
Click to expand...
Click to collapse
I read the entire post and here what I've to say. The above quoted steps is where you went wrong. The recovery needs to to be flashed as a recovery and not as system.
In your case the nougat recovery was never replaced with the oreo recovery because you flashed it as a system. This is where it went wrong. Sorry for the dalvik cache and USB - otg, I didn't mentioned about them. Those are the least important points in flashing though I should have mentioned that already
The next thing you mentioned is you went back to recovery which at that moment was nougat recovery and not oreo recovery. I'll link the modded recovery I used for oreo below
The next thing you did is you flashed oreo zip and again flashed the oreo recovery but as you flashed the recovery as system, the oreo stock rom was automatically replaced with recovery because you flashed it as system and the device didn't boot because there was no android OS to boot up
You got stuck on oneplus boot up screen. (this was going to happen because of the same flashing error at your end).
You were unable to boot back to nougat as well because of the same issue.. Never flash the recovery as system. This won't let you boot the device.
To restore your nandroid backup just follow the steps below
As you confirmed you booted to stock rom with a stock recovery.
Flash nougat twrp via fastboot
Boot back to the twrp recovery and restore the nandroid backup and you are good to go
---------- Post added at 01:18 AM ---------- Previous post was at 01:06 AM ----------
I'll make a video in my free time to help you guys with the steps that I've followed to flash oreo rom and how i came back to nougat successfully.
Hello @maxs8007
Sorry I didn't have any screen shots of the prompt and finally I was fed up with the whole process and had to switch back to oreo stock rom.
Login prompt I was referring to was standard pin required load android. Black background with only pin entry.
BTW I tried blu twrp recovery oreo version and nougat version.
What's interesting is, after several failed attempts it said I got 10 more tries before phone wiped out but after 10 attempts it started counting backwards from zero, - 1,-2 etc., finally I had to flash stock recovery via fastboot and selected forgot password option which reset my phone.
BTW I have deleted all those files from data/system I found another thread but no dice.
Thank you for trying to help us all.
@maxs8007 followed your steps. Booted to oreo, didn't felt as stable as nougat then booted back to nougat. You saved me. Thanks.
sqlpro said:
Hello @maxs8007
Sorry I didn't have any screen shots of the prompt and finally I was fed up with the whole process and had to switch back to oreo stock rom.
Login prompt I was referring to was standard pin required load android. Black background with only pin entry.
BTW I tried blu twrp recovery oreo version and nougat version.
What's interesting is, after several failed attempts it said I got 10 more tries before phone wiped out but after 10 attempts it started counting backwards from zero, - 1,-2 etc., finally I had to flash stock recovery via fastboot and selected forgot password option which reset my phone.
BTW I have deleted all those files from data/system I found another thread but no dice.
Thank you for trying to help us all.
Click to expand...
Click to collapse
I'm sorry that I was unable to help you. The thing is I never used the pin prompt to load android because I reboot too often to flash things via recovery and its too much of a hassle to enter the pin everytime the device is booted and I think it's too much to a security for a android device when there's already a lock screen present once booted to secure the device.
Please don't put the pin entry to load android next time if you flash stuff regularly. It will save you the hassle of going back to stock rom and recovery when something like this ever happens again. The files which I told you to delete in the image I posted above remove the lock screen protection completely
The login pin at the boot to load android was implemented to avoid unauthorized access to the device in case it gets stolen or lost.
maxs8007 said:
I'm sorry that I was unable to help you. The thing is I never used the pin prompt to load android because I reboot too often to flash things via recovery and its too much of a hassle to enter the pin everytime the device is booted and I think it's too much to a security for a android device when there's already a lock screen present once booted to secure the device.
Please don't put the pin entry to load android next time if you flash stuff regularly. It will save you the hassle of going back to stock rom and recovery when something like this ever happens again. The files which I told you to delete in the image I posted above remove the lock screen protection completely
The login pin at the boot to load android was implemented to avoid unauthorized access to the device in case it gets stolen or lost.
Click to expand...
Click to collapse
Frankly no clue why deleting those files didn't reset my pins and I even deleted gatekeeper files too.
Maybe these are lock screen key files and android boot prompt stored somewhere else. Not sure though.