Bootloop - Legend General

Hi
I have an HTC Legend, but it's so buged
When i try to turn it on, it has to be connected to a cable, or else it goes into bootloop.
I've tried to make a factory reset, tried to install a different RUU, tried to downgrade it, but the adb shows no devices.
I've run out of ideas, so please help me

Somehow I managed to get the same issue. It goes into bootloop unless it's connected to a pc... I already went back to the stock 2.2 rom and deleted everything but nothing changed.
Funny thing is that after I got this problem I first installed the old 1.31 rom and that one worked without the usb cable. The 2.05 to. But as soon as I installed the 3.14 it started again with the bootloop thing...
Did you find any solutions?

Ok, after installing the stock rom I noticed that the usb is not working so I just needed to unbrick the phone and that solved a problem.
(I just did not think about that before because usb was still working when I installed cm7 but the bootloop problem was already there.)

CrWEE said:
Ok, after installing the stock rom I noticed that the usb is not working so I just needed to unbrick the phone and that solved a problem.
(I just did not think about that before because usb was still working when I installed cm7 but the bootloop problem was already there.)
Click to expand...
Click to collapse
What exactly means unbricking the phone?
I got simillar problems: since CM7 final I have bootloops when my phone isn't connected to power. Also I can't mount the sd card from a computer (when I press the button on the phone it works for like 5seconds and then unmounts again).
I already tried downgrading again to CM7 RC4 and other versions(I always wiped before), but the problem persists. Also upgrading to another radio version didn't work .

virus54 said:
I have this problem too
but i found one way to stop this rebot loop util u reboot your phone again...
enter into recovery mode and via adb write the command
adb devices
Click to expand...
Click to collapse
now press volume up and power button(when you see black screen with phone)
press on reboot system now and it will work for you for one time
each reboot you have to follow those steps
Click to expand...
Click to collapse
after this do a usb brick to use your usb http://android.modaco.com/content/h...com/309961/usb-brick-rickrolled-b0rked-fixed/

I had exactly the same problem, the USB unbrick linked to above solved the problem. If you need the image hex edited for you give me a shout

Related

[Q] Bricked Defy and not recognized by my USB

