So i got this lovely update from Verizon. I rooted using the one touch but never made any changes to the phone. Still using default UI etc. Just rooted to access saves, overclocking.
So the update reboots the phone, starts installing, and fails. Then i can go to the menu and reboot the phone. It will come all the way on, and immediately just shuts down and tried the update again. Stuck in this vicious cycle. Help?
Mount the SD card either in recovery or on a PC and see if there is a PG05IMG.zip on it. Remove it if so, then reboot.
tqhx said:
So i got this lovely update from Verizon. I rooted using the one touch but never made any changes to the phone. Still using default UI etc. Just rooted to access saves, overclocking.
So the update reboots the phone, starts installing, and fails. Then i can go to the menu and reboot the phone. It will come all the way on, and immediately just shuts down and tried the update again. Stuck in this vicious cycle. Help?
Click to expand...
Click to collapse
You can't install an OTA if your rooted, even if you haven't made any changes. The problem is the custom recovery (e.g. ClockworkMod)
When the update tries to install the updated recovery, it sees that the old stock recovery isn't there, and fails.
As far as recovering from that, I'm not entirely sure.
Seeing as you used the one touch root, I doubt you installed the S-Off eng bootloader. Try what the above poster suggested first.
Thanks for the replies guys. I did have s-off, but yeah ill tell you i tried what he suggested with no luck.
I ended up being ok i made another clockwork backup, did a full restore from a backup before the date of the update, then did just a data restore from the backup i had just made. Phone is back to normal. Thanks for the responses, ill give you both marks for being helpful
I'm in the same boat, except I was silly enough to not have a backup made. I do not see the PG05IMG.zip from recovery. Any other possible ways to fix this? If I have to clear all my data and start again, I'm ok with that though I'd obviously prefer not to do that.
Boot into clockwork recovery and wipe cache only.
Sent from my HTC Thunderbolt
This same issue has happened to me with the Verizon update. Long story on how it i clicked okay to the update. I told it reject at least 3 times already.
Anyway - i was stuck in this nasty reboot cycle. I was lucky to have a backup from March when I first rooted my TB. Not having a more recent backup is my bad.
So I have worked most of today with near factory settings from my recovered backup and now I am restoring todays backup to see if I can fix this reboot BS.
I did the Wipe Cache from ClockMod and when the phone rebooted it gave the prompt to reinstall the update which I cancelled. So success!!! Now I can clean up my junk apps and do a proper backup to protect myself in the future.
I have a Samsung Galaxy Y. I got it about 2 months ago and used a stock rom that wasn't from my region on it. It worked fine even with root till about 2 days ago. Then I decided to reboot my phone but it entered a boot loop. I flashed my region's stock rom on it (DDLA1) and then I updated it to the latest version (DDLC3). I thought that since it was using a stock rom it wouldn't get bricked but after rooting my phone again to restore all my apps and data using Titanium Backup it got an unexpected error but it wasn't even immediate. I got the error about 30 minutes after rooting my phone. The error, however, didn't stop my phone completely. It just force closed the app that I was using. But after I rebooted to put in my SIM card it entered the boot loop again.
Some extra info:
Since I'm using Go Launcher I uninstalled my Samsung Home screen, keyboard and any other apps that I don't need.
My questions:
1) Can someone help me figure out the problem. If you need me to give you any extra details just ask.
2) Is there any other way to back up and restore my device.
3) Could any of my previous attempts at unbricking cause this. It worked every single time but each time the same thing happened. It got bricked again after about 30 minutes after bricking. (That's 30 minutes of time that I used the phone. It didn't brick when my phone was sleeping for an entire night.)
If you just reflash stock ROM without restoring any backup, are there still problems? Maybe some app with root privileges causes the error. Please post a list of all such apps you use and aren't sure that they cause no problem.
I use Titanium Backup, App 2 SD Root, and TBPatcher (to get the one click restore to work)
I think the root of the problem wasn't rooting (see what I did there ) but as you said App 2 SD root. Now it works properly without any problems. I'm not entering a boot loop like I used to so I'm extremely happy. I just need to find someway to install apps to the SD. I remember reading about it somewhere but I'm not too sure because I had root access then and didn't care about things that didn't require root.
You said "Since I'm using Go Launcher I uninstalled my Samsung Home screen, keyboard and any other apps that I don't need" - have you simply tried restoring the stock ROM and not doing any of that?
So I just got my GS4 and I rooted it (stock) on the VRUAMDK build and flashed TWRP. I was using an app called No Bloat Free to delete some system apps, mostly VZ apps and Samsung apps. I guess i might have deleted something (but i used backup and delete). Now after i reboot, my phone works for about 30 seconds before it reboots.
Went to TWRP to make a nandroid and so far its taking a while even though the file size is like 8000 MB
I'm a little worried but i'm gonna try to fix it tommorow, just wondering if theres any advice. I would prefer to stay stock for now but i understand i could just flash a stock-like ROM and probably fix my bootloop issue.
Edit: TWRP Nandroid finished (it claimed 800 seconds, but it felt longer lol) so i can take a deep breath lol
Fix permissions after the Nandroid seemed to have fixed bootloop
To Moderator: Fixed the issue myself, you can remove this post if you want or keep it up for other users who might have run into this issue
Edited out
Hi, I've been fiddling around to fix my RNE-L21C432 after I managed to do some things wrong with it.
What I tried to do:
I tried to install LineageOS from the thread in this forum. I downloaded a couple of TWRP recoveries and tried them all - no avail.
So I read I also needed to delete /system. So I was like, hell, I just delete everything including /vendor and /oeminfo.
And then the fun started... I managed to install OpenKirin's LineageOS. The install whent fairly okay, but the software is buggy, the bluetooth doesn't work, the icons were small, the system UI kept crashing regularly and performance was bad overall.
So, back to stock EMUI I thought. Ha was I wrong. I followed KingOfMezi's guide to restore the original ROM.
It all went fine in the first couple of minutes. But, oh wait, there goes the bluetooth again. And as soon as I unlocked the phone, the system UI crashes, it restarts, the Play Store is buggy as hell. So back to the working table I thought!
I used HWOTA (boots to eRecovery only to show an error which is unresponsive after all) , Huawei's Multi Tool (also gives errors when trying to restore stuff), HiSuite (can't find phone) and even Huawei's stock recovery can't be used anymore (can't click on any of the buttons to download recovery, factory resets fail,...).
This phone has been the most annoying ever to root and to install ROMs. My old Galaxy S2 and Oneplus One were great.
TL;DR is there a way to restore this device completely to stock, as deep as it goes?
Edit: I tried HuRUpdater to install the 3 update.zip files and finally I got my phone working again.
Sorry for you wasting your time if you read this
dabateau said:
Hi, I've been fiddling around to fix my RNE-L21C432 after I managed to do some things wrong with it.
What I tried to do:
I tried to install LineageOS from the thread in this forum. I downloaded a couple of TWRP recoveries and tried them all - no avail.
So I read I also needed to delete /system. So I was like, hell, I just delete everything including /vendor and /oeminfo.
And then the fun started... I managed to install OpenKirin's LineageOS. The install whent fairly okay, but the software is buggy, the bluetooth doesn't work, the icons were small, the system UI kept crashing regularly and performance was bad overall.
So, back to stock EMUI I thought. Ha was I wrong. I followed KingOfMezi's guide to restore the original ROM.
It all went fine in the first couple of minutes. But, oh wait, there goes the bluetooth again. And as soon as I unlocked the phone, the system UI crashes, it restarts, the Play Store is buggy as hell. So back to the working table I thought!
I used HWOTA (boots to eRecovery only to show an error which is unresponsive after all) , Huawei's Multi Tool (also gives errors when trying to restore stuff), HiSuite (can't find phone) and even Huawei's stock recovery can't be used anymore (can't click on any of the buttons to download recovery, factory resets fail,...).
This phone has been the most annoying ever to root and to install ROMs. My old Galaxy S2 and Oneplus One were great.
TL;DR is there a way to restore this device completely to stock, as deep as it goes?
Edit: I tried HuRUpdater to install the 3 update.zip files and finally I got my phone working again.
Sorry for you wasting your time if you read this
Click to expand...
Click to collapse
Yeah, don't delete /vendor if you want to flash Treble. Treble only uses system, if you wipe vendor stuff will break.
Hi!
Finally I got stuck in a boot loop on my Pixel 6 running QPR2.
It's looping after the G animation (vibrates a few times at that point when attached to a PC).
Reflashing the latest QPR factory image (without -w) by using SDK 33.0.3 does not solve the issue.
The ROM was running fine before, but it rebooted due to a faulty custom kernel version and now I'm stuck.
My theory is, that the launcher (nova) can't load and therefore it reboots.
Anything I could do using fastboot?
Never flash a custom kernel on a stock ROM, If not suggested by the dev.
I understand that you flash without wipe?
Done that for years without any issue.
The last version of the custom kernel had an issue and caused reboots.
Not sure if this is the ulprit, but normally that should be solved by flashing factory image without -w.
So the question is: Is there any other option than doing a factory reset?
Sui77 said:
Done that for years without any issue.
The last version of the custom kernel had an issue and caused reboots.
Not sure if this is the ulprit, but normally that should be solved by flashing factory image without -w.
So the question is: Is there any other option than doing a factory reset?
Click to expand...
Click to collapse
If the kernel broke your actually ROM, nope. You could backup the file stored locally via adb in the recovery, but not anything more.
Wipe all is the best, better than have to handle with an hard brick.
Sui77 said:
Done that for years without any issue.
The last version of the custom kernel had an issue and caused reboots.
Not sure if this is the ulprit, but normally that should be solved by flashing factory image without -w.
So the question is: Is there any other option than doing a factory reset?
Click to expand...
Click to collapse
If I were you I'd maybe get some logs and go through them and see if you can find anything that way. Maybe add logs to your op here.
There aren't many ways to backup things nowadays for pixel 6 but what I have used to backup apps + app data that works well when restoring is Neo app from Fdroid store. As far as backing up goes, at this time I've used nothing that is/has been as solid as Neo. I miss the days of just being able to boot one of a few various custom recoveries, making a nandroid backup to a USB thumb drive with my OTG cable and restore it whenever it was needed but things change. Sounds like maybe something was left behind from your kernel install. If you really dislike formatting I'd stay away from whatever you installed here to get in this loop but definitely backup using Neo once you get going again and put your backups on thumb drive or you PC or somewhere other than your device so you can restore them when you need to. I don't flash nowhere near as much as I used to but I used to flash my device(s) many times a day , everyday for many years but I remember years ago on another device I looped and wiped my cache and system and reflashed rom and ended up booting up. But that was another device years ago. Maybe try adb sideloading instead of factory image flash without wiping data. Try that and after it's done installing reboot to others slot and sideload it again... These things probably won't work but you never know until you try. Did you have magisk installed before and not now? Maybe flash stock kernel patched with magisk to both slots if so. Hate to say it but you will probably end up having to format data but idk because I don't know exactly how you installed the kernel "in detail" or exactly what kernel it is or if anything else was changed from before you looped ... No logs...
I've been using Android since the beginning (G1) and I've been tinkering with my devices since back in the Nexus S days on a regular basis and I've found that the best way for to get the help I need is to try like hell to figure whatever it is out myself by searching for the problem I'm having, I mean like really searching, sometimes for hours , sometimes maybe searching for things related to the problem I'm having that show up in my searches, sometimes the answer can be in another devices forum, piecing together bits of info from various places to try and solve whatever it is... etc ... etc... But the best way to get help is do research on it, take some notes, try various things to fix it, then if I still can't figure it out make a post about it here and in op attach every log I can possibly gather from said device, include all the things I tried to fix it with myself "in detail..." My exact installation process, you know like: reboot bootloader, was on slot A, executed ./flash-all.sh for factory image xxxxx, rebooted system ... The more details you provide the more accurate people will be when answering and the more people you will get to reply.. I'm not trying to sound like some asshole or anything at all. Im just speaking what works best here to get answers. Sometimes you just don't get any answers even if you post 18 paragraphs with a chart and a line graph, things you tried, what all you tried it with and links to it all. But anyone here who does this will most definitely stand a much better chance at getting some replies on whatever it is. I sometimes read over on Reddit and Tele groups , sometimes answers can be found that way. Sometimes people just give you the silent treatment.. Even if you do your homework. That's just a thing with anything related to development that happens. I always used to think when I would get no replies that the other guys and gals who know the answer are thinking to themselves, "oh look at this idiot here!" "He clearly didn't graduate from Harvard top of his class with a PhD like we did. " " Such an imbecile!!! " But what could have been going on and more than likely was/is is life , kids, bills, sleep, relationships, covid19, and tons of other things..
Some of this development stuff is a real beech to get and everyone works hard to get it and many aren't too fond of just giving random people answers that took them many sleepless nights to get. But if and when a dev sees someone with a detailed post , things tried.... etc ... etc .. Theyre much more likely to throw some knowledge your way. That's been my experience anyway.
@flash713
Wow, thx for thw write up, appreciate!
I was on latest QPR2.1 with Radioctive Kernel, Magisk installed.
Since the device got stuck in the boot animation, I tried a lot and flashed different factory images using the flash-all method. w/o success.
Also tried the Flash tool in the google website, also w/o success.
When the device boots while it's connected to the PC, it beeps/vibrates 3 times and the reboots.
My guess is that it has problems to load the launcher, Nova was set as standart.
I'm using android since years, tinkering a lot, but I'm not a pro in doing so.
Meanwhile i set up my new Pixel 7 and restored it via Google backup and a few apps by using a SWIFT backup.
Fotos were restored by Google, but all whatsapp pictures are messed up ow, cause the date of restore.
How do I gather proper logs?
Did a last attempt and sideloaded the OTA to both slots...same outcome...
Doesn't magisk have a remove all modules.zip? I mean oriole doesn't have TWRP available yet.
I presume that when it's bootlooping you don't have any ADB?
You did have ADB enabled, right?
Depending on system and setup you may have ADB started by init or started by Android.
Your problem could be as simple as a bad Launcher.
I don't know if the P6 has a UART console. Does it?
Hi Renate,
thx for your reply.
Yes, that is what i thought. The Pixel boots up into the G-animation and then loops 3 times (beeping/vibrating if connected to PC) and than reboots in total.
I think I had something like that in the past when I accidently deleted the launcher apk (don't ask )
Anyway, Nova launcher was set as standart, so the only idea could be to set the genui Pixel launcher as default, but I don't know how to do that in fastboot or adb mode.
Sui77 said:
Anyway, Nova launcher was set as standard, so the only idea could be to set the genui Pixel launcher as default, but I don't know how to do that in fastboot or adb mode.
Click to expand...
Click to collapse
I'm still not clear if you have ADB ever available.
If you do you could:
Code:
adb uninstall com.nova.whatever.launcher
If the /data/data that Nova is using is corrupt or missing it could cause failure.
Android will switch to whatever else belongs to android.intent.category.HOME automatically.
If there is nothing there you can install another launcher.
Have adb (after booting into recovery mode), will report back asap
I habe adbd device connected via recovery/rescue mode, but that's not working.
In bootloader, I can't use adb, no device connected.
Hw can I use adb while the device is not booted up?
Can you mount data in recovery (and it's unecrypted)?
Feeling a bit dumb, but I can only boot into fastboot or into the boot loop, don't know how to mount data in recovery mode (the one with the andoird robot)
When you're in the boot loop you don't get adb even for a few seconds?
This are the last lines of the recovery.log
2 new items by TheMrSui
photos.app.goo.gl
Checked that by opening a cmd and using "adb devices", but nothing showed up
When you're viewing that log, don't you have ADB working then? It says that it is.
I had this weird issue on Raven, first try using android flash tool through a chrome based browser. If that still loops then wipe, and flash an older image. For some reason I had to flash an image from the previous month and that would boot.