I Tried posting elsewhere but newer members can't post in dev section
Sorry
My HeroC is stuck in a HTC splash screen loop of aggravation.....
I have access to fastboot, hboot, and even rebootRUU...no adb obviously. I've downloaded the 2.31.651.7 RUU and renamed it HERCIMG.zip but it will not recognize the file on 3 different sd cards... after rebootRUU I can fastboot flash zip HERCIMG.zip with absolutely no problem at all....UNTIL typing fastboot reboot, then it's back to the dreaded loop of aggravation... Tried the 1.56RUU but every time i get the 140 error, the phone had CM7 on it before and I don't know what happened
The hboot is 1.47 and S-ON
typing fastboot oem boot gives me this....
C:\android-sdk\platform-tools>fastboot oem boot
... INFOsetup_tag addr=0xA8000100 cmdline add=0x8F06E63C
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 32
INFOTAG:hwid 0x0
INFOTAG:skuid 0x21102
INFOTAG:hero panel = 0x4
INFOTAG:engineerid = 0x0
INFOMCP dual-die
INFOMCP dual-die
INFOTAG:mono-die = 0x0
INFODevice CID is not super CID
INFOCID is SPCS_001
INFOsetting.cid::SPCS_001
INFOserial number: HT06CHF01833
INFOcommandline from head: no_console_suspend=1 console=null
INFOcommand line length =413
INFOactive commandline: board_heroc.disable_uart3=0 board_heroc.
INFOusb_h2w_sw=0 board_heroc.disable_sdcard=0 board_heroc.usb_ra
INFOdio_diag=0 board_heroc.debug_uart=0 smisize=32 androidboot.
INFObaseband=2.42.01.04.27 androidboot.cid=SPCS_001 androidboot.
INFOcarrier=COMMON androidboot.mid=HERO20000 androidboot.keycaps
INFO=qwerty androidboot.mode=normal androidboot.serialno=HT06CHF
INFO01833 androidboot.bootloader=1.47.0000 no_console_suspend=1
INFOconsole=null
INFOaARM_Partion[0].name=misc
INFOaARM_Partion[1].name=recovery
INFOaARM_Partion[2].name=boot
INFOaARM_Partion[3].name=system
INFOaARM_Partion[4].name=cache
INFOaARM_Partion[5].name=userdata
INFOpartition number=6
INFOValid partition num=6
INFO69466957
INFO69784520
INFO7473
INFO0
INFO0
but ends down farther with - FAILED (status read failed (Too many links))
If you can access Hboot you can use the latest RUU, and return to stock then reroot. Its not too difficult and doesnt take much time. this is the Ruu I use, RUU_Hero_C_Sprint_1.29.651.1_signed_release.exe you can find it in developemeny and use regaws rooter (old versoion if you can find it). hope this helps in some way,,,Later
jj9320tsi said:
I Tried posting elsewhere but newer members can't post in dev section
Sorry
My HeroC is stuck in a HTC splash screen loop of aggravation.....
I have access to fastboot, hboot, and even rebootRUU...no adb obviously. I've downloaded the 2.31.651.7 RUU and renamed it HERCIMG.zip but it will not recognize the file on 3 different sd cards... after rebootRUU I can fastboot flash zip HERCIMG.zip with absolutely no problem at all....UNTIL typing fastboot reboot, then it's back to the dreaded loop of aggravation... Tried the 1.56RUU but every time i get the 140 error, the phone had CM7 on it before and I don't know what happened
The hboot is 1.47 and S-ON
typing fastboot oem boot gives me this....
C:\android-sdk\platform-tools>fastboot oem boot
... INFOsetup_tag addr=0xA8000100 cmdline add=0x8F06E63C
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 32
INFOTAG:hwid 0x0
INFOTAG:skuid 0x21102
INFOTAG:hero panel = 0x4
INFOTAG:engineerid = 0x0
INFOMCP dual-die
INFOMCP dual-die
INFOTAG:mono-die = 0x0
INFODevice CID is not super CID
INFOCID is SPCS_001
INFOsetting.cid::SPCS_001
INFOserial number: HT06CHF01833
INFOcommandline from head: no_console_suspend=1 console=null
INFOcommand line length =413
INFOactive commandline: board_heroc.disable_uart3=0 board_heroc.
INFOusb_h2w_sw=0 board_heroc.disable_sdcard=0 board_heroc.usb_ra
INFOdio_diag=0 board_heroc.debug_uart=0 smisize=32 androidboot.
INFObaseband=2.42.01.04.27 androidboot.cid=SPCS_001 androidboot.
INFOcarrier=COMMON androidboot.mid=HERO20000 androidboot.keycaps
INFO=qwerty androidboot.mode=normal androidboot.serialno=HT06CHF
INFO01833 androidboot.bootloader=1.47.0000 no_console_suspend=1
INFOconsole=null
INFOaARM_Partion[0].name=misc
INFOaARM_Partion[1].name=recovery
INFOaARM_Partion[2].name=boot
INFOaARM_Partion[3].name=system
INFOaARM_Partion[4].name=cache
INFOaARM_Partion[5].name=userdata
INFOpartition number=6
INFOValid partition num=6
INFO69466957
INFO69784520
INFO7473
INFO0
INFO0
but ends down farther with - FAILED (status read failed (Too many links))
Click to expand...
Click to collapse
Did you try this RUU zip http://forum.xda-developers.com/showthread.php?t=804692? I think you can be S-on and still use it, but I could be totally wrong because I haven't been S-on in a long time. Maybe it is only fastboot that will work. I know that there is a thread in the HeroC Development section that is dedicated to that as well. Make sure that you don't name the zip "HERCIMG.zip.zip" accidently. You don't need to put .zip in the name because it does that automatically. I have to go I would research a little more regarding the fastboot/hboot/s-on issue. I am guessing that you have no recovery image anymore, or are you trying to get back to stock?
Drunkpilot said:
Did you try this RUU zip http://forum.xda-developers.com/showthread.php?t=804692? I think you can be S-on and still use it, but I could be totally wrong because I haven't been S-on in a long time. Maybe it is only fastboot that will work. I know that there is a thread in the HeroC Development section that is dedicated to that as well. Make sure that you don't name the zip "HERCIMG.zip.zip" accidently. You don't need to put .zip in the name because it does that automatically. I have to go I would research a little more regarding the fastboot/hboot/s-on issue. I am guessing that you have no recovery image anymore, or are you trying to get back to stock?
Click to expand...
Click to collapse
That is the RUU file i used after fastbooting into the RUU. it flashes all the way to the OKAY message at the end. then typing fastboot reboot, it reboots all right..... right back into the splash screen loop. I've ran three different sprint RUU executable programs, always get the ERROR 140 BOOTLOADER ERROR, or some crap about reverting to an older version blah blah blah... But every RUU program I've ran says the current version is the .7 ....the phone had CM7 prior to this issue. I replaced the phone when this happened in May 2011, but i can't stand this POS SANYO ZIO lol
Thanks guys, I'll just keep at it until it becomes a paperweight lol
jj9320tsi said:
That is the RUU file i used after fastbooting into the RUU. it flashes all the way to the OKAY message at the end. then typing fastboot reboot, it reboots all right..... right back into the splash screen loop. I've ran three different sprint RUU executable programs, always get the ERROR 140 BOOTLOADER ERROR, or some crap about reverting to an older version blah blah blah... But every RUU program I've ran says the current version is the .7 ....the phone had CM7 prior to this issue. I replaced the phone when this happened in May 2011, but i can't stand this POS SANYO ZIO lol
Thanks guys, I'll just keep at it until it becomes a paperweight lol
Click to expand...
Click to collapse
Are you still having this issue ??
#Root-Hack\Mod*Always_
""Shooter on Deck""
jj9320tsi said:
That is the RUU file i used after fastbooting into the RUU. it flashes all the way to the OKAY message at the end. then typing fastboot reboot, it reboots all right..... right back into the splash screen loop. I've ran three different sprint RUU executable programs, always get the ERROR 140 BOOTLOADER ERROR, or some crap about reverting to an older version blah blah blah... But every RUU program I've ran says the current version is the .7 ....the phone had CM7 prior to this issue. I replaced the phone when this happened in May 2011, but i can't stand this POS SANYO ZIO lol
Thanks guys, I'll just keep at it until it becomes a paperweight lol
Click to expand...
Click to collapse
This is the one I have used from H-boot, not fastboot. Have you tried it from H-boot after renaming it HERCIMG and putting it on your sd card? Does it recognize it? Like I said in the previous post, if you add a .zip to the name it F's it up like if you do a "mtdpartmap.txt" using Firerat's because it's already a text file. Maybe it's a moot point if you are not S-off.
Please refrain from swearing. Even if it's #$(*&#$ ... it's still against forum rules.
Yes I'm still having this issue, I've run the file thru rebootRUU and also from HBOOT, just every time I get a successful flash when it goes to reset it goes back into the HTC splash screen loop. For quite a long time I might add. Obviously I'm doing something wrong somewhere down the line. It would've been fine if i didn't use Sprint's update way back when. I have the Nandroid backups from prior to all this, but I can't get to any point to be able to use them.... If it goes back to stock I can always restore them, but just can't seem to get there yet lol.
I reprogrammed it to Cricket's network a long time ago, do you think what was changed in QPST can be causing any issues?
Sorry for being a nuisance everyone
Win7 could be causing a problem???
jj9320tsi said:
Yes I'm still having this issue, I've run the file thru rebootRUU and also from HBOOT, just every time I get a successful flash when it goes to reset it goes back into the HTC splash screen loop. For quite a long time I might add. Obviously I'm doing something wrong somewhere down the line. It would've been fine if i didn't use Sprint's update way back when. I have the Nandroid backups from prior to all this, but I can't get to any point to be able to use them.... If it goes back to stock I can always restore them, but just can't seem to get there yet lol.
I reprogrammed it to Cricket's network a long time ago, do you think what was changed in QPST can be causing any issues?
Sorry for being a nuisance everyone
Win7 could be causing a problem???
Click to expand...
Click to collapse
Check your pm's
#Root-Hack\Mod*Always_
""Shooter on Deck""
If there one person I see more helping out with the complicated problems here and the shooter threads its laie guaranteed one if the most useful members here.
Sent from my PG86100 using xda premium
MattCrystal said:
If there one person I see more helping out with the complicated problems here and the shooter threads its laie guaranteed one if the most useful members here.
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Thanks Matt man I appreciate that. Same to you man I like how you been holding down the hero as well keep up the excellence. Glad to have to have you in shooter land as well.
#Root-Hack\Mod*Always_
""Shooter on Deck""
laie1472 said:
Thanks Matt man I appreciate that. Same to you man I like how you been holding down the hero as well keep up the excellence. Glad to have to have you in shooter land as well.
#Root-Hack\Mod*Always_
""Shooter on Deck""
Click to expand...
Click to collapse
Im just lurking in shooter land. Im compiling ICS for it now, or at least trying to. Dastin and i would like to continue Team Hydra and i think ICS is the next step.
Funny part is I don't even like ICS.
Sent from my PG86100 using xda premium
MattCrystal said:
Im just lurking in shooter land. Im compiling ICS for it now, or at least trying to. Dastin and i would like to continue Team Hydra and i think ICS is the next step.
Funny part is I don't even like ICS.
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Whaaaat!!! Me lost on this one Lol why not may I ask you kind sir ????
#Root-Hack\Mod*Always_
""Shooter on Deck""
The whole look of it. Just too dramatic of a change to me but eventually ill get used to it. I better start liking it because its all I'm building.
Sent from my PG86100 using xda premium
This may be of no help to you but it cant hurt. I have had ROM's boot loop if I don't wipe the user data. If you hold back and home on start up it will let you wipe form the boot loader! But who am I to talk my phone is in about the same state yours is! Laie has been a big help with my phone too!
RyAndoid said:
This may be of no help to you but it cant hurt. I have had ROM's boot loop if I don't wipe the user data. If you hold back and home on start up it will let you wipe form the boot loader! But who am I to talk my phone is in about the same state yours is! Laie has been a big help with my phone too!
Click to expand...
Click to collapse
Lmao man, thanks for the complement much appreciation however you misunderstood the posts. His phone isn't messed up he's a dev, look on the hero development thread he has roms posted. He's developing ics and I was asking him why he didn't prefer ics.
#Root-Hack_Mod*Always\
MattCrystal said:
The whole look of it. Just too dramatic of a change to me but eventually ill get used to it. I better start liking it because its all I'm building.
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
100% agree on the look of ics man imo its just not for me. I'll be keeping my current setup because I favor it over the stock ics. I know the leaks are out now and I know roms are being made but I don't know if any themes will emerge. If they do then I might flash it, I'm to hooked on eye candy.
#Root-Hack_Mod*Always\
visual reference to what my problem is
http://www.youtube.com/watch?v=1NtTcVaGYpw
I sent you a few pm's
#Root-Hack_Mod*Always\
Related
Warning: This method hasn't been throughly tested. It could brick your HTC Click (Tattoo). In either situation, I am not responsible if your phone explodes into a portable fireworks show. Should you decide to take the risk, please make sure you have backed up your data in case of a brick. Thanks.
I found an another way to flash the HTC Tattoo via HBOOT.
What I did is name 'CLICDIAG.nbh' to 'CLICIMG.nbh' and got the following:
HBOOT said:
CLICK PVT SHIP S-ON
HBOOT-0.52.0001 (CLIC10000)
MICROP-0203
RADIO-3.35.07.20
Sep 22, 2009, 14:40:39
HBOOT
Parsing [CLICIMG.nbh]
[1] MFG_DIAG
Do you want to start update?
<ACTION> Yes
<Power> No
Click to expand...
Click to collapse
Knowing that I could possibly screw up/brick my Tattoo (and make it continuously boot into the DIAG program), I aborted the update. It goes to show that the Click/Tattoo still supports the classic way of flashing ROMs (like the way we got root on the HTC Dream/G1 via DREAIMG.nbh).
I have also heard that if you get rom.zip from the RUU (go to your temp folder in Windows while the RUU is on the "Welcome" screen and search for rom.zip) and rename it to 'CLICIMG.zip' and place it in the root of your MicroSD card, the Tattoo will also detect it as a ROM and ask if you'd like to flash it.
Opinions/Suggestions/Comments, anyone?
UPDATE: Tried to flash the ROM with SU-binary, and it bombed out with the dreaded error: "Main version is old! Update fail!". I googled for a solution, it said something about 'fixing' a perfect SPL on the Magic/Sapphire. Alas, I'm not game enough to try using a different devices' firmware.
I'm tapped for ideas.
Hi.
Did you check or try the recovery partition options?
Maybe something could be done with it...
android-dls.com/wiki/index.php?title=Replace_Recovery_Partition
Just tried flashing... sadly failed with a 'signature error'.
P
Note: I was not using a goldcard, assume it wouldn't make any difference in this instance?
P
Coburn64 said:
UPDATE: Tried to flash the ROM with SU-binary, and it bombed out with the dreaded error: "Main version is old! Update fail!". I googled for a solution, it said something about 'fixing' a perfect SPL on the Magic/Sapphire. Alas, I'm not game enough to try using a different devices' firmware.
I'm tapped for ideas.
Click to expand...
Click to collapse
Bad. RUU checking rom version to prevent downgrade.
ROM with test signed keys is one of oldest.
Need to search something new...
modaco said:
Note: I was not using a goldcard, assume it wouldn't make any difference in this instance?
P
Click to expand...
Click to collapse
Since you were willing to flash it, I think trying with a goldcard is well worth the effort. It painless to create one..
It didn't help.
Coburn and I have been chatting on IRC (#modaco on freenode) and we're kinda running out of ideas at this point...
P
Does that mean you don't see a chance getting root ever or just not that way?
Any 1 root
hi guys
any 1 successfully Root/or Flashed Via Goldcard ?
-bm- said:
Does that mean you don't see a chance getting root ever or just not that way?
Click to expand...
Click to collapse
We're trying our best. The root looks grim, unless we can somehow get a S-OFF bootloader. :/
Getting a S-OFF SPL would only be possible through HTC (who hold the keys to sign it). Either we're very lucky and someone leaks such a SPL or we're dead in the water.
Next best hope is someone finding a local root exploit on the kernel or in one of the setuid binaries that come in the Tattoo.
I have updated a rooted Tattoo with rom renamed to CLICIMG.zip and and an unrooted Magic 32a with rom.zip renamed to SAPPIMG.zip and copied to and fat32 sd followed by fastboot as described earlier in this thread - and2209
Thank you man my old dead tattoo is alive now becouse of you! thanks again
Like AlphaRev, I am NOT responsible if your phone gets bricked.
The size is a bit bigger than the stock alpharev iso, probably because of the way I packed it, I successfully s-off'd my Bell Mobility Legend!
There was one little part, when it was flashing the HBOOT, it froze on step 3 just past the MD5 check saying flashing... OK. I waited a few mins, then rebooted my phone. All was fine, S-OFF.
Thanks to ariaxu for the necessary information to add in the alpharev script!
Link to my repacked .iso below.
http://uploading.com/files/m6c95a4d/alpharevBellMOD_rev2.iso/
MEGAUPLOAD Link
Edit: Changed the size of the iso, I forgot I had a copy of the archive inside a folder in the root of the filesystem, removed that. Now is ~20 mb smaller
Edit: To make the step process easier, use the counting method. On the first sequence that needs user interaction, count from 21, 22, 23 (3 seconds) then press power. On the second sequence, count from 21, 22, 23, 24 (4 seconds) then press power.
Nice job.. Hope you will help out a lot of other Bell owners out there..
Sent from my S-OFF'ed HTC Legend
Nice job dude. I don't think I'm quite in the mindset to perform such surgery right now, but I'm sure i'll get to it pretty soon.
It's fairly easy to do, just follow the instructions.
Sent from my S-OFF Bell HTC Legend using XDA App
Good job man! I wish that someone will figured it out how to S-OFF phones with hboot 1.01!
Sent from my Legend using XDA App
Cool ! Much thanks !
Running CM7 nightly on my Virgin Legend. Didn't work last night on stock firmware, LOL.
Worked first attempt, following your tips and some picked up in the main AlphaRev thread:
- wait for "HBOOT" on phone to change to "HBOOT-USB_PLUG" before hitting "Any Key".
- Count 3 seconds (1 missisippi, 2..., 3...) then hold power down for 10 seconds or so. When I did this I hit the power button SLIGHTLY before the message appeared on the screen.
And yeah, feel AWFUL nervous rebooting after the flash... Only way I found to reboot was to run "adb reboot". Didn't wanna pull batteries to reboot for sure.
I have no idea why it froze on the last step though, alpharev would probably know more if they had a Bell Legend...
Successfully flashed, woot.
Just attempted this for my Bell Legend and the counting method worked for me up until step 3 but at step 3 my timing must have been off and it got frozen when I tried to select fastboot.. Waited about 10 minutes for something to happen before finally deciding to pull the battery and then do a nandroid restore so I could try the whole thing all over again. However, after completing the restore, my phone rebooted but just stayed at the HTC boot up screen for about 20 minutes, just wouldn't boot, so I did another battery pull to try it again. Is it possible my phone is bricked?
Also, if it helps anyone, during the alpharev process I chose 'yes' when prompted to install clockworkmod recovery... should I not have?
Tried deleting the cache in recovery?
Kwen said:
Tried deleting the cache in recovery?
Click to expand...
Click to collapse
Hmm.. I didn't think to try that but doesn't the cache get overwritten anyway when I restore a backup?
UPDATE: Okay, so I tried deleting the cache and it's no good.. still unable to boot the phone, but I am still able to get into fake-flash menu.. so I'm kind of at a loss, not sure whether I am bricked or not or what to do about it
Try wiping everything on fake flash or you can try and restore using an older RUU and root again...
Sent from my S-OFF Bell Canada HTC Legend.
marclh1992 said:
Try wiping everything on fake flash or you can try and restore using an older RUU and root again...
Sent from my S-OFF Bell Canada HTC Legend.
Click to expand...
Click to collapse
Yeah, that was going to be my next course of action but luckily I determined that my nandroid backup was somehow corrupted.. I managed to restore an earlier backup with no problems. Thanks for the advice though
No problem! I was just scared that flashing the recovery would intentionally brick the Bell Legend. (It IS unsupported by Alpharev)
marclh1992 said:
No problem! I was just scared that flashing the recovery would intentionally brick the Bell Legend. (It IS unsupported by Alpharev)
Click to expand...
Click to collapse
No sweat man. Haha I decided that I'd bite the bullet and give it another go, which brings me to one more question. This time around I got through steps 1 and 2 just fine, and now at the third step I believe it's frozen at 'Flashing new bootblock: OK' just like you described in your first post.
I'm leaving it for a bit to see if it'll resolve itself on its own because I'm worried now that rebooting the phone at this stage may brick it perhaps?
For reference, my pc screen shows 'Waiting for flashing to complete...'
and on my phone it says
'Dumping old HBOOT.
Flashing Alpharev HBOOT: SUCCESS!
HBOOT Md5sum: b8c9de531c5e828abf0a8607732a9071.
Flashing new bootblock: OK'
I assume all this is normal but I'm not sure how to proceed
I have no idea why it freezes on that part for Bell Legends, but just unplug the USB and do a battery pull. You should be S-OFF.
Haha so I was clearly too damn impatient/excited and used adb reboot as mikereidis did (too nervous to pull the battery). And it worked, I'm S-OFF, wooo!!
Thanks a lot!
el.dizzee said:
Haha so I was clearly too damn impatient/excited and used adb reboot as mikereidis did (too nervous to pull the battery). And it worked, I'm S-OFF, wooo!!
Thanks a lot!
Click to expand...
Click to collapse
Congrats !
AFAIK, if the phone comes up and does much of anything, like displaying a logo, your phone is not truly and ir-reversibly bricked.
To be truly bricked IMO, absolutely nothing would show up on screen, not even a recharging logo. I had that happen to my last phone; absolutely no sign of life.
And BTW, when I say "ir-reversibly bricked", I mean unrecoverable by the usual relatively "simple" methods most of us use. Specialized hardware and techniques can unbrick just about any phone, if you have the right hardware and/or know the special techniques.
Is the Bell Legend significantly different from European / normal Legend models? I have an HTC Legend bought from United Kingdom (unbranded and unlocked). Would I have a problem trying out this method? My phone comes with HBOOT 1.01 and I have not yet been able to revert it to the older one. Even flashing official RUU with Goldcard allows the entire process to go through except for step 1 (it claims that there is no need to downgrade HBOOT).
1+ HBoots are not supported yet, sorry. Even alpharev has not found out a way to S-OFF it.
Well after installing few games and reflashing my recovery after accidentally putting an older version on, I somehow in turn corrupted my boot loader, system files, data etc, so much so that my backups would boot once but never a second time, clearing my cache and dalvik only made it stuck on htc screen and afterwards it just repeatedly booted into clockwork over and over. This all happening after trying to also make a new nand backup where it hung at system for 30 minutes only to eat up my battery from 100 to 10.
it does charge, I tried using the buttons to boot into fastboot and hboot but it doesn't seem to work, but fastboot usb comes up with I turn it on while connected to the computer but sadly I keep getting error 171 when I try to RUU it.
Have you tried the ruu in zip format??? .
Found here
forum.xda-developers.com/showthread.php?t=804692
#Root/Hack_Mod-Always®
laie1472 said:
Have you tried the ruu in zip format??? .
Found here
forum.xda-developers.com/showthread.php?t=804692
#Root/Hack_Mod-Always®
Click to expand...
Click to collapse
When I try to go into hboot mode I get no change on the screen it stays at the htc logo.
try this then try RUU
http://forum.xda-developers.com/showthread.php?t=843544
il Duce said:
try this then try RUU
http://forum.xda-developers.com/showthread.php?t=843544
Click to expand...
Click to collapse
my doesn't get past htc screen, how would I use that?
gigermunit said:
When I try to go into hboot mode I get no change on the screen it stays at the htc logo.
Click to expand...
Click to collapse
If your not s-off flash darch's eng/spl. Then try the ruu in zip format. Look in hero dev section for darchs method. I posted a working zip on that thread.
Darchs spl s-off
http://forum.xda-developers.com/showthread.php?t=765237
ruu in zip format
http://forum.xda-developers.com/showthread.php?t=804692
#Root/Hack_Mod-Always®
laie1472 said:
If your not s-off flash darch's eng/spl. Then try the ruu in zip format. Look in hero dev section for darchs method. I posted a working zip on that thread.
Darchs spl s-off
http://forum.xda-developers.com/showthread.php?t=765237
ruu in zip format
http://forum.xda-developers.com/showthread.php?t=804692
#Root/Hack_Mod-Always®
Click to expand...
Click to collapse
no recovery to flash a zip.
if you mean something else mind linking me? Ive been searching through xda and ppcgeek along with google since 10am est, it's 3:49pm now.
gigermunit said:
no recovery to flash a zip.
if you mean something else mind linking me? Ive been searching through xda and ppcgeek along with google since 10am est, it's 3:49pm now.
Click to expand...
Click to collapse
I hope you're not making time sensitive demands.....
Try this link and the zip near the end of the thread, if it doesn't work try the other link I put up earlier.
http://forum.xda-developers.com/showthread.php?t=958968
EDIT: are you s-off, and if so which method did you use?
il Duce said:
I hope you're not making time sensitive demands.....
Try this link and the zip near the end of the thread, if it doesn't work try the other link I put up earlier.
http://forum.xda-developers.com/showthread.php?t=958968
Click to expand...
Click to collapse
I'm not and I am having the exact same issues as
http://forum.xda-developers.com/showthread.php?t=788894
I called sprint and was told since I have had the phone for less than a year I can get a free one from htc just need to go to sprint and let them fiddle with it, if they can fix it then it's a free repair if they can't its a free replacement, I am supposing no traces of rooting can even be seen the phone literally has nothing on it, it nuked itself while I went to take a leak, left it on updating 10 applications, backing up the others and flashing my cw3 recovery, after that it was acting up, kept booting to recovery than after flashing things and formatting it nuked everything else recovery and all.
gigermunit said:
I'm not and I am having the exact same issues as
http://forum.xda-developers.com/showthread.php?t=788894
I called sprint and was told since I have had the phone for less than a year I can get a free one from htc just need to go to sprint and let them fiddle with it, if they can fix it then it's a free repair if they can't its a free replacement, I am supposing no traces of rooting can even be seen the phone literally has nothing on it, it nuked itself while I went to take a leak, left it on updating 10 applications, backing up the others and flashing my cw3 recovery, after that it was acting up, kept booting to recovery than after flashing things and formatting it nuked everything else recovery and all.
Click to expand...
Click to collapse
Well, maybe you have a brick. Cool you have the warranty. And if xda can't find a way to fix it, sprint almost surely cannot, lol. I would say get the new one sent to you, that way when you send the old one back it will be too late for them to tell at you - IF they figure it out.
sent from a series of tubes.
il Duce said:
Well, maybe you have a brick. Cool you have the warranty. And if xda can't find a way to fix it, sprint almost surely cannot, lol. I would say get the new one sent to you, that way when you send the old one back it will be too late for them to tell at you - IF they figure it out.
sent from a series of tubes.
Click to expand...
Click to collapse
Yeah, I may not post alot but that's due to college and church, otherwise I would be making guides and helping out in Q&A instead of asking for it now haha, I tried so many things and nothing worked so I concluded a brick, sadly I'll never know why my phone randomly nuked itself, I didn't do anything I normally don't was so odd.
Update: they couldn't fix it so they are sending me a new phone.
Hey guys, I'm attempting to root my HTC Vivid and things aren't going as well as I hoped. I'm new to Android, this is my first Android phone, and I'm still trying to learn a bit.
I have been following the guide here: http://forum.xda-developers.com/showthread.php?t=1416836
So far I have unlocked my bootloader via HTCdev.com and now I'm working on flashing CWM following the guide above. I booted into H-Boot and plugged the phone into my computer and typed "fastboot devices" and it displayed my phone in command prompt. Then, following the instructions, I typed "Fastboot flash recovery root_recovery.img" and this is what command prompt printed out:
sending 'recovery' (4448 KB)...
OKAY [ 0.998s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.763s
I'm trying to figure out why it FAILED, and I've been looking around but I just can't seem to figure it out. What am I doing wrong?
Thanks for your help!
Never seen this before. Are you sure the unlock worked correctly? Does it say unlocked at the top of the screen when you go into hboot?
Sent from my Transformer TF101 using Tapatalk
becandl said:
Hey guys, I'm attempting to root my HTC Vivid and things aren't going as well as I hoped. I'm new to Android, this is my first Android phone, and I'm still trying to learn a bit.
I have been following the guide here: http://forum.xda-developers.com/showthread.php?t=1416836
So far I have unlocked my bootloader via HTCdev.com and now I'm working on flashing CWM following the guide above. I booted into H-Boot and plugged the phone into my computer and typed "fastboot devices" and it displayed my phone in command prompt. Then, following the instructions, I typed "Fastboot flash recovery root_recovery.img" and this is what command prompt printed out:
sending 'recovery' (4448 KB)...
OKAY [ 0.998s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.763s
I'm trying to figure out why it FAILED, and I've been looking around but I just can't seem to figure it out. What am I doing wrong?
Thanks for your help!
Click to expand...
Click to collapse
are you sure it says UNLOCKED across the top of HBOOT?
becandl said:
Hey guys, I'm attempting to root my HTC Vivid and things aren't going as well as I hoped. I'm new to Android, this is my first Android phone, and I'm still trying to learn a bit.
I have been following the guide here: http://forum.xda-developers.com/showthread.php?t=1416836
So far I have unlocked my bootloader via HTCdev.com and now I'm working on flashing CWM following the guide above. I booted into H-Boot and plugged the phone into my computer and typed "fastboot devices" and it displayed my phone in command prompt. Then, following the instructions, I typed "Fastboot flash recovery root_recovery.img" and this is what command prompt printed out:
sending 'recovery' (4448 KB)...
OKAY [ 0.998s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.763s
I'm trying to figure out why it FAILED, and I've been looking around but I just can't seem to figure it out. What am I doing wrong?
Thanks for your help!
Click to expand...
Click to collapse
Yea... what the other guys said. You must not be actually unlocked via HTC Dev because it's failing at the part when it's checking with the bootloader. Go into bootloader and tell us if it says unlocked. (Turn off phone, once off, hold down power and vol down button)
Good call guys, it says *** RELOCKED *** at the top. Now the question is... why? I'll attempt to unlock it again and let you know how it turns out.
Alright, I tried it again and that did the trick. I'm now permanently rooted! This is so exciting! Thanks again guys.
So unfortunately I'm having a bit more trouble. I got my phone rooted and tried installing the Holicakes kernel, and now my phone is stuck on the white HTC screen. I can boot into recovery, just not into the ROM. What should I do? I've tried doing a factory reset and stuff but it's still doing the same thing.
been there...
becandl said:
So unfortunately I'm having a bit more trouble. I got my phone rooted and tried installing the Holicakes kernel, and now my phone is stuck on the white HTC screen. I can boot into recovery, just not into the ROM. What should I do? I've tried doing a factory reset and stuff but it's still doing the same thing.
Click to expand...
Click to collapse
I Just went thru something similar this morning with my Vivid, I did the following to get it back:
1. Get the Cingular RUU if you don't already have it (I got it here, the server was down in the main RUU thread for this ruu file) http://forum.xda-developers.com/showthread.php?t=1416956
2. Had to relock bootloader to get past the verification error (if you have your unlock.bin you just reuse the same file to re-unlock)
3. Boot your phone to bootloader then select fastboot. (you will likely have to pull the battery to get this step done)
4. Connect your phone & run the RUU and you should be good.
5. (optional) Re-unlock & root.
Hope this helps
Cheers
BR
becandl said:
So unfortunately I'm having a bit more trouble. I got my phone rooted and tried installing the Holicakes kernel, and now my phone is stuck on the white HTC screen. I can boot into recovery, just not into the ROM. What should I do? I've tried doing a factory reset and stuff but it's still doing the same thing.
Click to expand...
Click to collapse
Did you flash the kernel but not the rom? If you are going to flash the kernel, you must flash the rom right after, without even leaving recovery. Try again and see if it works.
Sent from my HTC PH39100 using xda premium
Yup that was it. I just tried flashing the ROM and it booted into the ROM just fine. I like some of the features but I'm not so sure I'm gonna keep it. Thanks again everyone!
becandl said:
Yup that was it. I just tried flashing the ROM and it booted into the ROM just fine. I like some of the features but I'm not so sure I'm gonna keep it. Thanks again everyone!
Click to expand...
Click to collapse
No problem. Try out rumrunner if you'd like. It's got the newest sense 3.5 which is different from our stock Rom.
Sent from my HTC PH39100 using xda premium
I'm new to android, Vivid is my first device. Got my phone rooted, thanks to all the info I found throughout the forum.
2lazy2day said:
I'm new to android, Vivid is my first device. Got my phone rooted, thanks to all the info I found throughout the forum.
Click to expand...
Click to collapse
allow me to congratulate you on utilizing the information already here and not firing up a new thread asking how to do it....
Was that a stab at me?
Sent from my HTC PH39100 using Tapatalk
becandl said:
Was that a stab at me?
Sent from my HTC PH39100 using Tapatalk
Click to expand...
Click to collapse
nope. not at all.
you should see the other forums i am in.
even the captivate that has been out since July 2010 still has people come in and make new posts asking how to root. and samsungs are among the easiest damn phones EVER to root....not to mention the GOBS of information out there on it.
the vivid doesnt have much. slapshot has been helpful with the guide and keeping it up to date.
Pirateghost said:
nope. not at all.
you should see the other forums i am in.
even the captivate that has been out since July 2010 still has people come in and make new posts asking how to root. and samsungs are among the easiest damn phones EVER to root....not to mention the GOBS of information out there on it.
the vivid doesnt have much. slapshot has been helpful with the guide and keeping it up to date.
Click to expand...
Click to collapse
Yea that guide was really helpful. I had a fair bit of trouble trying to get root and everything, but now that I have, I've at least learned something about how this all works. It's addicting Can't wait for more ROMs to start coming out.
becandl said:
Yea that guide was really helpful. I had a fair bit of trouble trying to get root and everything, but now that I have, I've at least learned something about how this all works. It's addicting Can't wait for more ROMs to start coming out.
Click to expand...
Click to collapse
What gave you the most trouble would you say? I'm trying to get feedback from the successful people so I can add more details where needed, but as soon as they get root they just ditch lol.
The trouble I was having had nothing to do with the guide, just my ignorance on the topic. I had no clue what I was doing. I screwed up a few times by accidentally re-locking the bootloader without noticing it, which obviously caused some problems. And then flashing a kernel confused me a bit. I was trying to install Holicakes ROM and I didn't realize that you wouldn't be able to boot after installing the kernel, and that you had to install the ROM on top of it as well.
becandl said:
The trouble I was having had nothing to do with the guide, just my ignorance on the topic. I had no clue what I was doing. I screwed up a few times by accidentally re-locking the bootloader without noticing it, which obviously caused some problems. And then flashing a kernel confused me a bit. I was trying to install Holicakes ROM and I didn't realize that you wouldn't be able to boot after installing the kernel, and that you had to install the ROM on top of it as well.
Click to expand...
Click to collapse
Gotcha, thanks for the info. Glad you got it all figured out. The kernel installing is being worked on. PG is testing out a new app.
Forgive me for posting here, I'm still noob and cant post in development forum. Just wanted to put out there, I flashed the RumRaider beta10. Had no issues flashing and booting, was pretty smooth with the provided instructions. Wifi working, had to manually set the AT&T pta, so far havent noticed any issues with mobile data ot MMS. This is a very fast ROM, ran Quadrant with a result of 2969, sorry I don't know how to do a screenshot yet. Very nice work so far
Sent from my HTC PH39100 using xda premium
Hello all,
I'm sorry to interrupt you all, but this is rather important!
I tried to root my girlfriends Velocity 4G which she got with her contract with A1 (austrian carrier).
I already flashed a One S and knew of the complications a root for HTC could bring.
So I tried to get everything together before flashing and then I did it...
Got the bootloader unlocked, installed TWRP and flashed sun_dreams rom.
Don't worry, I wiped all clean and think I did it the right way (already flashed 4 other phones, but samsungs').
But I seem to have missed something as I got in a neverending bootanimation (white background with green htc logo).
I know, that you sometimes have to wait a few minutes, but after about 5 minutes or so, I thought I was stuck on boot loop.
So I rebooted, flashed it again and rebooted and nothing changed.
I then read about the boot.img... So I extracted the boot.img and did a full wipe, then installed it, after that the rom and then (just to be safe) three times again the boot.img.
Rebooted and now I got the reboot loop (white background with green logo, then black, then white background again and so on)
I tried everything and as I was about to give up, read about the final solution: the RUU or PH39IMG.zip.
Now the problem is: I cant get either of them to work. At all. When trying to flash the RUU (with bootloader relocked), the programm says: "ERROR 170: No device connected".
I read about some other people having the same problem, so I tried the solution given to them: go to the first screen, then to your temp data, extract the rom.zip, rename it and flash that one, via putting it on the external sd and booting into bootloader.
Didn't work either: Wrong CID. Same for all RUUs I could find even closely related to my phone.
As I couldn't find the real correct RUU, I tried to cheat and use the goldcard to overgo the cid-problem.
Because I couldn't boot up the Velocity 4G I tried to make one with my own Galaxy S2, which worked.
Seems to be the wrong way, since it's the wrong CID anyways, when trying to install the PH39IMG (still all RUUs say ERROR 170).
I might need to mention I didn't do the S-OFF thing, as I didn#t want to mess with the hardware... Is that necessary for my problem to getting fixed?
Maybe I just need the one correct RUU for my model, but I can't find it anywhere!
please help me somebody, as I feel very guilty because of wrecking my girlfriends phone! :crying:
any help is appreciated!!!
greetings
deweini said:
Hello all,
I'm sorry to interrupt you all, but this is rather important!
I tried to root my girlfriends Velocity 4G which she got with her contract with A1 (austrian carrier).
I already flashed a One S and knew of the complications a root for HTC could bring.
So I tried to get everything together before flashing and then I did it...
Got the bootloader unlocked, installed TWRP and flashed sun_dreams rom.
Don't worry, I wiped all clean and think I did it the right way (already flashed 4 other phones, but samsungs').
But I seem to have missed something as I got in a neverending bootanimation (white background with green htc logo).
I know, that you sometimes have to wait a few minutes, but after about 5 minutes or so, I thought I was stuck on boot loop.
So I rebooted, flashed it again and rebooted and nothing changed.
I then read about the boot.img... So I extracted the boot.img and did a full wipe, then installed it, after that the rom and then (just to be safe) three times again the boot.img.
Rebooted and now I got the reboot loop (white background with green logo, then black, then white background again and so on)
I tried everything and as I was about to give up, read about the final solution: the RUU or PH39IMG.zip.
Now the problem is: I cant get either of them to work. At all. When trying to flash the RUU (with bootloader relocked), the programm says: "ERROR 170: No device connected".
I read about some other people having the same problem, so I tried the solution given to them: go to the first screen, then to your temp data, extract the rom.zip, rename it and flash that one, via putting it on the external sd and booting into bootloader.
Didn't work either: Wrong CID. Same for all RUUs I could find even closely related to my phone.
As I couldn't find the real correct RUU, I tried to cheat and use the goldcard to overgo the cid-problem.
Because I couldn't boot up the Velocity 4G I tried to make one with my own Galaxy S2, which worked.
Seems to be the wrong way, since it's the wrong CID anyways, when trying to install the PH39IMG (still all RUUs say ERROR 170).
I might need to mention I didn't do the S-OFF thing, as I didn#t want to mess with the hardware... Is that necessary for my problem to getting fixed?
Maybe I just need the one correct RUU for my model, but I can't find it anywhere!
please help me somebody, as I feel very guilty because of wrecking my girlfriends phone! :crying:
any help is appreciated!!!
greetings
Click to expand...
Click to collapse
OK... Vodafone is still on gingerbread...
Soooo... You need a gingerbread ROM... And a gingerbread boot.img... Then get it to boot...
After that I would s-off, super cid, get to ICS hboot... Then flash the ROM of your choice
rignfool said:
OK... Vodafone is still on gingerbread...
Soooo... You need a gingerbread ROM... And a gingerbread boot.img... Then get it to boot...
After that I would s-off, super cid, get to ICS hboot... Then flash the ROM of your choice
Click to expand...
Click to collapse
So far so good... but where do I get it from?
I have this one:
RUU_HOLIDAY_SENSE3_5_Vodafone_DE_2.38.162.1_Radio_3.02.4740.09_34.20.701040.19_release_241518_signed
But this one won't work either...
What complicates the search, is that this phone goes by so many different names (vivid, velocity, holiday, raider, etc...)
Should I post a getvar all?
Concerning your further steps: I would be very happy to get it to run at all, maybe then think of reflashing something.
I don't know if I manage that s-off thing and I don't want to hard brick it and give it the final punch...
anyways, thanks for the fast response!
Can you get the ph39img from it?
Sent from my Vivid 4G using Tapatalk
rignfool said:
Can you get the ph39img from it?
Sent from my Vivid 4G using Tapatalk
Click to expand...
Click to collapse
I already did that with all the RUUs I found, but none worked...
EDIT: so I tried a solution offered by another poster in another forum which said to install CM10 on a clean wipe.
did that and it booted in the cm boot screen and loads the "first install wizard"... well, at least to the language selection screen, then it freezes and reboots again.
but at least we bought us some time at the start.
deweini said:
I already did that with all the RUUs I found, but none worked...
EDIT: so I tried a solution offered by another poster in another forum which said to install CM10 on a clean wipe.
did that and it booted in the cm boot screen and loads the "first install wizard"... well, at least to the language selection screen, then it freezes and reboots again.
but at least we bought us some time at the start.
Click to expand...
Click to collapse
Its because of a wrong hboot...
It will happen with all of the ICS+ ROMs...
I wish you hadn't relocked your bootloader...
Can you reunlock...
Iirc there is a thread with hboot updated... Maybe try that... Or download the Wcxroot thingy and flash the juopenut hboot...
Sent from my Vivid 4G using Tapatalk
rignfool said:
Its because of a wrong hboot...
It will happen with all of the ICS+ ROMs...
I wish you hadn't relocked your bootloader...
Can you reunlock...
Iirc there is a thread with hboot updated... Maybe try that... Or download the Wcxroot thingy and flash the juopenut hboot...
Sent from my Vivid 4G using Tapatalk
Click to expand...
Click to collapse
so, you're basically saying i might be able to get it to work without any RUUs or PH39IMGs?
Wow, that would be good news at last.
I already reunlocked before i flashed the CM10 rom and i didn't forget to flash the boot.img afterwards and even went back again to recovery to wipe cache and dalvik and fixed permissions.
Which one should i try?
thank you for your help!! :good:
is updating the hboot even possible without s-off?
so it seems i have to obtain s-off to flash anything else than stock rom...
as far as i read you have to be on stock ruu to obtain s-off, is that correct?
because that would be bad, as i don't have the stock ruu for my phone.
is it possible to acquire s-off without being on stock rom and would it be possible with the state my phone is in?
deweini said:
is updating the hboot even possible without s-off?
so it seems i have to obtain s-off to flash anything else than stock rom...
as far as i read you have to be on stock ruu to obtain s-off, is that correct?
because that would be bad, as i don't have the stock ruu for my phone.
is it possible to acquire s-off without being on stock rom and would it be possible with the state my phone is in?
Click to expand...
Click to collapse
I think homeslice s-offed his phone on a non stock ROM...
Sent from my Vivid 4G using Tapatalk
rignfool said:
I think homeslice s-offed his phone on a non stock ROM...
Sent from my Vivid 4G using Tapatalk
Click to expand...
Click to collapse
i already wrote a pm. do you have any ideas left? maybe try and install a gb rom and then try that ruu again?
ps: i did manage to start the ruu.exe (by reinstalling the htc sync) and it stopped with the error 131. installing the rom.zip (or PH39IMG.zip) still won't work as it says customer id check failed...
deweini said:
i already wrote a pm. do you have any ideas left? maybe try and install a gb rom and then try that ruu again?
ps: i did manage to start the ruu.exe (by reinstalling the htc sync) and it stopped with the error 131. installing the rom.zip (or PH39IMG.zip) still won't work as it says customer id check failed...
Click to expand...
Click to collapse
Okay, so I did manage to fix it, as it seems... :laugh:
This is what I did:
1. reunlocked bootloader
2. installed TWRP and booted into recovery
3. mounted the internal SD as mass storage
4. copied over VJRaiders GB rom
5. did a full wipe
6. installed VJRaiders rom
7. rebooted into bootloader
8. fastboot flashed the kernel found in the rom thread (twice)
9. rebooted and it worked...
I don't know how and why, but the problem seemed to be that I always tried to flash non-GB roms. As simple as that.
I have no idea why the RUU and PH39IMG didn't work tho...
Well. I won't touch that thing for a looong time, as it works and I had enough problems getting there!
The reason that you had problems with ics and upward roms is because your phone still has the gb hboot. This is because boss never released the ics update. To install ics roms you need the ics hboot.
Sent from my HTC One
WildfireDEV said:
The reason that you had problems with ics and upward roms is because your phone still has the gb hboot. This is because boss never released the ics update. To install ics roms you need the ics hboot.
Sent from my HTC One
Click to expand...
Click to collapse
Which I'm only able to attain with s-off, am I right?
Correct, I believe. If you didn't get an official update to ICS, you'll have to S-Off. It's honestly not as bad as it sounds, I did mine with some speaker wire...probably the worst part of it is getting the cover off of the section where you have to ground out the point. Just take your time, and make sure you're in a well lit area, with a little bit of working space, and you'll be fine.
well, the problem is, that we are not longer on a stock rom and can't seem to flash the original ruu, as we don't find it anywhere...
and as far as i know it is not recommended or possible to go s-off without being on stock rom!?
AFAIK it is UNTESTED... Not impossible
Sent from my Vivid 4G using Tapatalk
If this is anything like other HTC devices, i'd say your best shot if you're willing to try an untested idea, would be to give it a shot with a sense rom, as they tend to be (under the hood anyways) a lot closer to stock than non sense roms.