Database Info

[Q] I can't get any 4.3 roms to work.

Every 4.3 rom I install after the first reboot it hangs at unlocked bootlaoder screen. I have tried every recovery out there but everytime I have to fastboot to be able to restore a 4.2.2 rom and get it to boot. Does anyone know how to fix this because it is very frustrating. I wipe everything when I install to. I follow the standard procedure and I am not new to rooting or flashing.

ajh305 said:
Every 4.3 rom I install after the first reboot it hangs at unlocked bootlaoder screen. I have tried every recovery out there but everytime I have to fastboot to be able to restore a 4.2.2 rom and get it to boot. Does anyone know how to fix this because it is very frustrating. I wipe everything when I install to. I follow the standard procedure and I am not new to rooting or flashing.
Click to expand...
Click to collapse
you tried 6.0.3.5 cwm also?
i had the same problem and this was the only one i could get to work.

bweN diorD said:
you tried 6.0.3.5 cwm also?
i had the same problem and this was the only one i could get to work.
Click to expand...
Click to collapse
Ya i tried every cwm including 6.0.3.6 and twrp 2.0.6.1

ajh305 said:
Ya i tried every cwm including 6.0.3.6 and twrp 2.0.6.1
Click to expand...
Click to collapse
not sure if it will help but this is the exact process i used:
-rts using matts utility found here http://batakang.com/dr_utility.php
-put stock recovery back on using the above utility
-root with the above utility and protect with voodoo
-take the ota to get the latest baseband back (will likely fail but still update the bb)
-restore root
-install cwm 6.0.3.5 from this utility http://www.mediafire.com/download/tt7cwwua49n24uv/Razr_HD_Recovery_Flasher_V7.rar
-flash your 4.3 rom of choice
-profit (hopefully lol)

ajh305 said:
Every 4.3 rom I install after the first reboot it hangs at unlocked bootlaoder screen. I have tried every recovery out there but everytime I have to fastboot to be able to restore a 4.2.2 rom and get it to boot. Does anyone know how to fix this because it is very frustrating. I wipe everything when I install to. I follow the standard procedure and I am not new to rooting or flashing.
Click to expand...
Click to collapse
keep in mind the second boot on 4.3 roms seems to take a while, how long is it hanging on the boot screen? I remember the first 4.3 I flashed hung for about 5-8 minutes before it booted up. it seems to be the second one that hangs consistently for me, but it does always boot. All following reboots after the 2nd are normal with no hangs.

bjoostema said:
keep in mind the second boot on 4.3 roms seems to take a while, how long is it hanging on the boot screen? I remember the first 4.3 I flashed hung for about 5-8 minutes before it booted up. it seems to be the second one that hangs consistently for me, but it does always boot. All following reboots after the 2nd are normal with no hangs.
Click to expand...
Click to collapse
I think I have waited for about 10 minutes before. I'll try again and see if it does actually boot. Does your hang on the bootloader unlocked screen or the boot animation screen?
EDIT: I tried another 4.3 rom and booted it up. Set some things up then updated su binaries and restarted and let it sit there at the unlocked bootloader warning for 15 minutes with no changes.

bweN diorD said:
not sure if it will help but this is the exact process i used:
-rts using matts utility found here http://batakang.com/dr_utility.php
-put stock recovery back on using the above utility
-root with the above utility and protect with voodoo
-take the ota to get the latest baseband back (will likely fail but still update the bb)
-restore root
-install cwm 6.0.3.5 from this utility http://www.mediafire.com/download/tt7cwwua49n24uv/Razr_HD_Recovery_Flasher_V7.rar
-flash your 4.3 rom of choice
-profit (hopefully lol)
Click to expand...
Click to collapse
I did actually restore it back to completely stock, recovery and everything. I downloaded the OTA after rooting and using voodoo. The update failed but I installed cwm 6.0.3.6 and then restored my backup. Then I flashed twrp 2.0.6.1 to try that and flashed a 4.3 rom and same issue came up.

ajh305 said:
I think I have waited for about 10 minutes before. I'll try again and see if it does actually boot. Does your hang on the bootloader unlocked screen or the boot animation screen?
Click to expand...
Click to collapse
Yeah, mine hangs at the bl unlocked screen on that second boot, though I flashed a different logo to get rid of that annoying message 10 minutes seems a bit excessive but not unheard of-longest I clocked was around 8. Does yours ever make it to the boot animation? If so, it should go into a full boot eventually. I think the hang has something to do with the rom building cache on that second boot Also, whichever 4.3 your using, I would make sure it's a more recent release as they have come a very far since the early releases which hung for longer periods of time. I'm currently running pa rc2 by cj and it went smoothly using cwm 6.0.3.2.

