Very strange. My phone was working perfectly yesterday. But this morning when I powered it on, it's stuck in a boot loop (going over and over to the first splash screen).
I can't get it into recovery either, which also seems odd.
I'm sure I can get it out of it by flashing a ROM or perhaps factory reset (goes into hboot fine). Will experiment a bit later (no time this morning) to see if I can get it out of the loop without flashing a ROM though - e.g. I will probably try just flashing Clockwork via fastboot.
Just putting this up there for info. I flashed a new radio yesterday, but as I said the phone was working perfectly, so I don't see why that should have anything to do with it.
I had issues flashing CWM recovery via fastboot... I was able to "fastboot boot recovery.img" From there, you can flash a ROM with ROM Manager and reflash your recovery.
Let me know if you run into the same issues.
steviewevie said:
Very strange. My phone was working perfectly yesterday. But this morning when I powered it on, it's stuck in a boot loop (going over and over to the first splash screen).
I can't get it into recovery either, which also seems odd.
I'm sure I can get it out of it by flashing a ROM or perhaps factory reset (goes into hboot fine). Will experiment a bit later (no time this morning) to see if I can get it out of the loop without flashing a ROM though - e.g. I will probably try just flashing Clockwork via fastboot.
Just putting this up there for info. I flashed a new radio yesterday, but as I said the phone was working perfectly, so I don't see why that should have anything to do with it.
Click to expand...
Click to collapse
You might have to flash a rom via bootloader/fastboot. Just remember you can't flash one with a older hardboot version. If you have the eng bootloader, you shouldn't have a problem. What a pain though, I hope it isn't the radio either as I flashed a different one earlier tonight also, lol!
Crap, I flashed the same damned radio as you did too. Ha! Although, I do find this ironic after our little debate about the forum merge yesterday I'm sure you can try reflashing recovery via fastboot and if that fails reflash stock rom through fastboot. Its not bricked for sure...
Did you reboot (properly) after you flashed the new radio? (i.e. after it powered on once).
I did worry that anyone with radio s-off will have issues like this when they tried to flash a new radio.
Lennyuk said:
Did you reboot (properly) after you flashed the new radio? (i.e. after it powered on once).
I did worry that anyone with radio s-off will have issues like this when they tried to flash a new radio.
Click to expand...
Click to collapse
He must have had a bad flash... I flashed the same radio with no problems and several powering off attempts and reboots, checking compatiblity, and backups. No issues and have already reflashed a few roms and kernels. The radios are safe... at least the lastest desire z one from Eygpt and the two stock tmobile usa ones are too.
I never did a second reboot after flashing the new radio, but it did reboot after flashing it from fastboot of course, and it worked perfectly for the rest of the day (I'm positive I was getting a better signal).
I just tried fastboot to flash CW recovery - same problem (stuck in boot loop).
I then tried fasboot boot with the CW recovery image - same problem.
Then I used fastboot to reflash the radio. It worked ! The phone is back up and running.
So that's odd. Could just be a bad flash, as has been suggested ?
steviewevie said:
I never did a second reboot after flashing the new radio, but it did reboot after flashing it from fastboot of course, and it worked perfectly for the rest of the day (I'm positive I was getting a better signal).
I just tried fastboot to flash CW recovery - same problem (stuck in boot loop).
I then tried fasboot boot with the CW recovery image - same problem.
Then I used fastboot to reflash the radio. It worked ! The phone is back up and running.
So that's odd. Could just be a bad flash, as has been suggested ?
Click to expand...
Click to collapse
Sounds like it... I've seen this happen on some old WM phones before.
Well my phone has exactly the same problem this morning after being left powered off overnight.
I tried flashing the recovery image and radio image again, via fastboot, like last time, but it didn't help.
Going to reflash the stock ROM. I'm starting to think there is something wrong with my phone and it's going to have to go back
Shizzer! Again? You went back to stock after using Visionary didn't you?.. Done Rage from clean yeah?
ddotpatel said:
Shizzer! Again? You went back to stock after using Visionary didn't you?.. Done Rage from clean yeah?
Click to expand...
Click to collapse
No I didn't use Visionary lol.
Yesterday, after first having the problem, all I did was flash CW recovery and flash the new (Egypt) radio again. Then the phone was back to life, I rebooted it several times and all was 100%.
This morning though it was stuck again but flashing CW recovery and the radio (both via Fastboot) didn't help at all.
So I've just flashed the stock UK/Europe ROM. Will root again via rage, install ROM Manager, flash Clockwork and restore the nandroid backup I did last night.
I will stay back on the stock ROM/radio combination for a bit because I'm starting to wonder if my phone has a problem. No-one else has reported an issue with this radio.
Edit - back up and running fine now after doing the above.
I'm still newbie in these phone things but really sounds like something is corrupting your files.
Device working perfectly after a flash and getting into boot loop later sounds like a hard ware problem to me. (also I have understood that /system is r-only if you don't remount it?)
AnyDone said:
I'm still newbie in these phone things but really sounds like something is corrupting your files.
Device working perfectly after a flash and getting into boot loop later sounds like a hard ware problem to me. (also I have understood that /system is r-only if you don't remount it?)
Click to expand...
Click to collapse
Yeah I know what you mean. I'm going to stick with the stock radio (even though it's worse than the newer one) for a while to check that the problem goes away. Then I will probably try flashing it again to see if the problem comes straight back again.
I also did wonder about whether I can just "dd" the new radio to the correct partition instead of using fastboot to flash it, though I'm not going to do that unless someone can confirm that's ok.
hi all.
I got a Vodafone Romania Galaxy Nexus yesterday and started doing the usual stuff , oem unlock, root, install custom rom... Everything went smoooth ( i had another gnex in december so i knew what i had to do). Used Galaxy Nexus toolkit 5.3. I installed ARHD 2.1.5 with stock kernel then i tried to revert back to stock. So i got the images from google site and reflashed with the same galaxy nexus toolkit.
Then it started. After flashing was ok, phone rebooted and started to bootloop. Shows the Google logo, vibrates and reboots. Countless times.
Tried to reflash it. same stuff. Used the odin file chainfire posted. Odin flash was fine too, but when it rebooted, the same endless loop. Tied all rom variants ( its a GSM Nexus). Nothing, still loop.
I thought i should re-lock it and try to get it back, but the fun part is I cannot re-relock. I start the phone, go to fastboot, it shows up when i type : fastboot devices, i do fastboot oem unlock command, does its magic, shows up as locked, but after reboot ( even if i reboot bootloader), it's unlocked again.
I can flash temporary CWM but not permanent. Needles to say i didnt't do a nandroid before....
What else can i do, if there's anything i can do to make it work?
Thanks in advance.
I recently flashed the newest CM Nightly. When I booted the phone up, I was having too many bugs for my taste, so I decided to flash back to my previous rom Pure Nexus. When I did that, everything went well according to the recovery. However, when I booted the phone, it was stuck in the boot animation. So then I decided I'd flash back to stock and start all over from the beginning. Brought up the bootloader and prepared the whole fastboot thing only to get this message:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot devices
???????????? fastboot
I reflashed CM to see if I could get my phone to work at least and it would boot up, allowing me to use basic phone functions, but apparently my mobile data isn't working.
Now I can't do anything in fastboot. What did I do and can I fix it? Thank you all for the help in advance.
Edit - I was able to get it to register in fastboot somehow, so I tried flashing the latest stock firmware. It appeared to work perfectly. Now when I boot up the phone, I get past the boot animation and an error pops up saying "system UI has stopped" and won't go away. Now when I attempt to get fastboot working again, I get the ?????????. WTF did I do? Is my phone FUBAR?
Firstly reinstall fastboot.
Secondly flash fully stock again, latest version.
If you flash everything again everything should be OK.
Thank you for the reply. I did what you said and again everything appeared to flash correctly. However, once I got past the boot animation again, the "System UI has stopped" message popped up and I can't do anything with the phone.
Should I lock the bootloader to make it completely stock again? Keep flashing until it works?
Okay so I decrypted my data partition and now it works perfectly. Weird. Thanks for your help anyway.
Hello all, my M9 has been crazy since some days. I have a lot of different problems and haven't been able to see what the common issue is, so I will list everything I know:
1. European M9 unlocked, baseband 01.01_U11440792_97.00.51203G_F, OS-3.35.401.32
2. Had official Android 6.0 and couldn't update OTA to Nougat (update crashing after 25%) so I tried rooting and flashing a custom ROM (RR-N-v5.8.0-20170106-himaul-Unofficial). Worked without problems for 3 months and 2 days ago my phone restarted and didn't boot to the rom anymore (I see the HTC logo with white background and red letters, after 10 seconds or so I see the logo of my rom but it freezes and restarts again, over and over again).
3. Tried flashing the same version stock rom with RUU method (renaming it to 0PJAIMG.zip and place it in sd card) and this failed because of a problem with the zip signature.
4. Tried another custom rom (ViperOneM9_6.1.0) and the same situation (I see the rom logo but freezes and restarts again)
5. After flashing the 2nd rom, my TWRP stopped working (I see the logo of TWRP and freezes, restart)
6. I tried using fastboot commands to boot to recovery and nothing happens, tried flashing different TWRP versions and still freezes.
So at the moment the working modes are only download and bootloader.
Any ideas of where the problem is?
I'm pretty used to flashing custom roms but never had such problems before, so my knowledge doesn't go that far. Also if you need logs, please give me some instructions on how to get them. Thanks
Not sure what is going on or if anyone else has this problem, but since I got the Moto G power I've had a problem booting into the system after flashing stock ROMs in fastboot. Everytime I try my device doesn't go past the blue Moto logo. I'm no stranger to rooting/flashing ROMs/or anything like that. I probably flash more than necessary always switching up my phones. Ive flashed fastboot ROMs for years with no problems. I've got used to just using LMSA and it never failed to fix my issue. Now, LMSA won't recognize my device in terms of matching firmware and I can't use it without validation. I can flash everything fine and start to boot but nothing after that. I've tried formatting, factory reset in both stock and twrp to no avail. Even restored my Omni backup countless times in twrp which usually did its job no problem. Tried flashing vbmeta etc.. am I just experiencing tunnel vision and missing something obvious or what? Any help would be appreciated I'm not the same without my phones working device is US retail unlocked 2041-4 Sofia on what I assume is the latest firmware. (lolli Moto)
You've been trying to boot it with the stock kernel and not a magisk patched one after restoring however? / Have you tried booting without a magisk patch kernel (stock) and userdata formatted?
I had the same problem updating the firmware and i had to first boot it with the non rooted kernel and userdata formatted to first boot.