I have have an htc amaze that is not soff or bootloader unlocked rmember it not .Tbad thing is my volume - button does work it wont let me boot into the bootloader mode to use the recover so i tried to use a regular Ruu to flash the phone . Once it got done it says please get the right update utility and retry flashing. Another thing is my memory card hasn't been working it stoped a month ago . I have been using this RUU RUU_Ruby_Globalive_WWE_1.46.1500.3_Radio_1.10.550L.01v2DC_30.69.550L.10_release_229312_signed
i know its not tmobile but hey on the stickies i dont see one for tmobile AS AN EXE file. If i plug in the phone and flash it i can get into what looks like the bootloader mode but wont let me do anything except for reflashing the phone. Im thinking i can only try to use an original ruu thats a tmobile version, BTW last operating installed was ice cream so that is what i have installed.
1 phone is stock
2 my volume - does not work (cant boot into bootloader )
3 memory card does not work
What?
I can't tell what you are trying to do here, but if it's a question this is the wrong place
Sent from my HTC_Amaze_4G using xda premium
Umm. If I understood right, you should be able to use adb commands to get into bootloader and everything without needing volume buttons. To be honest though is it your memory card? Or the phone won't read them, because if volume buttons aren't working and memory cards aren't either I'd be calling tmobile/htc
Edit: I don't know the adb commands offhand but Google should be able to help you find what you need or this forum could provide the info you need just look around.
Sent from my HTC_Amaze_4G using xda app-developers app
im trying to restore my phone to a working condition this is my problem look, the other thing is when i write comand adb shell it says device not found ????????
i have several phones rooted aside from this phone
my touch 4g
htc vivid
one x
inspire
all working fine
skylinegtrvspec said:
im trying to restore my phone to a working condition this is my problem look, the other thing is when i write comand adb shell it says device not found ????????
i have several phones rooted aside from this phone
my touch 4g
htc vivid
one x
inspire
all working fine
Click to expand...
Click to collapse
Try this command:
fastboot devices
and then tell me if you get a serial number.
ok it sees my device sorry and yes there is a serial number
skylinegtrvspec said:
ok it sees my device
Click to expand...
Click to collapse
Alright, do you have a T-Mobile RUU downloaded? If so, can you tell me where you got it from? I want to verify that you have the right version of the RUU.
I'm going to write a quick program that'll flash the RUU through USB cable, so please wait. If you haven't got the RUU, then please get the correct RUU while I write the script.
RUU:
http://d-h.st/3VD
Be sure to thank Krook6023 for providing this RUU
RUU_Ruby_Globalive_WWE_1.46.1500.3_Radio_1.10.550L .01v2DC_30.69.550L.10_release_229312_signed ive used it once before and it worked now this time it wont . Te ruu that i got was from here
http://forum.xda-developers.com/showthread.php?t=1617644
skylinegtrvspec said:
RUU_Ruby_Globalive_WWE_1.46.1500.3_Radio_1.10.550L .01v2DC_30.69.550L.10_release_229312_signed ive used it once before and it worked now this time it wont . Te ruu that i got was from here
http://forum.xda-developers.com/showthread.php?t=1617644
Click to expand...
Click to collapse
You need a T-Mobile RUU. Download the one I gave you the link to in my last post.
I am, its downloading
skylinegtrvspec said:
I am, its downloading
Click to expand...
Click to collapse
While you wait, could you do a quick fastboot command to prepare for my script?
The command is:
fastboot erase cache
That's all.
When you're done downloading, let us know and then I'll post the script to flash the RUU.
Additional Instructions:
When it's done downloading, please rename the file to PH85IMG
If you do not, the script WILL not work.
ok i will ,its almost done like 5 mins left
ok ready File has been renamed to PH85IMG
and fastboot erase cache has cleared the cache all done
skylinegtrvspec said:
ok i will ,its almost done like 5 mins left
ok ready File has been renamed to PH85IMG
and fastboot erase cache has cleared the cache all done
Click to expand...
Click to collapse
Alright, I've attached the tool. All you need to do is extract the script, and then put the batch file to your desktop. Also, put the PH85IMG.zip file to your desktop, but DO NOT extract it!
After that's done, double click on the RUUFlasher.bat file, and it should automatically start the process. Please make sure your phone is connected to your computer before running the script.
This will take up to 10 minutes, and after it's done, it will reboot your phone, and your phone should be up and running again!
Please post if you get any errors or issues, or just questions about this.
Good Luck!
Just want to know if your phone is a T-Mobile Amaze or not?
Double0EK said:
Just want to know if your phone is a T-Mobile Amaze or not?
Click to expand...
Click to collapse
Look at the picture. It has the T-Mobile logo emblazoned on the top.
did not work ,this is what i did
1 dowlonded the file and did like you said i extract it to the desktop
2 placed the other file PH85IMG in the desktop
3 ran the batch file it started then it stoped nothing happend
skylinegtrvspec said:
did not work ,this is what i did
1 dowlonded the file and did like you said i extract it to the desktop
2 placed the other file PH85IMG in the desktop
3 ran the batch file it started then it stoped nothing happend
Click to expand...
Click to collapse
Give it a minute. It's checking for connection. Try again.
nothing weird ????
look at what i was able to catch, it says fastboot is not recognized as an internal or external command operable program or batch file
i figured out the problem
now the app is working the problem was i did not have in the directory where the fastboot was
it failed look
Device detected!
Now entering RUU mode...
...
(bootloader) Start Verify: 3
(bootloader) Start Verify: 3
(bootloader) erase sector 130560 ~ 131071 (512)
OKAY [ 3.443s]
finished. total time: 3.443s
Now flashing the update! Hang on there!
This will take up to 10 minutes to complete!
DO NOT TOUCH YOUR PHONE!!!
DO NOT UNPLUG THE USB CORD!!!
DO NOT TOUCH ANYTHING!!!
sending 'zip' (498144 KB)...
OKAY [ 57.602s]
writing 'zip'...
(bootloader) adopting the signature contained in this image..
(bootloader) signature checking...
FAILED (remote: 92 supercid! please flush image again immedia
finished. total time: 144.140s
RUU flashed!
The program will now reboot your phone!
Please wait!
Script made by Keylogger_0
Good Luck!
DO NOT CLOSE THIS WINDOW, AS IT MAY
CONTAIN IMPORTANT DIAGNOSTIC INFORMATION!
rebooting...
finished. total time: 3.206s
DO NOT CLOSE THIS WINDOW, AS IT MAY
CONTAIN IMPORTANT DIAGNOSTIC INFORMATION!
Related
This is a tutorial to revert to 100% stock as like when you bought your phone! Read the whole entire thing before you start!
1)Download the RUU here:
http://www.multiupload.com/2QWMDPG2M8
2)Copy to the root of your sd card
3)Boot into bootloader by either using quickboot from market or pulling battery and holding power+volume down until you see bootloader.
4)Bootloader will scan for PG86IMG
5)Click power button to select install for the file
6)Bootloader will now install, you are now on the stock sprint ROM
7)Now plug your device in, and navigate to the fastboot setting from the menu and select it(power button)
8)Open CMD with the fastboot files in with the adb files
9)Run the command "fastboot oem writesecureflag 3" without quotes
10)You should now be 100% stock unrooted and s-on!
Included is the fastboot and adb files, when you get to step 7 run the start here, and get into fastboot on your phone either through bootloader or typing 'adb reboot bootloader' while having your phone on charge only mode. then continue on your way to s-on
Download fastboot and adb files here:
http://www.mediafire.com/?90scvyi9a94cq
*Remember never do this with the eng hboot, you could brick, only do this on ship hboot!
I am not responsible for anything that happens to your device!
Maybe someone can convert this into a flashable zip that would automatically do the steps for you?
Thanks!
Updated !
Good job! I bet this will be of use.
Like my help? Thank me
Just so you know I posted a very "similar" thread hours ago: http://forum.xda-developers.com/showthread.php?t=1193540
I didnt have the fast boot command in my instructions. Thanks for pointing that out! Its been a very long weekend so far. Havent slept since release... lol
The flashable zip is a good idea. I bet we will see a new thread soon, lol
Sorry, I didn't notice, and I bet we will, hopefully.
Sent from my 3devo...s-off can run but you can't hide!
The more the better.
Added to my complete list thread: http://forum.xda-developers.com/showthread.php?p=16132451
so um i couldnt get this to work i went in to fastboot on phone opened cmd window dir to location of fastboot typed in the command and it just says command error
lopez62 said:
so um i couldnt get this to work i went in to fastboot on phone opened cmd window dir to location of fastboot typed in the command and it just says command error
Click to expand...
Click to collapse
make sure you type it in exactly, do you have adb setup right?
ok so i'm an idiot. i spent all this time waiting and waiting for s-off. now that it's here i went flash crazy over the last 18 hours. about ten minutes ago i had my phone on charge, it slipped out of my hand as i was taking the cable out and it landed on the cable still half in the charging port with the internals of a microusb sitting cockeyed in there and the plastic piece from the phones usb port was jammed into the cable's port. so here's my predicatment.... i need to get back to stock and s-on without adb. any ideas at all? if not i'm going to literally kick it to/on the curb and take it back to best buy tomorrow. i have to make sure that they don't try and keep my phone for a month while they "repair" it.
Thanks!!! i was waiting for someone to come out with a tut..
I'm pretty sure adb is setup right I been using it since the HTC vogue days....Idk what I'm doing wrong I guess ill just have to wait and see in the coming days....
Sent from my HTC EVO 3D using the XDA Premium App!
You have ship hboot right
Sent from my rEVOlutionary 3D
rtbluver said:
You have ship hboot right
Sent from my rEVOlutionary 3D
Click to expand...
Click to collapse
who are you talking to?
Ok... I have fastboot.exe, adb.exe and adb files in the platform-tools directory. So do I navigate to the platform-tools folder or tools folder in the CMD prompt to run the fastboot command? Thanks in advance for the help... Apologize for the noobness...
Only thing I'm not getting is how to do the s-on part, maybe I'm overlooking something but can u explain that a little better? I can't make any texts and phone calls keep saying "error number 16" ever since I ran the revolutionary root and s-off process so I'm trying to at least go back to full stock in case I need to take it in
Cool! I will keep this handy for when I need to swap out parts with my Sprint Techy friend.
WyldOne91 said:
Only thing I'm not getting is how to do the s-on part, maybe I'm overlooking something but can u explain that a little better? I can't make any texts and phone calls keep saying "error number 16" ever since I ran the revolutionary root and s-off process so I'm trying to at least go back to full stock in case I need to take it in
Click to expand...
Click to collapse
your problem is very common. simply call in to sprint and they can fix it on their end with the error 16. they shouldn't ask and you don't need to tell them you rooted, it's simply a provisioning issue. your phone is fine.
trying to set s-on and get this error message on CMD prompt:
(bootloader) [ERR] Command error !!!
OKAY [ 0.008s]
finished. total time: 0.008s
any ideas?? i noticed when i ran the PG86IMG file it downgraded the hboot to 1.30...
will survive said:
trying to set s-on and get this error message on CMD prompt:
(bootloader) [ERR] Command error !!!
OKAY [ 0.008s]
finished. total time: 0.008s
any ideas?? i noticed when i ran the PG86IMG file it downgraded the hboot to 1.30...
Click to expand...
Click to collapse
I will play with it, its stock ruin, maybe a bad diwnload?
Sent from my rEVOlutionary 3D
p3tr0s said:
ok so i'm an idiot. i spent all this time waiting and waiting for s-off. now that it's here i went flash crazy over the last 18 hours. about ten minutes ago i had my phone on charge, it slipped out of my hand as i was taking the cable out and it landed on the cable still half in the charging port with the internals of a microusb sitting cockeyed in there and the plastic piece from the phones usb port was jammed into the cable's port. so here's my predicatment.... i need to get back to stock and s-on without adb. any ideas at all? if not i'm going to literally kick it to/on the curb and take it back to best buy tomorrow. i have to make sure that they don't try and keep my phone for a month while they "repair" it.
Click to expand...
Click to collapse
Use adbwireless from the market and you can use adb over wifi
will survive said:
trying to set s-on and get this error message on CMD prompt:
(bootloader) [ERR] Command error !!!
OKAY [ 0.008s]
finished. total time: 0.008s
any ideas?? i noticed when i ran the PG86IMG file it downgraded the hboot to 1.30...
Click to expand...
Click to collapse
This is exactly what I was getting when I ran this. I don't know what to do.
for some reason today i started getting random reboots here and there. when i got home i decided to wipe my phone and do a clean install. everything went well, successful wipe and complete flash of the rom, but when it restarted after the flash it was still the same as before. nothing changed, all my apps, wallpaper, settings everything had been untouched. i even did fastboot wipe userdata. it was like i didnt do anything at all. then i tried wiping my internal sd card, same thing successful wipe, but it all comes back again. i did it a couple of times from the phone settings and also from my computer. then i flashed the ruu from the bootloader, everthing flash normal but when it restarted nothing changed. also tried changing my recovery to cwm but that didnt work either. tried flashing the eng bootloader and it said fail-pu.
right now im running energy rom june 19th, 4 ext recovery, joupunutbear 1.93.2222
any help or advise would be great.
msndroid said:
for some reason today i started getting random reboots here and there. when i got home i decided to wipe my phone and do a clean install. everything went well, successful wipe and complete flash of the rom, but when it restarted after the flash it was still the same as before. nothing changed, all my apps, wallpaper, settings everything had been untouched. i even did fastboot wipe userdata. it was like i didnt do anything at all. then i tried wiping my internal sd card, same thing successful wipe, but it all comes back again. i did it a couple of times from the phone settings and also from my computer. then i flashed the ruu from the bootloader, everthing flash normal but when it restarted nothing changed. also tried changing my recovery to cwm but that didnt work either. tried flashing the eng bootloader and it said fail-pu.
right now im running energy rom june 19th, 4 ext recovery, joupunutbear 1.93.2222
any help or advise would be great.
Click to expand...
Click to collapse
The outlook isn't good, sorry to say that. Most likely, the internal memory chips have failed. Basically, it won't write anymore on it, meaning what you have on it right now may be stuck, permanently. This is because of the "Fail-PU" error. Before doing anything like the wire trick below, try to ensure that the RUU you're trying to flash is a correct one. It would be great if you could get a picture (or describe) what it says when the ruu flash is done. But since you have problems wiping, this may not be the issue. Try the wire trick, as described below with caution.
Unfortunately, there isn't much you can do. I've heard that sometimes if you do the wire trick, it can temporarily fix the error. Heed this. Do the wire trick on its own, meaning do not connect the phone to a computer, or run the Juopunutbear's S-OFF program, or anything of that nature. Just do the exact same wire trick (same timing too) you did to obtain s-off, but without using the s-off program, or plugging it in the computer.
Keep us updated if that trick works for you.
It would also be a good idea to flash a RUU after doing the wire trick (again, without the s-off program, or plugging it in the computer!!!)
Again, best of luck!
this is what came up.
i used this ruu
http://d-h.st/z70
msndroid said:
this is what came up.
i used this ruu
http://d-h.st/z70
Click to expand...
Click to collapse
Have you tried the trick i mentioned earlier and then flashing the RUU?
yes, i've tried it a couple of times. ill try again in the morning but i think its a lost cause though. thanks for your help.
msndroid said:
yes, i've tried it a couple of times. ill try again in the morning but i think its a lost cause though. thanks for your help.
Click to expand...
Click to collapse
theres another thing you could try too.
Boot into fastboot and then type in this command:
fastboot oem boot
Pull out your battery
Put back in.
Flash the RUU
Keylogger_0 said:
theres another thing you could try too.
Boot into fastboot and then type in this command:
fastboot oem boot
Pull out your battery
Put back in.
Flash the RUU
Click to expand...
Click to collapse
no good. i pulled the battery as soon as the htc screen came on and also when the boot animation started. still getting the same results with the ruu.
i noticed this though. isnt it supposed to be bootloader instead of misc?
INFOaARM_Partion[0].name=misc
I'm assuming you know how to use fastboot, flash your stock SHP or ENG hboot via fastboot via:
fastboot erase cache
fastboot rebootRUU
fastboot flash zip en_hboot.zip
Place the attached zip of choice be it sh or en in your adb folder and try those commands, let me know your results.
If he flashes eng hboot, redownloads ruu to ensure good download, and try flashing ruu in bootloader again... I bet it would work
Sent from my HTC VLE_U using Tapatalk 2
msndroid said:
no good. i pulled the battery as soon as the htc screen came on and also when the boot animation started. still getting the same results with the ruu.
i noticed this though. isnt it supposed to be bootloader instead of misc?
INFOaARM_Partion[0].name=misc
Click to expand...
Click to collapse
Actually, I checked it out for my phone with fastboot oem boot too. It lists the partition 0 being the misc partition too. So I think that's fine. My device is fully functional (wipe/flash capabilities included) *knocks on wood* so I think that partition is normal.
Dark Nightmare said:
I'm assuming you know how to use fastboot, flash your stock SHP or ENG hboot via fastboot via:
fastboot erase cache
fastboot rebootRUU
fastboot flash zip en_hboot.zip
Place the attached zip of choice be it sh or en in your adb folder and try those commands, let me know your results.
Click to expand...
Click to collapse
tried both and it gave me this....
C:\adb>fastboot flash zip sh_hboot.zip
sending 'zip' (396 KB)... OKAY [ 0.246s]
writing 'zip'... FAILED (remote: not allowed)
finished. total time: 0.563s
To be honest I think the emmc chip although it's s-off it thinks its still s-on, my best guess would be to try s-off again, see what happens.
Sent from my SGH-T679 using xda app-developers app
msndroid said:
tried both and it gave me this....
C:\adb>fastboot flash zip sh_hboot.zip
sending 'zip' (396 KB)... OKAY [ 0.246s]
writing 'zip'... FAILED (remote: not allowed)
finished. total time: 0.563s
Click to expand...
Click to collapse
Boot into fastboot, and then type in this command
fastboot oem readsecureflag
This command should return with a value of 0
If not, let us know.
Keylogger_0 said:
Boot into fastboot, and then type in this command
fastboot oem readsecureflag
This command should return with a value of 0
If not, let us know.
Click to expand...
Click to collapse
yup thats what i got.
C:\adb>fastboot oem readsecureflag
... INFOsecure_flag: 0
OKAY [ 0.007s]
finished. total time: 0.007s
I kinda gave up on the phone. Ill just buy a galaxy nexus by the end of the month. But if there's still any suggestions I can do to try to fix it, I'm willing to do so, just incase it happens to someone else. Thanks for helping.
Sent from my myTouch_4G_Slide using xda app-developers app
msndroid said:
I kinda gave up on the phone. Ill just buy a galaxy nexus by the end of the month. But if there's still any suggestions I can do to try to fix it, I'm willing to do so, just incase it happens to someone else. Thanks for helping.
Sent from my myTouch_4G_Slide using xda app-developers app
Click to expand...
Click to collapse
You could try to claim warranty, but the thing is, it's already modified so most likely, they won't touch it. A fail-pu error usually means a hardware failure. Most likely, your chip failed and will not write any more.
Another thing you could try to do is brick it, and then claim warranty. You can always say that it turned off and never turned on again.
Keylogger_0 said:
You could try to claim warranty, but the thing is, it's already modified so most likely, they won't touch it. A fail-pu error usually means a hardware failure. Most likely, your chip failed and will not write any more.
Another thing you could try to do is brick it, and then claim warranty. You can always say that it turned off and never turned on again.
Click to expand...
Click to collapse
The warranty is not the same as the tmobile insurence is it? Because I took that off thinking I wouldn't need it. Also stupid question, how would I go about bricking it?lol
Sent from my myTouch_4G_Slide using xda app-developers app
msndroid said:
The warranty is not the same as the tmobile insurence is it? Because I took that off thinking I wouldn't need it. Also stupid question, how would I go about bricking it?lol
Sent from my myTouch_4G_Slide using xda app-developers app
Click to expand...
Click to collapse
HTC usually has warranty too. The thing is, they will most likely refuse it if you have modified the phone.
Bricking can be easy. But, bricking with a Fail-PU error isn't always easy.
PM me later, and I will try to assist you. I'm a bit busy right now so just send me a PM to remind me.
Keylogger_0 said:
HTC usually has warranty too. The thing is, they will most likely refuse it if you have modified the phone.
Bricking can be easy. But, bricking with a Fail-PU error isn't always easy.
PM me later, and I will try to assist you. I'm a bit busy right now so just send me a PM to remind me.
Click to expand...
Click to collapse
Will do. Thanks I appreciate it
Sent from my myTouch_4G_Slide using xda app-developers app
Hi,
I'm having similar issue with my phone, tried a lot of things when I enter command
fastboot oem readsecureflag
I'm getting this:
(bootloader) secure_flag: 3
OKAY [ 0.010s]
finished. total time: 0.011s
If anybody is still checking that thread appreciate any help.
Thanks.
So I know I'm a dumb ass but here's what happened:
HTC Rezound S-off
Amon Ra 3.15
Hboot 2.27
ViperRez 1.0.3
My phone was acting a little buggy and my friend kept telling me I should flash a firmware update so I flashed
this " PH98IMG-firmware.zip - 33.02 MB " from here: http://forum.xda-developers.com/showthread.php?t=1835811&highlight=ruu&nocache=1
I checked the MD5 when I dl'd to PC BUT not when I copied to sd card. When flashing, all steps were successful except for 2: MDM9K - FAIL-UZ & RADIO_V2 - FAIL-UZ
I rebooted and got stuck at the white HTC screen. Battery pop and I tried to flash again. This time almost everything returned -- FAIL-PU except for the two above which still said FAIL-UZ.
Adding insult to injury I tried flashing two more RUU's from android police, I have a screenshot attached of one of my failed attempts.
ADB Devices doesn't recognize my phone but FASTBOOT devices returns a serial number. Boot loader also changes from " fastboot" to "fastboot-usb" when I plug into a PC but my PC doesn't see my phone.
I think it was a corrupted RUU because I decided to check the MD5 of a RUU on my sd card after the damage was done and it was bad. I then copied the same file over to my sd card a bunch of times, checking each MD5 and more than half the time they were bad.
I appreciate any suggestions anyone might have.
Sorry, thought I was in the Q & A section. (I already said I was a dumb ass)
Try this one http://forum.xda-developers.com/showthread.php?t=1835039
Sent from my ADR6425LVW using xda app-developers app
Thanks Squirrel...tried that one. That's actually the RUU that I ran for the screenshot. I think the problem has to do with updating my partition in the internal memory.
Squirrel1620 said:
Try this one http://forum.xda-developers.com/showthread.php?t=1835039
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
I tried flashing in fastboot...heres what I got:
c:\mini-adb_vigor>fastboot devices
HT19RS207848 fastboot
c:\mini-adb_vigor> fastboot -w update rezound_AndroidPolice_4.03.605.2_PH98IMG.z
ip
Whoops: didn't find expected signature
read_central_directory_entry failed
²ετ╪»╛g[ÑÖ╥yïS¬☼û÷A☼├║f:e{ûhh%►ÉÉW└|'╢σG╣S╙τφN}┐{S
c:\mini-adb_vigor>
Yikes!!
Try this in fastboot. Make sure you have the rezound_AndroidPolice_4.03.605.2_PH98IMG.zip in the same directory with fastboot.exe Make sure it is way over 33MB.
fastboot oem rebootRUU
fastboot flash zip rezound_AndroidPolice_4.03.605.2_PH98IMG.zip
Here we go....
c:\mini-adb_vigor>fastboot devices
HT19RS207848 fastboot
c:\mini-adb_vigor>fastboot oem rebootRUU
... INFO[SD_HW_ERR] read data fail in CMD18
INFO[SD_HW_ERR] SD: Read data fail..
INFO[ERR] partition_read_emmc(732): error 1
INFOStart Verify: 0
INFO[SD_HW_ERR] read data fail in CMD18
INFO[SD_HW_ERR] SD: Read data fail..
INFO[ERR] partition_read_emmc(732): error 1
INFOStart Verify: 0
INFOerase sector 130560 ~ 131071 (512)
INFOemmc_erase(1853): sd_write_sector failed!
OKAY [ 0.082s]
finished. total time: 0.083s
c:\mini-adb_vigor>
Flyhalf205 said:
Try this in fastboot. Make sure you have the rezound_AndroidPolice_4.03.605.2_PH98IMG.zip in the same directory with fastboot.exe Make sure it is way over 33MB.
fastboot oem rebootRUU
fastboot flash zip rezound_AndroidPolice_4.03.605.2_PH98IMG.zip
Click to expand...
Click to collapse
jksell07 said:
Here we go....
c:\mini-adb_vigor>fastboot devices
HT19RS207848 fastboot
c:\mini-adb_vigor>fastboot oem rebootRUU
... INFO[SD_HW_ERR] read data fail in CMD18
INFO[SD_HW_ERR] SD: Read data fail..
INFO[ERR] partition_read_emmc(732): error 1
INFOStart Verify: 0
INFO[SD_HW_ERR] read data fail in CMD18
INFO[SD_HW_ERR] SD: Read data fail..
INFO[ERR] partition_read_emmc(732): error 1
INFOStart Verify: 0
INFOerase sector 130560 ~ 131071 (512)
INFOemmc_erase(1853): sd_write_sector failed!
OKAY [ 0.082s]
finished. total time: 0.083s
c:\mini-adb_vigor>
Click to expand...
Click to collapse
Stinks to say but it looks like if you have bad blocks I don't think it can be fixed.
You can try unlocking and if it will unlock. Download a recovery. CWM. AmonRA. or TWRP. A fastboot command would be fastboot boot recovery.img or fastboot flash recovery recovery.img. Use the first command if you can't flash the recovery. If you can get a recovery to load. Flash a rom
Just an idea here. I would go here http://shipped-roms.com/index.php?category=android&model=Vigor and down load one of the "EXE" RUU and try it. These are windows executables, so just double click on the file after downloading. Start with a ICS first and if that dont work try the GB
mclass55 said:
Just an idea here. I would go here http://shipped-roms.com/index.php?category=android&model=Vigor and down load one of the "EXE" RUU and try it. These are windows executables, so just double click on the file after downloading. Start with a ICS first and if that dont work try the GB
Click to expand...
Click to collapse
The .exe basically does the same thing as fastboot oem rebootRUU. Just does it for you in a GUI.
Wish I could help here but curious about something, if he some how flashed a bad dl of an ruu, which contains hboot, and radio's etc..I know that if you have a bad dl of an hboot, or radio and you flash it it would brick your phone. could it be possible he bricked his phone due to this same theory? Except by running an ruu, or could that even be a possibility when updating via ruu? Just my 2cent and ??
Sent from my ADR6425LVW using xda app-developers app
Maybe he can try flashing just the hboot then trying the ruu again
Sent from my ADR6425LVW using xda app-developers app
Squirrel1620 said:
Maybe he can try flashing just the hboot then trying the ruu again
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Agreed, he is s-off.. you can try doing everything seperately, make sure you check your md5s.. start with your hboot..
Sent from my ADR6425LVW using xda app-developers app
I just got home and my internet connection's out. I'm tethered to my OG droid right now and it is slooooooowww. When it rains, it pours.
" Stinks to say but it looks like if you have bad blocks I don't think it can be fixed.
You can try unlocking and if it will unlock. " Thanks Flyhalf205, I already tried unlocking and that was a no go.
I tried messing around in a linux terminal:
" Detect the device using the script provided. Type this in the terminal: ./brickdetect.sh "
(I got this from here - http://forum.xda-developers.com/showthread.php?t=1833530&page=6)
It said something like permission denied.
I'll try flashing an hboot...I had thought about that but since its the only thing working on my phone I was a little hesitant. First I have to get my internet back up and running. I'll check back later.
Everyones help is much appreciated.
jksell07 said:
I just got home and my internet connection's out. I'm tethered to my OG droid right now and it is slooooooowww. When it rains, it pours.
" Stinks to say but it looks like if you have bad blocks I don't think it can be fixed.
You can try unlocking and if it will unlock. " Thanks Flyhalf205, I already tried unlocking and that was a no go.
I tried messing around in a linux terminal:
" Detect the device using the script provided. Type this in the terminal: ./brickdetect.sh "
(I got this from here - http://forum.xda-developers.com/showthread.php?t=1833530&page=6)
It said something like permission denied.
I'll try flashing an hboot...I had thought about that but since its the only thing working on my phone I was a little hesitant. First I have to get my internet back up and running. I'll check back later.
Everyones help is much appreciated.
Click to expand...
Click to collapse
Can't wait to hear if it worked. But as famouscollin said, check check and triple check that MD5. A bad hboot = permanent brick
Sent from my ADR6425LVW using xda app-developers app
Here are some confirmed working hboots, in case you were unsure of where to get them or which to use. They are based on the latest release, but have fastboot enabled without HTCDev unlock, and have the "LOCKED" at the top replaced with various other words.
Internet's back up but I won't have a chance to play with my phone until Tuesday night, so I'll post again when I have something to report. :good:
Like to hear how it went for you
mclass55 said:
Like to hear how it went for you
Click to expand...
Click to collapse
Not good. Nothing will flash. The only thing I have left to try is some fastboot erase commands. That might be the nail in the coffin though if I lose hboot.
Heres something else I tried...extracted the img from a RUU:
c:\mini-adb_vigor>fastboot flash mdm9k mdm9k.img
sending 'mdm9k' (23389 KB)... OKAY [ 3.259s]
writing 'mdm9k'... FAILED (remote: not allowed)
finished. total time: 3.575s
Flyhalf205 said:
Stinks to say but it looks like if you have bad blocks
Click to expand...
Click to collapse
If your'e still around, when you say bad blocks, is that something physically wrong like fried or just that the blocks are not accessible? Even if my phone is toast, I'm still curious as to what exactly happened.
I've been rooting phones for a few years now and no matter how bad I messed up my phone, I've always been able to bring it back from the brink. I was starting to think that bricking your phone wasn't really possible. It's like your dog dying and learning about death for the first time.
That's weird, I've only seen the remote not allowed when the bootloader is locked and you are s on
Can you try and unlock even though you are s off?
Sent from my ADR6425LVW using xda app-developers app
jksell07 said:
If your'e still around, when you say bad blocks, is that something physically wrong like fried or just that the blocks are not accessible? Even if my phone is toast, I'm still curious as to what exactly happened.
Click to expand...
Click to collapse
A bad HBOOT will cause a bad block. I am not sure how I can explain it. But the original MD5 did not match the one you downloaded and so it was a bad flash but this time a bad flash that can't be undone.
I know this sounds crazy. But trying doing the wire trick again and if asked to flash HBOOT. Do it!
Hello,
I have tried to flash a custom ROM to my htc desire x but unfortunetly I am a almost complete noob. I have been using Desire_X_All-In-One_Kit_v2.0 in order to complete the action. The problem is that i have never rooted the fone nor i have put in the recovery into it. So basically i unlocked the bootloader and thought it would all work.Well you know yourselfs it didn't.I have been looking all over the place for a way to get my phone fixed and i found one(ima Junior member can't post links yet ( Re-flash stock ROM (RUU) after bricking a rooted device)) .I have done all the steps but in step5 i get an error
C:\rec>fastboot flash recovery recovery_signed.img
sending 'recovery' (4266 KB)...
OKAY [ 0.795s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.323s
and in step 7 i get Error 140 bootloader error during RUU
Any help here would be greatly appreciated
Regards Kuba
First of all write down all you have written in bootloader screen.
It will be easy to fix it.
nlooooo said:
First of all write down all you have written in bootloader screen.
It will be easy to fix it.
Click to expand...
Click to collapse
How do you mean? do you mean whats written when i enter the bootloader or what have I written in in the terminal ( eg. fastboot flash recovery recovery_signed.img)
Thanks a lot for your quick reply
Bootloader screen, when you enter bootloader.
Also, give me the version of RUU that you have.
nlooooo said:
Bootloader screen, when you enter bootloader.
Also, give me the version of RUU that you have.
Click to expand...
Click to collapse
*****RELOCKED********
PROTO PVT SHIP S-ON RL
HBOOT-1.24.0000
RADIO-1.10.40.23
eMMC-boot
Oct 30 2012, 20:09:09
The most recent RUU i have downloaded is RUU_PROTO_U_ICS_40A_HTC_Europe_1.14.401.1_Radio_10.18.40.05U_1.09.45.201_release_284072_signed
But i have read that FAILED <remote: signature verify fail> error that im getting is related to wrong ruu .I guess you know better
There's a newer release 1.18.401.1 there's a link in Index in my signature, try to download that one and run it with phone booted in fastboot and attached to PC. If that doesn't go will try something else.
nlooooo said:
There's a newer release 1.18.401.1 there's a link in Index in my signature, try to download that one and run it with phone booted in fastboot and attached to PC. If that doesn't go will try something else.
Click to expand...
Click to collapse
Great man!! thanks for help!! Could you just make it clear what i need in the folder with the ruu ?. its Adb.exe AdbWinAp.dll fastBoot.exe and the image file? is there anything else i would need? (as you see i know basically nothing about this)
It's not a folder its exe file, just run it from PC.
nlooooo said:
It's not a folder its exe file, just run it from PC.
Click to expand...
Click to collapse
YOUR Fuc**ng Awsome bruf everything back on track !!.....THank a lot
hlick14 said:
YOUR Fuc**ng Awsome bruf everything back on track !!.....THank a lot
Click to expand...
Click to collapse
That's why I'm here and that's what the thanks button stands for...
HTC preloaded some image files for the "stickers" in the duo effects camera. They are preloaded to /data/preload so you can either flash the zip at the bottom of the second post or manually copy them over to that directory. They (HTC) haven't fully implemented this yet... so you probably won't even notice them missing. The also preload calc and flashlight app this way too.
NOTE- This will work for S-on users provided their current software level is at or below this version. S-off users can user this either way.
OPTION 1)
Rename download file to 0P3PIMG.zip. Make sure you use an SD card formatted to fat32!! (otherwise the phone might not see it) Place file on physical SD card (not internal phone memory)... i repeat physical SD card. Boot up phone to bootloader mode and the phone will auto-detect the file and prompt to install it. Follow any remaining prompts to allow the RUU to flash the software to your phone.
-or-
OPTION 2)
Download file into working fastboot directory. Boot phone to fastboot mode and connect to pc. Type in the following commands.
fastboot oem rebootRUU
fastboot flash zip RUU_T6_Sprint_WWE_1.16.651.4.zip
first time you run this it will be short... so run it a second time
fastboot flash zip RUU_T6_Sprint_WWE_1.16.651.4.zip
The command prompt output will show you details as it flashes each partition and will show you when it has completed. At this time the green bar on the phone will appear 99% of the way across the screen.. Completely normal!~ Issue the next command to kick it out of RUU mode or optionally flash the custom recovery TWRP if you intend to root/flash custom roms and THEN issue the below command to get out of RUU mode.
fastboot reboot
(note) if you just want to reboot back to bootloader you can issue the command fastboot reboot-bootloader This will allow you to boot directly to recovery and start flashing/rooting fun.
I don't own this model phone... so if someone would like to capture the output of the command prompt I would be happy to add it to the OP similar to how I have my VZW ruu threads.
Downloads Do NOT mirror these elsewhere.
RUU Download link
https://www.androidfilehost.com/?fid=23622183712460121
Data preload apps/stickers
https://www.androidfilehost.com/?fid=23622183712460132
RUU Mode TWRP 2.7.1 (must be s-off or unlocked)
https://www.androidfilehost.com/?fid=23622183712460136
Getting error, too many links
I followed the directions, but when I do I get an error: FAILED (status read failed (Too many links))
output:
sending 'zip' (1271836 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOrom parsing start ...
INFOrom parsing finish ...
INFOzip header checking...
INFOzip info parsing...
INFORead zipped android_info fail
FAILED (status read failed (Too many links))
martinoj2009 said:
I followed the directions, but when I do I get an error: FAILED (status read failed (Too many links))
output:
sending 'zip' (1271836 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOrom parsing start ...
INFOrom parsing finish ...
INFOzip header checking...
INFOzip info parsing...
INFORead zipped android_info fail
FAILED (status read failed (Too many links))
Click to expand...
Click to collapse
Did your md5 check out fine?
dottat said:
Did your md5 check out fine?
Click to expand...
Click to collapse
Yes
8f380af56b92ac2c4e3055b9a43b5871 ruu_t6_sprint_wwe_1.16.651.4.zip
martinoj2009 said:
Yes
8f380af56b92ac2c4e3055b9a43b5871 ruu_t6_sprint_wwe_1.16.651.4.zip
Click to expand...
Click to collapse
Do you have an sd card to try it via option 1?
dottat said:
Do you have an sd card to try it via option 1?
Click to expand...
Click to collapse
I'm sure I do, I'll let you know, and thanks for the prompt reply!
martinoj2009 said:
I'm sure I do, I'll let you know, and thanks for the prompt reply!
Click to expand...
Click to collapse
Not a problem. Also, under my android file host I have a mini sdk zip. You try using that on your pc too...it's a newer version of Fastboot/adb. All you have to do is unzip it and use it from wherever you unzip it to.
dottat said:
Not a problem. Also, under my android file host I have a mini sdk zip. You try using that on your pc too...it's a newer version of Fastboot/adb. All you have to do is unzip it and use it from wherever you unzip it to.
Click to expand...
Click to collapse
So I did this, no errors, but when I rebooted it went right into Cyanogenmod. Am I missing a step?
martinoj2009 said:
So I did this, no errors, but when I rebooted it went right into Cyanogenmod. Am I missing a step?
Click to expand...
Click to collapse
How long did it take to run the zip?
dottat said:
How long did it take to run the zip?
Click to expand...
Click to collapse
It takes a while ~5mins, it loads the file, then checks the signature, and then says ROM parsing start (for 5 seconds) and then tells me to press the power button to reboot.
martinoj2009 said:
It takes a while ~5mins, it loads the file, then checks the signature, and then says ROM parsing start (for 5 seconds) and then tells me to press the power button to reboot.
Click to expand...
Click to collapse
You have to do it twice if the first time is short. Sometimes it can only update certain files first.
You are s off right?
dottat said:
You have to do it twice if the first time is short. Sometimes it can only update certain files first.
You are s off right?
Click to expand...
Click to collapse
Lol, shhhh, forgot to S-Off
martinoj2009 said:
Lol, shhhh, forgot to S-Off
Click to expand...
Click to collapse
OK... so if you aren't S-off AND this firmware is older than what you have it will fail. Only S-off can downgrade. You guys don't have a newer RUU yet and there were two OTAs after this one. Definitely S-off that thing while you still can (assuming it's not too late).
@dottat
I have developer edition device and have ruu for it to stock jellyben
But I found that I can't flash the ruu to go back to jellyben from sense 6 firmware and the error was the same as mentioned above in other comments .. android info fail too many links
And after a lot of trials, I found that the rug is fine not damaged so I flashed the firmware if sense 5.5 and then tried the ruu again and it works perfect
So from my point , I think that older jb ruus can't be flashed if u have sense 6 firmware
So only I need tho flash firmware zip of sense 5.5 not the whole system the try the ruu again although both sense 6 and sense 5.5 have hboot 2.49 but I think that the one that came with sense 6 have some modifications
Also I tried to flash from sd card but no go so the only solution is flashing hboot of sense 5.5
Maybe it's the same with Sprint devices but I think that it will be the same
mido.fayad said:
@dottat
I have developer edition device and have ruu for it to stock jellyben
But I found that I can't flash the ruu to go back to jellyben from sense 6 firmware and the error was the same as mentioned above in other comments .. android info fail too many links
And after a lot of trials, I found that the rug is fine not damaged so I flashed the firmware if sense 5.5 and then tried the ruu again and it works perfect
So from my point , I think that older jb ruus can't be flashed if u have sense 6 firmware
So only I need tho flash firmware zip of sense 5.5 not the whole system the try the ruu again although both sense 6 and sense 5.5 have hboot 2.49 but I think that the one that came with sense 6 have some modifications
Also I tried to flash from sd card but no go so the only solution is flashing hboot of sense 5.5
Maybe it's the same with Sprint devices but I think that it will be the same
Click to expand...
Click to collapse
Either way....without being s off you can't downgrade firmware anyways. On my vzw rezound, m7, m8, and t6 I can simply flash ruus up or down all day long.
dottat said:
Either way....without being s off you can't downgrade firmware anyways. On my vzw rezound, m7, m8, and t6 I can simply flash ruus up or down all day long.
Click to expand...
Click to collapse
Yes I know that I should be s-off
And that's why I said I should downgrade first to sense 5.5 firmware then flash the ruu
And I won't be able to downgrade without s-off
So I was writing only about the error when I already have a-off because it took me 2 days till I found this fix after many trials
posted a current RUU for s-off users here...
http://forum.xda-developers.com/htc...rint-ruu-3-02-651-5-s-off-pre-rooted-t2865704
i have some troubles here
im in the HBOOT 2.49 i need to downgrade to the first HBOOT to install this RUU i need to know if make S-OFF with sunshine how to downgrade can any one. explain me how to do it ...dotatt dude u r awesome i always follow ur work and u r the best ...
please help me a little i have the knowledge to do it i just need a direction thx in advance
w1n73rf3ll said:
im in the HBOOT 2.49 i need to downgrade to the first HBOOT to install this RUU i need to know if make S-OFF with sunshine how to downgrade can any one. explain me how to do it ...dotatt dude u r awesome i always follow ur work and u r the best ...
please help me a little i have the knowledge to do it i just need a direction thx in advance
Click to expand...
Click to collapse
IF sunshine doesn't work on your current rom (have you tried running it yet).... you need to unlock your bootloader and flash a 100% stock older rom. Then use that to s-off. Then flash whatever rom you want and sim unlock.