My experience upgrading to Rezound ICS 3.11.065.22 leak. I was already at 2.01.605.11 stock rooted with radio 0.95.00.1118r.
Copied the following to external SD card:
rezound_ics_androidpolice_3.11.605.22 .zip
su-bin-3.0.3.2-efghi-signed.zip
renamed rezound_ics_androidpolice_3.11.605.22 .zip file to PH98IMG.zip
Headed over to my bootloader unlock directory where I also had Amon Ra and rebooted phone into recovery.
C:\vprasad\htcunlock>dir
Volume in drive C has no label.
Volume Serial Number is
Directory of C:\vprasad\htcunlock
03/13/2012 01:19 PM <DIR> .
03/13/2012 01:19 PM <DIR> ..
02/07/2012 02:43 AM 162,816 adb.exe
02/07/2012 02:43 AM 96,256 AdbWinApi.dll
02/07/2012 02:43 AM 70,144 fastboot.exe
03/12/2012 11:32 PM 7,243,776 recovery-ra-vigor-3.14-gnm.img
03/13/2012 12:19 AM 256 Unlock_code.bin
C:\vprasad\htcunlock>adb reboot recovery
adb server is out of date. killing...
* daemon started successfully *
Click to expand...
Click to collapse
In Amon Ra did a backup for just in case (even though Gingerbread may not be able to use the new ICS radios, maybe somebody will figure a way. Besides, backups are good practice!).
After the backup completed it was time to start the ICS install process.
C:\vprasad\htcunlock>adb reboot bootloader
Click to expand...
Click to collapse
Once bootloader came up, it said Unlocked at top of screen. Started the lock before PH98IMG.zip install began because I wanted the radios upgraded
C:\vprasad\htcunlock>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 134086000 (0x7FDFD70)
FAILED (status read failed (Too many links))
finished. total time: 0.937s
Click to expand...
Click to collapse
Bootloader now said Relocked at top of screen. Chose Fastboot and it began the PH98IMG.zip installation. Was prompted for update and selected YES.
Screen went blank for about a minute and phone’s orange LED was blinking.
After that minute, screen came up in bootloader and there was the “tampered” message (badge of honor/shame for having Amon Ra installed?) at top of screen. Radio still showed 0.95.00.1118r/0.95.00.1223r
From the bootloader menu chose Fastboot / boot again and it began to check the PH98IMG.zip file again (progress bar on right side was increasing). Prompted to update and chose YES again. Screen stayed up the whole time.
About 2 minutes in it completed sbl1, recovery, sbl2, userdata, splash1 and then began to install System.
About 4 minutes in System completed.
After 5 minutes all installation completed (past system, sbl3, trust_zone, bootloader, mdm_cust, adsp, tp, rpm, mdm9k, pgfs_spcustom, radio_v2, radio_cust)
Updates completed, phone went to black screen and back into bootloader. Radio now showed 1.22.10.0310r/1.22.10/0308r
Went through the re-lock process again:
C:\vprasad\htcunlock>fastboot oem get_identifier_token
Click to expand...
Click to collapse
Fed the token in at htcdev.com and got the unlock code, and installed
C:\vprasad\htcunlock>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.144s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.010s]
finished. total time: 0.156s
Click to expand...
Click to collapse
Screen briefly flashed black again and then the bootloader unlock warning appeared on the phone. Agreed w. the terms.
Screen went black again. Phone appeared powered off. After waiting a minute, just decided to power phone back on to see what was up.
White HTC screen and phone booted into OS. PHEW! Did the basic setup.
Enabled USB debugging under settings / develop option on phone
Downloaded / installed OI file manager on the phone and used it to delete the PH98IMG.zip file from the ext sdcard
C:\vprasad\htcunlock>adb reboot bootloader
adb server is out of date. killing...
* daemon started successfully *
C:\vprasad\htcunlock>fastboot flash recovery recovery-ra-vigor-3.14-gnm.img
sending 'recovery' (7074 KB)...
OKAY [ 1.661s]
writing 'recovery'...
OKAY [ 1.837s]
finished. total time: 3.498s
C:\vprasad\htcunlock>adb reboot recovery
adb server is out of date. killing...
* daemon started successfully *
Click to expand...
Click to collapse
In Amon Ra 3.14, did developer menu / install su & superuser. Unfortunately, this was not sufficient for my applications—had to go through zip menu / choose zip from sdcard / su-bin-3.0.3.2-efghi-signed.zip before my applications were able to get get root access.
What were your experiences installing this? I highlighted the times the screen went blank and for how long because that was harrowing!
Also, anybody got an explanation why Amon Ra developer menu rooting does not work properly and why the .zip file is needed?
I really like the play by play. Thanks for taking the time to post it up.
It is likely that amonra root binaries aren't compatible with the new leak. This I am sure will be fixed in the future.
IM running the recent ics leak I'm stock and non rooted. My radio had been updated. Also when wifi is on the 4g icon remains.
Sent from my ADR6425LVW using xda premium
Reboot, it should go back to normal after the reboot.
I'm not even doing this upgrade, but have giving you thanks for the great job describing the steps you did to do it. Easy to follow instructions that clearly lays out what you are doing and what should happen.
Good work.
I am on the New leak and all my contacts don't sync from my Google account. And when I try to add a contact they save automatically to the phone instead of asking me where I want to save em to.
Sent from my Galaxy Nexus using Tapatalk
Reverted to gb and the new radio works. Just restored a nandroid, flashed boot.img in fastboot and flashed scroslers SD fix
Sent from my HTC Flyer P510e using xda premium
I'm stuck with a locked bootloader. The unlock process never completes, just stays at "sending 'unlocktoken' (0 kb)..." but never writes. I've tried it several times over. Apparently I'm the only one having this issue...but I don't understand, to my knowledge I've done everything right. The phone is useable, albeit bone stock on the new RUU so I guess it could be worse. Just no root, no recovery, no unlock, nothing.
socal87 said:
I'm stuck with a locked bootloader. The unlock process never completes, just stays at "sending 'unlocktoken' (0 kb)..." but never writes. I've tried it several times over. Apparently I'm the only one having this issue...but I don't understand, to my knowledge I've done everything right. The phone is useable, albeit bone stock on the new RUU so I guess it could be worse. Just no root, no recovery, no unlock, nothing.
Click to expand...
Click to collapse
Did you go back and re-do the
fastboot oem get_identifier_token
Click to expand...
Click to collapse
and then feed it into the HTCdev.com site and get a new Unlock_code.bin?
Or are you still using the old Unlock_code.bin from (assuming) your very first unlock?
con247 said:
I really like the play by play. Thanks for taking the time to post it up.
It is likely that amonra root binaries aren't compatible with the new leak. This I am sure will be fixed in the future.
Click to expand...
Click to collapse
krelvinaz said:
I'm not even doing this upgrade, but have giving you thanks for the great job describing the steps you did to do it. Easy to follow instructions that clearly lays out what you are doing and what should happen.
Good work.
Click to expand...
Click to collapse
Thanks! The thread where the leak was announced had a lot of high-level explanations on how to do it, but wasn't detailed enough for my comfort, so figured I'd do this in case there are other peeps that want to try it and see how their experiences were ( maybe there are easier ways of doing it that don't require sitting at the edge of the seat )
krazie1 said:
I am on the New leak and all my contacts don't sync from my Google account. And when I try to add a contact they save automatically to the phone instead of asking me where I want to save em to.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Is syncing selected in settings/accounts & sync/google/contacts?
I got confused and tried to do PH98IMG.zip with a flash AmonRa image, and of course once I got that figured out I had to go looking for a working SU.
Right now I'm completely disappointed with battery utilization. Phone is very hot all the time, and I think it's looking for 4g even though I live in an area of spotty coverage and try to keep the networking in CDMA only.
And the batt utilization says 90% of my power is being used by the display, but that's impossible.
cpurick said:
I got confused and tried to do PH98IMG.zip with a flash AmonRa image, and of course once I got that figured out I had to go looking for a working SU.
Right now I'm completely disappointed with battery utilization. Phone is very hot all the time, and I think it's looking for 4g even though I live in an area of spotty coverage and try to keep the networking in CDMA only.
And the batt utilization says 90% of my power is being used by the display, but that's impossible.
Click to expand...
Click to collapse
No thats entirely possible if the phone has not been on very long since its first boot. My screen has used 61% of the current power draw, with only 15 minutes of "screen on" time with 6 hours of total uptime since it was unplugged.
Thanks for the detailed post. I'm going through the process and following your results as a check is very helpful.
No problems here. Was on CleanRom 3.x before trying to update since I wanted to go to 4.x
Relocked. Easy enough. Downloaded RUU file and renamed to PH98IMG. Flashed that. Took a minute and a couple reboots. Once the bootloader says *Tampered* it means you've done it right. I then flashed Amon Ra, the same recovery image from end of February. Flashed the new CleanRom. Been running for the last few hours just fine. Screen is using an inordinate amount of battery but I've been on wifi tether for the last two hours and its currently at 93 degrees Fahrenheit. Granted, I set it on the windowsill with the window cracked but hey. Gotta do what you gotta do.
Check out Cleanrom 4.0 it has a link to a great walk through and in the has a lot of trouble shooting in the commits below the OP.(Sorry cant post links yet)
Related
hello. i recently unlocked my phone through htcdev.com and today i took my shot at rooting the device. i followed the rooting video http://forum.xda-developers.com/showthread.php?t=1225974 to try and root the device and when i got to the flashing the clockworkmod portion, instead of it working it gave me this error
C:\android>fastboot flash recovery cwm-4.0.1.4-shooter.img
sending 'recovery' (4832 KB)...
FAILED (remote: not allowed)
finished. total time: 0.000s
can anyone give me any advice on whats going wrong?
chemicalinferno said:
hello. i recently unlocked my phone through htcdev.com and today i took my shot at rooting the device. i followed the rooting video http://forum.xda-developers.com/showthread.php?t=1225974 to try and root the device and when i got to the flashing the clockworkmod portion, instead of it working it gave me this error
C:\android>fastboot flash recovery cwm-4.0.1.4-shooter.img
sending 'recovery' (4832 KB)...
FAILED (remote: not allowed)
finished. total time: 0.000s
can anyone give me any advice on whats going wrong?
Click to expand...
Click to collapse
Not many of the technical people have unlocked their devices uses the htcdev.co method, most of us have used the revolutionary method was it was released first and seems to unlock more of the device than HTC does.
With that said, based on your above command and error message it would appear the bootloader is not unlocked. Are you sure the HTCdev.com method worked properly?
The only other method for loading a custom recovery, which could work using the HTCdev method would be through ROM Manager in normal android mode, or using my application, Flash Image GUI.
Both these methods just mentioned will require the recovery partition write access to be allowed while booted in normal android mode. This is definitely accomplished with the revolutionary s-off method, but I'm not 100% sure the HTCdev method allows this. If the HTCdev method does not allow recovery write access from normal android mode, then the worse that will happen is the application will say it flashed correctly, but it will not have worked.
Keep us updated as I'm curious how much write access the HTCdev method provides to the internal partitions... hope that helps!
chemicalinferno said:
hello. i recently unlocked my phone through htcdev.com and today i took my shot at rooting the device. i followed the rooting video http://forum.xda-developers.com/showthread.php?t=1225974 to try and root the device and when i got to the flashing the clockworkmod portion, instead of it working it gave me this error
C:\android>fastboot flash recovery cwm-4.0.1.4-shooter.img
sending 'recovery' (4832 KB)...
FAILED (remote: not allowed)
finished. total time: 0.000s
can anyone give me any advice on whats going wrong?
Click to expand...
Click to collapse
Did you happen to skip step 17 prior to flashing recovery by chance?
"Step 17. Put your Evo 3D in fastboot mode by first going to Settings->Power and make sure "Fast boot" is checked off. (Again, yes)."
rleonard55: when i went to turn off the fast boot option I found that it was still off. So i just continued on with the process. I don't know if that has anything to do with the error I had or not.
joeykrim: I know my device is unlocked because when i load it in hboot mode it says unlocked at the top. However I don't know if it was unlocked properly. It may bmhave been an error in my process so I'm gonna try it from the start again. If that doesn't work I will be researching the other methods you mentioned and then proceeding with them.
I also realized I did not have usb debugging mode on So I'm gonna check if that changes anything. I appreciate both of you helping me with this issue. Thanks!
ok so i have tried relocking my device and then unlocking it again and i came out with the same result. i was going to try the GUI app you suggested but you need root access to use it which i do not have. i am trying to root my device through this method which requires cwm recovery. could i possibly temp root my device and then install the recovery through android mode that way? or would that risk bricking my device? also if i can go the temp root method in your application should i have the clear the cashe and dalvik cashe options checked or not?
looking forward to hearing from you
SOLVED!!!!
ok so i figured out exactly what was going wrong. it was a very specific issue. after you have unlocked the device and you are about to flash cwm you must load up hboot (power, vol down) then BEFORE pressing any buttons you must plug in your usb cable. THEN go to fastboot and press power to select it.
the order i was doing it in (hboot, fastboot, then usb cable) was causing the issue because when i did it the other way it flashed with no problem.
thank you for your help and thanks for the app i will definately be using it
chemicalinferno said:
ok so i figured out exactly what was going wrong. it was a very specific issue. after you have unlocked the device and you are about to flash cwm you must load up hboot (power, vol down) then BEFORE pressing any buttons you must plug in your usb cable. THEN go to fastboot and press power to select it.
the order i was doing it in (hboot, fastboot, then usb cable) was causing the issue because when i did it the other way it flashed with no problem.
thank you for your help and thanks for the app i will definately be using it
Click to expand...
Click to collapse
wow! frustrating it was such a small step but definitely good to know. i have a feeling you won't be the only person running into that issue.
thanks for posting back your solution and glad everything is working now!
Yeah no problem glad no one else will have to go through that.
I did run into one other issue or a possible issue. After I installed my root it gave me an "error code:0" now I do have root but I'm questioning if its a full root. I don't know what stuff is specifically locked by HTC's unlock method so I've just been researching to see what I can find out. All I know is in the video I watched his Su install continued doing different installations where mine stopped. I'll figure out what's going on eventually but if its a known issue that has a solution it would definately save me some time.
this is the official error i got
creatng SYSTEM:xin/su symbolic link...
E:error in /sdcard/su-2.3.6.3-efgh-signed.zip
(status 0)
installation aborted
dont know if it matters or not it was the very last step in the root and like i said i have root access. thanks in advance for any response
and yet again SOLVED! lol you just have to install it 3 times in a row
CWM
@ chemicalinferno.
I tried the method of loading hboot first that worked for you but sadly didn't work for me . Any other suggestions?
This may sound like a way off question, but did you unlock using revolutionary or HTC? If HTC when the option to unlock your device appeared (lock screen where you select yes/no) did your phone reboot or did you have to take out the battery?
Thanks
UPDATE: Soooo ****ing weird. I had been trying to get cwm to flash for have the day yesterday (5 hours)
I went to this sight here: http://forum.xda-developers.com/showthread.php?t=1239821
and tried this method. It also wouldn't work. Went to bed at 3 am this morning, woke up at 9:30 this morning. Sat down, looked at the screen, typed in the adb commands and low and behold **** started working??? I didn't do anything different than I did yesterday. But hey, I'm rooted with SU.
Craziest thing every.
chemicalinferno said:
and yet again SOLVED! lol you just have to install it 3 times in a row
Click to expand...
Click to collapse
Hey, I was reading your post and I'm still stuck not able to get past the "fastboot flash recovery cwm-4.0.1.4-shooter.img" step. I'm trying to do exactly as you. Can you tell me exactly what you did that im still stuck as it is stuck in sending 'recovery' <4832 KB>.... and wont do anything else. You are right this is frustrating
IM STUCK IN A BOOT LOOP AND WHEN I TRY TO FLASH FROM FASTBOOT IT GIVE ME AN ERROR WONT LET ME FLASH cwm img FROM FASTBOOT ??? PLEASE ADVISE IM hboot 1.50 AND ext4 RECOVERY BUT MY RECOVERY GOT MESSED UP SO IM TRYING TO FLASH cwm.img FROM FASTBOOT SO I CAN FLASH A KERNNEL AND GET BACK GOING THANKS
I had updated my HTC Evo 3D OTA from 2.3.3 to Android 4.0.3 software version 3.28.707.1 then unlocked it using HTC Method. Unlock success than I flashed recovery with CWM Shooter. Flash success but when I load recovery, the phone just boot up normally. CWM screen not loaded to load custom ROM.
Option 1. ROM Manager says:
You must root your phone for ROM Manager to function. Superuser was not found at "/system/bin/su" or "/system/xbin/su". Use Google Search on your computer to find instruction to root your phone.
Option 2. Superuser apps says:
su binary not found
Option 3. SuperOneClick v2.3.1
Stuck at Step 7. No respond at all.
And, at the command "CheckIfRooted" my device gave result 'false'.
I already tried USB debugging mode, and flash with other .img with other version of CWM. Still not working. Is there any other method to gain superuser access?
New to android. Using a MAC to unlock, root and install senseless ICS. I've unlocked the bootloader via htcdev. Everything worked and now shows unlocked. I downloaded amon ra version 3.11 and installed with this command:
./fastboot flash recovery recovery.img
It seemed to work:
sending 'recovery' (4124 KB)...
OKAY [ 0.908s]
writing 'recovery'...
OKAY [ 1.265s]
finished. total time: 2.173s
When I go back to the fastboot menu and select recovery it goes to the white HTC screen and freezes. At least I think it freezes. Waited 10 minutes and it didn't do anything. I am trying to root the phone now. It looks like I should be able to root by booting into recovery, go to developer and install su. I may be wrong though. Can someone help me with this? I've searched everywhere and there's not a lot of help on using a MAC. My phone boots normally if I don't go to fastboot.
Hey, man I know that its a pain because most people here don't use Macs, or the ones that do have iPhones or whatever but I feel your pain. I'd start from scratch and follow this post from start to finish. I did it and it worked fine.
A couple of notes that you should be careful of:
1. When copying the token identifier from your phone, do not copy the INFO text at the beginning of each line
2. At the end of the process it shouldn't reboot to HTC logo but back into the Hboot screen and say S-off at the top. (If it hangs anywhere after successful completion, try a battery pull and then reboot into hboot)
3. If you got there safely, boot back into your stock rom, and follow this post to flash custom recovery (choose AmonRa NOT cwm).
4. After you flash recovery, flash Super User (non-eng) from within Amon Ra (again follow directions from the post!) and then reboot and you should be perm root. Download Titanium Backup to test and back up your crap before flashing roms or something.
That's how I got mine going from my unibody macbook pro running Lion. Good luck my fellow mac-tard! (I say that with love )
mrmadrid said:
2. At the end of the process it shouldn't reboot to HTC logo but back into the Hboot screen and say S-off at the top. (If it hangs anywhere after successful completion, try a battery pull and then reboot into hboot)
Click to expand...
Click to collapse
I think you meant to say that the phone will say "unlocked" at the top, not S-off.
feralicious said:
I think you meant to say that the phone will say "unlocked" at the top, not S-off.
Click to expand...
Click to collapse
Yep Un-Locked on the top left corner.
are you typing this exactally?
./fastboot flash recovery recovery.img
If so that may be your problem, recovery.img should be whatever the recovery file name is.
I was using the latest amon ra recovery and it wasnt working. I used an older version and it worked. Been running scotts senseless ics for 2 days now. Working very well.
If you want to avoid this issue in the future, don't buy a Mac lol
Sent from my ADR6425LVW using Tapatalk
ok so I am s-off, my hboot says 2.21.0000 and I am running the latest stock ICS leak.
I am doing my darndest to flash RA and get some root going.
When I flash anything via ADB, I am getting
C:\android\platform-tools>adb reboot fastboot
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\android\platform-tools>fastboot flash recovery ra315.img
sending 'recovery' (7078 KB)...
OKAY [ 1.445s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.765s
I have tried renaming the recovery just "recovery.img", it is in the same folder as ADB.
I have even tried flashing the modified hboot again and got the same error message.
What is with the remote not allowed? I do have usb debugging on (I tried on and off)
So fine I figure I am smarter than all that. I figured I would flash it via the PH file, not, acts like it will, but will not.
THen I figured that I would do it via flashing the rooted stock ROM that scott has out....nope again it acts like it will but just will not do anything.
Anyone have any ideas? I did everything before without issue (just got this phone as a replacement)...
Try this....download, rename PH98IMG.zip place on sd card and flash in downloader.
http://db.tt/UuiVjcrb
This is the version of amon ra 3.15 I was able to get to flash while having the same issue.
Sent from my ADR6425LVW using Tapatalk 2
Adb commands may not work due to bootloader being locked. Do not HTC unlock. If you do your bootloader will always say relocated or unlocked. Basically this is why some people flashed eng hboots or had the jouponut bear hboot.
Most people can get by with flashing stuff as ph98img and not worry about messing stuff up and stay on the stock bootloader.
You may want to check the dev section for more info on hboots if you need to use Adb commands and want a modified hboot.
If you unlock after s off, and decide to return to stock its a lengthy process. Scotty has a thread on how to do it. Basically you need to s on, redo s off and then go s on again. After the steps the bootloader will be like Verizon shipped the phone.
When s off first came out, we thought running a ruu would return the bootloader to locked if you unlocked....sadly it didn't. I myself had to redo the process, since I unlocked after s off. Such is life for early adopters.....
Sent from my ADR6425LVW using Tapatalk 2
Thanks a ton for the help. I did flash your AR file, and that seemed to do the trick. I do not know what the difference was between that one and the other 50 I downloaded.
I wasnt really satisfied there though. I ended up nuking the whole thing and going back to GB, flashing RA, then ICS, then the modified Hboot. The whole process went as flawlessly this time as the first time...
Thanks again
piizzadude said:
Thanks a ton for the help. I did flash your AR file, and that seemed to do the trick. I do not know what the difference was between that one and the other 50 I downloaded.
I wasnt really satisfied there though. I ended up nuking the whole thing and going back to GB, flashing RA, then ICS, then the modified Hboot. The whole process went as flawlessly this time as the first time...
Thanks again
Click to expand...
Click to collapse
Glad to hear you got it working.
Sent from my ADR6425LVW using Tapatalk 2
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.
current state: unrooted, s-on, relocked
I successfully unlocked my phone, installed TWRP and attempted to flash a new ROM. Some how I messed up by wiping out system file without backup, and I failed to flash a new ROM either.
So I flashed my phone with RUU latest version (hboot 1.19, radio 1.12.) Now on the bootloader screen it says RELOCKED on top.
When I tried to unlock (normal HTC Dev method) the terminal gave "unlock token checked successfully OKAY", and the unlock confirmation screen showed up normally.
But after rebooting, it turns out my phone is still "RELOCKED." Is there any reason why it doesn't work? And how to reunlock it successfully?
Did you submit the unlock token to htc website so that you can be given the unlock_code.bin file to flash?
---------- Post added at 05:42 PM ---------- Previous post was at 05:41 PM ----------
Never mind I misread the post, try the relock command and unlocking again
Make sure the command is right
Fastboot flash unlocktoken Unlock_code.bin
om4 said:
Did you submit the unlock token to htc website so that you can be given the unlock_code.bin file to flash?
---------- Post added at 05:42 PM ---------- Previous post was at 05:41 PM ----------
Never mind I misread the post, try the relock command and unlocking again
Make sure the command is right
Fastboot flash unlocktoken Unlock_code.bin
Click to expand...
Click to collapse
Here is what happened in my terminal:
C:\android-sdk\platform-tools>fastboot oem lock
...
(bootloader) Device was already locked!
OKAY [ 0.011s]
finished. total time: 0.014s
C:\android-sdk\platform-tools>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.147s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.011s]
finished. total time: 0.164s
After that the green unlock confirmation screen showed up on the phone, I chose unlock, pressed power button, waited for it to reboot, then reboot again to see the bootloader. Still no avail (relocked).
Have you tried flashing twrp anyway?
Use the 2.2.2.0 release, the new 2.3 has some issues that need to be worked out. It may just flash over, and never know
om4 said:
Have you tried flashing twrp anyway?
Use the 2.2.2.0 release, the new 2.3 has some issues that need to be worked out. It may just flash over, and never know
Click to expand...
Click to collapse
Here's what I got:
C:\android-sdk\platform-tools>fastboot flash recovery recovery.img
sending 'recovery' (7356 KB)...
OKAY [ 1.170s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.810s
(I used the img file in 2.2.2.0 twrp zip file. The name is recovery.img)
Does the failure message have something to do with being relocked?
Have you tried the PJ75IMG.zip for twrp. If you are s-off you should be able to install that and not worry about being unlocked.
Sent from my icrap 2 using Tapatalk HD
That shouldn't happen unless phone is still locked or software doesn't match
cruise350 said:
Have you tried the PJ75IMG.zip for twrp. If you are s-off you should be able to install that and not worry about being unlocked.
Click to expand...
Click to collapse
Opps sorry, I'm currently S-On.
om4 said:
That shouldn't happen unless phone is still locked or software doesn't match
Click to expand...
Click to collapse
When I tried to lock the phone again, it says my phone is already locked. But the problem is normal unlock method doesn't work with some reason.
I'm stumped, maybe ruu again?
om4 said:
I'm stumped, maybe ruu again?
Click to expand...
Click to collapse
Done ruu again, but still can't get unlocked.
Maybe it's worth mentioning that after select 'Yes' on the unlock bootloader screen (the green page), the phone didn't reboot. It just turned itself off with red LED charging.
chtat12 said:
Done ruu again, but still can't get unlocked.
Maybe it's worth mentioning that after select 'Yes' on the unlock bootloader screen (the green page), the phone didn't reboot. It just turned itself off with red LED charging.
Click to expand...
Click to collapse
Is there another way around (manual method) for unlocking? To me it looked like some thing after the green confirmation page just didn't work right.
I can't think of any reason it wouldn't work again, maybe someone else will see this and have a fix. Sorry
chtat12 said:
Is there another way around (manual method) for unlocking? To me it looked like some thing after the green confirmation page just didn't work right.
Click to expand...
Click to collapse
You could try downgrading to hboot 1.12 to get s-off...then it won't matter if you're unlocked or not. The process is still pretty new and not for the faint of heart (yet), but seems to be verified working. Check the downgrade sticky thread in the original dev forum for more details.
Sent from my EVO LTE
I would have mentioned it if closeone had a release ready but it's still a bit off. Better to wait then to have someone following directions to purposely brick their phones
premo15 said:
You could try downgrading to hboot 1.12 to get s-off...then it won't matter if you're unlocked or not. The process is still pretty new and not for the faint of heart (yet), but seems to be verified working. Check the downgrade sticky thread in the original dev forum for more details.
Sent from my EVO LTE
Click to expand...
Click to collapse
I believe downgrading method requires an unlocked phone, since it needs twrp for adb commands?
Yes it does, I didn't even remember that lol. I just didn't mention it because right now the overall process is rough
I think the unlock process modified the boot section, and looks like mine is a bit messed up. If so, would 'fastboot flash boot <bootfile>' work? (I don't know where to find it yet, just an another thought.)
chtat12 said:
I believe downgrading method requires an unlocked phone, since it needs twrp for adb commands?
Click to expand...
Click to collapse
Good point...
Sent from my EVO LTE
any resolution to this? i find myself in the same situation