Database Develop

[Q] cannot root: hboot 2.0 ver. 2.3.5

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!

[Q] i think i messed up

I rooted my phone without knowing about s-off and its s-on and i installed miui and i cant boot that room it gets to the miui logo and just sits there is there anyway at all to fix this
Edit:
ok now it wont turn i connect my usb to the phone and the orange light appears i get the sounds on windows saying its connected then it disconnects and then dose this over and over again so i have no idea what is going on please please help its really annoying me

If you are still s-on you need to manualy flash the boot.img or it will just boot loop. I use Flash Image GUI but there are other ways
Sent from my Vivid 4G using xda premium

Spectrejester said:
If you are still s-on you need to manualy flash the boot.img or it will just boot loop. I use Flash Image GUI but there are other ways
Sent from my Vivid 4G using xda premium
Click to expand...
Click to collapse
could u give me more info please

new problem
re edited to top post

Your battery is dead and cwm doesn't support off-mode charging, hence the reason you get the orange light but only for a moment. You can't charge the phone while its off..and you incorrectly flashed a custom rom. If you can find a way to charge your batt out of the phone you can fix this by either flashing the proper boot.IMG for the ROM from fastboot, or by running the appropriate ruu and starting from scratch. I highly recommend doing the s-off procedure. Its not difficult, and it makes customizing the phone so much simpler.
Sent from my PAC MAN Raider using XDA Premium

i have the same problem man did it just minutes before...i have only a black screen, the display gives a vibration feedback. i see the sdcards in windows but cant open them
What can i do help please!
Edit: Ok screen is on "htc" and keeps so for minutes and hours
Any solution?

N-rG said:
i have the same problem man did it just minutes before...i have only a black screen, the display gives a vibration feedback. i see the sdcards in windows but cant open them
What can i do help please!
Edit: Ok screen is on "htc" and keeps so for minutes and hours
Any solution?
Click to expand...
Click to collapse
Boot to bootloader (pwr and vol-). Does it say locked or unlocked? Does it say s-on or s-off? Select recovery. Does it still boot to custom recovery or do you get the android with the exclamation point? If the bootloader says locked, and you get the android with the !, you need to unlock the bootloader, fastboot flash a custom recovery, boot to that custom recovery, and flash your ROM. If bootloader is s-on, you'll also need to fastboot flash a boot.img that's compatible with the ROM you're flashing (can be found in the ROM's .zip)

homeslice976 said:
Boot to bootloader (pwr and vol-). Does it say locked or unlocked? Does it say s-on or s-off? Select recovery. Does it still boot to custom recovery or do you get the android with the exclamation point? If the bootloader says locked, and you get the android with the !, you need to unlock the bootloader, fastboot flash a custom recovery, boot to that custom recovery, and flash your ROM. If bootloader is s-on, you'll also need to fastboot flash a boot.img that's compatible with the ROM you're flashing (can be found in the ROM's .zip)
Click to expand...
Click to collapse
Thank you so much for your answer
It says "unlocked"
It says "s-on"
It boots to nothing. When i start the phone there is only standing "htc" nothing more happend. No explantion Mark But i can get into the bootloader.
Or what do you mean with "it still boot to custom recovery or do you get the android with the exclamation point?"
How do I do that with the boot.img? Please i am such a noob im so sorry i dont unterstand a lot im so angry about myself that i did it, please can you exactly tell me what i should do and what i need?
I did a backup before but there is no "boot.img"
And how can i use the boot.img wenn i cant get access to the sd memory?

N-rG said:
Thank you so much for your answer
It says "unlocked"
It says "s-on"
It boots to nothing. When i start the phone there is only standing "htc" nothing more happend. No explantion Mark But i can get into the bootloader.
Or what do you mean with "it still boot to custom recovery or do you get the android with the exclamation point?"
How do I do that with the boot.img? Please i am such a noob im so sorry i dont unterstand a lot im so angry about myself that i did it, please can you exactly tell me what i should do and what i need?
I did a backup before but there is no "boot.img"
And how can i use the boot.img wenn i cant get access to the sd memory?
Click to expand...
Click to collapse
When you boot to bootloader, scroll down and select recovery. What happens?
As far as flashing the boot.img, when you downloaded the ROM's .zip, inside the .zip should have been a file called boot.img. You need to drag that to the directory where you have fastboot installed, boot to bootloader, connect your phone, select fastboot. It should now say "fastboot usb". Now in the directory where you have fastboot and boot.img (with neither selected), shift+right click, choose "Open command window here". You need to enter "fastboot flash boot boot.img" and hit enter. Then reboot

