I'm selling my HTC One (stock ROM, unlocked) so I wanted to wipe my data, apps and settings. I performed a factory reset/data wipe in CWM and rebooted and it would get stuck at the Verizon logo. I cleared cache, tried again, and got stuck at "Android is updating, Starting apps" for a good 20 minutes. Now it goes back to the Verizon logo.
Does the factory reset not leave the ROM intact? What can I do now just so it'll boot to a clean slate?
kram12085 said:
I'm selling my HTC One (stock ROM, unlocked) so I wanted to wipe my data, apps and settings. I performed a factory reset/data wipe in CWM and rebooted and it would get stuck at the Verizon logo. I cleared cache, tried again, and got stuck at "Android is updating, Starting apps" for a good 20 minutes. Now it goes back to the Verizon logo.
Does the factory reset not leave the ROM intact? What can I do now just so it'll boot to a clean slate?
Click to expand...
Click to collapse
Download the stock rooted odexed ROM from here: http://forum.xda-developers.com/showthread.php?t=2485319
After you flash it, wipe data and boot up.
Then flash the latest firmware and stock recovery through Fastboot (also that thread), and do another factory wipe using stock recovery.
Your S-Off / Unlocked status will not be affected by this.
NotATreoFan said:
Download the stock rooted odexed ROM from here: http://forum.xda-developers.com/showthread.php?t=2485319
After you flash it, wipe data and boot up.
Then flash the latest firmware and stock recovery through Fastboot (also that thread), and do another factory wipe using stock recovery.
Your S-Off / Unlocked status will not be affected by this.
Click to expand...
Click to collapse
Thanks for your help. Unfortunately, I've been at it for a good 5 hours now and I can't get past the first step.
Using TWRP, I've tried adb push <rom.zip> to /sdcard/, /mnt/sdcard/ and /data/media/ and every time it says it's successful, but the directories show up empty in TWRP. Without a removable SD card, I'm not sure how else I can get the ROM on the phone for flashing. I'm not sure if it's related or not, but everytime I reboot from TWRP, it says my phone isn't rooted. I select "Install" but it occurs again, even though supersu.apk is on the internal storage.
I also tried CWM but couldn't get past "format () expected 5 args, got 4. Installation aborted (Status 7)".
Does anyone have any suggestions on how I can get TWRP to flash the ROM? Thanks.
Try this cmd instead.
Code:
adb push nameofrom.zip /data/media/0/nameofrom.zip
kram12085 said:
Thanks for your help. Unfortunately, I've been at it for a good 5 hours now and I can't get past the first step.
Using TWRP, I've tried adb push <rom.zip> to /sdcard/, /mnt/sdcard/ and /data/media/ and every time it says it's successful, but the directories show up empty in TWRP. Without a removable SD card, I'm not sure how else I can get the ROM on the phone for flashing. I'm not sure if it's related or not, but everytime I reboot from TWRP, it says my phone isn't rooted. I select "Install" but it occurs again, even though supersu.apk is on the internal storage.
I also tried CWM but couldn't get past "format () expected 5 args, got 4. Installation aborted (Status 7)".
Does anyone have any suggestions on how I can get TWRP to flash the ROM? Thanks.
Click to expand...
Click to collapse
I recently returned my phone to stock in order to reset all the firmware and RIL data. Here is how I did it:
Enter recovery TWRP 2.6.3.4 (if you have 2.6.3.3 you may experience issues)
Boot into recovery, then format Data, System, Cache, and Internal Storage (this will leave the phone with NO ROM installed)
Reboot back into recovery. Answer No to the prompt to root your device.
Once back in recovery, Internal Memory will be available again (if you push the ROM before rebooting, it will not be there afterward)
Push the ROM using adb push ROM.zip /sdcard/ROM.zip (this will take 5-7 minutes for a 1.4GB file)
Flash the ROM in TWRP
Reboot when done, phone should boot up corrrectly
Reboot into Fastboot, push firmware.zip package
Reboot into ROM verify connectivity
Reboot into Fastboot, push stock recovery
Reboot into stock recovery, perform a Factory Reset
Boot into ROM
Once you are up and running on the latest 4.4.2 ROM with stock recovery, boot into Fastboot one last time and push TWRP 2.6.3.4. Your S-Off will not be affected and the new owner will be able to flash any ROMs they like.
If all of the above fails, then try using ADB Sideload from the Advanced menu in TWRP.
You guys are a life saver. TWRP 2.6.3.4 did the trick, it just wasn't available on the TWRP site so I didn't install it in the first place. Flashed the ROM and everything back to normal! Thanks for the help!
FWIW, none of the m7 versions of TWRP would load (stuck at "Entering Bootloader" screen). The Sprint version would load, but wouldn't mount the filesystem properly.
kram12085 said:
You guys are a life saver. TWRP 2.6.3.4 did the trick, it just wasn't available on the TWRP site so I didn't install it in the first place. Flashed the ROM and everything back to normal! Thanks for the help!
FWIW, none of the m7 versions of TWRP would load (stuck at "Entering Bootloader" screen). The Sprint version would load, but wouldn't mount the filesystem properly.
Click to expand...
Click to collapse
So what state is the phone in now? Stock w/ HTC recovery, or the Sprint TWRP?
NotATreoFan said:
So what state is the phone in now? Stock w/ HTC recovery, or the Sprint TWRP?
Click to expand...
Click to collapse
The former, stock. The Sprint TWRP loaded but didn't work right. I ended up finding 2.6.3.4 for VZW m7 on an xda thread, it's not on the TWRP site for some reason. That worked great.
kram12085 said:
The former, stock. The Sprint TWRP loaded but didn't work right. I ended up finding 2.6.3.4 for VZW m7 on an xda thread, it's not on the TWRP site for some reason. That worked great.
Click to expand...
Click to collapse
Excellent. Glad to see it all worked out.
Related
So I woke up this morning and I was running CM10, goo manager told me I had an update so I applied the update and low and behold it was CM9 on boot. Needless to say CM9 would not boot because nothing was wiped. So I decided to go back and re-flash 10 (CWM touch). So wiped and it said could not mount user data. after re-flashing it again would not boot. so I downloaded odin3 and the stock sprint rom and tried flashing that. No dice Odin screen gets stuck on "Erasing userdata.." for like 10 minutes, after it gets past the sprint LTE animation and get stuck booting in the glowing samsung screen. Also I cannot mount /SDcard in recovery but i can mount the external. I also cannot adb to the device. any Ideas????
JBurlison said:
So I woke up this morning and I was running CM10, goo manager told me I had an update so I applied the update and low and behold it was CM9 on boot. Needless to say CM9 would not boot because nothing was wiped. So I decided to go back and re-flash 10 (CWM touch). So wiped and it said could not mount user data. after re-flashing it again would not boot. so I downloaded odin3 and the stock sprint rom and tried flashing that. No dice Odin screen gets stuck on "Erasing userdata.." for like 10 minutes, after it gets past the sprint LTE animation and get stuck booting in the glowing samsung screen. Also I cannot mount /SDcard in recovery but i can mount the external. I also cannot adb to the device. any Ideas????
Click to expand...
Click to collapse
Sounds like odin flash is a success. When in recovery, can you wipe data/factory reset without error? That is a MUST after the odin flash. So boot into recovery and wipe
billard412 said:
Sounds like odin flash is a success. When in recovery, can you wipe data/factory reset without error? That is a MUST after the odin flash. So boot into recovery and wipe
Click to expand...
Click to collapse
No dice. The default android recovery was put back from the stock odin re-flash, it comes up with "ERROR unable to mount /Userdata.." "Cannot Find /Userdata.."
JBurlison said:
No dice. The default android recovery was put back from the stock odin re-flash, it comes up with "ERROR unable to mount /Userdata.." "Cannot Find /Userdata.."
Click to expand...
Click to collapse
Assuming you haven't already tried. See if a custom recovery can wipe or mount it. try to factory reset with TWRP (attched odin flash) and report back
billard412 said:
Assuming you haven't already tried. See if a custom recovery can wipe or mount it. try to factory reset with TWRP (attched odin flash) and report back
Click to expand...
Click to collapse
I think My stock image was bad I re-downloaded one and ran ODIN again and it worked.
Hello, I decided to root my device using Odin. I followed steps from a video and successfully rooted and installed twrp with flashify. When I booted to twrp I did a swipe without backup. I proceeded to install CM11 nightly with the gapps zip. Everything went well during installation and the device rebooted. I saw the cm mod logo upon reboot but I get error setup wizard failed after boot. I cant access the tablet or anything. All I see is the blue CM wallpaper and no apps. Upon further investigation, it turns out I flashed the wrong gapps zip? I tried rebooting to twrp recovery to reflash gapps. But problem is that I cant access twrp recovery only the stock recovery. It gives me limited options...update from adb, update from external, wipe data, wipe cache... Is there anyway to fix this? I installed adb and fastboot but when I install rom using adb sideload, i get signature failures all the time. I tried fastboot but apparently there is only download mode (which i used when rooting with odin). My device isnt recognized with fastboot devices command only adb devices. Can anyone help? I am new to this stuff.
Hi,
I will have your thread moved to your device section.
Good luck!
Try to wipe cache, then flash TWRP again by Odin.
If you can get TWRP up and running, you should be able to do the default wipe (cache, Dalvik, and user data) and flash CM11 and gapps again.
I think I had the same issue with CM11 not booting since I flashed the wrong gapps. But flash the right gapps, and you should be ok.
Hello everyone. I got a M8s from a friend wich is stuck in bootloader. The recovery didn't work at the begin, so I flashed twrp-recovery-2.8.6.0-m8s-qlul.img (flashing recovery using htc_fastboot.exe flash recovery theimagename.img) and it worked, then I tried to install a custom ROM Android_Pandora_Rom_1.2_(Discontinued).zip wich went all the steps fine until: Optimizing applications 8 of 204..then phone shat down to black screen. I booted back to bootloader, recovery, wiped and go for a new install, same issue.
After that, I was going to install lineage-13.0-20170715-UNOFFICIAL-m8qlul.zip where the developer of this rom recommends twrp-3.0.2-0-m8ql.img so I tried to flash it (flashing recovery using htc_fastboot.exe flash recovery theimagename.img), then tried to acces recovery, brings me back to bootloader so fast, rebooted bootloader, tried again, same problem. Tried the fasboot erase cache, no help.
The Hboot state is Unlocked and the S is ON. I tried some other recovery images, as stock_signed or 3.0.1, tried the one from M8 ToolKit but all failed and I still can't access recovery, everyting I do, it brings me back to bootloader. I did htc_fastboot boot recoveryfile.img wich works, but useless, the dd if= method to set the recovery permanent load did not work after reboot, /data and /system can't be mountet, it seems the "boot recovery" option is 99% readonly.
Any advice, any help please? It would be much appreciated! Thanks in advance!
Hi McBad,
you could try the following. I also had some problems to access the recovery.
- Again bring the phone into fastboot, flash the 2.8 recovery and access it
- Do a wipe for factory reset, not just only cache
- after that try to flash the twrp-3.0.1-0-m8ql.img version, the other one worked for me neither
- the try to install the custom ROM LOS13
I hope this will help you.
clone
It would be great if that would work, but flashing a recovery does not work. I flash it, success message, try to access it, vibrates and bootloader pops back instantly. That is the problem.
Sorry for double post, but can anyone help me with this? This is the second day I struggle to make it work. Any chance to make the hboot locked again? It didn't work with oem lock command. I would like to lock it so I can put an official zip on sdcard so the hboot to restore it to factory stock, some RUU. Or get it s-off so I can flash a rom from fastboot? The phone does not have any ROM on it, image crc results system 0x0, recovery 0x0. Please, help!
Have you tried sideloading twrp ?
McBad said:
Sorry for double post, but can anyone help me with this? This is the second day I struggle to make it work. Any chance to make the hboot locked again? It didn't work with oem lock command. I would like to lock it so I can put an official zip on sdcard so the hboot to restore it to factory stock, some RUU. Or get it s-off so I can flash a rom from fastboot? The phone does not have any ROM on it, image crc results system 0x0, recovery 0x0. Please, help!
Click to expand...
Click to collapse
Did you use HTC fastboot ?
Yes, I used htc_fastboot. Use sideloading? Like boot the img file directly? Tried that too.
McBad said:
Yes, I used htc_fastboot. Use sideloading? Like boot the img file directly? Tried that too.
Click to expand...
Click to collapse
Is there any way you could flash twrp 2.8 again? Once in that recovery you have sideloading option which you could use to transfer latest recovery onto your device. Are we talking about the same process?
McBad said:
Yes, I used htc_fastboot. Use sideloading? Like boot the img file directly? Tried that too.
Click to expand...
Click to collapse
Sideload as follows ....
McBad said:
Hello everyone. I got a M8s from a friend wich is stuck in bootloader. The recovery didn't work at the begin, so I flashed twrp-recovery-2.8.6.0-m8s-qlul.img (flashing recovery using htc_fastboot.exe flash recovery theimagename.img) and it worked, then I tried to install a custom ROM Android_Pandora_Rom_1.2_(Discontinued).zip wich went all the steps fine until: Optimizing applications 8 of 204..then phone shat down to black screen. I booted back to bootloader, recovery, wiped and go for a new install, same issue.
After that, I was going to install lineage-13.0-20170715-UNOFFICIAL-m8qlul.zip where the developer of this rom recommends twrp-3.0.2-0-m8ql.img so I tried to flash it (flashing recovery using htc_fastboot.exe flash recovery theimagename.img), then tried to acces recovery, brings me back to bootloader so fast, rebooted bootloader, tried again, same problem. Tried the fasboot erase cache, no help.
The Hboot state is Unlocked and the S is ON. I tried some other recovery images, as stock_signed or 3.0.1, tried the one from M8 ToolKit but all failed and I still can't access recovery, everyting I do, it brings me back to bootloader. I did htc_fastboot boot recoveryfile.img wich works, but useless, the dd if= method to set the recovery permanent load did not work after reboot, /data and /system can't be mountet, it seems the "boot recovery" option is 99% readonly.
Any advice, any help please? It would be much appreciated! Thanks in advance!
Click to expand...
Click to collapse
You can't install lineage if you haven't upgraded your device with latest official update. I would try reinstaling twrp 2.8, do a wipe of cache, dalvik cache and system, Sideload CM 12; and see how it goes. As well, while in twrp I would try relocking bootloader but only after an unsuccessful attempt to flash said rom. I don't know what your experience with soft bricked devices is, but sometimes it takes a while, different usb cable or usb slot on your PC, correct files in adb folder, re-download of rom or recovery because it easily gets corrupted while downloading. And obviously a fully charged device. Let us know how it goes.
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.
I just got my 5t a couple of days back. Unlocked the bootloader and used Blu spark twrp and magisk beta for root.
On restart phone would boot up to one plus logo, and then just go black. The notification light goes on. But nothing else.
Help please?
Edit FIXED(No data loss)
1. Boot into TWRP, clear cache. Hard reset(Volume up + Power from a switched off state).
2. Boot back into twrp.
3. Adb push full zip(Found here - Signed Flashable Zip)(Adb push follows this syntax - adb push /(filename).zip /storage/
4. On twrp goto the install menu, navigate to storage and install the file.
5. Optionally you may clear the cache and then install magisk. I couldn't get it to work without magisk but YMMW
Do a hard reset if you still can...
Manish54 said:
Do a hard reset if you still can...
Click to expand...
Click to collapse
Already did that, multiple times. No success.
Same happened to me. It eventually forced into a fastboot bootloop. I had to flash and boot twrp from fastboot again, and then flash the full ota zip and essentially start over.
Decided to skip the root though, until there is a solid ROM release or a stable magisk.
imatts said:
Same happened to me. It eventually forced into a fastboot bootloop. I had to flash and boot twrp from fastboot again, and then flash the full ota zip and essentially start over.
Decided to skip the root though, until there is a solid ROM release or a stable magisk.
Click to expand...
Click to collapse
I tried a similar approach. Cleared dalvik, hard reset then booted into Blu twrp. Flashed Full zip and then magisk again. Booted right up.
therock12123 said:
I tried a similar approach. Cleared dalvik, hard reset then booted into Blu twrp. Flashed Full zip and then magisk again. Booted right up.
Click to expand...
Click to collapse
Yes that was one of my many troubleshooting steps as well, didn't work for me.
Can you help me with this, having a similar issue when I tried to unroot and screwed everything up.
Can anyone help me with this? I'm trying to push via adb the stock os and it looks successful but I don't see it in TWRP.
It's not a big issue, you just flashed the wrong magisk, just boot into recovery and re flash the stock OS
With this type of brick, if u r able to access recovery just go amd reflash, this is not a major brick