Database Users

[Guide] How to restore to pure stock (no root, FFF, etc.) with TWRP

just thought I'd post as a quick note;
if you wish to restore to stock from CM7 or just go back to stock with no root or FireFireFire at all, TWRP works for it. quick tutorial:
1. download amazon's stock software: http://www.amazon.com/gp/help/customer/display.html/ref=hp_navbox_kspot_fireupdate?nodeId=200790620
2. rename it to update.zip and place on root of sdcard
3. boot into TWRP and wipe cache, dalvik cache and factory reset
4. flash update.zip, however it will stop the install mid-way and say it can not find the misc volume or something, but fear not
5. boot up and you'll be restored to stock! note FireFireFire and TWRP will have to be re-installed as well as re-root
I had issues at first boot like WiFi not working, but a factory reset changed that. now I'm gonna reinstall FFF and TWRP for some kernel action

This worked for my Kindle Fire. But it did give me a scare though, since after I flashed it the Kindle Fire seemed to be on a boot loop as it kept blinking the "Kindle Fire" boot screen over and over, but then it suddenly started up.

When I try to do this, I get an error from TWRP saying that it could not mount /sdcard/udpate.zip, any ideas?

Make sure your file isnt update.zip.zip
Check your windows settings for hidden file extensions.
Sent from my Galaxy Nexus using XDA App

Yeah, I double checked that. Been bit by that before. I am using ubuntu also.

lonelliott said:
When I try to do this, I get an error from TWRP saying that it could not mount /sdcard/udpate.zip, any ideas?
Click to expand...
Click to collapse
Make sure you checked the MD5sum of the file against what it is supposed to be. this would ensure that the file didn't get corrupted in the transfer(s)

I will check it again to be safe. Also, I tried to do a restore with a system.img and it said the file was to large, using fastboot and quit the flash.

Restore to stock from CM7 worked fine.
​

Quick question, does the restore/factory reset wipe the SD Card?
Thanks,
~J

jmbneaf said:
Quick question, does the restore/factory reset wipe the SD Card?
Thanks,
~J
Click to expand...
Click to collapse
nope, just system.

gqkevyn said:
This worked for my Kindle Fire. But it did give me a scare though, since after I flashed it the Kindle Fire seemed to be on a boot loop as it kept blinking the "Kindle Fire" boot screen over and over, but then it suddenly started up.
Click to expand...
Click to collapse
its happening to me now too. im stuck at the "KINDLE FIRE" bootscreen, but it hasn't moved yet. how long did yours sit there for until it fully booted? no clue what to do now?
ive tried everything i could think of: http://forum.xda-developers.com/showthread.php?t=1443107
if you guys know of anything please let me know...have a giant paperweight until then
EDIT: DO NOT USE THIS METHOD, YOU WILL BRICK YOUR KINDLE!

This method worked perfectly for me, first go. Way easy. I was on one of the latest CM9 builds and downloaded the stock files from the Amazon link posted by the OP.
-Re-name the file in ES File explorer to update.zip
-Moved it to the root of the SD card
-Booted in to TWRP
-Factory Wipe/Restore
-Wiped Cache
-Wiped Dalvik Cache
-Wiped System
-Installed the "update.zip"
-Wiped cache/dalvik again
-Rebooted
-My Kindle Fire booted back into stock 6.2.2 in less the a minute.

Back to Stock
kmmxracer said:
This method worked perfectly for me, first go. Way easy. I was on one of the latest CM9 builds and downloaded the stock files from the Amazon link posted by the OP.
-Re-name the file in ES File explorer to update.zip
-Moved it to the root of the SD card
-Booted in to TWRP
-Factory Wipe/Restore
-Wiped Cache
-Wiped Dalvik Cache
-Wiped System
-Installed the "update.zip"
-Wiped cache/dalvik again
-Rebooted
-My Kindle Fire booted back into stock 6.2.2 in less the a minute.
Click to expand...
Click to collapse
Followed these instructions and Robert is your father's brother!!
Thanks!

adz1966 said:
Followed these instructions and Robert is your father's brother!!
Thanks!
Click to expand...
Click to collapse
Ditto. Worked perfectly. No problems at all and I'm back to completely stock.

I'm stuck at a black screen with my power button orange...any ideas?

wormat22 said:
I'm stuck at a black screen with my power button orange...any ideas?
Click to expand...
Click to collapse
Same here.... does the restore point I have mess that up?
Update
I tried a couple more times until I realized what I did wrong.. loll
I zipped the file instead of renaming it. Stupid me.

bal1985 said:
its happening to me now too. im stuck at the "KINDLE FIRE" bootscreen, but it hasn't moved yet. how long did yours sit there for until it fully booted?
Click to expand...
Click to collapse
I would say a good 5 minuets or so.
EDIT: DO NOT USE THIS METHOD, YOU WILL BRICK YOUR KINDLE!
Click to expand...
Click to collapse
Just because you didn't do it right, doesn't mean everyone else will brick their kindle. I just used this method and it worked perfect. Just waiting for more charge to finish it off with a factory reset.