At first, thaaank you so much for your help, i feel so lost....
Ah ok i understand, you mean the "[ROM][ICEss v 0.4][Stockish ICS/SENSE 3.6" -that is what i downloaded.
When i am in the bootloader menu and activate recovery the htc symbol appears with a white backround...nothing more happen for minutes
unfortuneately there is not boot.img in this zip
I did the whole procedure with the Vivid_All-In-One_Kit_v2.2 and not fastboot.
Ok i now downloaded fastboot and put it to c:/fastboot
I do what you say and reach your point " It should now say "fastboot usb" thats right, it works. But i dont have the boot.img where can i get it?

N-rG said:
At first, thaaank you so much for your help, i feel so lost....
Ah ok i understand, you mean the "[ROM][ICEss v 0.4][Stockish ICS/SENSE 3.6" -that is what i downloaded.
When i am in the bootloader menu and activate recovery the htc symbol appears with a white backround...nothing more happen for minutes
unfortuneately there is not boot.img in this zip
I did the whole procedure with the Vivid_All-In-One_Kit_v2.2 and not fastboot.
Ok i now downloaded fastboot and put it to c:/fastboot
I do what you say and reach your point " It should now say "fastboot usb" thats right, it works. But i dont have the boot.img where can i get it?
Click to expand...
Click to collapse
There's not a boot.img in the zip you downloaded? Then you need to read the thread and see what kernel they recommend, get the boot.img, and fastboot flash it. You're getting close.
It sounds like you may have lost your custom recovery along the way too (in which case more may have broke) - you'll need to get a custom recovery .img (wcx or twrp) and fastboot flash it (fastboot flash recovery <nameofrecovery>.img). Then fastboot flash boot.img, then boot to recovery and reflash the ROM and hopefully you'll be all set.

Thanks again, im getting closer! I read the whole thread and found that "Holics_Kernel_0730_S-ON" is recommended. I downloaded and found the boot.img I put it in the fastboot folder.
But i dont understand what do you mean with "you'll need to get a custom recovery .img (wcx or twrp)"
Do you mean the recovery i created with my old working Gingerbread or a recovery form the custom rum i downloaded?
When last, where can i get such a recovery.img?
Hey man btw. you gave me so much hope at the moment, thats incredible, thank you!

Check the dev section. Everything you will need is in the stickied threads. Twrp recovery also has its own thread

bypruv oculus
Okay i'll do meanwhile there is something new. I create use fastboot, the boot.img of the new kernel and do it with the command line like you said.
The phone now boots one step more to "htc quietly brilliant" and then restarts over and over again to this screen, like a loop.
---------- Post added at 11:42 PM ---------- Previous post was at 11:25 PM ----------
ahhh i reach Android System Recovry with several menus. I didnt find any help in google what i have to do now.
Backup google propritary System, nand backup, Nand Restore, Restore google proprietary System? Or something else?

No.. at this point you should wipe cache, dalvik cache, system, an data. This can all be done In Recovery's wipe menu. Them recovery should have a flash zip menu. Flash the ROM .zip

Put the brakes on!
I saw gingerbread...
When you boot to bootloader...
There is a line labeled hboot
What's the number next to it?
If its 1.85... you good...
If its 1.83... thou shalt find an ICS ruu for your carrier.
Almost none of the ROMs you find here run on 1.83
Sent from my Vivid 4G using Tapatalk 2

Good catch!

Hey,
i bring it to run! I restored every part manuall...system, cache, data. Only restore boot didnt work. I suggest its because Rom Manager/ClockworkMod didn't created such a file (boot.img) So i downloaded a custom kernel für Gingerbread.
Vola, handy startet, Os is on. Loggin into network worked!
BUT! I cannot use Wlan/wifi or mobile networking. I suppose its because the rom right?
I mentioned that i have the same phone here from my girlfriend.
How and can i make a boot.img of her phone? Please tell my how and then i have finished everything i hope

You can't. S*on devices can't flash boot.IMG or back up boot.IMG in recovery. You have to fast boot flash the boot.IMG. this is also why wifis broken
The kernel and ramdisk and some other things are packed into boot.IMG, and are made by ROM or kernel devs. Actually now that you're booting, you can use an app called flash image GUI to flash the boot.img