Guys,
First of all, hello to all! So, I followed a tutorial to install Froyo on my Defy. Now I'm stuck with my phone trying to boot as soon as i put the battery on, but it never makes it past the "M". I can get into recovery. I wiped data, cache and tried to install the "update.zip" but it aborts saying "signature verification failed." I have the boot file (that was the next step) to install using RSDlite 4.9 but the phone is not even recognized any of my USB ports. Any ideas? Thanks to all in advanced.
press volumn up buton and power button on boot , once you saw the backlit is on , release the button , you will see the rsd litle showing your usb .
dont worry . i think it is your first time to use RSD only
yea i been through that ( doesnt work on vista )
you need to install rsd lite and 2.51 UK Firmware ( no usa )
google it and you will find it or on this forum
install usb driver from motorola webiste
install rsd lite
put uk firmware in ... C drive/ program files / motorola / rsd lite
install driver
If your phone is stuck on " M " then pull battery out
turn on and quicky press power + vol up ( i think ) before M even appear
wait till it say your boot loader and your battery
plug phone in
start rsd lite
on ... look up your uk firmware that you you recently put in rsd lite folder
then you should see your phone connected on the 1 slot
then hit start or something and wait it out .
Thanks guys! But I've been messing around with this thing for so long, I drained the battery. I had to run it up to the local phone store to get it charged. I'll pick it up in a couple of hours and give your advice a try.
Hey guys! it worked! I'm up and running. Now, anyone has a link to bypass this Welcome to Motoblur screen. Is there a Custom Froyo or Gingerbread Rom out there without Motoblur?
Alright... I'm up and running, but no camera!!! Heck, it was a learning experience. I guess I'll go back to 2.1 now. LOL
So the Chinese ROM was rooted. I installed Clockworkmod and restored from the backup i had made of the original 2.1 OS. I'm back to a rebooting phone not making it past the "M" I went back to RSDlite and realized the boot file said 2.2 only. Can anyone assist me finding the right one to go back to original. I haven't been able to find a thread about reverting back to original.
The more I read, the smarter I get seems like the only thing I'm missing here is the SBF file for my original T-Mobile OS. I'm looking at the motorola website, but I can't find it. Can anyone point me to it? Thanks all! Oh yeah, this is the first android phone i mess with so my apologies.
There is no us sbf file. You have to flash a uk version and restore 3g with the posted fix. You can find the links to available sbf files on this forum. They are not available thru moto's site.
Sent from my ME525 using Tapatalk
Just to make sure I got it right. After using clockworkmod to restore to my factory backup, I need to use the UK sbf to be able to boot to it. Correct?
I found the sbf for Central Europe with no Motoblur. Does anyone know of any issues with it?
well the only way to fix this if you previously backed up your rom/files with recovery ( good thing i did this ). If not then you have to live with what you got.
I backed up my original firmware using clockworkmod. I flashed to the Chinese 2.2 but my camera didn't work. Since the camera is important to me, the Chinese Froyo was a deal breaker. I installed clockworkmod again and "recovered" from my original backup but now my defy won't boot. Did I miss a step?
Your data from the backup may cause issues when rolling backwards. Install an eclair sbf, then restore. That worked for me.
On another note there is a fix for the camera. Check the forums.
Sent from my ME525 using Tapatalk
Bricked Defy and not recognized by my USB
I also bricked my phone when going back to stock from cm7. My phone is able to go into boot loader. But it is not recognized by my desktop PC/RSDlite. I tried in linux with SBF_Flash. I tried with my laptop also. no luck . anyone please help me!
arulshoponline said:
I also bricked my phone when going back to stock from cm7. My phone is able to go into boot loader. But it is not recognized by my desktop PC/RSDlite. I tried in linux with SBF_Flash. I tried with my laptop also. no luck . anyone please help me!
Click to expand...
Click to collapse
Just try and install the Motorola Drivers in your desktop and open RSDLite and press 'show devices' button. It will surely show the details of your phone.
Then point RSDLite to the stock SBF and flash away.
kvigneshkrish said:
Just try and install the Motorola Drivers in your desktop and open RSDLite and press 'show devices' button. It will surely show the details of your phone.
Then point RSDLite to the stock SBF and flash away.
Click to expand...
Click to collapse
Thanks! Vignesh. But i have drivers installed. Tried uninstalling and reinstalling drivers. But did not help
Edit:
I missed to mention. My defy did not connect to desktop even before bricking.
arulshoponline said:
Thanks! Vignesh. But i have drivers installed. Tried uninstalling and reinstalling drivers. But did not help
Edit:
I missed to mention. My defy did not connect to desktop even before bricking.
Click to expand...
Click to collapse
If you hear the USB plugged in sound in your Pc, it's a messed up driver installation. If you don't hear the sound, it can be a bad cable, or a faulty microusb port (assuming that your pc usb works fine). Try once in a different pc and with a different microusb cable.
nsm1234 said:
If you hear the USB plugged in sound in your Pc, it's a messed up driver installation. If you don't hear the sound, it can be a bad cable, or a faulty microusb port (assuming that your pc usb works fine). Try once in a different pc and with a different microusb cable.
Click to expand...
Click to collapse
I do not hear any sound from desktop/laptop.
I think I stuck in boot loop. When I try to power on the phone, it just shows CM7 boot logo for few seconds then restarts again shows the boot logo... this happens continually. When I try to enter into recovery, it does not go to CWM recovery instead it goes to stock recovery. I am still able to enter into boot loader. In boot loader, it says battery OK connect USB to program. When I connect USB, it is recognized by phone and says transfer mode: USB. But my PC does not shows up the phone.
I tried re-installing drivers and RSDlite many times but no luck. But I have nandroid backup of CM7. Is there any possibilities to enter into CWM recovery?
Any help is appreciated.
Edit:
I tried even different USB cables and PCs also.

I think i just bricked

