Having telecom NZ upgraded to 4.0.4 and try to upgrade to 4.1, I failed to update it, and now I couldn't flash back the ROM with message 7/20 in RSDLite, any idea?
same problem
I have same problem. I was on official ISC 4.0.4 in NZ upgraded over OTA a than I tried flasH JB, but flash it wasnt successful on cdt.bin step and now every time I turn on phone, it runs in fastboot mode flash failure (s) and I have to to do vol+ vol- and power and hit normal boot. Its really annoying. PLS HELP!
Insight appreciated
I have similar issues. The sequence of events to get to this state
Telecom XT phone bought with android 2.X
OTA update to 4.0.4
SCV7 Installed
Attempted flash to 4.1.2 leak
The upgrade failed, I tried flashing fxzs to return to a usable state, but this did not work (Via fastboot commands and RSD lite). The only functioning fxz I found was the AT&T version (I know cross flashing is bad but I was desperate, and figured it would fail too). I used this to re-implement a custom recovery and nandroid back to SCV7. The issues with flashing certain bits (cdt.bin and a few others) persist, as does the fastboot mode flash failure menu on boot.
I've attached my about page if it helps
Hi
Personal Sandwich said:
I have similar issues. The sequence of events to get to this state
Telecom XT phone bought with android 2.X
OTA update to 4.0.4
SCV7 Installed
Attempted flash to 4.1.2 leak
The upgrade failed, I tried flashing fxzs to return to a usable state, but this did not work (Via fastboot commands and RSD lite). The only functioning fxz I found was the AT&T version (I know cross flashing is bad but I was desperate, and figured it would fail too). I used this to re-implement a custom recovery and nandroid back to SCV7. The issues with flashing certain bits (cdt.bin and a few others) persist, as does the fastboot mode flash failure menu on boot.
I've attached my about page if it helps
Click to expand...
Click to collapse
I have the exact same problem except I missed the SCV7 step. At first I didn't think I could start it from fastboot, but I tried recover and it works.
I guess it isn't too bad having to start from flash fail menu, at least its still working.
Related
Hey guys,
I've been using this website as reference for years but never had an issue I hadn't already seen asked.
I've been looking for weeks for a solution to this and haven't found anything.
I tried to flash cm10.1 over my stock 4.1.2 and corrupted the system.
It was booting directly to AP Fastboot and showing an error about not calling the ROM properly.
I tried reflashing using RSD Light 5.7 but every time it tried to flash the system it said the phone returned failed.
So I upgraded RSD to v6.1 and tried again. This time the phone says it flashed properly but it freezes during the droid boot logo.
I've tried using the utility and it gives me the same results.
I can get into factory recovery and I've performed several hard resets. But the phone still freezes whenever it tries to load the system.
I'm using a Motorola Factory Cable on a high speed USB port.
Any ideas why I'm stuck in a soft brick that I can't flash out of?
ShiningRaven said:
Hey guys,
I've been using this website as reference for years but never had an issue I hadn't already seen asked.
I've been looking for weeks for a solution to this and haven't found anything.
I tried to flash cm10.1 over my stock 4.1.2 and corrupted the system.
It was booting directly to AP Fastboot and showing an error about not calling the ROM properly.
I tried reflashing using RSD Light 5.7 but every time it tried to flash the system it said the phone returned failed.
So I upgraded RSD to v6.1 and tried again. This time the phone says it flashed properly but it freezes during the droid boot logo.
I've tried using the utility and it gives me the same results.
I can get into factory recovery and I've performed several hard resets. But the phone still freezes whenever it tries to load the system.
I'm using a Motorola Factory Cable on a high speed USB port.
Any ideas why I'm stuck in a soft brick that I can't flash out of?
Click to expand...
Click to collapse
Format system via any of the custom recoveries before flashing your new ROM - this will wipe out any leftover problems completely & should let you start 100% fresh with a new ROM.
tzlot said:
Format system via any of the custom recoveries before flashing your new ROM - this will wipe out any leftover problems completely & should let you start 100% fresh with a new ROM.
Click to expand...
Click to collapse
I lost my root when I originally got stuck in fastboot. And I can't boot up the phone until I can get it fixed.
ShiningRaven said:
I lost my root when I originally got stuck in fastboot. And I can't boot up the phone until I can get it fixed.
Click to expand...
Click to collapse
Can you get back into fastboot now? If so
Use fastboot to flash a custom recovery (CWM, TWRP or OUDHS)
use the recovery to factory reset, wipe cache/dalvic, AND format system (sometimes in the advanced menu)
then flash rom of your choice.
If you can't get fastboot working you'll need smarter help than I can give you... but the format system step clears out all kinds of gremlins.
I can get into fast boot but I don't have an unlocked boot loader to flash anything custom.
ShiningRaven said:
I can get into fast boot but I don't have an unlocked boot loader to flash anything custom.[/QUOTE
If you can get into fastboot then you should be able to unlock b/l with this toolkit I used it and it worked for me you can also flash rom with it its in the orginial development thread
http://forum.xda-developers.com/showthread.php?t=2154995
Click to expand...
Click to collapse
ShiningRaven said:
So I upgraded RSD to v6.1 and tried again. This time the phone says it flashed properly but it freezes during the droid boot logo.
I've tried using the utility and it gives me the same results.
I can get into factory recovery and I've performed several hard resets. But the phone still freezes whenever it tries to load the system.
I'm using a Motorola Factory Cable on a high speed USB port.
Any ideas why I'm stuck in a soft brick that I can't flash out of?
Click to expand...
Click to collapse
Had the same problem after a fastboot via the utility. Try powering your phone down completely and leaving it off for about 5-10 min. This can be tricky with the hardware buttons so if you have access to TWRP that will help as it has a power off option. You might also try flashing again via the utility. I believe that's what I had to do, but the power down method is what a friend suggested based of his experience with the same exact problem you documented.
FIXED!!!
OK first I want to thank everybody who responded. I got tied up with work and kind of forgot about this project for a few days.
Repeated uses of the Utility and RSD both left me stuck with the phone freezing every time it tried to load the system into memory.
I had checked out the toolbox before but I didn't think I could do much from a locked bootloader.
After your suggestion jmcdonald I tried it again. It says my device isn't available to be unlocked so I tried downgrading back to ICS.
The toolbox says that it failed but it must have fixed something because the phone booted back up to android 4.1.2 stock!
So far I have bricked a lot of phones and learned a lot about ADB in the process of fixing them but I've never had one I was so certain was bricked permanently. But now it seems to be working fine, I'm scared to try rebooting in now.
Definatly going to unlock the bootloader pronto.
Thanks again jmcdonald!
Hello to all.
Here's the problem:
I installed KK 4.4.2 on my Xoom 3G (stingray) using bigPart TWRP. Everything works well except battery life - full charged battery goes to 0% in a day or two (in standbye mode).
Then I decided to roll-back to JB (or ICS) (eos-stingray-2.0 firmware). It flashes normally but device hangs on boot - when displaying Motorola's logo.
I can flash again to KK and it boots and works. But I finally decided to have my old firmware installed on Xoom.
Can anyone help me to flash correctly the device and make it boot to OS?
BR, akadimka
akadimka said:
Hello to all.
Here's the problem:
I installed KK 4.4.2 on my Xoom 3G (stingray) using bigPart TWRP. Everything works well except battery life - full charged battery goes to 0% in a day or two (in standbye mode).
Then I decided to roll-back to JB (or ICS) (eos-stingray-2.0 firmware). It flashes normally but device hangs on boot - when displaying Motorola's logo.
I can flash again to KK and it boots and works. But I finally decided to have my old firmware installed on Xoom.
Can anyone help me to flash correctly the device and make it boot to OS?
BR, akadimka
Click to expand...
Click to collapse
I dont think there ia a procedure to roll back from Bigpart.
The only way is , to reflash the original firmware of your device - root - instal CWM etc
mermigas said:
I dont think there ia a procedure to roll back from Bigpart.
The only way is , to reflash the original firmware of your device - root - instal CWM etc
Click to expand...
Click to collapse
Thanx for the answer.
Here's what I did:
1. Flashed recovery to TWRP 2.6.3.0 (not bigPart)
2. Flashed Xoom to eos-stingray_cdma-2.0.0.zip
3. Rebooted Xoom -> now I passed the Moto's logo but hanged on booting OS itself - EOS logo spinning round and round and nothing happens. Look like there's smth more need for OS to boot. But what exactly?
How now pass this issue?
Please help me!
BTW, tried to flash original ROM - error during flashing via recovery.
akadimka said:
Thanx for the answer.
Here's what I did:
1. Flashed recovery to TWRP 2.6.3.0 (not bigPart)
2. Flashed Xoom to eos-stingray_cdma-2.0.0.zip
3. Rebooted Xoom -> now I passed the Moto's logo but hanged on booting OS itself - EOS logo spinning round and round and nothing happens. Look like there's smth more need for OS to boot. But what exactly?
How now pass this issue?
Please help me!
BTW, tried to flash original ROM - error during flashing via recovery.
Click to expand...
Click to collapse
Use fastboot method
http://forum.xda-developers.com/showthread.php?t=1049485
mermigas said:
Use fastboot method
http://forum.xda-developers.com/showthread.php?t=1049485
Click to expand...
Click to collapse
Did it. Just after UNLOCK process via fastboot Xoom booted to OS normally. So no flash to stock firmware required.
BIG thanx for your help!
Hi I'm in a similar situation, the process that took at the actual status is the same as your.
Now I cannot flash any img, I receive writing 'system'... FAILED (command write failed (Unknown error)) also after flashing with RSD stock rom.
I had opened a thread http://forum.xda-developers.com/showthread.php?t=2611538 this morning but without any luck noone replied.
Thanks
Hi,
I've been searching the web for a few days and tried many things, but so far I haven't been able to fix my Moto G.
My device:
Moto G (XT1032)
DE distribution
single-sim 8GB variant
Stock firmware was Blur_Version.14.71.8.falcon_umts.O2.en.DE or Blur_Version.14.91.11.falcon_umts.O2.en.DE (not sure)
What preceded the problem:
Something like a week ago I turned on my Moto G for the first time, checked for updates to KitKat but no updates were found
I forced checkin several times, rebooted the device, still no updates found.
Updates were available on the web for several weeks, so I thought I would update manually.
I unlocked bootloader (didn't know I didn't have to)
Downloaded KitKat rom for a single-sim variant from o2 DE distribution
Flashed firmware using motorola version of fastboot (didn't forget to clear the cache and userdata)
All went fine and I was able to boot to KitKat
When it happened:
I was tinkering with developer options, probably switched runtime to ART (not sure)
I rebooted the device (manually or when switching runtime)
Device stuck in a bootloop
What doesn't work:
Stock recovery (bootloop, 4.3 and 4.4 firmware)
CWM recovery (bootloop, both with motoboot.img for 4.3 and 4.4)
TWRP recovery (splashscreen flashing, both with motoboot.img for 4.3 and 4.4)
CM 11 (bootloop)
What works:
Philz recovery (http://forum.xda-developers.com/showthread.php?t=2639583, when this recovery is flashed, device boots straight into recovery)
ADB (in recovery)
What I've tried:
Flashing many, many firmwares. Triple checked if I didn't miss anything.
Factory resets, partition formatting (In philz recovery).
Rooting the phone
Checked whether eMMC chip is corrupted through ADB shell (dmesg | grep mmc0), seemed OK, no error messages (http://forum.xda-developers.com/showthread.php?t=1284196)
Using 4.3 motoboot.img with cyanogenmod and recoveries that doesn't work
Flash stock firmware and install OTA 4.4 update in philz recovery (seemed promisingly, took longer than flashing full firmware)
Where I may have had screwed up:
- After few initial attempts to fix my phone failed, I tried corrupting the bootloader to get to download mode as suggested here http://forum.xda-developers.com/showthread.php?t=2623587 and correct it.
I would be glad for any idea C'mon, you are some smart guys, we can do it!
Try to flash stock 4.4 firmware, do not flash any recovery after flashing the stock 4.4 and see what happens
I've experienced something like that, and after reflashing the stock many times i fixed it
sounds like my problem exactly. what did you do, return the phone?
how does flashing stock repeatedly help? which stock? which method (does it matter if you do it from fastboot or in philz or some other way?)
I have the same problem, could u solve this? plsssss HELP MEEEEE
FINAL EDIT: FIXED!!! Sparsechunk files 1,2and 3 have to match the exact name with the firmware folder sparsechunk files.
I did not notice that my firmware sparsechunk files ended in .0 .1 .2 and not 1 2 3 like the tutorial had listed, so I was fastbooting the wrong sparsechunk command. That was the final fix that finally worked for me.
Original post:
SHORT VERSION:
My god this has been one crazy root journey.
I have done absolutely EVERYTHING I could pull up on google to fix my phone, and what seemed to be the final piece to the puzzle, still has not fixed anything.
My phone is bricked, and i would really appreciate help at this point.
The current problem:
When I turn on my phone, it vibrates, and displays the WARNING BOOT LOADER UNLOCKED screen, and stays there forever.
I can access my boot loader, and recovery, but I dont know what to do at this point.
I tried a quick flash stock recovery kit kat with moto tool AIO, and it didnt help.
Any ideas?
LONG VERSION (backround info may help to understand the current issue)
Now, if you want to know what began all of this, continue reading, otherwise the above is my current issue.
After successfully unlocking and rooting my phone
I downloaded SWITCHME, an app that lets you create multible users on the phone. the instructions say that you can use a sub account to test and mess around with anything because you can simply go back to the admin account that has everything untouched.
That was a lie.
1.I deleted .setup, along with a few other things THAT WHERE NOT FLAGGED AS IMPORTANT, assuming the phone would still work. and my phone went bonkers, displaying this infinite message: UNFORTUNATELY, SETUP HAS STOPPED. It was impossible to use the phone, and I could only access bootloader.
2.After endless googling, driver downloading, xda mod installing, I managed to set up my boot loader to do the guide restore stock firmware:http://forum.xda-developers.com/showthread.php?t=2542219
Sadly, I flashed the wrong model number package, I was flashing x35, when I later discovered that my phone is x45.
Flashing the x35 firmware bricked my phone further, to where it would "fail to boot up" and would only display bootloader over and over after attempting to turn the phone on.
3. Simple, I realized I flashed the wrong thing, so I downloaded the x45 firmware from the firmware teem on this website, flashed all of the commands, and bam, the phone starts up with the boot loader warning, and DOES NOT get stuck in the previous boot loader issue I had.
But now the phone wont get past that warning screen so... now im pissed.
Please, if anyone can help me I would greatly appreciate it, Im so close to getting my phone back...
EDIT 2: Looks like the phone wont stay shut down, I realized that if I dont open up boot loader, it will turn itself on and display the warning message.
EDIT:
The stuffs I have, ready to try anything:
CWM touch mod
Moto Tool AIO
Minimal ADB and Fast boot
RETUS x1045 factory firmware
All directories, folders, cmd commands are set up and working properly between all of the programs.
The phone appears to be responding to all cmd commands properly.
I also have the windows one touch super boot root method. (he superboot-windows.bat )
Im afraid to try anything major after freshly flashing the x45 firmware that seemed to bring me one step closer without the help of someone else.
I restored stock to my phone using this link yesturday http://www.ibtimes.co.uk/how-restore-motorola-moto-g-stock-firmware-1447290
it may work for you
I have almost the same problem as if the fastboot not install anything despite not display errors
great that you got it done.
maybe my few cents about my "bricking" story. (xt1032 moto g)
yesterday i wanted to change the rom from cm11 nightly to another custom rom like ehndroix/carbonrom...
first i thought that will be done in a few mins, after having already flashed a custom rom.
then the story began, getting adb work, but, 2weeks ago everything was setup and went fine. dunno why my laptop lost the "drivers".
thats the link which solved that problem: tinyurl . com / kgffjh4 [sorry cant post links outside of xda yet, spam protection]
so after a few hours of getting that fixed i, i began flashing.
suddently i got stuck in bootscreen (ehndroix logo for example)...
then i wanted to go back with my previous backup made internaly of clockworkmod. though i couldnt restore my backup because there was an error message while restoring /data of my backup
also when restoring to factory/wipe in cwm there was that error message about clouldnt "touch" /data, i dont remember the message exactly.
after thinking i bricked everything, i though lets wipe my internal sdcard, maybe that causes the /data error.
then i restarted the device and went for a shower... after 15min i came back and my device was "started".
now i dont know that exactly helped, maybe wiping all data on my phone, or just letting my device boot for a "long" time...
so, thats my yesterdays brick story.
do a factory reset if the bootloader has that option.. otherwise install or run/boot a custom revovery, then either
try the factory reset option there and reboot or..
wipe everything and install a rom
Ok try this, I'm was a victim too:
Relock and unlock bootloader
Download and flash latest Philz
From there format everything...EVERY PARTITION...switch F2FS
After switching wipe every partition again
Select and execute the other 3 wiping option ie., Clean to install new ROM and the other 2 (I can't remember now)
Do this all over again via TWRP too
Now, this is important, don't use the mfastboot for restoring stock...use the one provided by Google for its Android SDK
Flash the stock images
Flash the Moto Razr boot animation and not the one for Moto G to remove the warning sign
I'm 99.99% sure your phone will boot properly
After the phone boots, reflash the Moto G bootanimation
Good Luck!
ngr.hd said:
Ok try this, I'm was a victim too:
Relock and unlock bootloader
Download and flash latest Philz
From there format everything...EVERY PARTITION...switch F2FS
After switching wipe every partition again
Select and execute the other 3 wiping option ie., Clean to install new ROM and the other 2 (I can't remember now)
Do this all over again via TWRP too
Now, this is important, don't use the mfastboot for restoring stock...use the one provided by Google for its Android SDK
Flash the stock images
Flash the Moto Razr boot animation and not the one for Moto G to remove the warning sign
I'm 99.99% sure your phone will boot properly
After the phone boots, reflash the Moto G bootanimation
Good Luck!
Click to expand...
Click to collapse
I try to flash any recovery but after entering I get an android and says no commands, and installation does not throw errors
angelgzg said:
I try to flash any recovery but after entering I get an android and says no commands, and installation does not throw errors
Click to expand...
Click to collapse
You're still in stock recovery.
Use fastboot flash recovery xyz.zip to flash philz recovery
Use this when you're in bootloader mode.
ngr.hd said:
You're still in stock recovery.
Use fastboot flash recovery xyz.zip to flash philz recovery
Use this when you're in bootloader mode.
Click to expand...
Click to collapse
I flash the recovery but rebooted into recovery, the android keeps popping up (no commands)
FINAL EDIT: FIXED!!! Sparsechunk files 1,2and 3 have to match the exact name with the firmware folder sparsechunk files.
I did not notice that my firmware sparsechunk files ended in .0 .1 .2 and not 1 2 3 like the tutorial had listed, so I was fastbooting the wrong sparsechunk command. That was the final fix that finally worked for me.
Sorry I'm traveling a d couldnt update thread fast enough.
Hi guys,
I have a Moto G XT1039 (peregrine) 4.4.4
I unlocked bootloader, flashed Clockwork recovery and rooted.
Tried to flash Cyanogen but failed so went back to 4.4.4 and after updating Motorola Update Services tried to install 5.1 but failed again. Tried reflashing stock firmware and recovery but it still failed to update to 5.1. Maybe I got the wrong stock firmware, EU as opposed to GB...
Anyway, tried to flash 5.1 with XT1039_PEREGRINE_RETGB_5.1_LPB23.13-17_cid7_CFC.xml.zip using the following method http://forum.xda-developers.com/showthread.php?t=2542219
All looked good but after reboot it was stuck on Warning Bootloader Unlocked screen.
I'm now back in fastboot screen and tried again to use the above method but this time for XT1039_RET-GB-SS_4.4.4_KXB21.14-L1.56-1_cid7_CFC_1FF.xml.zip as this appears to be the correct firmware for my phone.
But in cmd I keep getting 'mfastboot' is not recognized as an internal or external command, operable program or batch file.
What can I do to get my phone working again?
Thanks in advance
Just realised I forgot to get the mfastboot... will try again.
Repeated the steps but with the 4.4.4 zip. It looked like a fail at first (had a dead green dalek with an exclamation mark in a red triangle on the screen) but after some waiting it started showing some signs of life and eventually booted up. The only problem is it has like a shockwave line constantly traveling down the screen. Any ideas why and how to fix it?
Repeated the flashing process once more with XT1039_RET-GB-SS_4.4.4_KXB21.14-L1.56-1_cid7_CFC_1FF.xml.zip but this time added mfastboot oem lock begin in front of other commands.
Didn't solve the line accross the screen but was able to download and install the 5.1 through the official channel.
All sorted now.
Was good talking to self
Over and out