Hello community!!
I'm new to the HTC/Incredible S world, I have a rooted/cfw LG P500 and now I bought this great phone. Problem is that I updated it to the last official version before this try.
So I went to the official site and I followed successfully the HTC site steps to unlock the bootloader (golden card?) and now I'm trying to follow the guide
http://forum.xda-developers.com/showthread.php?t=1385084
But I have some problems.
First of all clearly the revolutionary program doesn't work (HBOOT 2.0).
I booted to the bootloader (power+volume down) and I had the error "main version is older" then I copied on the SD card the file for the recovery PG32IMG_Vivo_Gingerbread_S_KT_KR_2.32.1010.1_Radio_20.2810.30.085AU_3805.06.03.16_M_release_199684_signed.zip, I renamed it PG32IMG.zip, it loads it but when I press recovery it gives me an allert icon (the phone with a red triangle + red "!" ) and it does nothing.
I installed the SuperUser app like it is written in the post but when I type SU under the adb shell and it gives me "permission denied".
What could I do?
Is it even possible to downgrade it to a rootable/customable version?
If someone write a guide for rooting with the last update installed from original s-on step to step will be very util and a lot of people will be gratefull!
Inviato dal mio HTC Desire usando Tapatalk
Bootloader unlock and goldcard are 2 seperate things. Bootloader unlock is required at the moment for flashing recovery and superuser for rooting the phone.
Gold card is required for flashing another carriers rom.
Read this thread about recovery http://forum.xda-developers.com/showthread.php?t=1104765
After that you can enter recovery mode and flash a superuser zip file http://goo-inside.me/superuser/
My guide should be able to downgrade your rom and get s-off after that (if after researching you decide you require it) http://forum.xda-developers.com/showthread.php?t=1373697
Hope this helps
Thanks, I'm going to try this as soon as I can, I'll write back the results
edit:
It seems like I can't even pass the first step, the 4EXT Recovery Updater doesn't work, it crushes at EVERY menu item....
(I waited 5+minutes and I had the internet connection on).
I checked and the boot loader says "unlocked". Notice that my device is, of course, NOT rooted (at least for what I know for "rooted", it is still unlocked by the HTC official method)....
you need root to use the recovery updater.
download the recovery image and flash it in fastboot
Thanks it is finally working!!
I totally forgot that you flash with fastboot via windows console, not within the bootloader....
I hope to finally install something tonight, I'll post some news later.
Thanks again!
edit:
Nothing..I went successfully to the RUU downgrade part but that doesn't work, I tried from the normal system and it blocked because of the hboot version, then I tried within the phone fastboot phase and it blocked again, giving the security failed error...
sariel82 said:
Thanks it is finally working!!
I totally forgot that you flash with fastboot via windows console, not within the bootloader....
I hope to finally install something tonight, I'll post some news later.
Thanks again!
edit:
Nothing..I went successfully to the RUU downgrade part but that doesn't work, I tried from the normal system and it blocked because of the hboot version, then I tried within the phone fastboot phase and it blocked again, giving the security failed error...
Click to expand...
Click to collapse
Could I get a couple of screenshots to help with debugging please?
Sure, ASAP
Hi!
I have successfully rooted my phone on the last update 2.3.5
The steps I made:
1. Going to htcdev and unlocked the bootloader
2. Flashed a recovery image from clockworkmod.com
3. Installed SuperUser from clockworkmod.com using recovery
I collected the information from a few threads here and had no problem.
I didn't tested custom roms, all I wanted was to root and worked just fine.
I can detail my steps if someone need it.
edit:
It seems I cannot post the images, too noob ....
Anyway:
I had a photo of the phone in the custom recovery mode, another of the phone with the 4EXT recovery successfully flashing his recovery, another of the script of your post running with this message:
(no errors)
Do you have an unlocked bootloader from htcdev.com (I have)
y OR n:y
<waiting for device>
...
(bootloader) Lock successfully..
FAILED (status read failed (Too many links))
finished. total time: 0.239s
Note: run the RUU in fastboot mode
If all steps etc etc
Now if I try to run RUU NOT in fastboot mode I receive the message:
The Utility of ROM udating can't update the Android device.
Take a valid ROM updating Utility and try again
(I'm translating from Italian)
If I try to go to fastboot after running the script I need to go to hboot using volume down+power since you can go to fastboot only through bootloader and HIS first step is to check the bootloader file (am I right?)
so, since it is again LOCKED the custom boot file I was using PG32IMG_Vivo_Gingerbread_S_KT_KR_2.32.1010.1_Radio_20.2810.30.085AU_3805.06.03.16_M_release_199684_signed
doesn't work anymore and the old one neither so I have to unlock it again and it goes the loop......
So this is the situation, I hope I will be able to post some image soon...
sergiopat said:
Hi!
I have successfully rooted my phone on the last update 2.3.5
The steps I made:
1. Going to htcdev and unlocked the bootloader
2. Flashed a recovery image from clockworkmod.com
3. Installed SuperUser from clockworkmod.com using recovery
I collected the information from a few threads here and had no problem.
I didn't tested custom roms, all I wanted was to root and worked just fine.
I can detail my steps if someone need it.
Click to expand...
Click to collapse
Thanks, I did too the 3 steps, rooting my device successfully...
But I think I need to do a total S-OFF (deeper than the HTC one) to use the CFWs.
It should be like: follow the above 3 steps and:
4. use some script/console command to prepair the device
5. DOWNGRADE it to 2.2 or something
6. use the "revolutionary" Utility to S-OFF permanently
7. flash the ROMS from the recovery
I cannot pass the 4th step.
sariel82 said:
Thanks, I did too the 3 steps, rooting my device successfully...
But I think I need to do a total S-OFF (deeper than the HTC one) to use the CFWs.
It should be like: follow the above 3 steps and:
4. use some script/console command to prepair the device
5. DOWNGRADE it to 2.2 or something
6. use the "revolutionary" Utility to S-OFF permanently
7. flash the ROMS from the recovery
I cannot pass the 4th step.
Click to expand...
Click to collapse
OK, I thought you only wanted to root.
Thank you anyway
You don't need s-off for CFW's, just the unlocked bootloader. I cannot help you any further until I see screenshots as I'm getting lost in your descriptions. Ctrl prtscrn, paste in paint.
Well, I have the screenshots but I can't post web links in the forum (new user).
Let's see if I can flash some cfw in the mean time
Now I can post
The phone goes successfully in recovery mode:
http://imageshack.us/photo/my-images/406/img20111215194852.jpg/
Screen of the script with the error:
http://imageshack.us/photo/my-images/41/cmdok.png/
The screen of the phone while RUU got the error:
http://imageshack.us/photo/my-images/440/img20111215195909.jpg/
The RUU screen (translation in the posts above):
http://imageshack.us/photo/my-images/703/catturaruunotok.png/
Btw I tried to flash cyanogenmod, revHD e runnydroid following the instructions (wipe all, super wipe etc), every step was successfull, even the flash part (inistall zip from sdcard), but after the reboot it goes in boot loop (standard white HTC loading screen forever)
sariel82 said:
Now I can post
The phone goes successfully in recovery mode:
http://imageshack.us/photo/my-images/406/img20111215194852.jpg/
Screen of the script with the error:
http://imageshack.us/photo/my-images/41/cmdok.png/
The screen of the phone while RUU got the error:
http://imageshack.us/photo/my-images/440/img20111215195909.jpg/
The RUU screen (translation in the posts above):
http://imageshack.us/photo/my-images/703/catturaruunotok.png/
Btw I tried to flash cyanogenmod, revHD e runnydroid following the instructions (wipe all, super wipe etc), every step was successfull, even the flash part (inistall zip from sdcard), but after the reboot it goes in boot loop (standard white HTC loading screen forever)
Click to expand...
Click to collapse
After you flash a custom ROM in recovery, you have one last step to do to prevent the hang. You extract the boot.img file from the ROM's zip file and then manually flash it in FASTBOOT mode on the phone:
FASTBOOT flash boot [path to boot.img]
That totally solved the problem
Thank you ALL!!!
sariel82 said:
That totally solved the problem
Thank you ALL!!!
Click to expand...
Click to collapse
Hi,
Please list the methods you use from the start. I have also 2.3.5 and hboot 2.0. cant manage to downgrade, i always getting an error.
Thanks
htc developer site -> unlock bootloader
find and download this file:
PG32IMG_Vivo_Gingerbread_S_KT_KR_2.32.1010.1_Radio _20.2810.30.085AU_3805.06.03.16_M_release_199684_s igned.zip
copy it on the sd card and renamto to pg32IMG.zip
reboot in power+volume down mode
go in fastboot
from your pc use fastboot to flash this recovery:
http://forum.xda-developers.com/showthread.php?t=1104765
copy to sd card the superuser file:
http://goo-inside.me/superuser/
enter recovery mode and flash the zip
Then if u want to flash a custom rom you dont need to downgrade, just copy the zip into the sd card, flash it, copy on the sd card the boot.img you find inside the rom zip file and reboot in fastboot (power+volume down)
FASTBOOT flash boot [path to boot.img]
and reboot and the job is done!
Related
Device Details:
Carrier: Sprint
Android OS: 1.5 (Cupcake)
Bootloader details:
Hero XC
HBOOT-1.41.0000 (HERO20000)
MICROP-0110
TOUCH PANEL-SYN0104
RADIO-1.04.01.09.21
Sep 1 2009, 19:18:45
Right now I am tinkering with the Linux kernel for the HTC Hero. I am able to build the kernel source from the HTC website and have access to root on the device. However when attempting to flash the zimage using fastboot it gives the error "(Remote: not allowed)"
While searching through the forums I have found that there are additional steps that needed to be done to fully root the device. I have followed the instructions on the following thread.
http://forum.xda-developers.com/showthread.php?t=583291
After flashing the recovery image and sending the command to reboot into recovery mode, the device will start up at the HTC splash screen and will not continue further for upwards of 15 minutes (I have not tried waiting much longer)
I have also attempted the flashrec method outlined here.
http://forum.xda-developers.com/showthread.php?t=603052
Recovery mode yields the same results when booting into recovery mode from shell or from hboot's home button. Has anybody ran into this problem and found a solution? If so, please provide direction.
do u realize the methods u are using are over a year old.
just had to put that out there...
dlongestopp said:
Device Details:
Carrier: Sprint
Android OS: 1.5 (Cupcake)
Bootloader details:
Hero XC
HBOOT-1.41.0000 (HERO20000)
MICROP-0110
TOUCH PANEL-SYN0104
RADIO-1.04.01.09.21
Sep 1 2009, 19:18:45
Right now I am tinkering with the Linux kernel for the HTC Hero. I am able to build the kernel source from the HTC website and have access to root on the device. However when attempting to flash the zimage using fastboot it gives the error "(Remote: not allowed)"
While searching through the forums I have found that there are additional steps that needed to be done to fully root the device. I have followed the instructions on the following thread.
http://forum.xda-developers.com/showthread.php?t=583291
After flashing the recovery image and sending the command to reboot into recovery mode, the device will start up at the HTC splash screen and will not continue further for upwards of 15 minutes (I have not tried waiting much longer)
I have also attempted the flashrec method outlined here.
http://forum.xda-developers.com/showthread.php?t=603052
Recovery mode yields the same results when booting into recovery mode from shell or from hboot's home button. Has anybody ran into this problem and found a solution? If so, please provide direction.
Click to expand...
Click to collapse
go to the search box at the top of the paige and put in
"z4root apk for hero cdma" and use it
oostah said:
go to the search box at the top of the paige and put in
"z4root apk for hero cdma" and use it
Click to expand...
Click to collapse
Thank you for the response. Currently my device is running Android 1.5 so it cannot install this. I will try updating the OS in order to install it.
well, my best advice is this: hopefully you can run an RUU.exe while connected to fastboot. Follow the logical links in my links thread listed below, once you have RUU'ed to android 2.1, then root by whatever method you wish from my thread, hope this helps.
http://forum.xda-developers.com/showthread.php?t=1063843
EDIT: you may also be able to update officially from www.htc.com/support
EDIT 2: there are also links there to unlock the nand and bootloader AKA "s-off" so that you can fastboot flash your kernel. But look around in the development section, A LOT has happended since 1.5 lmao. Like custom fast kernels and nice ROMs and such.
il Duce said:
well, my best advice is this: hopefully you can run an RUU.exe while connected to fastboot. Follow the logical links in my links thread listed below, once you have RUU'ed to android 2.1, then root by whatever method you wish from my thread, hope this helps.
http://forum.xda-developers.com/showthread.php?t=1063843
EDIT: you may also be able to update officially from www.htc.com/support
EDIT 2: there are also links there to unlock the nand and bootloader AKA "s-off" so that you can fastboot flash your kernel. But look around in the development section, A LOT has happended since 1.5 lmao. Like custom fast kernels and nice ROMs and such.
Click to expand...
Click to collapse
Thanks for your suggestion
I didn't realize there was an official 2.1 update until now since there was no over-the-air update for this device.
dlongestopp said:
Thanks for your suggestion
I didn't realize there was an official 2.1 update until now since there was no over-the-air update for this device.
Click to expand...
Click to collapse
Holy crap lol. I think the update to 2.1 was in august or something, wow. How did you not know? I would think sprint would have told you at some point in an email or text or if you ever called them for tech help. Anyway, yeah hunt around those links, ask questions back in here if you need help.
once u get everything going this thread will be your best friend and be sure to thx duce for it.
http://forum.xda-developers.com/showthread.php?t=1063843
il Duce said:
Holy crap lol. I think the update to 2.1 was in august or something, wow. How did you not know? I would think sprint would have told you at some point in an email or text or if you ever called them for tech help. Anyway, yeah hunt around those links, ask questions back in here if you need help.
Click to expand...
Click to collapse
Thanks for the assistance. I have updated my Hero to the official 2.1, then attempted rooting with z4root. It would freeze at the reboot screen for about 10 minutes, yet still rooted the phone (except the recovery partition)
I had tried using fastboot to load my own zImage, but it would continue giving me the "Remote: not allowed" error. After that, I unrooted through z4root to undo my changes and used RegawMOD Hero Rooter v1.3 which installed clockworkmod as the recovery partition. (http://forum.xda-developers.com/showthread.php?t=909258 )
Once I had done this, I was able to boot into the recovery partition and use the unrevoked-forever boot to have hboot turn to "S-OFF" ( http://forum.xda-developers.com/showthread.php?t=759955 ) which seemed to work. However, when runnning
Code:
fastboot flash image zimage zImage
It gives me the same Remote: not allowed. I saw a post for using fastboot without s-off by booting into RUU mode, however it would not recognize the zimage partition.
Do you have any more suggestions?
I really appreciate your assistance
dlongestopp said:
Thanks for the assistance. I have updated my Hero to the official 2.1, then attempted rooting with z4root. It would freeze at the reboot screen for about 10 minutes, yet still rooted the phone (except the recovery partition)
I had tried using fastboot to load my own zImage, but it would continue giving me the "Remote: not allowed" error. After that, I unrooted through z4root to undo my changes and used RegawMOD Hero Rooter v1.3 which installed clockworkmod as the recovery partition. (http://forum.xda-developers.com/showthread.php?t=909258 )
Once I had done this, I was able to boot into the recovery partition and use the unrevoked-forever boot to have hboot turn to "S-OFF" ( http://forum.xda-developers.com/showthread.php?t=759955 ) which seemed to work. However, when runnning
Code:
fastboot flash image zimage zImage
It gives me the same Remote: not allowed. I saw a post for using fastboot without s-off by booting into RUU mode, however it would not recognize the zimage partition.
Do you have any more suggestions?
I really appreciate your assistance
Click to expand...
Click to collapse
regaws s-off allows flashing HERCIMG.zip to any partition, in your case the boot.img. The ohter s-off method by darch allows fastboot commands. You should read up on regaws way. All you need is a zip that contains a boot.img and an android-info.txt. If you wish to flash darchs s-off methos over top of regaws you CAN do that, I did that myself. That way you can use whatever method you wish. There are links in my links thread. Good luck.
il Duce said:
regaws s-off allows flashing HERCIMG.zip to any partition, in your case the boot.img. The ohter s-off method by darch allows fastboot commands. You should read up on regaws way. All you need is a zip that contains a boot.img and an android-info.txt. If you wish to flash darchs s-off methos over top of regaws you CAN do that, I did that myself. That way you can use whatever method you wish. There are links in my links thread. Good luck.
Click to expand...
Click to collapse
Thanks again I used regaw's method to overwrite the recovery partition (http://forum.xda-developers.com/showthread.php?t=694572 ) afterwards used the new recovery partition to flash the hboot ( http://forum.xda-developers.com/showthread.php?t=765237 )
I can now flash using fastboot.
Hi,
So I decided to flash a ROM for the first time. Followed the steps from this:
http://forum.xda-developers.com/showthread.php?t=1337105
and got everything working with Cyanogenmod 7.1.
Whilst browsing I came across this interesting ROM:
http://forum.xda-developers.com/showthread.php?t=1312021&page=7
Copied it to SD card and flashed it. Everything went well. However, my phone is stuck in the loading screen. This already happened once. It's actually the second time I'm trying to flash this ROM. The first time I removed the battery after I spent an hour waiting in the loading screen; but that didn't help.
Anyone can help or give suggestions pls? Any help is appreciated.
Thanks in advance.
Incredible2011 said:
Hi,
So I decided to flash a ROM for the first time. Followed the steps from this:
http://forum.xda-developers.com/showthread.php?t=1337105
and got everything working with Cyanogenmod 7.1.
Whilst browsing I came across this interesting ROM:
http://forum.xda-developers.com/showthread.php?t=1312021&page=7
Copied it to SD card and flashed it. Everything went well. However, my phone is stuck in the loading screen. This already happened once. It's actually the second time I'm trying to flash this ROM. The first time I removed the battery after I spent an hour waiting in the loading screen; but that didn't help.
Anyone can help or give suggestions pls? Any help is appreciated.
Thanks in advance.
Click to expand...
Click to collapse
You may need to manually flash the boot.img from the ROM's zip file If you unlocked HBOOT 2.00.
You need to flash it in FASTBOOT USB mode using the command:
fastboot flash boot boot.img
Oh y forgot about that! Thing is I'm now stuck in the HTC loading screen instead of the ROM loading screen...
Press and hold the volume down key while starting the phone.
Then you are in boot menu you go to "fastboot". Connect the phone to the computer and you can work with adb and fastboot.
How his work you see in the developer forum.
Success...
Don't quite get what you mean...sry I'm kinda new at this. Thing is the ROM has been flashed; checking the SD card the files have been copied.
However, every time I try to boot the new ROM I get stuck at the HTC loading screen with no way out but to remove the battery.
So I flashed the boot.img and now I'm stuck in the HTC loading screen instead of the ROM loading screen. Any possible solution pls?
I'm just guessing here as I have never had this problem.
It's always went well for me, takes a while to boot first time but never an hour!
Did you do an MD5 check on the ROM you downloaded?
Try this.
Boot into recovery (Hold volume down and power)
Format all partitions apart from SDCard (I think it's System, Data and Cache)
Clear Cache
Clear Davlik-Cache
Re-flash rom.
Also would be wise to update your recovery first. (You will need to use fastboot to do this probably)
Not sure if this will work, but it definatly won't hurt you.
If it doesn't work, get a different ROM in a zip, flash through recovery see if you can boot phone.
I'm going to sound like a total noob now but I'm kinda new at this...what is an MD5 check?
MD5 checksum is to verify the file you have on your computer is exactly the same as the uploader. The uploader will generate an MD5 checksum, you generate an MD5 checksum using any program (google or some ROM manager apps) and if they match you're fine, but if they dont then it means your file has an error/is incomplete and flashing it will cause an error.
It sounds like the stuff you've done already is probably fudged so I would start over by clearing/formatting all the cache (dalvik is important), doing a complete wipe of the system (not including the SD card of course), re-download the ROM you tried and flash it in recovery, and immediately flash the boot.img file (extract it from your new ROM) from fastboot.
Wow gee thanks so much info! Will try everything from scratch and see how that works out. Thanks once again.
Could it be that I need to S-OFF my phone? It's still S-ON.
How did you flash the boot.img?
Being s-on it has to be done through your pc using fastboot commands. If you just copied it to sd card it won't work.
Try flashing rom again, then boot phone into fastboot usb mode. Flash boot.img with the command written above.
What version of hboot are you on?
Y I used my PC to flash the boot.img. HBoot 2.00 here.
If you're set on flashing other ROMs (if you don't want to restore the CM backup) it will be easier in the long run to just downgrade to HBOOT v1.13 so you can S-OFF and have no further problems flashing ROMs due to the locked bootloader.
Guide with many thanks to Nonverbose: http://forum.xda-developers.com/showthread.php?t=1373697
Remember to carefully read everything if you do that!
Incredible2011 said:
Y I used my PC to flash the boot.img. HBoot 2.00 here.
Click to expand...
Click to collapse
best thing is to flash boot img as i see from your postings that you don't know that much (earlier i was the same)
but if you do go for downgrade i suggest these things
read the full guide as soothsayer suggested.
with me and i think many of us an error appeared on the bootloader saying relocked security warning when you lock the bootloader again
don't worry
reboot your bootloader, connect your phone and start the ruu exe named ruu needed for downgrade and voila your hboot will be downgraded!
...guys I was looking around, but couldn't find answer for my little problem. I have rooted HTC One, but rom is stock (didn't plan to change it at all just needed root), but the problem is today a new update came up, and when I tried to install it, it simple didn't do anything.
I go on Install now, phone restarts in recovery mode, then it gives me Installation aborted, and I have 3 thingies, - No; - Yes - Disable recovery flash: - +++++Go Back+++++
Whatever I choose, it just restarts and asks again for same recovery. What shall I do?
In console stands this:
ClockworkMod Recovery v6.0.3.4
E: Invalid command argument
E: Invalid command argument
Warning: No file_contexts
Finding update package...
E: unknown volume for path [DATA:data/cp,/amdrpod_HTC_Europe_2.24.401.8-2.24.401.1_release_331108tottoh71qygw07hf.zip]
E: Can't mount DATA:data/cp,/amdrpod_HTC_Europe_2.24.401.8-2.24.401.1_release_331108tottoh71qygw07hf.zip
Installation aborted
It seems that it cannot mount or something?!?
Cheers...
rex1825 said:
...guys I was looking around, but couldn't find answer for my little problem. I have rooted HTC One, but rom is stock (didn't plan to change it at all just needed root), but the problem is today a new update came up, and when I tried to install it, it simple didn't do anything.
I go on Install now, phone restarts in recovery mode, then it gives me Installation aborted, and I have 3 thingies, - No; - Yes - Disable recovery flash: - +++++Go Back+++++
Whatever I choose, it just restarts and asks again for same recovery. What shall I do?
In console stands this:
ClockworkMod Recovery v6.0.3.4
E: Invalid command argument
E: Invalid command argument
Warning: No file_contexts
Finding update package...
E: unknown volume for path [DATA:data/cp,/amdrpod_HTC_Europe_2.24.401.8-2.24.401.1_release_331108tottoh71qygw07hf.zip]
E: Can't mount DATA:data/cp,/amdrpod_HTC_Europe_2.24.401.8-2.24.401.1_release_331108tottoh71qygw07hf.zip
Installation aborted
It seems that it cannot mount or something?!?
Cheers...
Click to expand...
Click to collapse
Because HTC's updates only work on stock recovery.
Sent from my One using xda app-developers app
Tw1tchy said:
Because HTC's updates only work on stock recovery.
Sent from my One using xda app-developers app
Click to expand...
Click to collapse
Is there a way to update my phone now?
re
is it enough to put in cmd throuhg adb the "fastboot oem lock" command, since my rom is already stock?
Or do I need to flash stock recovery?
Cheers...
rex1825 said:
is it enough to put in cmd throuhg adb the "fastboot oem lock" command, since my rom is already stock?
Or do I need to flash stock recovery?
Cheers...
Click to expand...
Click to collapse
I'm sure you need stock recovery.
Sent from my One using xda app-developers app
Tw1tchy said:
I'm sure you need stock recovery.
Sent from my One using xda app-developers app
Click to expand...
Click to collapse
...ah, I knew it. I presume that stock recovery can't be flashed from custom recovery.
So I need to flash stock recovery, then to lock bootloader, and then I guess I'm good to go!?!
Can I flash it from custom recovery, or do I need to flash it differently? Anyone has link for it, or are all stock recoveries same (I mean from different providers)?
Thanks
You need to install stock recovery using fastboot command "fastboot flash recovery recovery.img"
AllAboutTheCore said:
You need to install stock recovery using fastboot command "fastboot flash recovery recovery.img"
Click to expand...
Click to collapse
...so only stock recovery, I do not need fastboot lock or something?
Cheers...
rex1825 said:
...so only stock recovery, I do not need fastboot lock or something?
Cheers...
Click to expand...
Click to collapse
Install stock recovery like I said above, once done type the following :- "fastboot oem lock"
You should be good to go then for the update. Re-locking your bootloader doesn't wipe your files either, only unlocking wipes the internal storage.
...OK, so here is what I did. From ADB restored the original recovery.img, then lock bootloader, and viola. Thanks guys for helping me out.
Cheers...
Edit: ...I forgot to uninstall SuperSU, and now I have a shortcut in apps and it cannot be removed. When I run it, phone says: "There is no SU binary installed, and SuperSU cannot install it. This is a Problem!" ...lolz me, what to do?
rex1825 said:
...OK, so here is what I did. From ADB restored the original recovery.img, then lock bootloader, and viola. Thanks guys for helping me out.
Cheers...
Edit: ...I forgot to uninstall SuperSU, and now I have a shortcut in apps and it cannot be removed. When I run it, phone says: "There is no SU binary installed, and SuperSU cannot install it. This is a Problem!" ...lolz me, what to do?
Click to expand...
Click to collapse
Just do update then reroot phone as before that's what I did but more than likely you won't be able to soff using revone th world have to use htcdev method
Sent from inside the T.A.R.D.I.S
joselv456 said:
Just do update then reroot phone as before that's what I did but more than likely you won't be able to soff using revone th world have to use htcdev method
Sent from inside the T.A.R.D.I.S
Click to expand...
Click to collapse
What is all this about S-Off and HTCDev ... You unlock your bootloader through HTCDev, S-Off is NOT something that can be done any other way than Revone and Moonshine and NOT on Hboot 1.54 ... Yet.
I've seen several people mention S-Off and HTCDev in the same breath and I think some of you are getting it all mixed up. Unlocking the bootloader and going S-Off are not the same thing and only unlocking the bootloader can be done through the HTCDev website.
I'm pretty sure HTC aren't going to help you remove the security from your device.
I stand corrected you are correct I had soff before that's why I guess it wasn't reset after update
Sent from inside the T.A.R.D.I.S
Original recovery and lock oem doesn't help.
Lads,
Would someone give me a hand here please.
There is a major update for HTC One.
I've flashed original recovery and locked back the phone.
Now it's downloading the update, then goes into reboot and opens fastboot bootloader, instead of installing the update.
What am i doing wrong here?
Thanks in advances
Hi,
I have the same problem as OP.
However the instructions in the replies are terribly confusing, I don't even know where to start!
Someone could do a step-by-step summary for less expert (or just android-retarded) people ?
Thanks a lot!
further to my post above
You need to be on stock recovery. Figure that out and you should be good.
Looking at the various guides somehow related to stock recovery doesn't make sense to me.
There's too many things I am not aware of such as how to flash the stock recovery, if the process will wipe all data, what is a fastboot command etc. etc. Has anybody ever created an easy guide to assess the problem?
AllAboutTheCore said:
What is all this about S-Off and HTCDev ... You unlock your bootloader through HTCDev, S-Off is NOT something that can be done any other way than Revone and Moonshine and NOT on Hboot 1.54 ... Yet.
I've seen several people mention S-Off and HTCDev in the same breath and I think some of you are getting it all mixed up. Unlocking the bootloader and going S-Off are not the same thing and only unlocking the bootloader can be done through the HTCDev website.
I'm pretty sure HTC aren't going to help you remove the security from your device.
Click to expand...
Click to collapse
I have HBOOT 1.54 and S-OFF with rumrunner_HTC_0.5.0
-marco- said:
further to my post above
Click to expand...
Click to collapse
For the sake of common knowledge and in case it may help other unknowing people like me, I'll post what I did here:
I sort of mixed these two guides: this one and this.
Premise:
A. It was impossible to make this whole thing run on my Win8.1 x64 computer. It would never recognize my Fastboot USB device plugged in. I had to use bloody WINXP x86 on my old-ass netbook....
B. Somehow I still had my fastboot/adb compiled folder that I used back in time to root my HTC at first.
C. My phone was Tampered, Unlocked, with HBOOT (i think 1.44 ?) and most definitely S-OFF I would say ? Still don't know for sure.
D. I updated from 4.1.2 through 4.2 to 4.3.
At the 4.2 upgrade the phone went on black screen twice (1st time at ~25%, and 2nd time after 100% was complete). Panic is useless in that case. I went to the bathroom, blasted the strongest lights I had and exposing the phone to the lights, I pressed the power button til the capacitative buttons blinked. After a while the phone rebooted and resumed exactly from the point it blacked out before.
The update to 4.3 went smooth as oil instead.
This is each step I did, following the quoted guides above:
1. Extract the stock recovery file (should be .img) that can be found in the OTA update firmware.zip file, in the firmware package (in some other thread it's explained the path of this file). Place the file in the folder with your fastboot commands.
2. Make sure fastboot and USB Debugging are unchecked on your phone in power settings>fastboot.
3. Power down phone by holding power button and pressing shut down.
4. Once phone is shut down, power phone into bootloader by holding volume down button and pressing power button.
5. Once in the bootloader navigate until it says fastboot usb (must have phone connected to computer).
6. Open up a command prompt where your fastboot commands are located.
7. Type the following with the filename of the stock recovery:
Code:
fastboot flash recovery <filename>
8. Navigate in the bootloader menu to the reboot option to restart your phone.
9. Download the latest SuperSU and place it on your sdcard.
10. Perform the OTA update normally.
11. Once it finishes installing, power down the phone like before and get back to fastboot usb.
12. Flash back the custom recovery using fastboot (I used latest CWM available):
Code:
fastboot flash recovery <filename>
or
Code:
fastboot flash zip <recovery>.zip
13. Then type :
Code:
fastboot reboot
14. Enter recovery by navigating with the volume buttons. Once in recovery, flash the zip of the SuperSU file you previously downloaded.
15. Restart once flashing is complete.
Hello
first my problem was:
Quote:
Originally Posted by mara_hr
to cut the long story short, i have formated data on my htc one m7 without making backup (i know)
i have downloaded several roms and am able to read them though usb-otg without problem.
problem occurs when i try to flash them:
Error log:
Skipping MD5 check: no MD5 file found.
assert failed: getpro()
E:Error executing updater binary in zip
Error flashing zip
But when i try to flash android revolution HD 81 - Android revolution 81 , he reads the rom, starts to flash it but screen doesnt respond. volume keys and power keys respond, but you can not say where is the key??
please help
i use TWRP v2.5.0.0
is there any way to update twrp? (latest roms require 2.6 twrp or higher???)
Download the 2.6.3.3 version of TWRP, rename the file to recovery, place the .img file in the folder on your PC where ADB is located and then flash in fastboot with fastboot flash recovery recovery.img. After that command completes, run fastboot erase cache. Then you can copy the ARHD 81 .zip to your phone and flash away.
after that i have tried:
So now you probably have screwed your partitions flashing an incompatible rom and recovery to your phone. Flash a twrp version for Sprint variant and then format data and flash a Custom rom compatible with Sprint phones (M7WLS)
Sprint TWRP here: http://techerrata.com/browse/twrp2/m7wls
Sprint roms here: http://forum.xda-developers.com/spri...ne/development
i have flashed sprint twrp and sprint roms:
Bad Boyz Sprint ONE ROM 4.4.2 Sense 6 v1.0
ROM] Eragon v53Stable&clean|Sense/Aosp/GPE mix, ROM for the HTC One
Sprint_Eragon_V_54.0.0.zip
ViperOne 7.0.1
and they all have same issue.
installation went well. on first boot rom went to lock screen. after unlocking only white screen occurs with green htc logo.
after that dialer app reports crushing
what to do next?
do i need to unlock sprint sim since i live in croatia (europe)?
thanks for help
You should RUU and get everything working the way it should again.
Then flash a rom from the Sprint section.
BD619 said:
You should RUU and get everything working the way it should again.
Then flash a rom from the Sprint section.
Click to expand...
Click to collapse
thx for repling
im a bit of a n00b. can you send me a link or something how to do that? thank you
mara_hr said:
thx for repling
im a bit of a n00b. can you send me a link or something how to do that? thank you
Click to expand...
Click to collapse
android revolution HD 81
Click to expand...
Click to collapse
bruhhh
NOTE: Read the threads, the instructions I'm giving you are just for you to gauge the difficulty of this task, to see if you can do it. Don't follow my instructions! Read the threads!
Read this first.
Then get this firmware.zip and put it in your adb/fastboot folder
source
reboot into fastboot mode with:
adb reboot bootloader
unless you don't have ADB, which you probably don't because you dun goofed when you flashed an Int'l ROM. In which case just press and hold power + vol down and pray.
once you're in fastboot mode, check to see if your device is recognized (may have to do this as root user in linux):
fastboot devices
This should list your device. If nothing comes up, check back here.
Now we're gonna lock your bootloader because RUU fails on unlocked bootloaders (security reasons). Skip this if you're S-Off (you shouldn't be, that's for advanced users).
fastboot oem lock
Now you're gonna go into RUU mode, which lets you modify all partitions of the phone (because you won't be in one):
fastboot oem rebootRUU
Now, we're going to flash the stock image to all the partitions of your device. This is the step that will undo your mistake!
fastboot flash zip firmware_version.zip
NOTE: Change the name of firmware_version.zip to whatever you download from above. If you get an error saying "flush again immdeiately," flash again immediately; just put in the exact same command.
Done. Just finalize with this:
fastboot reboot-bootloader
And then unplug and redo your entire root/ROM process from there.
Hopefully this mini guide will give you an idea of whether you'll need further help. @BD619 is a great fellow to ask.
thank you. you are a life saver. my phone is alive
iv unlocked the bootloader. what do i have to do now install custom rom?
Hello i was using this guide :
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
to root my phone i went and finished fastboot oem unlock step
the problem is after it and booted the phone i extracted the root files and clicked on it
then realized it said oem is not enabled in developer option
so now when i boot the phone a message says"Your Device is Corrupt. It can't be trusted and may not work properly."
and after it like 1-2 sec it turns off
i can still boot in bootloader
PLEASE SOME ONE HELP ME
Also it says device is unlocked in the bootloader statues code 3
extra information i was using android marshmallow 6 latest firmware
oudric said:
Hello i was using this guide :
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
to root my phone i went and finished fastboot oem unlock step
the problem is after it and booted the phone i extracted the root files and clicked on it
then realized it said oem is not enabled in developer option
so now when i boot the phone a message says"Your Device is Corrupt. It can't be trusted and may not work properly."
and after it like 1-2 sec it turns off
i can still boot in bootloader
PLEASE SOME ONE HELP ME
Also it says device is unlocked in the bootloader statues code 3
extra information i was using android marshmallow 6 latest firmware
Click to expand...
Click to collapse
The same thing happened to me when I tried to use a rootkit method for rooting the phone when it apparently knew nothing about the most recent updates (MRA58N or MRA58R). I ended up having to manual flash each individual image file from the MRA58N factory image (the flash-all script in the factory image zip wouldn't work). Even so, when I rebooted it still displayed the Your Device is Corrupt message. Then I went through the manual root process again (flashed the modified boot.img through fastboot, then flashed the latest TWRP recovery via fastboot, and then used TWRP to flash the latest SuperSU. Only then did the Your Device is Corrupt message go away and I also had root with everything else working fine.
It definitely made for an un-Godly horrible first 24-hours with my new phone! I hope this helps you.
internetpilot said:
The same thing happened to me when I tried to use a rootkit method for rooting the phone when it apparently knew nothing about the most recent updates (MRA58N or MRA58R). I ended up having to manual flash each individual image file from the MRA58N factory image (the flash-all script in the factory image zip wouldn't work). Even so, when I rebooted it still displayed the Your Device is Corrupt message. Then I went through the manual root process again (flashed the modified boot.img through fastboot, then flashed the latest TWRP recovery via fastboot, and then used TWRP to flash the latest SuperSU. Only then did the Your Device is Corrupt message go away and I also had root with everything else working fine.
It definitely made for an un-Godly horrible first 24-hours with my new phone! I hope this helps you.
Click to expand...
Click to collapse
can you please tell me steps i am so afraid to do anything to my phone now and i think my problem is same as yours
i downloaded 6.0.0 (MRA58R) and i used option in toolkit flash stock it gave me an error
"failed (data transfer failure (unknown error))
Its not so easy to brick nexus, but make sure you don't lock bootloader before your phone is working right. You can find the guide how to flash it on XDA.
You will need to flash the missing files by hand.
I was able to fix the erro i got by flashing by :
setting up environmental variable
copy all the flash files, all.bat bootloaderXXX.img... etc to platform tools folder
made sure i connected into usb 2.0 port not usb 3.0
then i flashed the stock firmware XD now my phone to point zero again
oudric said:
I was able to fix the erro i got by flashing by :
setting up environmental variable
copy all the flash files, all.bat bootloaderXXX.img... etc to platform tools folder
made sure i connected into usb 2.0 port not usb 3.0
then i flashed the stock firmware XD now my phone to point zero again
Click to expand...
Click to collapse
You don't need to move the files to the platform-tools folder.
Go to Nexus 6 General > Sticky rol-up thread > Adb and fastboot. What is it?
This will tell you how to set up and use adb or fastboot properly.