i think i just bricked my phone
i downloaded the RC2 rom, I have the bootstrap recovery and CWM and the unknown sourses app.
i was following your instructions on the dev release on how to install the rom
I downloaded the rom, put in on my sdcard i checked debugging usb
and then i hit the recovery bootstrap recovery button then the normal one ...
when it boots again i get critical error: CC00
DBAD
then another scren shows up with: Bootloader
09.12
Err:A5,70, 39,00,21
and i on the same screen it says: Battery: OK
OK to program
Connect USB
Data Cable
whe i conect the cable its says tranfermode: on
i dont know what to do at this point is there anything i could do to fix this?
I already tried yanking the battery out SDcard and put back in i just go back to the same screen
slowcurve said:
i think i just bricked my phone
i downloaded the RC2 rom, I have the bootstrap recovery and CWM and the unknown sourses app.
i was following your instructions on the dev release on how to install the rom
I downloaded the rom, put in on my sdcard i checked debugging usb
and then i hit the recovery bootstrap recovery button then the normal one ...
when it boots again i get critical error: CC00
DBAD
then another scren shows up with: Bootloader
09.12
Err:A5,70, 39,00,21
and i on the same screen it says: Battery: OK
OK to program
Connect USB
Data Cable
whe i conect the cable its says tranfermode: on
i dont know what to do at this point is there anything i could do to fix this?
I already tried yanking the battery out SDcard and put back in i just go back to the same screen
Click to expand...
Click to collapse
I just replied to your email, you efused!
This is exactly what happened to me when I bricked my gf's first bravo.
Good news is sbf and its fixed. You wont even lose any data.
IDK how this happens, seems it has happened twice now, there must be a specific change made before bootstraping that causes the check.
Either way the code group that is problematic is in the sbf, flash it and your good.
you will need to reroot, rerun nonmarket apps enabler, and re-bootstrap recovery, then reboto recovery and flash rc2 and you will be fine.
sorry for the spam... i panic'd..
i have the rsd lite i searched for sbf's and a whole bunch came up mind pointing which one i should use.
Edit: Its fixed thank you bando, you own half of my soul

[Q] Please Help!! Flashed wrong version of software!

Hi guys. I had a 32gb G2 and i was able to root it, upgrade it to 4.4 and use it without a hitch.
Today i got another one (16gb version) and flashed a kitkat rom i had around without stopping to check if it was 16 or 32gb (i forgot they had this difference). Well, now i got phone that i cannot use (im stuck at the SIM card PIN). What happens is that the screen is erratic. i click 2 and it registers 7...i click 5 and it selects simultaneously 123 and so on. basically i cannot pass this screen to enable all the good stuff.
Is there any way i can solve this?
I have a LG G802.
mechlord said:
Hi guys. I had a 32gb G2 and i was able to root it, upgrade it to 4.4 and use it without a hitch.
Today i got another one (16gb version) and flashed a kitkat rom i had around without stopping to check if it was 16 or 32gb (i forgot they had this difference). Well, now i got phone that i cannot use (im stuck at the SIM card PIN). What happens is that the screen is erratic. i click 2 and it registers 7...i click 5 and it selects simultaneously 123 and so on. basically i cannot pass this screen to enable all the good stuff.
Is there any way i can solve this?
I have a LG G802.
Click to expand...
Click to collapse
Boot without SIM card, connect to USB and transfer correct ROM. Boot into recovery, flash proper ROM. If you can't boot without SIM card you can probably use adb push to just push the ROM onto the sdcard and then reboot to recovery + flash.
Agret said:
Boot without SIM card, connect to USB and transfer correct ROM. Boot into recovery, flash proper ROM. If you can't boot without SIM card you can probably use adb push to just push the ROM onto the sdcard and then reboot to recovery + flash.
Click to expand...
Click to collapse
Ok. will implement & report
My problems just keep getting worse.
Since i wanted to go full stock i ended up downloading a kdz file a nd followed the tutorial on http://unbrick.itcse.com/unbrick-soft-bricked-lg-g2/
well...that didnt work. the process initiated and somewhere along the way the app stopped, and the only thing i could undestand was a "EMERGENCY something". After like 1hr with nothing happening, i unplugged the phone and got some corrupted partitions.
I then turned to the tutorial on http://forum.xda-developers.com/showthread.php?t=2582142 ...but damn! i cant reboot properly. now all the phone does is boot up to the lg logo and nothing else happens. windows doesnt detect it, linux doesnt detect it and adb doesnot detect it. am actually crying now....IS THERE ANYTHING I CAN DO TO SOLVE THIS?....im kinda desperate here. This is a brand new phone!
mechlord said:
My problems just keep getting worse.
Since i wanted to go full stock i ended up downloading a kdz file a nd followed the tutorial on http://unbrick.itcse.com/unbrick-soft-bricked-lg-g2/
well...that didnt work. the process initiated and somewhere along the way the app stopped, and the only thing i could undestand was a "EMERGENCY something". After like 1hr with nothing happening, i unplugged the phone and got some corrupted partitions.
I then turned to the tutorial on http://forum.xda-developers.com/showthread.php?t=2582142 ...but damn! i cant reboot properly. now all the phone does is boot up to the lg logo and nothing else happens. windows doesnt detect it, linux doesnt detect it and adb doesnot detect it. am actually crying now....IS THERE ANYTHING I CAN DO TO SOLVE THIS?....im kinda desperate here. This is a brand new phone!
Click to expand...
Click to collapse
maybe i could try to mess with the partitions and this time try to install some twrp that actually works? the one in the last tutorial doesnt seem to work on my 16gb model.

