Noob, May have bricked my phone :( - Desire General

Okay so i am in desperate need of help!
I wanted to root my desire. I have the telstra next g A8183 Desire, i attempted to root it using this method:
http://nimbu.amorvi.com/2010/05/how-to-root-your-htc-desire/
Only to find out it doesnt work because apparently my phone has a bootloader of 0.80.
So i used a method on Xda;
http://forum.xda-developers.com/showthread.php?t=696189
I used the method for rooting an unlocked desire, with a gold card.
I got almost to the end, up to the step;
"In the command prompt/terminal window, enter either 'step2-windows.bat', './step2-mac.sh' or './step2-linux.sh' as appropriate"
However, my zip i downloaded didnt contain "'step2-windows.bat'"
which now has lead me to a problem where i am stuck on the 'recovery' screen.
Please can anyone help me, im afraid ive bricked my phone

Follow exactly what it says in that XDA thread, ignore what is says in the nimbu thread and download what the XDA thread tells you to download, you should be goldcarded and rooted in about 20 mins (not kidding) as i did this last night (difference being i didnt need a goldcard)
but again follow the XDA stuff and ignore the rest for now

i cant actually get my phone past the boot screen, it just hangs..
so i cant follow those steps!

can you get into bootloader??
Vol- + Power??

yes, but i dont know what to do from there..

put your phone into the bootloader and start again/resume
no harm is done if you can get into the recovery screen
you are hanging because you have formatted your system, this is meant to happen
now you simply flash the rooted rom
download the files needed to root your phone from here and complete step 2

cgrec92 said:
put your phone into the bootloader and start again/resume
no harm is done if you can get into the recovery screen
you are hanging because you have formatted your system, this is meant to happen
now you simply flash the rooted rom
download the files needed to root your phone from here and complete step 2
Click to expand...
Click to collapse
You took the words right out of my keyboard

i continue step 2 but i get an error message..
"Desire Root Step 2
Pushing required files to device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
error: device not found
Pushing update file to device sdcard - this may take a few minutes..
error: device not found
error: device not found
Now wipe and apply rootedupdate.zip from the recovery image menu."

Are the files already on the SD???
What happens when you procede onto wipe and applying rootedupdate.zip?

all i have is a blank sd card in there at the moment, because i had to wipe my gold card, i cannot connect it to make another one.
BUT i re ran step 1 and now its going through a completely different process.
im pretty sure its flashing now, its saying stuff like
INFO[RUU] UZ, radio 05..
INFO[RUU] UZ, system 100
does that mea its flashing properly?

Okay ive pretty much gone through the process, however im up to the 'green' screen where i have to choose wipe.
which buttons do i use to select wipe? haha
i must sound like an idiot lol

See
Yeh wipe and format (or whatever it says) then flash from update.zip on SD
Simples!

Thanks so much for your help!! :

If we had a Karma or a Thanks Button on this forum feel free to click it for me

Related

EVO Bricked? Please Help

I had rooted my phone and updated the radio to 1.47.651.1 when I tried to update a custom rom I accidently re-ran PC36IMG.zip and it rebooted quick NOW the radio says 1:39:00:04:26
and in the options below I now have
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
HBOOT USB
I tried putting the phone on FASTBOOT then connected it to the USB and began a stock rom not rooted and it boots my phone into an HTC Black screen Boot mode and begins to update until it comes to the signatures and it gives me an error.
I run windows 7
I went and tried this, connected sd card to Computer with adapter and transferred stock rom rooted and renamed it to sdcard.zip
booted Evo to bootloader and chose recovery.
I as usual got the black background with EVO Icon and red triangle with exclamation mark.
There I click on hold Volume Up and Power until I get the following error:
E:Can't open /cache/recovery/command
Then I click volume up and the following title and menu appear:
Android system recovery <2e>
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
When I choose the sdcard:update option the following message is displayed
----Install from Sdcard ------
Finding Update package
Opening update package
verifying update package
E:signature verification failed
instalation aborted
After, I downloaded tha froyo 2.2 file and placed it on the sd and rename it to update.zip
and when I ran Update.zip from bootloader it ran half way but then stopped saying the following error
failed to verify whole-file signature
So now I load any PC36IMG and I get NO QUESTION to update just puts me onto the bootloader screen….
Not bricked, just stuck. Download stock ruu, plug phone into computer and install. Or put pc136.img on rot of sd, boot into fast boot, it should install automatically. If none of the above, go to a sprint store, tell them it won't boot and you don't know why, and they will flash or replace.
Sent from my PC36100 using Tapatalk
What I would do from here if I were you is put that sd card back in the computer and erase everything on it.
while your at it shut down the phone. Hold down the volume down button and press power. When that comes up post what version of Hboot you have please.
And I'll be better able to help out.
WOw
did you try to reinstall another ROM?
if you still see the RECOVERY menu item, go there and then go where it says update from zip on sdcard. then using up/down buttons highlight the .zip file of the ROM then push the power button to make it run.
this hoping you got a ROM on your sdcard. if not just get one at the forum and download.
i got clockworkmod but im sure the other recovery tools have similar options.
@ adelaney Stock Ruu begins to update and gives me an error when signatures are being installed. I tried three Stock ROMS
RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_release_171253
RUU_Supersonic_1.32.651.6_Radio_1.39.00.05.31_release_171253_signed
RUU_Supersonic_1.47.651.1_Radio_2.05.00.06.10_release_CL195459
@ rjmjr69
Hboot information is:
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-0.79.0000
MICROP-041F
TOUCH PANEL-ATMWLC03_16ac
RADIO-1.39.00.04.26
@mogul420
Recovery gives me an error
E:Can't open /cache/recovery/command
Then I click volume up and the following title and menu appear:
Android system recovery <2e>
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
When I choose the sdcard:update option the following message is displayed
----Install from Sdcard ------
Finding Update package
Opening update package
verifying update package
E:signature verification failed
instalation aborted
Ok here's the deal. If you have nan unlock, fully rooted then you should have a nandroid back. If you do then boot into recovery and no a nandroid restore. This should boot you to one of your pervious backup/ system state.
Please note.
If you are fully rooted u should always do a nandroid backup before you flash any update, that way u can do a restore in the even something goes wrong.
http://WWW.rootznculture.com
Thank you for the information but it was a step I did not do... The tutorial that I went with did not speak about that when I rooted my phone...
EDIT: I even tried mixing files that I have downloaded with various PC36IM.zip and nothing triggers the update question.
Would they be able to notice if its rooted?
adelaney said:
Not bricked, just stuck. Download stock ruu, plug phone into computer and install. Or put pc136.img on rot of sd, boot into fast boot, it should install automatically. If none of the above, go to a sprint store, tell them it won't boot and you don't know why, and they will flash or replace.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Most likely NOT bricked if it boots!
Sounds like you re-applied root but glitched somewhere?
Try root again - may still work?
http://forum.xda-developers.com/showthread.php?t=706411
Another helpful post
http://forum.ppcgeeks.com/showthread.php?t=123714
What version is your hboot - press power and volume down WITHOUT pc36img.zip, update, etc on your sd - i.e. rename it or remove it, i.e. with adb or sd card slot on pc.... See if you can still access recovery?
I've been hammering on these things for a bit and if I can get into the boot screen, it's pretty much good to go...
Hboot-0.79.0000
Also the error that began all of this was running the wrong PC36IMG to begin with... I had 1.4 radio and I think that the one I used had the 1.3 radio so the only thing that helped me boot up again was that 1,2,3 step flashing so I thought that I had to take the second step and that placed in on booter, I have not been able to boot again ever since.... That was yesterday been trying for about 9 hours lol
lwarranty said:
sounds like you re-applied root but glitched somewhere?
Try root again - may still work?
http://forum.xda-developers.com/showthread.php?t=706411
another helpful post
http://forum.ppcgeeks.com/showthread.php?t=123714
what version is your hboot - press power and volume down without pc36img.zip, update, etc on your sd - i.e. Rename it or remove it, i.e. With adb or sd card slot on pc.... See if you can still access recovery?
I've been hammering on these things for a bit and if i can get into the boot screen, it's pretty much good to go...
Click to expand...
Click to collapse
Yes your just not rooted anymore. Run whatever process worked for you the first time
Try whitslack's method.
EDIT: Nevermind, no can do.
What happens is that my phone DOES read the PC36IMG.zip but it does not give me update option as it used to before. Any suggestions?
rjmjr69 said:
Yes your just not rooted anymore. Run whatever process worked for you the first time
Click to expand...
Click to collapse
xx1479 said:
Try whitslack's method.
Click to expand...
Click to collapse
latinsbest said:
What happens is that my phone DOES read the PC36IMG.zip but it does not give me update option as it used to before. Any suggestions?
Click to expand...
Click to collapse
Like he said
Make sure you delete all the files off your sdcard first
Do you have a link? I made a quick search and could not find a direct link...
xx1479 said:
Try whitslack's method.
Click to expand...
Click to collapse
I have several times even formatted (fat32) various times too
rjmjr69 said:
Like he said
Make sure you delete all the files off your sdcard first
Click to expand...
Click to collapse
latinsbest said:
I have several times even formatted (fat32) various times too
Click to expand...
Click to collapse
Reroot your phone using toast method! That is all! If you are on 1.47 then use simple root!
Seems you have un-rooted the boot me thinks but also read something about mixing radio's causing grief, someone more in the know could answer that... If you can get to hboot usb and try the RUU from your PC? Sometimes taking the battery out and restarting, if communication fails, try it again, rebooting the pc, hell I have no procedure, I just hammer till it makes sense, however 9 hours - holy crap, I'd be foaming at the face!
Ok will do right away and post update
novanosis85 said:
Reroot your phone using toast method! That is all! If you are on 1.47 then use simple root!
Click to expand...
Click to collapse
I have done that via PC and the only thing that works with that are the stock roms since they come in EXE they manage to reboot my phone and everything but when the update gets to the signature part it says it fails in the signatures and aborts... any other custom roms that have EXE?
lwarranty said:
Seems you have un-rooted the boot me thinks but also read something about mixing radio's causing grief, someone more in the know could answer that... If you can get to hboot usb and try the RUU from your PC? Sometimes taking the battery out and restarting, if communication fails, try it again, rebooting the pc, hell I have no procedure, I just hammer till it makes sense, however 9 hours - holy crap, I'd be foaming at the face!
Click to expand...
Click to collapse

IDK What I did to my phone.HELP PLZ!

I tried to root my phone using the tutorial here:
http://forum.xda-developers.com/showthread.php?t=838448
Everything went fine until I got to the point where im guessing it was suppose to boot into recovery mode but it didnt. Instead it stayed at the HTC logo for a while and booted up as normal..as so it seems. This is the log....so what do I do now?? The phone still works, but im not sure as to what i did..HELP!!!!
Starting ADB server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Checking MTD configuration...
Phone uses the old block size.
Firmware version '3.70.651.1'
Battery is at 77 percent.
The ADB Shell does not have root permissions.
Installing exploit...
Rooting...
Looking for Root...
Got Root!
Checking for needed files...
Pushing res\flash_image to /data/local/flash_image...
Pushing res\mtd-eng.img to /sdcard/mtd-eng.img...
Pushing res\URFSOFF.zip to /sdcard/URFSOff.zip...
Pushing res\URFSON.zip to /sdcard/URFSOn.zip...
Flashing misc partition...
Rebooting in to bootloader...
Verifying bootloader status...
Bootloader shows Firmware Version '1.17.651.1'
hbootpreupdate set at '11'
Verified the phone has the older MTD setup with hBoot Version '2.10.0001'
Verified NAND is locked.
Setting RUU mode...
*
* Flashing Firmware...
*
* It is very important that you do not interrupt this while flashing.
* Unplugging or turning the phone off while it is flashing can easily brick
* your phone.
*
Rebooting...
Waiting for the phone...
error: write failure during connection
** daemon still not runningerror: cannot connect to daemon
** daemon still not runningerror: cannot connect to daemon
** daemon still not runningerror: cannot connect to daemon
Just use unrevoked. Download and run the reflash package. This will give you root and NAND unlock/S-Off.
http://unrevoked.com/#evo
ducats said:
Just use unrevoked. Download and run the reflash package. This will give you root and NAND unlock/S-Off.
http://unrevoked.com/#evo
Click to expand...
Click to collapse
You shouldn't have any problems at all.
Simply follow the directions, and don't forget to install and uninstall HTC Sync prior to.
I downloaded the reflash program and ran it..seems like nothing is happening..the phone rebooted to the red exclamation mark screen with the phone icon been here for atleast 15 minutes.....on my pc, the evo 3 icon is in the traybar says: failed to push recovery:Termating
Recovery Image:CLockworkmod Recovery
the cmd.exe still says daemon still not runningerror.Cannot connect to daemon..
ugh
DO i wait? Restart? idk what to do
Put that on your sdcard and boot into the bootloader, select update, reboot, reboot back into recovery, and you'll have amon_ra 2.3. The triangle with the ! is the recovery but you have no recovery.
Oh..so what exactly do i put on the sd card? The reflash program? and is it safe to restart the phone?
Calico_NC said:
Oh..so what exactly do i put on the sd card? The reflash program? and is it safe to restart the phone?
Click to expand...
Click to collapse
No, the file I attached above, also do not extract it.
So how do I go about restarting the phone..Remove the battery? I dont think the power button functions to restart now.
I downloaded that zip file before but forgot to install it on my sdcard..silly me thanks
Calico_NC said:
So how do I go about restarting the phone..Remove the battery? I dont think the power button functions to restart now.
I downloaded that zip file before but forgot to install it on my sdcard..silly me thanks
Click to expand...
Click to collapse
You can restart the phone into bootloader by turning the phone off or battery pull. While the phone is turning back on, hold the vol+down button.
Put the file into the sdcard directory. Rebooted into recovery. I Didnt see the "update" item you referenced above. I did however see "recovery", selected it and now im back at the red exclamation mark. lol i dont know how long its suppose to stay on screen or if it suppose to be up there.
Also if i do this do i need to run any other programs? Like if i put the file in the sdcard..what next...do i need to run the reflash program from above? Im kind of confused
ok nvm i think the file i placed on the scdard was the wrong one..the one i placed in the sdcard was 202mb named (3.70.651.1_PC36IMG.zip) im guessing thats the wrong file
Did you rename the zip file? You didn't need to if so, because its supposed to scan and it will detect the PC36IMG file.
Yeah... it's a Very bad idea to start mixing different root methods when one is incomplete. Use the 3.70 RUU that can be found in the same thread you downloaded autoroot from before doing unrevoked. Although you'll probably need to stop whatever it is thats interfering with it before either will work.
Right now it just has old software on it, thats why it doesn't want to let you boot it.
Sent from my PC36100 using XDA App
ok ok ok so im confused now. Do I put the file on the sdcard that roxx attached..and boot into bootloader go to recovery? If so what about RUU or the other program mentioned. DO i run RUU over again? like im really confused on what now. With the two methods above im getting a little off track.I got all the right files downloaded but im not sure on what to do now.
and no i did not rename the file.
Go ahead and run the RUU. Boot the phone into fastboot from the bootloader, then connect to pc. Once fastboot usb is shown, then run the RUU exe.
teh roxxorz said:
Go ahead and run the RUU. Boot the phone into fastboot from the bootloader, then connect to pc. Once fastboot usb is shown, then run the RUU exe.
Click to expand...
Click to collapse
ok i ran the RUU phone is back to stock it looks like. Sprint startup etc.. now u said i should run the same ruu.exe in fastboot from the bootloader?
edit: Booted to bootloader, now its asking me do I want to start the update. Update? YAY? or NAY?
Does your phone says s-on or s-off?
s-on in the bootloader screen
You can try to apply the update. But after running the RUU you're unrooted, so you need to re-root first.
I think I have it now..no errors this time! Went through without an error. Fully rooted. Thanks everyone
No problem man.

[Q] Wildfire S [Marvelc] Stuck on opening update package

Hello all, for the past few days I have been trying to install android 4.0 ICS on my HTC Wildfire S CDMA phone, currently connected to youtube. on one instance I accidently formatted my backup so at this point im prettty scared.
I have already tried full resets, clearing memory, batttery, cache etc. I am stuck using CWM because TWRP touch screen doesnt seem to work at all. All help will be greatly appreciated. thank you.
I have also tried most of what is on other forums such as kernel update, redownloading.
I also find that if while installing, the phone restarts on its own. at first I thought the installation was done but to my dismay, it wasnt....
I'm not sure I can help but I would suggest you try to clarify what you are asking and trying to do. You state that you're doing an install of ICS 4.0 on your WFSc. I don't think any WFS, gsm or cdma got the ICS update unless you mean as Cyanogen Mod 9 or some other ROM? You also said something about being connected to You Tube now...that doesn't make sense.
That being said, if you meant you were trying to install the ICS theme then you might get a quicker more focused response if you posted in this forum:
http://forum.xda-developers.com/showthread.php?t=1504935
Clarification
I got a second wildfire s from my cousin. exact same model and was bought the exact time as my current one and it successfully installed the cynanogen 9 with the only failure being that the touchscreen is inoperable but I will work on that another time. also when I said connected to youtube, I meant I tried to look on youtube for fixes but never found one. anyway the main problem is that my phone stops midway through the "installin updates" to either freeze or restart to a blank operating system "meaning its stuck on the htc logo". I hope this clarifies what I was trying to convey in the previous post and I promise to keep a closer eye for any other messages. I also thank you for answering.
Instead of potentially aggravating you with 20 questions, I'll just briefly run thru the steps, FWIW. I see you mention CWM.
-So, you probably unlocked the booloader at HTC dev and are S-on.
-Installed CWM, so you have the adb files and htc sync on your computer.
-Rooted, although flashing CM will root.
-Battery charged.
-Downloaded the correct CM9 for your WFS, i.e., gsm or cdma, and moved it to your sd card after extracting the boot.img file and putting it into the folder on your computer with the adb, fastboot, etc. files for later.
-Booted into CWM and wiped the cache, dalvik-cache, and data/factory reset.
-Selected the CM9 file on your zip, and started the install.
I'm a little unsure what you are saying happens next, but normally you would:
-after CM9 is flashed go to fastboot in the bootloader or reboot into recovery>fastboot.
-Attach the USB cable from the computer to the phone and with the command prompt at that folder where you have those adb files type:
fastboot flash boot boot.img and press enter
-Then reboot and CM9 should load...unless now both of us have missed something ::yikes!::
For some reason most guides seem to skip that part about extracting the boot.img file and flashing it after the ROM install, which is needed if the phone is still S-on. Typically seen when stuck on the HTC logo after flashing the ROM and rebooting, and you mentioned being stuck on the HTC logo. If the phone is S-off, the boot.img gets flashed from within the ROM during the install.
Hope I found the missing step and that it installs successfully.
romemo two
MiCeltic said:
Instead of potentially aggravating you with 20 questions, I'll just briefly run thru the steps, FWIW. I see you mention CWM.
-So, you probably unlocked the booloader at HTC dev and are S-on.
-Installed CWM, so you have the adb files and htc sync on your computer.
-Rooted, although flashing CM will root.
-Battery charged.
-Downloaded the correct CM9 for your WFS, i.e., gsm or cdma, and moved it to your sd card after extracting the boot.img file and putting it into the folder on your computer with the adb, fastboot, etc. files for later.
-Booted into CWM and wiped the cache, dalvik-cache, and data/factory reset.
-Selected the CM9 file on your zip, and started the install.
I'm a little unsure what you are saying happens next, but normally you would:
-after CM9 is flashed go to fastboot in the bootloader or reboot into recovery>fastboot.
-Attach the USB cable from the computer to the phone and with the command prompt at that folder where you have those adb files type:
fastboot flash boot boot.img and press enter
-Then reboot and CM9 should load...unless now both of us have missed something ::yikes!::
For some reason most guides seem to skip that part about extracting the boot.img file and flashing it after the ROM install, which is needed if the phone is still S-on. Typically seen when stuck on the HTC logo after flashing the ROM and rebooting, and you mentioned being stuck on the HTC logo. If the phone is S-off, the boot.img gets flashed from within the ROM during the install.
Hope I found the missing step and that it installs successfully.
Click to expand...
Click to collapse
Thanks again for the reply. you have given me quite a lot of information and 90% of it was correct and dead on, but where you misunderstand is that while using CWM and flashing ANY Rom onto the phone, it either freezes at "installing updates" or restats if it ever gets to the next step. The confusing part of this is that the other phone which is the exact same model was able to be flashed with all the roms that I tried on my own phone with no problem.
To make things easier. after this I will adress the phones differently:
My phone (Not working Flash) is Marvelc 1
My cousins phone (working flash) is Marvelc 2
This is particularly challenging because you keep emphasizing that you are doing exactly what (you did?) on the other WFS, and I presume they have identical hboots (which they'd have to if you unlocked using htcdev). You also say that you re-downloaded the different files (recovery, CM9) and double checked that their for the MarvelC, and re-did then, re-tried, re-tried, re-tried...and I'm presuming that when you were re-trying that you didn't skip any steps, like the wipes. Oh, and most of all that everything worked on this phone before you started unlocking - flashing the recovery - and rooting. I thought about htc sync and adb, but the fail point is not when the computer is hooked up.
So all that being re-hashed, I'm looking for something concrete, a clue from what you've said or hinted at and right now I'm curious about your SD card. That is most likely not common to both phones and you did say, "on one instance I accidently formatted my backup..." Did you get everything formatted OK with no errors...that SD especially, as Fat32, shouldn't need an ext partition at this time. It could be corrupted and failing at some point when it's unpacking CM9, or whatever. You might re-do formatting that, including doing it on a computer if you have an adapter or a card reader, if not in CWM. It wouldn't hurt to put it in another phone and see if you can read it there and/or on a computer when that other phone is hooked up as a disk drive. Then put a fresh copy of whichever CM9 your flashing on it and try EVERYTHING one more time (back in your phone of course) ::haha:: be sure to leave the battery out for at least 30 sec. after all this and before trying the flash just to be sure any residual static in the phone has dissipated.
If it fails again, leave on and hook up to the computer and run: "adb logcat" from the prompt where you have your adb files and see if it will show you anything. You can exit logcat with the Ctrl + C keys. What do you think?
Oh, and while you're doing all that, who's CM9 are you trying to install. Do you have a link so I can look at it out of curiosity?
It took me awhile to absorb all that but after trying all.those steps,.there was no progress. Furthermore the microsd card I use is for both of my HTC's. And lastly the adb logcat or any adb script for that matter won't work unless the phone is in debug mode with a working o.s.
Thanks for hanging with me and I look forward to your next suggestion.
Sent from my HTC-PG762 using xda app-developers app
I wasn't sure whether there would be some kind of script running in a buffer of the install that might be captured with something like: logcat -b event > /sdcard/logcat.txt
so it was a shot in the dark and I don't know what's left, but perhaps someone else that is reading the post might have some ideas, or experience with this specific issue and jump in with a solution.
I was writing a macro once and couldn't get it to work and spent too much time over 3 days trying to figure it out. When I finally asked someone else to look at it, I was just missing a semi-colon or some one simple thing. You sound pretty knowledgeable, sorry I couldn't be the second set of eyes to come up with the missing thing. If I can think of anything more, I'm subscribed to this thread and I'll surely suggest it.
Thank you for trying, I hope to find an answer soon enough.
Sent from my HTC-PG762 using xda app-developers app

HTC One M9 Down - Need Help

HI all. I am in serious need of help please.
My wifes M9 is stuck on a screen with only a backlight. How this came about is after several failed attempts of updating the system via Wi-Fi. South Africa does not have a RUU available and only over the air updates are available
After about 2 days on the net, searching and reading and trying and failing I have determined the following.
What I have tried
1. Boot to Bootloader and tried recovery. This give me an Error - "Failed to boot to recovery"
2. Tried a Official RUU from HTC, this failed due to CID - Error wrong Customer ID
3. Learned a bit of ADB but this is no use as It seems USB debugging is disabled on the phone
4. Tried Custom ROM's via the SD card but this is blocked as the phone is **Locked** and **S-On**
5. Fastboot sees the phone as I can push reboot commands but because of locked status I can not do much
6. I can not get a unlock token as OEM is locked and this must be unlocked for ADB command to get token to get unlock.bin from HTCDEV
Basically it seems like I am at a dead end as it appears that I need to get into a boot status to enable debugging and enable developer mode from phone settings to be able to work from ADB
So here is the Million dollar question, How can I "wipe" the phone with a SD card boot image/loader or does any one know of a RUU-.exe for South Africa CID_016 that I could flash the phone with or possibly any other methods to get a ROM on it that we can use it again
I repeat, phone goes to blank screen with only backlight after HTC Logo, S-on, USB debugging seems to be disabled and it is in Locked status. I am able to boot in download mode and bootloader and fastboor does see the device. ADB devices does not see the phone, even after trying loads of different drivers, ADB USB ADB Interface etc etc
Please I need help
I'm suffering from the same fate. Except I had rooted it before, then I tried to update it to 5.1 and I relocked my bootloader. Android 5.1 loaded successfully but it got stuck while booting and now I can't unlock my bootloader. I have tried EVERYTHING!
https://www.google.com/url?q=https:...261000&usg=AFQjCNEBlBxkVmymaiJO1eaxKcHsKsE-wg
1.download this zip file
2. Rename the file to 0PJAIMG.zip (zero not O)
03. Copy the file to the root directory of a SD card which is formatted to fat32
04. Put the card into your phone and boot to Download Mode.
05. You will be asked whether you want to flash the file. Confirm with the volume up button.
06. Your phone will reboot at least one time. Depending on your current firmware version it may reboot to Android instead of rebooting to Download Mode. If this happens you just need to shut your phone down and manually boot it to Download Mode.
07. Flashing may take some time.
08. At the end you will be asked to push the power button. You phone will shut down if you do so.
09. Wait some seconds and then turn your phone on, again.
10. First boot may take a while.
11. Congrats! thanks to flippy
YES!!! OP I tried this and it works!!! My phone is finally alive again thanks to flippy's instructions.
Maybe I missed it, but I spent an entire day yesterday trying to find THIS solution. I didn't know it was this particular one, but I would have tried it first if I could have found it somewhere obvious. It really should be stickied as a "How to unscrew what though hast screwed"!
Thank you so much for taking the time to answer this Degerli43! I know virtually every answer possible is available on this forum, but finding it is the trick!
Note to anybody else doing this, be sure to locate the correct image file for your provider and area, as the link above and the one below may not be the correct one for you. I am a T-Mobile US customer and used this one -
https://www.androidfilehost.com/?w=...6ce7fb817fc1524b58f67fe05270f032107d2306abcd4
This worked perfectly after I could not boot or enter TWRP recovery. Anybody who can still access Android Recovery the Downloader should be able to use it to get un-bricked to a clean carrier state if the image file will take.
ksnax said:
Maybe I missed it, but I spent an entire day yesterday trying to find THIS solution. I didn't know it was this particular one, but I would have tried it first if I could have found it somewhere obvious. It really should be stickied as a "How to unscrew what though hast screwed"!
Click to expand...
Click to collapse
Did you ever visit the general section? :silly: There's a sticky thread with stock files and linked instructions for recovering TWRP backups and flashing RUUs. Read the OP, follow it's instructions to my google sheet and you will see where the steps that helped you out are taken from.
Sent from my HTC One S using XDA Labs

HTC One M8s propably bricked HELP GUYS

Hi,
i just got an HTC One M8s and i think its propably bricked. I don't know whats owner of that phone done here. Its Software status : Modified, Bootloader: Locked, and S-ON.
I can't turn on the phone, i just can go to bootloader option and cant access recovery bc its popably didn't exist anymore.
I was trying to flash RUU for my CID T-MOB009 but htc_fastboot says "data length is too large" and sometimes "remote:signature verify fail", and i was trying to unlock this bootloader with HTCDev, but when i clicked yes it looks like that(means 1st photo) and just reboot to fastboot in bootloader and it's still locked
Is there's a way to unbrick this phone ? I just spend like 4 hours of trying some tips but it doesn't work for it.
Some screens (remove spaces cause i can't post link before 10posts):
s14.postimg .org/b35qjqt6p/DSC_0001_1.jpg
s22.postimg .org/iiihlx2tt/DSC_0002_1.jpg
image.prntscr .com/image/85f19f6602fe4776b993affe62e959c1.png
Please understand my bad english, it's not my primary language
Mikkal said:
Hi,
i just got an HTC One M8s and i think its propably bricked. I don't know whats owner of that phone done here. Its Software status : Modified, Bootloader: Locked, and S-ON.
I can't turn on the phone, i just can go to bootloader option and cant access recovery bc its popably didn't exist anymore.
I was trying to flash RUU for my CID T-MOB009 but htc_fastboot says "data length is too large" and sometimes "remote:signature verify fail", and i was trying to unlock this bootloader with HTCDev, but when i clicked yes it looks like that(means 1st photo) and just reboot to fastboot in bootloader and it's still locked
Is there's a way to unbrick this phone ? I just spend like 4 hours of trying some tips but it doesn't work for it.
Some screens (remove spaces cause i can't post link before 10posts):
s14.postimg .org/b35qjqt6p/DSC_0001_1.jpg
s22.postimg .org/iiihlx2tt/DSC_0002_1.jpg
image.prntscr .com/image/85f19f6602fe4776b993affe62e959c1.png
Please understand my bad english, it's not my primary language
Click to expand...
Click to collapse
Yeah maybe there's a problem with the "Security warning" it shouldn't be there. What you can do is to reflash the RUU. But not with fastboot but from your sdcard.
Probably this is the firmware that you should use. I'm not sure though you can go one directory back and search for another one if that doesn't suit to you.
Now to flash it follow the steps
1) Download it and if you can check the md5sum so as to ensure it has downloaded correctly.
2) Rename it to 0PKVIMG.zip (note the first character is a zero and not a O
3) Take out the sdcard of your phone.
4) Insert it on your pc and format it to Fat32 or exfat.
5) Copy the above file into your sdcard.
6) Power off your phone and insert the sdcard
7) Go into the bootloader mode. It should automatically detect the firmware
8) When it asks you if you want to install choose "Yes"
9) Wait until it is done. It will flash multiple times the system partion. WAIT patiently
10) Hope that fixed it!
PS: When you enter fastboot you probably see some green letters. This means the hboot is searching for the software file i said above. If it finds it's ok. I had problems copying the file with windows though.
root-expert said:
Yeah maybe there's a problem with the "Security warning" it shouldn't be there. What you can do is to reflash the RUU. But not with fastboot but from your sdcard.
Probably is the firmware that you should use. I'm not sure though you can go one directory back and search for another one if that doesn't suit to you.
Now to flash it follow the steps
1) Download it and if you can check the md5sum so as to ensure it has downloaded correctly.
2) Rename it to 0PKVIMG.zip (note the first character is a zero and not a O
3) Take out the sdcard of your phone.
4) Insert it on your pc and format it to Fat32 or exfat.
5) Copy the above file into your sdcard.
6) Power off your phone and insert the sdcard
7) Go into the bootloader mode. It should automatically detect the firmware
8) When it asks you if you want to install choose "Yes"
9) Wait until it is done. It will flash multiple times the system partion. WAIT patiently
10) Hope that fixed it!
PS: When you enter fastboot you probably see some green letters. This means the hboot is searching for the software file i said above. If it finds it's ok. I had problems copying the file with windows though.
Click to expand...
Click to collapse
Yeah thanks for that great advice man! Unfortunately i was trying to copy this on Windows and when i try to Hboot that it just skip process (but stops for sec on a 0PKVIMG.zip) and going back to bootloader. Any advice how to do that properly on windows ? I checked md5 on sd card and its the same as on my computer disk and same as on this site what youre sent to me . Thanks for replies
Mikkal said:
Yeah thanks for that great advice man! Unfortunately i was trying to copy this on Windows and when i try to Hboot that it just skip process (but stops for sec on a 0PKVIMG.zip) and going back to bootloader. Any advice how to do that properly on windows ? I checked md5 on sd card and its the same as on my computer disk and same as on this site what youre sent to me . Thanks for replies
Click to expand...
Click to collapse
I couldn't get it that done on windows. Dunno what's going wrong. Hopefully i had a linux distro installed and i copied the file from there. Maybe you can do that.
If you haven't installed any linux then create a live cd and boot it up.
root-expert said:
I couldn't get it that done on windows. Dunno what's going wrong. Hopefully i had a linux distro installed and i copied the file from there. Maybe you can do that.
If you haven't installed any linux then create a live cd and boot it up.
Click to expand...
Click to collapse
Okay so now its the trick. I have done copied that properly, bc it start to loading when i put sd card. I click yes for update, and its start to flashing. Some of first steps failed so it wasn't look good. It called ROM failed to flashed click POWER to restart, and when i clicked it phone goes off and now its propably close to hardbricked cause i cant turn on bootloader. When i take it to charger there is no battery on screen informating its already charging. Only LED is working when charging and sound on windows when plug it on and off. Any suggestions guys? I'am scared now
Similar situation
Hi,
I appear to be in a similar situation with my M8 that I tried to convert to GPE. Something went wrong and although the ROM booted, I kept getting told my data was corrupt or encrypted... Tried a few reboots, and refreshed but still got the same...
A thread on here suggested formatting one of the partitions from TWRP which just returned an error, since then the phone appears to be 'hard bricked'.
No display, no charging indication, not recognised in ADB, and I can't force boot into recovery or fast boot.
However, I do still get the notification sound when I plug it into my PC...
It appears in the Device Manager as Qualcomm Mass Storage Device, and Windows shows ~20 drives most of which are unformatted, a few of which seem to contain system info...
I was wondering, would it be possible to re-image the Device? Given that the PC recognises the partitions, would anyway know what -should- be on them?
Alternatively, can anyone provide an image of a stock drive, partitions etc which I could apply?
Apologies if this is nonsense, but I'd imagine the reason it can't boot is the Bootloader partition is 'missing' or corrupted.
The same may be true for your device Mikkal.
Thanks in advance,
Mikkal said:
Okay so now its the trick. I have done copied that properly, bc it start to loading when i put sd card. I click yes for update, and its start to flashing. Some of first steps failed so it wasn't look good. It called ROM failed to flashed click POWER to restart, and when i clicked it phone goes off and now its propably close to hardbricked cause i cant turn on bootloader. When i take it to charger there is no battery on screen informating its already charging. Only LED is working when charging and sound on windows when plug it on and off. Any suggestions guys? I'am scared now
Click to expand...
Click to collapse
Exactly the same problem here, I followed the same steps as you, and had same errors as you.. Is there any help for this?
funjai said:
Exactly the same problem here, I followed the same steps as you, and had same errors as you.. Is there any help for this?
Click to expand...
Click to collapse
What is your CID , software version
No idea mate.. I can't turn on the phone so I can't check that..
For those who can't flash a RUU, unlock the bootloader install TWRP recovery, and install a custom ROM. Voila!
LoneWolfO2Se said:
For those who can't flash a RUU, unlock the bootloader install TWRP recovery, and install a custom ROM. Voila!
Click to expand...
Click to collapse
Oh really? You never noticed that there are no custom roms for M8S ?
funjai said:
Oh really? You never noticed that there are no custom roms for M8S ?
Click to expand...
Click to collapse
You sure about that ?
Hi can you paste info from your phone use this command in fasboot
fastboot getvar all
also tell me what software did you try to flash
Regards

Categories

Resources