I have an HD2 Leo running Cyanogen mod 7 by MDJ. I recently was updating my Netflix app and had to change the Build.Prop so I could do so. Now my phone is just stuck on the boot screen and isnt doin anything . . . . Ive done this many time before but maybe I did something wrong this time . . ?
BRICK ? Tell me it isnt so. What should I do ?
Hold Vol- and start your phone. if you're in the bootloader (colored screen), it isn't bricked.
You could "Task29" your phone, reinstall MagLdr, and so on.
i recommend you to do a backup from your SD card.
jcnbama1983 said:
I have an HD2 Leo running Cyanogen mod 7 by MDJ. I recently was updating my Netflix app and had to change the Build.Prop so I could do so. Now my phone is just stuck on the boot screen and isnt doin anything . . . . Ive done this many time before but maybe I did something wrong this time . . ?
BRICK ? Tell me it isnt so. What should I do ?
Click to expand...
Click to collapse
a messed up build.prop can cause bootloops, you can extract the orig. build.prop from your rom cwm zip and push it via adb or just flash your mdj (quite old ^^) rom over your current again.
people need to learn the definition of bricked
your phone is not bricked, bricked would indicate it doesnt even power up when you turn the phone one, your issue issue is a messed up rom, just reflash it again
So thanks for all the info. The worst part of this. I can not get my phone to connect to the PC via bootloader mode. It keeps saying the devica has malfunctioned or is unrecognized. I must have tried EVERYTHING! Im using Windows 7. Obviously it worked before thats how I flashed it in the first place.
Any thoughts on a way to overcome this?
Yeah I've really been working on trying to get Windows 7 to recognize the phone. I know this is fairly simple just re-flash and go forward but I have tried everything I know and am at a brick wall. I dont understand what the issue is. HTC USB sync in the device Mgr is showing installed and working properly but as soon as I start trying to install MAGLDR113 when it tries to connect to the phone its like Windows just kicks the phone out of the system and shows it to not be installed properly. I have tried re-installing it and tried using different drivers etc. I really am at a loss to know what to do and of course Microsoft is a joke. . . .
Run as Admin maybe?
So after playing with this awhile I have noticed when I plug the phone into the USB it shows HTC usb sync is installed and working properly then after maybe a minute is just goes away. Almost like I unplugged it from the pc. Is this a Windows problem? It happens on both my Windows 7 laptop and the ole Windows Vista upstairs . . . . . .
i had faced this problem once and formatted my laptop and solved this way. but before that it may be a good idea trying another pc that you haven't connected your phone before.
So here's where I am at. I got my pc to recognize my phone a few mins earlier and was able to use task29 and go ahead and install the newest MAGLDR. . Im ready to install the newest Cyanogen mod but now none of my pc's or my neighbors pc will recognize the phone at all. Not in MAGLDR or boot mode. What in the world is going on here? This is beggining to look very bleak. I have literally been working on this for about a day and a half non stop. AHHHHH lol
Whats left ? What have I not thought of? Is my trusty ole HD2 a goner?
Related
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
I upgraded to official 2.3.4 GB (i think it was a Chinese ROM because i downloaded it from the huawei website) and i did not like it because my phone did not get Data or Wifi Or Bluetooth so i i downgraded my phone to 2.2.2 back to the original firmware it had but when i was installing it my phone said Successfully Installed and then it turned of but then nothing happened black screen, next day i change it it turn on the touch keys turn on and LED turn red but screen is black
anyone know how to fix this
I am also having this type of problem. I rooted installed CWM and flashed a custom rom now i have the blue screen issue. Can't find the files I need to repair this anywhere. All the treads have broken links.
r0y123 i am following this guide to correct my problem http://forum.xda-developers.com/showthread.php?t=1589205 I will let you know if it works out.
EDIT: worked perfect I can now boot and reroot.
thanks for the help
my phone wont turn on ,the LED and touch keys turn on for a while only when i connect it to the pc or wall charger. ohh also my computer recognized my u8800-51 as a HID-Compatible device------------- anyone know why?
i cant access pink/purple screen or blue screen not even recovery.
PLEASE I NEED HELP!!!!:crying:
I installed ubuntu
can I use ubuntu to see my phone stuff? sorry i couldnt explain my self
It would be worth a try. I have and increadble and the first time i rooted and and tried to run a rom on it. I got the same kinda thing yor getting. It was a screen driver problem. That might be something to think about. My previous post worked like a charm. Try it your phone is already dead. Just pretend it is at the right screen it wont work if it doesnt find your device.
Nope It did not recognize my phone only when I'm on windows my PC recognize it as a HID-Compatible device but when I go to my Device Manager and uninstall the driver it recognize it as a ""Quantomm something something MSM"" but then windows installs it again and I'm trying to install as something else, ANYONE GOT ANY TIPS?
Sent from my MB300 using xda app-developers app
Mine was being reconized as a Qualcomm ........ but it still worked. See if this is helpfull. http://www.addictivetips.com/window...tomatic-driver-installation-in-windows-vista/
r0y123 Did you ever get your phone working? I have the same issue.
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.
I changed a cracked screen on a Nexus 4. I have done this before with no problems. It is not rooted and locked to a carrier. Now it is stuck in bootloop.
Now the real problem is that even though the phone will take a charge, when I connect it to a PC it the PV doesnt see the phone and it doesn't show up in file folders or in Nexus Toolkit.
So I cannot access ADB either since the PC doesn't see the device and same with Nexus Toolkit.
I can boot into recovery mode but it goes to Android man on back with red flag and "No Command Found" message.
I have spent a week on this. Who out there knows what the hell I can do. I have thought about swapping out the charger port to see if thats why the pc isnt seeing the phone...I am stumped. Help would be very appreciated folks.
Thanks
Wallstud44 said:
I changed a cracked screen on a Nexus 4. I have done this before with no problems. It is not rooted and locked to a carrier. Now it is stuck in bootloop.
Now the real problem is that even though the phone will take a charge, when I connect it to a PC it the PV doesnt see the phone and it doesn't show up in file folders or in Nexus Toolkit.
So I cannot access ADB either since the PC doesn't see the device and same with Nexus Toolkit.
I can boot into recovery mode but it goes to Android man on back with red flag and "No Command Found" message.
I have spent a week on this. Who out there knows what the hell I can do. I have thought about swapping out the charger port to see if thats why the pc isnt seeing the phone...I am stumped. Help would be very appreciated folks.
Thanks
Click to expand...
Click to collapse
What happened to this? I have the same damn issue. Although I managed to get fastboot and adb functionality with great difficulty. But the device doesn't seem to be able to boot into anything. I've tried every single thing software by the book, and by the forums too. I suspect it might be hardware.
Any luck?
Hello everyone, so here i am trying to flash a friend's a1000, but unfortunately, i'm unable to do so because when i try to enter the bootloader by holding the volume up key before plugging in the usb cable to start the process, it only connects to the computer for about 9 seconds, and then automatically disconnects, i get a coloured screen afterwards, and i would be forced to restart the device, i first suspected that it was the cable, but i was wrong, since i've already tried a bunch of cables, all with the same exact result, i also used 3 different computers, and i still got the same result, please respond if you have any idea.
Sisine said:
Hello everyone, so here i am trying to flash a friend's a1000, but unfortunately, i'm unable to do so because when i try to enter the bootloader by holding the volume up key before plugging in the usb cable to start the process, it only connects to the computer for about 9 seconds, and then automatically disconnects, i get a coloured screen afterwards, and i would be forced to restart the device, i first suspected that it was the cable, but i was wrong, since i've already tried a bunch of cables, all with the same exact result, i also used 3 different computers, and i still got the same result, please respond if you have any idea.
Click to expand...
Click to collapse
you need drivers to flash it. i flashed mine in september 2021 and most drivers didnt work. i ended up getting drivers with the same name for a diffrent phone and the flash worked. so try doing that it might end up working. i dont how i did it but it was really hard
Vuk1152 said:
you need drivers to flash it. i flashed mine in september 2021 and most drivers didnt work. i ended up getting drivers with the same name for a diffrent phone and the flash worked. so try doing that it might end up working. i dont how i did it but it was really hard
Click to expand...
Click to collapse
You're right, it is hard indeed, i've already tried so many drivers, i think i'm giving up lol, thanks a lot for the reply, i really didn't expect one since that specific phone is ages old by now !
Sisine said:
You're right, it is hard indeed, i've already tried so many drivers, i think i'm giving up lol, thanks a lot for the reply, i really didn't expect one since that specific phone is ages old by now !
Click to expand...
Click to collapse
thanks. i replied this cause i have the same phone which i want to custom rom but there arent any roms available.(if you have any roms, please let me know)i can try to find you the youtube video i used for the drivers if you tell me what they are called. (if you want to xd) i think its something like "mediatek drivers"
Vuk1152 said:
thanks. i replied this cause i have the same phone which i want to custom rom but there arent any roms available.(if you have any roms, please let me know)i can try to find you the youtube video i used for the drivers if you tell me what they are called. (if you want to xd) i think its something like "mediatek drivers"
Click to expand...
Click to collapse
I appreciate that, i'll let you know if i find a compatible rom for the device, i think the drivers are called CDC drivers if i remember correctly, i don't have the files, but i'm almost sure it's CDC, i'll be grateful if you can send me a link to that video.
Sisine said:
I appreciate that, i'll let you know if i find a compatible rom for the device, i think the drivers are called CDC drivers if i remember correctly, i don't have the files, but i'm almost sure it's CDC, i'll be grateful if you can send me a link to that video.
Click to expand...
Click to collapse
i dont think i ever used that cdc thing when flashing that phone. im pretty sure i used https://firmwarefile.com/lenovo-a1000 to get the stock firmware and just searched up "(driver name) download" on youtube and used some indian guys tutorial. you can try this video if you havent alredy (for the cdc driver)
Vuk1152 said:
i dont think i ever used that cdc thing when flashing that phone. im pretty sure i used https://firmwarefile.com/lenovo-a1000 to get the stock firmware and just searched up "(driver name) download" on youtube and used some indian guys tutorial. you can try this video if you havent alredy (for the cdc driver)
Click to expand...
Click to collapse
I'll try that one, thank you.
Sisine said:
I'll try that one, thank you.
Click to expand...
Click to collapse
np
Do you guys still have the files?
I managed to get the proper drivers and the phone is seen by the computer and I manage to flash it , but the phone is completly dead after the flash .
The power button wont do anything, plugging it into the charger doesnt do anything, I can only reflash it by connecting it to the pc while holding the volume up & down buttons.
Checking on old forums, aparently there are two versions of the phone , single sim and dual sim.
Also the revision number seems to be important for some reason, so mines is dual sim , revision 61 .
I believe this was the firmware that was on it previously, although the phone remained stuck at the boot logo : a1000_usr_s29798_1511241708_sprd7731_ro , but i cant find it anywhere , so I flashed the one you guys had , but now the phone is a dead brick after the flashing ends . Nothing on the screen, no response from any of the buttons, just dead.
CurlyBlonde said:
Do you guys still have the files?
I managed to get the proper drivers and the phone is seen by the computer and I manage to flash it , but the phone is completly dead after the flash .
The power button wont do anything, plugging it into the charger doesnt do anything, I can only reflash it by connecting it to the pc while holding the volume up & down buttons.
Checking on old forums, aparently there are two versions of the phone , single sim and dual sim.
Also the revision number seems to be important for some reason, so mines is dual sim , revision 61 .
I believe this was the firmware that was on it previously, although the phone remained stuck at the boot logo : a1000_usr_s29798_1511241708_sprd7731_ro , but i cant find it anywhere , so I flashed the one you guys had , but now the phone is a dead brick after the flashing ends . Nothing on the screen, no response from any of the buttons, just dead.
Click to expand...
Click to collapse
sorry, i deleted my lenovo a1000 files to focus on other phones. from what i have heard that issue is common with that phone. i know someone who flashed the firmware on their a1000 and got stuck in the same issue as you. i tried to help them unbrick it but it seems to be impossible. i think you need to do a board replacement if you want to use that phone again. also, i dont think that the phone revisions are that important cause i managed to get lenovo a1000m firmware on my lenovo a1000.