I messed up my phone today and had to do a nandroid restore. After restoring, phone boots up and gets past the boot logo animation and then gets stuck at "Phone is starting...." for over 1 hour at this point. If I press and hold the power button, I can see the power menu just fine, but I can't get past that screen at all.
I've tried a bunch of things, including flashing a .zip that removes the lockscreen and none of them worked.
One of the things I tried is to do a clean ROM install (Havoc OS Android 11). I let it boot up into the ROM, customized it a little bit and then did a new nandroid backup. I then wiped system and data and restored from the backup, exact same issue showing "Phone is starting..." and this tells me that it's got nothing to do with Magisk (because I haven't flashed it) and it's got nothing to do with any apps. It's literally a clean ROM, so a nandroid restore should have worked.
I've tried with the latest TWRP and the latest Fox Recovery. Same issue.
Anyone have any ideas why? I don't have this issue on my other device models.
Related
I have a rooted HTC Hero (Sprint) and during preparations for upgrading to CM7 I ran into issues with ROM Manager.
First, I backed up everything (apps and data) via two different methods. I cleared davlik cache, and then performed a CWM Flash Recovery backup. Once that completed successfully, I sought out to apply the CM7 ROM. I selected it from the GUI menu, rather than rebooting into the Flash Recovery. I selected to backup everything and then wipe the data/cache. During the process, the phone hung (white HTC screen for over 10 minutes). I could reboot successfully after this, and selecting "Recovery" didn't work either. I figured my phone was bricked. But miraculously, it managed to finally recover.
The recovered ROM was a fresh clean slate. So, I installed ROM Manager and Titanium backup again. However, when I tried to reboot to the CWM Flash Recovery, or even try entering the CWM CUI menu from power up (by holding the HOME key), the phone hangs. Something is seriously screwed up with ROM Manager. I'd like to wipe it completely clean and start over, but everything I've tried results in a phone that hangs. I'm now thinking I should use a different program for managing the ROMs... but, being familiar with ROM Manager and seeing other people use it successfully, I feel determined to make it work. Any suggestions?
I would just flash an RUU and start from scratch.
https://docs.google.com/file/d/0B9lyYjZr_O3gZnJrRVFqRmh4eVU/edit
I was able to recover.
What I didn't realize is that the first boot can take upwards of 20-30 minutes. I pulled the battery after around 15 minutes, thinking my phone had hung.
Anyway, when I selected "Recovery" again I left the phone alone and eventually I got a stock ROM again. Whew!
While ClockworkMod is fine for 2.1, when you're on 2.3 there's no question that TWRP is the way to go. I've flashed it to my phone (did "flash_image recovery [recoveryfilename.img]") from the terminal window and it's working great, far more extensive than ClockworkMod.
Hello all. I have been in the Android root community for a little over three years, and even after tinkering with the various devices I've owned since, I cannot get my T599N to come out of its current bootloop.
A background: I had been checking some things in my settings app (running stock, rooted), and I ended up just force closing the settings app to get out of it quickly. Well, this action deleted all of my text messages, and later on it removed my notification bar and made my wallpaper go black. I ended up booting into recovery mode to try and clear the cache. After it cleared, I rebooted, and bam, the bootloop started.
Now, here's what's interesting. The phone is in a bootloop where it displays the first boot message (SGHT599N Galaxy Exhibit or whatever), and then it tries to boot into cwm recovery, displays the loading screen for that for 2 seconds, and just reboots again. I've tried installing a stock rom from ODIN with no success. The rom apparently loads onto the device but it's still in the bootloop. After this, I tried to install philz recovery to try to install a zipped rom to get the device to somehow boot. I tried to factory reset it for installing purposes, and it just reboots. The device will literally clear everything but /data, so that makes me think that it may be a file system problem. I really need to get it to work, as I am out of a phone right now.
Does anyone have any suggestions? I've tried everything I know.
I am having a hard time recovering from my curiosity with my XT1060, Developer's Edition (unlocked bootloader and all)
I had factory 5.1 ROM, xposed and all tweaked. But it's been months, phone's getting slow, and I'm itchy for MM...
So last night, I made a TWRP/nandroid backup onto my USB-OTG stuck, and then, installed Resurrection-Remix-M.
Works fine, until I tried to make a call. I can't hang up. After 30 seconds, the phone rebooted.
I had another guy call me. The phone rings, but the screen is blank. I cannot pick up the call. WTF? I tried turning screen back on, screen's blank. After a couple attempts to swipe blindly, power button, the phone rebooted.
At this point, I'm like WTF, that's enough. So I tried to plug in the USB-OTG and tried to restore.
TWRP does NOT see my backup. At this point, I realized that perhaps TWRP can't see the item due to MM's security structure.
So I engaged the RR's CM explorer and copy the Nandroid backup onto the built-in 32 GB . THere should be enough room.
I looked back X minutes later, the phone had rebooted itself (?!!) and it's stuck at the bootloader logo (I had replaced it with generic "White Google" logo)
I cursed a bit more, did the VOL-DOWN / POWER to bring up the Fastboot menu, and boot into recovery. I got the Team Win logo, then nothing. I waited 5 minutes. It's stuck too.
At this time, I'm cursing a blue streak. My phone has been dead for HOURS now, no end in sight.
I went back into Fastboot, did Factory (which I assume is "Factory Reset?") no effect. Still freezes both normal boot and recovery boot.
I boot back into Fastboot mode, I already have Minimal ADB and Fastboot loaded on PC, so I use that to flash the a new recovery.IMG (downloaded fresh off TWRP.ME for ghost) and rebooted. STILL FROZEN at TWRP. WTF?!?!?!
(FWIW, Ghost TWRP is still 2.8.7.0, while TWRP main is already at 3.0.2)
At this time I'm at a loss as on what to do.... I tried extracting one of the factory ROM's boot.img and flashed that via fastboot, nothing.
I just RSDLite the 292-ghost_verizon_51.... ROM onto the phone (with servicefile option). It rebooted to the bootloader warning, so flash did work, but it doesn't seem continue to boot either, but I guess I was supposed to have waited like 10 minutes just to get past the bootloader? I flashed the TWRP on there. Still waiting for TWRP to load. After a couple minutes, I decided it wasn't working.
I'm now using RSDLite with the Flashfile option (wipe out all the data). Wonder if this will do it?
EDIT: Now I'm past the bootloader logo and now it's kinda stuck on the Verizon logo, but I guess that's to be expected. Still charging... and waiting.
EDIT2: Verizon logo took about 5 minutes to boot into setup. I just hit skip / skip / skip until I got to launcher. Shut down, reboot into fastboot, flashed recovery again, and booted TWRP recovery successfully this time. (sigh)
Lessons to take away from this diversion that took HOURS away from my life... For no appreciable gain.
* Keep a flashable nandroid backup on the phone. I know it takes up GB's of space. But you'll be thanking yourself (and maybe me) when there's a problem and you need to recover, especially if you're into MM or N.
* And keep that nandroid backup UPDATED! (nightly, if possible)
* ALWAYS keep a copy of the stock ROM on your regular PC, and keep Minimal ADB/Fastboot (or whichever flavor recommended for your device) and Gapps loaded. Do update every once in a while.
* ALWAYS refer to XDA
When I tried reinstalling Stable OxygenOS 4.1.6, the phone locks up upon install and setup screen. This goes for previous OS versions, as well. It takes force quits, restarts, and numerous install attempts and the phone still locks up. I tried stock recovery, old and new TWRP versions, all of which are clean installs, Nothing. LineageOS and other Hydrogen based roms still lock up, either at the setup screen, or when I try and activate developer options. Every Rom I tried after activating developer options, it doesn't leave the gear icon in the menu, either. It takes a restart (force quit) for it to show up. Also, WiFi doesn't work. Sometimes when I try and install OxygenOS either by sideloading, or through TWRP, the phone locks up at the wifi setup screen. This goes for every version of OxygenOS I tried. Your advice is appreciated. Thanks.
I had some problems last night while switching back and forth between Beta and stable. I could try to help but I'm not a guru at this, so wait for confirmation if you are not sure.
First I think you need the right TWRP version. 3.1.1-2 is the latest one, but I'm using 3.0.4-1 (flashed stableOOS with it) and everything is back to normal for me.
Try a clean flash of stableOOS. TWRP > Advanced wipe, select dalvik,cache,data,system and swipe.
Then install the OS. Don't reboot yet, and instead boot into recovery after going back. I read that this ensures you keep TWRP.
It may say No OS installed, but go ahead. Then boot into system again. This worked for me and I restored my backups
I just went from beta 10 to 4.1.6 and have no issues at all.
I followed the basic procedure, in TWRP (recommend to use the latest bluesparks one from his kernel thread - just TWRP no need for his kernel), I did a factory reset, (in TWRP just swipe to Factory reset from the WIPE screen where it says 'Most of the time this is all you need'), its correct nothing else needed, then flashed the full v416 file, then flashed Magisk 13.2, rebooted to system, that was all. TWRP was not lost with this method.
System booted to stable v4.1.6 and no issues.
Check what format are your partitions fornatted in. Make sure they are f2fs. Otherwise try the debrick tutorial. It helped me fix a lot of bugs on my 3T.
I tried all of the above, and I'm certain under the right circumstances, your advice would work. In the end, I used the unbrick tool which brought it back to it's original locked state, and I'm still running into issues. I wonder if there's a hardware issue somewhere that was the result of using Beta. The OS boots up and I'm finally able to access developer options, but no WiFi and the phone still refuses to restart or power off unless I do a hard shutdown. I've never seen anything like it. Numerous ROMS, recoveries, and sideload installs using the One Plus Recovery, and it still doesn't work.
Thanks for everyone's input, but I feel like this phone is done.
Hi everyone! I have been suffering with this problem for 2 full days on my S10 (SM-G973F/DS) and now i just have absolutely no idea how to fix it, so I thought it was worth writing about it here.
On stock, I used one old and outdated application that made user certificates system certificates, but which worked. Having tried it on EvolutionX 5.9.1 (Android 11), it brought the phone into a bootloop. I didn’t have a backup and because in order not to go through the installation process on a new one again, I decided that I would try to delete the folders from the data partition ONLY, but after half a day of attempts, nothing happened and I started to install the rom from scratch, but then weird things began to happen: after reinstallation/factory reset, boot animation randomly started (check attached video), which either went into an endless boot, or loaded the system back, but then if boot animation started on loading then this loading become endless, and the buttons (in the system) "Reboot to recovery", "Reboot to bootloader" and etc simply turning off the phone without booting into the recovery or bootloader, and if this happened, then somewhere in 2 minutes after turning it off.
I think i tried almost everything: re-installation according to the instructions, re-installation according to the way I did it before, I even tried to install the stock, and after the recovery again and then rom, but absolutely nothing changes, I cannot use custom rom if it is up to this worked fine and everything started on the same version as I was trying to install like before, I even tried to download the rom installation file again, not installing magisk-patch in boot, installing multidisabler, even find my old backup for TWRP that has every partition, but absolutely nothing changes, maybe someone knows how to fix it?
Thanks in advance!
P.S Stock rom works perfectly (android 11), but i want to use custom anyway (also android 11)