i first tried to uroot my desire Z, by doin this it became t-mobile G2 because of the G2 rom,
i did a nandroid backup of g2 rom,
i had to make it desire Z again so i installed pc10img.zip having desire z hboot,cwm recovery,
then i restored from the bakup, then i tried to install stock hboot and turned off the phone,
after that i tried to turn it on but its not turning ON, no LED is flashing, not even goin to the bootloader, m having only black screen, help me plzz
Ok let me get this straight (your post is abit muddled).
1. You're trying to unroot your Desire Z.
2. Flashed the G2 hboot.
3. Made a Nandroid backup of the G2 ROM.
4. Flashed the Desire Z hboot.
5. Restored the backed up G2 ROM.
6. Rebooted as normal.
7. Your phone is now a paperweight - bricked or semi-bricked.
Correct?
Does the LED turn on if the phone is plugged into a wall socket or computer?
Last week I posted a way of returning an unbranded Desire Z to Stock, unrooted and S-ON - the wikis method wasn't working properly for some reason, no idea why.
yeah exactly, and LED turns on when i plug it into wall socket or computer.
have you done a battery pull and tried to get back into bootloader?
desirezbilal said:
yeah exactly, and LED turns on when i plug it into wall socket or computer.
Click to expand...
Click to collapse
Seemed like a stupid question at the time but it was to rule out the battery going dead at any point during the process, was also trying to clarify the situation for everyone else who can help you out.
i have pulled out battery many times and then again put it in but its not turning ON, and battery was fully charged and i have put it on charging for an hour and tried it again, still phone is dead
volume down+power is not even showing up the bootloader, i tried volume up+power it vibrated and red LED started blinking then i connected it to the PC, windows started search for Qualcomm CDMA Technologies driver, at this point I tried ADB but its not recognizing the phone
Related
Hey guys, I really need your help here.
I was trying to flash my mate's phone with the newest MIUI today, but it wouldn't work because the SD card wouldn't mount.
Now when he got this phone, it was already rooted. No idea how they rooted it, but there were a few Chinese apps on there. I got my phone (Samsung Captivate) from the same people, and there were also a few random apps on there, but I managed to flash a new ROM on that. It got to the point where I was un-rooting and rooting it over and over again, until I found a Clockwork Mod that worked on the Defy. It mounted the SD card fine, and then it installed the ROM using the "install from zip from sd card" function or something like it. It went fine, said it finished and it didn't lose power half way through the install. Rebooted the phone, and now it's stuck on the "M" Motorola logo. Went to go flash with sbf, and then it came up saying that the battery was too low so it wouldn't program. Well ****.
Tried the Mcgyver mod where you just splice a USB in between the battery and the phone, but that didn't work. I'm hoping that it will just charge from USB while the phone is off? I've read somewhere that it won't charge while it's off, but the LED is white (I think that indicates that it's charging). Occasionally the "M" logo comes on, but it goes away and starts "charging" again. It won't take to the wall charger for some reason, just doesn't want to charge D:
I've been at this for 8ish hours now, does anyone have any advice? Anything at all will be greatly appreciated.
Thanks,
Justin
How long have you been trying to charge it? That's normal behavior for the phone to show the Moto logo and go to battery charging animation when the phone is off. You should be able to power it on if it is plugged in though.
Are you in the boot loader when you try to flash the SBF? Reboot the phone and hold the volume key up to get to the bootloader. Use RSD lite to flash the SBF. I'm sure you've already looked at http://forum.xda-developers.com/showthread.php?t=966537. It's very helpful.
Good luck!
After flashing the new firm , try to make a WIPE before you install the zip !!
Worked for me!!
this should go to the development sector
youll find your answer there under "bricked phone"
somehow my Defy got stuck in bootloader mode, was working PERFECT, have had no problems with CM7 (except occasion wifi failure when using market or the stock internet app)
and i flashed CM7 to my HTC Hero, which i had some trouble with but got it to work (adb shell was acting weird, but worked sorta, had to use ROM manager tho)
but anyways, after that a little while later, i had plugged in (maybe during i dont even remember honestly, i dont think i had it plugged in while i was acctually using it tho) my defy, because it was dead, and now its stuck in bootloader mode, ive tried taking out the battery (and sd card) but nothing is working, cant boot, or boot into clockwork... i dont get wtf is going on, i figure the adb commands tried to run rage against the cage on my defy, maybe, i dont know, but now im stuck in bootloader mode
Ok let me get this straight....you remove the battery, the phone goes off, you put the battery and it boots directly on bootloader?
have you tried to flash a froyo SBF with RSD lite? it seems to me the only way then you can install 2init again and access the recovery to restore a nandroid bkp or install cm7 again
yes exactly when i put in the battery, it boots into bootloader
but now its working fine
believe it or not, i let it FULLY charge (accidentally fell asleep) in my friends broken defy, and then swapped the batteries this morning, and it just started up completely normal
was the fastboot mode thing simply because the battery was dead and i was using the PC to charge it? i dont get it... because i unplugged it and plugged it into a wall and it still stayed in fastboot... but anyways
PROBLEM SOLVED!
if anybody else has a motorola defy that will NOT BOOT AT ALL or BOOTS INTO FASTBOOT AUTOMATICALLY, try charging the battery in another phone or external charger and then try it in your phone, not sure what caused it but im sure glad to get it working again!!
THANKS FOR THE HELP!
Great man, glad that it's working
usual story.
got an htc one x. flashed unlocked all going well. installed a bad rom (did not make a back up)
froze at splash screen. only late last night i found disaster recovery, so i put it to download and shut off the phone. boot back up this evening and tried to install recovery re-lock bootloader, clear cashe etc but. i got a low battery warning when trying to flash.
i didn't have the latest clockwork mod for charging installed; and battery is too low to flash to it.
this is where things get different. i used the boot loader to power down. i plugged it in to the wall to charge and i got this strange flashing red led(not orange) after about an hour it went solid red. had it charging from the wall socket for well over 4 hours now with the solid red led.
then all of a sudden the led starts to flash red again. so i disconnect the phone and try to boot.... nothing happens. try bootloader mode(power + vol.dwn) nothing.
i had to hold the two buttons then plug in the wall charger. then it went into bootloader. problem is it says relocked AND security warning....... and still after all that time charging. i still get low battery warning @ flash.
so i tried to turn off the device again using the power down option. two things happen here. 1)if the charger is in the screen goes black and instantly restarts to fastboot usb menu. 2)if it isnt in it will turn off and wont turn back on (splash screen or bootloader) until the charger is back in.
so what ive done as of now is plug it in to charge over night and hope this thread can shed some light.
additional info:
ruu version: 'RUU_ENDEAVOR_U_ICS_40_hTC_Asia_WWE_1.28.707.10_Radio_1.1204.103.14_release_257076_signed.exe
os version: 1.28.707.10
clockwork mod version: 5.8.2.7
plz any help would be invaluable
EDIT: just turned on phone about ten minutes after i plugged it back in to the charger (held power button alone) splash screen is back (yay!!) but still battery low when trying to flash in
fastboot usb. ima try in the morning after a full night to the charger. fingers crossed
http://forum.xda-developers.com/showthread.php?t=1598336
no need to spam xda with two threads !!!
kasalamite said:
http://forum.xda-developers.com/showthread.php?t=1598336
no need to spam xda with two threads !!!
Click to expand...
Click to collapse
srry posted last night but would not show the thread... so i figured i couldn't so i tried to post in an existing thread. now i dont know how to delete that other one...
FIXED
well never mind the fact that i loaded a plethora of info onto this post and nothing.
but besides that i got it working. in the disaster recovery tut it only lists using the ruu through a flash... never stating that you can just run the file directly and not go in %temp% and get the rom.zip(excepting for the recovery_signed.img). simply find your version of the ruu that you need, flash back to the stock recovery image (within the rom.zip) relock bootloader place device in fastboot and run from pc.
the only hard part is getting it to charge... dont know how mines took charge but i pluged it into the sockets @ my school (long story read this thread: http://forum.xda-developers.com/showpost.php?p=26156147&postcount=20).
when i pluged it in the light went solid red instantly no blinking. after about an hour of charge i pressed the power button and it went to the splash screen (still was on a older CWM which doesn't support charging) left it at the splash screen for the remainder of the class (about another hour) unplugged entered bootloader.
@ this point i had no security warning under relocked. but i used the power down option, took it home and tried to unlock/flash to the latest version of CWM so i could charge. it worked without a hinge.
anyone know why it took charge on an older CWM?
note i got the phone back up and running and the first thing i did was make a nandroid back up
hi i dont have an answer to your question but i have a question to your answer am curently suffering the same problem i can flash the stock cwm because of low battery, and i know when in boot mode it doesnt charge so i rebooted the phone it took me to the htc logo and its displaying a solid red light does this mean its charging or what (the boot loader is re-locked so i can flash stock cwm but cant due to low charge)
Noob badly. But I think it should be charging. Could b wrong. Leave it there for a couple of hours and try again. Mayb fixed. Give it time and try again.
Sent from my HTC One X using XDA
Same thing is happening to my phone. and its bootloader is locked and cannot be unlocked because of the charging. its usb debugging wasnt turned on either before it went down.
Please help anyone?
Guys I have Htc One X. I rooted it then I thought to install a custom rom (resurrection remix) and gapps. so when I was in the CWM recovery I installed the mod while it was installing it said error no file contents but it installed successfully anyway. after that I installed Gapps but it got an error and said Installation aborted. I then started panicking and I tried to restore the backup but nothing happened, then I re-locked the bootloader with battery below 30% then I used the batch file to charge it then I unlocked it again. Now I want to download a stock rom I tried 2 one was a newer version than what my phone actually is and the other one was a lower version than what my phone actually is. I then tried alooooooooooot to search for the appropriate one for my phone but I didn't find it so I thought to continue with installing custom rom anyway but the problem is that I need to get the new mod zip file and new gapps zip file into my phones sdcard but I can't do that/I don't know how. My phone isn't recognized by my pc ( I can't browse it's files) and I tried using adb in command prompt which is very complicated for me however I searched on the internet and tried to do the same but then it says "adb server is out of date killing" then I found one adbFix.exe that said that the adb in HTC sync manager folder is causing a conflict but then the Fix file said that its ok and no problems are there. Now I need to put custom rom and gapps zip files to my phone's sdcard but I can't. Please I would be very grateful to anyone who would help me and guide me and If I'm posting in the wrong forum or thread then please forgive me for this is my first time I made an account on XDA and my first ever comment/
Hello,
I ran into some serious problems with my OneX about an hour ago...
here's my problem:
I flashed Ice Cold Jelly about a week ago with the provided boot.img. Everything worked fine until now. My Phone started to not turn back on after I turned off the screen so I turned it off using the 8sec powerbutton. After this it booted up and after around 5 mins the same thing happenend again.
So I wanted to go back to stock with a cwm recovery img I made just before I flashed the ICJ-Rom. I booted into the bootloader > fastboot and flashed the stock boot.img via the OneX AIO kit. After that I went into the cwm recovery and restored my stock rom.
The phone was plugged into the Pc during the whole process!
After the recovery finished I rebooted the phone and the stock boot animation greeted me so I plugged it off the Pc and just as I wanted to type in my pin the touchscreen didn't react. As I tried to figure out what happened the auto-lock kicked in and turned the screen off. Tried to turn it on again but it failed. Tried to power it off and on again pressing power for 8sec and rebooting it but no response.
Now I'm sitting here with my OneX which does not react to any button, is not recognized by the Pc and no powerLED when I plug it into the Pc or wall.
Some further information:
power was at 70% when I started
Cid is HTC__002
hboot was 0.95 (I'm not sure about that but it was before v 1.0)
Security was S on
I'm really helpless and a bit afraid right now... so if anyone could help me it would be just awesome!
Atm it's plugged into the wall, as I read in some other threads that after several hours this might help reviving it.
Thanks for any help!
Forunke said:
Hello,
I ran into some serious problems with my OneX about an hour ago...
here's my problem:
I flashed Ice Cold Jelly about a week ago with the provided boot.img. Everything worked fine until now. My Phone started to not turn back on after I turned off the screen so I turned it off using the 8sec powerbutton. After this it booted up and after around 5 mins the same thing happenend again.
So I wanted to go back to stock with a cwm recovery img I made just before I flashed the ICJ-Rom. I booted into the bootloader > fastboot and flashed the stock boot.img via the OneX AIO kit. After that I went into the cwm recovery and restored my stock rom.
The phone was plugged into the Pc during the whole process!
After the recovery finished I rebooted the phone and the stock boot animation greeted me so I plugged it off the Pc and just as I wanted to type in my pin the touchscreen didn't react. As I tried to figure out what happened the auto-lock kicked in and turned the screen off. Tried to turn it on again but it failed. Tried to power it off and on again pressing power for 8sec and rebooting it but no response.
Now I'm sitting here with my OneX which does not react to any button, is not recognized by the Pc and no powerLED when I plug it into the Pc or wall.
Some further information:
power was at 70% when I started
Cid is HTC__002
hboot was 0.95 (I'm not sure about that but it was before v 1.0)
Security was S on
I'm really helpless and a bit afraid right now... so if anyone could help me it would be just awesome!
Atm it's plugged into the wall, as I read in some other threads that after several hours this might help reviving it.
Thanks for any help!
Click to expand...
Click to collapse
Okay, did you flash the ruu's stock boot.img and system recovery the relock the bootloader before flashing the ruu?
---------- Post added at 02:37 AM ---------- Previous post was at 02:24 AM ----------
sorry i misread it. You flashed a backup of your stock rom and flashed the boot.img. i would recommend trying to flash the original ruu if youre getting errors. The fails to turn it on sounds like it out of battery. If you can find the thread there is a batch file you can run to start it charging through your pc
XxJibblesxX said:
The fails to turn it on sounds like it out of battery. If you can find the thread there is a batch file you can run to start it charging through your pc
Click to expand...
Click to collapse
I hope that's the problem, but I can't imagine my phone using up 70% of the battery plus the usb hub power in about half an hour.
...this all seems to me like there's a hardware fail (which I really don't want to) as the system booted and then crashed into brick mode.
I'm not home tonight but the phone is on usb and tomorrow I'll try the tool and report my findings
Edit:
Ok, the phone spent 6 hours plugged into the pc and until now it was plugged into the wall but nothing. It seems to be completely dead -.-
Tried the batch file but there's nothing much to try when I can't even get into fastboot. The phone simply won't react to anything...
I will send it back as it's only about a month old and hope the warranty will fix it.
There is a stock rom with stock kernel on it so I hope they don't bother about the bootloader beeing unlocked.
But what I think is that there is a serious hardware problem. As I continued to read through other posts I realized that I had the same audio problems (stuttering and slowing down of the music) like some others...
If HTC tells me something about what caused the problem I'll post it here.
So far thanks for your help
Long story short, I flashed under the recovery console a wrong bootloader image(only the bootloader, nothing else). Now the phone doesn`t turn on, charging led dead, screen dead, everything dead, usb connection dead. Fastboot devices won`t give me anything, adb also nothing, in computer`s device manager also nothing detected. Any ideeas? Thanks!
I am afraid its a hard brick!
Sent from my HTC Desire using xda premium
I kinda thought the same way. Now I`m hoping for that miracle with..pulling the battery out and waiting a few hours to "heal" to happen, if not it`s just another brick in the wall?
What "bootloader.img" did u flash?
Vodafone UK 2.33.161.6 PB9920000 from htc bootunlocker site http://www.htcdev.com/bootloader/ruu-downloads
Mihut84 said:
Vodafone UK 2.33.161.6 PB9920000 from htc bootunlocker site http://www.htcdev.com/bootloader/ruu-downloads
Click to expand...
Click to collapse
You only flashed the bootloader? Not the entire ruu?
Unless you get to boot somehow, your phone is a genuine brick.
Yes, only the bootloader. Any ideea how to get it to boot?
Maybe a buspirate can revive a hard brick?
Alive again
So, I made it boot again, using jtag, reflashed the right bootloader. But when I go to hboot and try to flash the rom from the micro-sd, it vibrates a few times and that`s it, doesn`t do anything, buttons stop working. Tried to flash it with fastboot via usb, same thing, tried the RUU utility, and when it says rebooting into bootloader, it also vibrates and dies. In hboot it gets stuck at checking the zip and parsing. So, last night I decided to give up, but then I remembered I saw on the internet some heat related problems, although my htc didn`t got hot or anything, so I put it in the freezer at -18 degrees celsius for half an hour, without the battery and micro-sd. After about 30 min, I put the battery and micro-sd, and for my surprise, it flashed it from the micro-sd, no errors, it booted, got it working. Ok, I removed the battery and let it dry a few hours. Put the battery back, turned it on, it gets stuck in bootloop. Put it back to freezer for 30 mins, works flawless. So, I believe there is a hardware problem, more likely electrical contacts on the board, since i don`t feel any heat coming out from the phone.