Related
Today , i successfully rooted my HTC Sensation 4G, everything was working totally fine, but then I wanted to install and custom ROM , called Super Villain Shensation.
I followed everything like the instructions told me to, but it says that the installation was aborted. and when i want to reboot my phone, it just stays on the white HTC logo screen, and doesnt do anything. I am able to get to the bootloader, but when i try recovery the same thing happens. what do i do !?
First of all, it is not bricked. Moving forward you need to re-download the ROM to make sure it is not a corrupted download, then try to flash again.
In order it would be:
-re download ROM again (I would personally suggest a ginger bread ROM that doesn't require you to flash firmware and such)
-download super wipe
-put them both in your sd card, somewhere where you could find the files
-go into your recovery and flash the super wipe zip (found in the Android Revolution thread)
-flash ROM
-let it boot (it will take about 5 minutes)
-done
Sent from my HTC Sensation 4G with Beats Audio using XDA App
He's thesuper wipe
http://db.tt/ps5JWwBw
Sent From Space Using My ICS Flavored Sensation
He said he can't get to recovery (-.- )
Sent from my HTC Pyramid using XDA App
Can you get to the bootloader?
Sent From Space Using My ICS Flavored Sensation
Need tothrow the pg85.img zip on the root of you're sd card then boot into bootloader. Follow on screen instructions.
Sent From Space Using My ICS Flavored Sensation
Go to your bootloader like previous poster said and paste this file in the root of your sd card.
-Press the up volume rocker once you get the prompt to do it
If everything goes the way is suppose to go, you will be able to get into recovery again and flash whatever ROM you like.
This file contains Clockwork recovery
http://db.tt/ht4BPIS8
Sent from my HTC Sensation 4G with Beats Audio using XDA App
Did you superCID? If not, what is your CID, because the file: P58IMG.zip is the firmware package for your device, and it's CID dependent. Get the one you need from here: http://forum.xda-developers.com/showthread.php?t=1459767
youssefkiev said:
Did you superCID? If not, what is your CID, because the file: P58IMG.zip is the firmware package for your device, and it's CID dependent. Get the one you need from here: http://forum.xda-developers.com/showthread.php?t=1459767
Click to expand...
Click to collapse
is there a way to know the cid if we are stuck at boot loader. i have no recovery(backup corrupt). and cant install pg58img.zip....
beartraxx33 said:
is there a way to know the cid if we are stuck at boot loader. i have no recovery(backup corrupt). and cant install pg58img.zip....
Click to expand...
Click to collapse
Are you s off?
Sent from my HTC Sensation 4G with Beats Audio using xda premium
Rhiannon224 said:
Are you s off?
Sent from my HTC Sensation 4G with Beats Audio using xda premium
Click to expand...
Click to collapse
Yes i did every thing right until the cid part. and when i flash the p58img.... wrong cid.
beartraxx33 said:
Yes i did every thing right until the cid part. and when i flash the p58img.... wrong cid.
Click to expand...
Click to collapse
In that case you can find it from fastboot.
Code:
fastboot getvar cid
Sent from my Pyramid-T
stringer7 said:
In that case you can find it from fastboot.
Code:
fastboot getvar cid
Sent from my Pyramid-T
Click to expand...
Click to collapse
Fixed It. used adb fastboot to superCiD and it worked....finally. Thanks for your support guys.
having the same problem with my htc sensation
theshanebennett said:
Today , i successfully rooted my HTC Sensation 4G, everything was working totally fine, but then I wanted to install and custom ROM , called Super Villain Shensation.
I followed everything like the instructions told me to, but it says that the installation was aborted. and when i want to reboot my phone, it just stays on the white HTC logo screen, and doesnt do anything. I am able to get to the bootloader, but when i try recovery the same thing happens. what do i do !?
Click to expand...
Click to collapse
i had rooted my htc sensation with s-off....
recently i tried to flash it with cyanogenmod 9 and all i get is the logo....
revolutionary and s-off changed back to pyramid and s-on...
i'm able to get to bootloader and recovery but still the phone is not getting rebooted..
help me out guys!!!!
cheers!!!!
rockinrraj said:
i had rooted my htc sensation with s-off....
recently i tried to flash it with cyanogenmod 9 and all i get is the logo....
revolutionary and s-off changed back to pyramid and s-on...
i'm able to get to bootloader and recovery but still the phone is not getting rebooted..
help me out guys!!!!
cheers!!!!
Click to expand...
Click to collapse
Format all partitions and reflash CM9
Sent from my HTC Sensation 4G using xda premium
rtorres422 said:
Format all partitions and reflash CM9
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
I formatted all the partitions but i'm unable to flash CM9 as the security flag is ON now..
S-ON. still not able to S-OFF.. i have tried all the methods posted in xda forums.. ;(
rockinrraj said:
I formatted all the partitions but i'm unable to flash CM9 as the security flag is ON now..
S-ON. still not able to S-OFF.. i have tried all the methods posted in xda forums.. ;(
Click to expand...
Click to collapse
HTC_DEV unlock ?
rockinrraj said:
I formatted all the partitions but i'm unable to flash CM9 as the security flag is ON now..
S-ON. still not able to S-OFF.. i have tried all the methods posted in xda forums.. ;(
Click to expand...
Click to collapse
What is you hboot if it's 1.18 or below and since you're r now s-on you need to run an ruu for ics that is closes to you stock rom. To upgrade your firmware to an ics compatible firmware. If it's 1.2x then you can htc-dev unlock and if you want s-off use jb then flash 4ext recovery even if your just htc-dev unlock. If your just htc-dev unlocked in 4ext enable smart flash. Now your good to go!
Sent from my HTC Sensation using xda app-developers app
unlocked.. yes!!
ganeshp said:
HTC_DEV unlock ?
Click to expand...
Click to collapse
yeah dude.. its unlocked.
rockinrraj said:
yeah dude.. its unlocked.
Click to expand...
Click to collapse
Post the complete bootloader details here
Then I can suggest you better and precise
Sent from my Nexus 7 using xda premium
CAN ANY BODY HELP??? I tried flashing the beta Jellybean Custom Rom. I installed the G Apps first by accident in trwp When i tried installing the actual rom. It failed
# I tried again.
Factory rested it first. So it erased my back ups
It failed again
#Now my phone was bricked
read some forums. tried unbricking it my self by using the ARU wizard and RRU.
All it did was secruity lock it.:crying::crying::crying:
# Now My One X is stuck on Hboot. But i can still get into twrp.
Ive been a fan android forever but new to rooting,.
Can anybody hellp me Please??
Andriod_Kuki_ said:
CAN ANY BODY HELP??? I tried flashing the beta Jellybean Custom Rom. I installed the G Apps first by accident in trwp When i tried installing the actual rom. It failed
# I tried again.
Factory rested it first. So it erased my back ups
It failed again
#Now my phone was bricked
read some forums. tried unbricking it my self by using the ARU wizard and RRU.
All it did was secruity lock it.:crying::crying::crying:
# Now My One X is stuck on Hboot. But i can still get into twrp.
Ive been a fan android forever but new to rooting,.
Can anybody hellp me Please??
Click to expand...
Click to collapse
if u can get into twrp...
mount sd copy a rom
wipe everyrhing except sdcard
and flash the rom... u should be good
Sent from my HTC One X using xda app-developers app
i tried doing that but my phone wont show up on my computer. ILL Try again. But what rom would u recommend.
Also is there another way i can fix it??
Thank you for helpping
Andriod_Kuki_ said:
i tried doing that but my phone wont show up on my computer. ILL Try again. But what rom would u recommend.
Also is there another way i can fix it??
Thank you for helpping
Click to expand...
Click to collapse
one promising fix would be relock your bootloader ...run a ruu....unlock ...twrp...
niceppl said:
one promising fix would be relock your bootloader ...run a ruu....unlock ...twrp...
Click to expand...
Click to collapse
Ok.. Run an RUU but it didnt get past the rom update. Am i doing it right.?
Andriod_Kuki_ said:
Ok.. Run an RUU but it didnt get past the rom update. Am i doing it right.?
Click to expand...
Click to collapse
?
what do u mean?
niceppl said:
?
what do u mean?
Click to expand...
Click to collapse
Im Using
RUU_Evita_UL_Cingular_US-1.73.502.2_2FE6772699D8596307CC997452BB8D25
When i run it. It tries to update the rom and it says rom up date fail. then closes.. Do i need to do anything before i run it??/
Andriod_Kuki_ said:
Im Using
RUU_Evita_UL_Cingular_US-1.73.502.2_2FE6772699D8596307CC997452BB8D25
When i run it. It tries to update the rom and it says rom up date fail. then closes.. Do i need to do anything before i run it??/
Click to expand...
Click to collapse
Yes, you most likely need to run the 1.85 ruu.
Sent from my One X using xda app-developers app
Andriod_Kuki_ said:
Im Using
RUU_Evita_UL_Cingular_US-1.73.502.2_2FE6772699D8596307CC997452BB8D25
When i run it. It tries to update the rom and it says rom up date fail. then closes.. Do i need to do anything before i run it??/
Click to expand...
Click to collapse
yes..relock your bootloader..
also are you att hox? or rogers hox
did you get supercid?
how you running the ruu?
if you running the .exe...did you install htc sync?(need to install this and have it running before running ruu)
Ok thanks ill try it thank u
Sent from my HTC VLE_U using xda app-developers app
Andriod_Kuki_ said:
Ok.. Run an RUU but it didnt get past the rom update. Am i doing it right.?
Click to expand...
Click to collapse
rpomponio said:
Yes, you most likely need to run the 1.85 ruu.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
suggestion to re lock his hox was mentioned but his reply didn't say if he locked it, just said he tried to run the ruu. Bet it still needs locking! Also OP do you have super cid? If so he doesnt need 1.85 right? He can use the 1.73. I would still probably use the 1.85 like rpopo recommended though. Also if you have done everything correct (re locked and 1.85 if not super cid) the USB drivers can make a difference. I was super cid and locked and ruu kept failing. uninstalled my HTC drivers and ran the HTC sync program and used those drivers...Worked first time after that! Just have to remember to not actually have HTC sync running!
Wats a super cid..? Srry I'm new to rooting
Sent from my HTC VLE_U using xda app-developers app
Try the 1.85 ruu. Relocking and running the 1.85ruu usually gets you back up and running.
Sent from my HTC One X using xda app-developers app
You have to be able to use adb on your computer to relock. There is a sticky with the info on how to install drivers, use adb and relock your phone.
Sent from my HTC One X using xda app-developers app
I have used adb to relock it
Sent from my HTC VLE_U using xda app-developers app
Then run 1.85 ruu, make sure you have the USB drivers for the phone installed and then once you do that, re-root and unlock the bootloader.
It works ran the 1.85 ruu. Ten minutes later running perfectly/ :laugh::good::good::good:
Thanks :laugh::laugh::good::good::good:
If you flashed a good ROM and your stuck in hboot, use fastboot and use the following command 'fastboot oem boot' that will force your phone to boot.
Stay unlocked push recovery in fastboot again
fastboot oem rebootRUU
Start the RUU. Finish the install, then back into hboot, select recovery
Invest in a copy of titanium backup and use between rom flashing hence there isn't a micro sd card slot in the HOX
Sent from my HTC One X using xda premium
lmnope1 said:
If you flashed a good ROM and your stuck in hboot, use fastboot and use the following command 'fastboot oem boot' that will force your phone to boot.
Click to expand...
Click to collapse
8125Omnimax said:
Stay unlocked push recovery in fastboot again
fastboot oem rebootRUU
Start the RUU. Finish the install, then back into hboot, select recovery
Invest in a copy of titanium backup and use between rom flashing hence there isn't a micro sd card slot in the HOX
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
fyi, This is an old thread. It looks like he got what he needed the 2nd day of august.
I decided to downgrade to 1.85 for a fresh start after downgrading hboot to 1.09.000. 1.85, 1.73 RUUs failed and im trying 2.20 as we speak :// if this fails what are mmy options?
thanks
Did you relock the bootloader?
Sent from my HTC One XL using xda app-developers app
RUU's still fail after Jet to 1.09 due to version reported on mmcblk0p23.
Fix here:
http://forum.xda-developers.com/showthread.php?t=1671135
Note one user reported that going from 3.17 back to 1.81 ended in a bricked phone.
After Jet to 1.09 and altering mmcblk0p23 version, RUU accepted flashing, but bricked phone.
area51avenger said:
Did you relock the bootloader?
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
yes
twistedddx said:
RUU's still fail after Jet to 1.09 due to version reported on mmcblk0p23.
Fix here:
http://forum.xda-developers.com/showthread.php?t=1671135
Note one user reported that going from 3.17 back to 1.81 ended in a bricked phone.
After Jet to 1.09 and altering mmcblk0p23 version, RUU accepted flashing, but bricked phone.
Click to expand...
Click to collapse
I did this and I keep getting error 140- per this I am stuck in bl and I cant get adb
anyone? im in need of desperate help..
You don't need to run an ruu.... you downgraded your boot loader so just go on to flashing ROMs
You can flash the old radios and you should be set
No reason to put yourself through all this trouble
Sent from my One X using Tapatalk 2
superchilpil said:
You don't need to run an ruu.... you downgraded your boot loader so just go on to flashing ROMs
You can flash the old radios and you should be set
No reason to put yourself through all this trouble
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
that's the problem, I relocked the BL, so now m stuck in fastboot with a locked boot loader any way I could get to adb so I can re unlock it?
Kole_Ackerson said:
that's the problem, I relocked the BL, so now m stuck in fastboot with a locked boot loader any way I could get to adb so I can re unlock it?
Click to expand...
Click to collapse
If you still have your unlock token
Fastboot flash unlocktoken unlocktoken.bin
Replace unlocktoken.bin with the location of your old unlock token
If you don't have it go through the steps on HTC dev to get a new one. You don't need to boot up the phone, just need fastboot
Sent from my One X using Tapatalk 2
superchilpil said:
If you still have your unlock token
Fastboot flash unlocktoken unlocktoken.bin
Replace unlocktoken.bin with the location of your old unlock token
If you don't have it go through the steps on HTC dev to get a new one. You don't need to boot up the phone, just need fastboot
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
ok, I got the unlock token but its hanging on sending (0kb)
Kole_Ackerson said:
ok, I got the unlock token but its hanging on sending (0kb)
Click to expand...
Click to collapse
Make sure you're in fastboot not hboot
If that doesn't work reset your computer to make sure not programs are interfering with it
Sent from my One X using Tapatalk 2
it is in fastboot usb so ill reset my comp.
If it fails again, try running
Fastboot devices
To see if your device is showing up
Sent from my One X using Tapatalk 2
superchilpil said:
If it fails again, try running
Fastboot devices
To see if your device is showing up
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
wow,i got it. it was my usb port... and ive been in 1.14 for so long I forgot that I can just unlock with 1.09... ill be buuying you a beer when I get paid.
Kole_Ackerson said:
wow,i got it. it was my usb port... and ive been in 1.14 for so long I forgot that I can just unlock with 1.09... ill be buuying you a beer when I get paid.
Click to expand...
Click to collapse
Nah don't worry about it!
Just helping out where I can
Sent from my One X using Tapatalk 2
Can only boot to bootloader and all RUU failed
I am in a bit of trouble at the moment. I will try to describe what I have done to end up where I am now.
I have a Telstra HTC One XL. Recently upgraded an already unlocked, rooted HOXL to JB using the OTA update (big mistake I know now). This upgraded the hboot to 2.14 and software to 3.17.8xxx.
Spent a lot of time trying to re-root. TWRP didn't work (no touch response). So I eventually found the Interim CWM Recovery (no touch) by Modaco. This seemed to work well and I managed to root the phone.
Then i followed the instructions to flash to KingBeatZ 1.2.0 ROM. Booted fine but had no touch response too.
So I wiped KingBeatZ 1.2.0 and went for the nightly CM10. Again, booted fine but no touch response.
OK, so I figured I should just go back to my restored data. Tried that but apparently no restore data (didn't realise a wipe wiped the restore data as well, what is the point of that?)
So I decided to wipe CM10 to try flashing the Stock Rooted Telstra ROM by pablo11. This wipe however seems to have wiped incorrectly and this is where my real problem begins. I can now only boot to BL and Recovery. I cannot mount the sdcard so I have no way of pushing ROMS to my phone. I have tried a Telstra RUU and the latest Asia one. About to try the 1.89 Telstra RUU but I don't think that will make any difference. The setups do not detect an existing version on my phone, and all fail with Error 155. I have read that this error generally occurs due to unlocked bootloader so I have already relocked it.
I do not know what I should do now to restore any functionality to my HOXL. Any help would be greatly appreciated.
o0okiato0o said:
So I decided to wipe CM10 to try flashing the Stock Rooted Telstra ROM by pablo11. This wipe however seems to have wiped incorrectly and this is where my real problem begins. I can now only boot to BL and Recovery. I cannot mount the sdcard so I have no way of pushing ROMS to my phone. I have tried a Telstra RUU and the latest Asia one. About to try the 1.89 Telstra RUU but I don't think that will make any difference. The setups do not detect an existing version on my phone, and all fail with Error 155. I have read that this error generally occurs due to unlocked bootloader so I have already relocked it.
Click to expand...
Click to collapse
You can't run the RUU for a different carrier (CID), and you can't run an RUU for an older version. So neither 1.89 Telstra or an Asia RUU will work. You may be stuck waiting for the 3.17 RUU (don't think its been posted yet?).
You might also be able to make your own RUU by sticking the ROM in the Development forum in an RUU package. I don't know the specifics, and haven't done it myself. But I think it was done for Rogers, which never had a proper RUU package. So others might be able to advise you better on this.
redpoint73 said:
You can't run the RUU for a different carrier (CID), and you can't run an RUU for an older version. So neither 1.89 Telstra or an Asia RUU will work. You may be stuck waiting for the 3.17 RUU (don't think its been posted yet?).
You might also be able to make your own RUU by sticking the ROM in the Development forum in an RUU package. I don't know the specifics, and haven't done it myself. But I think it was done for Rogers, which never had a proper RUU package. So others might be able to advise you better on this.
Click to expand...
Click to collapse
You would need the .img files EX: system.img boot.img
Since our ROMs aren't packaged that way it won't work.
There's a way to create the system.img but its beyond me, and I do believe if it isn't signed it will fail
The only thing you can flash in hboot by ruu without s-off without being signed would be a boot.img
I would suggest trying to flash a stock ROM and a different kernel, or waiting for the ruu
Sent from my One X using Tapatalk 2
superchilpil said:
You would need the .img files EX: system.img boot.img
Since our ROMs aren't packaged that way it won't work.
There's a way to create the system.img but its beyond me, and I do believe if it isn't signed it will fail
The only thing you can flash in hboot by ruu without s-off without being signed would be a boot.img
I would suggest trying to flash a stock ROM and a different kernel, or waiting for the ruu
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Could you elaborate on the different kernel bit? I have just tried flashing a stock rom via the fastboot flash zip rom.zip method, but it fails the hboot check. Cheers
o0okiato0o said:
Could you elaborate on the different kernel bit? I have just tried flashing a stock rom via the fastboot flash zip rom.zip method, but it fails the hboot check. Cheers
Click to expand...
Click to collapse
Take a stock ROM and pull out the boot.img
And fastboot flash boot boot.img just to make sure it flashes
Then flash the ROM in recovery
Sent from my One X using Tapatalk 2
I've been running AOSP ROM's on my evita for a while now, but apparently with the 3.4 kernel you now need hboot 2.14 or higher and mine's at 1.09. My phone was unlocked with S-ON, but I did "fastboot oem lock" this morning because I read that it's necessary for an RUU. I downloaded the 2.20 RUU and tried to run the installer but I always get an Error [170] USB Connection Error. I have the HTC and adb drivers installed successfully and have tried to run the RUU as admin in both Sense and fastboot (bootloader). I'm a bit stumped and would really like to get AOSP back on my phone.
You need to S-off first.
Sent from my HTC One X using xda premium
tlazarus said:
You need to S-off first.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Should I use facepalm for that then?
EDIT
I got s-off, but still no go. Still the error 170.
I know on my old Incredible I was able to rename the rom.zip from the RUU as PB99IMG.zip and put it on the root of my sdcard. Then in hboot it would detect it and ask to flash it. This isn't happening on my evita though. Is there a way to do that, or is that only for older htc devices?
Put phone into fastboot and try again. Check error log to see if it fails to identify your phone.
Open command prompt and type adb devices, if it does not see it then try installing new drivers. If it does see it then enter " adb shell reboot oem-78" that will reboot your phone in to RUU ready fastboot. Open ruu and try running it again.
Sent from my HTC One X using xda premium
Venomtester said:
Put phone into fastboot and try again. Check error log to see if it fails to identify your phone.
Open command prompt and type adb devices, if it does not see it then try installing new drivers. If it does see it then enter " adb shell reboot oem-78" that will reboot your phone in to RUU ready fastboot. Open ruu and try running it again.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Where can I find this error log? It did see my device, I did that command (which ended at the black htc screen) and I ran the RUU again but I still get the error 170. I'm also using this RUU http://bugsylawson.com/index.php/fi...320911-2-101053225l-release-271865-signedexe/
Sounds like a bad download. Is it 568.22 mbs? Try roomyshare.com/ruu-evita-ul-cingular.html
You can find it in the list.
Sent from my HTC One X using xda premium
Venomtester said:
Sounds like a bad download. Is it 568.22 mbs? Try roomyshare.com/ruu-evita-ul-cingular.html
You can find it in the list.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
It is that size, though I may try the link you gave.
EDIT
Okay, I think I found out what I've been doing wrong. I found this link http://forum.xda-developers.com/showthread.php?t=2119610 and it turns out that the file I've been trying does NOT include the 2.14 hboot that I need. The one I need is the latest JB release, but someone said that if you flash it with superCID and S-ON that it will brick your device. I have superCID but S-OFF, does anyone think that will brick my device? Should I flash the RUU with the 1.09 hboot (which I'm running) first, and then flash the newest RUU? Also, it looks like the link I provided offers flashable OTA's of each update. Would those work/be recommended for TWRP?
Change cid to cingular "cws_001" I think. Super cid can cause brick.
Sent from my HTC One X using xda premium
Venomtester said:
Change cid to cingular "cws_001" I think. Super cid can cause brick.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Well I didn't do that...haha. I read on another forum that TWRP doesn't support that cid check function or something and to just remove it from the updater-script so I tried that and flashed the latest OTA zip in TWRP and it failed after a few steps. I tried booting and it didn't get to the boot animation so I rebooted to recovery and restored my backup. I'm going to try a stock zip without the modified updater-script and restore my CID to normal and try again.
EDIT
Well, I restored the CID to CWS__001 and I still get that check_cid error
dshoe said:
Well I didn't do that...haha. I read on another forum that TWRP doesn't support that cid check function or something and to just remove it from the updater-script so I tried that and flashed the latest OTA zip in TWRP and it failed after a few steps. I tried booting and it didn't get to the boot animation so I rebooted to recovery and restored my backup. I'm going to try a stock zip without the modified updater-script and restore my CID to normal and try again.
EDIT
Well, I restored the CID to CWS__001 and I still get that check_cid error
Click to expand...
Click to collapse
To run a ota you need to flash stock recovery image.. and bootloader needs to be unlocked for that
Sent from my HTC One XL using xda premium
31ken31 said:
To run a ota you need to flash stock recovery image.. and bootloader needs to be unlocked for that
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Hm, okay then, let me ask another question. I'm on hboot 1.09 and I need 2.14 to run AOSP ROM's now. What's the best way to get there if I already have ROM's installed. Is it what I'm doing right now or should it be something else?
EDIT
The latest JB RUU is picking up my device now and offering the update, 2 seconds away from doing it....
dshoe said:
Hm, okay then, let me ask another question. I'm on hboot 1.09 and I need 2.14 to run AOSP ROM's now. What's the best way to get there if I already have ROM's installed. Is it what I'm doing right now or should it be something else?
EDIT
The latest JB RUU is picking up my device now and offering the update, 2 seconds away from doing it....
Click to expand...
Click to collapse
Just make sure you are s-off before running ruu or risk a brick..
Sent from my HTC One XL using xda premium
Hi. I am looking my update my hboot from 1.09 to 2.14. I am S-OFF now, also running the Sense 5 rom now(TWRP recovery).
I have downloaded the Latest JB 3.18 RUU from instructions here http://forum.xda-developers.com/showthread.php?t=2064621.
What else do I need to do before flashing the RUU to the device?
For what it's worth, I was on stock 2.20, got s-off and unlocked bootloader with superCID, and ran the 3.18 RUU with no problems. I didn't need to relock or anything.
knanda said:
Hi. I am looking my update my hboot from 1.09 to 2.14. I am S-OFF now, also running the Sense 5 rom now(TWRP recovery).
I have downloaded the Latest JB 3.18 RUU from instructions here http://forum.xda-developers.com/showthread.php?t=2064621.
What else do I need to do before flashing the RUU to the device?
Click to expand...
Click to collapse
You can go ahead and run the RUU. No real risk because you're s-off. Maybe make a backup though.
Sent from my Evita
Ok here it goes, my Sensation was unlocked, rooted, s-off then I had some network issues so I flashed the stock 3.32 RUU from Bell Canada and took it to a local company to fix. So apparently it had a problem and it needed some software fix. Anyways got it back all is good so my question is am I good to flash again? Bootloader is locked but I have s-off, hboot 1.27.000, I know I need to flash a recovery again but my question really is do I have to root again or am I still? and can just flash recovery then a rom and I'm good to go? Thanks :good:
Yeah you're good with just flashing recovery and then a rom, just don't forget to do a full wipe
Sent from my HTC Sensation 4G using Tapatalk 4 Beta
Right on, thanks! Time to get flashing :victory: Hmm don't know, thinking maybe it was a sim issue because after the fix it still didn't work till I got a new one, good thing they didn't charge me, just had to go out and buy a new sim card.
Yeah but I was thinking, wouldn't your fixes be wiped though?
Sent from my HTC Sensation 4G using Tapatalk 4 Beta
I'm wondering what a "software fix" even is, the guy couldn't tell me, he wasn't the one working on it. What could screw with cell and network connections? Firmware, radio, ril? Was thinking of not touching those because other than that I can't think what else would mess up connectivity that wouldn't already be fixed by RUU.
Same thing I was wondering, if it was a software fix, shouldn't it have been pushed by the carrier? But yes firmware, radio, ril can affect network connection.. If you decide to go back to flashing and experience bad connection again I suggest you start messing with radios with their corresponding rils to see which works best for you.. Last time I checked they were for sense ROMs and caused problems on cm and aosp, but you might want to read up on the thread or ask questions if you are unsure about something
Sent from my SGH-T999 using Tapatalk 4 Beta
Thanks for the help, I think I need to start over anyways now. Tried to flash recovery and fastboot gave me an error: Failed(remote: not allowed). Reading up sounds like hboot issue, solution sounds like s-off and root again.
Sent from my HTC-Z710a using xda premium
You should been able to if you are s-off already, never experienced that error before.. Good luck man
Sent from my HTC Sensation 4G using Tapatalk 4 Beta
serio22 said:
You should been able to if you are s-off already, never experienced that error before.. Good luck man
Sent from my HTC Sensation 4G using Tapatalk 4 Beta
Click to expand...
Click to collapse
I recently flashed hboot 1.29, and my new boot loader is locked even with s off. I like it this way, but until I unlock I too get failed error. It's alright
Happy to help.
mistaliu said:
Thanks for the help, I think I need to start over anyways now. Tried to flash recovery and fastboot gave me an error: Failed(remote: not allowed). Reading up sounds like hboot issue, solution sounds like s-off and root again.
Sent from my HTC-Z710a using xda premium
Click to expand...
Click to collapse
you can't use fastboot commands because now you have locked bootloader
the only thing you have to do is flash 3.33 firmware from here
http://forum.xda-developers.com/showthread.php?t=1459767
it will give you also a patched hboot which is unlocked
follow the instructions carefully
and before flashing check md5sums(important)
then you can flash the recovery using fastboot command
rzr86 said:
you can't use fastboot commands because now you have locked bootloader
the only thing you have to do is flash 3.33 firmware from here
http://forum.xda-developers.com/showthread.php?t=1459767
it will give you also a patched hboot which is unlocked
follow the instructions carefully
and before flashing check md5sums(important)
then you can flash the recovery using fastboot command
Click to expand...
Click to collapse
Ahh didn't think of that. Worked like a charm, everything is good now. Thanks for the help guys!