So I'm using myth tools to flash back to stock and when my device is in fastboot it begins flashing the firmware as usual, however when its like around 30% - 40% the screen flashes off and on for an instant, it then finishes flashing the firmware. However when I reboot the phone it boot loops. This happens with every version of stock firmware. Any one have any clues?
Related
Hello,
I have a Droid 4 that recently black-screened and wouldn't respond to any input, and upon rebooting won't get past the Motorola Logo boot screen.
It was previously rooted, but I had not flashed anything onto it, and I believe it was on Android 2.3.6 still.
The current state of affairs:
A normal boot shows the Motorola Dual Core Technology screen, as well as a thin multi-colored line along the bottom of the screen.
Boot Mode Selection Menu works fine, but booting into Recovery shows the Motorola screen indefinitely (without the thin line at the bottom)
AP Fastboot and BP SBF flash modes appear to work normally, and I am able to see the device in RSD Lite 6.0.
Steps I have taken:
I tried to fix the problem by flashing 9.8.2O-72_VZW-18 Blur_Version.98.72.18.XT894.Verizon.en.US from sbf.droid-developers.org/cdma_maserati/list.php The flash was successful, apart from not rebooting successfully. When I manually restarted into AP Fastboot, RSD said the flash passed successfully.
There has been no change in startup behavior since I flashed the new version. I still can't boot into normal phone operation or recovery.
Please help!
Regards,
RS
RestroomSounds said:
Hello,
I have a Droid 4 that recently black-screened and wouldn't respond to any input, and upon rebooting won't get past the Motorola Logo boot screen.
It was previously rooted, but I had not flashed anything onto it, and I believe it was on Android 2.3.6 still.
The current state of affairs:
A normal boot shows the Motorola Dual Core Technology screen, as well as a thin multi-colored line along the bottom of the screen.
Boot Mode Selection Menu works fine, but booting into Recovery shows the Motorola screen indefinitely (without the thin line at the bottom)
AP Fastboot and BP SBF flash modes appear to work normally, and I am able to see the device in RSD Lite 6.0.
Steps I have taken:
I tried to fix the problem by flashing 9.8.2O-72_VZW-18 Blur_Version.98.72.18.XT894.Verizon.en.US from sbf.droid-developers.org/cdma_maserati/list.php The flash was successful, apart from not rebooting successfully. When I manually restarted into AP Fastboot, RSD said the flash passed successfully.
There has been no change in startup behavior since I flashed the new version. I still can't boot into normal phone operation or recovery.
Please help!
Regards,
RS
Click to expand...
Click to collapse
It looks like you tried to flash the JB fastboot files. If you were on GB that may be your problem. I'm not for sure on this but I think the fastboot files will only flash over itself or the previous software version. Maybe try flashing the GB or ICS fastboot files and see what happens. Doesn't sound like it could make it worse.
kwyrt said:
It looks like you tried to flash the JB fastboot files. If you were on GB that may be your problem. I'm not for sure on this but I think the fastboot files will only flash over itself or the previous software version. Maybe try flashing the GB or ICS fastboot files and see what happens. Doesn't sound like it could make it worse.
Click to expand...
Click to collapse
Thanks for the suggestion. I tried the 6.5.1_167_DR4-1_M1-219, which didn't have any effect. I'll try the 6.5.1_167_DR4-1_M1-215 and see what happens.
You can flash same or higher than what your phone/device was....ie....if you were on GB you can flash the GB, ICS or JB fastboot files to stay at GB, update to ICS or update to JB. If you were on ICS you can fastboot the ICS or JB fastboot files to stay the same at ICS or update to JB.
If you are on JB or have flashed the JB fastboot files....you can only RSDlite the JB fastboot files.
I would reflash the JB fastboot files and then attempt to let the phone boot normally. If it boots normally, then reboot and try to enter Recovery.
Try booting into a Linux OS and connect the phone. Then use the Droid 4 ICS or JB utility. Boot the phone into fastboot ap mode,connect the phone to linux, and run ICS or JB Utility. It should work right away, I was getting the same thing a few days ago and the JB utility worked for me with Linux and not Windows.
Sent from my DROID4 using xda premium
Hi
I have an AT&T XT1058 with locked bootloader, on 4.4.4
I tried to rest it to factory, but it got stuck on 'Erasing...' (with the little droid) for more than an hour, so I reset it.
Since then it won't boot, only keep stuck on 'Erasing...'. I've tried reflashing it with ATT_XT1058_4.4.4-KXA21.12-L1.26_CFC_1FF both using RSD lite and manually using mfastboot, but no luck - the phone still boots to 'Erasing...' and sometimes after that to the recovery.
I didn't find anything in relevant threads. Does anyone have an idea?
Selecting 'Factory' in the bootloader seemed to fix it.
It is more comlicated than that
The phone does boot after selecting 'factory' in bootloader, but only once - turning the phone off and on again brings it back to its 'erasing...' state. Besides that the phone seems to not be able to charge the battery
mokagi said:
It is more comlicated than that
The phone does boot after selecting 'factory' in bootloader, but only once - turning the phone off and on again brings it back to its 'erasing...' state. Besides that the phone seems to not be able to charge the battery
Click to expand...
Click to collapse
Were you able to get this resolved? I have a xt1095 doing the same thing when I flash a stock recovery. Just shows the android guy and just stuck at erasing... When I flash TWRP it doesn't get stuck at the "erasing..." anymore but just boots straight into TWRP.
Sorry for the late response, I missed the notification on your message.
I wasn't able to fix it, returned it to motorola.
Hello,
I have a GT-N7000 which I am only able to access via download mode. Recovery mode does not work at all.
Odin 3.09 runs the following successfully:
1. Flashing a stock rom: N7000JPLSB_N7000OJPLSB_N7000XXLSO_HOME.tar.md5
2. Flashing a pit file: Q1_20110914_16GB.pit
3. Flashing a safe kernel: PhilZ-cwm6-JPLSB-UAE-4.89.4.tar.md5
These steps however have not solved the problem.
I have read that I need to flash a bootloader, but I don't know how to do that.
Any help would be highly appreciated.
GT2020 said:
Hello,
I have a GT-N7000 which I am only able to access via download mode. Recovery mode does not work at all.
Odin 3.09 runs the following successfully:
1. Flashing a stock rom: N7000JPLSB_N7000OJPLSB_N7000XXLSO_HOME.tar.md5
2. Flashing a pit file: Q1_20110914_16GB.pit
3. Flashing a safe kernel: PhilZ-cwm6-JPLSB-UAE-4.89.4.tar.md5
These steps however have not solved the problem.
I have read that I need to flash a bootloader, but I don't know how to do that.
Any help would be highly appreciated.
Click to expand...
Click to collapse
On a successful kernel flash, enter into recovery mode and flash raw kernel and its corresponding rom.
Unfortunately recovery does not work at all. The phone reboots when I attempt to enter recovery.
GT2020 said:
Unfortunately recovery does not work at all. The phone reboots when I attempt to enter recovery.
Click to expand...
Click to collapse
My phone has this thing where upon pressing the buttons for recovery, it will show the Samsung Galaxy Note screen twice before entering recovery. That means pressing the buttons until it finishes showing twice, or it will just reboots normally. Did you try it?
What I tried now was flashing the stock rom again. After Odin successfully flashed the rom, it went into a boot loop that lasted approximately 20 minutes, but I just let it loop without disturbing it. Eventually it stopped and switched itself off.
I tried to enter recovery and and it rebooted a few times as you mentioned, but eventually I now see the stock Recovery screen, but the Android is on his back with the red triangle on his chest.
I then performed a factory reset.
Phone reboots, I see the Samsung logo, I hear the jingle and then the phone switches off.
Edit:
Switch phone on: See message Android is upgrading. Reaches 33 of 73 apps and phone switches off.
Switch on again: Android is upgrading 1 of 41. Completes. Switches off.
Switch on again: See setup screen. Switches off.
Switch on again: Same thing.
Recovery still broken and can't setup phone as it switches itself off.
GT2020 said:
What I tried now was flashing the stock rom again. After Odin successfully flashed the rom, it went into a boot loop that lasted approximately 20 minutes, but I just let it loop without disturbing it. Eventually it stopped and switched itself off.
I tried to enter recovery and and it rebooted a few times as you mentioned, but eventually I now see the stock Recovery screen, but the Android is on his back with the red triangle on his chest.
I then performed a factory reset.
Phone reboots, I see the Samsung logo, I hear the jingle and then the phone switches off.
Edit:
Switch phone on: See message Android is upgrading. Reaches 33 of 73 apps and phone switches off.
Switch on again: Android is upgrading 1 of 41. Completes. Switches off.
Switch on again: See setup screen. Switches off.
Switch on again: Same thing.
Recovery still broken and can't setup phone as it switches itself off.
Click to expand...
Click to collapse
You need the stock recovery. Flash your rom in, reboot to stock recovery, then update with the corresponding Philz for your phone. If it works you should reboot and see philz recovery and your rom is unusable. Just flash raw kernel and any other rom after that
So all the random reboots were caused by a faulty battery.
I bought a new battery, followed steps 1,2 and 3 in my original post and my phone is working perfectly again.
Here's the deal, I have a sprout8 device (the Indonesian Nexian Journey One) running stock 6.0 with some xposed mods installed on it. Suddenly the device shuts down and when I try to boot it up it only goes halfway through the bootanimation when it shuts down again. I wasn't too worried as I thought it was just a conflicting system issue and I also thought it was time to re-flash fresh stock 6.0 to freshen up my phone anyway. So I went ahead and did it.
Here's where the problems start to show up, I had a hard time booting to recovery through the power + volume up combination. The phone suddenly shuts down on its own as it boots up. I tried it a few times and finally got to recovery. After that, as I flashed stock 6.0 the phone shut down again. I thought it was an issue with my recovery so I tried wiping everything through fastboot and re-flashed recovery through fastboot aswell. From there I tried again to flash stock 6.0 through recovery and again, the phone shut down. I tried a different ROM thinking it was a ROM issue but still got the same results.
After hours of trying to flash a ROM through recovery (retrying over and over as it suddenly shut down while flashing), I finally got a ROM installed. Then I rebooted my phone, but again it freezes halfway through the bootanimation (literally freezing the bootanimation) and refused to do anything. I took off the battery and booted up the phone countless tries trying to get it to boot up. When it finally booted up, I filled in all the Google startup credentials and finally got started on a fresh stock 6.0. However, I tried to restore my previous application data through Android's application recovery on startup but everytime the device installs a new application it would freeze up and shut down. This happened countless times. Then the phone, once again, shut down and could not start the ROM. It would freeze up on the bootanimation.
Then things started to get weird, when the phone turns on it should show the "Nexian" logo in all its glory before going to bootanimation. But here the screen gets all distorted and shows these weird horizontal (and sometimes vertical) lines. Nothing's wrong with my phone screen so I assume it is a system error. From here on, the phone refused to boot. It just shows the Nexian logo and restarts over and over. The same thing happens even after I re-flashed both my recovery and ROM. I even tried using SP Flash Tool to re-flash stock but still the same results.
Now, the device wouldn't even turn on. But when I connect it using USB to a Windows computer, it still gets detected through device manager as an ordinary MediaTek device.
I'm assuming now that it may be a problem with the /system parition where we install our ROMs in. The partition may be (partially) corrupt. Seeing as the device could still boot the ROM a few hours ago but freezing upon updates to the stated partition.
If you guys have any other ideas/solutions I'm all ears.
I was trying to flash a new rom couple days ago and I feel I did a mistake somewhere which led to an issue and I can't manually boot into recovery (I have tried reflashing recovery) when ever I try to boot into recovery or rom does it for Android updates it gets stuck in fastboot from here I can't turn on the phone, when ever I try to turn it on, it boots back into fastboot, the only way for me to actually get back into my device is by using a pc with fastboot boot recovery.img. It usually updates the rom and I can get back to my device from here. I've tried a couple of things but I'm not able to go to recovery without my pc. Suggest me some fixes that could possibly fix the phone
Thanks in advance