Database Info

[Solved] almost bricked mt4g. please verify my next step

First, let me say thanks to all who contribute. I started with a G1 when it first came out, using the JF mods and lurking these forums for hours. Without you guys, we'd all be stuck with boring stock devices!
Heres my question:
I've done a search and just want someone to verify my next planned step.
Tonight I think almost bricked my Mytouch 4g. I had root, and had CM6.1.2-RC2 installed. It was working great.
Then I wanted to get the CM7 nightlies working. I couldn't get the CM7 rom past the mytouch splash screen. So, I upgraded Rom Manager, and thought i had to upgrade ClockworkMod to 3.0 to get the CM7 nightly rom to boot. I accidentaly flashed the wrong ClockworkMod Recovery. I flashed the file that was for a G2 (vision). Rebooted without noticing my mistake, than noticed my error when I couldn't get into recovery mode.
Fortunately i installed Hboot during the rooting process. I'm planning on letting Hboot flash the file mentioned in this post to get back to stock:
http://forum.xda-developers.com/showpost.php?p=10514066
What do you think?
Just don't want to get myself in deeper S...
Thanks again.

connect the usb and run adb. Boot into bootloader and flash the recovery 3.0??? that way. You'll be good to go after that

osugsxr said:
connect the usb and run adb. Boot into bootloader and flash the recovery 3.0??? that way. You'll be good to go after that
Click to expand...
Click to collapse
You can connect adb with the bootloader? I ran:
Code:
adb devices
and adb came back with no devices found.
How do I flash the recovery if adb has nothing to communicate with?
BTW, I'm using Hboot Engineering, and Hboot does recognize the usb connection by displaying: HBOOT USB PLUG

fastboot devices

fastboot devices
fastboot flash recovery recovery.img

SOLVED
Thanks for trying to help osugsxr. I will have to read up on fastboot.
However, I did not follow your advice. I didn't get your reply in time to try fastboot. My impatient ADD personality went ahead and followed the advice in the thread that I referred to in my original post. In an effort to help others who may have gotten into a jam, heres what I did:
1. Took out my SD card and connected it to my PC via external SD card reader.
2. Because I had a ton of crap on the SD card, I formatted it FAT32 to have a clean card.
3. Downloaded the stock Glacier rom (A large 315mb file. Should have a filename like PD15IMG_Glacier_TMOUS_1.17.531.2_Radio_12.28b.60.140e_26.03.02.26_M_release_155771_signed.zip)
4. Copied the stock Glacier rom to the SD blank card.
5. Renamed the rom to PD15IMG.zip (maybe case sensitive, not sure)
6. Unmounted/Ejected the SD card from the PC reader an put it back in my phone.
7. Pulled the battery on my phone for about a minute then put it back in.
7. Hold volume down and the power button at the same time.
8. Hboot should start up, then after a few moments it will say loading PD15IMG.zip. After PD15IMG.zip loads, it will ask you "Do you want to start update?". Press VOL UP for Yes.
9. You will then see Hboot working its way down a list of about 9 items. Be patient, this takes a while. After this is done, it will say so, and tell you to press the power button to reboot.
Hopefully you have successfully flashed the stock rom, and your phone will be back to what it was like when you first bought it.
I attached pictures of the Hboot screen and flashing process for reference

[Q] cant get into Recovery after Updating FW

i was following this thread to install the ROM
http://forum.xda-developers.com/showthread.php?t=1429953
i applied the PG58IMG.zip from the http://forum.xda-developers.com/showthread.php?t=1432220 as this was said to be required.
now after i updated the firmware through HBOOT, the phone asked to reboot. but it only stays at the white screen "HTC" and nothing more
all i can do is pull the battery out and put it back in and boot into HBOOT
i want to get into recovery mod to install the ROM i have saved on my SD Card. but like i said i cant get into recovery as once i press "bootloader" it will try to update the FW again. i only can say YES or NO, either one will end up with Rebooting the Phone as my only option. which gets me back into the WHITE SCREEN.
HELP PLEASE!!!

Take the memory card out, boot in to hboot, enter recovery. Reinstall memory card, and deleat the file.

thnx
thx. didnt think of that

taogenix said:
thx. didnt think of that
Click to expand...
Click to collapse
Simple when you know how lol.
I learnt it last week

