Hi Guys, I have spent the last 2 days searching this forum and trying to understand what I need to do to bring my phone back to stock but can't seem to figure it out and thought I did post a new thread. Here is what I have,
HTC Evo4G
Android version 4.0.4
Baseband version 2.15.00.12.19
Kernal version 2.6.38.8-evervolv-acies-ics+
Build number MIUI-2.8.3.0 MIUI
If I go into recovery mode (the one that u get when u hold down power and volume down button), here is what I see,
*** RELOCKED ***
SUPERSONIC EVT2 SHIP S-ON
HBOOT 2.18.0001
I have tried to run RUU and each time it comes up with "Error 140: Bootloader version error"
Does anyone know how I can return my phone to stock please.
Which RUU are you trying to run? The RUU's Hboot has to be the same as what you already have, meaning it has to be Hboot 2.18.
designflaw said:
Hi Guys, I have spent the last 2 days searching this forum and trying to understand what I need to do to bring my phone back to stock but can't seem to figure it out and thought I did post a new thread. Here is what I have,
HTC Evo4G
Android version 4.0.4
Baseband version 2.15.00.12.19
Kernal version 2.6.38.8-evervolv-acies-ics+
Build number MIUI-2.8.3.0 MIUI
If I go into recovery mode (the one that u get when u hold down power and volume down button), here is what I see,
*** RELOCKED ***
SUPERSONIC EVT2 SHIP S-ON
HBOOT 2.18.0001
I have tried to run RUU and each time it comes up with "Error 140: Bootloader version error"
Does anyone know how I can return my phone to stock please.
Click to expand...
Click to collapse
You have to downgrade your hboot. to 2.10
FinZ28 said:
Which RUU are you trying to run? The RUU's Hboot has to be the same as what you already have, meaning it has to be Hboot 2.18.
Click to expand...
Click to collapse
Thank you.
accessing said:
You have to downgrade your hboot. to 2.10
Click to expand...
Click to collapse
How do I downgrade my hboot to 2.10?
Download the RUU from this link and run it through your bootloader. I believe you will need to rename it PC36IMG.zip for it to work. Make sure you don't have an extra .zip extension on the end.
http://forum.xda-developers.com/showthread.php?t=1484240
To downgrade your Hboot, you can use Captain Throwback's method for rooting Hboot 2.18. It involves using ADB to upgrade your misc. partition, which would then allow you to downgrade by running an older RUU.
Again, which RUU did you try to use originally?
Generally, since you are relocked s-on you can find a signed ruu file in which you can just flash from your relocked bootloader screen or you can run an ruu exe file from your computer. I do not know if there is a method for downgrading your hboot while on s-on but flashing a signed ruu or running an ruu exe will bring your bootloader down. If that don't work, then i would listen to this guy above my post lol and see if that method works.
FinZ28 said:
Download the RUU from this link and run it through your bootloader. I believe you will need to rename it PC36IMG.zip for it to work. Make sure you don't have an extra .zip extension on the end.
http://forum.xda-developers.com/showthread.php?t=1484240
To downgrade your Hboot, you can use Captain Throwback's method for rooting Hboot 2.18. It involves using ADB to upgrade your misc. partition, which would then allow you to downgrade by running an older RUU.
Again, which RUU did you try to use originally?
Click to expand...
Click to collapse
I've been having the same trouble, and already went through CT's method, but still had S-OFF. I then tried going to recovery and flashing unrevoked-forever-son but didnt work. I also installed RUU...4.65 thru PC, still S-OFF, then downgraded to RUU..3.29 tried to run unrevoked-forever-son again and still S-OFF.
I am able to get to stock rom just not back to S-ON
going cuckoo
UPDATE: Found answer: http://forum.xda-developers.com/showthread.php?p=16949711#post16949711
gellybelly said:
I've been having the same trouble, and already went through CT's method, but still had S-OFF. I then tried going to recovery and flashing unrevoked-forever-son but didnt work. I also installed RUU...4.65 thru PC, still S-OFF, then downgraded to RUU..3.29 tried to run unrevoked-forever-son again and still S-OFF.
I am able to get to stock rom just not back to S-ON
going cuckoo
Click to expand...
Click to collapse
I had the same problem also. It took me hours to figure this out. Before you can down grade to an earlier Hboot, you have to make sure the bootloader is unlocked from htc.devs, make sure that recovery is installed, and the phone has "su" rights superuser rights. It is critical that the phone have superuser installed and you have su rights before before you install these 2 files to your sd card. The first file is flash_image then the next one is mtd-eng. http://themikmik.com/attachment.php?...1&d=1327588554 http://themikmik.com/attachment.php?...1&d=1327588554
Unzip these files and copy it to your sd card. Then make sure your phone is in usb debugging mode, then go into command prompt on your pc, then type adb shell. then you should see a $ dollar sign. Type su and and you should see a # pound sign. Then enter these commands below one step a time.
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image misc /sdcard/mtd-eng.img
Then you can install your PC36IMG to your sd card then install the it into bootloader or run the RUU from your pc following the instructions on the program. Make sure your phone is charged up. I prefer a full charge so there won't be issues. If you still have concerns, Re post back and let me know where you are stuck. I followed this guide when I had my supersonic: http://forum.xda-developers.com/showthread.php?t=1473373
Thank You and courtesy of Capt Throwback and THC Butterz for these guides.
Thank you
nice thread guys..been looking for this..:good:
FinZ28 said:
Download the RUU from this link and run it through your bootloader. I believe you will need to rename it PC36IMG.zip for it to work. Make sure you don't have an extra .zip extension on the end.
http://forum.xda-developers.com/showthread.php?t=1484240
To downgrade your Hboot, you can use Captain Throwback's method for rooting Hboot 2.18. It involves using ADB to upgrade your misc. partition, which would then allow you to downgrade by running an older RUU.
Again, which RUU did you try to use originally?
Click to expand...
Click to collapse
Jsparta26 said:
Generally, since you are relocked s-on you can find a signed ruu file in which you can just flash from your relocked bootloader screen or you can run an ruu exe file from your computer. I do not know if there is a method for downgrading your hboot while on s-on but flashing a signed ruu or running an ruu exe will bring your bootloader down. If that don't work, then i would listen to this guy above my post lol and see if that method works.
Click to expand...
Click to collapse
Thanks Guys. I downloaded the RUU and tried to run it from my PC. I went through screens and eventually came up with the error Error [140]: Bootloader version error.
Here are the versions I am on,
From:
Image version:
4.24.651.1
To:
Image version:
4.67.651.3
designflaw said:
Thanks Guys. I downloaded the RUU and tried to run it from my PC. I went through screens and eventually came up with the error Error [140]: Bootloader version error.
Here are the versions I am on,
From:
Image version:
4.24.651.1
To:
Image version:
4.67.651.3
Click to expand...
Click to collapse
Boot into fastboot, and from the path where you have fastboot.exe on your computer, run the command:
Code:
fastboot getvar mainver
and then report back what it says. If your main version is 5.07.651.1, then that RUU won't work, and you'll have to unlock again and downgrade your misc partition to flash back to stock. You should really flash a stock ROM while you're unlocked too. Having an ICS ROM on there and relocking and likely what's causing your issues.
chickipaul said:
I had the same problem also. It took me hours to figure this out. Before you can down grade to an earlier Hboot, you have to make sure the bootloader is unlocked from htc.devs, make sure that recovery is installed, and the phone has "su" rights superuser rights. It is critical that the phone have superuser installed and you have su rights before before you install these 2 files to your sd card. The first file is flash_image then the next one is mtd-eng. http://themikmik.com/attachment.php?...1&d=1327588554 http://themikmik.com/attachment.php?...1&d=1327588554
Unzip these files and copy it to your sd card. Then make sure your phone is in usb debugging mode, then go into command prompt on your pc, then type adb shell. then you should see a $ dollar sign. Type su and and you should see a # pound sign. Then enter these commands below one step a time.
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image misc /sdcard/mtd-eng.img
Then you can install your PC36IMG to your sd card then install the it into bootloader or run the RUU from your pc following the instructions on the program. Make sure your phone is charged up. I prefer a full charge so there won't be issues. If you still have concerns, Re post back and let me know where you are stuck. I followed this guide when I had my supersonic: http://forum.xda-developers.com/showthread.php?t=1473373
Thank You and courtesy of Capt Throwback and THC Butterz for these guides.
Click to expand...
Click to collapse
Captain_Throwback said:
Boot into fastboot, and from the path where you have fastboot.exe on your computer, run the command:
Code:
fastboot getvar mainver
and then report back what it says. If your main version is 5.07.651.1, then that RUU won't work, and you'll have to unlock again and downgrade your misc partition to flash back to stock. You should really flash a stock ROM while you're unlocked too. Having an ICS ROM on there and relocking and likely what's causing your issues.
Click to expand...
Click to collapse
Here is the message I get,
C:\android>fastboot getvar mainver
< waiting for device >
So, what has happened since my last post is that I tried the directions that were given out by chickipaul, however, in trying that I was getting a segmentation error when trying to run '/data/flash_image misc /sdcard/mtd-eng.img' and I read some posts on here that folks having a segmentation error under icecream sandwich should try running the command on gingerbread. Because of that, I tried to put a gingerbread ROM and selected synergy. Now that I have done that, once the phone boots up, it gets to the lock screen Ok. When I try to unlock it, I keep getting messages that some process has died, I click Ok and another message pops up abt another process crashing, and so forth and so forth.
I am hoping that I just need to either install synergy rom again and hope it works Ok or somehow get another gingerbread ROM in there. From there, I could return to stock by installing the RUU. Right now if I run the RUU, the phone never boots into recovery (I think RUU never gets to connect to the phone because of all the processes crashing).
What do u think?
designflaw said:
Here is the message I get,
C:\android>fastboot getvar mainver
< waiting for device >
So, what has happened since my last post is that I tried the directions that were given out by chickipaul, however, in trying that I was getting a segmentation error when trying to run '/data/flash_image misc /sdcard/mtd-eng.img' and I read some posts on here that folks having a segmentation error under icecream sandwich should try running the command on gingerbread. Because of that, I tried to put a gingerbread ROM and selected synergy. Now that I have done that, once the phone boots up, it gets to the lock screen Ok. When I try to unlock it, I keep getting messages that some process has died, I click Ok and another message pops up abt another process crashing, and so forth and so forth.
I am hoping that I just need to either install synergy rom again and hope it works Ok or somehow get another gingerbread ROM in there. From there, I could return to stock by installing the RUU. Right now if I run the RUU, the phone never boots into recovery (I think RUU never gets to connect to the phone because of all the processes crashing).
What do u think?
Click to expand...
Click to collapse
Hi Design Flaw. I just read your current post about what you tried. It sounds like something got corrupted in system files of the phone, that's why your phone is crashing. Question can you get to your bootloader screen by removing the battery for a few seconds, reinstalling the battery then hold volume down and the power button at the same time. If you can get into the bootloader screen where it says on the top of your screen has the Hboot version 2.18 and the S-On. I recommend to unlock the bootloader with your unlock_token file from htc dev first. I will borrow my wife's evo 4g and let her have my evo 3d and try to duplicate the same concern on her phone to help you figure out your phone. Post back here when you have time to work on your phone. I will help you out.
designflaw said:
Here is the message I get,
C:\android>fastboot getvar mainver
< waiting for device >
So, what has happened since my last post is that I tried the directions that were given out by chickipaul, however, in trying that I was getting a segmentation error when trying to run '/data/flash_image misc /sdcard/mtd-eng.img' and I read some posts on here that folks having a segmentation error under icecream sandwich should try running the command on gingerbread. Because of that, I tried to put a gingerbread ROM and selected synergy. Now that I have done that, once the phone boots up, it gets to the lock screen Ok. When I try to unlock it, I keep getting messages that some process has died, I click Ok and another message pops up abt another process crashing, and so forth and so forth.
I am hoping that I just need to either install synergy rom again and hope it works Ok or somehow get another gingerbread ROM in there. From there, I could return to stock by installing the RUU. Right now if I run the RUU, the phone never boots into recovery (I think RUU never gets to connect to the phone because of all the processes crashing).
What do u think?
Click to expand...
Click to collapse
Do you have the HTC Drivers installed? Does your Bootloader say "FASTBOOT USB"? It sounds like either you don't have the drivers installed or you didn't select fastboot from the HBOOT list.
Once it says FASTBOOT USB, then run that command again and post the output.
Unfortunately, you can't downgrade the misc partition while you're on an ICS ROM - that's why you're getting the segmentation fault error.
Flash a stock Gingerbread ROM. Synergy isn't really a good choice.
Captain_Throwback said:
Do you have the HTC Drivers installed? Does your Bootloader say "FASTBOOT USB"? It sounds like either you don't have the drivers installed or you didn't select fastboot from the HBOOT list.
Once it says FASTBOOT USB, then run that command again and post the output.
Unfortunately, you can't downgrade the misc partition while you're on an ICS ROM - that's why you're getting the segmentation fault error.
Flash a stock Gingerbread ROM. Synergy isn't really a good choice.
Click to expand...
Click to collapse
Hey there ... I did not know that I had to run that when I was in bootloader and fastboot usb was being displayed. I was trying to run it when my phone was connected to the PC. I just booted into bootloader and while fastboot usb was up there on the screen, I ran the command and here is what I see,
C:\android>fastboot getvar mainver
mainver: 1.17.651.1
finished. total time: 0.003s
Synergy ROM did not work for me so I had to go back to MIUI.us. Now that I have a working phone and I can copy over files to the phone, I am going to flash urayamashii ROM and see if I can run ruu after that.
Thank you so much for your help!
designflaw said:
Hey there ... I did not know that I had to run that when I was in bootloader and fastboot usb was being displayed. I was trying to run it when my phone was connected to the PC. I just booted into bootloader and while fastboot usb was up there on the screen, I ran the command and here is what I see,
C:\android>fastboot getvar mainver
mainver: 1.17.651.1
finished. total time: 0.003s
Synergy ROM did not work for me so I had to go back to MIUI.us. Now that I have a working phone and I can copy over files to the phone, I am going to flash urayamashii ROM and see if I can run ruu after that.
Thank you so much for your help!
Click to expand...
Click to collapse
If that's your mainver, you should be able to run any RUU or signed PC36IMG.zip.
First though, you need to flash a stock Gingerbread ROM. Every ROM you talk about flashing is not a stock ROM. That's the first thing you need to do. Then you can relock, and I'd run the 4.54 PC36IMG.zip through HBOOT to restore back to stock (you can get it from the "Restore stock" link in my sig).
Captain_Throwback said:
If that's your mainver, you should be able to run any RUU or signed PC36IMG.zip.
First though, you need to flash a stock Gingerbread ROM. Every ROM you talk about flashing is not a stock ROM. That's the first thing you need to do. Then you can relock, and I'd run the 4.54 PC36IMG.zip through HBOOT to restore back to stock (you can get it from the "Restore stock" link in my sig).
Click to expand...
Click to collapse
When you say run 4.54 PC36IMG.zip through HBOOT, what do you mean? If I goto the link that is in your sig and downloaded, that is a RUU and the fullname is PC36IMG_SuperSonic_GB_Sprint_WWE_4.54.651.1_Radio_2.15.00.0808_NV_2.15_release_220182_signed.zip. Can I just rename it PC136IMG.zip and put in the root folder of sdcard and then from bootloader install it?
designflaw said:
When you say run 4.54 PC36IMG.zip through HBOOT, what do you mean? If I goto the link that is in your sig and downloaded, that is a RUU and the fullname is PC36IMG_SuperSonic_GB_Sprint_WWE_4.54.651.1_Radio_2.15.00.0808_NV_2.15_release_220182_signed.zip. Can I just rename it PC136IMG.zip and put in the root folder of sdcard and then from bootloader install it?
Click to expand...
Click to collapse
Yes, that's the link, and the procedure to flash it - but you will have to be relocked first for it to work.
And an RUU is not the same as a PC36IMG file, which is why I made the distinction. One is run from a PC, the other is installed directly from the device.
Captain_Throwback said:
Yes, that's the link, and the procedure to flash it - but you will have to be relocked first for it to work.
And an RUU is not the same as a PC36IMG file, which is why I made the distinction. One is run from a PC, the other is installed directly from the device.
Click to expand...
Click to collapse
Thanks again! So, dumb qs here but why RUU won't work when installing from PC (gives incorrect version error) but when installing directly from device, it is Okay?
designflaw said:
Thanks again! So, dumb qs here but why RUU won't work when installing from PC (gives incorrect version error) but when installing directly from device, it is Okay?
Click to expand...
Click to collapse
I have no idea. It should really work either way. Not sure why it doesn't. Though . . . It could be because the device can't reboot into RUU mode because you're not running it from a stock Gingerbread ROM (like I keep saying you need to flash).
Related
I have an incredible that bootloops at the white screen that was s-on that I got to repair. I tried to flash the gingerbread RUU through hboot and the exe and it still bootlooped. I saw that the official unlock method came out so I updated to the 1.02.0000 hboot and unlocked the phone. I flashed cwm through fastboot but the phone still bootloops. Since the official unlock doesn't allow all the fastboot commands, I can't completely wipe the system or flash different radios, hboot, NV etc. I think this phone is completely bricked unless I can find an RUU that will work with the 1.02.0000 hboot. Since you can't flash RUUs while the phone is unlocked, I have to relock and then I get the main version is older error.
Try flashing this one thru hboot. Its stock GB ruu modified for new hboot.
http://dinc.does-it.net/New_Hboot/StockGB/PB31IMG.zip
And also try this. Its cwm recovery updated for the new hboot.
http://dinc.does-it.net/New_Hboot/CWM_5.2.0.2/PB31IMG.zip
thanks for the files. The RUU reads but stops after parsing. The cwm file does flash correctly, but I still cannot access recovery. I think the partitions are corrupt on the internal memory and I can't ADB in to fix them without recovery. Sucks, I spent way too much time trying to fix this phone. Its perfect condition, but its not worth my time anymore. Hopefully I can resell it for what I paid.
these files need to be stickied somewhere. I searched for around 4 hours on how to root after htcdev unlock and finally found this
the modded RUU wont flash via a locked s-on hboot if its not signed by htc. simply pulling the hboot out wont trick the phone into flashing it,as it breaks the signiture.
if flashing it unlocked,the modified RUU is not working for 1 or both of these reasons:
1)the main version may be higher than that on the android info text doccument
2)you need to also pull splash.nb0 and radio out,as htcdev only lets you access boot/system/recovery.
check your main version number in fastboot with fastboot getvar all
make yourself up an "RUU" using only the system/boot/recovery images,and the Android info text document. if your mainversion is less than 4.08.605.2,then your good to go. just realize that this is going to change it to that. if your main version is higher,then youll have to edit the android info to reflect your current main version before zipping it back up with the images. flash it with bootloader unlocked.
if you can at least get a working custom recovery via htcdev(i use fastboot flash rather than PB31IMGs) then you can flash superuser,and mount data,and rewrite your misc image to downgrade.
we are working on downgrading an htcdev hboot to the .79 in this thread: http://androidforums.com/incredible-all-things-root/495687-htc-dev-unlock-problems.html
and the adb commands and such for rewriting the misc image are in this thread: http://androidforums.com/incredible-all-things-root/427344-how-root-2-3-4-downgrade-get-s-off.html (some specific comments on recovery/adb in post #865)
if you cant get a recovery to permanently flsh,try booting it into memory with unlocked hboot and
fastboot boot <recovery name>.img
unfortunately,ive learned alot about htcdevs limitations with my rezound. holler if i can be of further assistance
cmlusco said:
Try flashing this one thru hboot. Its stock GB ruu modified for new hboot.
http://dinc.does-it.net/New_Hboot/StockGB/PB31IMG.zip
And also try this. Its cwm recovery updated for the new hboot.
http://dinc.does-it.net/New_Hboot/CWM_5.2.0.2/PB31IMG.zip
Click to expand...
Click to collapse
Thanks, I did it with this file and it worked like a charm.
Thanks guys
When I tried the new OTA with a new Incredible I got off of eBay (not rooted or tampered with) it kept messing up half way through and causing my phone to constantly reboot. I restored my phone but when I leave it plugged in with 3G on the OTA messes up my phone again.
I don't have root access so ES Explorer can't delete the .zip in the security folder to stop the OTA.
I've been trying to downgrade the HBOOT and get it to 2.3.3 but it won't work.
I either want it to be full stock or gain S-OFF so I can put CM9 on there. I have HBOOT .98 and can't get it to downgrade.
So, I tried following the following:
http://forum.xda-developers.com/showthread.php?t=1298990
Everything worked fine up until near the end. It says "remote: 99 unknown fail". (SEE 1ST IMAGE)
*NOTE, ERASING CACHE WILL WORK. JUST DIDN'T THIS TIME. I'VE TRIED THIS SUCCESSFULLY UP UNTIL THE REMOTE 99 FAIL*
http://www.youtube.com/watch?featur...v=CgIYFGcVimU&annotation_id=annotation_395071
It's still 2.3.4, Sense 2.1.
My phone is Unlocked but still S-ON. I can't get rid of S-ON no matter what I try and do.
See 2nd image for what my HBOOT looks like.
Can anyone tell me what I'm doing wrong and what steps I need to follow at this point?
Also, can I flash CM9 and delete bloatware even with S-ON?
Thanks!
Someone correct me if I'm wrong, but it seems like the phone was unlocked through the HTC Dev Unlock tool. Have you tried relocking using that?
Sent from my Incredible 2 using xda app-developers app
To my knowledge I didn't use that. Just what is listed on these links.
Where can iI find this program and try to relock?
You need to relock the bootloader before pursuing s-off.
to relock bootloader
Navigate to your adb & fastboot folder
Code:
adb remount
adb reboot bootloader
fastboot devices
fastboot oem lock
Then you should be able to downgrade and s-off.
I cant boot back into the phone.
---------- Post added at 03:10 AM ---------- Previous post was at 02:43 AM ----------
I locked the bootloader and now it just will not boot into the phone. I tried to go into recovery but it just reboots.
Did I just mess up my phone?
sjpritch25 said:
You need to relock the bootloader before pursuing s-off.
to relock bootloader
Navigate to your adb & fastboot folder
Code:
adb remount
adb reboot bootloader
fastboot devices
fastboot oem lock
Then you should be able to downgrade and s-off.
Click to expand...
Click to collapse
Thank you! I actually decided to stick with stock. The new OTA actually worked this time around so I have no issues. IF ICS ends up never coming out, I'll eventually root. I really enjoy Cyanogenmod but for now stock feels safe for me.
You have no idea how much I truly appreciate this. I've been frustrated for a week. Searching all over the internet and doing everything in my power to fix it. All it took.. was that! THANK YOU!
Your welcome...
Now I have no stock recovery. It's a phone image and a red exclamation point. It then boots e3 and says something like "E: can't open cache/recovery/command"
How can I regain stock recovery?
Sent from my ADR6350 using xda app-developers app
Download the gingerbread RUU located http://minus.com/mvivow#1
I recommend renaming before downloading it.
rename it PG32IMG
Be careful with windows because it might rename it as PG32IMG.zip.zip. It won't work.
Move it to the sdcard
reboot into bootloader and allow the update. Its a signed RUU, so it should work.
It says "Main Version is older! Update fail"
Is there a RUU yet for the latest 6.xxxx OTA version?
I used the HTCDev tool to unlock again. At that point I was able to flash an .img of clockwork mod recovery.
When I re-locked I could no longer access Recovery. It said ***SECURITY WARNING*** and would not enter it.
I unlocked again and could use recovery, which is what I'm doing right now.
Am I not allowed to use Recovery with a locked phone?
Also, if I leave my phone unlocked, IF and WHEN there might be an ICS OTA for the Inc 2, can I still download and install while being unlocked?
Thanks!
It would be less confusing if you used the same user name on all the forums you post on.
undergone said:
I used the HTCDev tool to unlock again. At that point I was able to flash an .img of clockwork mod recovery.
When I re-locked I could no longer access Recovery. It said ***SECURITY WARNING*** and would not enter it.
I unlocked the phone again and can now use Recovery. I will stay like this I suppose.
Am I not allowed to use Recovery with a locked phone?
Also, if I leave my phone unlocked, IF and WHEN there might be an ICS OTA for the Inc 2, can I still download and install while being unlocked?
Thanks!
Click to expand...
Click to collapse
Sorry dude.
Here's what is happening now... let me re-clarify.
So I had several issues caused by the latest INC 2 OTA. After the OTA messed up my phone I followed several threads online to downgrade to 2.3.3. After I did this, I updated back to 2.3.4 and then did the new OTA. It worked.
When I did this, "recovery" disappeared in the bootloader.
I eventually unlocked my phone again and was able to flash a custom recovery.img to get clockwork mod recovery back on. Everything was going smoothly!
I then entered recovery and accidentally restored a previous backup (version 5.xxxxx which would power off due to the OTA messing it up). So I immediately did a factory reset.
After this, the Radio is 1.09.01.0312. Every time I boot up it gets stuck on the white HTC screen. I've tried clearing cache, formatting system and then doing a factory reset. It still is the same.
To my knowledge this current radio is the radio for the new OTA (6.xxxxxx). My phone thinks it's software is still 5.xxxxxx due to the accidental restore.
I guess the radio I need ends in .1111. Would not having this radio cause this issue? I downloaded the radio but it says I have to be S-OFF to install it.
I am currently unlocked and S-ON.
Am I screwed or is there anything I can do to fix this?
I can only Fastboot and use CMD prompts. I don't even care if it's a custom rom at this point. Anything I can do to restore the phone.
Please and thank you.
EDIT: Also, PG32IMG files will not work. If I go to manually install it says E: Can't open sdcard/PG32IMG.zip (BAD)
Nor will it go through when I boot it up in the bootloader. I tried this for the version 5.xxxxxx. Do I need to wait for a 6.xxxxxx officiall RUU PG32IMG to come out? I haven't seen one yet.
when you see the red exclamation point press power button and volume up at same time, will put you in stock recovery
Is there ANYONE that can possibly help be fix my phone? I'm still stuck in the white HTC boot screen.
I can only load up in the bootloader.
***UNLOCKED***
VIVO_W XB SHIP S-ON RL
RADIO-01.09.01.0312
eMMC-boot
I need to install the latest software. Is there a RUU yet for the latest 6.xxxx software yet as a PG32IMG?
Any steps to successfully do this would be appreciated.
Could someone with the stock software do a backup, zip the file and send it to me? that way I could put it in the sd/clockworkrecovery/backup and try to make it work.
Thank you.
EDIT: ***HERE IS THE FIX THAT WORKED FOR ME***
Here is how I fixed it: I suggest all others with my issue try this...
Flash the boot.img from this rom: http://forum.xda-developers.com/showthread.php?t=1737494
THEN went into recovery > factory reset > clear cache > wipe dalvik > install zip from SD > install
If you need addition details, how to flash, etc. they can be found here (http://forum.xda-developers.com/showthread.php?p=28262673#post28262673) where I was also given help.
I'm user "telecastertunes" on there.
Good luck!
G'day Guys,
I am trying to root my desire HD. currently 2.3.5
I initially followed the HTCDEV method
For my phone which downloaded the RUU program. PD9810000_Ace_Sense30_S_hboot_2.00.0029.exe
this is for Desire HD Vodaphone australia.
I ran the RUU successfully once. It supposedly upgraded the image from 2.12.178.2 to 3.13.0.0
apon rebooting into the fastboot screen as per the HTCDEV instructions when attempting to fastboot I recieved errors saying
"no image or wrong image" or something to that effect.
at this point I went back to the drawing board and tried the HOW TO ROOT WITHOUT HACK KIT thread (http://forum.xda-developers.com/showthread.php?t=2168500) method and script for unlocking the bootloader. which downloaded the same RUU program
apon running it this time it still wished to updrade from 2.12.178.2 to 3.13.0.0 and i recieved the error
ERROR [191]: Rom is not supported
I have searched several threads with this error however none of them seemed to have a solution ie.
http://forum.xda-developers.com/showthread.php?t=2264987
I cannot locate and temporary ROM zips as per this thread below.
http://forum.xda-developers.com/showthread.php?p=21231962
EDIT Just found and am re-naming the rom zip as PD98IMG.zip then copying it to sd card root folder.
will update thread with result. apologies again
Appologies for the first thread question and its length.
Any help would be much appreciated.
Thanks and Regards
Ben
So I renamed the rom.zip file copied it to the root folder of the SD card.
booted into fast boot. updated
it said "parsing bootloader complete"
however the phone still appears to be 3.12.178.2 ...
the next step
step 8
htcdev[dotcom]/bootloader/unlock-instructions/page-3
"fastboot oem get_identifier_token"
wont run as it sits there <waiting for device>
if I run the RUU again it still says need to update to 3.13 and that its error 191 invalid rom.
help guys
slickncghia said:
G'day Guys,
I am trying to root my desire HD. currently 2.3.5
I initially followed the HTCDEV method
For my phone which downloaded the RUU program. PD9810000_Ace_Sense30_S_hboot_2.00.0029.exe
this is for Desire HD Vodaphone australia.
I ran the RUU successfully once. It supposedly upgraded the image from 2.12.178.2 to 3.13.0.0
apon rebooting into the fastboot screen as per the HTCDEV instructions when attempting to fastboot I recieved errors saying
"no image or wrong image" or something to that effect.
at this point I went back to the drawing board and tried the HOW TO ROOT WITHOUT HACK KIT thread (http://forum.xda-developers.com/showthread.php?t=2168500) method and script for unlocking the bootloader. which downloaded the same RUU program
apon running it this time it still wished to updrade from 2.12.178.2 to 3.13.0.0 and i recieved the error
ERROR [191]: Rom is not supported
I have searched several threads with this error however none of them seemed to have a solution ie.
http://forum.xda-developers.com/showthread.php?t=2264987
I cannot locate and temporary ROM zips as per this thread below.
http://forum.xda-developers.com/showthread.php?p=21231962
EDIT Just found and am re-naming the rom zip as PD98IMG.zip then copying it to sd card root folder.
will update thread with result. apologies again
Appologies for the first thread question and its length.
Any help would be much appreciated.
Thanks and Regards
Ben
Click to expand...
Click to collapse
The top part, the one where you say RUU, that's not a RUU, that just simply updates the HBOOT.
You need to follow this guide.
Steam. said:
The top part, the one where you say RUU, that's not a RUU, that just simply updates the HBOOT.
You need to follow this guide.
Click to expand...
Click to collapse
thanks, yeah i was following that guide.
part of that guide is the "unlock bootloader" portion. I believed thats what the RUU was doing... as those were the steps i was doing.
I was trying to unlock to bootloader. which the guide states you need to do IOT continue on to the ROM steps in the guide you linked.
has anyone had success unlocking the bootloader or any ideas for my issue
thanks for the response. makes sure im on the right path,
Cheers
Ben
slickncghia said:
thanks, yeah i was following that guide.
part of that guide is the "unlock bootloader" portion. I believed thats what the RUU was doing... as those were the steps i was doing.
I was trying to unlock to bootloader. which the guide states you need to do IOT continue on to the ROM steps in the guide you linked.
has anyone had success unlocking the bootloader or any ideas for my issue
thanks for the response. makes sure im on the right path,
Cheers
Ben
Click to expand...
Click to collapse
Use a goldcard to flash a ruu that supports hboot update. That will allow you to unlock the bootloader.
Sent from my GT-N7100 using xda app-developers app
glevitan said:
Use a goldcard to flash a ruu that supports hboot update. That will allow you to unlock the bootloader.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Ok im ready to do this. got my CID... however it appears the Revskills goldcard generator is down and has been for a while
does anyone know of a current goldcard generator that is working.
EDIT:
ok its Alice down the rabbit hole at the moment.
I think I have created a gold card using this tool ... that you posted lol
http://forum.xda-developers.com/showthread.php?t=2288012
there are allot of threads asking for goldcards so hopefully this helps someone.
now i just have to work out how to ... Use a goldcard to flash a ruu that supports hboot update. That will allow you to unlock the bootloader. lol
apologies for the n00bage.
now I have a gold card. just trying to work out the next step to find a RUU that will support hboot update on htcdev
can anyone point me to an appropriate RUU? Glevitan perhaps?
thanks all for the help so far its been great
FYI I completed step 1 from this site http://forum.gsmhosting.com/vbb/f66...-os-s-off-change-imei-cid-hxc-dongle-1548982/
1.root ur phone :for root u mus unlock boot loader with htcdev/bootloader
hboot 2.00.0029 support token key for unlock bl 2.00.0027 stok not support
u must update hboot to 2.00.0029:
download this rom copy to your c:\ drive so download this dhd update hboot by behtash.rar
and run hboot update by behtash.bat in normal mode ,waiting until flash hboot complete
ok u can now unlock bl with htcdev.com\bootloader
however it would not unlock on htcdev it just sat there saying [waiting for device]
I think my fastboot program may be the issue due to it being the same 69k version that this chap had an issue with
http://androidforums.com/cdma-evo-3d-all-things-root/476366-help-w-htcdev-waiting-device.html
downloading sdk
MY current stats are
hboot-2.00.0029
radio-26.14.04.28_m
android 2.3.5
htc sense 3.0
software version 3.12.178.2
slickncghia said:
apologies for the n00bage.
now I have a gold card. just trying to work out the next step to find a RUU that will support hboot update on htcdev
can anyone point me to an appropriate RUU? Glevitan perhaps?
thanks all for the help so far its been great
Click to expand...
Click to collapse
Find what build version and main you are running by using the command in fastboot USB:
fastboot getvar all
Delete the IMEI and paste the outcome
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
glevitan said:
Find what build version and main you are running by using the command in fastboot USB:
fastboot getvar all
Delete the IMEI and paste the outcome
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
I was being a numpty and didnt have sdk installed. I have to crash tonight but will install it tomorrow. then try htcdev again,
if it dosent work i will do as suggested. if its something that simple I will feel a bit stupid. will keep you guys updated.
thanks again all for your help
Ok I have unlocked bootloader. I was being a bit of a numpty and not doing the "get identifier token" command whilst the phone was actually on fastboot... the htcdev instructions confused me.
I will keep this post open as I know i will have more problems as I go.
Thanks all for your help so far
do i have to
3. Download rooted stock rom: http://www.multiupload.nl/20T9R21IGY
(link to rom thread: http://forum.xda-developers.com/show...t=rooted+stock )
copy the ROM zip file to your SD card.
as per http://forum.xda-developers.com/showthread.php?t=2221039
or can I go straight to download a newer rom. a 4.2 or something and continue on the process
Ok, where I am at.
I have flashed the stock rooted rom as per the guide.
it works fine and has root access.
I didnt go through the process for S-OFF from step 6 onwards as I got a little lost what i needed to do as I had already done some of the goldcard steps. either way.
I am currently unlocked and rooted. with 2.3.5 stock rooted rom.
I tried to install a cryogenmod rom and jellytime rom.
as per this page http://forum.xda-developers.com/showthread.php?t=1866122
I installed them from the cwm recovery then tried to "flashboot flash boot boot.img" with their respective boot.img.
both roms didnt progress past the htc boot screen they just black screened.
can anyone hint why these roms wouldnt load? is it an s-on issue? or am i lost with the boot.img or missing another step?
i have reloaded the stock rooted image using cwm and flashboot flash boot boot.img
Thanks all
Ben
The command is "fastboot," not flashboot." Are there any errors when you run it?
bananagranola said:
The command is "fastboot," not flashboot." Are there any errors when you run it?
Click to expand...
Click to collapse
Yeah fastboot was what I was using . Typo sorry. Still not working. Should they work whilst using this method?
slickncghia said:
Yeah fastboot was what I was using . Typo sorry. Still not working. Should they work whilst using this method?
Click to expand...
Click to collapse
Again, is there an error message?
bananagranola said:
Again, is there an error message?
Click to expand...
Click to collapse
Ah appologies I am blind today.
No error msgs. Boot.IMG is coppied over as it is when I do it with the rooted stock Rom.
Just when rebooting afterwards. The phone does its .HTC flash screen for like 30 secs then it goes to a black screen (phone on) indefinitely.
The process I am using is
1 zip Rom on sdcard.
2 cwm delete user data
3 cwm install zip image from sdcard which works
4 reboot
5 fastboot USB
6 from pc: fastboot flash boot boot.IMG (extracted from Rom zip)
Am I doing anything incorrectly or missing a step.
Rooted, unlocked bootloader s-on
Thanks all
Is the phone in fastboot? What ROM? What recovery version?
bananagranola said:
Is the phone in fastboot? What ROM? What recovery version?
Click to expand...
Click to collapse
The phone was in fastboot USB
The working Rom is the one listed shoved from the full root sticky..3.12.405.1 rooted by nitr00
The 2 Roms that failed were jellytime and cryogen. Either the current or most recent stable apparently
Recovery is cwm. It's a slightly older version I think though. It was the only one I could find at the time.
Maybe 2. Something. I'll reboot now and check. Could that be an issue?
Bootloader unlocked
Hboot 2.00.0029
Radio 26.14.04.28m
Cwm recovery v 2.5.1.2
Yay just tried with the latest version of CWM and it works... FFS why wouldnt I have used the current version.
anyway I am playing with 4.2.2 jelly time now.
Thanks so much every contributor. your replies helped me keep going.
Okay so, I had a problem of having no OS and had my htc m8 on soft brick for a while but i finally got that resolved by flashing a new rom on it. ( Here it is if you want to read: http://forum.xda-developers.com/htc-one-m8/help/os-installed-transfer-files-t3018626)
Unfortunately, I wasn't getting wifi on it. I tried 2 other roms and still no dice. I read online that i needed to update my firmware to do that. To do that, I needed to relock my bootloader so I did and the firmware flashed successfully.
Now my hboot is 3.19 instead of 3.16 and my bootloader says RELOCKED.However, when i go into recovery mode, my phone shows a picture of the dead android. I can't get past the bootscreen either so my phone is stuck on bootloader mode.
I found this guide: http://forum.xda-developers.com/showthread.php?t=2497712 to help me get my phone unlocked again cause the unlock code at htc dev wont work again.
However, when i write adb devices, no serial number shows up now. adb shell says no devices connected.
I tried pushing and flashing a new recovery and rom in cmd and it said it failed.
I'm really grasping at straws at this moment since I can't really do anything.
Are you sure you are updated? In the bootloader, what does it say for "os"?
And what roms are you trying to flash? 4.4.4 or Lollipop?
And to unlock bootloader, start over at HTC Dev. See what happens. Instead of trying old code.
You can't flash a recovery with a locked bootloader.
I'm pretty sure it updated because everything looks different. Bootloader's background is black instead of white now too. When I flashed the firmware, everything seemed to be okay as well. . .
my OS says 3.11.1700.5
and i tried it at dev and generated a code, but it gave me an error and didn't give me a file. I tried to use my old file but that didnt work.
Personally, in your situation now..... I'd flash the correct RUU for your device, then use Sunshine to s-off. Then you'll be bootloader unlocked also and can flash recovery, root and all that.
You'll need the same Android version RUU that matches your firmware now.
See this thread,
http://forum.xda-developers.com/showthread.php?t=2701376
Without Sunshine... I can't say why HTC Dev isn't helping.
Darth said:
Personally, in your situation now..... I'd flash the correct RUU for your device, then use Sunshine to s-off. Then you'll be bootloader unlocked also and can flash recovery, root and all that.
You'll need the same Android version RUU that matches your firmware now.
See this thread,
http://forum.xda-developers.com/showthread.php?t=2701376
Without Sunshine... I can't say why HTC Dev isn't helping.
Click to expand...
Click to collapse
Which RUU do I download from here? I'm confused.
Shiverfire said:
Which RUU do I download from here? I'm confused.
Click to expand...
Click to collapse
Read the whole first post. It tells you how to determine that.
Any help needed after trying, you can ask there. ?
I just asked. I'm too confused.
For reference:
version-bootloader: 3.19.0.0000
version-main: 3.11.1700.5
product: m8_ul_ca
modelid:0P6B12000
cidnum: CWS__001
Shiverfire said:
I just asked. I'm too confused.
For reference:
version-bootloader: 3.19.0.0000
version-main: 3.11.1700.5
product: m8_ul_ca
modelid:0P6B12000
cidnum: CWS__001
Click to expand...
Click to collapse
Adb only works in custom recovery or OS.
If your phone shows bootloader, use fastboot to flash custom recovery
SaHiLzZ said:
Adb only works in custom recovery or OS.
If your phone shows bootloader, use fastboot to flash custom recovery
Click to expand...
Click to collapse
I can't flash a recovery because the bootloader is Relocked. I can't unlock it cause my phone wont get detected in adb devices.
I tried manually updating drivers as well. :/
Shiverfire said:
I can't flash a recovery because the bootloader is Relocked. I can't unlock it cause my phone wont get detected in adb devices.
I tried manually updating drivers as well. :/
Click to expand...
Click to collapse
Have you tried flashing a recovery using Hasoon2000 HTC one all in one ?. I had the same problem as you i flashed TWRP then I installed android revolution Hd Rom and it solved my problem but as I said try it may not work as your boot loader is locked..... You can also use the all in one too unlock boot loader might be worth a try
Sent from my HTC One_M8 using XDA Free mobile app
mikem2273 said:
Have you tried flashing a recovery using Hasoon2000 HTC one all in one ?. I had the same problem as you i flashed TWRP then I installed android revolution Hd Rom and it solved my problem but as I said try it may not work as your boot loader is locked..... You can also use the all in one too unlock boot loader might be worth a try
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Like I said, recoveries wont flash cause its stuck on Relocked mode. I cant fix that because adb devices wont see my phone.
All the other commands on the All-in-One root kit gives me this:" 'C:\Users\Admin' is not an internal or external command, operable program or batch file " regardless of where i do it. I don't understand what I'm doing wrong here.
I tried to put the 0p6bimg.zip file but it wont copy on to my sd card cause of some error saying not responding or disconnected.
I tried flashing it instead but it said the file was too large
I tried the latest firmware but it said Failed! verification error.
I tried using the RUU to update and it stopped on the 1/7 process saying Error 155: Unknown Error.
I think what i need to do and how to fix it but I just need adb devices to find my phone.
If i can do that I can unlock my bootloader, install a recovery, install a rom and be home free but I can't do that until it detects my phone. I've tried everything now including reinstalling my drivers three times now.
Please help :'(
You don't need adb devices to see the device. You need to put the phone in the bootloader and type fastboot devices.
Open the command prompt inside the folder where also the fastboot.exe file is located.
Like Mr Hofs said...The bootloader gets unlocked in bootloader/fastboot mode.
Last I remember the code to get the token was "fastboot oem get_identifier_token" and "fastboot flash unlocktoken Unlock_code.bin and not "adb oem get_identifier_token" or "adb flash unlocktoken Unlock_code.bin ...
BerndM14 said:
Like Mr Hofs said...The bootloader gets unlocked in bootloader/fastboot mode.
Last I remember the code to get the token was "fastboot oem get_identifier_token" and "fastboot flash unlocktoken Unlock_code.bin and not "adb oem get_identifier_token" or "adb flash unlocktoken Unlock_code.bin ...
Click to expand...
Click to collapse
No, you guys. I already said this. I already used the htc dev the first time to get my phone unlocked. I had to relock it to flash a firmware. Now I can't unlock it again.The token isn't working. I already used the token once and its not working for the second time. I need adb devices to use adb shell. That way I can adb push revone and unlock my bootloader, but im not sure if that would work either.
Edit: I tried htc dev by generating a code 3 times. It generated different ones, the last one worked.
Ok something is still wrong.
I flashed cwm 6.0.4.8, did a full wipe, installed supersu and installed the android revolution rom. When I reboot, it says I am not rooted, root now? I pressed yes and it reboot.
The phone goes into htc bootscreen for 2 minutes, reboots again and then goes into recovery mode. What do I do now?
Shiverfire said:
Ok something is still wrong.
I flashed cwm 6.0.4.8, did a full wipe, installed supersu and installed the android revolution rom. When I reboot, it says I am not rooted, root now? I pressed yes and it reboot.
The phone goes into htc bootscreen for 2 minutes, reboots again and then goes into recovery mode. What do I do now?
Click to expand...
Click to collapse
Try flashing the boot.img again.
Clear the Cache.
If it still doesn't work then it might be best to just flash the ROM again.
Is your bootloader still show GPE version no. ?
If yes, how do you expect to flash a Sense ROM on GPE partition ?
BerndM14 said:
Try flashing the boot.img again.
Clear the Cache.
If it still doesn't work then it might be best to just flash the ROM again.
Click to expand...
Click to collapse
just flashed the boot.img and recovery.
cleared cashe and reinstalled super su.
same thing.
ckpv5 said:
Is your bootloader still show GPE version no. ?
If yes, how do you expect to flash a Sense ROM on GPE partition ?
Click to expand...
Click to collapse
wait, how do i know if its GPE? (I didnt buy a GPE phone)
I was able to download skydragon and android revolution before, the former was stock lollipop.
So what do I do? how do i install sense roms??
Hello,
so I got the HTC 10 from my brother but I can not get the latest updates via OTA. Reason: Bootload unlocked und TWRP Recovery.
Now I wanna relock the bootloader and back to the Stock Recovery in order to get the OTA upates. I found files in the thread but I do not really know how to proceed at all
Is there any step by step guide for this situation which a newbie would understand?
Some Info's to the phone itself:
Recovery: TWRP 3.03-10_Unofficial
S-On
Unlocked Bootloader
CID: HTC_034
Android 7.0, January Security update
Software: 2.41.401.4
Kernel: 3.18.31-perf-g9ec8cbc and @aabm#1 SMP PREEMPT
Baseband: [email protected]_79.07_F
Is there any way to simply flash the stock recovery again put the bootloader to locked and then get the OTA?
Any help is appreciated
(And no can not ask my brother as he is for several months abroad)
pyo[st said:
;73891974]Hello,
so I got the HTC 10 from my brother but I can not get the latest updates via OTA. Reason: Bootload unlocked und TWRP Recovery.
Now I wanna relock the bootloader and back to the Stock Recovery in order to get the OTA upates. I found files in the thread but I do not really know how to proceed at all
Is there any step by step guide for this situation which a newbie would understand?
Some Info's to the phone itself:
Recovery: TWRP 3.03-10_Unofficial
S-On
Unlocked Bootloader
CID: HTC_034
Android 7.0, January Security update
Software: 2.41.401.4
Kernel: 3.18.31-perf-g9ec8cbc and @aabm#1 SMP PREEMPT
Baseband: [email protected]_79.07_F
Is there any way to simply flash the stock recovery again put the bootloader to locked and then get the OTA?
Any help is appreciated
(And no can not ask my brother as he is for several months abroad)
Click to expand...
Click to collapse
Bootloader status does not affect ability to take OTAs.
You need two things mainly to take the OTA:
1. Stock recovery matching your current software
2. An untouched backup image of the system partition matching your current software. This is needed if you're currently rooted.
Both can probably be found in the thread you linked. The backup image is flashed from twrp. The stock recovery is then flashed from download mode using this command:
Fastboot flash recovery yourrecoveryfile.img
But even after doing that, you might still get an error when trying to take the OTA. Easiest way to take it is to start from scratch, backup your phone's contents to your pc or sd card, and then run the latest ruu for your phone. This will bring you up to date, and will also allow you to make a backup system image from twrp before rooting so that you can easily take future OTAs. The ruu will also completely wipe your phone's contents.
So you can try the first method I mentioned, and if it doesn't work go with the ruu.
As your brother may root it before so the system may got modify, in this case the best and easiest way is flash a RUU.
Try this RUU, http://dl3.htc.com/application/[email protected]_79.07_F_release_495903_signed_2.exe
A RUU will restore your HTC 10 back to stock and wipe out everything. It require a match CID or super CID, if not it will not flash.
I tried to flash RUU via sd card method as well as fastboot method. Both got failed
sd card: Header Error
fastboot: load_file: could not allocate 1950335038 bytes
error: cannot load '2PS6IMG.zip'
Im running on venom rom , S ON with oem unlocked. How can i go back to stock rom??
Mine is 2.41.401.41
DummyPLUG said:
As your brother may root it before so the system may got modify, in this case the best and easiest way is flash a RUU.
Try this RUU, LINK
A RUU will restore your HTC 10 back to stock and wipe out everything. It require a match CID or super CID, if not it will not flash.
Click to expand...
Click to collapse
This RUU worked perfectly. And no the phone was not rooted, just unlocked Bootloader and TWRP as Recovery.
After flashing the RUU I got the July Security Patch and that is what I wanted.
Thank you very much, Problem solved
$tark3 said:
I tried to flash RUU via sd card method as well as fastboot method. Both got failed
sd card: Header Error
fastboot: load_file: could not allocate 1950335038 bytes
error: cannot load '2PS6IMG.zip'
Im running on venom rom , S ON with oem unlocked. How can i go back to stock rom??
Mine is 2.41.401.41
Click to expand...
Click to collapse
It is a EXE, you should run on windows instead of using the sdcard method, as for the not enough space I am not sure about
DummyPLUG said:
It is a EXE, you should run on windows instead of using the sdcard method, as for the not enough space I am not sure about
Click to expand...
Click to collapse
Nah, i downloaded the exe and the zip file also.
Anyway fixed it. Just restored from a nandroid backup. Now back in stock
PS:In btw, anyone facing any battery drop issue??
So I run in another Problem. I got the latest OTA for Europe (July Security Patch) but now my Phone gets shown as uncertified in the google play app which means I can not download certain apps like Netflix via Appstore.
Now I already figured out why I get shown uncertified: the Bootload is still unlocked. I thought the RUU would fix this as well. And if I wanna go in to the recovery (there was an TWRP Recovery on it before) I just get a red triangle with an "!" in it. It wont boot into recovery. Had to hard reset the phone to be able to boot normally to android then.
Now I wanna flash the stock recovery and lock the Bootload again to get again the certified status from google again.
Now here I need help.
1. Can't find the matching recovery version (EU unlocked, July Securtiy Patch, 2.41.401.41). Can anyone help me find the recovery image I need?
2. How do I get the bootload locked again? My Brother unlocked it via HTCdev.com back then, that I know already. But the command fastboot oem lock does not work at all. It just does nothing.
So how can I lock the bootloader?
Thanks for the help.
If you ran the RUU you already have stock recovery...red triangle with an "!" in it.
Are you running the fastboot oem lock from bootloader or download mode?
Sloth said:
If you ran the RUU you already have stock recovery...red triangle with an "!" in it.
Are you running the fastboot oem lock from bootloader or download mode?
Click to expand...
Click to collapse
Haha well then everything is ok with the recovery ^^
I tried both (download and bootloader mode), both times nothing happens. In download mode my PC does not even recognize the phone as the command "adb devices" does not list my phone and the command "fastboot oem lock" does nothing. HTCsnyc installed and ofc adb shell, worked even as when I normally checked with adb devices when my phone was on it was recognized.
pyo[st] said:
Haha well then everything is ok with the recovery ^^
I tried both (download and bootloader mode), both times nothing happens. In download mode my PC does not even recognize the phone as the command "adb devices" does not list my phone and the command "fastboot oem lock" does nothing. HTCsnyc installed and ofc adb shell, worked even as when I normally checked with adb devices when my phone was on it was recognized.
Click to expand...
Click to collapse
Try fastboot devices
Sent from a Glade Plugin.
Sloth said:
If you ran the RUU you already have stock recovery...red triangle with an "!" in it.
Are you running the fastboot oem lock from bootloader or download mode?
Click to expand...
Click to collapse
Sloth said:
Try fastboot devices
Sent from a Glade Plugin.
Click to expand...
Click to collapse
Alright this command works and shows my device.
Now I am in bootloader (Shows Software Status: Modified; Unlocked, S-ON). Then I type in "fastboot oem lock" and I get:
FAILED (remote: unknown command)
finished. total time: 0.014s
Well at least now I get something, before just nothing happened. Any clue what I might do wrong here?
*edit*
So I am a big noob
Phone has to be in download mode then the command works and my phone shows me a message if I want to lock again. Unfortunately it will factory reset my phone as well (at least it says that) so I have to backup my data (again) first.
But thank you for your help, appreciate it.
Cheers!
So I did lock the phone again and flashed again the RUU.exe BUT again my Phone shows in Bootloader Software Status as Modified...and it shows as Relocked.
So how do I get it to official status again?
pyo[st said:
;74318325]So I did lock the phone again and flashed again the RUU.exe BUT again my Phone shows in Bootloader Software Status as Modified...and it shows as Relocked.
So how do I get it to official status again?
Click to expand...
Click to collapse
By buying sunshine S-OFF. Only way to see the bootloader back to "locked" instead of "relocked"
Mr Hofs said:
By buying sunshine S-OFF. Only way to see the bootloader back to "locked" instead of "relocked"
Click to expand...
Click to collapse
Ye found a thread to it. But seems I dont need it. My Phone gets shown as certified again at google play store so I assume just "relocking" the bootloader seems to be enough.
.....