Stuck in rescue mode after tried flashing stock firmware

Good evening! I hope you can help me.
I flashed LineageOS 14.1, but I wanted to go back to EMUI. I made all the wipes and tried to flash different stock firmwares through a forced update (volume buttons + power button), but it never worked. At that point, I read about a guy in this forum who suggested to create a flashable zip with Huawei Update Extractor: I followed the suggestion and tried to flash it with TWRP. No error was given, but when I tried to restart, TWRP told me I had no OS installed. I thought it was strange, so I tried to restart anyway. That's when I got in rescue mode. I can't get into the recovery and I can't use fastboot. What rescue mode shows me is:
RESCUE MODE
Attention!
Please update system again
Update User Guide:
*link*
*android avatar*
Error!
Func NO: 10 (boot image)
Error NO: 2 (load failed!)
Pressing the three buttons, I'm able to force an update. The problem is I can't find a firmware that doesn't get rejected. With Lollipop firmwares, it starts to install, but it fails at 12%. With Marshmallow ones, the installation process doesn't even start.
What can I do to make it work again? I'm very sad because this phone was gifted to me a couple of days ago and I already messed it up. I don't even know how to turn it off.
What can I do to get in fastboot mode? At that point, what should I do to flash the stock firmware? Or maybe do I need to find the first stock firmware ever installed into this phone to make the forced update work?
Please, I need help. Thank you in advance!
P.S. The phone's model is ALE-L21. I live in Italy, so I assume it's a European version.
Did you managed to fix this?
Jhon_Locke said:
Did you managed to fix this?
Click to expand...
Click to collapse
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㄰㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!
ErikChimello said:
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㄰㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!
Click to expand...
Click to collapse
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).
Jhon_Locke said:
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).
Click to expand...
Click to collapse
No, it doesn't show anything if I write that command...
I guess mine won't ever boot into the rom because it seems like there's no system installed. I made some researches and found out there are some softwares that let you reflash the partitions IF the phone is recognized as "HUAWEI USB COM 1.0". I'm still trying to figure out how to do it correctly though. I feel like if I do something wrong, then my phone won't probably turn on again.
In your case, you should be able to flash a custom rom without any issue. You just have to be very careful and inform you as much as you can: I don't want your phone to end up like mine?. Anyway, it seems pretty hard to go back to the stock rom, so think about it before you flash a custom rom. Also, make a Nandroid Backup is very important.

xt1641 LATAM Hard Brick Alone

Hi Everyone!
I have an XT1641, which previously had a charging pin problem.
At the Last week, it started to reboot only many times until it suddenly shut down and didn't light anymore.
When plugged into a charger, the white light flickered.
Since I thought it was still a charging pin problem, make the change.
The cellphone works seemed to restart, but it continues with the same problem.
Sometimes the bootloader works ( Power + Vol -) and sometimes No.
I already tried everything. Install ROM STOCK, I made it blankflash (none worked "waiting for firehose to get ready" ).
It seems to be a firmware or similar problem, but I can't find the solution.
Previously, you never had a custom ROM installed, or root, or anything; at this cellphone
Thank you!
PD: SORRY FOR MY ENGLISH
How did you try for installing stock rom? Check usb drivers installed in your pc
przvlj said:
How did you try for installing stock rom? Check usb drivers installed in your pc
Click to expand...
Click to collapse
By Fast Boot (when it worked).
Now, after a week of turning it off, the cell phone turned on again without problems.

Categories

Resources