You can also run "adb reboot recovery" while the phone is off. That way you don't have to take the cover off. It also works if you for some reason get stuck (happens sometimes when flashing PG58IMG.zip files) at the HTC splash screen.

Guys someone please help.....I'm stuck.

I am having a new AT&T HTC ONE X......I rooted it, unlocked the bootloader and installed Clockwork MOD 5.8.3.1.......I wanted to flash LeeDrOiD_One_Xtreme_V6.4.0 onto my phone......I made a backup of the stock ROM and saved it onto my PC and formatted the storage and transfered LeeDrOiD_One_Xtreme_V6.4.0 on to the storage.....now I'm having no other files on the storage other than the leedroid zip file......I booted into the bootloader and flashed the boot.img file and then booted into recovery and wiped dalvik catch, wiped catch partition and wiped data/factory reset and then flashed the LeeDrOiD_One_Xtreme_V6.4.0.zip.......at the end I got a error message saying CHECK MODEL ID......I clicked on REBOOT and from then onwards I'm stuck at the HTC LOGO Screen......when I tried to mount as USB storage to transfer the stock backup ROM, I'm not able to mount the phone onto my PC.......
Guys please help me restore to the stock ROM.

Sounds like international rom? You on one XL or one x.
Place phone into fastboot and Try running a stock ruu. Should get you to stock.
Also. People are gonna flame the hell out of you for posting in the dev forum lol.
Sent from my HTC One X using xda premium

You are bricked..first of all leedroid is for.international one x..so you can't flash that to one xl
Sent from my HTC One X using XDA

http://www.youtube.com/watch?v=aIrhVo1WA78

Can you boot into recovery?

aimetti said:
Also. People are gonna flame the hell out of you for posting in the dev forum lol.
Click to expand...
Click to collapse
Isn't this the Q&A forum? Sounds like an appropriate question for this forum to me.

This started in development. It was moved.

I dont think its international ROM.....its AT&T United Sates Phone.......to run stock RUU I need to put the stock RUU onto my phone memory but I'm not able to connect my phone to my desktop in USB Storage or Mass Storage mode......if I could connect so I can transfer my stock rom backup files onto my ph and make a restore and make my phone work as usual.........guys someone please help me make my ph work as normal.
or is there any other custom recovery that allows me to connect my phone in USB storage more or mass storage more so that I can transfer my stock backup ROM and restore it and make my phone working.

praveen5344 said:
I dont think its international ROM.....its AT&T United Sates Phone.......to run stock RUU I need to put the stock RUU onto my phone memory but I'm not able to connect my phone to my desktop in USB Storage or Mass Storage mode......if I could connect so I can transfer my stock rom backup files onto my ph and make a restore and make my phone work as usual.........guys someone please help me make my ph work as normal.
Click to expand...
Click to collapse
You don't put the RUU on the phone's memory. You download it (must use windows) plug the phone in and run it...make sure you relock the bootloader first.
And you DID flash an international ROM....we don't have a leedroid ROM for our phone...everybody really ought to research hard before doing ANYTHING to their phones.

praveen5344 said:
I am having a new AT&T HTC ONE X......I rooted it, unlocked the bootloader and installed Clockwork MOD 5.8.3.1.......I wanted to flash LeeDrOiD_One_Xtreme_V6.4.0 onto my phone......I made a backup of the stock ROM and saved it onto my PC and formatted the storage and transfered LeeDrOiD_One_Xtreme_V6.4.0 on to the storage.....now I'm having no other files on the storage other than the leedroid zip file......I booted into the bootloader and flashed the boot.img file and then booted into recovery and wiped dalvik catch, wiped catch partition and wiped data/factory reset and then flashed the LeeDrOiD_One_Xtreme_V6.4.0.zip.......at the end I got a error message saying CHECK MODEL ID......I clicked on REBOOT and from then onwards I'm stuck at the HTC LOGO Screen......when I tried to mount as USB storage to transfer the stock backup ROM, I'm not able to mount the phone onto my PC.......
Guys please help me restore to the stock ROM.
Click to expand...
Click to collapse
Like mikelebz mentioned above, you best run the RUU of your PC and get back to STOCK, then redo all the mods you want to add.
There no better solution, that is that simple!
Good luck man! :good:

I made a backup of the stock rom and saved them onto my pc and these are the files available on my pc........can someone please tell me how do I flash them onto my phone using adb......please mention the commands and help me out guys.