bjoostema said:
Yeah, mine hangs at the bl unlocked screen on that second boot, though I flashed a different logo to get rid of that annoying message 10 minutes seems a bit excessive but not unheard of-longest I clocked was around 8. Does yours ever make it to the boot animation? If so, it should go into a full boot eventually. I think the hang has something to do with the rom building cache on that second boot Also, whichever 4.3 your using, I would make sure it's a more recent release as they have come a very far since the early releases which hung for longer periods of time. I'm currently running pa rc2 by cj and it went smoothly using cwm 6.0.3.2.
Click to expand...
Click to collapse
It never reaches the boot animation just sits at that screen. I have tried several 4.3 roms within the last few days so they are the newest versions I can find. Could I clear the cache to get it to boot?

ajh305 said:
It never reaches the boot animation just sits at that screen. I have tried several 4.3 roms within the last few days so they are the newest versions I can find. Could I clear the cache to get it to boot?
Click to expand...
Click to collapse
http://www.droidrzr.com/index.php/topic/27682-having-issues-with-43-roms-is-it-me/ check out the last post on the page in that link. It seems to have worked for that guy. If you don't mind, try that and let me know if it works. In the meantime, I'm going to try and find some more solutions. I'm assuming his method worked, as he hasn't posted back.

bjoostema said:
http://www.droidrzr.com/index.php/topic/27682-having-issues-with-43-roms-is-it-me/ check out the last post on the page in that link. It seems to have worked for that guy. If you don't mind, try that and let me know if it works. In the meantime, I'm going to try and find some more solutions. I'm assuming his method worked, as he hasn't posted back.
Click to expand...
Click to collapse
By golly that worked! It booted up fast as well. It must lie with the formatting your internal storage before flashing the 4.3 rom. I tried something similiar to this but I was already on a 4.3 rom that wouldn't boot and I formatted the sd card then tried flashing it again and it booted again for the first time but wouldn't the second. So if your having trouble do this:
Restored stock 4.1.2 using Matt's utility
Rooted with Matt's utility
Put 4.3 rom and GAPPS on external SD
Fastboot flash CWM 6.0.3.5 (or install via Matt's utility if you like)
Wipe data/factory reset
Wipe Cache/Dalvik
Go to mounts/storage and format /data and /data/media (/sdcard) **Back up anything in your internal SD you want to keep before doing this!**
Flash 4.3 rom
Wipe Cache/dalvik
Flash GAPPS
Wipe Cache/dalvik
Boot up and setup rom
Reboot

ajh305 said:
By golly that worked! It booted up fast as well. It must lie with the formatting your internal storage before flashing the 4.3 rom. I tried something similiar to this but I was already on a 4.3 rom that wouldn't boot and I formatted the sd card then tried flashing it again and it booted again for the first time but wouldn't the second. So if your having trouble do this:
Restored stock 4.1.2 using Matt's utility
Rooted with Matt's utility
Put 4.3 rom and GAPPS on external SD
Fastboot flash CWM 6.0.3.5 (or install via Matt's utility if you like)
Wipe data/factory reset
Wipe Cache/Dalvik
Go to mounts/storage and format /data and /data/media (/sdcard) **Back up anything in your internal SD you want to keep before doing this!**
Flash 4.3 rom
Wipe Cache/dalvik
Flash GAPPS
Wipe Cache/dalvik
Boot up and setup rom
Reboot
Click to expand...
Click to collapse
Awesome man! I'm glad it booted up for you welcome to the 4.3 side!

ajh305 said:
I did actually restore it back to completely stock, recovery and everything. I downloaded the OTA after rooting and using voodoo. The update failed but I installed cwm 6.0.3.6 and then restored my backup. Then I flashed twrp 2.0.6.1 to try that and flashed a 4.3 rom and same issue came up.
Click to expand...
Click to collapse
glad you got it fixed but i have to ask, in the sequence above why are you restoring a backup? you should be going right from stock to 4.3. also, some people have issues with twrp and 4.3, thats why i suggested cwm.

I'm not sure why I restored the backup. I didn't think coming from stock would work for some reason.
Sent from my XT926 using xda app-developers app

I am having the same problem. I have followed the steps but still no joy . Any thoughts?

sgtslaughter64 said:
I am having the same problem. I have followed the steps but still no joy . Any thoughts?
Click to expand...
Click to collapse
This was the only thing that worked for me. You could maybe try updating to the most current recovery instead of the one listed.

the only 2 issues i have seen to cause this problem are covered in the post a few below, and fixed it every time. my only suggestion would be to install cwm after rooting, then reboot, then continue with the steps. just my preference, it may not matter.

[Q] TWRP not restoring backups

I have encountered a strange problem. Please help.
1. I was running CM12 nightly (April 10 build). I also have TWRP backups of Apr 8 image and my old CM11S (44R) image.
2. I downloaded OxygenOS to try it out. Booted the phone into TWRP and tried flashing the ZIP.
3. Got an error while flashing the ZIP.
4. Rebooted the phone into recovery and tried restoring the Apr 10 image.
5. Restore says it is successful.
6. On reboot, the phone stays on the "Powered by Android" screen. It does not boot up into the ROM image. It boots up into recovery instead.
7. I tried the same process with Apr 8 image and the same issue.
8. Finally, I restored the backup image of CM11S and that works well.
Can someone please advise how can I get my backup ROMs to work?
I have now tried backing up ROMs for Cyanogen CMOS12 as well as Oxygen. None of the restores are working. I am backing up all partitions. Where am I going wrong? The restore does not give any error, but the boot is stuck at the logo. When I restore CMOS12, it gets stuck on the screen that says "Cyanogen". When I restore Oxygen, it gets stuck at the boot animation of Oxygen.
I am using TWRP 2.8.6 for restore and Online nandroid manager for backing up.
Is it possible that OnlineNandroid manager uses a different version of recovery for backup?
Please help.
.

I'm new to the CM 12 stuff but I thought I read that TWRP had an issue with compression during a certain range of weeklies, and due to that, would/could not restore from that range.
I think I also read to make sure you have the most up to date TWRP, and a weekly after 4/22, or so. I don't recall the exact date of the compressed weeklies causing the issue,but I think the compression problem began in April, sometime. Hopefully someone will come by and further clarify or identify your issue.
What version of TWRP do you have and what's the date of your weekly?

JeffDC said:
I'm new to the CM 12 stuff but I thought I read that TWRP had an issue with compression during a certain range of weeklies, and due to that, would/could not restore from that range.
I think I also read to make sure you have the most up to date TWRP, and a weekly after 4/22, or so. I don't recall the exact date of the compressed weeklies causing the issue,but I think the compression problem began in April, sometime. Hopefully someone will come by and further clarify or identify your issue.
What version of TWRP do you have and what's the date of your weekly?
Click to expand...
Click to collapse
I am using TWRP 2.8.6. I have tried restoring Oxygen, CM12, CM12S backups and none of them are working. Restore takes reasonable time and says it was successful.

indoliya said:
I am using TWRP 2.8.6. I have tried restoring Oxygen, CM12, CM12S backups and none of them are working. Restore takes reasonable time and says it was successful.
Click to expand...
Click to collapse
see if this link has any relationship to your general issue
https://forums.oneplus.net/threads/...cm12-1-nightlies.300277/page-78#post-11010591
read around a bit as some folks seem to have had the same issue as you, there is also an xda topic for the nightlies, as well which may be a good place to search

indoliya said:
I am using TWRP 2.8.6. I have tried restoring Oxygen, CM12, CM12S backups and none of them are working. Restore takes reasonable time and says it was successful.
Click to expand...
Click to collapse
Did you wiped cacha/Dalvik? I personnaly do these wipes before and after flashing/restoring.
If I were you, I'd try to flash the latest cm12 nightly "on" you restore, maybe it could help..

You might have to flash the right firmware for the CM 12/11 you want to restore. TWRP doesn't backup firmware by default, only ROM/Data. So flash the right formware for the ROM you want to restore and then restore your nandroid.

real_sl4cker said:
You might have to flash the right firmware for the CM 12/11 you want to restore. TWRP doesn't backup firmware by default, only ROM/Data. So flash the right formware for the ROM you want to restore and then restore your nandroid.
Click to expand...
Click to collapse
Thank you! Previously, I was switching between CM11 and CM12 without any problem. Are you sure about this?

indoliya said:
Thank you! Previously, I was switching between CM11 and CM12 without any problem. Are you sure about this?
Click to expand...
Click to collapse
Not sure as in "Yes, that's the way to go, do it!" but it's worth a try. I haven't switched back to CM11 from CM12 (updated to CM12 just yesterday) up to now.
What I'm pretty sure about is that TWRP (by default) only backs up system and data, no modem and stuff. And CM11 and CM12 come with different firmware. Flashing the right firmware for your build won't do any harm anyway

real_sl4cker said:
Not sure as in "Yes, that's the way to go, do it!" but it's worth a try. I haven't switched back to CM11 from CM12 (updated to CM12 just yesterday) up to now.
What I'm pretty sure about is that TWRP (by default) only backs up system and data, no modem and stuff. And CM11 and CM12 come with different firmware. Flashing the right firmware for your build won't do any harm anyway
Click to expand...
Click to collapse
Finally resolved this by going to Online Nandroid app and changed the shell to default and busybox to default. Now the backups taken with these settings are getting restored successfully.

Recovery unable to mount /sdcard

Hello!
I am sorry if this is the incorrect place to post, but I have a very annoying issue with my OnePlus One!
A few days ago I took the OTA update from Android 4.4.4 all the way to 5.1.1. However, there are quite a few bugs with this version, and the "Material UI" is seriously getting on my nerves so I would like to revert back to my previous version. This should be doable because I performed a Nandroid backup with TWRP before updating the phone. My backup is saved on a USB stick which I connect to the phone via a USB OTG cable, which is perfectly mountable in the Recovery.
My phone is rooted and WAS running TWRP Recovery before I upgraded to Lollipop, this replaced TWRP with Cyanogens stock. When I re-rooted my phone I had to reinstall a custom recovery. For some reason, ADB installing TWRP was just not working (No errors, it just didnt install no matter what) so I opted to try a CWM recovery which did the trick.
Now my issue is that my recovery is unable to mount /sdcard which prevents it from performing backups or restores.
I could really use some help here.

Did you update your backup (TWRP?) as well? What version of it are you on?

JeffDC said:
Did you update your backup (TWRP?) as well? What version of it are you on?
Click to expand...
Click to collapse
I am not sure what you mean by updating the backup. The backup is backed up and left in the state it was when I took it, that is to say Android 4.4.4 and the version of TWRP (The date I installed TWRP the first time) is mid February 2015.
The phones recovery right now is PhilzRecovery which as far as I understand is CWM. Latest version.

Try installing twrp from the CWM recovery.. And before restoring the phone from nandroid try installing the clean stock rom at 4.4.4 and then do the nandroid restore.
Sent from OPO using Tapatalk
Press on thanks if I helped you

ashuthosh.heda said:
Try installing twrp from the CWM recovery.. And before restoring the phone from nandroid try installing the clean stock rom at 4.4.4 and then do the nandroid restore.
Sent from OPO using Tapatalk
Press on thanks if I helped you
Click to expand...
Click to collapse
And to do this, I would just drop the .img for TWRP into my phones storage and chose it from inside the recovery? Would this really work? It might be my inexperience, but it sounds somewhat risky.

NodCom said:
And to do this, I would just drop the .img for TWRP into my phones storage and chose it from inside the recovery? Would this really work? It might be my inexperience, but it sounds somewhat risky.
Click to expand...
Click to collapse
Don't know if CWM recovery supports installing img. Twrp supports img flashing. Check the features of CWM recovery and proceed.
Sent from my A0001 using Tapatalk

ashuthosh.heda said:
Don't know if CWM recovery supports installing img. Twrp supports img flashing. Check the features of CWM recovery and proceed.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Well... I am not sure how I just managed this, but I was tinkering about inside my TWRP application and tried the "Install TWRP recovery" setting a second time (I tried it before making this thread, the first time it failed), it actually was successful because it booted into TWRP. From here I selected the TWRP-backup I kept and it installed it successfully (With one note, that it during the installation said something among the lines of "Restoring backup without deleting /data/media" or something like that. The phone rebooted itself after it finished updating, and the old Cyanogen/OPO bootanimation plays. But at login (My device is encrypted since long) it tells me my password is incorrect?!
How could this to happen? I've only ever used a single password (numbers only) for my phone encryption. This is very odd.

NodCom said:
Well... I am not sure how I just managed this, but I was tinkering about inside my TWRP application and tried the "Install TWRP recovery" setting a second time (I tried it before making this thread, the first time it failed), it actually was successful because it booted into TWRP. From here I selected the TWRP-backup I kept and it installed it successfully (With one note, that it during the installation said something among the lines of "Restoring backup without deleting /data/media" or something like that. The phone rebooted itself after it finished updating, and the old Cyanogen/OPO bootanimation plays. But at login (My device is encrypted since long) it tells me my password is incorrect?!
How could this to happen? I've only ever used a single password (numbers only) for my phone encryption. This is very odd.
Click to expand...
Click to collapse
I guess it's a side effect of restoring up a backup of 4.4.4 on lollipop. Try factory reset from twrp and then flash the backup. I would still suggest to first install the stock firmware of 4.4.4 and flash it and then do a restore of 4.4.4.
Sent from OPO using Tapatalk
Currently on Resurrection Remix
Thank me if I helped you.

Also make sure you are using the most recent version of TWRP, as it provides better 'outs' and reliability for newer OP OS versions.

Partitions

Hello everyone,
I don't know much about partitions but I know something is not right with mine
So, A few days ago my phone got bricked because I flashed crDroid rom. (I did something wrong)
So, after a lot of research, I found an solution to unbrick my phone. So it worked, I booted into software again and I was free to use.
So later, I decided to install an custom rom again (Havoc OS). I installed the rom but after I clean flashed the rom, I got stuck on booting logo.
So, I thought lets see what partition B does. So I booted into partition B and I got stuck on the logo of TWRP. Not sure why.
I really wanna know why this happend and how to fix my device.
(Btw, now my phone is working again and I am on stock os with rooted using Magisk 16,7.)
But just wanna know what I did wrong
I used the instruction in this thread: https://forum.xda-developers.com/oneplus-6/development/enchilada-romcrdroid-t3827070. And after I did that it got bricked.
I hope anyone knows what happend and how to fix my partition!
Friendly regards,
Crewz

Hi, why you get stuck and what not is because you simply do not follow the instructions 100%
After rom install and twrp install did you reboot? When you reboot at that point it will change partition.
If you get stuck on boot again, try reflash rom (without wipes), flash twrp, reboot to recovery, flash gapps and start the device. Apply root after setup this time just to be sure. Another thing could also be magisk, some roms require a later magisk version. But like I said, root after setup just to be sure where the issue is . Happy flashing mate!

whizeguy said:
Hi, why you get stuck and what not is because you simply do not follow the instructions 100%
After rom install and twrp install did you reboot? When you reboot at that point it will change partition.
If you get stuck on boot again, try reflash rom (without wipes), flash twrp, reboot to recovery, flash gapps and start the device. Apply root after setup this time just to be sure. Another thing could also be magisk, some roms require a later magisk version. But like I said, root after setup just to be sure where the issue is . Happy flashing mate!
Click to expand...
Click to collapse
I did the exact steps as in the thread.

ItsCrewz said:
I did the exact steps as in the thread.
Click to expand...
Click to collapse
If you're booted up and stable there's nothing wrong with your partitions.
What version of twrp are you using?

iElvis said:
If you're booted up and stable there's nothing wrong with your partitions.
What version of twrp are you using?
Click to expand...
Click to collapse
The newest one.
Look when I boot into TWRP and switch to partition B. I am stuck at logo of twrp

ItsCrewz said:
The newest one.
Look when I boot into TWRP and switch to partition B. I am stuck at logo of twrp
Click to expand...
Click to collapse
Which version? There are multiple "newest" ones.
Just because you have two slots doesn't mean both are bootable. The intent of the A/B arrangement is to allow seamless updates, not create a dual-boot phone. The inactive slot is often not bootable or will boot up with things broken. It's inactive because it's not suppose to be booted.
Switching slots manually is rarely necessary anyway. Why do you need to do it?

iElvis said:
Which version? There are multiple "newest" ones.
Just because you have two slots doesn't mean both are bootable. The intent of the A/B arrangement is to allow seamless updates, not create a dual-boot phone. The inactive slot is often not bootable or will boot up with things broken. It's inactive because it's not suppose to be booted.
Switching slots manually is rarely necessary anyway. Why do you need to do it?
Click to expand...
Click to collapse
Yes I know what it means. But it isn't normal that it boots into twrp and get stuck on the logo

Cannot boot phone after updating

The problem is kinda complicated. Previously, I flashed a custom ROM on my phone (a modified version of Oxygen OS). Just now, I updated my phone using the official ROM downloaded from Oneplus's official site (no idea what I was thinking), and I was only able to boot into the stock recovery. So, I tried reinstalling the TWRP recovery. I was able to boot the phone, but upon boot, it would say something like "Settings stopped working" and it would shut down immediately. I tried flashing a couple of different ROMs using the Install option in TWRP, but I still get the same error when booting my phone. Is there anyway to solve this problem? If not, would there be any way for me to recover my files at least?

Go back to factory stock using the MSM tool. If you can get to TWRP you can backup your stuff.

CosmicInsight said:
Go back to factory stock using the MSM tool. If you can get to TWRP you can backup your stuff.
Click to expand...
Click to collapse
I am able to get to TWRP right now. However, I did noticed that the Data partition in the TWRP Backup option is only 76MB. Does this mean that my data's gone already somehow?

leniumC said:
I am able to get to TWRP right now. However, I did noticed that the Data partition in the TWRP Backup option is only 76MB. Does this mean that my data's gone already somehow?
Click to expand...
Click to collapse
Yeah, probably.