Related
Guys I made a s-off using ControlBear and it crashed!!! so now I can not turn on my phone. Only what can I do is Bootloader and recovery modes. what is the reason of it and is there any solution???
I have requested that a mod move your thread to the Sensation Q&A forum for better device specific assistance.
Did s-off work?
When you say you can get into recovery mode do you mean 4ext or clockworkmod? Or do you mean something else?
If you can get into 4ext or cwm download a new rom and flash it. You should boot right up.
If you can only get to bootloader you can probably update your firmware with a modded version that has a custom recovery included, then proceed to the previous step.
If you need to do the firmware thing you can find all you need in the firmware thread in the development forum.
But....s-off has to have worked in order flash new firmware.
If all else fails you can run an ruu to restore the phone completely to stock and start over.
Sent from my HTC Sensation using xda app-developers app
Skipjacks said:
Did s-off work?
When you say you can get into recovery mode do you mean 4ext or clockworkmod? Or do you mean something else?
If you can get into 4ext or cwm download a new rom and flash it. You should boot right up.
If you can only get to bootloader you can probably update your firmware with a modded version that has a custom recovery included, then proceed to the previous step.
If you need to do the firmware thing you can find all you need in the firmware thread in the development forum.
But....s-off has to have worked in order flash new firmware.
If all else fails you can run an ruu to restore the phone completely to stock and start over.
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
No phone is s-on and I can not change it using any ways. I can enter HBOOT and recovery modes but I tried many roms but no solution. I get errors.
zviadi1987 said:
No phone is s-on and I can not change it using any ways. I can enter HBOOT and recovery modes but I tried many roms but no solution. I get errors.
Click to expand...
Click to collapse
Hey... help....
zviadi1987 said:
Guys I made a s-off using ControlBear and it crashed!!! so now I can not turn on my phone. Only what can I do is Bootloader and recovery modes. what is the reason of it and is there any solution???
Click to expand...
Click to collapse
Hey dude I also failed with JB method and still my sensation is S-ON. You can follow troubleshooting guide at http://unlimited.io/juopunutbear-public-beta-0-1/troubleshooting/
and it really saved my day. Anyways to flash a rom with s-on, simply instal 4EXT recovery and enable SMART-FLASH before installing any rom. It has worked for me
Its my sisters phone, currently stucked at bootsplash screen
I shall post the bootloader information first....
** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHOP S-ON RL
HBOOT-1.14.0002
RADIO-0.19as.32.0909_L
OpenDSP-vs29.1.0.45.0662
eMMc-boot
Jun 11 2012
CID returned is HTC_044... No matter how i flash recovery, the phone simply reboots... means i cant get into recovery mode.
I tried reflashing boot.img from vipers and relash recovery... doesnt work.
Right now, im trying to flash RUU via zip..... I have relocked my bootloader... Current status is that I managed to send the zip file over... but its stucked at writing for the past 10 mins...
This is the RUU where i extracted the rom.zip from
"RUU_EVITA_UL_ICS_40_S_hTC_Asia_WWE_2.23.707.2_Radio_0.19as.32.09.09_L_10.104b.32.25L_release_271654_signed"
It should be the same as my current rom... which if i read correctly, it will not get updated? that I should use the newer 3.17 RUUs for asia in order to fix?
************************ Update ************************
Okay great... now after waiting for 4332 seconds for the writing part to finish... I knew its not going to work via waiting any longer... I unplugged the USB... the command prompt shows up an error (FAILED, too many links)... I attempted to restart the phone from the HTC logo and now it doesnt start at all... cant even get into bootloader... =.=
************************ Update ************************
Okay I've managed to save my phone using this method http://unlimited.io/qhsusbdload.htm
So now im back to square one... I can go bootloader... i unlocked it again... but i still cant go recovery...
************************ Update ************************
Now its back to being bricked again... as I was working on the phone outside when i managed to unbricked it. I choose to power off the phone from bootloader menu, thinking that I could work on it when I get home... alas, when i got home... the phone doesnt turn on... and i saw the dreaded QHSUSB_DLOAD thingy again...... omg... And the above method no longer works..........
kedirakevo said:
Its my sisters phone, currently stucked at bootsplash screen
I shall post the bootloader information first....
** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHOP S-ON RL
HBOOT-1.14.0002
RADIO-0.19as.32.0909_L
OpenDSP-vs29.1.0.45.0662
eMMc-boot
Jun 11 2012
CID returned is HTC_044... No matter how i flash recovery, the phone simply reboots... means i cant get into recovery mode.
I tried reflashing boot.img from vipers and relash recovery... doesnt work.
Right now, im trying to flash RUU via zip..... I have relocked my bootloader... Current status is that I managed to send the zip file over... but its stucked at writing for the past 10 mins...
This is the RUU where i extracted the rom.zip from
"RUU_EVITA_UL_ICS_40_S_hTC_Asia_WWE_2.23.707.2_Radio_0.19as.32.09.09_L_10.104b.32.25L_release_271654_signed"
It should be the same as my current rom... which if i read correctly, it will not get updated? that I should use the newer 3.17 RUUs for asia in order to fix?
Click to expand...
Click to collapse
Stuck in a similar problem not sure what to do...
I dont understand why you guys want to relock and run the ruu... why not just flash a stock rom? Less headache
Sent from my One X using xda app-developers app
If you're relocked then you can't flash the zip. The ruu is an exe you need to run it with your phone in fastboot usb
Sent from my VENOMized HoxL
exad said:
I dont understand why you guys want to relock and run the ruu... why not just flash a stock rom? Less headache
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
how do i flash rom when recovery aint working?
area51avenger said:
If you're relocked then you can't flash the zip. The ruu is an exe you need to run it with your phone in fastboot usb
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1952426
Program says phone's bootloader must be locked in order to flash ruu zip
kedirakevo said:
how do i flash rom when recovery aint working?
Click to expand...
Click to collapse
Unlock boot loader again if its relocked and just fastboot flash twrp.. use the one click tool if you don't know how to flash recovery but as long as boot loader is unlocked you can flash recovery. Once you do, recovery will work again.
Sent from my One X using xda app-developers app
exad said:
Unlock boot loader again if its relocked and just fastboot flash twrp.. use the one click tool if you don't know how to flash recovery but as long as boot loader is unlocked you can flash recovery. Once you do, recovery will work again.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
which i stated in my first post that before relocking my bootloader... I have been reflashing the recovery many times but i cant boot into recovery mode....
kedirakevo said:
which i stated in my first post that before relocking my bootloader... I have been reflashing the recovery many times but i cant boot into recovery mode....
Click to expand...
Click to collapse
When you flash recovery is it successful? When you select recovery from boot loader what happens?
Which recovery and version are you flashing?
Sent from my One X using xda app-developers app
exad said:
When you flash recovery is it successful? When you select recovery from boot loader what happens?
Which recovery and version are you flashing?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
yea command prompt claimed its sucessful... I used the latest all in one toolkit where the creator claimed to use TWRP 2.4.1.0
kedirakevo said:
yea command prompt claimed its sucessful... I used the latest all in one toolkit where the creator claimed to use TWRP 2.4.1.0
Click to expand...
Click to collapse
Maybe A bad download. Download the latest twrp.
Make sure boot loader is unlocked and you have fastboot usb on in bootloader
Then within toolkit pick flash other recovery and manually select the one you downloaded. Then try selecting recovery in bootloader.
Sent from my One X using xda app-developers app
kedirakevo said:
Program says phone's bootloader must be locked in order to flash ruu zip
Click to expand...
Click to collapse
RUU is an exe the fact it creates a rom.zip is fairly well hidden. Are you running the exe or doing some other crazy thing?
You should not be flashing anything to your phone if you are confusing zip and exe's, it means you lack the basic understanding of computers to be able to complete these tasks without failing.
How did you try to flash the recovery? What recovery did you try to flash? What were the errors given?
EDIT: you should not be using one click tools.
Use fastboot and flash recovery yourself, it is a simple task.
exad said:
Maybe A bad download. Download the latest twrp.
Make sure boot loader is unlocked and you have fastboot usb on in bootloader
Then within toolkit pick flash other recovery and manually select the one you downloaded. Then try selecting recovery in bootloader.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
wish I could try that... it bricked now.
twistedddx said:
RUU is an exe the fact it creates a rom.zip is fairly well hidden. Are you running the exe or doing some other crazy thing?
You should not be flashing anything to your phone if you are confusing zip and exe's, it means you lack the basic understanding of computers to be able to complete these tasks without failing.
How did you try to flash the recovery? What recovery did you try to flash? What were the errors given?
EDIT: you should not be using one click tools.
Use fastboot and flash recovery yourself, it is a simple task.
Click to expand...
Click to collapse
the zip file can be obtained via temp folder of the windows directory when you run the exe file.
The all in one toolkit requires the zip so I got it done via that method...
Yes I know how to do it via command prompt but the toolkit is handy...
And lastly you can say my understanding of mobile phone system isnt complete but dont insult me saying I dont understand whats zip and exe......
Bricked? Exactly what is happening.
Sent from my One X using xda app-developers app
exad said:
Bricked? Exactly what is happening.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
beats me man... Told you, was trying to flash RUU through zip then it just hung there... but I managed to save my phone... I redownloaded and reflashed recovery as you advised but still no avail! Basically, back to square one....
kedirakevo said:
the zip file can be obtained via temp folder of the windows directory when you run the exe file.
The all in one toolkit requires the zip so I got it done via that method...
Yes I know how to do it via command prompt but the toolkit is handy...
And lastly you can say my understanding of mobile phone system isnt complete but dont insult me saying I dont understand whats zip and exe......
Click to expand...
Click to collapse
I know it can be obtained from temp folder.
Why go to the effort of getting the rom.zip to use in the toolkit when you could simply just run the RUU, which you had to do to get the rom.zip in the first place? Especially when it was failing, why push on with trying to use the toolkit instead of just using the RUU as it was intended by HTC?
I have not much knowledge of the toolkit, but when it flashes zip's is it for normal ROM's or for RUU rom.zip? The rom.zip is not in a format that can normally be used by most tools, it is not the same as flashing a custom ROM.
The toolkit is likely only for installing custom ROM's via pre installed TWRP and not compatible with rom.zip.
You said you were using a RUU zip and complaining it was failing, it appeared at face value you were confusing what the RUU even is.
I am still lost why running the RUU and grabbing the rom.zip from temp folder and then flashing in a toolkit was your chosen method. This just points more towards you are confused about what a RUU is.
I am sure the RUU would work if you just let it run like it is supposed to.
---------- Post added at 02:33 PM ---------- Previous post was at 02:23 PM ----------
kedirakevo said:
was trying to flash RUU through zip then it just hung there.
Click to expand...
Click to collapse
Why?
Personally because of the state you have got the phone in to I would:
1)go get the correct tools. eg fastboot, unlockcode, twrp and rom
2)Ensure phone is charged
3)fastboot oem lock
4)Run RUU.. and try actually running it which means just click next and yes a lot.. no fancy going to temp folders and trying to incorrectly install rom.zip via random tools
5)fastboot flash unlocktoken Unlock_code.bin
6)fastboot flash recovery openrecovery-twrp-2.4.1.0-evita.img
7)fastboot flash boot boot.img (from desired rom)
8)boot into recovery
9)mount USB and transfer desired ROM
10)wipe data and system
11)install ROM
12)reboot in to ROM.
twistedddx said:
I know it can be obtained from temp folder.
Why go to the effort of getting the rom.zip to use in the toolkit when you could simply just run the RUU, which you had to do to get the rom.zip in the first place? Especially when it was failing, why push on with trying to use the toolkit instead of just using the RUU as it was intended by HTC?
I have not much knowledge of the toolkit, but when it flashes zip's is it for normal ROM's or for RUU rom.zip? The rom.zip is not in a format that can normally be used by most tools, it is not the same as flashing a custom ROM.
The toolkit is likely only for installing custom ROM's via pre installed TWRP and not compatible with rom.zip.
You said you were using a RUU zip and complaining it was failing, it appeared at face value you were confusing what the RUU even is.
I am still lost why running the RUU and grabbing the rom.zip from temp folder and then flashing in a toolkit was your chosen method. This just points more towards you are confused about what a RUU is.
I am sure the RUU would work if you just let it run like it is supposed to.
---------- Post added at 02:33 PM ---------- Previous post was at 02:23 PM ----------
Why?
Personally because of the state you have got the phone in to I would:
1)go get the correct tools. eg fastboot, unlockcode, twrp and rom
2)Ensure phone is charged
3)fastboot oem lock
4)Run RUU.. and try actually running it which means just click next and yes a lot.. no fancy going to temp folders and trying to incorrectly install rom.zip via random tools
5)fastboot flash unlocktoken Unlock_code.bin
6)fastboot flash recovery openrecovery-twrp-2.4.1.0-evita.img
7)fastboot flash boot boot.img (from desired rom)
8)boot into recovery
9)mount USB and transfer desired ROM
10)wipe data and system
11)install ROM
12)reboot in to ROM.
Click to expand...
Click to collapse
well... as mentioned, would really love to follow your steps but.... its bricked now... again...
I did run RUU.exe once but it hung for 30 mins without activity... but then again that was when my bootloader was unlocked... then i read that i can relock and do it through ruu.zip instead.... so i went that route.......
Btw I did update my status on my first post...
kedirakevo said:
well... as mentioned, would really love to follow your steps but.... its bricked now... again...
I did run RUU.exe once but it hung for 30 mins without activity... but then again that was when my bootloader was unlocked... then i read that i can relock and do it through ruu.zip instead.... so i went that route.......
Btw I did update my status on my first post...
Click to expand...
Click to collapse
The least risky way would be to flash a stock ROM from here not an ruu. There are some untouched roms. I, myself have bricked running the telus ruu.
Sent from my One X using xda app-developers app
Ok first things first.. this all is what I did and what's my present situation
1. Unlocked the boooader as per the htc dev site instructions.
2. Tried to soff using jbear method. Every thing went fine untill the jbear utility gave command to restart the device.
After restart, jbear utility failed to recognise the device. It said device not detected, please install device drivers.
3. From that moment onwards, the device is stuck at the white htc bootscreen.
4. I also followed another guide to install custom recovery and custom rom without s off.
I was able to flash a custom recovery, and even the rom. But the device won't move ahead of the bootscreen.
5. Then tried to return to stock using ruu file. But my region ruu is still not available so that method didnt work(3.33.xx.xx asia india).
Have also tried a few more methods but none seem to work.
Help guys.
Phone info:
s-on
Cid 038
bootloader:1.27.0000 unlocked
b band:11.24A.3504.31_M
version main:3.33.720.6
model: PG58813000
Note:Fastboot usb mode seems to work fine.
PS:solution on second page
walkermoon said:
Ok first things first.. this all is what I did and what's my present situation
1. Unlocked the boooader as per the htc dev site instructions.
2. Tried to soff using jbear method. Every thing went fine untill the jbear utility gave command to restart the device.
After restart, jbear utility failed to recognise the device. It said device not detected, please install device drivers.
3. From that moment onwards, the device is stuck at the white htc bootscreen.
4. I also followed another guide to install custom recovery and custom rom without s off.
I was able to flash a custom recovery, and even the rom. But the device won't move ahead of the bootscreen.
5. Then tried to return to stock using ruu file. But my region ruu is still not available so that method didnt work(3.33.xx.xx asia india).
Have also tried a few more methods but none seem to work.
Help guys.
Phone info:
Cid 038
bootloader:1.27.0000
Note:Fastboot usb mode seems to work fine.
b band:11.24A.3504.31_M
version main:3.33.720.6
model: PG58813000
Click to expand...
Click to collapse
Try to make superCID and install RUU or search for 3.32 RUU
Or try flashing http://forum.xda-developers.com/showthread.php?t=1459767&highlight=universal firmware from here 3.33 (there is 058 CID)
TNGrawer said:
Try to make superCID and install RUU or search for 3.32 RUU
Or try flashing http://forum.xda-developers.com/showthread.php?t=1459767&highlight=universal firmware from here 3.33 (there is 058 CID)
Click to expand...
Click to collapse
he has to be on S-OFF to flash a firmware from bootloader and i don't think he achieved S-OFF
what he must to do is enable smartflash from 4ext(if you don't have that recovery use this one)
then flash the rom
rzr86 said:
he has to be on S-OFF to flash a firmware from bootloader and i don't think he achieved S-OFF
what he must to do is enable smartflash from 4ext(if you don't have that recovery use this one)
then flash the rom
Click to expand...
Click to collapse
Yeah exactly.. device is still s–on. And thats what is causing all the troubles i guess. Can't flash europe or asia ruu(cid error).
And i have tried enabling smartflash. Flashed the android revolution rom. Installed fine. But still stuck on bootscreen.
And as I am not s–off, so i dont think 3.32 ruu would work. Correct me if i'm wrong.
Try flashing boot.IMG manually.
I don't exactly remember the fast boot command but since fast boot commands are working then you can try flashing the boot image manually.
Sent from my Ouya
And where do i get this boot image? From ruu?
Sent from my GT-I9100G using xda premium
Not gonna try and bombard you with information I'm not sure why your phone won't boot but I am sure completely installing a new rom (everything) should fix you up so here is what I'll try and lead you to go..
1 use 4ext recovery and enable smart flash and flash a fresh rom.
So are u on 4ext recovery don't worry if your not that HTC unlocked bootloader is just as good as s-off if your bricked and know how to use it
Sent from my HTC Sensation Z710e using xda app-developers app
Get the boot image from the custom ROM. Try to extract it with 7-zip or another similar program
Sent from my Ouya
In the college right now.. give you update as soon as I reach home.
walkermoon said:
In the college right now.. give you update as soon as I reach home.
Click to expand...
Click to collapse
also before flashing any rom
format all partitions except sdcard from 4ext
then enable smartflash and flash the rom
Still no luck
Ok.. i decided to flash a custom rom (ANDROID REVOLUTION)
1. Flashed 4ext recovery
2. Wiped all partitions except sd card.
3. Enabled smartflash.
4. Flashed rom.
5. Rebooted and still stuck at the htc logo screen( m really sick of this logo now).
Did I miss something?
You know those official updates that cone in a format P8500IMG.zip can you try to find that for your phone unfortunately this will probably result in loss of your root
Sent from my HTC Sensation Z710e using xda app-developers app
Cheers guys.. Its back to life again
DON'T HAVE WORDS TO THANK YOU ALL.
Here's what I did..
From my experience.. i believe even after enabling smartflash, the boot image wasn't being flashed.
So what I did is extracted the boot. img from custom rom and flashed it via fastboot.
And voila.. it worked!!
Seems so simple now.. but it took me one week. Wouldn't have been possible without you guys.
Thanks a ton.
Cheers.
AndroidSupporter318 said:
Try flashing boot.IMG manually.
I don't exactly remember the fast boot command but since fast boot commands are working then you can try flashing the boot image manually.
Sent from my Ouya
Click to expand...
Click to collapse
xanda143 said:
Not gonna try and bombard you with information I'm not sure why your phone won't boot but I am sure completely installing a new rom (everything) should fix you up so here is what I'll try and lead you to go..
1 use 4ext recovery and enable smart flash and flash a fresh rom.
So are u on 4ext recovery don't worry if your not that HTC unlocked bootloader is just as good as s-off if your bricked and know how to use it
Sent from my HTC Sensation Z710e using xda app-developers app
Click to expand...
Click to collapse
AndroidSupporter318 said:
Get the boot image from the custom ROM. Try to extract it with 7-zip or another similar program
Sent from my Ouya
Click to expand...
Click to collapse
rzr86 said:
also before flashing any rom
format all partitions except sdcard from 4ext
then enable smartflash and flash the rom
Click to expand...
Click to collapse
Thank you all. Actually all these tips lead to the solution.
Hello,
I am trying to flash CleanRom 7.0 or any JB rom on my HTC One X (AT&T) but always gets stuck in bootloop (phone does not go past boot screen after flashing). This is what i have done.
The phone is on AT&T 1.82 stock room (rooted, SuperCID, S-Off). The phone was on some older HBoot version so I upgraded it to 2.15. Radio is 0.17.32.09.12. And I have TWRP recovery.
So I made a nadroid backup in recovery and than tried to install AT&T 3.82 rooted (downloaded from XDA, may be without radio and all). After successful flashing when I tried to reboot the system it got stuck on AT&T boot screen. So I rebooted in recovery and wiped everything. After that I tried to install CleanROM 7.0 R2 and same thing happened and even I tried latest elemental kernel but same thing is keep happening.
Can you please help me with this?
Thanks
At&t 3.82 rooted ROM? Where did you download that? It doesn't look familiar. What are your bootloader details? Which version of TWRP? How did you upgrade your hboot?
Sent from my Evita
timmaaa said:
At&t 3.82 rooted ROM? Where did you download that? It doesn't look familiar. What are your bootloader details? Which version of TWRP? How did you upgrade your hboot?
Sent from my Evita
Click to expand...
Click to collapse
Hey,
Thanks for reply. Sorry I think I mis-wrote it. It's AT&T 3.18 ROM from following link:
http://forum.xda-developers.com/showthread.php?t=2181891
I will check and let you know TWRP version when I get back home. I am not sure about the bootloader details either, what you need to know about the boot loader to help me?
I upgraded hboot by upgrading firmware to 2.15 by using instructions at one of the threads at xda (using adb and fastboot commands and pushing a 2.15 zip to device when it is in bootloader).
Note that I was never able to install any custom ROM on HTC One X. I rooted it before a year or so tried to install CleanROM 5.1 (I guess) but it din't work. I also tried few other ROMs but nothing worked and I gave up. Recently I read that I may need to update Hboot to flash the ROMs. So I did it (had a hard time installing drivers on windows 8 and ultimately have to try winXP!). Still after all this it is not working.
Let me know if you can suggest something based on this.
Thanks
alex8525 said:
Hey,
Thanks for reply. Sorry I think I mis-wrote it. It's AT&T 3.18 ROM from following link:
http://forum.xda-developers.com/showthread.php?t=2181891
I will check and let you know TWRP version when I get back home. I am not sure about the bootloader details either, what you need to know about the boot loader to help me?
I upgraded hboot by upgrading firmware to 2.15 by using instructions at one of the threads at xda (using adb and fastboot commands and pushing a 2.15 zip to device when it is in bootloader).
Note that I was never able to install any custom ROM on HTC One X. I rooted it before a year or so tried to install CleanROM 5.1 (I guess) but it din't work. I also tried few other ROMs but nothing worked and I gave up. Recently I read that I may need to update Hboot to flash the ROMs. So I did it (had a hard time installing drivers on windows 8 and ultimately have to try winXP!). Still after all this it is not working.
Let me know if you can suggest something based on this.
Thanks
Click to expand...
Click to collapse
Ok so you need to give us more info
Are you s-off
What version of twrp do you have
These things matter when you flash a rom. If you are s-on you need to flash boot.img after flashing. Just do
Fastboot flash boot.img
Sent from my HTC Butterfly s using Tapatalk
phonegeekjr said:
Ok so you need to give us more info
Are you s-off
What version of twrp do you have
These things matter when you flash a rom. If you are s-on you need to flash boot.omg after flashing.
Sent from my HTC Butterfly s using Tapatalk
Click to expand...
Click to collapse
Yes I am S-Off. I will let you know the version of TWRP when I get back home since I don't have phone with me right now. By the way I used goomanager to update TWRP, if that helps.
Thanks,
phonegeekjr said:
Ok so you need to give us more info
Are you s-off
What version of twrp do you have
These things matter when you flash a rom. If you are s-on you need to flash boot.img after flashing. Just do
Fastboot flash boot.img
Sent from my HTC Butterfly s using Tapatalk
Click to expand...
Click to collapse
One more thing, I am using TWRP to flash the ROM. Is it a correct way? or I need to flash it using fastboot commands (like you suggested for boot.img)?
I am not much fammilier with TWRP and HTC One X so.
Thanks
K so if you are s-off then you can just flash it. If you wernt then you would need to flash boot.img. now you can try to flash the boot.img. it might not fix it but start small and work up.
Sent from my HTC Butterfly s using Tapatalk
alex8525 said:
One more thing, I am using TWRP to flash the ROM. Is it a correct way? or I need to flash it using fastboot commands (like you suggested for boot.img)?
I am not much fammilier with TWRP and HTC One X so.
Thanks
Click to expand...
Click to collapse
TWRP is the correct way to install ROMs, but I have a feeling that your current version of TWRP is your problem. Some (2.4.x, 2.5.x) are buggy and have major problems. If your TWRP version is either of those that I've just mentioned you can update it to a known bug-free version like this:
Download the modified version of TWRP*2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Sent from my Evita
That's the reason I asked what twrp version he had
Sent from my HTC Butterfly s using Tapatalk
I am trying to restore my device to stock but i am unable to. Im trying to use the ruu. but i keep getting the 155 error. I relocked my bootloader but its not working. im using a telus htc one. My hboot is: 2.15.000 and radio 1.13.50.05.31. No os btw
But i can get to the bootloader
I might be wrong, but as far as I'm aware, it can't work on a locked bootloader, so you'll need to unlock it again.
Make sure you're using the correct ruu, double read the instructions for flashing it...
That's the most I can say, I don't really have that much experience in this.
Also, another option will be to send the stock ROM.zip to the phone using adb, flash a custom recovery, and boot into recovery and flash the ROM.
i could have swore that it needed to be locked. and to do adb,i need a os
still doesnt work
izzyisawesome said:
i could have swore that it needed to be locked. and to do adb,i need a os
Click to expand...
Click to collapse
If you already have a custom recovery, you can use adb there without an os
Sent from my XT1032 using XDA Free mobile app
The suggestion to relock the bootloader seems to be confirmed by this post: http://forum.xda-developers.com/showthread.php?t=1655832
If you didn't do it, you also need to restore the stock recovery.
Do you still have error 155?
tzzeri said:
If you already have a custom recovery, you can use adb there without an os
Sent from my XT1032 using XDA Free mobile app
Click to expand...
Click to collapse
Whenever i install a custom recovery, it doesnt show up
kdd998 said:
The suggestion to relock the bootloader seems to be confirmed by this post: http://forum.xda-developers.com/showthread.php?t=1655832
If you didn't do it, you also need to restore the stock recovery.
Do you still have error 155?
Click to expand...
Click to collapse
I relocked the bootloader. I installed the stock recovery,from another post. i am pretty sure its the right one. yes i keep getting that error
If you want to be sure of the recovery you can find the good one in the RUU. You'll find guides to get the firmware.zip from the RUU on XDA.
Same problem here. Anyone have a android backup I can try?