I unlocked eom and figured I could flash international right away with msmtool. It gave an error saying img doesn't match and stopped. Screen stays black and I get a USB error on pc. Any ideas to get me on usb again to flash stock tmo? Thanks
Not sure how to delete thread but i fixed it!
Related
I have a Motorola CLIQ on the blue screen of death that reads BOOTLOADER USB INIT... and that's it.
Is there ANYWAY for me to fix this? re-flash the phone, re-load android OS, something....????
just try every possible thing you just said,
flash shx firmware
you'll have to flash an shx firmware. look at ModMyMoto - Motorola CLIQ/DEXT - CLIQ & DEXT firmwares Superthread (sticky)
flash this fw w/ rsd lite:
Branding: T-Mobile US
Version: 1.3.18
Bootloader Version: 05.15
Requires RSD Lite 4.5.7.
I have almost the same problem, but mine stays on White Motorola logo.
I wiped my cliq using adb shell wipe all command and now I can't re-flash on RSD Lite because it says "Please wait for all-TCI ready, and try again..."
When executing a adb shell command it returns this error: - exec '/system/bin/sh' failed: No such file or directory (2) -
running adb devices returns:
List of devices attached
0391255714 device
Is there any way to access its internal storage and reflash?
I have tried reflashing the phone several times, it says it completes successfully - but always reboots in to this blue screen with bootloader usb init at the bottom.
any other suggestions?
Latest update: (and it's a bad one)
I downloaded tmo-morrison-viper-1.1.31-P3-rootedbythedude.shx file, flashed it using usb drivers 4.20 and rsdlite 4.5.7
It claimed it flashed successfully, but the phone never rebooted... just stayed on the blue screen with the bootloaded usb init on the bottom.
Now, I've tried to re-flash with either that same .shx file and it error's out. Then I thought maybe unrooting it would work so I tried tmo-morrison-viper-1.1.31-P3-supermonster-customer.shx and it error's out.
I originally tried tmo-morrison-viper-1.1.4-20091012-2014-cprintf-appsbl-P3-secure-supermonster-customer.shx, and it worked and flashed BEFORE today and BEFORE tmo-morrison-viper-1.1.31-P3-rootedbythedude.shx
At this point, the only thing that has changed is now whatever I try to flash, fail's immediately. It only power's on when the usb cable is inserted. I goes straight to the bluescreen with bootloader usb init on the bottom in white characters.
I'm pretty much STUMPED at this point.
Here is a screen shot of what RSDLITE shows when this cliq is connected. Anyone got any suggestions?
Maturz i am having the EXACT same problem. RSD is saying TCI ****, phone boots to the white moto logo, adb won't work. i have NO idea where to take this. The only menu i've seen that looked promising was the recovery menu which you reach by holding camera during boot. By holding(no stickykeys) ALT and hitting L you can see its menu. The options are to run an update.zip( I can't find a single file it will accept as signed/not fail executing), wipe, or restart. The wipe does not fix this issue. PLEASE tell me if you fix your device, I've got a mirror with a keyboard and its a serious bummer. This problem occurred while flashing a rom. RSD ****ed up. Some claim they can get the charging firmware to mount something ADB can talk to by plugging the phone into the wall and then switching to the computer quickly..but i haven't been able to get this to work.
i had this very same problem and i fixed it through rsd flashing the latest firmware. i lost root in the process but i don't have a brick anymore
moxiot said:
i had this very same problem and i fixed it through rsd flashing the latest firmware. i lost root in the process but i don't have a brick anymore
Click to expand...
Click to collapse
Which file did you flash to it? I'm stuck now - where it won't seem to accept any flashing now ... PLEASE HELP
OMG I sumwhat did it!
Turn ur phone off, than at the same time press power, star button & pound button that reboots and start as usual HOWEVER when u turn off the phone it goes back to blue screen! I figured this much maybe now I can reinstall android 2.0 hmmm! Email me [email protected] if u figured it out from there hop'e this help' ;0)
Cordellnj said:
Turn ur phone off, than at the same time press power, star button & pound button that reboots and start as usual HOWEVER when u turn off the phone it goes back to blue screen! I figured this much maybe now I can reinstall android 2.0 hmmm! Email me [email protected] if u figured it out from there hop'e this help' ;0)
Click to expand...
Click to collapse
Can you post the solution here?
HELPPPP
Flashed the original firmware with red light and it failed now my phone stays with a black screen but the keys light up :'(
Bummer!
my phone only turns on when i connect it to the charger and it boots to a Black screen with a blue bar at the bottom that reads "Bootloader USB Init" no motorola logo.
has anyone else ran into this? i had the logo before i flashed "tmo-morrison-viper-1.1.31-P3-supermonster-customer.shx"
Someone help me! this was supposed to be a xmas gift for my sister but now it feels like paper weight.
buddie024 said:
my phone only turns on when i connect it to the charger and it boots to a Black screen with a blue bar at the bottom that reads "Bootloader USB Init" no motorola logo.
has anyone else ran into this? i had the logo before i flashed "tmo-morrison-viper-1.1.31-P3-supermonster-customer.shx"
Click to expand...
Click to collapse
what exactly happened? why did you have to flash?
i am hoping i did not brick my phone, but i can not seem to get it working again, i have read through a few threads, and some of them seem to say that it is not bricked if you can enter the 3 color boot loader screen.
i have an AT&T fuze, i have flashed energy's roms many times and was just trying to flash the most recent cookie rom. about 79% through the flash i get a connection error and the progress stops and stays at 79% for a while before i try the recovery options, none of them worked.
I keep getting the same connection error. if i remove and reinsert the battery and power on, it takes me to the 3 color boot loader. at the bottom of the green part it says " upgrade ROM code error Please try again". in the white part it says serial, but changes to USB when I plug it in tho the computer.
i tried booting the rom from the SD card, but that didn't work either. I've tried with several different roms that i know i flashed successfully in the past, but those haven't worked either. when i tried to flash via the SD card i get a breif flash of the gray screen and a message that said "no rom image found" before returning to the bootloader screen.
After posting about this in another thread, someone suggested to try task 29.
I tried that followed all the instructions, and now when i boot up, it boots to a splash screen like it says, but i still get the same error when i try to flash from the sd and i still can not get a connection to the pc to flash. whenever i connect, the bootloader screen indicates a usb connection, but when i run the rom update utility i still get the connection error.
The thing that is even more confusing to me is that i was able to make the connection to the phone in order to run the task 29, but not for anything eles.
ALSO, one thing i noticed was that when a connection was made to the computer, the computer would make a sound indicaing a connection, but a couple of times i would get an indication in the bottom right corner that the drivers were not installed. maybe that is an issue that could be fixed.
if anyone can help or point me in the right direction i would appreciate it a lot.
I have tried to include as much info as needed here, but if more detailed info is needed, let me know
thanks in advance
keith
Long story short I messed up my i9020T while trying to apply the HSDPA hack (wouldn't get past Google boot logo, CWM couldn't mount partitions), and after a series of failed flashes I'm now at the point where stock 2.3.4 seems to be working fine, but I can't unlock the bootloader because it gets stuck after selecting the Yes prompt, and I can't properly enter Download mode to flash via ODIN (I don't get the yellow triangle, only part of the unlock-bootloader-prompt screen).
Do I have any options left? Any way to reflash completely using another method? Fastboot seems to work fine except for the inability to unlock the bootloader.
I'm at my wit's end, appreciate any help.
Try reinstalling the Samsung USB drivers. To get into download mode easily, hold down both volume keys and plug the phone into USB. It should go into download mode right away.
Run Odin as administrator and flash the stock images.
Thanks, but that didn't work either. Even the stock ROM and locked bootloader eventually failed, so something tells me there might have been a mechanical problem after all. Currently waiting for a Best Buy refurb replacement.
Hi guys, this is a friends Nexus S he bricked during an ICS update (official one). I can't get it to work at all. It boots up an android guy with a red triangle and a (!) coming out of his chest. The bootloader is locked (version I9020XXKL1). He's never tried to root beforee
Things I've tried:
Got ADB drivers working
'ADB factory reset oem unlock' gets me a dialog screen on the phone confirming the unlock, then when I confirm, I get: 'FAILED. remote erase: fail'. Tried with serial number (saw a random post mentioning that), but same result.
I tried flashing an IMG file through fastboot with a similar error. the device shows up in getstate and devices, but you can't write to it it seems.
Mentioned to someone at work and he said I should be able to get a stock RUU exe file and you just run the RUU. Similar to a 1 click odin fix, but...not. Cause I can't get into download mode. If I try to go into recovery mode from fast boot, that's when you see the dead android guy with the (!). If I just try and let it boot on its own..it just boot loops. Doesn't turn off/on, but never passes the 'Google' splash screen.
I've searched for the RUU files and can't find them anywhere, at least for a Nexus S. Am I missing something here? Not sure what else to try.
Thanks!
b0vine said:
Hi guys, this is a friends Nexus S he bricked during an ICS update (official one). I can't get it to work at all. It boots up an android guy with a red triangle and a (!) coming out of his chest. The bootloader is locked (version I9020XXKL1). He's never tried to root beforee
Things I've tried:
Got ADB drivers working
'ADB factory reset oem unlock' gets me a dialog screen on the phone confirming the unlock, then when I confirm, I get: 'FAILED. remote erase: fail'. Tried with serial number (saw a random post mentioning that), but same result.
I tried flashing an IMG file through fastboot with a similar error. the device shows up in getstate and devices, but you can't write to it it seems.
Mentioned to someone at work and he said I should be able to get a stock RUU exe file and you just run the RUU. Similar to a 1 click odin fix, but...not. Cause I can't get into download mode. If I try to go into recovery mode from fast boot, that's when you see the dead android guy with the (!). If I just try and let it boot on its own..it just boot loops. Doesn't turn off/on, but never passes the 'Google' splash screen.
I've searched for the RUU files and can't find them anywhere, at least for a Nexus S. Am I missing something here? Not sure what else to try.
Thanks!
Click to expand...
Click to collapse
Firstly is this still under warranty? Since its the offical ICS update. Just tell him to go to his provider and ask for a replacement since it was not the user's fault.
A few questions. Why is he receiving the ICS update now? If this was ages ago when ICS was first released, Google stopped ICS update for a weeks or so since there was some problems.
And if the warranty doesnt work. Id say root it and flash a Recovery.
http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/
It's a few months out of warranty, and no, TELUS won't replace it, he's already tried.
I also can't root it as mentioned. I get to this point in the guide
For Windows:
fastboot oem unlock
And get the ERASE:FAILED error once confirming the unloock.
I have a SM-G930FD Grey Market via Ebay to the US (UAE Version). I've been having some funny issues where it randomly changes the active SIM card on me. I thought maybe I should try flashing a new stock but during that process I discovered a weird issue that I can't get fixed. When I go to recovery mode the "installing update" screen comes up for a few seconds followed by a new screen that shows a warning sign with an exclamation point then a dead android with "x's" over it's eyes. The phone then goes to boot mode. Is this normal? If not, what do I do?
I should also note that the phone has been locking up - at least once a day.
hansgraff said:
I have a SM-G930FD Grey Market via Ebay to the US (UAE Version). I've been having some funny issues where it randomly changes the active SIM card on me. I thought maybe I should try flashing a new stock but during that process I discovered a weird issue that I can't get fixed. When I go to recovery mode the "installing update" screen comes up for a few seconds followed by a new screen that shows a warning sign with an exclamation point then a dead android with "x's" over it's eyes. The phone then goes to boot mode. Is this normal? If not, what do I do?
I should also note that the phone has been locking up - at least once a day.
Click to expand...
Click to collapse
Hi
No that is not normal.....
Can you get into download mode?.........
Just in case download an called PhoneInfo and make a refurbish check......
Thanks for your reply! Yes I can get to download mode and can connect to Odin. I flashed a stock rom but am still having the issue. After flashing sammobile stock the phone updated twice no issues.
Phonecheck says the phone is original....
I tried to push TWRP but it doesn't seem to load...
Any thoughts?
hansgraff said:
Thanks for your reply! Yes I can get to download mode and can connect to Odin. I flashed a stock rom but am still having the issue. After flashing sammobile stock the phone updated twice no issues.
Phonecheck says the phone is original....
I tried to push TWRP but it doesn't seem to load...
Any thoughts?
Click to expand...
Click to collapse
Flashed stock and same issue? no errors during flashing (odin)
At what point fails TWRP installation?
I'm going to try flashing TWRP once more this morning and will let you know.
I was able to get TWRP working and now am running Superman. Hopefully it will be stable. This still didn't fix the SIM card switching issue which is a huge bummer....