Ok I expressed something wrong, sorry (im not a native speaker u might noticed long before ^^ ). So i try again like I said i did the manuell recovery of everything except the boot.img.
Thats why i loaded this kernel for Gingerbread (http://forum.xda-developers.com/showthread.php?t=1351717) and installed the boot.img with fastboot "flash boot boot.img"
Fastboot said well done. Phone startet.
I think i understand what you are writing, but i dont understand which boot.img do you mean i need. I have no boot.img from my backup before flashing with custom rom without this boot.img i cant flash the not working one of the ICS on my phone am i right?
So thats why i thought i can take the phone of my girlfriend, create a boot.img and use it for my phone. So thats the only problem, i need working boot.img and then flash with fastboot oder the app you mentioned How to get the boot.img

[Q] How can I reinstall a good image after flashing my boot with CWM?

My question is similar to 'nikpmr's troubles but different enough I think they deserve a separate post.
The Problem as Understood​I was trying to root my device following the guide at this website. It's so simple it's a wonder I messed up. I think my failure was that I thought the drivers installed when I connected the phone were enough so I skipped that step. Then when running fastboot flash recovery.img the install failed. So I saw on some forum that it was supposed to be fastboot flash boot recovery.img of course now I know if anything it ought to have been "recovery" not "boot".
What I've Tried & Partial Solution​At first I was just stuck in a boot loop and selecting "sideload" from the CWM recovery failed to allow me to connect with ADB or fastboot. i.e. Running "fastboot devices" and "adb devices" both returned as having no devices connected to my computer. So I installed the HTC Sync and promptly uninstalled the non driver parts of the app. Then I installed USBdeview and used it to uninstall all the USB devices associated with my HTC First. After doing that I learned booting into HBOOT allowed me to connect to the computer using fastboot and after then booting to the CWM Recovery I was able to connect using ADB to do a sideload. So I guess I'm about halfway there. Unfortunately after looking up the newest RUU and attempting to sideload it using "adb sideload OTA_MYST_UL_1.08.502.1-1.08.502.4.zip" the sideload failed. After selecting "- install zip from sideload" I get a message twice of "failed to open driver control: No such file or directory". It also failed when I attempted it with a similar fastboot command. So from all that I surmise my ROM is ruined and just needs to be replaced.
Question​So how do I go about replacing this ROM and boot partition? And, which ROM should I use? Is the one I got from the RUU site suitable? And what about the radio? I just need my phone to work. I can worry about rooting later. At this point I think I know what's happened but I don't know where to begin reading to figure out how to fix it myself.
Thanks for reading,
Relevant HBOOT text:
Code:
*** TAMPERED ***
*** UNLOCKED ***
MYSTUL PVT SHIP S-ON RL
HBOOT-2.00.0000
RADIO-1.15.40.00.13_2
OpenDSP-v9.2.0268.1214
eMMC-boot
Mar 22 2013,21:29:50:1682

1. you had to type in fastboot flash recovery recovery.img NOT fastboot flash boot recovery.img

Well there was an actual all in 1 tool to get cwm/twrp & root with a click for this specific device somewhere around these threads.
1) what exactly is the problem? (Sorry it was just so many words)
I don't think side loading the RUU would work bc I haven't heard its possible to flash it in the phone itself.
2) why don't you just sideload an existing pre-rooted ROM instead of the RUU file?
3) I see you're s-on, did you try flashing just the boot.IMG from the ROM you've got on it?
BTW I've only had luck with twrp on having it successfully detected when wanting to sideload

abrahammmmmmm_ said:
Well there was an actual all in 1 tool to get cwm/twrp & root with a click for this specific device somewhere around these threads.
1) what exactly is the problem? (Sorry it was just so many words)
I don't think side loading the RUU would work bc I haven't heard its possible to flash it in the phone itself.
2) why don't you just sideload an existing pre-rooted ROM instead of the RUU file?
3) I see you're s-on, did you try flashing just the boot.IMG from the ROM you've got on it?
BTW I've only had luck with twrp on having it successfully detected when wanting to sideload
Click to expand...
Click to collapse
1) The issue is I did "fastboot flash boot recovery.img" rather than "fastboot flash recovery.img" now I don't seem to have a boot mount point.
2) That sounds best. I didn't realize the RUU want a flashable ROM. More I just have to find the updated stable stock ROM.
3) I didn't have a ROM on it. I was just trying to root stock. Seems like I'm pretty close once I find that ROM.
Thanks y'all! Between your answers I think I have enough to go on. Feel free to point me to your preferred stable ROM. I'm content with stock but it would be nice to have Tiranium BU.