praveen5344 said:
I made a backup of the stock rom and saved them onto my pc and these are the files available on my pc........can someone please tell me how do I flash them onto my phone using adb......please mention the commands and help me out guys.
Click to expand...
Click to collapse
We've been trying to help you....if you can't get into recovery, those are useless

If you have cwm installed, there is an option to mount sdcard.
Once it's mounted you should be able to transfer your files.
If you had the ability to load the rom you should have the ability to get back into cwm recovery.
I got stuck in a boot loop myself and did this to get myself out. But I also save at least 1 working backup on my sdcard.
Sent from my HTC One X using xda app-developers app

Like others have pointed out you tried to flash a International ROM for the Nvidia based chipset ONE X. That's why your stuck.
Now if you can get into the bootloader by holding down the vol down button and the power button from the phone being turned OFF here is what you do.
Step 1 Plug phone into your PC while turned off
Step 2 Boot into bootloader
Step 3 Select Fastboot
Step 4 Go to your ADB folder
Step 5 hold shift down and right click in the ADB folder and select open command window here (only works in windows 7)
Step 6 type fastboot oem lock in the command window.
Your phone is now relocked and will automatically reboot but will still lock up at the htc screen because your still using the wrong ROM. SO now force your phone off again and reload back into the bootloader select fastboot then run the RUU from your PC. This will restore your phone.
From this point you can re unlock your bootloader then fastboot flash a recovery I recommend TWRP as its guaranteed to have working sdcard mount. Then you can flash custom ROMs again but please this time pay attention to your phones model Stay away from the One X forum and only go to the AT&T ONE X forum and please please READ before blindly jumping in and flashing.

I got my problem solved guys.....I was having CWM-TOUCH-5.8.3.1 which was not able to mount my ph as USB storage ( its a bug in CWM )......I flashed the phone with TWRP recovery ROM and was able to mount my phone as USB storage and copied the ROM backup folder and restored my stock ROM.........

when I reject and incomming call I get two icons saying REMINDME and SEND TEXT.......How do I disable this option.....like reject the call and dont get this reminder and send text icons.

