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
Related
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.
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.
Please help.
I was trying to root the phone and keep the stock rom.
I used Hansoon's AIO kit for the HOX+ . I successfully unlocked the bootloader and I flashed the CWM (INTL model) firmware.
I successfully booted into the ROM where I had to set it up.
I rebooted afterwards and now it is stuck at the HTC boot screen.
I CAN get into CWM recovery.
I am just wondering how I should proceed from here.
Should I have flashed a custom kernel? I didn't htink so because I am keeping stock.
SHould I have flashed the ATT TWRP?
Thanks.
mfpreach said:
Please help.
I was trying to root the phone and keep the stock rom.
I used Hansoon's AIO kit for the HOX+ . I successfully unlocked the bootloader and I flashed the CWM (INTL model) firmware.
I successfully booted into the ROM where I had to set it up.
I rebooted afterwards and now it is stuck at the HTC boot screen.
I CAN get into CWM recovery.
I am just wondering how I should proceed from here.
Should I have flashed a custom kernel? I didn't htink so because I am keeping stock.
SHould I have flashed the ATT TWRP?
Thanks.
Click to expand...
Click to collapse
Find the RUU for your phone and run that. And yes you need to flash the ATT TWRP for the Telus model and also use a ATT - Telus ROM. After you run the RUU you can try again.
trannygranny said:
Find the RUU for your phone and run that. And yes you need to flash the ATT TWRP for the Telus model and also use a ATT - Telus ROM. After you run the RUU you can try again.
Click to expand...
Click to collapse
Ok, that's what I thought now.
Do you know where I can find the TElus RUU? I can't seem to find it.
THanks.
Figured out I need to sideload...
After it installed via sideload it was still stuck, I eventually just went into TWRP and reflashed the sideload.zip and it works now.
mfpreach said:
Figured out I need to sideload...
After it installed via sideload it was still stuck, I eventually just went into TWRP and reflashed the sideload.zip and it works now.
Click to expand...
Click to collapse
I'm stuck at the "HTC quietly brilliant" boot screen - can you outline what you did to get around this?
I grabbed the teamwin AT&T openrecovery image and fastbooted/flashed it, but what do you do after that?
Crankycoder said:
I'm stuck at the "HTC quietly brilliant" boot screen - can you outline what you did to get around this?
I grabbed the teamwin AT&T openrecovery image and fastbooted/flashed it, but what do you do after that?
Click to expand...
Click to collapse
I screwed up at one point, I actually didn't want to flash a custom rom, but only wanted to root stock. I ended up having to flash a custom rom since there is not Telus RUU available.
ANYWAYS,
Assuming that you have unlocked your bootloader,
Download a Rom and flash the kernel via fastboot.
The next problem is how to get the rom onto the phone in order to flash it because i spent 3 hours trying to figure out how to mount the phone and found out that you can't.
SO in order to flash a rom you need to use adb sideload.
In TWRP there is that option, then you just adb sideload romname.zip
At this point it installed the rom, ran aroma etc.. For some reason mine was still frozen. If this happens to you, just go into TWRP and install the sideload.zip , this will install the rom again.
Goodluck.
I wrote what I did to solve the same problem when I had the same issue. Check under my stats for my posts somewhere here on the forums...
Hope it helps.
Sent from my HTC One X+ using xda premium
gamepr said:
I wrote what I did to solve the same problem when I had the same issue. Check under my stats for my posts somewhere here on the forums...
Hope it helps.
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
For some reason my adb push wasn't working, I for sure tried that first.
Sideload did though.
gamepr said:
I wrote what I did to solve the same problem when I had the same issue. Check under my stats for my posts somewhere here on the forums...
Hope it helps.
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
Just wanted to make sure - this post?
http://forum.xda-developers.com/showpost.php?p=34993368&postcount=37
Crankycoder said:
Just wanted to make sure - this post?
http://forum.xda-developers.com/showpost.php?p=34993368&postcount=37
Click to expand...
Click to collapse
Just use sideload in twrp it will install it for you also right after you push it.
Crankycoder said:
Just wanted to make sure - this post?
http://forum.xda-developers.com/showpost.php?p=34993368&postcount=37
Click to expand...
Click to collapse
I grabbed the stock ROM from this msg - http://forum.xda-developers.com/showpost.php?p=34428702&postcount=1
1. Extracted the boot.img
2. flashed the boot.img with:
$ fastboot flash boot boot.img
sending 'boot' (8191 KB)...
OKAY [ 1.232s]
writing 'boot'...
(bootloader) Format partition LNX done
OKAY [ 0.464s]
finished. total time: 1.695s
3. Then used TW recovery to try to side load the zip file, but I get a failure to install.
I assume I'm doing something really stupid here. If someone can just point out what - that'd be awesome.
In the meantime, I'm going to try with the QX Senseless 2.0 rom as per the instructions in: http://forum.xda-developers.com/showpost.php?p=34993368&postcount=37
thanks!
vic
Crankycoder said:
I grabbed the stock ROM from this msg - http://forum.xda-developers.com/showpost.php?p=34428702&postcount=1
1. Extracted the boot.img
2. flashed the boot.img with:
$ fastboot flash boot boot.img
sending 'boot' (8191 KB)...
OKAY [ 1.232s]
writing 'boot'...
(bootloader) Format partition LNX done
OKAY [ 0.464s]
finished. total time: 1.695s
3. Then used TW recovery to try to side load the zip file, but I get a failure to install.
I assume I'm doing something really stupid here. If someone can just point out what - that'd be awesome.
In the meantime, I'm going to try with the QX Senseless 2.0 rom as per the instructions in: http://forum.xda-developers.com/showpost.php?p=34993368&postcount=37
thanks!
vic
Click to expand...
Click to collapse
Yeah I dunno then.
I used Elegancia and the kernel from that rom.
Out of interest, did you flash the ATT twrp or the int'l one? I am on telus and originally flashed int'l (Because Canada isn't part of the US even though many may think it is) , and that was wrong. If you are on Telus you must flash the ATT twrp.
Turns out that the stock rom I linked earlier must be corrupt. I'm using qx senseless 2.1 with no problems after flashing with TWRP.
We should probably have a list of rims that have been verified to work.
So, were my instructions good for you to recover? Sounds like it.....but i just want to make sure
Crankycoder said:
Turns out that the stock rom I linked earlier must be corrupt. I'm using qx senseless 2.1 with no problems after flashing with TWRP.
We should probably have a list of rims that have been verified to work.
Click to expand...
Click to collapse
Yes!
I used the qx senseless 2.0 rom and everything worked just fine.
Thanks a bunch!
Vic
Sent from my HTC One X+ using xda app-developers app
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.
To cut the story short, my EVO was working fine, it was S-off, Rooted, Unlocked with a custom rom. Two nights ago i decide to upgrade my HBOOT to 2.10 using RUU_JEWEL_CL_JB43_SENSE50_MR_Sprint_WWE_4.13.651.4 and everything went downhill from there.
This is my current situation and wondering if it's still fixable:
Phone is RELOCKED,Unrooted but S-off. Stuck in a bootloop where it stays on the Splash screen no matter what rom you install. FastBoot commands give me FAILED (remote : not allowed), tried re-using RUU but I keep getting Error 120: BATTERY under 30% while my phone battery is at 84%, I'm stuck and don't know what to do anymore.
and yes, I can still use recovery TWRP.
Any suggestions? Please and thanks for the help.
TheRedFlash said:
To cut the story short, my EVO was working fine, it was S-off, Rooted, Unlocked with a custom rom. Two nights ago i decide to upgrade my HBOOT to 2.10 using RUU_JEWEL_CL_JB43_SENSE50_MR_Sprint_WWE_4.13.651.4 and everything went downhill from there.
This is my current situation and wondering if it's still fixable:
Phone is RELOCKED,Unrooted but S-off. Stuck in a bootloop where it stays on the Splash screen no matter what rom you install. FastBoot commands give me FAILED (remote : not allowed), tried re-using RUU but I keep getting Error 120: BATTERY under 30% while my phone battery is at 84%, I'm stuck and don't know what to do anymore.
and yes, I can still use recovery TWRP.
Any suggestions? Please and thanks for the help.
Click to expand...
Click to collapse
Are you installing roms for the new layout
Sent from my EVO using XDA Free mobile app
Also, did you unlock the bootloader again? Do this before you do anything else. Also, as stated above, make sure you're flashing ROM's based on the new format. ROM's based on the old partition format (software version 3.17 or older) will not work. Additionally, what version of TWRP are you using? You have to use TWRP that's for the new format, also.
Sent from my HTC device
gstanke said:
Are you installing roms for the new layout
Click to expand...
Click to collapse
Yea and I updated the HBOOT because people usually say that updating is for the better for call qualities and signal retrieval.
Magnum_Enforcer said:
Also, did you unlock the bootloader again? Do this before you do anything else. Also, as stated above, make sure you're flashing ROM's based on the new format. ROM's based on the old partition format (software version 3.17 or older) will not work. Additionally, what version of TWRP are you using? You have to use TWRP that's for the new format, also.
Click to expand...
Click to collapse
No, I haven't attempted to unlock it again, but will do so now. Also, these are the two roms that i have tried and both didn't work Viper4G 4.0.0 and the Sense 5 (4.3) Y18 Version. They are both made for the new partition. Well i started with TWRP 2.7.0.0b but then downgraded it to 2.6.0.0 since i thought maybe the TWRP is failing to install my ROM's correctly.
TheRedFlash said:
No, I haven't attempted to unlock it again, but will do so now. Also, these are the two roms that i have tried and both didn't work Viper4G 4.0.0 and the Sense 5 (4.3) Y18 Version. They are both made for the new partition. Well i started with TWRP 2.7.0.0b but then downgraded it to 2.6.0.0 since i thought maybe the TWRP is failing to install my ROM's correctly.
Click to expand...
Click to collapse
Use TWRP from the 3rd post in the thread below:
http://forum.xda-developers.com/showthread.php?t=2751873
Sent from my HTC device
Magnum_Enforcer said:
Use TWRP from the 3rd post in the thread below:
http://forum.xda-developers.com/showthread.php?t=2751873
Click to expand...
Click to collapse
So far so good, I was able to unlock bootloader again and flashed the recovery you gave me. Should I flash a ROM now to see if it worked?
*Tip for those who can't get bootloader to re-unlock again through Fastboot. Put the Unlock_code.bin in the same directory as Fastboot and just use the command fastboot flash unlocktoken unlock_code.bin*
UPDATE:
Tried flashing a ROM, everything goes well but at the end of installation or wipe I get E: unable to mount /system and I cannot mount manually neither through recovery. I am also noticing that when the phone restarts it stays on the splash screen still but my HTCSyn Manager seems to be detecting it because it pops up mentioning that it couldn't connect to my phone.
TheRedFlash said:
So far so good, I was able to unlock bootloader again and flashed the recovery you gave me. Should I flash a ROM now to see if it worked?
*Tip for those who can't get bootloader to re-unlock again through Fastboot. Put the Unlock_code.bin in the same directory as Fastboot and just use the command fastboot flash unlocktoken unlock_code.bin*
UPDATE:
Tried flashing a ROM, everything goes well but at the end of installation or wipe I get E: unable to mount /system and I cannot mount manually neither through recovery. I am also noticing that when the phone restarts it stays on the splash screen still but my HTCSyn Manager seems to be detecting it because it pops up mentioning that it couldn't connect to my phone.
Click to expand...
Click to collapse
I got that error too, it sounds like you are not using the correct version of TWRP for the new partition layout.
http://forum.xda-developers.com/showthread.php?t=2639180
TWRP Recovery 2.7.0.8b or 4.13.651.4 Firmware + TWRP Recovery
Should work.
RChris173 said:
I got that error too, it sounds like you are not using the correct version of TWRP for the new partition layout.
http://forum.xda-developers.com/showthread.php?t=2639180
TWRP Recovery 2.7.0.8b or 4.13.651.4 Firmware + TWRP Recovery
Should work.
Click to expand...
Click to collapse
Chris, I got it working this morning, by coincidence/luck. I put my phone in RUU mode using fastboot oem rebootRUU and then ran the actually RUU utility and from there on it took off. Either way, thanks for you reply man, it'll probably help someone when they encounter this situation.