bnjo said:
1) The issue is I did "fastboot flash boot recovery.img" rather than "fastboot flash recovery.img" now I don't seem to have a boot mount point.
2) That sounds best. I didn't realize the RUU want a flashable ROM. More I just have to find the updated stable stock ROM.
3) I didn't have a ROM on it. I was just trying to root stock. Seems like I'm pretty close once I find that ROM.
Thanks y'all! Between your answers I think I have enough to go on. Feel free to point me to your preferred stable ROM. I'm content with stock but it would be nice to have Tiranium BU.
Click to expand...
Click to collapse
Right now our most stable stock ROM is our rooted stock ROM
http://forum.xda-developers.com/showthread.php?t=2287811
We currently have 2 very able recognized devs working on CyanogenMod. You can expect something new in the near future but until then what I've showed you is the best.
Have any problems just come back to the thread

Success!
abrahammmmmmm_ said:
Right now our most stable stock ROM is our rooted stock ROM
http://forum.xda-developers.com/showthread.php?t=2287811
We currently have 2 very able recognized devs working on CyanogenMod. You can expect something new in the near future but until then what I've showed you is the best.
Have any problems just come back to the thread
Click to expand...
Click to collapse
Thanks guys I know I always like to know when something I said was successful in helping someone. I just wanted yall to know after sideloading the most recent Odexed ROM then pushing it to memory after it wouldn't boot I succeeded after taking abrahammmmmm's advice of flashing the boot.img from HBOOT. After a longer boot than I'm used to I was able to get into my phone again. I wasn't able to use my TitaniumBU to restore but that just meant I had to spend a few minutes selecting apps to install.. And restoring a data backup for the only important app that doesn't keep the primary data off the phone.
Thanks again!
tl;dr Flashing the Odexed ROM boot.img fixed my issues. Thx!

bnjo said:
Thanks guys I know I always like to know when something I said was successful in helping someone. I just wanted yall to know after sideloading the most recent Odexed ROM then pushing it to memory after it wouldn't boot I succeeded after taking abrahammmmmm's advice of flashing the boot.img from HBOOT. After a longer boot than I'm used to I was able to get into my phone again. I wasn't able to use my TitaniumBU to restore but that just meant I had to spend a few minutes selecting apps to install.. And restoring a data backup for the only important app that doesn't keep the primary data off the phone.
Thanks again!
tl;dr Flashing the Odexed ROM boot.img fixed my issues. Thx!
Click to expand...
Click to collapse
Great! glad to hear I could help. Yes it's always nice knowing when something I've said has helped someone in any way

bnjo said:
Thanks guys I know I always like to know when something I said was successful in helping someone. I just wanted yall to know after sideloading the most recent Odexed ROM then pushing it to memory after it wouldn't boot I succeeded after taking abrahammmmmm's advice of flashing the boot.img from HBOOT. After a longer boot than I'm used to I was able to get into my phone again. I wasn't able to use my TitaniumBU to restore but that just meant I had to spend a few minutes selecting apps to install.. And restoring a data backup for the only important app that doesn't keep the primary data off the phone.
Thanks again!
tl;dr Flashing the Odexed ROM boot.img fixed my issues. Thx!
Click to expand...
Click to collapse
i think what happened, when you typed in "fastboot flash boot recovery.img" is this
boot, is also known as kernel in aosp and rom building terms, because if you look inside a rom.zip, you will see that the kernel is the boot.img
so what happened is you flashed a recovery as kernel, and duh it wont boot cause if the kernel doesnt work, the os doesnt either
so what YOU did is you simply reflashed the stock kernel, usually after changing a kernel, it takes a while to boot cause...well you get it right?
the kernel is what android is based off of, kind of like ubuntu, its a linux os based on the original linux kernel.

