I just updated my device with the Android Q Beta 4 update (via the OTA method) from Beta 3, and found my phone stuck booting up. After 30 minutes of it sitting around doing nothing, I decided to try wiping Cache, but that option isn't present on my recovery apparently.
Aside from running the Beta, everything is stock on the device. I tried sideloading the Beta 4 System Image, but that also failed to boot.
My post here is to ask if someone could link me to the Beta 3 System Image to try and jump back if possible. I want to try this before resorting to wiping the phone, as I stupidly didn't backup a few things before the update.
Or if someone has any advice/suggestion for a fix on this, aside from a full wipe.
BXWolf92 said:
I just updated my device with the Android Q Beta 4 update (via the OTA method) from Beta 3, and found my phone stuck booting up. After 30 minutes of it sitting around doing nothing, I decided to try wiping Cache, but that option isn't present on my recovery apparently.
Aside from running the Beta, everything is stock on the device. I tried sideloading the Beta 4 System Image, but that also failed to boot.
My post here is to ask if someone could link me to the Beta 3 System Image to try and jump back if possible. I want to try this before resorting to wiping the phone, as I stupidly didn't backup a few things before the update.
Or if someone has any advice/suggestion for a fix on this, aside from a full wipe.
Click to expand...
Click to collapse
Here's a image I downloaded a couple days ago to unlock the bootloader and try to upgrade to q.
I have a new account so here's the link: mega.nz/#!qNdxyaBA!Q9umFW_ybSTsEVQN9gWrAWoqCiNJncU6WhXIjKcV9gU
Related
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.
I'm having trouble mounting the system on my Nexus 5. I initially had some trouble mounting the system when I first got the phone back in December. It took a few times to finally root the phone.
Last night, I downloaded a few Xposed Modules (nothing major, just minor tweaks) and restarted the phone. It would boot up and go to the lockscreen, but it would never progress beyond that (keeps rebooting).
I tried formatting the cache and dalvik cache. I had to reboot into recovery several times because it failed to mount anything, including the system. No dice.
I thought about trying to reflash TWRP Recovery and the Purity ROM I am on, but I can't seem to do that either in bootloader mode.
Any ideas on how to fix this?
What version of twrp are you using?
After a few hours of trial and error, I ultimately just did a Stock Rom / Unroot and downloaded/installed a new copy of TWRP, latest Purity ROM, and re-installed the ElementalX Kernel.
Everything is running smoothly now. Just have to remember to backup everything to my mac to avoid starting from scratch.
Javeline4 said:
After a few hours of trial and error, I ultimately just did a Stock Rom / Unroot and downloaded/installed a new copy of TWRP, latest Purity ROM, and re-installed the ElementalX Kernel.
Everything is running smoothly now. Just have to remember to backup everything to my mac to avoid starting from scratch.
Click to expand...
Click to collapse
I think it you probably had an old version of TWRP.
I'm having a problem when I flash the CM12 ROM.
While having CM11.x I go to Settings and navigate to "CM Updates" where I can see a list of Nightlys and stable CM releases. When I install the new CM update this way everything seems to go okay, however This may be normal, I get a message from CWM "Possible Root loss, fix?",.. I select yes and it boots up, runs through the whole "Android is upgrading" message and all. When the phone is finally ready for use I get spammed with millions of messages saying "Application has stopped" and they will pop up infinity in less then a second. I have to hold power and tell the phone to reboot into recovery so I can resotre from backup.
I also downloaded the ROM from CM website and flashed it using "ROM manager". I get the exact same issues sadly.
What could be the problem?
Is CWM not compatible with lollipop?
Do I need to run a factory reset and wipe my phone before flashing?
I've been fiddling with this all day now. -Sigh-
EDIT:
Should I flash the latest version of "gapps" ?
You're going to need to do some reading. Installing LP over KK thru a nightly isn't going to work. You'll need LP Gapps for starters and you'll need to go into recovery and do some wiping before you flash. There are some good LP roms here: http://forum.xda-developers.com/lg-g2/development with full installation procedures. Also, most are using TWRP for recovery: http://forum.xda-developers.com/lg-g2/development/twrp-twrp-2-8-0-0-kernel-f2fs-tools-t2898705 You may also need to flash a different baseband but you'll find everything you need in the general development section. Also, next time you really should post your questions in the Q&A section. Anyway, do some reading and you'll be good to go! :good:
Thanks. I actually did get everything up and running
after going back a restore point, I
1: Flashed 10O Radio
2: Factory Reset
3: Flashed CM 12
4 Flashed gapps 5.0
I used latest version of CWM. I had TWRP years ago and I have never liked it compared to CWM
I'm curious about the Radio Modem though, Should I have 10O or Should I have 10D ?
Traceguy said:
Thanks. I actually did get everything up and running
after going back a restore point, I
1: Flashed 10O Radio
2: Factory Reset
3: Flashed CM 12
4 Flashed gapps 5.0
I used latest version of CWM. I had TWRP years ago and I have never liked it compared to CWM
I'm curious about the Radio Modem though, Should I have 10O or Should I have 10D ?
Click to expand...
Click to collapse
First let me apologise, I see that you are in Q&A and I'm the one that doesn't know which forum he's in.
Next, well I've used both CWM and TWRP. Personally I prefer TWRP but as long as you're on the latest and greatest you should have no problems from what I've read. And if you do just flash over to the other and see if it fixes the problem. I've been using the 10D radio for quite some time now and it works for me.
As I go from rom to rom I always do a clean flash, wiping data, system, dalvik and cache. I rarely do a dirty flash but that's just me. As long as you can recover from the occasional boot loop you'll be good. :laugh:
I didn't know where to post this so i am posting it here.
I tried to flash the latest version of CrDroid some hours ago and although the installation began with no errors, the whole thing got stuck on an infinite installation of the ROM. The log displayed "Patching system image unconditionaly."
After about 30 minutes i just lost faith and held down power button to force a reboot. Then, TWRP got reset to the screen which you see when you first flash TWRP, the one ascing about wether to keep system read only or not.
I will post screenshots too as soon as i figure out how to do it
.
Set it back to RW mode from RO mode. If it constantly turns back to RO, try reflashing the recovery image.
If you are lucky enough to abruptly abort a ROM installation, you will be able to atleast use the device. I had aborted a nandroid restore and my entire data partition was corrupted.
In any case you should post it in the appropriate ROM thread.
Make sure system is mounted writable, wipe system, data, and caches, and flash... it's that simple. If it fails use another ROM.
BTW, it is usually useful to tell which device (specifically), what ROM/Gapps, what version of TWRP, etc... the devil is usually in the details, the more the better.
Yeah i forgot about that, im new here. So, its the latest version of TWRP and the ROM was the latest version of crDroid (April 17th). Anyways, me being extremely stubborn as usual, I tried flashing the ROM through FlashFire and the problem is still there. By the way I did mount everything and it doesnt get better. I dont care anyways i'll just return to some other Nougat ROM. Thanks for replying though!
mike.... said:
Yeah i forgot about that, im new here. So, its the latest version of TWRP and the ROM was the latest version of crDroid (April 17th). Anyways, me being extremely stubborn as usual, I tried flashing the ROM through FlashFire and the problem is still there. By the way I did mount everything and it doesnt get better. I dont care anyways i'll just return to some other Nougat ROM. Thanks for replying though!
Click to expand...
Click to collapse
Weird... We can pretty much guarantee nothing is working in TWRP though, or at least it's not processing even the boot image of your ROM or the device wouldn't boot.
What is bootloader status?
Hi,
Its been a while since I been attentive to my Pixel. I was a lucky one who managed to get a Verizon 7.1.2 with an unlocked bootloader. I unlocked the bootloader, flashed a ROM, and rooted and haven't had a single major problem since.
I was running Resurrection Remix from about March and I yesterday I wanted to try to use Android Pay, so I followed a tutorial I found in another thread here to install Magisk, and when it was all said and done I ended up in a boot loop where the phone would reset as soon as it reaches the Google logo, ramdump, and eventually boot back into TWRP.
In the attempts to delete out all kinds of caches and dalviks and factory resets and whatever else, nothing worked.
So in the end I decided to just flash a new ROM. Flashed the latest Pure Nexus, reflashed TWRP, flashed the vendor image... went to go reboot and it gives me the WARNING! NO OS INSTALLED! error. I thought that was odd and decided to just update to the latest Resurrection Remix - same problem.
At this point I am unsure what to do next. I don't care about any user data on the phone, I just want to get it back up and running with a new ROM.
I have a few questions and thank you in advance for all help you may be able to offer:
1) Why am I getting the NO OS INSTALLED issue directly after flashing a ROM? Logs indicate no errors whatsoever. /system/ is mounted. Every time I boot into TWRP it asks me if I want to Keep System partition read only. I always tell it to allow modifications and never ask me this question again - it asks every time. Is it possible that /system/ can actually remain empty even after a fresh ROM install that gives no errors in the log?
2) I believe that I am supposed to reflash to stock image that this phone shipped with to start all over. If I reflash back to stock, will my bootloader have any chance of locking again? I don't even know what version the stock image was, and I'm further confused/concerned about the fact that it was a 7.1.2 image I shipped with - from my understanding there were security updates which make unlocking/rooting impossible. I don't understand why you have to start that far back - is it even needed? The latest Resurrection Remix ROM install instructions assumes that I am on latest "Firmware" NOF26W. This is another issue I don't understand - what is a firmware? The full factory image? In any case, NOF26W is specifically for Rogers Google Pixel devices. Since I need to be on this "firmware" before I install latest, can I just flash the NOF26W Stock image despite the fact that I am using a rooted Verizon Pixel? The NOF26W image is 1.8GB: What exactly in this ZIP am I supposed to flash?
3) There were various weird things about this phone/flashing ROMs that I seem to recall such as having to boot an older TWRP before flashing ROM and then flashing the newer TWRP - is any of this stuff still relevant?
4) I also remember that many people were fastbooting TWRP rather than flashing TWRP for some reason - are there specific builds/non-standard stuff required for any of this to work on the Pixel?
I really appreciate all and any help that anybody can provide. If there's files that you're referring to, PLEASE send links. I need to get this phone back up and running ASAP.
Thanks again!!
when you wipe system, twrp wipes current active slot but when install a rom, it gets installed in the inactive slot (which will become active upon reboot). but twrp still thinks the currently active slots system is erased and complains that no os is installed.
rohitece06 said:
when you wipe system, twrp wipes current active slot but when install a rom, it gets installed in the inactive slot (which will become active upon reboot). but twrp still thinks the currently active slots system is erased and complains that no os is installed.
Click to expand...
Click to collapse
This. I just reboot anyway after seeing that message and I've never had any issues.