praveen5344 said:
I dont think its international ROM.....its AT&T United Sates Phone.......to run stock RUU I need to put the stock RUU onto my phone memory but I'm not able to connect my phone to my desktop in USB Storage or Mass Storage mode......if I could connect so I can transfer my stock rom backup files onto my ph and make a restore and make my phone work as usual.........guys someone please help me make my ph work as normal.
or is there any other custom recovery that allows me to connect my phone in USB storage more or mass storage more so that I can transfer my stock backup ROM and restore it and make my phone working.
Click to expand...
Click to collapse
To answer your question. Yes there is a custom recovery that allows you to mount your storage as a USB Mass Storage device.
Its here http://techerrata.com/file/twrp2/openrecovery-twrp-2.1.8.1-evita.img.
If you don't already have ADB and all the Android software utilities download and install them here http://developer.android.com/sdk/index.html Only install "Tools" which includes the SDK Tools and SDK Platform Tools. They're located in C:\Program Files\Android\android-sdk\platform-tools, also by the way put the .img you downloaded into that folder as well.
Now go to Run... and type in CMD to get into command prompt. then type in
"cd C:\Program Files\Android\android-sdk\platform-tools"
or "cd C:\Program Files (x86)\Android\android-sdk\platform-tools" for 64 bit
then
Go into your phones bootloader (I assume you know how to do this since you can get into CWM and then go into the fastboot. Then connect it to your PC. If you've done this correctly it should have a red status of "FASTBOOT USB" if it didn't work make sure you have the right HTC Drivers installed for your phone.
Here: http://binary100100.googlecode.com/files/HTCDriver3.0.0.007.exe
After you have your phone in FASTBOOT USB mode then go back to command prompt and type in this command
fastboot flash recovery openrecovery-twrp-2.1.8.1-evita.img
It should then push the recovery img to the phone and over-write CWM.
If it said it couldn't read or find the img make sure you have it in the same folder as ADB and fastboot etc.
Let me know if it works.

when I reject and incomming call I get two icons saying REMINDME and SEND TEXT.......How do I disable this option.....like reject the call and dont get this reminder and send text icons.

praveen5344 said:
I was having CWM-TOUCH-5.8.3.1 which was not able to mount my ph as USB storage ( its a bug in CWM )......I flashed the phone with TWRP recovery ROM and was able to mount my phone as USB storage and copied the ROM backup folder and restored my stock ROM.........
Click to expand...
Click to collapse
That's 2 big mistakes that could have been easily avoided with the proper research. CWM Touch is not meant for our device, and has some major issues with our phone, as you found out the hard way. Two things that were never meant to be flashed to our device (CWM TOuch and LeeDroid). You're lucky you don't have a hard brick.
You need to slow down on the flashing of things without proper research. Take a breath, and do some reading before you do some irreparable damage. Specifically, only flash things in the Development forum for the AT&T version of the phone.
http://forum.xda-developers.com/forumdisplay.php?f=1541
And my index thread is an organized list of mods for our phone:
http://forum.xda-developers.com/showthread.php?t=1671237

Can only get into Hboot

hi everyone,
I could really need a quick solution.
I just received my phone from a screen repair and was going to root it.
I unlocked it first with htcdev and now it says juopunutBear and it's S OFF.
but when I'm booting it, it just stayson the HTC screen and when I select recovery or factory reset it goes into the reset screen for a little while and after that it returns to the boot screen.

If you can get to the hboot scrren it should be fixable.
You might be able to flash a new copy of a recovery from fastboot on your computer. That should let you reinstalled a saved rom.
You may also be able to flasha rom through a pm58img file in the bootloader.
If all else fails you should be able to run an ruu to reset it entirely and start over.
Sent from my HTC Sensation using xda app-developeras app

Thanks! I'm running the RUU right now, everything will probably go as planned!

[Q] hardware or software fault?

i recently started another thread asking for help with my soft bricked stock htc one s.
i was basically playing a game, exited then rebooted and got stuck in a boot loop. tried to install various ruus but was unable to find the proper version/cid to install.
today i got the bright idea of unlocking the bootloader and installing recovery to avoid the issue of my apparent o/s corruption and just installing a custom rom.
unlocked the bootloader successfully, installed cwm successfully then try and boot into recovery, screen goes white with the htc warning about being for developers for 30seconds or so then it restarts into the boot loop at the htc quietly brilliant screen. though maybe there was a problem with the cwm so i tried twrp with the same problem.
does this mean im looking at a hardware fault or does anyone think it could still be software related? im kind of worried now as i probably just voided any chance of getting warranty from htc...

A recovery and unlocked bootloader will not help you get out. Now flash a custom ROM. Don't forget to flash the boot.img
Sent from my locked, tampered ville
---------- Post added at 07:20 AM ---------- Previous post was at 07:18 AM ----------
Oh and don't start two threads!!
Sent from my locked, tampered ville

Is there a way to flash a rom from Fastboot? I've tried fastboot flash system romname.zip and fastboot flash boot boot.img without any luck, appears I've made it worse as the bootloop loads to fastboot now...
I can't get adb to recognize the device, only fastboot commands work. It's weird though, I checked the log of the failed ruu installs and it seems to recognize the phone with adb during the install attempt. I've also tried mirroring the commands from the ruu log but I can't replicate the ability to access adb. I was able to get that black htc screen that pops up during the ruu install though, I dunno if that's a special mode for running adb commands or what it's for but I wasn't able to connect then either...

fastboot flash zip rom.zip
then
fastboot flash boot boot.img

i broke down and spent $20 on a official ruu for my phone. it installed successfully but the phone is still stuck looping the white htc screen.
hoping htc honors my warranty, i unlocked my bootloader trying to fix this problem but its starting to look hardware related... unless there is another partition of software on the phone that could have become corrupted...

mikeinaus said:
i was basically playing a game, exited then rebooted and got stuck in a boot loop.
Click to expand...
Click to collapse
It happens sometimes, you should have just gone into the stock recovery and did a factory reset. But it's too late lets move on...
unlocked the bootloader successfully, installed cwm successfully then try and boot into recovery, screen goes white with the htc warning about being for developers for 30seconds or so then it restarts into the boot loop at the htc quietly brilliant screen. though maybe there was a problem with the cwm so i tried twrp with the same problem.
Click to expand...
Click to collapse
Sounds like the kernel didn't get put, you know the part where you are supposed to do fastboot flash boot boot.img. But it's too late lets move on...
does this mean im looking at a hardware fault or does anyone think it could still be software related? im kind of worried now as i probably just voided any chance of getting warranty from htc...
Click to expand...
Click to collapse
As long as you can get to bootloader you can recovery the phone (as least that's my experience)
mikeinaus said:
Is there a way to flash a rom from Fastboot? I've tried fastboot flash system romname.zip and fastboot flash boot boot.img without any luck, appears I've made it worse as the bootloop loads to fastboot now...
Click to expand...
Click to collapse
Yeah you made it worse, since it only loads to fastboot now, most likley you caused a problem with your recovery. But that's real easy to fix.
I can't get adb to recognize the device, only fastboot commands work. It's weird though, I checked the log of the failed ruu installs and it seems to recognize the phone with adb during the install attempt. I've also tried mirroring the commands from the ruu log but I can't replicate the ability to access adb. I was able to get that black htc screen that pops up during the ruu install though, I dunno if that's a special mode for running adb commands or what it's for but I wasn't able to connect then either...
Click to expand...
Click to collapse
That's a real mess, just stop whatever you're trying to do there.
mikeinaus said:
i broke down and spent $20 on a official ruu for my phone. it installed successfully but the phone is still stuck looping the white htc screen.
Click to expand...
Click to collapse
Where did you spend the $20? File Factory? An RUU shouldn't fail to the fix the problem. I would suggest you just unlock it, install a recovery and then your rom of choice. Even if it's just a rooted stock ROM.
If I was in your spot, I would do this.
1. Unlock Bootloader
2. Install TWRP - Do a factory reset, then wipe system.
3. Flash a custom rom
4. Boot into bootloader - fastboot flash boot boot.img.
5. Reboot

If I was in your spot, I would do this.
1. Unlock Bootloader
2. Install TWRP - Do a factory reset, then wipe system.
3. Flash a custom rom
4. Boot into bootloader - fastboot flash boot boot.img.
5. Reboot
Click to expand...
Click to collapse
1. have done so
2. tried it as well as cwm, phone will not boot into a recovery, doing so just loads into the loop
3. tried without luck
4. tried this as well after flashing rom and still same problem
running the ruu removed the "tampered" message from bootloader as well as stopping the loop from loading into fast boot, it also removed the red developer text from popping up when booting. however the phone is back to its original problem of looping the htc quietly brilliant screen. ive run the ruu twice now without any change.
if the ruu cant fix the problem im doubtful messing around with custom roms will. there is clearly some kind of problem with the phone causing the loop. as far as i understand a ruu completely wipes all the data on the phone and reinstalls all the partitions from scratch.
ive just sent htc an email seeing if theyll cover it for warranty, hopefully they will stand behind their product, as i was not the cause of this problem...
i got the ruu from football, he is the one who posted the thread with all the stock ruu's and he was able to track down the proper one for my phone...

mikeinaus said:
1. have done so
2. tried it as well as cwm, phone will not boot into a recovery, doing so just loads into the loop
3. tried without luck
4. tried this as well after flashing rom and still same problem
running the ruu removed the "tampered" message from bootloader as well as stopping the loop from loading into fast boot, it also removed the red developer text from popping up when booting. however the phone is back to its original problem of looping the htc quietly brilliant screen. ive run the ruu twice now without any change.
if the ruu cant fix the problem im doubtful messing around with custom roms will. there is clearly some kind of problem with the phone causing the loop. as far as i understand a ruu completely wipes all the data on the phone and reinstalls all the partitions from scratch.
ive just sent htc an email seeing if theyll cover it for warranty, hopefully they will stand behind their product, as i was not the cause of this problem...
i got the ruu from football, he is the one who posted the thread with all the stock ruu's and he was able to track down the proper one for my phone...
Click to expand...
Click to collapse
You're in a ****ty spot then. There might be one or two ways to still recover but it sounds like your chances are getting slimmer. I've seen a few other reports of completly stock One S's taking a ****. I hope HTC fixes it for you.

htc said this regarding unlocking the boot loader when i asked about coverage with my problem. looks like they may still cover it. im betting there gonna take the easy way out and just say its not covered when its all said and done though. ive read horrible things about htc customer service...
Not all claims resulting or caused by or from the unlocking of the bootloader may be covered under warranty. There are several possibilities of what may have caused this issue, that are covered by the warranty, in which the unlocking of the bootloader would not be a problem. We advise you to contact our tech specialists as they will let you know if this procedure will be covered by the warranty.
Click to expand...
Click to collapse