russian392 said:
usually after changing a kernel, it takes a while to boot cause...well you get it right?
Click to expand...
Click to collapse
Yes I get it.
russian392 said:
i think what happened, when you typed in "fastboot flash boot recovery.img" is this
boot, is also known as kernel in aosp and rom building terms, because if you look inside a rom.zip, you will see that the kernel is the boot.img
so what happened is you flashed a recovery as kernel, and duh it wont boot cause if the kernel doesnt work, the os doesnt either
so what YOU did is you simply reflashed the stock kernel, usually after changing a kernel, it takes a while to boot cause...well you get it right?
the kernel is what android is based off of, kind of like ubuntu, its a linux os based on the original linux kernel.
Click to expand...
Click to collapse
That's what I thought happened. If I had stopped to read the help on fastboot before running "fastboot flash boot recovery.img" I wouldn't have made that mistake because I would have seen I wanted to flash recovery. One thing I *did not* know, which I'm glad to know, was that the boot.img contains the kernal. I was thinking Android was more similar to IBM style PCs than it is and therefore the boot.img was analogous to a bootloader like grub or lilo.
So the one thing I don't get is how is partitioning done? I take it Androids have some reserved partition for boot and the boot.img takes care of all system partitioning and mounts /sdcard/ for everything else. i.e. userland; appdata, media, and files. Am I guessing correctly?

bnjo said:
So the one thing I don't get is how is partitioning done? I take it Androids have some reserved partition for boot and the boot.img takes care of all system partitioning and mounts /sdcard/ for everything else. i.e. userland; appdata, media, and files. Am I guessing correctly?
Click to expand...
Click to collapse
in a nutshell yes, the boot.img uses the fstab
btw 10 posts you'll be "verified"

So the one thing I don't get is how is partitioning done? I take it Androids have some reserved partition for boot and the boot.img takes care of all system partitioning and mounts /sdcard/ for everything else. i.e. userland; appdata, media, and files. Am I guessing correctly?
Click to expand...
Click to collapse
Yep that's correct.
The name correlation is booting up requires kernel there for kernel is called beet.IMG
Thing about custom kernels, they aren't like that and simply contain modded files and pretty much an in packaged kernel.
Sent from my HTC first using xda app-developers app

stock recovery
please can anyone send me the stock recovery.img
when i try to get it from RUU it says archive is corrupted

astrit1995 said:
please can anyone send me the stock recovery.img
when i try to get it from RUU it says archive is corrupted
Click to expand...
Click to collapse
here:
http://androidfiles.org/getdownload.php?file=MystUL/Stock_Roms/stockrecovery.img
if you help, press thanks!!

Serupo said:
here:
http://androidfiles.org/getdownload.php?file=MystUL/Stock_Roms/stockrecovery.img
if you help, press thanks!!
Click to expand...
Click to collapse
Thank you for your help,i solved my problem yesterday but i think im gona need this sometime...

HTC ONE M7 stuck on unlocking screen

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?

M7 Totally Messed up

I really messed my phone up its got no OS and its stuck in bootloop iv tried pushing cm-12 onto it and installing it but i keep getting error codes with what you see in the picture. can anyone help.

Burky1996 said:
I really messed my phone up its got no OS and its stuck in bootloop iv tried pushing cm-12 onto it and installing it but i keep getting error codes with what you see in the picture. can anyone help.
Click to expand...
Click to collapse
Try re download the zip (or try an other rom)maybe you just got an false download. i also had some trouble with my m7 back in the day.
But in your case now you are stuck with no os or bootloop, i give you as advice to follow an soft unbrick method it worked for me, or if you have an usb otg cable and usb or and usb otg thumbstick, put the rom on that usb and connect it to your phone and then try to flash it (if your using twrp you have an option to choose from wich storage you want to use)
Also a piece of advice, when flashing roms, kernels etc please have your phone charged above 50% (just in case).
Sent from my HUAWEI P7-L10 using XDA Free mobile app
---------- Post added at 09:28 PM ---------- Previous post was at 09:27 PM ----------
its the peanut said:
Try re download the zip (or try an other rom)maybe you just got an false download. i also had some trouble with my m7 back in the day.
But in your case now you are stuck with no os or bootloop, i give you as advice to follow an soft unbrick method it worked for me, or if you have an usb otg cable and usb or and usb otg thumbstick, put the rom on that usb and connect it to your phone and then try to flash it (if your using twrp you have an option to choose from wich storage you want to use)
Also a piece of advice, when flashing roms, kernels etc please have your phone charged above 50% (just in case).
Sent from my HUAWEI P7-L10 using XDA Free mobile app
Click to expand...
Click to collapse
Also make sure you downloaded the rom made for your phone model!
Sent from my HUAWEI P7-L10 using XDA Free mobile app

