Hello,
I've been following this guide: http://forum.xda-developers.com/showthread.php?t=1466436
When I came to the part where I had to fastboot the Chinese ROM my phone stopped working. I followed it straight out, and when I chose "Recovery" as the guide told me to choose, my phone only boots with a black lit screen and then turns black completely (no backlight), but the touch buttons still work and the phone vibrates.
The part it failed at was this:
1. You cant just flash a custom rom on this phone, firstly you will need the 'Chinese rom' which is here http://hotfile.com/dl/148413075/8990...01713.zip.html and make sure it is on the SDcard part of your phones memory. Make sure it on the root of the SDcard because it will be easier to find later. Then you will need this rom RCMix3d Runny XL rom from here http://dl.dropbox.com/u/56143145/RCM...ny_XL_v1.2.zip (thanks to benjamin.j.goodwin) and make sure that is on the SDcard too with the other rom
2. Then you will need to download this file from here http://forum.xda-developers.com/show...7&postcount=18 it is the 'Chinese boot.img' and will need flashing from fastboot again. So put the phone in fastboot and extract the 'boot.img' from the 'boot.rar' file and put it in the fastboot folder on the PC. Open the command prompt again and type this... fastboot flash boot boot.img ... This should only need doing once if you're coming from a stock rom.
3. Once you've done that you will need to get into recovery. From fastboot select bootloader and then look for recovery, it should be under fastboot if its worked correctly. Select that and the phone should then reboot and go into 'CWM' (recovery). Once there you will need to use the volume keys and power button just like when you were in bootloader. Go down and select 'Factory Reset/Data Wipe' and select that, the select yes on following screen. This will take a few mins (don't worry if it looks like its not doing anything). After that go down to 'Wipe Cache' and select that. and then go down to 'Advanced' select that and on the following screen select 'Wipe Dalvik Cache'.
Click to expand...
Click to collapse
The bolded text is what I have done, whatever comes after I never got a chance to do. Nothing I have tried so far have worked.
I'm very new to doing this kind of stuff and I thought I'd try the three musketeers ROM out, so far I haven't gotten this far. I need help in getting my phone to work again so I can continue the guide.
I'm sorry if this is in the wrong section of the forums. Like I said, I'm new, and please move this to the correct area (If any mods around). Sorry for any troubles, and appreciate any help.
Thanks! <3
I've tried to get back to stock version, but it's not working.
My phone only boots to FASTBOOT and BOOTLOADER right now. It says on the top:
***RELOCKED***
RUNNYMEDE PVT SHIP S-ON
RADIO-3831.16.00.16_M
eMMC-BOOT
When trying to do anything within the CMD it says:
C:\Android>fastboot flash boot boot.img
sending 'boot' (3424 KB)...
OKAY [ 2.594s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 3.031s
:/
Phrebbie said:
I've tried to get back to stock version, but it's not working.
My phone only boots to FASTBOOT and BOOTLOADER right now. It says on the top:
***RELOCKED***
RUNNYMEDE PVT SHIP S-ON
RADIO-3831.16.00.16_M
eMMC-BOOT
When trying to do anything within the CMD it says:
C:\Android>fastboot flash boot boot.img
sending 'boot' (3424 KB)...
OKAY [ 2.594s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 3.031s
:/
Click to expand...
Click to collapse
Unlock bootloader and flash recovery. Måske device s-off then run the ruu.exe . do not relock bootloader.
Sent from my Sensation XL using XDA Premium HD app
anders3408 said:
Unlock bootloader and flash recovery. Måske device s-off then run the ruu.exe . do not relock bootloader.
Sent from my Sensation XL using XDA Premium HD app
Click to expand...
Click to collapse
I'm really sorry, but how should I do this? :/
It keeps telling me it failed and remote: signature failed.
I think I did it now.
I unlocked bootlader again.
I flashed the recovery "Clockwork" OK.
Now I have no idea what to do next? I tried putting in the Chinese ROM again and then hit "Recover", but I only come to black screen and nothing happens.
RUU.EXE doesn't work either, tried it, it says security/update fail or something and it just stops.
Phrebbie said:
I think I did it now.
I unlocked bootlader again.
I flashed the recovery "Clockwork" OK.
Now I have no idea what to do next? I tried putting in the Chinese ROM again and then hit "Recover", but I only come to black screen and nothing happens.
RUU.EXE doesn't work either, tried it, it says security/update fail or something and it just stops.
Click to expand...
Click to collapse
From boot loader go to recovery.
From recovery mount SD card for PC/USB
Copy the ROM over to sdcard.
Unmount for USB/PC
Wipe data/factory reset
Wipe cache and dalvik cache
Flash the ROM
Boot up the new ROM
S-off the device
Then install the ruu.exe.
Sent from my Sensation XL using XDA Premium HD app
Thank you for reply Anders,
The problem is I can't go into "recovery" on my phone. It just goes black and nothing happens.
I did both version of Clockwork recovery flash and it succeeded - no idea if it's related, but I just can't go into recovery.
Phrebbie said:
Thank you for reply Anders,
The problem is I can't go into "recovery" on my phone. It just goes black and nothing happens.
I did both version of Clockwork recovery flash and it succeeded - no idea if it's related, but I just can't go into recovery.
Click to expand...
Click to collapse
Try from fastboot and flash twrp.
Fastboot flash recovery recovery.img
Sent from my Sensation XL using XDA Premium HD app
Thank you,
TWRP worked much better.
I put rom on USB storage (i had to format it first to be able to open it, so it was completely empty and i just put file in there)
I did wipe/reset and cache/dalvik wipe.
I flashed the ROM succesfully.
I tried booting it up, the HTC logo comes up as well as the BEATS animation, then HTC logo with "Quietly Brilliant" beneath, and it stops there, nothing happens. Also, it starts making the startup HTC signal for less than a second, then it's quiet.
The ROM I put in storage and flashed with was "Total_Senseless_SXL-v4.1.1".
No idea if I did it right but I will try the Chinese ROM as well. As said, I'm new to this.
I get a problem when trying to flash the runnymede_ax918 .zip file.
It tells me this:
Installing '/sdcard/runnymede_ax918_11511_10171
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
E:Error in /sdcard/runnymede_ax918_11511_101713
(Status 1)
Error flashing zip '/sdcard/runnymede_ax918_1115
Updating partition details...
And a red text "Failed".
According to the guide I have to install the Chinese ROM first which is what I'm trying to do here.
I flashed the boot.img first, entered TWRP, factory reset/wipe cache/dalvik
Find the Chinese .zip file (runnymede_ax918) and press install and this problem occurs.
That guide is old, you do not need any other chinese ROM's and suc, just unlock bootloader, flash recovery, root, S-OFF and after that you can have whatever you want on your phone. The thing with cbinese ROM and.such was before S-OFF was available.for the device...
Sent from my Nexus S using xda app-developers app
Well that's fun. Thanks for pointing that out though.
I can't stress it enough, I'm new to this, what should I do next? How do I root and how do I S-OFF? Guides?
Sorry for troubles.
Phrebbie said:
I get a problem when trying to flash the runnymede_ax918 .zip file.
It tells me this:
Installing '/sdcard/runnymede_ax918_11511_10171
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
E:Error in /sdcard/runnymede_ax918_11511_101713
(Status 1)
Error flashing zip '/sdcard/runnymede_ax918_1115
Updating partition details...
And a red text "Failed".
According to the guide I have to install the Chinese ROM first which is what I'm trying to do here.
I flashed the boot.img first, entered TWRP, factory reset/wipe cache/dalvik
Find the Chinese .zip file (runnymede_ax918) and press install and this problem occurs.
Click to expand...
Click to collapse
Delete ROM from zip and put it over again. And ofc try and open the zip on the computer first. If you can't open it on computer download the ROM again.
BTW. That is just how I did it, since no one really knows what its so special in that ROM and no one knows for sure that it makes Amy difference at all when using it or not, you can do as lexmazter wrote and don't use it.
The reason for me to flash that ROM is that I had read in here that when that ROM has been flashed hard brick was almost impossible with some common sense
No matter what, if you delete or has wrong vold.fstab and formats the sdcard from PC you only luck will be jtag.
Sent from my Sensation XL using XDA Premium HD app
anders3408 said:
Delete ROM from zip and put it over again. And ofc try and open the zip on the computer first. If you can't open it on computer download the ROM again.
BTW. That is just how I did it, since no one really knows what its so special in that ROM and no one knows for sure that it makes Amy difference at all when using it or not, you can do as lexmazter wrote and don't use it.
The reason for me to flash that ROM is that I had read in here that when that ROM has been flashed hard brick was almost impossible with some common sense
No matter what, if you delete or has wrong vold.fstab and formats the sdcard from PC you only luck will be jtag.
Sent from my Sensation XL using XDA Premium HD app
Click to expand...
Click to collapse
From what i know, that Chinese ROM was supposed to have unsecured boot, don't know how that helps and i don't get the ideea behind it anyways, so the right way to do it is to Unlock Bootloader -> Flash Recovery -> Root -> S-OFF -> Free to try whatever custom ROM out there you want, hard bricking is pretty hard even without common sense, i personally tried to do it and i failed, i think you need to know how to brick it in order to brick it, but to avoid that, make sure you do things the right way, read things before you try and so on.
Lexmazter said:
From what i know, that Chinese ROM was supposed to have unsecured boot, don't know how that helps and i don't get the ideea behind it anyways, so the right way to do it is to Unlock Bootloader -> Flash Recovery -> Root -> S-OFF -> Free to try whatever custom ROM out there you want, hard bricking is pretty hard even without common sense, i personally tried to do it and i failed, i think you need to know how to brick it in order to brick it, but to avoid that, make sure you do things the right way, read things before you try and so on.
Click to expand...
Click to collapse
a simple way to do a hard brick:
flash a rom with only has the vold.fstab for hboot 1.25 and device is 1.28 , then mount sdcard for pc and format sdcard (pc says you need to do it before it can read the sdcard) - the result = BRICKED
Related
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!
...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.
Ok, I know I'm going to catch all kinds of hell probably for posting this. But, I'm stuck. This is the first question I have asked on this forum, and have literally spent days on end searching, and trying new things. What happened is I think I tried flashing a GSM rom (the new android revolution 30.0) onto my Sprint HTC One. I just got this phone two weeks ago, and unfortunately upgraded to the 4.3 with the 1.55 hboot. So, S-on. I was using slimbean as my dd, but wanted to give revolution a try. When I dl the rom, it stated for m7wls, so thought I was good. Well, went into a kind of bootloop where it would upgrade android like 41 out of 120, then it would restart. When it finally would boot up, I had about fifteen seconds before it would reboot again. I tried to wipe and restore, but same thing was happening. I read that the partitions may have been screwed up from the gsm to cdma so, I wiped data and everything. I was going to relock and flash an RUU. Then I find out that there isn't one yet for the 4.3. I tried the Guru reset, updating drivers, sideloading, flashing cwm from twrp, pushing and had a rom boot up once, but no service or gapps. In cmd fastboot, my phone is recognized. But, when I use adb, it can't find it.I can get into recovery, and I have the official android 4.3 stock rom on my laptop ready to flash, but just can't get it to the phone. I am a noob, so I am sorry for that, but we all were at one time or another. I researched, tried to learn as much as I could before I took the plunge. I've read thread upon thread here and in other forums trying to find a fix. Everything that I've tried from some of these posts just didn't work for me. I don't know what I'm doing wrong, and I am not sure what you guys would need from me as far as more info. But, I would be grateful if someone could steer me in the right direction. Thanks in advance, and again apologies if I'm not doing things right for you guys. Just trying to learn and do.
C:\Users\Guest\Desktop\Fastboot>fastboot devices
FA38DS904955 fastboot
C:\Users\Guest\Desktop\Fastboot>fastboot flash rom.zip Dev-3.22.1540.1-Stock-Roo
ted-DE-ODEX.zip
target reported max download size of 1526722560 bytes
sending 'rom.zip' (1061169 KB)...
OKAY [ 47.135s]
writing 'rom.zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 169.469s
This is what cmd tells me when I try to flash the rom.
Dev-3.22.1540.1-Stock-Rooted-DE-ODEX.zip
Click to expand...
Click to collapse
Is not a Sprint rom
bigdaddy619 said:
Is not a Sprint rom
Click to expand...
Click to collapse
Even when I tried to flash slimbean, same thing happens. Thank you for the reply though.
I downloaded super one rom to laptop, tried using adb sideloader, but it doesn't detect my device. I went into mounts and storage on cwm and tried mounting usb, but doesn't toggle. I really am in desperate need of directions. I would even pay if I could lol.
bbjay351 said:
Even when I tried to flash slimbean, same thing happens. Thank you for the reply though.
I downloaded super one rom to laptop, tried using adb sideloader, but it doesn't detect my device. I went into mounts and storage on cwm and tried mounting usb, but doesn't toggle. I really am in desperate need of directions. I would even pay if I could lol.
Click to expand...
Click to collapse
Installed universal usb drivers, got sideload working. But now after installing the rom it is in bootloop.
Installed slimbean, I can get into the rom, but only for a minute or two. I have no service at all. When I go into about phone phone status it shows unknown network, out of service, unknow phone number etc. How do I get that back up and running? And, how do I get it to stop rebooting after a few minutes? Thank you guys
Your partitions are borked from flashing a non Sprint Rom. To fix them
if you are s-on, flash the 4.3 full firmware http://www.androidfilehost.com/?fid=23159073880933344
if you are s-off, flash the modified firmware http://www.androidfilehost.com/?fid=23159073880933456
Then side load your Rom and you should be golden.
Sent from my HTCONE using xda app-developers app
Konfuzion said:
Your partitions are borked from flashing a non Sprint Rom. To fix them
if you are s-on, flash the 4.3 full firmware http://www.androidfilehost.com/?fid=23159073880933344
if you are s-off, flash the modified firmware http://www.androidfilehost.com/?fid=23159073880933456
Then side load your Rom and you should be golden.
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
Tried sideloading this and fails saying zip file is corrupt.
bbjay351 said:
Tried sideloading this and fails saying zip file is corrupt.
Click to expand...
Click to collapse
I hate to say it but use the Format Data option within TWRP to format your sdcard the try to sideload
---------- Post added at 05:59 PM ---------- Previous post was at 05:57 PM ----------
bbjay351 said:
Tried sideloading this and fails saying zip file is corrupt.
Click to expand...
Click to collapse
Check PM
Get a signed download of the firmware and flash thru fastboot if nothing else.
Sent from my HTCONE using XDA Premium 4 mobile app
Big thanks
Just wanted to say thanks again to Bigdaddy619! Spent the time with me to walk me through. Learned a lot from him. And a thanks to all that replied. Love learning new stuff, even if it makes me pull my hair out lol
bbjay351 said:
Just wanted to say thanks again to Bigdaddy619! Spent the time with me to walk me through. Learned a lot from him. And a thanks to all that replied. Love learning new stuff, even if it makes me pull my hair out lol
Click to expand...
Click to collapse
Updated steps for below
So this is what we did:
1.We downloaded the s-on firmware zip from the link provided by @Konfuzion
2.Renamed it firmware.zip (put the firmware.zip into the folder you use to open your cmd window)
3.Booted to bootloader
4.Then used these commands
Code:
Fastboot oem rebootRUU
Fastboot flash zip firmware.zip
Fastboot reboot
He got an error so I had him re-lock his bootloader
5.Ran the commands again
Got another error
Code:
failed 90 hboot pre-update! please flush image again
press the UP Arrow on your keyboard and press enter to issue the command again.
6.He was able to unlock the bootloader again and re-flash TWRP and sideload or adb push a rom to his phone.
7. S-OFF using Rumrunner
8.Win lol
bigdaddy619 said:
So this is what we did:
1.We downloaded the s-on firmware zip from the link provided by @Konfuzion
2.Renamed it firmware.zip (put the firmware.zip into the folder you use to open your cmd window)
3.Booted to bootloader
4.Then used these commands
Code:
Fastboot oem rebootRUU
Fastboot flash zip firmware.zip
Fastboot reboot
He got an error so I had him re-lock his bootloader (not sure if it was needed but...)
5.Ran the commands again
Got another error
Code:
failed 90 hboot pre-update! please flush image again
press the UP Arrow on your keyboard and press enter to issue the command again.
6.He was able to unlock the bootloader again and re-flash TWRP and sideload or adb push a rom to his phone.
7. S-OFF using Rumrunner
8.Win lol
Click to expand...
Click to collapse
Ok so I am in a similar position with one of my Sprint devices (I have 2 my kids and mine...) Anyway the device is s-off and had gone into TWRP and formated everything in anticipation of loading a new ROM that 4.3 based so wiped everything and then was going to push the rom with ADB... Problem I am having is that ADB doesn't see the device.
Now it shouldn't be a driver issue as I connected my other device to it with no problem and adb sees it fine.
@bigdaddy619.
I followed steps 1-4 except I used the zip for s-off and received no errors so I went back to twrp and attempted to sideload and still won't work.
Thanks for the assistance.
MG
EDIT: Well looks like it was a driver issue, odd since I wasn't having trouble connecting with my other Sprint HTC One but I changed to the Universal Windows ADB Driver listed here in this post. I also updated to the latest Android-SDK and was able to sideload... Thanks all for the info in this thread!
MG
I am hoping someone can help with this, my son completely wiped his Google Edition HTC One. When I asked him what he did he stated that he flashed TWRP and did a full wipe checking all of the boxes under the advanced tab. Then when he tried to flash Cyanogenmod 10.2 it keeps failing. I asked him why he did this and he said his friend told him how cool Cyanogenmod is so naturally he want it to! (By the way my son is 13).
I know very little about this phone but I would like to get the phone back to the way it was before he messed with it as it cost me $650 to buy it. I started reading about RUU files but from what I can tell the RUU will not work with S-ON. And I can't seem to flash any ROM as it keeps failing. Any suggestions would be a big help!
Don't worry this is fixable
First relock your bootloader
Then download a RUU.zip for GPe
boot into fastboot
and type this command (in your pc of course with adb) fastboot oem rebootRUU
A silver htc logo should show
copy the RUU you downloaded to your adb folder and rename to ruu.zip
and type this command fastboot flash zip ruu.zip
this command should be typed twice (ignore the error that shows up)
after the second time it's done
type fastboot reboot
should turn right up
Good luck
Then make him use a flip phone for a week as punishment lol
I had the same. In my case I started ruu for another version (international), of course ruu failed to install but it did fix partitions, after that I was able to sideload rom. I will try to find my topic and provide You with my solution.
This is my BLS/ALS with HTC One, patient is alive and well now, only camera has pink tint...
http://forum.xda-developers.com/showthread.php?t=2322851
Try with CWM instead of TWRP... and finally pass some information about progress.
Thealshear said:
Don't worry this is fixable
First relock your bootloader
Then download a RUU.zip for GPe
boot into fastboot
and type this command (in your pc of course with adb) fastboot oem rebootRUU
A silver htc logo should show
copy the RUU you downloaded to your adb folder and rename to ruu.zip
and type this command fastboot flash zip ruu.zip
this command should be typed twice (ignore the error that shows up)
after the second time it's done
type fastboot reboot
should turn right up
Good luck
Click to expand...
Click to collapse
Will the ruu method work if the phone is S-ON? All of the XDA posts I read state that you need to be S-OFF?
Give it a shot the phone is already bricked what you got to lose
crixley said:
Then make him use a flip phone for a week as punishment lol
Click to expand...
Click to collapse
For now until I can fix the phone he is back to two cans and string!
Sent from my Nexus 5 using Tapatalk
woody970 said:
For now until I can fix the phone he is back to two cans and string!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
You can run an ruu but it has to be newer..
See here:
http://forum.gsmhosting.com/vbb/f485/understanding-s-off-super-cid-s-read-b4-u-run-ruu-1505916/
crixley said:
You can run an ruu but it has to be newer..
Any idea where to download the RUU? The build number that was on the phone before all this started was KRT16S.H5 release-keys
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
woody970 said:
I am hoping someone can help with this, my son completely wiped his Google Edition HTC One. When I asked him what he did he stated that he flashed TWRP and did a full wipe checking all of the boxes under the advanced tab.
Click to expand...
Click to collapse
The good news are that the phone isn't bricked, imho. The bad ones are that you will have to play with ROMs recoveries and RUU's a bit in order to have a working phone back. First of all I would focus to succeed in flashing a ROM in order to boot your phone. Googling I found a user with your same error showed in the pic that solved the issue "checking the signature box then flash a ROM where he got the error then unchecked the same signature box and reflash with success". If this process doesn't work for you, I suggest to flash a different recovery such as CWM and try to flash the ROM through it. Anyway you'll need an unlocked bootloader for the entire process. Let me know if you succeed.
Sent from my HTC One using Tapatalk
Delgra said:
The good news are that the phone isn't bricked, imho. The bad ones are that you will have to play with ROMs recoveries and RUU's a bit in order to have a working phone back. First of all I would focus to succeed in flashing a ROM in order to boot your phone. Googling I found a user with your same error showed in the pic that solved the issue "checking the signature box then flash a ROM where he got the error then unchecked the same signature box and reflash with success". If this process doesn't work for you, I suggest to flash a different recovery such as CWM and try to flash the ROM through it. Anyway you'll need an unlocked bootloader for the entire process. Let me know if you succeed.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
when your son was flashing CM mod was he using the correct version? I don't recall but I tried flashing my ATT HTC one but I am running a WWE firmware so that made me have to flash the GSM version of CM mod. http://www.cmxlog.com/11/m7ul/ Try downloading the latest zip file there and than try mounting to his phone with the USB mount or if you have a USB OTG you can install it from a USB. It shouldn't matter if your S-ON or S-OFF for installing some roms it just helps you avoid taking extra steps to get the ROM to install.
When your flashing with TWRP make sure to do a advanced wipe and check everything that is on there. After you do a advanced wipe do a regular factory reset. I'm hoping that the new CM11 rom will flash for his phone. You can also use ADB sideload to send the zip files over to your phone if you cannot mount the phone. What ADB sideload does is open up a connection from your phones USB and lets you transfer zips over onto the internal SD card basically in DOS command.
I want to thank everyone for there guidance in this. After googling for a couple of days and a few failed attempts with the RUU command I was finally able to restore the phone. I was able to flash a nandroid backup using TWRp from another google edition HTC which brought the phone back to life. Then I flashed a stock recovery and OTA's became available to the phone. The once dead HTC is now back up and running stock 4.4 android. The only issue I with the phone now is that there is a popping sound after a notification comes in that I can't get rid of... Anyone have any ideas?
Sent from my Nexus 5 using Tapatalk
The popping noises seem to come after I updated to kit Kat I don't know but a lot of people might have that issue too.
Sent from my HTC One using Tapatalk
I recently got an HTC Raider (Bell) and was following the steps to Root the device and got stuck...
was following this : http://forum.xda-developers.com/showthread.php?t=1416836
the phone was all stock, stock rom, was able to unlock the bootloader via HTC website, did the Wire Trick to S-Off the device but when i got to step 3 "Update the HBOOT (Juopunutbear)" i got an error when trying to "fastboot flash zip jb_hboot.zip" using WCXJB ROOT PACK ... im at work now and cant remember the exact wording of the error, but it Fails (will update tonight with the exact error message).
i read around and people seemed to say that when doing the wire-trick the HBOOT was already being updated and people said it wasnt required, so i went ahead and followed the next steps (Perm-Root) which did work, then i went and tried to load a custom Rom + Gapps and they never worked (either they crashed 5 seconds after boot or just crash at the HTC boot screen and never work)
i can still access Recovery, etc ... i just cant flash any roms, and stupid me i erased my backup on the SDCARD (wiped the SDCARD so i lost my nand backup... i thought the backup was on the internal phone memory)...
any idea ???
thanks for your time, I apreciate it.
Extraze said:
I recently got an HTC Raider (Bell) and was following the steps to Root the device and got stuck...
was following this : http://forum.xda-developers.com/showthread.php?t=1416836
the phone was all stock, stock rom, was able to unlock the bootloader via HTC website, did the Wire Trick to S-Off the device but when i got to step 3 "Update the HBOOT (Juopunutbear)" i got an error when trying to "fastboot flash zip jb_hboot.zip" using WCXJB ROOT PACK ... im at work now and cant remember the exact wording of the error, but it Fails (will update tonight with the exact error message).
i read around and people seemed to say that when doing the wire-trick the HBOOT was already being updated and people said it wasnt required, so i went ahead and followed the next steps (Perm-Root) which did work, then i went and tried to load a custom Rom + Gapps and they never worked (either they crashed 5 seconds after boot or just crash at the HTC boot screen and never work)
i can still access Recovery, etc ... i just cant flash any roms, and stupid me i erased my backup on the SDCARD (wiped the SDCARD so i lost my nand backup... i thought the backup was on the internal phone memory)...
any idea ???
thanks for your time, I apreciate it.
Click to expand...
Click to collapse
So.. the error I get when trying to update the HBOOT (step 3 of the Superguide) is :
sending 'zip' (379KB) ... OKAY
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
FAILED (remote: 41 model id check fail)
finished. total time : 2.110s.
please help
Extraze said:
I recently got an HTC Raider (Bell) and was following the steps to Root the device and got stuck...
was following this : http://forum.xda-developers.com/showthread.php?t=1416836
the phone was all stock, stock rom, was able to unlock the bootloader via HTC website, did the Wire Trick to S-Off the device but when i got to step 3 "Update the HBOOT (Juopunutbear)" i got an error when trying to "fastboot flash zip jb_hboot.zip" using WCXJB ROOT PACK ... im at work now and cant remember the exact wording of the error, but it Fails (will update tonight with the exact error message).
i read around and people seemed to say that when doing the wire-trick the HBOOT was already being updated and people said it wasnt required, so i went ahead and followed the next steps (Perm-Root) which did work, then i went and tried to load a custom Rom + Gapps and they never worked (either they crashed 5 seconds after boot or just crash at the HTC boot screen and never work)
i can still access Recovery, etc ... i just cant flash any roms, and stupid me i erased my backup on the SDCARD (wiped the SDCARD so i lost my nand backup... i thought the backup was on the internal phone memory)...
any idea ???
thanks for your time, I apreciate it.
Click to expand...
Click to collapse
I answered this yesterday...
Jbhboot.zip is not flashable...
Unzip and apply accordingly...
And please... Read the question and answer thread before starting new
Sent from my Vivid 4G using Tapatalk
rignfool said:
I answered this yesterday...
Jbhboot.zip is not flashable...
Unzip and apply accordingly...
And please... Read the question and answer thread before starting new
Sent from my Vivid 4G using Tapatalk
Click to expand...
Click to collapse
thanks, but it did flash, and i did read, i read for about 20 hours on this forum, if not more.
here's how i fixed it, hopefuly this can help others...
when i got the "remote: 41 model id check fail" i found a post hidden in here telling to change the phone's CID by typing "fastboot oem writecid 11111111" this worked and i was able to continue with the steps... it did not cure my booting issue, i was still stuck at the white HTC screen... so i locked the device back, got a basic AT&T RUU (my phone was a Bell, so i dont think it matters which one you use) and wiped everything (SD card, cache, data, etc) ...
this solved my non-bootable issue ... so i went at it again, unlocked the phone via HTC's website, re-install a recovery, then the ROM i wanted.
I hope this can save someone a couple of hours of headaches and searches
Bricked htc vivid stuck on white screen
i unlocked the bootloader with unlocker v2 by Fenguepay after that it was partially rooted so after that i rebooted and everything was fine then i tried to flash rom with cm-11-20140628-unofficial-pyramid.zip and gapps it didnt go tru, so i downloaded yet another rom: resurrection remix - kk- v5. 1.2-20140521-holiday.zip and pa gapps modular mini 4.4.2-20131230-signed.zip yet it got stuck on d htc white screen. That was when i used vivid all in one kit v3.0 to relock so i could try flahing factory RUU but no way. i flashed it by entring h boot den got into recovery and wiped cache,davik and data and i also did factory reset before flashing it with the above mentioned roms and gapps. please someone should help me. i have read and read and read till i am now confused. :crying: