Develop Bugs

Stuck in a boot loop

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.

[Q] CWM Recovery rom flashes won't boot

Hi everyone, I've come into a strange problem with my G2 and I bet someone here can help me out! I just got a refurbished G2 because my last one had display problems. I tried to root with one with gfree (05) and I ran into a couple of errors so I rebooted my phone and used the rage method. Anyway, I downloaded rom manager and flashed CWM 3.0.2.4 so I could flash that leaked gingerbread build. It wouldn't work for me, so I flashed xborders' version and it's all good. I went to flash the stock rom (to go back) and when it reboots it stays stuck on the HTC splash screen. The same thing happens with CM7, or any other rom I've tried recently. I let CM7 flash when I went to sleep, when I woke up it was still stuck on the HTC screen.
I'll explain what I do:
1. Flash superwipe g2
2. Flash the rom in recovery
I accidently deleted my froyo nandroid but I have one from xborders rom so I at least have a usable phone. Could my sd card be messed up? I've tried it on the two I have.
I had this problem with my other phone too, no matter what I tried I couldn't get CM7 to work. Now it seems like no roms are working.
After I do flash a rom, it doesn't say reboot system like I think it should? I have to hit back to go back into the recovery menu.

Ended up fixing the problem, thanks to anyone who looked at this!

Care to tell us how you fixed in case someone else comes to this thread for reference?

He probably didn't root the phone properly or the partition table has been messed up. To fix something like that just flash a stock ROM that you know works on the phone and from there you can use any root method to get SuperCID, Permanent ROOT, an unlocked HBOOT and ClockWorkMod. Then any rom designed for the G2/DZ should be flashed just fine as long as the requirements are met.

[Q] N7105T root, CWM process

Hi all,
I've rooted my new (Telstra/AU) N7105T using Odin & ChainFire's autoroot ala http://forum.xda-developers.com/showthread.php?t=1933542. I've installed ROM Manager (+premium) & tried to flash CWM (6.0.2.8), but have struck a problem. The root went fine (and works), but when I try to reboot into CWM-recovery, I get the Samsung splash screeen, then the screen does this weird scroll/wipe thing - and it gets stuck at that point. I have to power-on+vol-up to break out of the boot cycle to boot normally.
There's a possibility that I flashed it twice (screen went to sleep, I didn't see a confirmation on the first time, so tried it again). Unsure if that makes a difference though.
Is the problem that CWM isn't supported on this phone yet, or have I screwed something up?
Cheers,
Brettt

brettt said:
Hi all,
I've rooted my new (Telstra/AU) N7105T using Odin & ChainFire's autoroot ala http://forum.xda-developers.com/showthread.php?t=1933542. I've installed ROM Manager (+premium) & tried to flash CWM (6.0.2.8), but have struck a problem. The root went fine (and works), but when I try to reboot into CWM-recovery, I get the Samsung splash screeen, then the screen does this weird scroll/wipe thing - and it gets stuck at that point. I have to power-on+vol-up to break out of the boot cycle to boot normally.
There's a possibility that I flashed it twice (screen went to sleep, I didn't see a confirmation on the first time, so tried it again). Unsure if that makes a difference though.
Is the problem that CWM isn't supported on this phone yet, or have I screwed something up?
Cheers,
Brettt
Click to expand...
Click to collapse
Hey Brett,
I also have the N7105T. I tried to flash CWM to the phone earlier today too, and I had the same problem with the flashing screen. The only way I could fix it was to boot the phone into DOWNLOAD mode and use ODIN to flash TWRP recovery.. at least now I have a working recovery again.. I wish it was CWM, but at least TWRP works.
You've probably solved it by now considering you posted 2 months ago, so if you have, let me know how you got around the problem
Pete.

stupid mistake but can't seem to fix

Hi all.
I have been trying to root and load a custom ROM on my friends Chinese htc one m8.
I unlocked the boot loader fine. Then flashed twrp. Here I missed the actual root of the phone which is silly. I then flashed a custom ROM and now stuck in fast boot mode when I reboot.
I know I missed the actual root section. I tried to plug the phone back in computer and use command window to root. But it says device offline now.
Is there anything I can do? Its not rooted. I just think I've wiped the stock HTC software and I didn't make a back up. Please help

V410 7.0 LTE bricked

Ok guys I am pretty sure I fubar'd my tablet.
I am stuck in a recovery loop. When I start the tablet it just goes back into recovery. Which if I still had TWRP I think I could still do something, but I flashed cyanogen recovery trying to flash cm13 since I cold not get anything else to work. I cannot boot into download/firmware update screen. The screen just flickers a little and goes dark.
A little background:
Started when tablet forced install of 5.0 update and I was in a recovery loop. I flashed 410 test build, rooted, flashed twrp, installed stock rooted ROM. Everything was fine. Then tablet did it again, this time I just flashed rooted ROM and factory reset. Even took the steps to fix the white lines and storage issues. Was working fine. Got home a few days ago and I was in a recovery loop again. But now I don't have the bootloader screen/download mode/firmware update screen (whatever you want to call it) so last night i tried to download cm13, Gapps and cyanogen recovery with no avail.
I can access adb on my PC while in recovery, but when I try to access ADB shell I get unauthorized something or other. Because I cannot authorize USB debugging, because ROM won't boot. I tried to flash stock rooted ROM from cyanogen recovery and it says not signed or something like that.
Does anyone have any ideas? I really think I have screwed the pooch here.
sent from a device using an app

title
if you have a stock recovery image flashing it is easy, i had a LOT of troubles with my v410 and still am working with it. i have mine rooted, just with TWRP though, i cant use xposed framework, which negates why i rooted this in the first place. anyway, through much grit and determination flash your stock image after wiping what needs to be wiped and doing all other necessary things. Then, you must download kingo root, supersu, superuser. flashify would help with the flashing i hear, but it has troubles with the v410. kingo root was an apk i managed to find buried under a million viruses on the 34th page of google..or something. rooted mine in one click, from stock to reboot to twrp root.. many glitches.
I need help myself, deleted my "Phone" system app, causing me to lose connectivity with my data plan. cant seem to restore it, and flashify nor twrp has been able to flash a custom recovery, or a backup, im at a loss.
Help? We seek the same thing.

Ok but how do I flash the stock recovery image. I can't use fastboot. ADB says I am unauthorized.
sent from a device using an app

Anyone have any other ideas?
I am at a complete loss. I am by no means a developer, but I do know my way around. I really think I have FUBAR'd this one.

Kind of stinks, I give up. Anyone want a bricked v410?
Sent from my Galaxy Tab 2 using Tapatalk