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.
Related
Okay I have made a thread about this before, but no one had an answer for me, so I will try again, but I will be more descriptive of my issue.
So the other day, my Evo 3D, which is flashed to MetroPCS, lost its carrier settings when I was flashing a ROM. So I had to go home and use QPST to edit some files in the nvm/num folder (Using EFS). While I was editing, the program crashed, and I was forced to unplug my Evo.
Now, after it rebooted, it would go past the HTC Screen, and flash the boot animation for a split second, then shut off and restart. It would loop like this no matter how long I left it.
So I went into 4-EXT recovery, and formatted system, boot, data etc, and then flashed a ROM. Rebooted and got the same thing. So in a last ditch effort, I downloaded the latest ICS RUU for this phone, and tried all three methods to install. I ran the .exe, the program ran as expected, and the phone showed the progress bar on a black HTC Screen as updating, it rebooted when done, and then just continued to bootloop. I also pulling the rom.zip and renaming it to PG86IMG.zip and flashing it from fastboot. It worked and once it rebooted, did the same thing. I also ran it from fastboot usb, and got the same result.
However, I extracted the rom.zip and tried to use fastboot to flash individual .img files, and on EVERY one, I got "FAILED - Error: (remote: not allowed).
I had previously used the wiretrick to get S-OFF on my Hboot 1.58.
It says "Unlocked" at the top of the bootloader.
I really need to get my phone working, can someone PLEASE point me in the correct direction or at least help me out? Is my phone ruined? Is there a way I can clear the NV memory or something to truly reset the phone?
Once again, I will repeat, RUUs will not work!, I am S-OFF on HBOOT 1.58, my bootloader says "unlocked." No matter what I do it will bootloop. I can flash a recovery, but if I flash a rom it does the same stuff.
When you ran the ruu.exe, did you lock the bootloader first? If you don't, the ruu won't work.
coal686 said:
When you ran the ruu.exe, did you lock the bootloader first? If you don't, the ruu won't work.
Click to expand...
Click to collapse
I don't remember, but wouldn't the RUU fail if it was unlocked? Because it didn't fail, it just didnt work.
So now I screwed up, I got it to be able to erase/write in fastboot, I used fastboot erase instead of fastboot format and now my partitions are gone, how do I get those back?
AtmosFEAR4701 said:
I don't remember, but wouldn't the RUU fail if it was unlocked? Because it didn't fail, it just didnt work.
Click to expand...
Click to collapse
Sounds like a similar thing that happened to me when trying to flash a JB rom with a kernal that was not compatable....no matter what I did I could not get it out of the boot loop...I am Hboot 1.58 HTC unlocked and wire trick S-off...I finally flashed an old backup I had with a stock kernal and it fixed it all...dont know if this helps you at all but try wiping everything possible and flashing a stock kernal or an old backup you may have...
coal686 said:
When you ran the ruu.exe, did you lock the bootloader first? If you don't, the ruu won't work.
Click to expand...
Click to collapse
His s-off so doesn't matter if its locked or not.
iTzLOLtrain said:
His s-off so doesn't matter if its locked or not.
Click to expand...
Click to collapse
Good to know. I always thought you had to lock the bootloader anyway but leave it s-off. I learn something new everyday. :beer:
coal686 said:
Good to know. I always thought you had to lock the bootloader anyway but leave it s-off. I learn something new everyday. :beer:
Click to expand...
Click to collapse
Ok so I had accidenatly did "fastboot erase" and lost my partitions. I flashed the RUU again and now they are back, but if I try to use fastboot format, it says "Failed - Error: (remote: unknown command)." and it also said something about cannot determine partition type or something. I really need some help lol.
AtmosFEAR4701 said:
Ok so I had accidenatly did "fastboot erase" and lost my partitions. I flashed the RUU again and now they are back, but if I try to use fastboot format, it says "Failed - Error: (remote: unknown command)." and it also said something about cannot determine partition type or something. I really need some help lol.
Click to expand...
Click to collapse
Why are you using fastboot commands like "erase" and "format". Partitions should be formatted in recovery, not the bootloader.
If the RUU ran successfully it should reboot into the stock ROM when it finished. Did that work?
ramjet73
ramjet73 said:
Why are you using fastboot commands like "erase" and "format". Partitions should be formatted in recovery, not the bootloader.
If the RUU ran successfully it should reboot into the stock ROM when it finished. Did that work?
ramjet73
Click to expand...
Click to collapse
My first post says that I have run the RUU countless times and it still bootloops.
Nevermind... I sold it.
AtmosFEAR4701 said:
Nevermind... I sold it.
Click to expand...
Click to collapse
That's one way to solve the problem.
Sorry we couldn't figure it out.
coal686 said:
That's one way to solve the problem.
Sorry we couldn't figure it out.
Click to expand...
Click to collapse
It's okay. I am not buying another Evo 3D though. I am a MetroPCS customer so I buy flashed phones a lot, and I have a low budget so I'll either grab a flash Galaxy S2, or possibly grab the MetroPCS Galaxy S3 when I get some money.
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!
So just got the phone yesterday and I wanted to S-off immediately. Me being the idiot I am I fully rooted through fireballas method rather than temp-rooting and that messes up dirtyracun. So I need to flash the stock RUU again. I re-locked my phone and tried flashing the RUU and each time I get "FAILED (remote: 99 unknown fail)". Maybe I'm missing something here. How do I flash back to stock?
Are you following the instructions on the unlimited.io website? Because all you need to do is run the fastboot command and it should run just fine.
Sent from my ADR6410LVW using xda app-developers app
Ikikaea said:
So just got the phone yesterday and I wanted to S-off immediately. Me being the idiot I am I fully rooted through fireballas method rather than temp-rooting and that messes up dirtyracun. So I need to flash the stock RUU again. I re-locked my phone and tried flashing the RUU and each time I get "FAILED (remote: 99 unknown fail)". Maybe I'm missing something here. How do I flash back to stock?
Click to expand...
Click to collapse
after you get that error retype the command and it will go though. all part of the process
fastboot flash zip RUU.zip.
Aldo101t said:
after you get that error retype the command and it will go though. all part of the process
fastboot flash zip RUU.zip.
Click to expand...
Click to collapse
No matter how many times I try it won't flash. I figure it's the TWRP recovery or the root that's causing the problem. I must be missing something since I should be able to flash back to stock.
Ikikaea said:
No matter how many times I try it won't flash. I figure it's the TWRP recovery or the root that's causing the problem. I must be missing something since I should be able to flash back to stock.
Click to expand...
Click to collapse
It is most likely the custom recovery that is the problem. Flash the stock recovery (found HERE), then try the RUU again.
Good news! A factory reset and redownloading the RUU.zip fixed the problem. I have my theories on what was messed up, but I'm just glad it worked out in the end. Thanks to all the people who tried to help.
My phone was acting buggy with the radios and had HUGE performance issues. To be frank, i think a SNAIL was faster than this phone at the time... I am S-OFF, unlocked and i cannot flash recovery.
I get this output and error:
Code:
sending 'recovery' (8516 KB)...
OKAY [ 1.087s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.129s
here is the current HBOOT Config and display:
Code:
FIREBALL PVT SHIP S-OFF RL
CID-VZW__001
HBOOT-1.15.0000
OpenDSP-29.1.0.45.622
eMMC-boot
Just for good measure i re-wrote the CID to 11111111 and locked and unlocked the bootloader again to no avail, thinking it was possibly that being unlocked during an RUU. The thing is, while unlocked, the RUU still processed... Oh and the phone boots up fully. i have ZERO issues with actually using the phone, but i cant believe i am stuck on a stock rom and not allowed to flash a custom recovery... >_>
Other thing... just to see if this would help, i used junkmail9's ENG HBOOT with the RegawMOD Customizer to flash the ENG hboot to try my luck. STILL no good. i can flash hboot directly, and whatever else, but is recovery just stuck??
i really want to be free again, so can someone please explain to me why after an RUU even WHILE S-OFF and unlocked, that i cannot flash recovery?
cyberkeeper1 said:
I get this output and error:
Code:
sending 'recovery' (8516 KB)...
OKAY [ 1.087s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.129s
Click to expand...
Click to collapse
You did not mention either the recovery image you tried to flash, nor the command you used to try and flash it. There's no point in messing with bootloader lock/unlock if you're s-off. Just leave it alone.
my apologies... well basically, i cannot flash any custom recovery for this phone. CWM 6.0.3.1 which i had before the restore, and i just tried the philZ Touch 5 recovery which is basically the same thing as CWM... for some reason, the recovery partition became locked after the restore despite being s-off. i remember this error before while s-on and locked when I used to have the Wildfire S.
cyberkeeper1 said:
my apologies... well basically, i cannot flash any custom recovery for this phone. CWM 6.0.3.1 which i had before the restore, and i just tried the philZ Touch 5 recovery which is basically the same thing as CWM... for some reason, the recovery partition became locked after the restore despite being s-off. i remember this error before while s-on and locked when I used to have the Wildfire S.
Click to expand...
Click to collapse
alright, i am a dodo-bird... apparently, i really need glasses because i JUST noticed that i was flashing a zip file.... dang it... for whatever reason, it can flash zip files, but i guess i didnt have the right one. anyhow, no help needed now. Mods, you can close the thread... my apologies for the wasted space. If its any consolation, i havent really slept so.... yea. lol. thanks for the help thus far.
i wasnt flashing the IMG file like i should have been.
similiar issue
hello users of the almighty xda!
I have obtained s-off using dirtyracun and flashed between team venoms viper rom and cyanogenmod10.1 multiple times
this last time I tried to flash back to viper2.2.0 from cyanogenmod because of the problems with the m2 snapshot I wiped everything as usual including cache,data, and even a factory reset and installed the viper rom and said everything was good to go and now the phone wont boot past the htc screen
so I figured i'd reflash the viper boot.img to see if that would help and doesn't
not only will it not boot but when I go to the bootloader and try to enter recovery it flashes and I see the clockwork mod symbol and then it boot loops back to the htc logo endlessly
wtf! ugg! any ideas oh great xda users?
p.s im also under the impression that because im s-off I cant RUU back to stock is this the case?
styxking said:
im also under the impression that because im s-off I cant RUU back to stock is this the case?
Click to expand...
Click to collapse
This is not true. You may at any time run the RUU to restore borked programming. Besides, the dirtyracun method of flashing s-off is risky to say the least. I used facepalm s-off and it was stupid easy. Anyhow, run the RUU and then immediately run a factory reset. The RUU formats and repairs all partitions on the device and the factory reset restores the radio and baseband as described by mdmower.
Sent from my ADR6410LVW using xda app-developers app
Do the following to prepare for RUU-
Run these commands in order:
fastboot oem resetRUUflag (wait for reload)
Fastboot oem rebootRUU
Fastboot erase cache
Fastboot flash zip name_of_file.zip
Alternatively, you can run the automated HTC RUU utility, but it often fails vs. A manual reflash.
Sent from my ADR6410LVW using xda app-developers app
ignore please, came late and didnt notice
gonna try it
thanks for the response. I agree the dirtyracun method is pretty risky, but at the time I think it was the only s-off method I could find
well I will ruu then
thanks for the detailed fastboot commands and such
I don't have to relock the bootloader do I?
Im having a difficult time getting back to stock
downloaded the stock files from this thread: http://forum.xda-developers.com/att...nt/att-stock-backups-recoveries-otas-t2855966
but the following happened :
ive had a botched attempt at updating the firmware and installing venomone.
i tried installing these via the all in one kit but it didnt work, it had me try relocking my bootloader and still didnt work.
so now im stuck with a relocked bootloader, and cant figure out how to get back to stock =/
edit: i managed to get the phone back to stock using this ruu
http://forum.xda-developers.com/showthread.php?t=2757462
so now, how can i unlcok my bootloader again?
whei try using htc devs methood
"fastboot flash unlocktoken Unlock_code.bin"
i get the message
"target reported max download size of 1830580224 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.128s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.149s
"
also from here which verision of twrp is the propper one? (att m8), and which firmware shoudl i upgrade to for venom rom to be compatible (also do i need to super cid again?)
Did you tried to get a new token From HTC ? Or you using the old one?
JEANRIVERA said:
Did you tried to get a new token From HTC ? Or you using the old one?
Click to expand...
Click to collapse
tried using the old one
edit:woohoo new token worked, not with the one click tool, but it worked when i used
"fastboot flash unlocktoken Unlock_code.bin"
I'm glad I was able to help!!!
JEANRIVERA said:
I'm glad I was able to help!!!
Click to expand...
Click to collapse
appreciate it, never would have thought of that
(i always assumed youd get the same token if you re-ran the process with the same phone)
The_Zodiac said:
ive had a botched attempt at updating the firmware and installing venomone.
Click to expand...
Click to collapse
Ditch the toolkit, brother. It has been a point of failure in itself for at least a few folks, so better to just remove it from the equation and flash things manually by adb/fastboot.
redpoint73 said:
Ditch the toolkit, brother. It has been a point of failure in itself for at least a few folks, so better to just remove it from the equation and flash things manually by adb/fastboot.
Click to expand...
Click to collapse
yeah very likely a good idea. i ended up manually flashing it and it seemed to have actually worked.
i finally managed to get venomone to work
for some reason every time i wipe (either in twrp and or in aroma ) it wont work correctly,
but i dirty flashed it over the failed attempt (with wipe) and it works for some reason weird
The_Zodiac said:
for some reason every time i wipe (either in twrp and or in aroma ) it wont work correctly,
but i dirty flashed it over the failed attempt (with wipe) and it works for some reason weird
Click to expand...
Click to collapse
I never wipe in AROMA. Might just be an old habit from One X (EVITA) days (where AROMA wipes caused some major problems) and those bugs might not exist on this phone. But wipes in TWRP have never caused issues for me.
Make sure you are on the latest TWRP. Maybe wipe cache in fastboot and re-install TWRP to see if its just not a faulty TWRP install.
redpoint73 said:
I never wipe in AROMA. Might just be an old habit from One X (EVITA) days (where AROMA wipes caused some major problems) and those bugs might not exist on this phone. But wipes in TWRP have never caused issues for me.
Make sure you are on the latest TWRP. Maybe wipe cache in fastboot and re-install TWRP to see if its just not a faulty TWRP install.
Click to expand...
Click to collapse
I ended up figuring out what the problem was, one of the apps I was removing was causing the problem.
After I didn't select the "remove apps" option it booted no problem