Related
Hello, I have a T-Mobile HTC Sensation 4G, and I've ran into some problems recently. I'm a basic-intermediate user when it comes to Android, but I can't find a solution specifically for this. It started with a small problem but got worse and worse until I couldn't even boot correctly.
I started out installing a small custom battery mod, but that led to a few problems with the notification bar (not a big deal).
Then I tried to revert to the stock battery to fix the problem, format cache and dalvik cache in recovery, and reset. Then I was put into an infinite boot loop with the HTC splash, but going into cwm recovery was still possible.
Then, in recovery, I could not access my sd card for some reason, so I shut off, reinserted the sd card, and remounted it, then I reset again.
Now, it's impossible to boot to android at all, and I am completely stuck at HBOOT/FASTBOOT, and cannot access recovery OR perform a hard reset.
If I try to reinstall cwm recovery, I get a partition update fail as well...
I have full root, s-off, etc.
ROM- InsertCoin 3.3.1
Kernel- Stock
Hboot- 1.17.1011
Clockwork version- 5.0.0.8
Any suggestions? Am I bricked? I can give more details if needed.
I think you could take a official RUU and rename to the same as if you were trying to flash CWR pm58img or whatever it is.... Don't have my files with me. It should reformat to stock. Hope it helps.
Sent from my HTC Sensation XE with Beats Audio using xda premium
neoissuperman said:
I think you could take a official RUU and rename to the same as if you were trying to flash CWR pm58img or whatever it is.... Don't have my files with me. It should reformat to stock. Hope it helps.
Sent from my HTC Sensation XE with Beats Audio using xda premium
Click to expand...
Click to collapse
Alright, thanks, I'll try that soon and see if it works.
Update: Unfortunately, I don't think I can flash anything, it just comes up with a partition update fail...
Anyone else know what I could try? I also tried to flash the 1.45 RUU, but it can't continue past the search for the bootloader.
If u can get to fastboot have u tried manually flashing recovery.img ie
Fastboot flash recovery recovery.img
This should work if u can get into fastboot and allow u to then get back to a recovery and may save ya life lol
Sent from my mind control device
joshndroid said:
If u can get to fastboot have u tried manually flashing recovery.img ie
Fastboot flash recovery recovery.img
This should work if u can get into fastboot and allow u to then get back to a recovery and may save ya life lol
Sent from my mind control device
Click to expand...
Click to collapse
I just tried that, but I get this error in the terminal-
"writing 'recovery'... FAILED (remote: image update error)"
I tried adb devices, and it's not even recognized, even though my sensation says FASTBOOT USB...
have you tried re-installing the drivers...
http://forum.xda-developers.com/showthread.php?t=1161769
from here to see if the phone will re-mount the phone...
also have you tried adb remount... see if that works?
personally im running out of ideas
joshndroid said:
have you tried re-installing the drivers...
http://forum.xda-developers.com/showthread.php?t=1161769
from here to see if the phone will re-mount the phone...
also have you tried adb remount... see if that works?
personally im running out of ideas
Click to expand...
Click to collapse
Nope, still nothing, I even tried different sd cards and usb cables, with no difference...
So has my phone been reduced to a paperweight?
APmoss13 said:
I just tried that, but I get this error in the terminal-
"writing 'recovery'... FAILED (remote: image update error)"
I tried adb devices, and it's not even recognized, even though my sensation says FASTBOOT USB...
Click to expand...
Click to collapse
ummmm just a quick questions.... if you are on the fastboot screen and at the top it says fastboot usb have you tried running the ruu from there and are you scid? what carrier are you on? also in another post above this you said the bootloader doesnt get past the searching files, im wondering if you left the .zip that says pm58img on the root of your sd card. that could be the reason it doesnt get past that screen. just trying to get more info to see if we can get more help for you.
Divine flaw said:
ummmm just a quick questions.... if you are on the fastboot screen and at the top it says fastboot usb have you tried running the ruu from there and are you scid? what carrier are you on? also in another post above this you said the bootloader doesnt get past the searching files, im wondering if you left the .zip that says pm58img on the root of your sd card. that could be the reason it doesnt get past that screen. just trying to get more info to see if we can get more help for you.
Click to expand...
Click to collapse
Yes, I have tried to flash the 1.45 Pyramid RUU, but when the RUU tries to reset my phone into bootloader, it just resets right back into fastboot (the RUU command stays at "waiting for bootloader"). I am also super cid and my carrier is US T Mobile. I made sure not to leave the update package on my sd card, and I even tried the RUU without an sd card at all, but no difference.
APmoss13 said:
Yes, I have tried to flash the 1.45 Pyramid RUU, but when the RUU tries to reset my phone into bootloader, it just resets right back into fastboot (the RUU command stays at "waiting for bootloader"). I am also super cid and my carrier is US T Mobile. I made sure not to leave the update package on my sd card, and I even tried the RUU without an sd card at all, but no difference.
Click to expand...
Click to collapse
ok.... i was just askin cause did the exact same thing (well almost, i tried to change the notification icons which resulted in my notification bar completely gone) you did and got into that infinite boot loop. and couldnt boot into android. and couldnt figure it out. the only thing i did was just install the ruu while i was in the fastboot screen and it worked. i wasnt aware that there was a 1.45 ruu for tmous but i dont think that should matter since you are scid anyways. now im just wonderin if you tried any other ruu's besides that one. for me i flashed the 1.29 ruu for tmous and that got me up and running...... sorry i couldnt help
Hi Everyone,
So i followed all the steps to temp root 2.20 including successfully installing TWRP (Team Win Recovery Project). I then downloaded the CM10 rom and extracted the boot.img as per posts and rebooted into the bootloader and flashed the boot.img from CM10 via Fastboot. However after doing then rebooting to Recovery mode in order to flash the ROM, i get stuck in the red text where it gives you a warning about it being in development mode or something.
I am able to successfully boot into the bootloader via Power+down volume. Additionally I am able to boot into the TWRP recovery just fine, however I am lost and have no clue how to restore my phone to either the CM10 ROM or most importantly at least to stock working condition.
When i got to mount the SDCARD via twrp normally i would get a pop up on my screen and allow me to access my SD card, now i get a pop up just telling me that i need to format my SD card first. I'm afraid some how my SD card got wiped or something.
Can someone please walk me through the steps on how to restore my phone. Please if possible i would appreciate using LAME terms as i do not have any experience as you can tell i screwed up :/ Can you please listed step by step instructions including commands for Fastboot/adb etc etc if needed. Thank you very much for your help and support.
I've typed and retyped a response to help. I'm so tired and my brain is mush. (More so than normal) if you can't find any resolution by morning? Pm me and I'll try and help. Something about pluggin the USB in The back of your pc something something....... snore
Sent from my One X using xda premium
subarudroid said:
I've typed and retyped a response to help. I'm so tired and my brain is mush. (More so than normal) if you can't find any resolution by morning? Pm me and I'll try and help. Something about pluggin the USB in The back of your pc something something....... snore
Sent from my One X using xda premium
Click to expand...
Click to collapse
I know you tried to help, but it appears now I have bricked the phone. Hopefully i can fix it as i still have access to Bootloader and TWRP recovery. I'll PM you in the morning, thank you.
dont factory reset in bootloader. only factory reset in twrp. sometimes evita has a hard time getting into recovery from bootloader. just keep trying to get into recovery from bootloader. also even if your phone doesn't boot all the way adb sometimes still works. so try "adb reboot recovery" while its trying to boot.
if you did corrupt your sdcard try this method to get it fixed without having to run ruu.
[How to] Fix corrupt/unmountable internal storage on the HTC One X/XL
when you get your sdcard fixed remember to wipe everything and then copy cm10 and gapps to your sdcard and flash. since boot.img is already flashed you shouldn't need to do it again.
you did flash boot.img as "fastboot flash boot boot.img"? i made the mistake of flashing boot.img to recovery instead of boot. i was freaking out. just to make sure flash recovery again "fastboot flash recovery openrecovery-twrp-2.3.1.0-evita.img"
DvineLord said:
dont factory reset in bootloader. only factory reset in twrp. sometimes evita has a hard time getting into recovery from bootloader. just keep trying to get into recovery from bootloader. also even if your phone doesn't boot all the way adb sometimes still works. so try "adb reboot recovery" while its trying to boot.
if you did corrupt your sdcard try this method to get it fixed without having to run ruu.
[How to] Fix corrupt/unmountable internal storage on the HTC One X/XL
when you get your sdcard fixed remember to wipe everything and then copy cm10 and gapps to your sdcard and flash. since boot.img is already flashed you shouldn't need to do it again.
you did flash boot.img as "fastboot flash boot boot.img"? i made the mistake of flashing boot.img to recovery instead of boot. i was freaking out. just to make sure flash recovery again "fastboot flash recovery openrecovery-twrp-2.3.1.0-evita.img"
Click to expand...
Click to collapse
Yes i did fastboot flash boot boot.img from within the Bootlader. FYI that boot.img was from inside the CM10 zip file. I belive my SD card is corrupt i will check out that link. FYI I am able to get into Recovery mode form the Boatloader if i chooser recovery. However since the SD card seems messed up i can't access it currently. Also I tried to use the method to install the CM10.zip file using TWRP recovery. That recovery has a GUI and you can click on the INSTALL button and choose the zip file you want to install, however it errors out.
What is the proper way to flash a rom when i am in the TWRP recovery? Can you provide me with the commands/steps? Thanks for all your support guys.
movadoevo8 said:
Yes i did fastboot flash boot boot.img from within the Bootlader. FYI that boot.img was from inside the CM10 zip file. I belive my SD card is corrupt i will check out that link. FYI I am able to get into Recovery mode form the Boatloader if i chooser recovery. However since the SD card seems messed up i can't access it currently. Also I tried to use the method to install the CM10.zip file using TWRP recovery. That recovery has a GUI and you can click on the INSTALL button and choose the zip file you want to install, however it errors out.
What is the proper way to flash a rom when i am in the TWRP recovery? Can you provide me with the commands/steps? Thanks for all your support guys.
Click to expand...
Click to collapse
install/install from zip/browse to your zip/slide to flash (they really should patent that)
now most of us, to do a clean flash, we'd go into the "wipe" menu in TWRP before flashing , factory reset, wipe cache, wipe dalvik cache, wipe system. then we flash our rom.
hope that cleared it up!
Sent from my One X using xda premium
You won't be able to flash anything until you fixed your sdcard using the method in that link.
Ptesmoke where have you been? DvineLord is the only one been helping here. The Q&A thread is a mess. where is edditsync chongo, rohan and the other superhero's. I feel like Hawkeye trying to shoot sh#@ down with a bow and arrow. Waiting for ironman, hulk, Thor and the other avengers to get real sh#@ done. I'm tired going to sleep now.
Sent from my One X using xda premium
ptesmoke said:
install/install from zip/browse to your zip/slide to flash (they really should patent that)
now most of us, to do a clean flash, we'd go into the "wipe" menu in TWRP before flashing , factory reset, wipe cache, wipe dalvik cache, wipe system. then we flash our rom.
hope that cleared it up!
Sent from my One X using xda premium
Click to expand...
Click to collapse
I tried to fixed corrupted SD card as per video. however after flashing the recovery.img via fastboot when it wants me to do a factory reset instead of doing the factory reset it just goes back to the HTC brilliant screen with the red warning text and sits there. If i go to twpr recovery and click on install i can't access me zip currently due to sd card issues.
Is there a way to format via PC since it lets me as long as I am in twpr and just put stock files/folders onto the SD card? Or is it possible to install the 2.20 ruu again? I re-downloaded it form HTC's site while I am in twrp however I cannot install it won't detect my phone. Thanks for your help.
"fastboot oem lock" then run ruu. ruu gets run in fastboot.
after the ruu, reunlock bootloader and flash twrp, copy cm10 and gapps to your sdcard, flash boot.img in fastboot, wipe everything except for external storage in twrp, flash cm10 and gapps in twrp, then reboot.
If you can get into twrp and go to mount, mount usb storage and connect your phone windows should prompt you to format the SD card.
Once that's done you can drag and drop the rom you want to flash then boot into fastboot and flash the boot.img.
If you want to run the ruu you need to relock the bootloader first.
To do that you must go into fastboot usb and then type fastboot oem lock.
Sent from my HTC One XL using xda premium
DvineLord said:
"fastboot oem lock" then run ruu. ruu gets run in fastboot.
after the ruu, reunlock bootloader and flash twrp, copy cm10 and gapps to your sdcard, flash boot.img in fastboot, wipe everything except for external storage in twrp, flash cm10 and gapps in twrp, then reboot.
Click to expand...
Click to collapse
I'm sorry i'm not too tech savy. Can you clarify how to Fastboot OEM lock. Assuming i just need to be in fastboot mode and run a command in command prompt?
Also once that is done how can i run RUU via fastboot? Right now i have HTC RUU for 2.20 from august that i downloaded from their site and not sure how i can have it detect my phone. If you could clarify and explain those steps in Lame terms i would greatly appreciate it, thanks in advance.
movadoevo8 said:
I'm sorry i'm not too tech savy. Can you clarify how to Fastboot OEM lock. Assuming i just need to be in fastboot mode and run a command in command prompt?
Also once that is done how can i run RUU via fastboot? Right now i have HTC RUU for 2.20 from august that i downloaded from their site and not sure how i can have it detect my phone. If you could clarify and explain those steps in Lame terms i would greatly appreciate it, thanks in advance.
Click to expand...
Click to collapse
That's the command you do and the ruu is an exe file so get into fastnoot on your phone from bl and run the ruu after you've locked the bootloader
Thank you both will try that now.
Hey guys thanks for all your help and your support it worked. I had the wrong CM10 file instead of Evita i had the other one :/ That was the issue all along ugh... but all resolved could of not have done it without your support. Thanks!! I can now finally go to bed.. been at it since 10pm, now 3:11am
Maybe you can help me . I'm having the same problem. The problem is, everytime I try to use any fastboot commands, it'll say "waiting for device". I'm stressing out.
marcur12 said:
Maybe you can help me . I'm having the same problem. The problem is, everytime I try to use any fastboot commands, it'll say "waiting for device". I'm stressing out.
Click to expand...
Click to collapse
Make sure you have the right drivers installed, download the latest htc sync from htc's website.
Install HTC sync connect phone and let the drivers install, then make sure you close htc sync from the system tray and try again.
Like DvineLord said below make sure you're in the bootloader then select Fastboot once selected it should say in red writing Fastboot USB.
fastboot only works in bootloader btw
Hit the thanks button for the people helping you fix your boo boos.
If you can type it, click it for them, least you can do in return.
WR
Sent from my HTC One X
Sent from my HTC One XL using Tapatalk 2
Today I flashed the last CleanRom 5.1 then I flashed kernel BeastMode evita 4.4 and the phone has bricked in the screen of HTC. So I did a big mistake, in the bootlloader i am pretty sure I have wiped the phone, now I have no ROM in the phone, and the TWRP will not let me select mount sd card. I have thinking in push the ROM in ADB but sincerely I have no idea how to do that. Actually I´m in the bootloader screen and connected the phone, appearing "Fastboot USB". Could someone kindly tell me what are the orders in the Command Prompt to connect the phone to my pc and push the rom?
The phone was with CM10 ROM, rooted and TWRP provided by a friend who is not available to help me.
BTW sorry for my regular english, I´m from Argentina.
juanfranrod said:
Today I flashed the last CleanRom 5.1 then I flashed kernel BeastMode evita 4.4 and the phone has bricked in the screen of HTC. So I did a big mistake, in the bootlloader i am pretty sure I have wiped the phone, now I have no ROM in the phone, and the TWRP will not let me select mount sd card. I have thinking in push the ROM in ADB but sincerely I have no idea how to do that. Actually I´m in the bootloader screen and connected the phone, appearing "Fastboot USB". Could someone kindly tell me what are the orders in the Command Prompt to connect the phone to my pc and push the rom?
The phone was with CM10 ROM, rooted and TWRP provided by a friend who is not available to help me.
BTW sorry for my regular english, I´m from Argentina.
Click to expand...
Click to collapse
My First advice, relock bootloader and run ruu...If your on the newer hboot don't you have to flash boot.img as well before flashing the rom? Did you wipe cashe and dalvik when you flashed? Did you see if rom first worked before flashing kernel?
WhatTheAndroid? said:
My First advice, relock bootloader and run ruu...If your on the newer hboot don't you have to flash boot.img as well before flashing the rom? Did you wipe cashe and dalvik when you flashed? Did you see if rom first worked before flashing kernel?
Click to expand...
Click to collapse
I have flashed boot.img in the aroma installer of cleanrom. Then I wipe cache and dalvik after flash rom. But I made the mistake of not checking if it worked the ROM before installing the new kernel.. I installed after the rom.
Could you explain me how to relock bootloader and run ruu?
Appreciate your help
juanfranrod said:
I have flashed boot.img in the aroma installer of cleanrom. Then I wipe cache and dalvik after flash rom. But I made the mistake of not checking if it worked the ROM before installing the new kernel.. I installed after the rom.
Could you explain me how to relock bootloader and run ruu?
Appreciate your help
Click to expand...
Click to collapse
I'm sure someone will provide a ruu download based on your phone. Fastboot oem lock command in fastboot to lock bootloader. I would wait though to see if there is still a way to flash Rom and mount your phones sd card.by the way did you create a recovery in twrp of stock rooted version?
You dont need to RUU. I don't know why everyone runs to that.
Open TWRP, mount usb storage.
If you're on windows, it should prompt you to format your sd card. Format it to fat32.
Copy whatever rom you want onto the card.
Install in TWRP.
Dance
He wiped his phone from bootloader... Therefore corrupting his SD card. He could adb push the rom to his card though
Sent from my One X using xda app-developers app
WhatTheAndroid? said:
I'm sure someone will provide a ruu download based on your phone. Fastboot oem lock command in fastboot to lock bootloader. I would wait though to see if there is still a way to flash Rom and mount your phones sd card.by the way did you create a recovery in twrp of stock rooted version?
Click to expand...
Click to collapse
Myrder said:
He wiped his phone from bootloader... Therefore corrupting his SD card. He could adb push the rom to his card though
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Hi, I still cannot solving my problem :/ I locked the phone with the command "fastboot oem lock" in fastboot. Then I downloaded a RUU called htc_one_x_RUU_2.20.502.7_att_us_08022012.exe and I´ve executed the file in fastboot but appears during the installation process an error message that the phone is not connected with the USB cable, when obviously connected.
I have no idea what to do, I tried to check the connections, right now I'm trying to download another RUU apparently compatible, my CID is 11111111 and my HBOOT is 1.09.0000. Can you think of anything else I can do?
juanfranrod said:
Can you think of anything else I can do?
Click to expand...
Click to collapse
Did you reformat your SD card?
iElvis said:
Did you reformat your SD card?
Click to expand...
Click to collapse
Yes, I did it. I will try with another RUU (1.85) and see what happens.. for now I accept suggestions. Thanks
Your hboot is 1.09 which means you need the 1.85 firmware
area51avenger said:
Your hboot is 1.09 which means you need the 1.85 firmware
Click to expand...
Click to collapse
Newer RUU version should still work, but avoiding the 1.14 hboot is a good idea. So I too would recommend getting the 1.85 RUU: http://forum.xda-developers.com/showthread.php?t=1670238
OP should make sure he has the latest HTC drivers installed on the PC, or try re-installing them. Also try a different USB port. I've seen more than a few times on here, where it was simple as the drivers or the USB port.
redpoint73 said:
Newer RUU version should still work, but avoiding the 1.14 hboot is a good idea. So I too would recommend getting the 1.85 RUU: http://forum.xda-developers.com/showthread.php?t=1670238
OP should make sure he has the latest HTC drivers installed on the PC, or try re-installing them. Also try a different USB port. I've seen more than a few times on here, where it was simple as the drivers or the USB port.
Click to expand...
Click to collapse
damn.. now adb devices doesn't show my phone, there is no way to connect the phone to the pc, sooner if I did, I find it very strange
maybe for this reason the install of the RUU 1.85 has failed
This is my screen, and in fastboot, the pc doesnt recognize the phone with the command "adb devices"
please help, im freaking out!
juanfranrod said:
This is my screen, and in fastboot, the pc doesnt recognize the phone with the command "adb devices"
please help, im freaking out!
Click to expand...
Click to collapse
Don't freak out, if your phone can be turned on it can be fixed.are you sure you have done everything they have said? Or have you tried unlocking again wiping and flashing a Rom? Does the computer make those 2 beeps when you plug your phone in?
juanfranrod said:
This is my screen, and in fastboot, the pc doesnt recognize the phone with the command "adb devices"
please help, im freaking out!
Click to expand...
Click to collapse
You can't use adb in fast boot
Use
Fastboot devices
Sent from my HTC One X-
WhatTheAndroid? said:
Don't freak out, if your phone can be turned on it can be fixed.are you sure you have done everything they have said? Or have you tried unlocking again wiping and flashing a Rom? Does the computer make those 2 beeps when you plug your phone in?
Click to expand...
Click to collapse
Ok I unlocked the phone again, and wiped the phone. I tried typing in commands "fastboot flash zip Cleanrom5.zip" and gave me FAILED.. and yes, the computer make the beep (1) when I connect the phone, as a usb sound.
iElvis said:
Did you reformat your SD card?
Click to expand...
Click to collapse
hey iElvis, had not understood exactly where reformatting the SD card, as I did through the recovery and failed, will be the problem?
I have relocked the phone again, and I have tried to run the RUU in fastboot, but the last step in the installation appear an Error 170: Usb Connection Error... sigh
almost a complete day for nothing
juanfranrod said:
I have relocked the phone again, and I have tried to run the RUU in fastboot, but the last step in the installation appear an Error 170: Usb Connection Error... sigh
almost a complete day for nothing
Click to expand...
Click to collapse
This happened to me and I was able to do
fastboot flash recovery recovery.img (using original recovery)
Then reboot into bootloader then fastboot
fastboot boot TWRP.img
Then, once you're in TWRP, you can just flash a rom
Hope it helps! I'm still kinda nooby w/ htc as I was with motorola forever! I got my phone 1 month ago so... yeah
Try it! I was hopeless but I just kept trying!
Good luck!
---------- Post added at 05:48 AM ---------- Previous post was at 05:42 AM ----------
juanfranrod said:
This is my screen, and in fastboot, the pc doesnt recognize the phone with the command "adb devices"
please help, im freaking out!
Click to expand...
Click to collapse
Also, that just means your battery is low.
Just charge the phone while in bootloader overnight.
You should then be able to detect USB
juanfranrod said:
hey iElvis, had not understood exactly where reformatting the SD card, as I did through the recovery and failed, will be the problem?
Click to expand...
Click to collapse
You connect the phone to the PC, select "Mount USB" in TWRP. Then on your PC format the phone's SD card.
Gday,
I did many searches and I read the " here are the similar treads found" but none has the solution. I am reading and searching for the last 3 hours, but no sigar. SO I am hoping someone can help me out.
I used this link to install my current ROM - http://forum.xda-developers.com/showthread.php?t=2445392
HTC one 2 ville
ROM maximus 10
I had TWRP 2.6.3 installed
All was working fine, only to have TWRP working with this ROM I needed to use TWRP 2.6.1. As I was not able to run backups.
So I went into fastboot USB. Run the below command.
C:\HTC>fastboot flash recovery recovery.img
sending 'recovery' (6246 KB)...
OKAY [ 1.009s]
writing 'recovery'...
OKAY [ 1.501s]
finished. total time: 2.510s
And after this I guess I screwed up something.
The laptop is not recognizing the phone anymore and says the device is malfunctioned.
I cannot get in TWRP recovery anymore. If I try the screen goes black. I need to hold the power button to turn it off.
WinDROID is not seeing the device either
I just cleared cache, dalvik, wiped data and went back to factory default.
That did not helped a thingy.
USB settings:
If I change it to HTC sync manager of clear check mark either way it comes with the same message " USB not recognized".
Can someone help me out plz
Thanks a lot
I reinstalled HTC drivers and now the phone gets recognized again.
But I still cannot install anything from recovery....
E:\Can't mount /sdcard/
After I installed the HTC drivers I was able to get on the sdcard again and get connected.
I installed TWRP 2.6.3. and I am able to boot in recovery,
That's nice, but now TWRP say's I only have 48MB on the SDcard?? When booted in systeem and connected to my laptop it tells me the SDcard = 11.9GB and has 11.6GB free.....
At least the phone keeps me off the street
INstalled SDrescan. That does not solve it.
Also TWRP 2.6.3 gives different info. Like battery 66% and on another page it tells me it has 100%.
Does this means the SDcard is damaged?
Ray187 said:
INstalled SDrescan. That does not solve it.
Also TWRP 2.6.3 gives different info. Like battery 66% and on another page it tells me it has 100%.
Does this means the SDcard is damaged?
Click to expand...
Click to collapse
you need to flash the stock recovery, then go to bootloader and perform "factory reset + clear storage".
nce done you can flash your custom recovery again and you should be fine
Thanks.
I have hboot 2.16. I thought that there is no stock Rom for this hboot. I,ll have a look.
Ray187 said:
Thanks.
I have hboot 2.16. I thought that there is no stock Rom for this hboot. I,ll have a look.
Click to expand...
Click to collapse
HBoot 2.16 means you're "S-OFF" and can run ANY RUU
LS.xD said:
HBoot 2.16 means you're "S-OFF" and can run ANY RUU
Click to expand...
Click to collapse
Yes..after I read your post I slapped myself.....twice
HHmmzz
I copied the RUU to the root om the SDcard. Then I rebooted into recovery. Recovery is not able to see the root of the SDcard. Only folders he can see are TWRP and CWM.
Now I cannot even get on fastboot USB anymore. When I reboot the device the screen is blinking green.
*edit*
I mounted the USB device so it popped up on my laptop. And here as well it says it has only 48MB. SO no chance to copy the RUU.
Is there another way to flash my phone?
What did you do? The RUU needs to be started in Windows
Sent from my beloved HTC One S using (most time buggy) Tapatalk
---------- Post added at 10:11 AM ---------- Previous post was at 09:58 AM ----------
Ray187 said:
HHmmzz
I copied the RUU to the root om the SDcard. Then I rebooted into recovery. Recovery is not able to see the root of the SDcard. Only folders he can see are TWRP and CWM.
Now I cannot even get on fastboot USB anymore. When I reboot the device the screen is blinking green.
*edit*
I mounted the USB device so it popped up on my laptop. And here as well it says it has only 48MB. SO no chance to copy the RUU.
Is there another way to flash my phone?
Click to expand...
Click to collapse
Did you reed anything about using RUU? Connect phone in fastboot mode and run the RUU in windows. You need to flash stock recovery and set your CID back to stock before you can use the RUU.
LS.xD said:
What did you do? The RUU needs to be started in Windows
Sent from my beloved HTC One S using (most time buggy) Tapatalk
---------- Post added at 10:11 AM ---------- Previous post was at 09:58 AM ----------
Did you reed anything about using RUU? Connect phone in fastboot mode and run the RUU in windows. You need to flash stock recovery and set your CID back to stock before you can use the RUU.
Click to expand...
Click to collapse
I used to install RUU it on my previous phone. I cannot get fastboot USB connected anymore. I can't get the phone connected to my laptop at all. gives me the device malfuntion.
Bit frustrated...I almost broke the phone in half :laugh:
For now I just keep using it with the current ROM. Maximus 4.2.2 and sence 5.0 S-off. I did not changed CID.
I will try again in a couple of days.
Thank you :good:
nvm
Owkeee smie again
Couldn't recist trying to fix this.
I managed to get fastboot USB active. So I tried to erase recovery. That failed as remote is not allowed. Then I flash TWRP 2.6.1.0 succesfully.
And now it's back to normal.
2 bad I damaged the phone a bit. I forgot the one s is a phone you cannot open to remove the battery of SDcard....thought about it while having a screwdriver in my hand and partly in the phone :silly:
Appriciated your replies LSxD :good:
Ray187 said:
Owkeee smie again
Couldn't recist trying to fix this.
I managed to get fastboot USB active. So I tried to erase recovery. That failed as remote is not allowed. Then I flash TWRP 2.6.1.0 succesfully.
And now it's back to normal.
2 bad I damaged the phone a bit. I forgot the one s is a phone you cannot open to remove the battery of SDcard....thought about it while having a screwdriver in my hand and partly in the phone :silly:
Appriciated your replies LSxD :good:
Click to expand...
Click to collapse
Means your phone is working again? Or did you kill it with the screwdriver?
LS.xD said:
Means your phone is working again? Or did you kill it with the screwdriver?
Click to expand...
Click to collapse
Phone works fine again. Able to connect it to the PC, use fastboot and get in recovery and see full size SDcard :good:
So will be making a backup and copy those files to my NAS.
I damaged the phone a bit physically at the back.
Hi everybody !
I think i'm in the right section to expose you my problem, and no one on this forum had been confronted to such fails ! but i'm new in this forum to write threads (altough i already read many of them)
i'll try to be quick :
a year ago i bought a htc one sv , i unlocked the bootloader and then i stopped because i was with windows 8 and it was boring with usb 3.0 (i can use windows 7 right now..!). then i got some problems with "android.phone", or android.process.media" stopped et i believed my phone dead, but i learned things, installed the TWRP recovery 2.7.0.1 and flashed therom stock odexed jelly bean which allowed me to get back to stock my phone! (the twrp was with the root (or the rom odexed...) so i became rooted! but when i updates the superuser app few months ago, i got problems of binaries so i didn't install the last supersu app update (2/3 weeks ago). unfortunately,2 weeks ago, my phone did a reboot in the night (which awoke me) but in a bootloop...
First i tried factory reset then clean storage du bootloader, but it did nothing.
at the beginning i could not acceed to the recovery, but, lucky i am, a boot in fastboot usb and now from the phone, i can go to my recovery twrp 2.7.0.1 -or 2.8.4.0 by boot fastboot usb) however, TWRP shows "no os installed"it s been 2 weeks that i'm searching, but without results... that's why i'm asking here to the best in android world ^^
the things that i already tried without results:
flash the same zip odexed from recovery and from fastboot usb
flash hboot, but i'm s-on
update recovery ( i only can boot by fastboot usb)
flash rom custom venom with the installer in the rom
find files for sdcard "pl80diag.zip et nbh et pl80img.zip et nbh"
but i'm S-on and can't be S-off, the process with moonshine stopp when the devices has to boot...
i also tried adb sideload and simple adb with the phone in recovery recovery but:
recovery is unable to mount internal storage partitions (unable to mount int-sd, etc............)
my phone shows "tampered" "unlocked" and "s-on" hboot "2.00.000".. ask for more...
from now on, when i boot the phne i don't have any more bootloop, i'm directly in the hboot..!
i tried extract rom.zip from RUU.exe of ICS but i didn't used it...
so i'm wondering if there is a way to unbrick this soft bricked devices 'casue i already tried all of the unbrick things for soft brick but the partitions being unable to mount killed all my tries... i hope i gave you many informations ! all the suggestions and ideas are welcome!
(i can't find nbh files..)
thanks for reading this busy text, i'm a bit bored of using a very old phone in remplacement if i can repair my lover htc..!
i trust you people i'll check and answer suggestions asap!
Well, you are S-on, there is not much you can do.
Flash twrp recovery 2.7.x or 2.8.x and try to flash a rom for your device model.
Don't forget to do a full wipe in twrp and to flash the boot.img of the rom you are using with fastboot.
old.splatterhand said:
Well, you are S-on, there is not much you can do.
Flash twrp recovery 2.7.x or 2.8.x and try to flash a rom for your device model.
Don't forget to do a full wipe in twrp and to flash the boot.img of the rom you are using with fastboot.
Click to expand...
Click to collapse
it that i was thinking... i already try this (i have already twrp without booting in fastboot or flashing) but the fact is : twrp cannot mount any partitions so the step "writing" is impossible.. even the wipe fails..
If i remember right, in TWRP 2.8, under Wipe - Advanced there must be a button "Repair broken filesystem".
Not sure if this is working on SV, but it is worth a try i think.
What version of this phone do you own?
old.splatterhand said:
If i remember right, in TWRP 2.8, under Wipe - Advanced there must be a button "Repair broken filesystem".
Not sure if this is working on SV, but it is worth a try i think.
What version of this phone do you own?
Click to expand...
Click to collapse
yep you're right i'v already try it on every partitions but i'll do it again !
i've got the K2_UL (i'm french) and it was on 4.2.2 JB.
by the way, thanks for your answers
guess who's back
old.splatterhand said:
If i remember right, in TWRP 2.8, under Wipe - Advanced there must be a button "Repair broken filesystem".
Not sure if this is working on SV, but it is worth a try i think.
What version of this phone do you own?
Click to expand...
Click to collapse
hey guys, it's been a while but i was searching during all this time. I've experienced some things with adb shell and what i saw :
my partitions are messed up, not annihilated, but messed up. 2 reasons : partitions can't be mounted in the last recovery of TWRP, and when i use Fdisk -l /dev/block/mmcblk0 and the partition table of mmcblk0 and what I see is that my partitions table are not in disk order. My partitions are overlapping.. Perhaps it will help. I tried some ext2fd and mkfs.ext4 but it as not worked properly... maybe you have ideas... because it's been about months that my phone is useless and a paperweight.
by the way on my computer under windows 10, my phone used to be in qhsus_dload..! perhaps there are issues with that!
Thanks.
colton49 said:
hey guys, it's been a while but i was searching during all this time. I've experienced some things with adb shell and what i saw :
my partitions are messed up, not annihilated, but messed up. 2 reasons : partitions can't be mounted in the last recovery of TWRP, and when i use Fdisk -l /dev/block/mmcblk0 and the partition table of mmcblk0 and what I see is that my partitions table are not in disk order. My partitions are overlapping.. Perhaps it will help. I tried some ext2fd and mkfs.ext4 but it as not worked properly... maybe you have ideas... because it's been about months that my phone is useless and a paperweight.
by the way on my computer under windows 10, my phone used to be in qhsus_dload..! perhaps there are issues with that!
Thanks.
Click to expand...
Click to collapse
Which K2 variant do you have?
Sent from my C525c using Tapatalk
SHM said:
Which K2 variant do you have?
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
K2_UL, but I am at a point that each try worths it.. even with other K2!
moreover I've got a full stock backup of K2_UL but it didn't work with TWRP when I tried
. from now on i have no more ideas.. ^^
colton49 said:
K2_UL, but I am at a point that each try worths it.. even with other K2!
moreover I've got a full stock backup of K2_UL but it didn't work with TWRP when I tried
. from now on i have no more ideas.. ^^
Click to expand...
Click to collapse
You need an RUU to fix you up.
http://androidruu.com/getdownload.p...0.14_2_10.49.40.11L_release_301902_signed.exe
Sent from my C525c using Tapatalk
SHM said:
You need an RUU to fix you up.
http://androidruu.com/getdownload.p...0.14_2_10.49.40.11L_release_301902_signed.exe
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
ha
I've already tried but when it as to be detected, nothing occured, but i'll try again.. do you think that could be restore my phone ( ave you read my first explanation message,)
colton49 said:
ha
I've already tried but when it as to be detected, nothing occured, but i'll try again.. do you think that could be restore my phone ( ave you read my first explanation message,)
Click to expand...
Click to collapse
Well if you can extract the RUU from the .exe program then you can boot to your hboot then select fastboot from the screen. Plug device to your pc then enter:
Confirm pc reads phone and displays serial number before proceeding...
Code:
fastboot devices
Code:
fastboot oem rebootRUU
Code:
fastboot flash zip RUU.zip
If terminal shows it has completed successfully then reboot:
Code:
fastboot reboot
If terminal shows it didn't complete successfully then do not reboot but try again:
Code:
fastboot flash zip RUU.zip
I went through this last weekend for my K2CL because I was converting my device to f2fs and messed up in the process.
Sent from my C525c using Tapatalk
SHM said:
Well if you can extract the RUU from the .exe program then you can boot to your hboot then select fastboot from the screen. Plug device to your pc then enter:
Confirm pc reads phone and displays serial number before proceeding...
Code:
fastboot devices
Code:
fastboot oem rebootRUU
Code:
fastboot flash zip RUU.zip
If terminal shows it has completed successfully then reboot:
Code:
fastboot reboot
If terminal shows it didn't complete successfully then do not reboot but try again:
Code:
fastboot flash zip RUU.zip
I went through this last weekend for my K2CL because I was converting my device to f2fs and messed up in the process.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
OK well i'll use my computer under windows 7, but i know that when i extract the ruu from the .exe (using the folder temp, you know) the file can't be flash with recovery but i'll give a try with fastboot (fastboot devices always work) if this can work you'll be my heroe haha because i've tried so many things with the adb shell the recoveries, the flash with fastboot (which taught me some things about android) but nothing worked!
colton49 said:
OK well i'll use my computer under windows 7, but i know that when i extract the ruu from the .exe (using the folder temp, you know) the file can't be flash with recovery but i'll give a try with fastboot (fastboot devices always work) if this can work you'll be my heroe haha because i've tried so many things with the adb shell the recoveries, the flash with fastboot (which taught me some things about android) but nothing worked!
Click to expand...
Click to collapse
Yea, the RUU extracted is not made to be flashed in the custom recovery or any recovery for that matter. Must be flashed with the device in RUU mode as instructed in my last comment. If you are S-On then make sure you relock the bootloader first before doing it. If you are S-Off then it does not matter. It will fix your device. Like I said, I borked my partitions last weekend and the RUU fixed it right up for me with no problems. However, I used a decrypted RUU but the process is still the same.
Sent from my C525c using Tapatalk
SHM said:
Yea, the RUU extracted is not made to be flashed in the custom recovery or any recovery for that matter. Must be flashed with the device in RUU mode as instructed in my last comment. If you are S-On then make sure you relock the bootloader first before doing it. If you are S-Off then it does not matter. It will fix your device. Like I said, I borked my partitions last weekend and the RUU fixed it right up for me with no problems. However, I used a decrypted RUU but the process is still the same.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
okay thanks i'm gonna try this again and again if it does not work at the first shot! yes i'm S-ON and Unlocked.. ! okay you give me hope !!
i'll tell you if i succeed
SHM said:
Yea, the RUU extracted is not made to be flashed in the custom recovery or any recovery for that matter. Must be flashed with the device in RUU mode as instructed in my last comment. If you are S-On then make sure you relock the bootloader first before doing it. If you are S-Off then it does not matter. It will fix your device. Like I said, I borked my partitions last weekend and the RUU fixed it right up for me with no problems. However, I used a decrypted RUU but the process is still the same.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
to decrypt the RUU You use smthing on Ubuntu right ? or you tried something else because i guess it's better when decrypted
colton49 said:
to decrypt the RUU You use smthing on Ubuntu right ? or you tried something else because i guess it's better when decrypted
Click to expand...
Click to collapse
On linux in general and decrypting the RUU is way more complicated and difficult than it sounds. An encrypted RUU will do you just fine.
Sent from my C525c using Tapatalk
SHM said:
On linux in general and decrypting the RUU is way more complicated and difficult than it sounds. An encrypted RUU will do you just fine.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
ok i'll try with the encrypted and if it doesn't work after many tries i'll try to decrypt it! i'm gonna try all of this right now ! just have to remember where extract the ruu
SHM said:
On linux in general and decrypting the RUU is way more complicated and difficult than it sounds. An encrypted RUU will do you just fine.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
I've got a huge pb, it seems that i can't relock my bootloader and well i'm s-on...
because fastboot oem lockfail
even htc bootloader unlock fails when i put the phone in a recovery to be recognized.. ****.. but if i can lock it it'll work..
colton49 said:
I've got a huge pb, it seems that i can't relock my bootloader and well i'm s-on...
because fastboot oem lockfail
even htc bootloader unlock fails when i put the phone in a recovery to be recognized.. ****.. but if i can lock it it'll work..
Click to expand...
Click to collapse
What do you mean by putting the phone in "recovery"? You shouldn't be in your recovery when using fastboot. You should be in your bootloader. Power off device, then press and hold the volume down key and the power key. Release when you see your hboot appear. Using your volume keys to move up and down you want to highlight the option, fastboot. Hit the power button to select fastboot. You are now in fastboot mode. You will see fastboot in red text. Plug your device into your pc and you should now see, fastboot usb, in red text. Using the terminal on your pc proceed to lock your bootloader using fastboot. Then proceed with my instructions in the other post.
Sent from my C525c using Tapatalk
SHM said:
What do you mean by putting the phone in "recovery"? You shouldn't be in your recovery when using fastboot. You should be in your bootloader. Power off device, then press and hold the volume down key and the power key. Release when you see your hboot appear. Using your volume keys to move up and down you want to highlight the option, fastboot. Hit the power button to select fastboot. You are now in fastboot mode. You will see fastboot in red text. Plug your device into your pc and you should now see, fastboot usb, in red text. Using the terminal on your pc proceed to lock your bootloader using fastboot. Then proceed with my instructions in the other post.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
yeah of course i did it. Being in the recovery was just a try with a toolkit which is used to relock.
i know how fastboot works but i've got error messages with fastboot oem lock and by flashing the ruu the last thing after the signature checking fails because of my bootloader unlocked i guess.