Would love to see a video on this
Sent from my Touchpad using xda premium

http://www.youtube.com/watch?v=V0-4icc6ahk
it's an older one - superoneclick don't work any more - the rest is the same

zonbal33 said:
EDIT: DO NOT USE THIS METHOD, YOU WILL BRICK YOUR KINDLE!
Click to expand...
Click to collapse
I would like to also Confirm that this is false.. It worked flawless with mines. Dont be afraid of the flashing kindle fire logo.. Just be patient.

Need help - freezes and restarts

I updated my phone to latest liquidsmooth rom two days ago and the phone freezes and restarts/reboots randomly like sometimes when im on phone/ playing a game/ using browser/ connected to charger. Yesterday I changed rom to latest carbon rom. Did install (3 wipes) as told in the thread but im still having the reboots.
Im using TWRP recovery and had used Utility 1.10 to go back to stock from Energy rom with safestrap recovery.
Can tell me whats the prob? Is it the kernel problem?

Have you tried upgrading or reflashing TWRP and then doing a clean install of Carbon? Its probably worth doing a fresh download of each first just to make sure you cover all your bases. These reboots were happening to me a few months ago and it drove me mad. following these steps fixed it for me.

jcxmej said:
I updated my phone to latest liquidsmooth rom two days ago and the phone freezes and restarts/reboots randomly like sometimes when im on phone/ playing a game/ using browser/ connected to charger. Yesterday I changed rom to latest carbon rom. Did install (3 wipes) as told in the thread but im still having the reboots.
Im using TWRP recovery and had used Utility 1.10 to go back to stock from Energy rom with safestrap recovery.
Can tell me whats the prob? Is it the kernel problem?
Click to expand...
Click to collapse
Honestly, if you're using SafeStrap, that might be your problem. Remove SS and flash the ROM in TWRP. If your bootloader is unlocked, you don't really want to use SS. Also, make a stock backup in TWRP, prior to flashing. This way, it will be easier for you to recover in the future, and you won't need to go through the painful process of fastboot.

RikRong said:
Honestly, if you're using SafeStrap, that might be your problem. Remove SS and flash the ROM in TWRP. If your bootloader is unlocked, you don't really want to use SS. Also, make a stock backup in TWRP, prior to flashing. This way, it will be easier for you to recover in the future, and you won't need to go through the painful process of fastboot.
Click to expand...
Click to collapse
Like I said on first post Im using TWRP now. Previously I was using safestrap. I removed it and installed TRWP. Anyways thanks.

PantherVT said:
Have you tried upgrading or reflashing TWRP and then doing a clean install of Carbon? Its probably worth doing a fresh download of each first just to make sure you cover all your bases. These reboots were happening to me a few months ago and it drove me mad. following these steps fixed it for me.
Click to expand...
Click to collapse
Thanks man. I will upgrade TWRP or reinstall it first. Thanks for that tip. Will post again if it doesnt work.

Still having those restarts. Really irritating. Froze and rebooted 4 5 times today morning while I was on call and trying to message. I reflashed reinstalled everything. I used both Utility 1.10 and 1.20. Im getting reboots even the stock ROM after using the Utility. I am confused which Utility I should be using. I had no issue of rebooting before flashing using Utility. Can someone give me exact procedure to reflash so that i know i am not missing out anything.