Burky1996 said:
I really messed my phone up its got no OS and its stuck in bootloop iv tried pushing cm-12 onto it and installing it but i keep getting error codes with what you see in the picture. can anyone help.
Click to expand...
Click to collapse
Can you please post the output of
Code:
fastboot getvar all
please remove your imei and serial number.
Depending on which variant of the M7 you have you probably just need a different version of recovery to install a CM rom. I think they prefer TWRP 2.7.x.x. Post the getvar and we can see what you have. then I can give you a better informed instruction. :good:
P.s also check the md5 of the rom zip you downloaded. Use this tool www.winmd5.com the correct md5 should be listed with the link you downloaded the rom from

failed to mount /dev/block/blah blah blah = needs "block:by-name" support which twrp 2.6.3.3 doesn't have
everything explained here
So update your recovery
and do what danny said above so he can confirm you have the right rom/recovery for your device.

Burky1996 said:
I really messed my phone up its got no OS and its stuck in bootloop iv tried pushing cm-12 onto it and installing it but i keep getting error codes with what you see in the picture. can anyone help.
Click to expand...
Click to collapse
Your getvar looks fine this rom should work fine with your device. Download this version of TWRP https://www.androidfilehost.com/?fid=23501681358561860 (2.7.1.2). dropthe file in your fastboot folder and flash it with fastboot.
Code:
fastboot flash recovery "name-of-recovery".img
fastboot erase cache
fastboot reboot-bootloader
Once thats done reflash the rom with the new version of TWRP. It should flash just fine :good:

iv managed to flash cm12.1 now, thanks guys, is there anyway i could get the HTC software back on.

Burky1996 said:
iv managed to flash cm12.1 now, thanks guys, is there anyway i could get the HTC software back on.
Click to expand...
Click to collapse
There are a number of ways to return to stock software. You can simply flash a stock rom through twrp or use a stock nandroid. look for rom that match your version main. 7.19.401.22
I think there is even an lollipop 7.19.401.22 RUU for your device but I'm not sure if it will work with s-on though because it's a zip but it certainly wouldnt hurt to try it though. You will need to relock your bootloader and flash it with fastboot.
I'll edit this post with links when I find them unless some one beats me to it

Hey Dan do you think we could skype and you could talk me through it, it would be much easier?

Burky1996 said:
Hey Dan do you think we could skype and you could talk me through it, it would be much easier?
Click to expand...
Click to collapse
Sorry I am at work so availability is scetchy. I found the ruu but it's for the older 7.19.401.2 lollipop, this won't work for you because your s-on. Downgrading firmware is only possible with s-off.
You can use this stock rom though http://forum.xda-developers.com/htc-one/development/rom-100-pure-stock-5-0-2-7-19-401-2-t3044041 just flash it with twrp. The thread recommends TWRP 2.8.5.X no need to relock the bootloader or anything silly, just flash it like any other rom :good:
You'll notice that this rom is also for the older 7.19.401.2 so you will need to install the last OTA update to bring your rom in line with your firmware. Flash this recovery with the same method as twrp. (Stock recovery required for installing the OTA) http://sourceforge.net/projects/htcone/files/Recovery/STOCK/7.19.401.2_recovery.img/download reboot then just go to Settings>About>Check for updates.

Danny201281 said:
Sorry I am at work so availability is scetchy. I found the ruu but it's for the older 7.19.401.2 lollipop, this won't work for you because your s-on. Downgrading firmware is only possible with s-off.
You can use this stock rom though http://forum.xda-developers.com/htc-one/development/rom-100-pure-stock-5-0-2-7-19-401-2-t3044041 just flash it with twrp. The thread recommends TWRP 2.8.5.X no need to relock the bootloader or anything silly, just flash it like any other rom :good:
You'll notice that this rom is also for the older 7.19.401.2 so you will need to install the last OTA update to bring your rom in line with your firmware. Flash this recovery with the same method as twrp. (Stock recovery required for installing the OTA) http://sourceforge.net/projects/htcone/files/Recovery/STOCK/7.19.401.2_recovery.img/download reboot then just go to Settings>About>Check for updates.
Click to expand...
Click to collapse
i did what you said when i applied the system update my phone turned on booted to a white screen with the green htc logo then it turned off the battery symbol came up its like its turned off. i tryed to lock the boot loader to see if it would work then but it never, when i appy the update it dosent even boot into the recovery.

