Folks, 7 rooted devices over last 7 years, and I have usually been able to find a solution without having to start a new thread... however, this time... I better get an expert opinion.
Essentially, here are the facts... I was flashing a rom yesterday on my wife's m8, and the wifi would not work. I thought about it, and then figured it likely was that I had not updated to latest TWRP prior to flashing. So I restored an old backup, I think the one I made right after rooting, which was 1.5 yrs ago, maybe more. That flashed fine, except after many tries via many methods, I could not get TWRP updated, and in fiddling around, I clicked update software, which downloaded the Verizon kitkat update, and started installing it... that was a mistake, finger too fast notwithstanding... I did not need to do it at all, since I was going to flash something new anyway right after updating recovery. Anyway phone appeared to be stuck, I powered it off (Vol up + Power) and went into bootloader (Vol down while it powered up) to go back into recovery and start over. However, the phone went into a boot loop and has since given me much grief over the past few hours.
Output from getvar all is below. It appears to be missing the OS - which kind of makes sense, if I interrupted it midway through something. The phone neither boots, and refuses to enter recovery - even after flashing recovery using fastboot as well as the Hasoon All in One tool. I also cleared cache. I suspect the recovery is loading, but is hidden behind the boot loop screen (is that possible? not sure, just a guess) because the phone has haptic feedback where the TWRP buttons would be - FWIW.
What should my next steps be? Please advise...
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 0.89.20.0321
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: dottat was here
(bootloader) imei: ###
(bootloader) imei2: Not Support
(bootloader) meid: ###
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: fd3e0448
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.021s
First off you should edit you're post to remove the imei and meid. I don't know how but they say people can do bad things with them so they shouldn't be posted publicly.
cntryby429 said:
First off you should edit you're post to remove the imei and meid. I don't know how but they say people can do bad things with them so they shouldn't be posted publicly.
Click to expand...
Click to collapse
Thanks for the heads up, I have taken those out.
I tried fastboot flash zip rom.zip, that failed with error 'remote: not allowed'
montropistic said:
Thanks for the heads up, I have taken those out.
I tried fastboot flash zip rom.zip, that failed with error 'remote: not allowed'
Click to expand...
Click to collapse
I edited out your serial number. As to the not allow error you must do the following first before attempting to flash.
Fastboot oem rebootRUU
Sent from my Nexus 6 using Tapatalk
dottat said:
I edited out your serial number. As to the not allow error you must do the following first before attempting to flash.
Fastboot oem rebootRUU
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Thanks dottat, yes, I got to the need of being in RUU just prior to your pointing it out, and on doing that, it failed with remote: 24 parsing android-info fail
Trying again with a different ROM now... let us see.
Edit - and it failed with the different ROM zip with the same error, 24: parsing android-info fail.
montropistic said:
Thanks dottat, yes, I got to the need of being in RUU just prior to your pointing it out, and on doing that, it failed with remote: 24 parsing android-info fail
Trying again with a different ROM now... let us see.
Edit - and it failed with the different ROM zip with the same error, 24: parsing android-info fail.
Click to expand...
Click to collapse
could be a bad download of the RUU
andybones said:
could be a bad download of the RUU
Click to expand...
Click to collapse
hmmm... shall i 'Flash factory RUU zip' (in all in one toolkit, or fastboot). Note that I have not done this yet. I will have to go look for the said factory RUU, should be findable. Can I do that while being unlocked/S off, or do I need to adjust any of those first?
montropistic said:
hmmm... shall i 'Flash factory RUU zip' (in all in one toolkit, or fastboot). Note that I have not done this yet. I will have to go look for the said factory RUU, should be findable. Can I do that while being unlocked/S off, or do I need to adjust any of those first?
Click to expand...
Click to collapse
I personally stay away from toolkits, and use fastboot
you can always RUU, with S-OFF you can downgrade if need be. I would fastboot flash the latest RUU. Or you can put on SD-Card and do that method.
http://forum.xda-developers.com/ver...zip-ruu-m8vzw-5-0-1-s-off-onlynewest-t3047103
andybones said:
I personally stay away from toolkits, and use fastboot
you can always RUU, with S-OFF you can downgrade if need be. I would fastboot flash the latest RUU. Or you can put on SD-Card and do that method.
http://forum.xda-developers.com/ver...zip-ruu-m8vzw-5-0-1-s-off-onlynewest-t3047103
Click to expand...
Click to collapse
Yep, grabbing the file from dottats post now, and will flash that. I assume I will do it using option 1 (rename and put it on the root of SD card)... or should I fastboot flash that instead, as you suggested?
montropistic said:
Yep, grabbing the file from dottats post now, and will flash that. I assume I will do it using option 1 (rename and put it on the root of SD card)... or should I fastboot flash that instead, as you suggested?
Click to expand...
Click to collapse
Either way works the same - which one your more comfortable with.
andybones said:
Either way works the same - which one your more comfortable with.
Click to expand...
Click to collapse
OK - so update from my side.
1. Grabbed dottat's RUU file(as pointed out above), checked md5, renamed it, and put it on the root of SD card.
2. Rebooted into bootloader - it saw file, went about updating as per spec - orgasmic.
3. While going through list of updates 2nd cycle, USERDATA - Fail-PU, PG2FS - SPCOSTUM - Fail PU and at the bottom - partition update fail, update fail - press power to reboot - crap.
4. Pressed power - HTC ONE - Vzw Logo - Android is updating - back to orgasmic.
Phone is back to life. Yay!
Going back to bootloader, Phone is still unlocked and S-off. Has the default recovery. I will flash TWRP next.
2 questions - what were the fails, and should i be worried about them?
the issue that got me going down this path still remains. maybe that is a separate topic, but the phone seems to have lost the ability to sense touch in the notification area. I cant pull down notifications, from the portrait mode notifications area. i can pull down in landscape mode, or if i use swipe down in middle of screen in adw.
anyway - will probe into that after TWRP and ROM.
Thanks for all the advice!
Update:
5. Flashed TWRP via fastboot, worked
6. Went into recovery, installed CleanRom v 4.0, worked.
All seems fine. Except that notification pull down issue...
montropistic said:
OK - so update from my side.
1. Grabbed dottat's RUU file(as pointed out above), checked md5, renamed it, and put it on the root of SD card.
2. Rebooted into bootloader - it saw file, went about updating as per spec - orgasmic.
3. While going through list of updates 2nd cycle, USERDATA - Fail-PU, PG2FS - SPCOSTUM - Fail PU and at the bottom - partition update fail, update fail - press power to reboot - crap.
4. Pressed power - HTC ONE - Vzw Logo - Android is updating - back to orgasmic.
Phone is back to life. Yay!
Going back to bootloader, Phone is still unlocked and S-off. Has the default recovery. I will flash TWRP next.
2 questions - what were the fails, and should i be worried about them?
the issue that got me going down this path still remains. maybe that is a separate topic, but the phone seems to have lost the ability to sense touch in the notification area. I cant pull down notifications, from the portrait mode notifications area. i can pull down in landscape mode, or if i use swipe down in middle of screen in adw.
anyway - will probe into that after TWRP and ROM.
Thanks for all the advice!
Update:
5. Flashed TWRP via fastboot, worked
6. Went into recovery, installed CleanRom v 4.0, worked.
All seems fine. Except that notification pull down issue...
Click to expand...
Click to collapse
Run the ruu again. It's not typical to have partition update messages. Bypass is OK but not pu (partition update). Regardless of how it's running right now re-run it.
Sent from my Nexus 6 using Tapatalk
dottat said:
Run the ruu again. It's not typical to have partition update messages. Bypass is OK but not pu (partition update). Regardless of how it's running right now re-run it.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
OK - Yeah - it is running very nice right now, Clean Rom loaded fine, and all systems seem ok. However, per your advice, I will run the RUU again. FWIW, I had grabbed the version with the patch.
dottat said:
Run the ruu again. It's not typical to have partition update messages. Bypass is OK but not pu (partition update). Regardless of how it's running right now re-run it.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
OK, so I finally got around to this. I ran the RUU again, and got a fail on Userdata, and finally the same message at the end, partition update failed - power to reboot.
I let the phone boot, and then ran the RUU again, by straightaway going back into bootloader. This time, no fails, everything went through as per spec.
Thanks for insisting on re RUU. Seems like something was off, and iterating over it cured it finally. You rock, dottat.
Related
Hello!
Just got my hands on a desire S from someone who said they bricked it, i dont think it is though.
I can access fastboot/HBOOT but it doesnt seem to have a custom recovery installed, shows the stock recovery or download mode logo, the screen goes blank and vibrates 7 times.
Every time i try to flash anything through fastboot it gives me the error in the heading
FAILED (remote: not allowed)
The ROM just doesnt boot and shows T mobile logo indefinitely (must be a bootloop) but the phone doesnt have any Tmo logos on the body.
more details
SAGA PVT SHIP S-OFF RL
HBOOT-0.98.0002
RADIO-3805.06.02.03_M
eMMC-boot
I read about ENG S-off but i dont know what this phone has, maybe its just radio S-OFF cos its Tmo and doesnt have a recovery though i dont understand what the 7 vibrates mean either.
little help please?
even more details
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.98.0002
(bootloader) version-baseband: 3805.06.02.03_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.47.110.3
(bootloader) serialno: HT15TTJ01262
(bootloader) imei: 356708041646975
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: T-MOB005
(bootloader) battery-status: good
(bootloader) battery-voltage: 3653mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 0e35ea5b
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
7 vibrations most likely mean overheating, and this can't be cured by any means.
The phone is S-OFF, but doesn't have Engineering HBOOT - so you can't use fastboot, it won't allow you (just what it says).
Your best bet is to try a stock RUU and see if it helps.
Download a PG88IMG.zip from an eng hboot, copy it to root of sd (cardreader), boot to bootloader and let it do his job.
Afterwards delete the zip boot to bootloader once more and flash a recovery with fastboot.
I would use a ruu only if those steps fail.
Swyped because PC is under full load or to far away
Tectas said:
Download a PG88IMG.zip from an eng hboot, copy it to root of sd (cardreader), boot to bootloader and let it do his job.
Afterwards delete the zip boot to bootloader once more and flash a recovery with fastboot.
I would use a ruu only if those steps fail.
Swyped because PC is under full load or to far away
Click to expand...
Click to collapse
Hey Tectas I tried your method,
went here
http://forum.xda-developers.com/showthread.php?t=1178001
and got the first radio which had the same number as mine ie this one
From the 1.31.832.3 RUU:
20.28d.30.0805U_3805.04.02.01
says cid incorrect.
shall i try all the ones with 3805 in them? cos i really have no clue which one is right for me considering i dunno which RUU is compatible with this phone
raheeljessa said:
Hey Tectas I tried your method,
went here
http://forum.xda-developers.com/showthread.php?t=1178001
and got the first radio which had the same number as mine ie this one
From the 1.31.832.3 RUU:
20.28d.30.0805U_3805.04.02.01
says cid incorrect.
shall i try all the ones with 3805 in them? cos i really have no clue which one is right for me considering i dunno which RUU is compatible with this phone
Click to expand...
Click to collapse
No, not radio, leave it untouched yet, the hboot is what you need
Check my signature, I personally would recommend this one
Swyped because PC is under full load or to far away
even for this PG88IMG.zip which is the 1mb hboot file it says cid incorrect update fail press power to reboot
Tectas said:
No, not radio, leave it untouched yet, the hboot is what you need
Check my signature, I personally would recommend this one
Swyped because PC is under full load or to far away
Click to expand...
Click to collapse
even for this PG88IMG.zip which is the 1mb hboot file it says cid incorrect update fail press power to reboot
Ok then try it with a ruu, sry that i took your time for nothing
Tectas said:
Ok then try it with a ruu, sry that i took your time for nothing
Click to expand...
Click to collapse
how do i do that? sorry i seem to know nothing
Do you know from which regions your phone is?
Try in fastboot : fastboot getvar all, and Google your main version then download the appropriate file from this link
http://forum.xda-developers.com/showthread.php?t=1002506
Once you are sure you have the right RUU, you might have to make a goldcard to get rid of the CID error
The whole point of having "right" RUU is to avoid this error - having RUU for his specific region gets rid of CID error message. Otherwise he just needs any RUU and goldcard.
Jack_R1 said:
The whole point of having "right" RUU is to avoid this error - having RUU for his specific region gets rid of CID error message. Otherwise he just needs any RUU and goldcard.
Click to expand...
Click to collapse
I have what seems to be the right RUU..
now when i try to install it, the RUU installer hangs and the phone also hangs.
I should reiterate that my phone DOES NOT BOOT into the rom, has what may be boot loop error. If i could access android i wouldnt be asking any of these questions as from in there all this is easy peasy!
i'm trying booting into Hboot and fastboot to install this. as far as i remember it doesnt work here so how else can i go about it?
once again, no custom recovery, no eng bootloader, no working android rom
Thanks to all of you who tried to help by the way
raheeljessa said:
I have what seems to be the right RUU..
now when i try to install it, the RUU installer hangs and the phone also hangs.
I should reiterate that my phone DOES NOT BOOT into the rom, has what may be boot loop error. If i could access android i wouldnt be asking any of these questions as from in there all this is easy peasy!
i'm trying booting into Hboot and fastboot to install this. as far as i remember it doesnt work here so how else can i go about it?
once again, no custom recovery, no eng bootloader, no working android rom
Thanks to all of you who tried to help by the way
Click to expand...
Click to collapse
3 possibilities:
1. Let the ruu run without attached device till the only option is to close the program, search in your temp folder for the rom.zip, copy it to another folder, close the program, copy it to sd and try to flash it the same way you did before with the hboot (rename the rom.zip to PG88IMG.zip before you flash it)
2. Do the same like at 1. but create a goldcard before
3. Do the same I described before with hboot, but create a goldcard before
Swyped because PC is under full load or to far away
If the RUU installer hangs - your chances aren't too good.
If it hangs on "rebooting to bootloader" - boot to FASTBOOT manually and start RUU while in fastboot mode.
If it hangs updating - chances are you're another case of faulty eMMC.
gave the phone to some guy in the market. says he'll take 5£ to open it and check it out and let me know whats wrong.
the RUU rom.zip file when renamed to pg88img.zip or whatever does work as its the only zip file it detects in hboot mode,
it starts the update, heats up like an angry mountain and then sucks its battery off..
thanks you guys for all the help. I'll update you on what was the actual problem when this guy tells me so you know what these symptoms are for in future
Have you tried using the gold card? As it has already been stated that it should get rid of the wrong cid issue.
Sent from my HTC Desire S using XDA
Hello Community,
Let me begin by apologizing if I am in the wrong forum channel. I am new to the site kind of. I mostly sift through answers.
In this case I have not found anyone with my problem cause the wouldn't make the rookie mistake of forgetting to take a backup BEFORE flashing junk on their fancy phones.
Resources: I have latest TWRP, can access it and bootloader
Problem: :crying:
I have an HTC One M7 from Sprint. Currently all user data has been formatted (cause I am genius). I am able to lock and unlock bootloader. My phone is in S-ON (another dumb mistake I know). The device is recognized in fastboot but not in ABD and I cant figure out why not. superuser was deleted by the wipe. :crying:
Solutions Tried but Failed:
I have download the RUU for my phone (or at least I think *651.10 and *651.7) and tried to run the setup.exe in admin mode while my phone was locked in fastboot... This resulted in an Error:155
I have tried flashing the same RUU from cmd prompt... this resulted in remote 12: signature error (still dont know what that means)
I have tried achieving S-OFF but alas I cant get my device to be recognized by ABD, I dont have an OS for internet/radio signal
I am starting to think I may have just effed everything up.
fastboot getvar all
version: 0.5
version-bootloader: 1.56.0000
version-baseband: N/A
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: FA
imei: 99*
meid: 99*
product: m7_wls
platform: HBOOT-8064
modelid: PN0720000
cidnum: SPCS_001
battery-status: good
battery-voltage: 4237mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-4dab9d12
hbootpreupdate: 11
gencheckpt: 0
PLEASE HELP
nbranch1311 said:
Hello Community,
Let me begin by apologizing if I am in the wrong forum channel. I am new to the site kind of. I mostly sift through answers.
In this case I have not found anyone with my problem cause the wouldn't make the rookie mistake of forgetting to take a backup BEFORE flashing junk on their fancy phones.
Resources: I have latest TWRP, can access it and bootloader
Problem: :crying:
I have an HTC One M7 from Sprint. Currently all user data has been formatted (cause I am genius). I am able to lock and unlock bootloader. My phone is in S-ON (another dumb mistake I know). The device is recognized in fastboot but not in ABD and I cant figure out why not. superuser was deleted by the wipe. :crying:
Solutions Tried but Failed:
I have download the RUU for my phone (or at least I think *651.10 and *651.7) and tried to run the setup.exe in admin mode while my phone was locked in fastboot... This resulted in an Error:155
I have tried flashing the same RUU from cmd prompt... this resulted in remote 12: signature error (still dont know what that means)
I have tried achieving S-OFF but alas I cant get my device to be recognized by ABD, I dont have an OS for internet/radio signal
I am starting to think I may have just effed everything up.
fastboot getvar all
version: 0.5
version-bootloader: 1.56.0000
version-baseband: N/A
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: FA
imei: 99*
meid: 99*
product: m7_wls
platform: HBOOT-8064
modelid: PN0720000
cidnum: SPCS_001
battery-status: good
battery-voltage: 4237mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-4dab9d12
hbootpreupdate: 11
gencheckpt: 0
PLEASE HELP
Click to expand...
Click to collapse
As long as you're S-ON you may only flash a RUU thats the same version or newer as installed on your phone. The RUUs you tried are older than the installed firmware. A backup that yu can restore via recovery should work.
Have you been on Android 4.3? This is the latest available RUU -> http://dl3.htc.com/application/RUU_M7_WL_JB43_SENSE50_SPCS_MR_Sprint_WWE_3.04.651.2_Radio_1.00.20.0913_3_NV_SPCS_4.38_003_release_335355_signed_2.exe
no backup
LS.xD said:
As long as you're S-ON you may only flash a RUU thats the same version or newer as installed on your phone. The RUUs you tried are older than the installed firmware. A backup that yu can restore via recovery should work.
Click to expand...
Click to collapse
Thank you for responding so quickly. I do not have a backup like I said. I dont know what version of RUU to get cause none of them work. If you know of the right RUU that would be AWESOME (HTC One M7 Sprint) so then I can up-date that in to my solutions tried.
Again thank you for helping.
nbranch1311 said:
Thank you for responding so quickly. I do not have a backup like I said. I dont know what version of RUU to get cause none of them work. If you know of the right RUU that would be AWESOME (HTC One M7 Sprint) so then I can up-date that in to my solutions tried.
Again thank you for helping.
Click to expand...
Click to collapse
Have yu been on Android 4.3 before? Have you checked the RUU i posted? That the latest available. BTW you'll have to flash stock recovery before you run the RUU!
LS.xD said:
Have yu been on Android 4.3 before? Have you checked the RUU i posted? That the latest available. BTW you'll have to flash stock recovery before you run the RUU!
Click to expand...
Click to collapse
No I have not gone to Android 4.3 site. I will check it now. Also sorry I saw your RUU right after I replied. As for flashing the stock recovery I assume I can find the file for that Android 4.3? orrr is it already in TWRP.
nbranch1311 said:
No I have not gone to Android 4.3 site. I will check it now. Also sorry I saw your RUU right after I replied. As for flashing the stock recovery I assume I can find the file for that Android 4.3? orrr is it already in TWRP.
Click to expand...
Click to collapse
The RUU contains ALL you need. Flash stock recovery via fastboot. Then relock bootloader. Then run the RUU while phone is connected in fastboot mode. It will delete al changes and set ALL phone files to stock. TWRP will be gone, root, erros, your data...
LS.xD said:
The RUU contains ALL you need. Flash stock recovery via fastboot. Then relock bootloader. Then run the RUU while phone is connected in fastboot mode. It will delete al changes and set ALL phone files to stock. TWRP will be gone, root, erros, your data...
Click to expand...
Click to collapse
I can't seem to find the stock recovery. I am sucking at the internet
nbranch1311 said:
I can't seem to find the stock recovery. I am sucking at the internet
Click to expand...
Click to collapse
Its contained in the RUU. When you open the RUU you have to go to windows temp directory. There are two folders created by the ruu. One folder conatins a rom.zip. Open it with winrar to extract the recovery.img.
LS.xD said:
Its contained in the RUU. When you open the RUU you have to go to windows temp directory. There are two folders created by the ruu. One folder conatins a rom.zip. Open it with winrar to extract the recovery.img.
Click to expand...
Click to collapse
I searched the RUU you sent me but its an exe. All it does is start up. I hate to be a pain but could you please send me the latest image I need. Starting to freak out cause I think I am doing all this right and its still not working. I dont know.
Received my pm?
Sent from my beloved HTC One S using (most time buggy) Tapatalk
nbranch1311 said:
I searched the RUU you sent me but its an exe. All it does is start up. I hate to be a pain but could you please send me the latest image I need. Starting to freak out cause I think I am doing all this right and its still not working. I dont know.
Click to expand...
Click to collapse
I think you gave me a virus... This deleted pretty every local folder on my machine... Thank you?
nbranch1311 said:
I think you gave me a virus... This deleted pretty every local folder on my machine... Thank you?
Click to expand...
Click to collapse
Are you kidding me?
I posted link to the RUU for your phone lol. Thats not a virus...
If you check the link again --> ITS FROM OFFICIAL HTC.COM!!!
LS.xD said:
Are you kidding me?
I posted link to the RUU for your phone lol. Thats not a virus...
If you check the link again --> ITS FROM OFFICIAL HTC.COM!!!
Click to expand...
Click to collapse
Look man I am just tell you what I see. Literally every folder in my library has been delete. I will send a screen shot.
As soon as I tried to unhide temp folder it freaked out and I cant even find me as a user... freaking out. worried about my phone now my comp is pretty much empty. LOL its like having a brand new computer but i have all my apps
nbranch1311 said:
Look man I am just tell you what I see. Literally every folder in my library has been delete. I will send a screen shot.
As soon as I tried to unhide temp folder it freaked out and I cant even find me as a user... freaking out. worried about my phone now my comp is pretty much empty. LOL its like having a brand new computer but i have all my apps
Click to expand...
Click to collapse
I really have no clue what you did with your machine BUT i'm pretty SURE that offficial HTC software from official HTC.COM website won't contain any harmfull software, malware, viruses and so on!!! So just think about it before you start blaming me, while i'm trying to help you.
BTW
I'm downloading the file on my own now, just to be REALLY SURE its fine.
Also i can extract the recovery.img and upload it (If you're still interested... )
LS.xD said:
I really have no clue what you did with your machine BUT i'm pretty SURE that offficial HTC software from official HTC.COM website won't contain any harmfull software, malware, viruses and so on!!! So just think about it before you start blaming me, while i'm trying to help you.
BTW
I'm downloading the file on my own now, just to be REALLY SURE its fine.
Also i can extract the recovery.img and upload it (If you're still interested... )
Click to expand...
Click to collapse
I am interested but I dont know what I would do with them at the moment. literally every file i had personally is gone. I open the option to show all folders and all my folders are empty from the ones I can open. I lost everything. I dont know what happened. All I did was try to unhide hidden folders to see the temp folder
nbranch1311 said:
I am interested but I dont know what I would do with them at the moment. literally every file i had personally is gone. I open the option to show all folders and all my folders are empty from the ones I can open. I lost everything. I dont know what happened. All I did was try to unhide hidden folders to see the temp folder
Click to expand...
Click to collapse
You probably have manually changed or deleted files. I never suggested to do so! You can easily open temp by typing %temp% ! The files are just accessable while the RUU is opened.
I'm opening RUU now to check it for viruses...
nbranch1311 said:
I am interested but I dont know what I would do with them at the moment. literally every file i had personally is gone. I open the option to show all folders and all my folders are empty from the ones I can open. I lost everything. I dont know what happened. All I did was try to unhide hidden folders to see the temp folder
Click to expand...
Click to collapse
Ok...so lol lets say I fixed it and gave you a giant freaken apology for claiming you gave me a virus...I wont go into what dumb-a thing I did I will just say I have my folders and files.
Sooo about that img file.
Dude seriously I feel like bunk and wish I could do something to make it up
LS.xD said:
You probably have manually changed or deleted files. I never suggested to do so! You can easily open temp by typing %temp% ! The files are just accessable while the RUU is opened.
I'm opening RUU now to check it for viruses...
Click to expand...
Click to collapse
If you figure this phone bullcrap out I will donate. I just need my phone back. So I need what ever needs to be done to get this back to stock so I can remake mistakes on it
nbranch1311 said:
If you figure this phone bullcrap out I will donate. I just need my phone back. So I need what ever needs to be done to get this back to stock so I can remake mistakes on it
Click to expand...
Click to collapse
I have checked the RUU. Its locked to extract recovery. I'm just downloading the decrypted version. Just have some patientce. I'll post link as soon as i can
EDIT:
Here is the right firmware (It conatins e.g. recovery.img) --> LINK
And I just minded that THIS is the latest RUU.
Please download both files. Just calm down, your phone will be fine again soon
Installation:
1. connect your phone in fastboot mode
2. flash the "recovery.img" contained in the "firmware.zip" via fastboot (Fastboot flash recovery recovery.img)
3. Reboot bootloader (Fastboot reboot-bootloader)
4. Re-lock bootloader (Fastboot oem lock)
5. Reboot bootloader (Fastboot reboot-bootloader)
6. Run the RUU while phone is still connected
7. Thats all. If you proceed in the described way, your phone will be and fully working again
LS.xD said:
I have checked the RUU. Its locked to extract recovery. I'm just downloading the decrypted version. Just have some patientce. I'll post link as soon as i can
EDIT:
Here is the right firmware (It conatins e.g. recovery.img) --> LINK
And I just minded that THIS is the latest RUU.
Please download both files. Just calm down, your phone will be fine again soon
Click to expand...
Click to collapse
Does this matter
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (Too many links))
finished. total time: 1.152s
Hi
A few days ago I tried to unlock my HTC XL Evita and then flash a custom rom. I'm not entirely sure exactly what I have done.
** TAMPERED **
** UNLOCKED **
Evita PVT SHIP S-On RL
HBOOT-2.18.0000
RADIO-1.34a.32.45.21
OpenDSP-v33.1.0.45.1128
eMMC-boot
Nov 15 2013
At the moment it boots directly into CWM 6.0.4.4
CWM reports that it can not mount basically anything, including the USB Storage. Hence CWM has no usefulness.
From the bootloader, I can run FASTBOOT commands. This is what happens if I try to send a zipped rom
C:\.android>fastboot flash zip KarbonKat-v1.0-14-20140531-1251-evita.zip
sending 'zip' (178295 KB)...
OKAY [ 7.930s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 7.963s
If I try to upgrade CWM to 6.0.4.8 it works, but after a full reboot it reverts to 6.0.4.4
If I 'send' a rom zip via CWM, it appears to install correctly, but when it reboots it just goes back into CWM.
I'm a little lost with what to try next. Would appreciate some help. Do I need to provide any more information?
WiZeR said:
Hi
A few days ago I tried to unlock my HTC XL Evita and then flash a custom rom. I'm not entirely sure exactly what I have done.
** TAMPERED **
** UNLOCKED **
Evita PVT SHIP S-On RL
HBOOT-2.18.0000
RADIO-1.34a.32.45.21
OpenDSP-v33.1.0.45.1128
eMMC-boot
Nov 15 2013
At the moment it boots directly into CWM 6.0.4.4
CWM reports that it can not mount basically anything, including the USB Storage. Hence CWM has no usefulness.
From the bootloader, I can run FASTBOOT commands. This is what happens if I try to send a zipped rom
C:\.android>fastboot flash zip KarbonKat-v1.0-14-20140531-1251-evita.zip
sending 'zip' (178295 KB)...
OKAY [ 7.930s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 7.963s
If I try to upgrade CWM to 6.0.4.8 it works, but after a full reboot it reverts to 6.0.4.4
If I 'send' a rom zip via CWM, it appears to install correctly, but when it reboots it just goes back into CWM.
I'm a little lost with what to try next. Would appreciate some help. Do I need to provide any more information?
Click to expand...
Click to collapse
You can't flash a ROM using fastboot, you flash ROMs through the recovery. If you've performed a factory reset from the bootloader that's why you can't mount your sd card. This is a bug common to this device, it corrupts the sd card, so never perform a factory reset from the bootloader. My advice right now would be to flash TWRP recovery instead of CWM, you'll find TWRP builds for our device here:
http://goo.im/devs/OpenRecovery/evita
Check the How-To Guide For Beginners thread in my signature for detailed instructions on how to do this, and many other basic operations. You should also check the Evita FAQ thread in my signature.
Anyway, once you have TWRP installed you can use the wipe menu to wipe the sd card (if indeed you did corrupt it by performing a factory reset from the bootloader). Use the mount menu to mount the sd card (mount usb storage) and copy a ROM across. Then use proper process to flash a ROM.
Sent from my Evita
ooooh you beautiful ozzie bastard!! I could kiss you on the mouth I've been f*cking about with this for 3 days straight!
Your beginner thread helped. Although I could not get it to install via the SD card/internal storage for some reason. In the end I tried sideload and that did it. Re-flashed boot.img and now I'm booting into KarbonKat
Thanks again. Appreciate the help.
Should I bother with S-Off? Will that give me anything extra above custom roms?
WiZeR said:
ooooh you beautiful ozzie bastard!! I could kiss you on the mouth I've been f*cking about with this for 3 days straight!
Your beginner thread helped. Although I could not get it to install via the SD card/internal storage for some reason. In the end I tried sideload and that did it. Re-flashed boot.img and now I'm booting into KarbonKat
Thanks again. Appreciate the help.
Should I bother with S-Off? Will that give me anything extra above custom roms?
Click to expand...
Click to collapse
Lol, I'll just take the thanks [emoji13]
Having s-off is definitely something you should do, there are some great benefits:
- You'll no longer need to flash the boot.img via fastboot every time you change ROMs or kernels.
- You'll be able to flash radios.
- You can run any Evita RUU.
- There are other benefits I can't think of right now.
Facepalm S-off (requires SuperCID)
Rumrunner S-off (doesn't require SuperCID, but I'm not sure how reliable this method is with an aosp ROM installed)
I find it odd that installing from the sd card didn't work. I'm thinking that's possibly because you don't have the correct recovery version installed (TWRP 2.7.0.8 is required for current aosp ROMs due to an updated fstab layout that's been introduced by CM). It's worth flashing that version, you'll find a thread for it by @pandasa123 in our Android Development Section.
Sent from my Evita
Ahh bollix, I fuxed it!
I needed to unlock the Orange sim on my Evita and realised, after I bought an unlock code, that it would only work on stock roms. I started trying to flash a stock rom and failed. FAILED I TALL YE!!
I tried following this thread to flash a stock rom. However it failed and when I rebooted, I got stuck in a bootloop to the bootloader. Fixed that by re-flashing the recovery. However, now it does not boot the phone anymore (hangs on the boot logo). I can't mount the SDCard. So last resort, I tried sideloading the stock rom. This is what happened:
C:\.android>adb sideload OTA_EVITA_UL_JB_45_S_Orange_UK_3.17.zip
* failed to write data 'protocol fault (no status)' *62%
Click to expand...
Click to collapse
Here's where I'm at.
C:\.android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.18.0000
(bootloader) version-baseband: 1.34a.32.45.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8311000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4171mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c20bff6f
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.069s
Click to expand...
Click to collapse
** TAMPERED **
** UNLOCKED **
Evita PVT SHIP S-On RL
HBOOT-2.18.0000
RADIO-1.34a.32.45.21
OpenDSP-v33.1.0.45.1128
eMMC-boot
Nov 15 2013
Click to expand...
Click to collapse
I'm befuzzled
What recovery version do you have installed? And exactly which ROM did you attempt to install?
Sent from my Evita
Hey
So I was playing with it into the early hours and managed to get some progress. Was using TWRP 2.7.0.8, I installed an older version of CMR (6.0.4.8) and was able to properly 'wipe'/format the SDCard partition. After this, I could mount the SDCard and transfer ROMs from Windows. The first ROMs I tried where the stock Orange Roms from this thread. But I got a failed message on both. I then tried the last ROM I had working, which was KarbonKat-v1.0-14-20140531 - That flashed fine and booted. So just for kicks I thought I'd try the Slim-Evita-4.4.4.build.6-Unofficial - That flashed fine, but it buggy as hell.
So I can go back to KarbonKat and be up and running, but it does not solve my problem of needing to unlock it to use another simcard.
What should I do next?
WiZeR said:
Hey
So I was playing with it into the early hours and managed to get some progress. Was using TWRP 2.7.0.8, I installed an older version of CMR (6.0.4.8) and was able to properly 'wipe'/format the SDCard partition. After this, I could mount the SDCard and transfer ROMs from Windows. The first ROMs I tried where the stock Orange Roms from this thread. But I got a failed message on both. I then tried the last ROM I had working, which was KarbonKat-v1.0-14-20140531 - That flashed fine and booted. So just for kicks I thought I'd try the Slim-Evita-4.4.4.build.6-Unofficial - That flashed fine, but it buggy as hell.
So I can go back to KarbonKat and be up and running, but it does not solve my problem of needing to unlock it to use another simcard.
What should I do next?
Click to expand...
Click to collapse
Those Orange files you found aren't ROMs, they're OTA files, they're not flashable via recovery. Nothing from that thread you linked to is flashable via recovery, they're all RUU's and OTA's.
KarbonKat is a pretty good ROM and you should have a pretty good experience on that one. You'll need to flash a Sense ROM in order to use your SIM unlock code, you'll find Sense ROMs in the Android Development Section.
Sent from my Evita
timmaaa said:
Those Orange files you found aren't ROMs, they're OTA files, they're not flashable via recovery. Nothing from that thread you linked to is flashable via recovery, they're all RUU's and OTA's.
KarbonKat is a pretty good ROM
Click to expand...
Click to collapse
Ok, thanks. I'm downloading 'CleanROM' and will try that.
I had a pretty annoying issue with KarbonKat, in that it kept locking up and rebooting. Wasn't running any major apps or overclocking it. It would reboot just sitting on the side doing nothing. Often would lockup when I pressed the power button to wake it up. Would that be a hardware fault?
Further testing on different ROMs will tell you whether you have a hardware problem or not.
Sent from my Evita
I had a similar issue with aosp roms. Relieved it by turning off MP-Decision with Trickster MOD (should be possible with other kernel tuners.) I'd try flashing other roms first to be sure it isnt rom/flash related.
Thanks
So I finally got CleanMod on there and it's now fully booted and the simcard is unlocked.
If I now flash an AOSP KitKat ROM, will I loose the sim unlock? Other than KarbonKat, are there any other 4.4 roms you would recomend?
WiZeR said:
Thanks
So I finally got CleanMod on there and it's now fully booted and the simcard is unlocked.
If I now flash an AOSP KitKat ROM, will I loose the sim unlock? Other than KarbonKat, are there any other 4.4 roms you would recomend?
Click to expand...
Click to collapse
You'll never lose the SIM unlock, no matter how many ROMs you flash. Asking which ROM is best/most stable/fastest/prettiest, or asking for a suggestion isn't allowed so I can't answer that, here's why. To say one ROM is better is to infer that the others are inferior in some way. This is disrespectful to the devs who spend their spare time bringing us these awesome ROMs free of charge. Each user has different tastes anyway, the best way to see which ROM suits you is to flash a few and find out for yourself. We have plenty to choose from.
Sent from my Evita
Understood, thanks
My HTC One SV (LTE europe version ) stuck while booting, it displays white logo screen only,
now i unlocked bootloader and tried to flash rom, but failed,
How i can flash a custom rom or original oerating systedm in my phone,
please help me.
anpayy said:
My HTC One SV (LTE europe version ) stuck while booting, it displays white logo screen only,
now i unlocked bootloader and tried to flash rom, but failed,
How i can flash a custom rom or original oerating systedm in my phone,
please help me.
Click to expand...
Click to collapse
Can you get into the bootloader? If you can, you can flash TWRP recovery via fastboot and flash a custom Rom with the recovery.
Yes
thearif said:
Can you get into the bootloader? If you can, you can flash TWRP recovery via fastboot and flash a custom Rom with the recovery.
Click to expand...
Click to collapse
i can get into bootloder, but where can i get TWRP recovery and custom rom file ?
anpayy said:
i can get into bootloder, but where can i get TWRP recovery and custom rom file ?
Click to expand...
Click to collapse
Go to http://forum.xda-developers.com/showthread.php?t=2292432 . Read through and find the recovery there. It is pretty well explained there. I am on my mobile so I am not sure of the link will take you to the first page. It is on the first page. Make sure you get the correct recovery for your phone model.
Original rom
Where i can get original ROM for HTC ONE SV LTE k2ul_4.2.2_3.11.401.1 ???
anpayy said:
Where i can get original ROM for HTC ONE SV LTE k2ul_4.2.2_3.11.401.1 ???
Click to expand...
Click to collapse
That I do not know, but if my memory serves me right, there was a thread either in android development or general sections with the latest OTAs. You might wanna search for that...
anpayy said:
Where i can get original ROM for HTC ONE SV LTE k2ul_4.2.2_3.11.401.1 ???
Click to expand...
Click to collapse
You've already got the link to my index thread, but it seems you are to lazy to have a look at it. You even only need to watch for the software number and you will easily find what you are searching for.
Os intallation failed
i tried to install OTA update through TWRP recovery , but it failed
You can't flash this in recovery. Use TWRP recovery and flash the rom (not the Ota). Links are in my index thread.
Installed rom
Sucessfully instaled Viper SV rom,
but still phone did not booting,
Did you also flash boot.img of the rom in fastboot?
no
I missed to boot boot.img,
Now phone is working perfectly...........
Thanks all........specially old.splatterhand & thearif
Nice
anpayy said:
I missed to boot boot.img,
Now phone is working perfectly...........
Thanks all........specially old.splatterhand & thearif
Click to expand...
Click to collapse
Good to hear that...
Hi all,
I'm new in this forum so I post there.
My problems starts after try to updete htc one sv k2_ul. After update I get red triangle and then my phone freezed on white screen with logo.
Try to do factory reset from bootloader, but nothing happen. After few days looking information I unlock bootloader and try flash new boot, but after that I get Tampered. I found if I must s-off, but how I can get it? My pc found phone only on fastboot mode. Any ideas?
miegas said:
Hi all,
I'm new in this forum so I post there.
My problems starts after try to updete htc one sv k2_ul. After update I get red triangle and then my phone freezed on white screen with logo.
Try to do factory reset from bootloader, but nothing happen. After few days looking information I unlock bootloader and try flash new boot, but after that I get Tampered. I found if I must s-off, but how I can get it? My pc found phone only on fastboot mode. Any ideas?
Click to expand...
Click to collapse
You can't get S-off, without working OS.
You don't have an OS anymore on your phone?
Are you running a custom recovery like TWRP?
Run this fastboot cmd and copy the output here (remove your imei & serial number):
Code:
fastboot getvar all
old.splatterhand said:
You can't get S-off, without working OS.
You don't have an OS anymore on your phone?
Are you running a custom recovery like TWRP?
Run this fastboot cmd and copy the output here (remove your imei & serial number):
Code:
fastboot getvar all
Click to expand...
Click to collapse
My os just stop working.
I don't try TWRP, today will look more about that.
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0000
(bootloader) version-baseband: 1.15.40a.00.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.14.401.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: k2_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8010000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4143mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.075s
edit
I flashed TWRP and I make restore, but phone won't start anyway. Maybe need to flash new os?
Flash the stock rom in TWRP, and don't forget to flash boot.img of the rom in fastboot.
Links are in my index thread.
Make a backup in recovery (just in case) and a wipe (advanced -> everything except int & ext sdcard) before.
old.splatterhand said:
Flash the stock rom in TWRP, and don't forget to flash boot.img of the rom in fastboot.
Links are in my index thread.
Make a backup in recovery (just in case) and a wipe (advanced -> everything except int & ext sdcard) before.
Click to expand...
Click to collapse
Something I make wrong. I flashed TWRP, then installed ViperSV, phone restarted and booted TWRP. Then I found boot.img in yours index thead.
Then in fastboot flashed new boot, but phone still booting in TWRP. What I make wrong?
You need to flash the boot.img thats inside the ViperSV.zip, not any from my index thread.
Hi all! I have a bricked HTC Sensation 4G (T-Mobile) that I am trying to fix.
I need help with RUUing the HTC Sensation 4G. (Z710e)
I believe I have tried everything, all without luck, please help, TIA.
Heres the problem with the phone- It appears to be stuck in a bootloop, boots up to the white HTC screen, makes the HTC startup chime with Quietly Brilliant written under it, and then immediately reboots, and continuously does this over and over again.
Heres what I know about the phone
The Bootloader is Locked
The Phone is S-ON
The CID of the phone is HTC__621
Here's what I've tried
I have tried RUUing the phone with RUU_PYRAMID_ICS_TMOUS_3.32.531.14_Radio_11.69A.3504.00U_11.23.3504.07_M2_release_256085_signed.exe
since it is a T-Mobile HTC Sensation 4G. However I keep getting Error 130: Model ID error.
I also tried RUUing the phone manually using CMD, following the guide however this failed aswell, I kept getting "remote: 12 signature verify fail" at the end.
I also tried renaming extracting the rom.zip from the RUU, renaming that to PG58IMG.zip, placing that on my sd card and booting the phone into bootloader. However when I tried this it said checking PG158.img, but nothing happened, it just continued to boot up to the bootloader.
At this point I realized maybe that this RUU didn't match my CID, which was why it was failing. So I tried opening the ROM.zip file however it said it was corrupt in windows explorer. I then tried redownloading the RUU but it still kept saying ROM.zip was corrupt. I then opening ROM.zip with winrar and it opened up! I then opened android-info.text and saw that the cidnum for the RUU was T-MOB0101. I tried changing this to my CID (HTC__621) and then saving as instructed in this guide, however when I pressed on YES to update the files in the archive, winrar gives an error and says that the archive is corrupt, and does not update android-info.text.
I am not sure what else to try at this point, and I am stumped as to why none of the following methods I've tried worked. Is there something I am doing wrong? Is there anything I'm missing? Any help would be very gladly appreciated, as I am out of ideas.
Also worth noting, I've attached 2 pictures below as attachements to this post, (since I am new to xdadevelopers I cannot post direct links to images), one of the bootloader of the phone, including information such as my hboot version, radio version, etc. in case its needed.
I've also attached a picture below of what happens when I put the phone into HTC stock android recovery and press Factory Data Wipe/Reset. I get a bunch of errors, I'm not sure if this is related to anything but it doesn't look normal, so I attached a picture of it below.
Thanks in advance!
sebzter said:
Hi all! I have a bricked HTC Sensation 4G (T-Mobile) that I am trying to fix.
I need help with RUUing the HTC Sensation 4G. (Z710e)
I believe I have tried everything, all without luck, please help, TIA.
Heres the problem with the phone- It appears to be stuck in a bootloop, boots up to the white HTC screen, makes the HTC startup chime with Quietly Brilliant written under it, and then immediately reboots, and continuously does this over and over again.
Heres what I know about the phone
The Bootloader is Locked
The Phone is S-ON
The CID of the phone is HTC__621
Here's what I've tried
I have tried RUUing the phone with RUU_PYRAMID_ICS_TMOUS_3.32.531.14_Radio_11.69A.3504.00U_11.23.3504.07_M2_release_256085_signed.exe
since it is a T-Mobile HTC Sensation 4G. However I keep getting Error 130: Model ID error.
I also tried RUUing the phone manually using CMD, following the guide however this failed aswell, I kept getting "remote: 12 signature verify fail" at the end.
I also tried renaming extracting the rom.zip from the RUU, renaming that to PG58IMG.zip, placing that on my sd card and booting the phone into bootloader. However when I tried this it said checking PG158.img, but nothing happened, it just continued to boot up to the bootloader.
At this point I realized maybe that this RUU didn't match my CID, which was why it was failing. So I tried opening the ROM.zip file however it said it was corrupt in windows explorer. I then tried redownloading the RUU but it still kept saying ROM.zip was corrupt. I then opening ROM.zip with winrar and it opened up! I then opened android-info.text and saw that the cidnum for the RUU was T-MOB0101. I tried changing this to my CID (HTC__621) and then saving as instructed in this guide, however when I pressed on YES to update the files in the archive, winrar gives an error and says that the archive is corrupt, and does not update android-info.text.
I am not sure what else to try at this point, and I am stumped as to why none of the following methods I've tried worked. Is there something I am doing wrong? Is there anything I'm missing? Any help would be very gladly appreciated, as I am out of ideas.
Also worth noting, I've attached 2 pictures below as attachements to this post, (since I am new to xdadevelopers I cannot post direct links to images), one of the bootloader of the phone, including information such as my hboot version, radio version, etc. in case its needed.
I've also attached a picture below of what happens when I put the phone into HTC stock android recovery and press Factory Data Wipe/Reset. I get a bunch of errors, I'm not sure if this is related to anything but it doesn't look normal, so I attached a picture of it below.
Thanks in advance!
Click to expand...
Click to collapse
You can access bootloader so no problems here. Unlock bootloader through htcdev. In fastboot mode flash latest 4ext recovery, enable smartflash in settings, then flash a custom rom. You can also try Android Revolution HD rom if you prefer a stock look.
matekaneve said:
You can access bootloader so no problems here. Unlock bootloader through htcdev. In fastboot mode flash latest 4ext recovery, enable smartflash in settings, then flash a custom rom. You can also try Android Revolution HD rom if you prefer a stock look.
Click to expand...
Click to collapse
Thanks for the info! However I just tried unlocking the bootloader through htcdev but I keep getting an error at the end "Unlock token check failed". You can see this in the picture I attached below of the command prompt window. Any ideas? I tried resubmitting my unlock token on htcdev to make sure I didn't leave any extra spaces or anything but still got the same result. Thanks
sebzter said:
Thanks for the info! However I just tried unlocking the bootloader through htcdev but I keep getting an error at the end "Unlock token check failed". You can see this in the picture I attached below of the command prompt window. Any ideas? I tried resubmitting my unlock token on htcdev to make sure I didn't leave any extra spaces or anything but still got the same result. Thanks
Click to expand...
Click to collapse
Strange... Make sure you copy and paste right from the beginning to the end. You can also try to move your adb/fastboot folder somewhere else for example to the desktop and try resubmitting the token from there. (Might sound stupid but works sometimes). If not, you need to find the right RUU for your device and RUU it, then follow this guide for s-off: http://forum.xda-developers.com/showthread.php?p=26280760 there are some devices htcdev unlock doesn't work unfortunately... Otherwise I have no other idea, sorry. Somebody might be able to help.
matekaneve said:
Strange... Make sure you copy and paste right from the beginning to the end. You can also try to move your adb/fastboot folder somewhere else for example to the desktop and try resubmitting the token from there. (Might sound stupid but works sometimes). If not, you need to find the right RUU for your device and RUU it, then follow this guide for s-off: http://forum.xda-developers.com/showthread.php?p=26280760 there are some devices htcdev unlock doesn't work unfortunately... Otherwise I have no other idea, sorry. Somebody might be able to help.
Click to expand...
Click to collapse
Thanks again for your response, I just did it again this time with my fastboot folder on the desktop, however I still got the same error. How would I find the right RUU for my device? It is an american HTC Sensation 4G from T-Mobile with its CID: HTC__621. I haven't been able to find another RUU for it other than the one I used as previously mentioned in my original post. If anyone has the link to the right RUU I could use for this device, it would be really helpful. Thanks again.
sebzter said:
Thanks again for your response, I just did it again this time with my fastboot folder on the desktop, however I still got the same error. How would I find the right RUU for my device? It is an american HTC Sensation 4G from T-Mobile with its CID: HTC__621. I haven't been able to find another RUU for it other than the one I used as previously mentioned in my original post. If anyone has the link to the right RUU I could use for this device, it would be really helpful. Thanks again.
Click to expand...
Click to collapse
Could you write here the info you get for the command "fastboot getvar all"
matekaneve said:
Could you write here the info you get for the command "fastboot getvar all"
Click to expand...
Click to collapse
Yes, here it is
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.0000
(bootloader) version-baseband: 11.24A.3504.31_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.33.709.6
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813000
(bootloader) cidnum: HTC__621
(bootloader) battery-status: good
(bootloader) battery-voltage: 3991mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 617f0a98
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.562s
sebzter said:
Yes, here it is
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.0000
(bootloader) version-baseband: 11.24A.3504.31_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.33.709.6
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813000
(bootloader) cidnum: HTC__621
(bootloader) battery-status: good
(bootloader) battery-voltage: 3991mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 617f0a98
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.562s
Click to expand...
Click to collapse
Your firmware version (3.33.709.6) is an Asian one. Try downloading this ruu and run it: http://androidruu.com/getdownload.p...0U_11.24A.3504.31_M_release_266490_signed.exe
Edit: and delete your serial and imei number from your post!
matekaneve said:
Your firmware version (3.33.709.6) is an Asian one. Try downloading this ruu and run it: http://androidruu.com/getdownload.p...0U_11.24A.3504.31_M_release_266490_signed.exe
Edit: and delete your serial and imei number from your post!
Click to expand...
Click to collapse
Hi, thanks again for your help! The RUU completed successfully this time!!! However, unfortunately, for some reason it is still bootlooping :/
When I turn it on, it shows the HTC logo, plays the little chime with Quitely Brilliant written under HTC, makes a very silent beep noise, and reboots. It keeps on doing this again and again.
Any ideas on what to do next? Why would the phone do this?
sebzter said:
Hi, thanks again for your help! The RUU completed successfully this time!!! However, unfortunately, for some reason it is still bootlooping :/
When I turn it on, it shows the HTC logo, plays the little chime with Quitely Brilliant written under HTC, makes a very silent beep noise, and reboots. It keeps on doing this again and again.
Any ideas on what to do next? Why would the phone do this?
Click to expand...
Click to collapse
Well, I'm out of ideas now. At least the ruu worked. Try maybe the htcdev unlock again now. Get a new token and submit that. And go for the normal sensation option on htcdev site and NOT for the 4g
sebzter said:
Hi, thanks again for your help! The RUU completed successfully this time!!! However, unfortunately, for some reason it is still bootlooping :/
When I turn it on, it shows the HTC logo, plays the little chime with Quitely Brilliant written under HTC, makes a very silent beep noise, and reboots. It keeps on doing this again and again.
Any ideas on what to do next? Why would the phone do this?
Click to expand...
Click to collapse
UPDATE!! I just got the phone to sorta bootup once! It booted up to a configuring android screen (in japanese) and then it shut right off, and started rebooting again. Why is the phone constantly and randomly rebooting like this? I've heard some people said it was the battery but the battery seemed to hold a fairly long charge in bootloader mode, so I don't see why this would be the issue. Anyways I will try an htcdev unlock now and see if that works, will update soon.