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.
Related
Ok so I think I've bricked my Nexus One. Everything was working perfect until I re-rooted it (to have SetCPU to work). I am now stuck at the loading animation screen (Google Nexus One "X"). It just keeps going and going and going. I've even tried loading my Nandroid backup and still does the same and won't work. Also I've wiped to factory default settings and tried to reinstall Modaco's 1.3 rom.
Someone please help me out...
Flash bacon add-on on top
bye!
So reinstall Modaco's 1.3, then install Bacon Add-On, and then reboot?
Yep That's the solution for some users
ok cool I'll give it a shot right now... I really appreciate it
ok at this moment it's still stuck on the animated screen... now I really don't know what to do...
Try flashing the stock rom
if u have the sdk installed, the run ddms. power on the phone usb connected to pc and see the log in ddms, paste-bin here
I have no idea on how to do that... I'm pretty much stuck at this point
try not flashing Modaco's Rom,
just flash CM's bacon
i think there is a confusion because Modaco's rom is in the rooting threat (made me believe you HAVE to use Modaco's superboot and then go to CM's bacon.
reality is you don't need modaco's superboot. after bootloader unlocking and flashing Amon Ra's recovery image you can go straight flashing CM's Makin' Bacon.
It seems people have been successful with CM's
maybe just go straight back to the start, check that bootloader is unlocked, flash amon ra's recovery, then flash Makin' Bacon
good luck
shmigao said:
try not flashing Modaco's Rom,
just flash CM's bacon
i think there is a confusion because Modaco's rom is in the rooting threat (made me believe you HAVE to use Modaco's superboot and then go to CM's bacon.
reality is you don't need modaco's superboot. after bootloader unlocking and flashing Amon Ra's recovery image you can go straight flashing CM's Makin' Bacon.
It seems people have been successful with CM's
maybe just go straight back to the start, check that bootloader is unlocked, flash amon ra's recovery, then flash Makin' Bacon
good luck
Click to expand...
Click to collapse
WOW, I really appreciate it and that just worked for me. Thank you to the both of you guys!
if you can get into bootloader mode (this is the lowest level mode you can boot into), you can not brick. Even more so if you can get into recovery (which is usually always possible if you can get to bootloader)
Good you found a way to get out of your situation.
Like i said in Android 101, you CAN NOT brick the phone unless you are updating SPL and Radio. All other stuff is just a minor inconvenience.
risterdid said:
WOW, I really appreciate it and that just worked for me. Thank you to the both of you guys!
Click to expand...
Click to collapse
haha, i am glad it worked! I don't even have my Nexus One in my hands (my biz trip to the States has been delayed again ), but i spend the waiting time doing my research... it's a bit like the Holiday Season, just that the gift giving day gets pushed out further and further...
glad it worked and it confirmed my research - so i can go at it with ease once i can
This is good news. OP, you should update your thread titled with the prefix [SOLVED].
ahh how'd I miss that 101 sticky... thanks for the heads up again guys.
Edited title =)
Am I bricked?
Ok, my issue is that I cant boot into bootloader or recovery (I tried booting with rollerball pushed in, booting with down volume, abd-mac reboot recovery, abd-mac reboot bootloader) and it just goes right into my OS which is crashing every few minutes, and my radio wont work. Any suggestions? If I am bricked, can I send it to HTC even though its rooted and bootloader is unlocked? I dont care if I have to pay for fixing it.
DrBlast33 said:
Ok, my issue is that I cant boot into bootloader or recovery (I tried booting with rollerball pushed in, booting with down volume, abd-mac reboot recovery, abd-mac reboot bootloader) and it just goes right into my OS which is crashing every few minutes, and my radio wont work. Any suggestions? If I am bricked, can I send it to HTC even though its rooted and bootloader is unlocked? I dont care if I have to pay for fixing it.
Click to expand...
Click to collapse
First of all, if your phone boots at all, it isn't bricked. A brick is a paperweight - it doesn't do anything. Second, this thread of 5 months old. Third, people have talked A TON about sending phones in to HTC with an unlocked bootloader, do a bit of searching.
And finally, it is very peculiar that your phone doesn't boot into bootloader or recovery. Try plugging your phone into your computer, opening your command prompt, navigate to your adb install direction, typing "adb wait-for-device reboot bootloader", and turning on your phone. Best of luck!
People should be banned for bumping 5 month old threads with posts not even related to the OP's post. Ridiculous.
@rcxquake: thanks for your suggestion. That didnt work, it just rebooted the OS. Ill keep searching for my solution and how to send to HTC if I cant find the solution.
@GldRush98: Sorry for ruining your day. I put in a google search for what I was experiencing and this was one of the top result of anyone remotely close to my issue. Yes, this is an old post, but maybe someone had this issue months ago, and had a solution I wasnt aware of.
And like I said, I found this post, although not exactly my same issue, was as related as Ive been able to find. I didn't find it so ridiculous.
If you can find my same issue on another post, then please help by pointing me to it so I can find my solution. I didn't mean to cause any issues.
Thanks
I for one am glad you posted. I don't know whether this is a solution for you or not, but I'm sometimes only able to get to the bootloader after I've had the phone off the charges, with the battery out, for some time. It varies for me between a few minutes and many minutes. It is hard to say because when I try and it doesn't work, I don't know if I've reset the time by having tried.
Anyhow, I found this thread because I'm having trouble with an N1, and one of the earlier posts may help me. Thanks for bumping the thread for my benefit.
There seems to be an influx of posts with users asking for help after bricking/semi-bricking their phone after upgrading using the ph39img method. Upgrading using the PH39IMG.zip is risky if you don't THOROUGHLY understand the steps, it is a bit complex even for those of us who have flashed numerous times when it was the gingerbread. It is hard to know what you are doing even if you are an expert at flashing roms because it completely different and new process.
With that being said, USE THE RUU TO UPGRADE!
Do not use the PH39IMG to upgrade just because it takes too long to download the RUU file, because there is a HIGH chance that you WILL brick your phone if you accidentally miss just one step in the process.
So do yourself a favor, be smart and use the RUU.
Official RUU from AT&T
-make sure to back up your files (that includes internal storage)-
Please forgive me for asking but can you point me to the RUU?
Also, I am unlocked & rooted...can you give me (or point me to) the "dummies simple guide" to flashing with the RUU?
I have flashed my older Captivate many times and many previous WM6 phones but not up on the HTC and Vivid yet... I apologize!
Sent from my HTC Vivid using Tapatalk
We can probably close this thread...lol. Good intentions, bad timing.
mark72501 said:
Please forgive me for asking but can you point me to the RUU?
Also, I am unlocked & rooted...can you give me (or point me to) the "dummies simple guide" to flashing with the RUU?
I have flashed my older Captivate many times and many previous WM6 phones but not up on the HTC and Vivid yet... I apologize!
Sent from my HTC Vivid using Tapatalk
Click to expand...
Click to collapse
No problem, this post was intended to get you to use the RUU if you are not familiar with the HBOOT upgrade process.
http://forum.xda-developers.com/showthread.php?t=1338919
To run the RUU, you must relock your bootloader
anthromatt said:
We can probably close this thread...lol. Good intentions, bad timing.
Click to expand...
Click to collapse
Yeah, it looks like if you are on stock, you can now update through phone AT&T software update in settings. Hopefully it's a much smoother upgrading process.
dizzyraider said:
Yeah, it looks like if you are on stock, you can now update through phone AT&T software update in settings. Hopefully it's a much smoother upgrading process.
Click to expand...
Click to collapse
I am on stock ROM that came on the phone, just unlocked and rooted and most of the bloat gone...I thought I read somewhere a couple of days ago that it wouldn't give it to me OTA unless I re-locked. Is this correct?
I guess I could try it but it's middle of the day, I'm at work...can't mess with it right now so just checking!
Thank you
Correct...
mark72501 said:
I am on stock ROM that came on the phone, just unlocked and rooted and most of the bloat gone...I thought I read somewhere a couple of days ago that it wouldn't give it to me OTA unless I re-locked. Is this correct?
I guess I could try it but it's middle of the day, I'm at work...can't mess with it right now so just checking!
Thank you
Click to expand...
Click to collapse
I believe you will need to Re-Lock. I'm guessing that OTA and just running the EXE will result in the same thing if you are unlocked. No Go.
This probably isn't the proper thread to post this in but it is somewhat related.
Got home tonight and wanted to do this. Ran across the below link and it sounded detailed and easy enough...so...I decided to try it.
Well, I got down to step 15 and after that it automatically rebooted or something and it seems from there I can't do step 16, 17 and on. I can get to HBOOT but it never asked to update the PH39IMG.
What do I need to do now? Now if I try to boot the phone up I get stuck at the HTC splash screen.
Oops...forgot link: http://www.androidauthority.com/vivid-4g-pre-rooted-ics-htc-sense-3-6-63538/
Thanks!
mark72501 said:
This probably isn't the proper thread to post this in but it is somewhat related.
Got home tonight and wanted to do this. Ran across the below link and it sounded detailed and easy enough...so...I decided to try it.
Well, I got down to step 15 and after that it automatically rebooted or something and it seems from there I can't do step 16, 17 and on. I can get to HBOOT but it never asked to update the PH39IMG.
What do I need to do now? Now if I try to boot the phone up I get stuck at the HTC splash screen.
Oops...forgot link: http://www.androidauthority.com/vivid-4g-pre-rooted-ics-htc-sense-3-6-63538/
Thanks!
Click to expand...
Click to collapse
Pull out the battery them put it back in (Before starting up again, make sure the file is downloaded correctly in the sd card) Power up by pressing power and vol down, them you can try to update again.
dizzyraider said:
Pull out the battery them put it back in (Before starting up again, make sure the file is downloaded correctly in the sd card) Power up by pressing power and vol down, them you can try to update again.
Click to expand...
Click to collapse
Do you mean the PH39IMG file? And I'm not sure how to check that since I can't connect the phone to the computer after booted and see it as a drive. All I can get to is fastboot.
I did notice that on the site with the directions it says the PH39IMG file is 35.6MB and I d/l'd it twice and it shows 35.5MB on my computer. Not sure if that means anything or not.
Is there a way to see what's on the SD card without the phone booting?
mark72501 said:
Do you mean the PH39IMG file? And I'm not sure how to check that since I can't connect the phone to the computer after booted and see it as a drive. All I can get to is fastboot.
I did notice that on the site with the directions it says the PH39IMG file is 35.6MB and I d/l'd it twice and it shows 35.5MB on my computer. Not sure if that means anything or not.
Is there a way to see what's on the SD card without the phone booting?
Click to expand...
Click to collapse
Yes, take out the card and use an external sd card reader. That's how i would do it
dizzyraider said:
Yes, take out the card and use an external sd card reader. That's how i would do it
Click to expand...
Click to collapse
Ah...that would be the, or one of the, problem then...I put it on the phone. I'm accustomed to that from the phone I came from where the phone memory was often referred to as the SD card (because it was one it just couldn't be removed). I have no SD card in my phone that is removable. Yeah......
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.
Im sending my phone back to HTC for repair.
I have two questions...
Would they look at the CID?
Can I change it back to my original CID if I've already installed a RUU that doesn't allow my CID? (sounds like a dumb question)
stanny2k said:
Im sending my phone back to HTC for repair.
I have two questions...
Would they look at the CID?
Can I change it back to my original CID if I've already installed a RUU that doesn't allow my CID? (sounds like a dumb question)
Click to expand...
Click to collapse
I read your other post http://forum.xda-developers.com/showthread.php?t=2599739 and probably a lot of others too, no answer because I have none.
So here's a small summary:
1- you're S-ON again, so changing CID cannot be done
2- you have a .401. software version which means it cannot be CID H3G, so HTC__001 is correct for that software version
3- you've removed TAMPERED and set to LOCKED (not relocked)
4- I don't know how the service center will react, and whether they would bother checking CID, etc. (from what I've seen the UK centers are quite lenient)
If you really want to go back fully to your carrier version, and "out of the box", you can take a look at my guide: http://forum.xda-developers.com/showthread.php?t=2541082
but that means starting the procedure all the way from the start again, ie
-- unlocking (and you're gonna have to do that with HTCdev)
-- s-off using rumrunner.
then follow the rest of the guide.
Don't know if it's worth the hassle; but if you need help with it, post back there.
cheers
nkk71 said:
I read your other post http://forum.xda-developers.com/showthread.php?t=2599739 and probably a lot of others too, no answer because I have none.
So here's a small summary:
1- you're S-ON again, so changing CID cannot be done
2- you have a .401. software version which means it cannot be CID H3G, so HTC__001 is correct for that software version
3- you've removed TAMPERED and set to LOCKED (not relocked)
4- I don't know how the service center will react, and whether they would bother checking CID, etc. (from what I've seen the UK centers are quite lenient)
If you really want to go back fully to your carrier version, and "out of the box", you can take a look at my guide: http://forum.xda-developers.com/showthread.php?t=2541082
but that means starting the procedure all the way from the start again, ie
-- unlocking (and you're gonna have to do that with HTCdev)
-- s-off using rumrunner.
then follow the rest of the guide.
Don't know if it's worth the hassle; but if you need help with it, post back there.
cheers
Click to expand...
Click to collapse
Thanks for taking the time in responding mate. The issue I have is that I can't get a stock RUU for my H3G CID... It just doesn't seem to exist anywhere... I think a few other people are asking the same question... Which is why I've had to change my CID to HTC__001..
stanny2k said:
Thanks for taking the time in responding mate. The issue I have is that I can't get a stock RUU for my H3G CID... It just doesn't seem to exist anywhere... I think a few other people are asking the same question... Which is why I've had to change my CID to HTC__001..
Click to expand...
Click to collapse
Well if you checked my guide, you'd see that method 3 (CWM Backup), works, and there is a H3G__001 backup out there; as a matter of fact, the example I used was for H3G__001.
nkk71 said:
Well if you checked my guide, you'd see that method 3 (CWM Backup), works, and there is a H3G__001 backup out there; as a matter of fact, the example I used was for H3G__001.
Click to expand...
Click to collapse
In that case, I take that back I'm going to follow your guide again tonight.
The last thing I want is for HTC to say No, they cant do my repair cause I've messed about with my phone...
Oh, and have a "thanks"
stanny2k said:
In that case, I take that back I'm going to follow your guide again tonight.
The last thing I want is for HTC to say No, they cant do my repair cause I've messed about with my phone...
Oh, and have a "thanks"
Click to expand...
Click to collapse
I'm going to recommend this CWM recovery, just cause the newer versions are taking close to an hour to backup/restore:
recovery-clockwork-touch-6.0.3.2-m7--v2.img 7.2 MB
https://mega.co.nz/#!6E8RiIrQ!GF5LyhmEdg8OQJxuQVVjwSxBljxhW7xsZAHLzjVACsc
MD: 1c6afb14db3f305b0ad7d85d5af80bef
Also, please follow the instruction properly, no jumping, skipping or adding steps
The only slightly tricky part (as mentioned), is in Step 6, where when the phone reboots to "stock recovery" it could hang somewhere between 25% to 50%, and you have to manually reboot, and (possibly) again towards the end, and you have to reboot manually again.
This is a known side effect because stock recovery is not exactly the same as your version, but it's not a problem.
After the FIRST (and only the FIRST) OTA update, should you go back S-On, because hboot 1.55 has a patch that will force TAMPERED to come back if you go from s-off to s-on.
NB: after the first OTA, you're phone will be 100% stock.
If you have any trouble (hopefully not), post back in my thread, as I get instant notifications on that (and if i'm still awake, i'm 2 hours ahead), and I'll try to help out.
Cheers.
---------- Post added at 06:50 PM ---------- Previous post was at 06:48 PM ----------
stanny2k said:
Oh, and have a "thanks"
Click to expand...
Click to collapse
Thanks, I like those
nkk71 said:
I'm going to recommend this CWM recovery, just cause the newer versions are taking close to an hour to backup/restore:
recovery-clockwork-touch-6.0.3.2-m7--v2.img 7.2 MB
https://mega.co.nz/#!6E8RiIrQ!GF5LyhmEdg8OQJxuQVVjwSxBljxhW7xsZAHLzjVACsc
MD: 1c6afb14db3f305b0ad7d85d5af80bef
Click to expand...
Click to collapse
Ok, I'll grab this!
nkk71 said:
Also, please follow the instruction properly, no jumping, skipping or adding steps
Click to expand...
Click to collapse
Will do! Don't worry, word for word!
nkk71 said:
The only slightly tricky part (as mentioned), is in Step 6, where when the phone reboots to "stock recovery" it could hang somewhere between 25% to 50%, and you have to manually reboot, and (possibly) again towards the end, and you have to reboot manually again.
This is a known side effect because stock recovery is not exactly the same as your version, but it's not a problem.
Click to expand...
Click to collapse
Noted.
nkk71 said:
After the FIRST (and only the FIRST) OTA update, should you go back S-On, because hboot 1.55 has a patch that will force TAMPERED to come back if you go from s-off to s-on.
NB: after the first OTA, you're phone will be 100% stock.
Click to expand...
Click to collapse
When you say "should you go back S-On" do I let the first OTA update install, then manually go back to S-ON, then let the other updates install once I've got S-ON back?
nkk71 said:
If you have any trouble (hopefully not), post back in my thread, as I get instant notifications on that (and if i'm still awake, i'm 2 hours ahead), and I'll try to help out.
Cheers.
Click to expand...
Click to collapse
Appreciate it, thank you
stanny2k said:
When you say "should you go back S-On" do I let the first OTA update install, then manually go back to S-ON, then let the other updates install once I've got S-ON back?
Click to expand...
Click to collapse
yep, exactly, after the 1st OTA, your phone will be 100% "out-of-the-box"; once the OTA updates successfully it will mean
1- your entire firmware was updated (hboot, recovery, kernel, radio, etc)
2- your ROM will also be updated, proving everything is 100%
otherwise, the OTA would not be able to complete.
Now due to a patch in later hboots (in particular 1.55 as far as i know), going from s-off to s-on, will (after a few reboots) result in "tamper detected - rebooting" and TAMPERED is back.
so in summary, if you really need to go S-On, you do so after first successful OTA (using the command mentioned in my guide), and then you can take any OTAs you like.
hope that makes sense
Perfect sense!
I'll have a bash at this tonight! Thanks a lot
Well, that was an eventful evening
Followed your guide to the letter. Everything went ok apart from a few things..
Pushing files via adb whilst in recovery causes me no end of issues... I kept getting no device found, luckily I was able to boot up and transfer the files manually.
I then flashed the wrong stock recovery (recovery 1.28.401.7.img) so I had to unlock the bootloader again to flash a different one, thankfully the one I did flash (recovery 2.24.771.3 - TRE.img), which matched the first OTA update, everything installed fine after that
Thanks a lot mate. I'll happy to send my device away for repair with no worries now.
Regards, Ryan
stanny2k said:
Well, that was an eventful evening
Followed your guide to the letter. Everything went ok apart from a few things..
Pushing files via adb whilst in recovery causes me no end of issues... I kept getting no device found, luckily I was able to boot up and transfer the files manually.
I then flashed the wrong stock recovery (recovery 1.28.401.7.img) so I had to unlock the bootloader again to flash a different one, thankfully the one I did flash (recovery 2.24.771.3 - TRE.img), which matched the first OTA update, everything installed fine after that
Thanks a lot mate. I'll happy to send my device away for repair with no worries now.
Regards, Ryan
Click to expand...
Click to collapse
Sorry to hear you had some troubles , are you on Windows 8 or 8.1, is that why adb wasn't working.
Also have a two questions about stock recovery you used,
1- when you used 1.28.401.7 the OTA didnt work, or you didnt try?
2- when you used 2.24.771.3 did the OTA hang at any point, or did it reboot (twice, I believe), correctly and by itself?
would be nice if you could give me some more info, it would probably be helpful to others too.
Thanks
nkk71 said:
Sorry to hear you had some troubles , are you on Windows 8 or 8.1, is that why adb wasn't working.
Also have a two questions about stock recovery you used,
1- when you used 1.28.401.7 the OTA didnt work, or you didnt try?
2- when you used 2.24.771.3 did the OTA hang at any point, or did it reboot (twice, I believe), correctly and by itself?
would be nice if you could give me some more info, it would probably be helpful to others too.
Thanks
Click to expand...
Click to collapse
I'm on Windows 7 mate. It just seemed really intermittent. May have been my USB lead/port.
1.28.401.7 - Downloaded the OTA fine, when the phone rebooted to install, it just hung on the "Entering Recovery" screen... Didnt get past that.
2.24.771.3 - Downloaded the OTA fine, booted into Recovery fine, hung on the first quarter (had to manually reboot) after that it installed straight away.
Hope this helps.
stanny2k said:
I'm on Windows 7 mate. It just seemed really intermittent. May have been my USB lead/port.
1.28.401.7 - Downloaded the OTA fine, when the phone rebooted to install, it just hung on the "Entering Recovery" screen... Didnt get past that.
2.24.771.3 - Downloaded the OTA fine, booted into Recovery fine, hung on the first quarter (had to manually reboot) after that it installed straight away.
Hope this helps.
Click to expand...
Click to collapse
hmm: it just hung on the "Entering Recovery" screenit just hung on the "Entering Recovery" screen
did you do a "fastboot erase cache", after flashing it? that's usually the only reason it could get stuck (or perhaps a corrupt download, did you check MD5; i've had some issues downloading from dev-host sometimes).
But thanks anyway, glad all worked out, and hope you get your device back soon
cheers.
nkk71 said:
hmm: it just hung on the "Entering Recovery" screenit just hung on the "Entering Recovery" screen
did you do a "fastboot erase cache", after flashing it? that's usually the only reason it could get stuck (or perhaps a corrupt download, did you check MD5; i've had some issues downloading from dev-host sometimes).
But thanks anyway, glad all worked out, and hope you get your device back soon
cheers.
Click to expand...
Click to collapse
Yup, I did fastboot erase cache before and after flashing it, both were successful as well. I didnt check the MD5, I just installed it after I downloaded it.. it was midnight by the time I got that far! I was tired!
Yeah and thanks a lot for your help mate. Really appreciate it.
I'll let you know the outcome with HTC Hopefully they find nothing untoward!
stanny2k said:
I'm on Windows 7 mate. It just seemed really intermittent. May have been my USB lead/port.
1.28.401.7 - Downloaded the OTA fine, when the phone rebooted to install, it just hung on the "Entering Recovery" screen... Didnt get past that.
2.24.771.3 - Downloaded the OTA fine, booted into Recovery fine, hung on the first quarter (had to manually reboot) after that it installed straight away.
Hope this helps.
Click to expand...
Click to collapse
Sorry, one last question, when you manually rebooted, did you have to keep holding VOLDOWN during boot-up, or did it enter stock recovery by itself
nkk71 said:
Sorry, one last question, when you manually rebooted, did you have to keep holding VOLDOWN during boot-up, or did it enter stock recovery by itself
Click to expand...
Click to collapse
I'm not sure if it enters recovery by itself as I just followed your guide of holding VOLDOWN
My thumbs were killing me by the end of the night!
stanny2k said:
I'm not sure if it enters recovery by itself as I just followed your guide of holding VOLDOWN
My thumbs were killing me by the end of the night!
Click to expand...
Click to collapse
finger gymnastics :laugh:
stanny2k said:
Well, that was an eventful evening
Pushing files via adb whilst in recovery causes me no end of issues... I kept getting no device found, luckily I was able to boot up and transfer the files manually.
Click to expand...
Click to collapse
Looks like I have to express my apologies on that, I believe I found the problem; the "quicker way"
I really should avoid those shortcuts, until I've tested them 100% (or at least 98%).... I'll let you know what the problem was / is when i update the guide, and sorry again for the headache!!
nkk71 said:
Looks like I have to express my apologies on that, I believe I found the problem; the "quicker way"
I really should avoid those shortcuts, until I've tested them 100% (or at least 98%).... I'll let you know what the problem was / is when i update the guide, and sorry again for the headache!!
Click to expand...
Click to collapse
:laugh: thats alright mate. No issues.
Let me know once you've updated the guide and I'll take a look at it
stanny2k said:
:laugh: thats alright mate. No issues.
Let me know once you've updated the guide and I'll take a look at it
Click to expand...
Click to collapse
problem is with the CWM i recommended, works just fine when flashed, but when using "fastboot boot CWM.img" looks like 6.0.3.2 doesnt work properly with adb, 6.0.4.5 on the other hand works with "fastboot boot"
I'll update my guide with some more "visuals" whenever I get a chance....
I'm not sure if I'm posting this in the right thread or not, and I do hope that I'm not wasting anyone's time. However, I have searched and searched and have gone through an insane amount of trial and error to no avail. I have just recently purchased an HTC One M8 for Sprint and the lcd underneath the glass got cracked when it fell and so, I assumed that I'd take advantage of the Advantage program, and all seemed well, except I had previously unlocked the bootloader using htcdev and have been running stock rooted with TWRP recovery. I've tried so many methods of getting back to stock, at least enough to argue with HTC into fixing my screen, since it has no bearing on hardware. I'm now s-off with a relocked bootloader and root, and I'm lost. I've trying to use RUU files to recover my device, but everytime, I get a bad zip file. And when I tried flashing the firmware anyways using adb it looked exactly the same, in fact the only thing different is that TWRP was gone and booting into recovery simply got me a picture of a phone with an exclamation point in a red triangle. I don't know if they're corrupted or if I'm just dumb. I apologize for any inconvenience. Please help, I've just spent 650 dollars on this phone and I'm out of money. Thank you for your time and any suggestions you may give, I sincerely appreciate it.
MrCeroSombra said:
I'm not sure if I'm posting this in the right thread or not, and I do hope that I'm not wasting anyone's time. However, I have searched and searched and have gone through an insane amount of trial and error to no avail. I have just recently purchased an HTC One M8 for Sprint and the lcd underneath the glass got cracked when it fell and so, I assumed that I'd take advantage of the Advantage program, and all seemed well, except I had previously unlocked the bootloader using htcdev and have been running stock rooted with TWRP recovery. I've tried so many methods of getting back to stock, at least enough to argue with HTC into fixing my screen, since it has no bearing on hardware. I'm now s-off with a relocked bootloader and root, and I'm lost. I've trying to use RUU files to recover my device, but everytime, I get a bad zip file. And when I tried flashing the firmware anyways using adb it looked exactly the same, in fact the only thing different is that TWRP was gone and booting into recovery simply got me a picture of a phone with an exclamation point in a red triangle. I don't know if they're corrupted or if I'm just dumb. I apologize for any inconvenience. Please help, I've just spent 650 dollars on this phone and I'm out of money. Thank you for your time and any suggestions you may give, I sincerely appreciate it.
Click to expand...
Click to collapse
did u do a backup prior to rooting? if yes, restore backup & flash the stock recovery
if no, RUU is your best bet. make sure you're extracting the 0P6BIMG.zip from Sprint_HTC_One_M8_1.54.651.10_RUU.zip using 7zip, to your ext sd card, then boot into bootloader
u can also use the older Sprint_HTC_One_M8_1.54.651.8_RUU.zip which has a exe to flash from pc
Thank you. When I attempted flashing the stock recovery, I'd gotten the red exclcmation screen. And when I try using 7 zip on the actual 0P6BIMG.zip it says zip is invalid, is this just normal?
MrCeroSombra said:
Thank you. When I attempted flashing the stock recovery, I'd gotten the red exclcmation screen. And when I try using 7 zip on the actual 0P6BIMG.zip it says zip is invalid, is this just normal?
Click to expand...
Click to collapse
red exclamation screen is stock recovery....no, you can't open 0P6BIMG.zip, it's encrypted...just copy to ext sd
Wait. So flashing stock recovery did work then? I feel, really foolish if thats the case. I was only wondering about it because I did not see any text up top. But, thank you so much! If that's it then I'm done. Now to send it off and convince htc to fix it. Thank you
MrCeroSombra said:
Wait. So flashing stock recovery did work then? I feel, really foolish if thats the case. I was only wondering about it because I did not see any text up top. But, thank you so much! If that's it then I'm done. Now to send it off and convince htc to fix it. Thank you
Click to expand...
Click to collapse
yeah, your only indication of stock recovery is the red exclamation
MrCeroSombra said:
I'm not sure if I'm posting this in the right thread or not, and I do hope that I'm not wasting anyone's time. However, I have searched and searched and have gone through an insane amount of trial and error to no avail. I have just recently purchased an HTC One M8 for Sprint and the lcd underneath the glass got cracked when it fell and so, I assumed that I'd take advantage of the Advantage program, and all seemed well, except I had previously unlocked the bootloader using htcdev and have been running stock rooted with TWRP recovery. I've tried so many methods of getting back to stock, at least enough to argue with HTC into fixing my screen, since it has no bearing on hardware. I'm now s-off with a relocked bootloader and root, and I'm lost. I've trying to use RUU files to recover my device, but everytime, I get a bad zip file. And when I tried flashing the firmware anyways using adb it looked exactly the same, in fact the only thing different is that TWRP was gone and booting into recovery simply got me a picture of a phone with an exclamation point in a red triangle. I don't know if they're corrupted or if I'm just dumb. I apologize for any inconvenience. Please help, I've just spent 650 dollars on this phone and I'm out of money. Thank you for your time and any suggestions you may give, I sincerely appreciate it.
Click to expand...
Click to collapse
When you use HTCDEV you void the warranty and they'll most likely charge you to fix it since you literally gave them the info about your phone to unlock the bootloader. Had a previous experience like this.