i did what you said when i applied the system update my phone turned on booted to a white screen with the green htc logo then it turned off the battery symbol came up its like its turned off. i tryed to lock the boot loader to see if it would work then but it never, when i appy the update it dosent even boot into the recovery.

Burky1996 said:
i did what you said when i applied the system update my phone turned on booted to a white screen with the green htc logo then it turned off the battery symbol came up its like its turned off. i tryed to lock the boot loader to see if it would work then but it never, when i appy the update it dosent even boot into the recovery.
Click to expand...
Click to collapse
Okay try this. Download the OTA but select the option "Install Later" connect your m7 to your pc and browse your storage. In the download folder on your phone you should find the OTA in zip format. Copy it to your pc.
Now open the OTA zip on your pc. Inside you'll find another zip called "firmware.zip" extract it then open it. Inside you'll find a recovery.img. extract the recovery file and flash it with fastboot. Now reboot to android and continue to install the OTA. :fingers-crossed:
Sent from my SM-T230 using Tapatalk

im going to have to unlock the boot loader again and then do it

Burky1996 said:
im going to have to unlock the boot loader again and then do it
Click to expand...
Click to collapse
Yes you will need to unlock the bootloader to flash the recovery, Dont forget to fastboot erase cache after flashing the recovery that is cruicial. You don't need to be relocked to install the OTA though.
When you select install now, the device should reboot to the Stock Recovery. At first the screen will just be black for a short while. Then you'll see an image of a phone with a Green ring and download arrow. If you hold Volume up and press the power button you will see the Stock Recovery and its progress in installing the OTA.
I'm not sure why your device was hanging on boot after installing the OTA. Maybe a bad recovery.img. that's why I say to get the recovery from the OTA file.

its still not working so i mite just install twrp and restore to cm12.1

Burky1996 said:
im going to have to unlock the boot loader again and then do it
Click to expand...
Click to collapse
Yes you will need to unlock the bootloader to flash the recovery, Dont forget to fastboot erase cache after flashing the recovery that is cruicial. You don't need to be relocked to install the OTA though.
When you select install now, the device should reboot to the Stock Recovery. At first the screen will just be black for a short while. Then you'll see an image of a phone with a Green ring and download arrow. If you hold Volume up and press the power button you will see the Stock Recovery and its progress in installing the OTA.
I'm not sure why your device was hanging on boot after installing the OTA. Maybe a bad recovery.img. that's why I say to get the recovery from the OTA file.

Danny201281 said:
Sorry I am at work so availability is scetchy. I found the ruu but it's for the older 7.19.401.2 lollipop, this won't work for you because your s-on. Downgrading firmware is only possible with s-off.
You can use this stock rom though http://forum.xda-developers.com/htc-one/development/rom-100-pure-stock-5-0-2-7-19-401-2-t3044041 just flash it with twrp. The thread recommends TWRP 2.8.5.X no need to relock the bootloader or anything silly, just flash it like any other rom :good:
You'll notice that this rom is also for the older 7.19.401.2 so you will need to install the last OTA update to bring your rom in line with your firmware. Flash this recovery with the same method as twrp. (Stock recovery required for installing the OTA) http://sourceforge.net/projects/htcone/files/Recovery/STOCK/7.19.401.2_recovery.img/download reboot then just go to Settings>About>Check for updates.
Click to expand...
Click to collapse
could it be not working coz my hboot has changed to 1.51.

Burky1996 said:
could it be not working coz my hboot has changed to 1.51.
Click to expand...
Click to collapse
Your still stuck with this? Try starting the process over, but do not relock your bootloader at any point.
Wipe system data and cache partitions with TWRP Advanced wipe
Flash the Rom with twrp as a clean install.
Reboot and download the OTA. Choose install later, then copy the OTA to your pc. Extract the Stock Recovery and flash it with fastboot. Reboot and install the OTA.
But do not relock your boot loader. Because when you unlock the bootloader, it wipes the device including the data/preload folder. If the preload folder is not intact the OTA will fail
Sent from my M7 Running ARHD 92.x