jcxmej said:
Still having those restarts. Really irritating. Froze and rebooted 4 5 times today morning while I was on call and trying to message. I reflashed reinstalled everything. I used both Utility 1.10 and 1.20. Im getting reboots even the stock ROM after using the Utility. I am confused which Utility I should be using. I had no issue of rebooting before flashing using Utility. Can someone give me exact procedure to reflash so that i know i am not missing out anything.
Click to expand...
Click to collapse
you might need to do a clean install.
- what version of TWRP are you using (anything other than 2.4 should be fine)?
- to perform the clean install, mount system, then try wiping everything (system, factory reset, & internal storage) - DO NOT WIPE external SD (I presume this is where you store the ROM files
- after wiping, reboot recovery, then install whichever 4.2.2 ROM you want follow by the GApps (use the 3/2013 version)

jco23 said:
you might need to do a clean install.
- what version of TWRP are you using (anything other than 2.4 should be fine)?
- to perform the clean install, mount system, then try wiping everything (system, factory reset, & internal storage) - DO NOT WIPE external SD (I presume this is where you store the ROM files
- after wiping, reboot recovery, then install whichever 4.2.2 ROM you want follow by the GApps (use the 3/2013 version)
Click to expand...
Click to collapse
Since TWRP wasnt working for me, I tried flashing with CWM recovery by hashcode. Still had reboots. I was using TWRP 2.3.2.3
When you say wipe everything, does it include 'modem' and 'pds'? Saw these two options also inside Mount/Format menu of CWM recovery.
Also there was an option 'Mount sdcard' (internal I suppose) but when i click it nothing happens it remains as Mount sdcard. Rest of it changes from Mount to Unmount. Is there some problem with that?
Do I have to just Mount system only? Also after rebooting recovery do I have to mount system again?
I try again as you said meanwhile.

jcxmej said:
Since TWRP wasnt working for me, I tried flashing with CWM recovery by hashcode. Still had reboots. I was using TWRP 2.3.2.3
When you say wipe everything, does it include 'modem' and 'pds'? Saw these two options also inside Mount/Format menu of CWM recovery.
Also there was an option 'Mount sdcard' (internal I suppose) but when i click it nothing happens it remains as Mount sdcard. Rest of it changes from Mount to Unmount. Is there some problem with that?
Do I have to just Mount system only? Also after rebooting recovery do I have to mount system again?
I try again as you said meanwhile.
Click to expand...
Click to collapse
nope, just system/factory reset/internal storage.
yes, make sure everything is mounted (checked) so that they read "unmount"

jco23 said:
nope, just system/factory reset/internal storage.
yes, make sure everything is mounted (checked) so that they read "unmount"
Click to expand...
Click to collapse
Did exactly like said. Got into CWM recovery. Mounted system. Formatted system, data, cache, sdcard. Did factory reset and wiped the caches. Then rebooted recovery. Then installed the ROM, 3/13 gapps, gsm fix. Reboot system. Still no use. I got 2 reboots in 5 mins in the ROM. I checked the md5 of the files and its ok. Dont know what else to try?

jcxmej said:
Did exactly like said. Got into CWM recovery. Mounted system. Formatted system, data, cache, sdcard. Did factory reset and wiped the caches. Then rebooted recovery. Then installed the ROM, 3/13 gapps, gsm fix. Reboot system. Still no use. I got 2 reboots in 5 mins in the ROM. I checked the md5 of the files and its ok. Dont know what else to try?
Click to expand...
Click to collapse
which ROM are you trying to install?

jco23 said:
which ROM are you trying to install?
Click to expand...
Click to collapse
LiquidSmooth v2.9 by DHacker29
http://forum.xda-developers.com/showthread.php?t=2373703
I have also tried Carbon ROM but was having reboots with that too. I liked liquidsmooth better so trying to make this work.

jcxmej said:
LiquidSmooth v2.9 by DHacker29
http://forum.xda-developers.com/showthread.php?t=2373703
I have also tried Carbon ROM but was having reboots with that too. I liked liquidsmooth better so trying to make this work.
Click to expand...
Click to collapse
are you flashing a kernel at the same time?
I would recommend trying a basic 4.2.2 ROM right now - like unoffical AOKP.
another problem could be the GApps or GSM fix. try installing just the ROM without the GApps perhaps?
carbon was very solid too. unfortunately, I can't help you with the GSM fix, as I am CDMA.

jco23 said:
are you flashing a kernel at the same time?
I would recommend trying a basic 4.2.2 ROM right now - like unoffical AOKP.
another problem could be the GApps or GSM fix. try installing just the ROM without the GApps perhaps?
carbon was very solid too. unfortunately, I can't help you with the GSM fix, as I am CDMA.
Click to expand...
Click to collapse
Okay i will try but had this reboot issue even with the stock ROM after flashing with Utility 1.20.

jcxmej said:
Okay i will try but had this reboot issue even with the stock ROM after flashing with Utility 1.20.
Click to expand...
Click to collapse
hmm.... not really sure then. perhaps you lost root? try re-installing SuperSU - I'm just grasping at straws here.
someone mentioned a similar issue:
http://forum.xda-developers.com/showthread.php?p=44317692#post44317692

jco23 said:
hmm.... not really sure then. perhaps you lost root? try re-installing SuperSU - I'm just grasping at straws here.
someone mentioned a similar issue:
http://forum.xda-developers.com/showthread.php?p=44317692#post44317692
Click to expand...
Click to collapse
I think I have root access I had no issue with it. Okay maybe I will check the thread you gave. Anyways I tried Eclipse ROM which is based AOKP. Still had reboots. So I switched back to liquid. Anyways Im gonna keep trying the basics. If anyone has any suggestions I could try its welcome.
PS. Should I flash another kernel with the ROM just in case ? I have been only installing ROM and gapps only till now.

jcxmej said:
I think I have root access I had no issue with it. Okay maybe I will check the thread you gave. Anyways I tried Eclipse ROM which is based AOKP. Still had reboots. So I switched back to liquid. Anyways Im gonna keep trying the basics. If anyone has any suggestions I could try its welcome.
PS. Should I flash another kernel with the ROM just in case ? I have been only installing ROM and gapps only till now.
Click to expand...
Click to collapse
I don't think changing the kernel will do it.... I suspect the issue is with your recoveries - will respond in other thread....

[Q&A] [ROM][LOLLIPOP][5.0][LRX21T][UNTOUCHED PURE STOCK][Nexus⁴]

Q&A for [ROM][LOLLIPOP][5.0][LRX21T][UNTOUCHED PURE STOCK][Nexus⁴]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][LOLLIPOP][5.0][LRX21T][UNTOUCHED PURE STOCK][Nexus⁴]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

So i kinda figured it out.
well, I sort of did something(i think) and its now working fine... I went to twrp.. did a factory reset. Then went for advance wipe and wiped system cache and dalvik. Then followed the same procedure. Bootloader-->radio-->Rom-->Kernel. It worked just fine. The first boot took some 15 minutes.

does the internal storage work for you? it works only on twrp for me :/
i can't see anything in file explorer and canìt restore from twrp :/ that's a big problem guys.

If you can not see your old nandroid backups
After rooting If you can not see your old nandroid backups
Via file explorers try to enable usb debuging from
dev. opt. if not worked (Recovires or SuperSU issue)
But you can see and restore your old or new backups via recovery (TWRP tested)
New recoveries and superSU may fix this issues.
Want to ask? SuperSU XDA Thread here
Note: SE Linux Mod Changer may help to fix this issue
Recommended Recovery is TWRP 2.8.1.0
​

HunterAtXDA said:
I also got this message
Code:
unmount of /system failed: no such volume
followed by
Code:
unmount of /data failed: no such volume
a few minutes later. The process finished a few minutes later without any more output but I'm booting now after wiping the cache and everything seems fine.
Click to expand...
Click to collapse
I had the this same problem. After installing everything, I let it sit for 20 minutes and it finally showed the Android logo. After that it was stuck on a black screen. I wiped everything and repeated the install procedure again, minus the kernal, and got the same "unmount of /system failed: no such volume" while flashing the rom zip. It booted after a while and everything works except my storage is FUKT. I cant see any of my pictures, music, etc, and the only thing I see via PC is the DCIM folder which is empty. Not cool

mattgrantlackey said:
I had the this same problem. After installing everything, I let it sit for 20 minutes and it finally showed the Android logo. After that it was stuck on a black screen. I wiped everything and repeated the install procedure again, minus the kernal, and got the same "unmount of /system failed: no such volume" while flashing the rom zip. It booted after a while and everything works except my storage is FUKT. I cant see any of my pictures, music, etc, and the only thing I see via PC is the DCIM folder which is empty. Not cool
Click to expand...
Click to collapse
Recommended Recovery is TWRP 2.8.1.0

mattgrantlackey said:
I had the this same problem. After installing everything, I let it sit for 20 minutes and it finally showed the Android logo. After that it was stuck on a black screen. I wiped everything and repeated the install procedure again, minus the kernal, and got the same "unmount of /system failed: no such volume" while flashing the rom zip. It booted after a while and everything works except my storage is FUKT. I cant see any of my pictures, music, etc, and the only thing I see via PC is the DCIM folder which is empty. Not cool
Click to expand...
Click to collapse
Nothing wrong with my storage. I installed the bootloader, radio, and rom on top of my existing 4.4.4 rom by sideloading in CWM. Wiped caches and rebooted to make sure everything was working, then back to CWM to sideload the kernel. I haven't rooted yet.

HunterAtXDA said:
Nothing wrong with my storage. I installed the bootloader, radio, and rom on top of my existing 4.4.4 rom by sideloading in CWM. Wiped caches and rebooted to make sure everything was working, then back to CWM to sideload the kernel. I haven't rooted yet.
Click to expand...
Click to collapse
Did you have the "unmount of /system failed: no such volume" while flashing the rom zip?

mattgrantlackey said:
Did you have the "unmount of /system failed: no such volume" while flashing the rom zip?
Click to expand...
Click to collapse
Yes, and a similar error about /data

JaMeVu said:
Recommended Recovery is TWRP 2.8.1.0
Click to expand...
Click to collapse
Same error after using ADB to flash v2.8.1.0 TWRP, full wipe, and reinstall of everything in the correct procedure. My storage is still not working.

mattgrantlackey said:
Same error after using ADB to flash v2.8.1.0 TWRP, full wipe, and reinstall of everything in the correct procedure. My storage is still not working.
Click to expand...
Click to collapse
try this
enable usb debuging via dev opt.
connect phone to pc
put files to your sd card then reboot to recovery then flash

JaMeVu said:
try this
enable usb debuging via dev opt.
connect phone to pc
put files to your sd card then reboot to recovery then flash
Click to expand...
Click to collapse
I always enable usb debugging, didn't help. And as far as the file transfer, it won't let me. I can only access it while in TWRP. All my files are there, its just android can't see them, and wont show under windows either. Not sure what the issue is there, I've tried everything I know of. I'll just flash CM12 that I was using before. Let me know if you figure out this problem, as I'm curious as to what is causing it (and I'm not the only one having it).

mattgrantlackey said:
Wont let me. I can only access it while in TWRP. All my files are there, its just android can't see them, and wont show under windows either. Not sure what the issue is there, I've tried everything I know of. I'll just flash CM12 that I was using before. Let me know if you figure out this problem, as I'm curious as to what is causing it (and I'm not the only one having it).
Click to expand...
Click to collapse
re plug usb cable take it of then plug
no we do not have this kind of problem here many phones we tested and flashed

JaMeVu said:
re plug usb cable take it of then plug
no we do not have this kind of problem here many phones we tested and flashed
Click to expand...
Click to collapse
Same problems as me:
spupuz said:
does the internal storage work for you? it works only on twrp for me :/
i can't see anything in file explorer and canìt restore from twrp :/ that's a big problem guys.
Click to expand...
Click to collapse
spupuz said:
big big problem can't see the internal storage partition at all.
Click to expand...
Click to collapse

mattgrantlackey said:
Same problems as me:
spupuz said:
big big problem can't see the internal storage partition at all.
Click to expand...
Click to collapse
try re flash everything but not autoroot using..
Click to expand...
Click to collapse

try re flash everything but not autoroot using..[/QUOTE]
All of this was without autoroot. Don't worry about it man, I just installed my old rom. For some reason this ROM doesn't like me and spupuz's phone. Thanks for trying to help me, I appreciate your time. Let me know if someone else has the issue and you figure it out, I'm very curious as to what it might be.

mattgrantlackey said:
try re flash everything but not autoroot using..
Click to expand...
Click to collapse
All of this was without autoroot. Don't worry about it man, I just installed my old rom. For some reason this ROM doesn't like me and spupuz's phone. Thanks for trying to help me, I appreciate your time. Let me know if someone else has the issue and you figure it out, I'm very curious as to what it might be.[/QUOTE]
ok but we test it many phones and 1500+ downloads
may be u are using multirom ? or multirom twrp ?

JaMeVu said:
ok but we test it many phones and 1500+ downloads
may be u are using multirom ? or multirom twrp ?
Click to expand...
Click to collapse
Nope, no multirom or multirom twrp. I have no idea.

After rooting If you can not see your old nandroid backups
Via file explorers try to enable usb debuging from
dev. opt. if not worked (Recovires or SuperSU issue)
But you can see and restore your old or new backups via recovery (TWRP tested)
New recoveries and superSU may fix this issues.
Want to ask? SuperSU XDA Thread here
Note: SE Linux Mod Changer may help to fix this issue
Recommended Recovery is TWRP 2.8.1.0
​

I flashed this ROM this morning, and I initially had the weird can't unmount /system error. I rewiped, using twrp to ensure that /system was wiped too. Install went fine. I have a weird glitch or something on my recent apps list, though. I attached a picture. Anyone know what this is? It doesn't seem to be causing any functional problem, but it looks bad.
Edit: I cleared the cache for google now launcher, and restarted recovery and wiped my cache partition and the error went away.

Probably soft bricked my OP5, is this fixable?

Dear XDA,
I screwed up... I think my device is now soft bricked.... :crying:
It all started good on a sunny saturday. I thought this was a good day to try another custom rom. Namely Codename Phoenix.
My device was already rooted so i started with upgrading my TWRP to the latest Blu_Spark TWRP 3.2.1. After flashing the recovery i continued with the ROM. It all went downhill from there....
The install finished and i booted my device. Knowing this could take a while i got into the shower thinking it would finish when i got back. But when i got back it was still booting. Knowing the first boot can take a while so I let it be. After an hour or so it was still stuck on the google logo and the weather and my mood changed for the worse.
I figured something in the process went wrong and tried to boot into recovery. That worked so I thought 'Cool, let's fix it there'. But the recovery was encrypted so i couldn't get to my data. Normally you put in your pincode and it decrypts your phone. This was not the case.... I couldn't put in my pincode so decrypting was out of the question.
Luckily ADB was still working so I downloaded the original Oxygen OS rom and tried to side-load it... This got stuck on 47% for no reason at all. Phone had 100% battery and didn't time-out..
I was really confused, but I let the device do it's thing and maybe things would work out... I was wrong. Everything was worse. Because i tried installing the original firmware it removed the custom recovery....
So now i have a device with no OS and I can't get into recovery. Luckily there is a unbrick tool for OnePlus 5. Following those steps i got stuck on the part that it does not show in my device-manager.
Currently i'm really grumpy and have no idea how to fix this.
I humbly ask for advice. Is this solvable or do i have a wasted OnePlus 5?
Thanks in advance,
Lennard

can you reboot to bootloader?
if yes, you can flash original or custom recovery...

---------- Post added at 09:39 AM ---------- Previous post was at 09:38 AM ----------
[/COLOR]
len.asdf said:
Dear XDA,
I screwed up... I think my device is now soft bricked.... :crying:
It all started good on a sunny saturday. I thought this was a good day to try another custom rom. Namely Codename Phoenix.
My device was already rooted so i started with upgrading my TWRP to the latest Blu_Spark TWRP 3.2.1. After flashing the recovery i continued with the ROM. It all went downhill from there....
The install finished and i booted my device. Knowing this could take a while i got into the shower thinking it would finish when i got back. But when i got back it was still booting. Knowing the first boot can take a while so I let it be. After an hour or so it was still stuck on the google logo and the weather and my mood changed for the worse.
I figured something in the process went wrong and tried to boot into recovery. That worked so I thought 'Cool, let's fix it there'. But the recovery was encrypted so i couldn't get to my data. Normally you put in your pincode and it decrypts your phone. This was not the case.... I couldn't put in my pincode so decrypting was out of the question.
Luckily ADB was still working so I downloaded the original Oxygen OS rom and tried to side-load it... This got stuck on 47% for no reason at all. Phone had 100% battery and didn't time-out..
I was really confused, but I let the device do it's thing and maybe things would work out... I was wrong. Everything was worse. Because i tried installing the original firmware it removed the custom recovery....
So now i have a device with no OS and I can't get into recovery. Luckily there is a unbrick tool for OnePlus 5. Following those steps i got stuck on the part that it does not show in my device-manager.
Currently i'm really grumpy and have no idea how to fix this.
I humbly ask for advice. Is this solvable or do i have a wasted OnePlus 5?
Thanks in advance,
Lennard
Click to expand...
Click to collapse
Don't worry! Your device is safe. At most, you'll be required to wipe your data.
Try using the official twrp recovery here:
https://twrp.me/oneplus/oneplus5.html
If this doesn't work, let me know.

canteo said:
can you reboot to bootloader?
if yes, you can flash original or custom recovery...
Click to expand...
Click to collapse
I can go into fastboot and managed to install TWRP with the comment below!
Zohair.ul.hasan said:
---------- Post added at 09:39 AM ---------- Previous post was at 09:38 AM ----------
[/COLOR]
Don't worry! Your device is safe. At most, you'll be required to wipe your data.
Try using the official twrp recovery here:
https://twrp.me/oneplus/oneplus5.html
If this doesn't work, let me know.
Click to expand...
Click to collapse
Thanks for these words! That's a big relieve
With your link I managed to install TWRP through fastboot. So now i have a custom recovery. The current problem is that my data is encrypted and I cannot decrypt it. There is no option to fill in a password since there is no OS that requires a password. So it's sort of a neverending cycle . Although fastboot, recovery and sideload should work now.
The thing is, previously I tried installing the original firmware and that failed at 47%. So i'm not sure what to do now.
I tried installing 'codeworkx universal twrp 3.2.1-0 recovery' since he seems to have fixed the encrypt issue. But when I tried sideloading the file it says "Zip file is corrupt!". So no succes there yet.
To be precise, this is the threat for Codeworkx Universal TWRP : https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
And i downloaded and tried installing: twrp-3.2.1-0-universal-codeworkx-cheeseburger.img
I was thinking about downloading the latest Codename Phoenix ROM, but when I try to download the latest release the file is name "Codename-Phoenix-NOS-8.1-oneplus5t-20180303.zip". That implies it's only for the 5t and not for the 5. So that could be my original problem? That i downloaded the wrong ROM?
That aside.
Should I try to get the download link for CNP and download the latest release for the OP5 and install that.
Or
Should i try to install the original firmware. Reset everything and start over from the beginning (unlocking, rooting, etc..)
Thanks again for all the help

len.asdf said:
I can go into fastboot and managed to install TWRP with the comment below!
Thanks for these words! That's a big relieve
With your link I managed to install TWRP through fastboot. So now i have a custom recovery. The current problem is that my data is encrypted and I cannot decrypt it. There is no option to fill in a password since there is no OS that requires a password. So it's sort of a neverending cycle . Although fastboot, recovery and sideload should work now.
The thing is, previously I tried installing the original firmware and that failed at 47%. So i'm not sure what to do now.
I tried installing 'codeworkx universal twrp 3.2.1-0 recovery' since he seems to have fixed the encrypt issue. But when I tried sideloading the file it says "Zip file is corrupt!". So no succes there yet.
To be precise, this is the threat for Codeworkx Universal TWRP : https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
And i downloaded and tried installing: twrp-3.2.1-0-universal-codeworkx-cheeseburger.img
I was thinking about downloading the latest Codename Phoenix ROM, but when I try to download the latest release the file is name "Codename-Phoenix-NOS-8.1-oneplus5t-20180303.zip". That implies it's only for the 5t and not for the 5. So that could be my original problem? That i downloaded the wrong ROM?
That aside.
Should I try to get the download link for CNP and download the latest release for the OP5 and install that.
Or
Should i try to install the original firmware. Reset everything and start over from the beginning (unlocking, rooting, etc..)
Thanks again for all the help
Click to expand...
Click to collapse
Nice to hear that!
To be clear, does the TWRP decrypt you data? When you click install in TWRP, is it a bunch of randomly named files?
I think you should go ahead with installing CNP, you shouldn't have any problems with it now that you've got the correct version.
Good luck!

Zohair.ul.hasan said:
Nice to hear that!
To be clear, does the TWRP decrypt you data? When you click install in TWRP, is it a bunch of randomly named files?
I think you should go ahead with installing CNP, you shouldn't have any problems with it now that you've got the correct version.
Good luck!
Click to expand...
Click to collapse
Yeah it's a bunch of random file names. Like "2TAjnCI8CpHDL38Oh684DuTSgaO".
Alright, i'll let you know if I succeed. Thanks for the help

len.asdf said:
Yeah it's a bunch of random file names. Like "2TAjnCI8CpHDL38Oh684DuTSgaO".
Alright, i'll let you know if I succeed. Thanks for the help
Click to expand...
Click to collapse
Wait! Staying encrypted is a bunch of trouble. I recommend u to follow these steps:
Go to recovery
Select wipe
Select advanced wipe
Clear dalvik and cache
Go back
Select wipe
Click "Format Data"
Type in yes
Go back
Select wipe
Swipe to factory reset
Reboot recovery
Transfer the ROM from PC to phone
Install it

Zohair.ul.hasan said:
Wait! Staying encrypted is a bunch of trouble. I recommend u to follow these steps:
Go to recovery
Select wipe
Select advanced wipe
Clear dalvik and cache
Go back
Select wipe
Click "Format Data"
Type in yes
Go back
Select wipe
Swipe to factory reset
Reboot recovery
Transfer the ROM from PC to phone
Install it
Click to expand...
Click to collapse
Haha thanks! Just in time. Was still downloading the latest CNP .

Whew! Update me after flashing.

Zohair.ul.hasan said:
Whew! Update me after flashing.
Click to expand...
Click to collapse
Hmm, the installation should be a succes. But when i tried to reboot and start up the OS / System it just reboots into TWRP.... ? It's sort of boot looping into recovery.
I tried installing a couple of times with and without wiping dalvik/cache/system.
Could the install file not be complete?
On a side note, my data is not encrypted

len.asdf said:
Hmm, the installation should be a succes. But when i tried to reboot and start up the OS / System it just reboots into TWRP.... ? It's sort of boot looping into recovery.
I tried installing a couple of times with and without wiping dalvik/cache/system.
Could the install file not be complete?
On a side note, my data is not encrypted
Click to expand...
Click to collapse
Did you factory reset by going into wipe>swipe to factory reset?
If not then do that and flash it

Zohair.ul.hasan said:
Did you factory reset by going into wipe>swipe to factory reset?
If not then do that and flash it
Click to expand...
Click to collapse
YES! It work. Many thanks

len.asdf said:
YES! It work. Many thanks
Click to expand...
Click to collapse
Congrats! Please like my replies if you don't mind

Zohair.ul.hasan said:
Congrats! Please like my replies if you don't mind
Click to expand...
Click to collapse
But of course! Already did that. But i'm not sure if it shows or not. Tried clicking multiple times on the thanks button but it doesn't highlight. It should do that right?

len.asdf said:
But of course! Already did that. But i'm not sure if it shows or not. Tried clicking multiple times on the thanks button but it doesn't highlight. It should do that right?
Click to expand...
Click to collapse
Yes it should but that's okay

Zohair.ul.hasan said:
Yes it should but that's okay
Click to expand...
Click to collapse
installed the xda app and there I could give you a 'thanks'

Us996 TWRP not sticking

I'm using the tutorial on the LineageOS wiki for the Us996. I've unlocked the bootloader via official means from LG, but when it comes time to send the recovery via fastboot, it successfully sends and writes it, it even let's me boot into it, after pulling the battery, and using the correct button commands. But if I restart and try to enter again I'm greeted by the official erase everything recovery.
Does anyone know what I'm doing wrong? Do I need to flash root to get the recovery to stick?

Take a look at this video. If you have TWRP installed right, and are going to it through a battery pull and the power button volume down combination, then the screen that comes up looks scary and looks like you'll "format" your phone, but as you see in this video, you don't.

baldybill said:
Take a look at this video. If you have TWRP installed right, and are going to it through a battery pull and the power button volume down combination, then the screen that comes up looks scary and looks like you'll "format" your phone, but as you see in this video, you don't.
https://www.youtube.com/watch?v=https://www.youtube.com/watch?v=tDq0qMbgjL4
Click to expand...
Click to collapse
See I've gotten into TWRP, then I reboot system(actual Android not just restarting recovery).the problem is When I power off my phone and tried to get back into TWRP, I clicked yes and yes and it proceeded to wipe my phone. TWRP wasn't there just factory reset lol

lowsnamebrand said:
See I've gotten into TWRP, then I reboot system(actual Android not just restarting recovery).the problem is When I power off my phone and tried to get back into TWRP, I clicked yes and yes and it proceeded to wipe my phone. TWRP wasn't there just factory reset lol
Click to expand...
Click to collapse
Not sure why it isnt happening automatically (it usually does when flashing things like magisk to root) but when you get into twrp or with root rename /system/recovery-from-boot.p to /system/recovery-from-boot.bak. If in twrp first go into the mount page and uncheck the box at the bottom that says something about system read only first, then you can use the file manager.
Or since it sounds like you want to flash lineage, just flash the lineageos zip (and then optionally opengapps and root). Be sure to format data too (wipe->format data->yes). Then if you dont have lineage on an sdcard ready to go you could reboot recovery so that the formatted data is ready then connect to pc and send the zips over by using adb push C:\path\to\lineage.zip /sdcard/

Phoenix591 said:
Not sure why it isnt happening automatically (it usually does when flashing things like magisk to root) but when you get into twrp or with root rename /system/recovery-from-boot.p to /system/recovery-from-boot.bak. If in twrp first go into the mount page and uncheck the box at the bottom that says something about system read only first, then you can use the file manager.
Or since it sounds like you want to flash lineage, just flash the lineageos zip (and then optionally opengapps and root). Be sure to format data too (wipe->format data->yes). Then if you dont have lineage on an sdcard ready to go you could reboot recovery so that the formatted data is ready then connect to pc and send the zips over by using adb push C:\path\to\lineage.zip /sdcard/
Click to expand...
Click to collapse
What I'm thinking about doing is flashing TWRP again, on first boot(of TWRP) backing up my current rom(stock) and trying to boot into recovery again, because if it doesn't stick again, it'll wipe but at least I'll have a backup.
I've noticed a lot of different root files which would you recommend?

lowsnamebrand said:
What I'm thinking about doing is flashing TWRP again, on first boot(of TWRP) backing up my current rom(stock) and trying to boot into recovery again, because if it doesn't stick again, it'll wipe but at least I'll have a backup.
I've noticed a lot of different root files which would you recommend?
Click to expand...
Click to collapse
Sorry for the double post but does the "LG factory reset" stay even after having TWRP installed? Like will I always have to answer yes twice to enter TWRP?

lowsnamebrand said:
Sorry for the double post but does the "LG factory reset" stay even after having TWRP installed? Like will I always have to answer yes twice to enter TWRP?
Click to expand...
Click to collapse
Yes thats always the same.
If you don't flash lineage or something to root stock (I reccommend magisk since the alternative, Supersu, is owned by some Chinese company, and magisk has various modules that do many things) and don't rename /system/recovery-from-boot.p manually (theres a file manager under advanced in twrp) the stock rom will use that file to reflash stock recovery any time it boots.

Phoenix591 said:
Yes thats always the same.
If you don't flash lineage or something to root stock (I reccommend magisk since the alternative, Supersu, is owned by some Chinese company, and magisk has various modules that do many things) and don't rename /system/recovery-from-boot.p manually (theres a file manager under advanced in twrp) the stock rom will use that file to reflash stock recovery any time it boots.
Click to expand...
Click to collapse
Awesome I think my issue is not renaming that file and the stock rom reinstalling stock recovery. I've used SuperSU, never used magisk, is there a stickied release thread for it?

lowsnamebrand said:
Awesome I think my issue is not renaming that file and the stock rom reinstalling stock recovery. I've used SuperSU, never used magisk, is there a stickied release thread for it?
Click to expand...
Click to collapse
Its got more than a thread, has a whole section. Anyway heres the main release thread

Phoenix591 said:
Its got more than a thread, has a whole section. Anyway heres the main release thread
Click to expand...
Click to collapse
You've been a huge help, thank you! I'll report back later tonight, when I can actually work on my phone

So i was able to obtain root aswell as installed twrp, the only issue I had was every rom I tried refused to boot. They just hung at the loading screen, that includes the back up I'd made of stock, is there something I missed?

lowsnamebrand said:
So i was able to obtain root aswell as installed twrp, the only issue I had was every rom I tried refused to boot. They just hung at the loading screen, that includes the back up I'd made of stock, is there something I missed?
Click to expand...
Click to collapse
If you mean the boot animation, the very first time can take a good while, like 20 minutes. Also make sure you've formatted /data if you havnt yet especially going to lineage.

Phoenix591 said:
If you mean the boot animation, the very first time can take a good while, like 20 minutes. Also make sure you've formatted /data if you havnt yet especially going to lineage.
Click to expand...
Click to collapse
Sorry for the late reply, yeah I think I just let the boot animation go for around 5, I'm gonna have to try reflashing it and hoping for the best, I'll be sure to answer back when I get a chance

OK, I know this is an old thread - but I just got a replacement US996 phone; my old standby has a charger plug problem so I decided to get another one and put a rooted stock Oreo ROM on it. However, I'm having the same issue as the OP. Get into fastboot, flash TWRP (I have the 3.3.1-0 version, as the newer 3.3.1-1 version does not have any download mirrors). The flash appears to go just fine, it says the write was completed. However, when I reboot into adb mode and do "adb reboot recovery" I get "no command" and the little droid with his belly hatch open. So obviously TWRP wasn't flashed. The OP says he eventually was able to get it to work and install root. How did you fix the issue?
Do I still need to do the old recowvery shenanigans that we had to do back when the phone first came out?
Thanks!

I believe you MUST use the button combo to reboot into twrp.
See here:
https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239/post78513963

pistacios said:
I believe you MUST use the button combo to reboot into twrp.
See here:
https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239/post78513963
Click to expand...
Click to collapse
I've done that. The problem is that TWRP hasn't actually been installed via fastboot flash recovery - it goes through the motions, SAYS it's been installed, but when I do the button combo, it actually does reset my phone rather than booting into TWRP.
---------- Post added at 09:36 AM ---------- Previous post was at 08:55 AM ----------
Disregard the above. Flashed it again (4th time), and it finally took.

The same happened with my wife's US996 now that you mention it. Took a few tries and was a bit frustrating.
When I flashed TWRP on mine it was a "one and done".
Glad you got it sorted.

Thanks - all good. Rooted stock Oreo ROM installed, working great.