All Desire S users should know about the infamous error message:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Click to expand...
Click to collapse
this is the so called eMMC fried chip, etc.. This is actually the "cache" partition being corrupted..
I myself have already received this error NUMEROUS times when tinkering with my phone..
The fix..?
Here's my method:
1. remove the battery for 30secs to 1 minute and putting it back in
2. boot directly to your bootloader, then go to recovery
3. If you haven't received the errors, your cache will be formatted to EXT3, try formatting it to ext4 if need be
4. I wipe everything (all partitions) including dalvik cache and battery stat
5. flash your rom again, cross your fingers and hope for the best..
Click to expand...
Click to collapse
Based on experience: Even the RUUs will tell you to unplug your battery for 3secs if RUU had some problem.
Some additional info:
Skanob said:
You should be able to change your recovery without any problem if your s-off or unlocked 2.xx.xx hboot s-on.
1. Get 4ext recovery.img
2. connect phone on fastboot
3. In cmd use these command to push the recovery image:
fastboot flash recovery D:\recovery.img (<- should be directory of 4ext recovery image)
fastboot reboot-bootloader
Now you should have 4ext recovery.
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
And...
Skanob said:
amidabuddha said:
I do not think that you can use fastboot flash whatewer without an engineering bootloader (requires s-off) or push images with adb without su (requires rooting). This is the point of all the guides and tutorials around here...
Click to expand...
Click to collapse
You actually can.. Check my sig.. I have already flashed a stock recovery then back to 4EXT many times.. I am on OFFICIAL HBOOT from the 2.10.401.4 update..
flashing OFFICIAL RUUs prior to latest hboot didn't work for me as the HBOOT seems to be un-writable to old HBOOTs. I haven't tried revolutionary's 6.xx.xx HBOOT though..
I am on unrooted STOCK RUU when I tried to flash the update forcefully. HBOOT and RECOVERY got updated so got me stock on HTC logo (without the "quietly brilliant") means ROM is not booting.
That is the method I used to revive my phone.
Edit:
"Unlocking" my S-ON could've helped me..
Click to expand...
Click to collapse
Also..
Skanob said:
amidabuddha said:
Ok taking my words back And how do you did this? You flashed the Stock 2.10.401.4 ROM over you bricked phone and it worked? (overwritted the revolutionary hboot or which version was it before?).
Click to expand...
Click to collapse
To make the long story short:
I stupidly get the firmware.zip file inside the ota file. That file had the latest hboot, recovery, and others. I renamed it to the correct pgxxximg.zip (cant remember the correct filename, currently drinking ) to flash it from bootloader.
Everything went well. Everything inside the file updated the corresponding file/partition/image to my phone. Hence letting me be stuck to the "locked" hboot 2.xx.xx s-on. ROM wouldn't boot as I said.
Being on the "locked" state wouldn't allow me to flash anything on the phone as far as i can remember. While writing, it will say has its unsuccessful.
But "unlocking" the hboot let me flash the recovery.
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
cheers for this info. I myself have experienced this too after flashing new radio, but this is the message u also get when the partition table gets corrupted.
If that is the case then the method u provided will work, but fried emmc = no fix
Had the same problem, but I couldnt even get into recovery.
This helped for me:
chaelli said:
1. Download this http://www.4shared.com/get/JeuI2H2s/...YIMG-3200.html
2. Rename to PG88IMG.zip and put on sd-card
3. boot with vol-down pressed
4. wait.. press vol-down (yes) to install
5. reboot with vol-down pressed
6. select recovery and press enter.
7. wait
8. use recovery
Click to expand...
Click to collapse
TimMun said:
Had the same problem, but I couldnt even get into recovery.
This helped for me:
Click to expand...
Click to collapse
What you've done is exactly the same of my instruction on how to flash a recovery. That's another way as it is automatic. You just have to make sure your .zip passes the security check of bootloader if your on s-on, as far as i know.
This look promissing.
Since my bricked DS is S-On do I need a gold card?
DanielPascoal said:
This look promissing.
Since my bricked DS is S-On do I need a gold card?
Click to expand...
Click to collapse
Not necessarily, you just need to unlock your hboot..
TimMun said:
Had the same problem, but I couldnt even get into recovery.
This helped for me:
Click to expand...
Click to collapse
it show me
Main Version is older!
Update Fail
i have use hboot 2.00.0002
Solution found: New Hboot 2.00.0002
Didn't search threads good enough sorry...
Problem down solved!
-----------------------------------------------------
Skanob said:
Not necessarily, you just need to unlock your hboot..
Click to expand...
Click to collapse
and...
How can we unlock hboot...
When I use HTCDev site, fastboot oem get_identifier_token returns with a Command not found Error...
Is there an another way to get this token, or...?
I ran the 1st method when I've changed and tested some roms (on 2.3.3) without knowing that this was a possibility to resolve this problem.
1. remove the battery for 30secs to 1 minute and putting it back in
2. boot directly to your bootloader, then go to recovery
3. If you haven't received the errors, your cache will be formatted to EXT3, try formatting it to ext4 if need be
4. I wipe everything (all partitions) including dalvik cache and battery stat
5. flash your rom again, cross your fingers and hope for the best..
Click to expand...
Click to collapse
I put more all my partitions on Ext4 (except sdcard )
Since I don't have this problem anymore
Skanob said:
All Desire S users should know about the infamous error message:
this is the so called eMMC fried chip, etc.. This is actually the "cache" partition being corrupted..
I myself have already received this error NUMEROUS times when tinkering with my phone...
Click to expand...
Click to collapse
my friend, did u try:
Code:
dmesg | grep mmc0
and what's the output?
like this:
Code:
mmc0: failed to get card ready
mmc0: reinit card
mmc0: Starting deferred resume
mmc0: Deferred resume failed
or maybe u never got these error-magic-infamous-$60costs-strings, lol.
well, im kidding. xD
How do you format to ext4?
The steps don't explain how I can do this. I already have pushed Recovery using the post #3 method, and I formatted and reset everything. But then Recovery doesn't allow me to reboot or turn off the phone (I get a black screen with a pictogram and then it goes back to Recovery).
So I still have to format to ext4 but how?
BTW I tried RUU 1.47 that worked, then I wanted to do RUU 2.10 and the phone hangs at white screen with green HTC. Thats how I ended up here in this topic trying to revive my girlfriends phone :S
So I can access Recovery now, and I reset everything. But still have the White screen. Also RUU can't find the phone, I suppose because the phone hangs at the white screen... any help is DEEPLY appreciated!
EDIT:
I installed this prerooted ROM (deodexed version cos people complained about issues with odex version):
http://forum.xda-developers.com/showthread.php?t=1287797
And now I have Android 2.3.5 with Sense 3.0 fully working. Only it's not the newest rom (version .............4 instead of .............5) and it has old Market but it's better then having Android 2.3.3 and Sense 2.1
EDIT2: after Android installed all my apps automatically, Market was also updated
Help!!!
my Desire S oso hav this problem eMMC fried chip
and i use fastboot flash recovery.img oso cant
Help me...Help me...PLS
allenteoh said:
my Desire S oso hav this problem eMMC fried chip
and i use fastboot flash recovery.img oso cant
Help me...Help me...PLS
Click to expand...
Click to collapse
Damn! Wish I'd thoughg up a guide sooner. More initiative next time. Point is, I've been scared into near cardiac arrest a number of times based on guys here making me believe my chip was baked. Bounced back with no sequelae each time. Apparently, we over-diagnose this fried emmc chip of a thing. IIf you however have a truly Kentucky fried chip, as with most hardware errors, you'll need a hardware replacement. In this case, the chip. But only when all else has failed.
OMFG, this is a solution for eMMC fries on G2 (desire Z) - http://forum.xda-developers.com/showthread.php?t=1572924 Anyone wanna test on Saga?
shrome99 said:
OMFG, this is a solution for eMMC fries on G2 (desire Z) - http://forum.xda-developers.com/showthread.php?t=1572924 Anyone wanna test on Saga?
Click to expand...
Click to collapse
That does look very interesting.
Although just in case anyone takes you at your word....consider that you'll need to use the relevant ROM and recovery files specifically for our device if you do fancy trying this, not those found in that post.
Yes, but i saw that the OP of that thread is offering help on other devices (Evo 4G) too, so if anyone is willing to test, post there.
Sent from my iPod touch using Tapatalk
I repaired my bricked htc desire s in local service. It had emmc fried chip. They used tool for reprograming device or chip.
Repair costed me 15€
can sombody please help me here
my desire s is not booting up stuck on HTC screen
Note: my phone is not Rooted
bootloader reads
SAGA PVT SHIP S-ON RL
HBOOT-0.98.0000
RADIO-38.03.02.11_M
eMMC-BOOT
MAR 10 2011,14:58:38
I have tried the following downloaded
RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.0805U_38.03.02.11_M_release_177977_signed
and
RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.0805U_38.03.02.11_M_release_177977_signed
tried running the ruu both get stuck on rebooting bootloader nothin happens
i extracted the rom.zip from the ruu and tried pushing the boot.img using adb but is says failed remote: signature verify fail
i renamed the rom to pg88img and put it on mmc rebooted phone in bootloader yet nthin
i downloaded the recvery img from above tried renaming t to pg88img andput in mmc again reboot yet nothin tried pushing it via adb same error signature verify fail
chk the bellow screen shot and please advise
http://www.freeimagehosting.net/8lsmy
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I answered this exact question yesterday. Try searching.
is this the answer u are talking about
Boot to bootloader (power on while pressing VolDown).
Select FASTBOOT with volume buttons.
Press Power.
Connect USB. See that it says "fastboot usb".
Check that you can see the phone in fastboot mode ("fastboot devices" shows a device). If not - install fastboot drivers.
Run RUU.
well done all that too but doesn work
also tired fastboot devices yes i do get my device but wen i install the RUU it jus gets stuck on rebooting bootloader.
on a NOTE: wen i but into bootloader and scroll down to the option reboot bootloader and i select it my phone totally freezes nothin happen till i remove the battery.
---------- Post added at 10:47 AM ---------- Previous post was at 10:39 AM ----------
one more thing and my bootloader i don see on the top written
**LOCKED**
or
**UNLOCKED**
thats weird
Related
hi all xda community !
So here is the situation :
HBOOT Screen :
***UNLOCKED***
pyramid pvt ship s-off rl
HBOOT-1.27.0000
Radio-11.21.3504.13_2
OpenADSP-v02.6.0.226.00.0104
eMMC-boot
Symptom:
I'm Stuck in a bootloop after i flash the 3.24 firmware and the Elegancia ROM.
First Time the roms boot normaly, then i reboot with the USB Cable attach.
And here come the BootLoop
Try to go to recovery, but bootLoop too.........
So I can go in Hboot, i can do FASTBOOT command and that all.
I try to flash CWM from fastboot -- > Ok for flash but wont go in recovery..
Try to flash 1.17 firmware then flash ROM.zip from 1.35Ruu Europe release --> Bootloop
Try to Flash 3.24 Ruu Same BOOTLOOP..
So what can I do community ?
What Solution i have ?
Why i cant flash a recovery since i Have S-OFF ??
MAYBE :
- Maybe i flash a Ruu who was Corrupt
- Maybe the radio don't match the Ruu i Tried to flash
- Maybe i'm just a simple mind guy
It seems that the 3.24 Firmware from SebastianFM with hBoot unlock have some problem, cause it seems that i'm not the only one who got several problem after flash this Firmware.
toowave said:
hi all xda community !
So here is the situation :
HBOOT Screen :
***UNLOCKED***
pyramid pvt ship s-off rl
HBOOT-1.27.0000
Radio-11.21.3504.13_2
OpenADSP-v02.6.0.226.00.0104
eMMC-boot
Symptom:
I'm Stuck in a bootloop after i flash the 3.24 firmware and the Elegancia ROM.
First Time the roms boot normaly, then i reboot with the USB Cable attach.
And here come the BootLoop
Try to go to recovery, but bootLoop too.........
So I can go in Hboot, i can do FASTBOOT command and that all.
I try to flash CWM from fastboot -- > Ok for flash but wont go in recovery..
Try to flash 1.17 firmware then flash ROM.zip from 1.35Ruu Europe release --> Bootloop
Try to Flash 3.24 Ruu Same BOOTLOOP..
So what can I do community ?
What Solution i have ?
Why i cant flash a recovery since i Have S-OFF ??
MAYBE :
- Maybe i flash a Ruu who was Corrupt
- Maybe the radio don't match the Ruu i Tried to flash
- Maybe i'm just a simple mind guy
It seems that the 3.24 Firmware from SebastianFM with hBoot unlock have some problem, cause it seems that i'm not the only one who got several problem after flash this Firmware.
Click to expand...
Click to collapse
Follow this thread .
http://forum.xda-developers.com/showthread.php?t=1480061
I doubt you may have to look the highlighted red text.
hi & thks
I already read this thread, problem is that i can't flash anything except Ruu Roms with fastboot or maybe i can but i don't know how to do ..
i already try to flash recovery (CWM) but bootloop when i want to go to recovery
if you now how i can have a recovery to work, or maybe if i can wipe everything with fastboot i would appreciate
toowave said:
hi & thks
I already read this thread, problem is that i can't flash anything except Ruu Roms with fastboot or maybe i can but i don't know how to do ..
i already try to flash recovery (CWM) but bootloop when i want to go to recovery
if you now how i can have a recovery to work, or maybe if i can wipe everything with fastboot i would appreciate
Click to expand...
Click to collapse
I got you. Actually you do not have any custom recovery installed. Actually if you flash any RUU it will wipe your recovery partition and install stock recovery. So first you flash a custom recovery. I know you tried to flash CWM.But you got bootloop. Did you delete the file PG58IMG.zip from sdcard after flashing CWM ???? Please redo the following steps.
STEPS TO FOLLOW:
1. Download recovery v5.0.0.8 for the Sensation here .
2. Copy the PG58IMG file into the Root folder of your SD card (The main Folder of your Memory Card)
3. Turn off your phone.
4. Remove the battery.
5. Wait a minute.
6. Put the battery again.
7. Press Power + Volume Down key together.
8. The phone will boot into bootloader.
9. Press Volume up to Accept when it asks" Do you want to start the update"
10. Press Power Off to Reboot back to android after installation is successful (normal screen with homescreen)
11. It may not boot . Do not worry because you may have wiped out evrything.
12. Power off your phone.
13. Delete PG58IMG from your memory card .
14. Download your favorite custom ICS ROM.
15. Put it on the root of your SDCARD.
16. Remove the battery.
17. Wait a minute.
18. Put the battery again.
19. Press Power + Volume Down key together.
20. The phone will boot into bootloader.
21. Select "Recovery" by pressing Volume Down Key.
22. Press Power button after selecting Recovery.
23. Your phone will reboot into clockworkmod recovery.
24. Wipe system, boot, cache, data , and dalvik cache
24. Install your ROM from SDCARD.
25. Wait at least 7 to 10 minutes for first boot
26. Your phone will be normal now.
NOTE:
******* You must be SuperCID to do the above. Please also note , from your preveous post, I understand that you have V3.24 Firmware. Remember only ICS rom will work with this firmware. So do not flash Gingerbread ROM.**********
hi help is appreciate,
`So i tried to follow your step 3 times . One with 1.17 Firmware 3.12 & 3.24.
every time after flashing the recovery, i reboot and when i go to recovery the phone go into boot loop.
toowave said:
hi help is appreciate,
`So i tried to follow your step 3 times . One with 1.17 Firmware 3.12 & 3.24.
every time after flashing the recovery, i reboot and when i go to recovery the phone go into boot loop.
Click to expand...
Click to collapse
Which ROM you want to flash ??
Why did you try all three firmware ???? You should choose your firmware according to your ROM you want to flash.
You may get boot loop after flashing recovery as there might be no rom installed.
So as I said after flashing recovery you should power off your device. Then boot into bootloader by the preveous method. ( Step 3 to 7 ).Selct recovery by volume down key. Then press power button. You will be in recovery. And flash your ROM. But your ROM should match with the firmware.
Ok but How could i flash a ROm if i can't go to recovery ...
Ok maybe you miss understand, i got boot loop when i want to go to recovery too
Please tell me what ROM you want to flash. Post the link here. And once again you give the details of your boot loader screen. Do you have fastboot/adb set up on your PC?
Sent from my HTC Sensation XE with Beats Audio using Tapatalk
Android Revolution : http://forum.xda-developers.com/showpost.php?p=14192842&postcount=4
Seem to be a good Base.
I can Do fast boot command, but no adb .
HBOOT Screen :
***UNLOCKED***
pyramid pvt ship s-off rl
HBOOT-1.27.0000
Radio-11.21.3504.13_2
OpenADSP-v02.6.0.226.00.0104
eMMC-boot
toowave said:
Android Revolution : http://forum.xda-developers.com/showpost.php?p=14192842&postcount=4
Seem to be a good Base.
Click to expand...
Click to collapse
Ok you want arhd 6.2.1 . Tell me your cid. And where is the details of your current boot loader screen?
You did not tell me whether you have adb/fastboot set up..
Sent from my HTC Sensation XE with Beats Audio using Tapatalk
Ok i edit my previous response, with the informations you want.
And i'm super CID.
other Things, the phone won't want to charge cause he repeatedly try to boot.
toowave said:
Ok i edit my previous response, with the informations you want.
And i'm super CID.
other Things, the phone won't want to charge cause he repeatedly try to boot.
Click to expand...
Click to collapse
So, Let fix the recovery first.
Download this attatched recovery (4Ext Touch).
MD5 Checksum : d31d7df8d275f7234416af6a2e8b1c73
Check the md5check sum after download. If it matches , go to the next step else redownload.
Put the downloaded recovery.img in the directory of your fastboot binary.
Connect your phone with pc via usb cable.
Reboot your phone into bootloader.
Open fastboot command from your pc.
Now type the following command in fastboot.
" fastboot flash recovery recovery.img "
After flashing type " fastboot reboot"
Now try to go to recovery. If it is successfull then I will tell you the ROM flashing part.
Please come on gtalk . My gtalk id is musarraf172
ok i'm on gtalk wait for ya
so i'm still in the BOotLoop mode.
i've tried almost everything who was in the forum.
i'm aware of the noob style problem(Firmware not updated, still got PM58IMG.zip in SDcard, wrong Rom--firmware etc ..) and i'm not in this case !!!!
I think the device is brick but maybe someone with good knowledge, and experience can help me.
For now i got the last Hboot, i can flash recovery from fastboot , the command return OK but recovery wont boot.
Ruu flashing run nice with no problem but don't Boot (.exe and PM58IMG.zip).
when i try to unlock bootloader (who is already mark S-OFF but just for try)
with the HTCDEV method i'm stuck on the Unlock bootloader screen and i can't click YES.
it seems that my data partition have disappear ...
I here if you need more information.
Maybe someone can tell me if it's possible to FullWipe from fastboot ?
toowave said:
so i'm still in the BOotLoop mode.
i've tried almost everything who was in the forum.
i'm aware of the noob style problem(Firmware not updated, still got PM58IMG.zip in SDcard, wrong Rom--firmware etc ..) and i'm not in this case !!!!
I think the device is brick but maybe someone with good knowledge, and experience can help me.
For now i got the last Hboot, i can flash recovery from fastboot , the command return OK but recovery wont boot.
Ruu flashing run nice with no problem but don't Boot (.exe and PM58IMG.zip).
when i try to unlock bootloader (who is already mark S-OFF but just for try)
with the HTCDEV method i'm stuck on the Unlock bootloader screen and i can't click YES.
it seems that my data partition have disappear ...
I here if you need more information.
Maybe someone can tell me if it's possible to FullWipe from fastboot ?
Click to expand...
Click to collapse
if yo can go in fastboot your likley not bricked.
you can always flash the original or similar ruu (not a rom) you phone came with in fastboot.
so you will go to stock with your hboot and recovery and to see if it boots.
then do the whole process over. s-off, then root.
then check your mid and cid if its supported.
and only then update to ics.
btw whats the type of phone? branded or og htc
my phone is from vodaphone so branded.
What do you mean by flashing your original or similar Ruu ?
The one coming with the phone out of box ?
i flash via command, .exe or PM58IMG.zip ?
i don't write my original cid is it bad ?
thks
toowave said:
my phone is from vodaphone so branded.
What do you mean by flashing your original or similar Ruu ?
The one coming with the phone out of box ?
i flash via command, .exe or PM58IMG.zip ?
i don't write my original cid is it bad ?
thks
Click to expand...
Click to collapse
Come on g talk
Sent from my HTC Sensation XE with Beats Audio using Tapatalk
toowave said:
my phone is from vodaphone so branded.
What do you mean by flashing your original or similar Ruu ?
The one coming with the phone out of box ?
i flash via command, .exe or PM58IMG.zip ?
i don't write my original cid is it bad ?
thks
Click to expand...
Click to collapse
yes the rom the phone came with or close to it (any with recent ota`s).
always flash the ruu.exe because it wil recover the hboot, radio and recovery to stock. (zipfiles can be easily corrupted)
so go in fastboot usb (via power and volume button) and run the ruu.exe
then s-off/root the device
when s-off you should be able to install recovery within the original rom like cwr or ext4 updater tool, backup, then check your mid and cid, get a correct zipfile for the ics firmware update, flash arhd (it includes the lastest ext4 recovery). then change roms if you like.
you then also can check if the phone is working correctly.
if you already changed to supercid, i think its oke.
if not, on the forum there is al list of cid`s from different countrys and brands.
also there is al list of originals ruu the devices came with.
i assume you have done custom roms before ics came out?
so the cupercid was applied correctly?
i never supercid my devices (on a personal note)
and always flashed the testroms (to get the latest firmware) with no probs.
but if your branded its mandatory.
i've already flash 3 Ruu from this thread : http://forum.xda-developers.com/showthread.php?t=1074559
and all finish in a bootloop with no stock recovery... almost all Ruu run fine with no alert
ruu i flashed already :
RUU_Pyramid_HTC_Europe_1.27.401.3_Radio_10.42.9007.00P_10.11.9007.
RUU_Pyramid_HTC_Europe_1.35.401.1_Radio_10.43a.9007.00U_10.51.9007.
RUU_PYRAMID_LE_ICS_35_S_HTC_Europe_3.25.401.101_Radio_11.68.3504.00U_11.21.3
Hi,
i came to the screen install form zip on sdcard
but then it starts installation
and shows : installation aborted
now i cant start the phone i always get tothis screen
with the red text this build is for ....
what can i do?
edit: now i am again there where i can install zip from sdcard, but now it doesnt recognize the sdcard. What can I do, because i the phoen does not take a microsdcard where I could put a new rom.
how can i get access to the internela storage now wihtour a os?
How did this happen ? Selecting a ROM to flash in recovery cant really cause so much damage if it fails. They usually fail because of a md5 mismatch or something.
try to mount the sd card and you can use adb to push files to it..
you could also try a full wipe..
I did several things. I rooted and unlocked the device
and now it does not boot.
Everytime I tired to flash leedroid or stock rom with choosing install form zip
installation get aborted.
I am only able to get into the boolloader and into the recovery.
how can i restore the phone?
wipe and recovery is not possible i always end in this screen
with the red text.
edit: i think i try to get into booloader and copy another file version with adb to the sd card and hope it was a download error.
but why the hell then did both the leedroid 'AND the stock rom fail?
did you flash the boot.img BEFORE flashing leedroids ROM ??
If not i suggest trying that, If that fails, Just run an RUU and start from the beginning
Thanks for the Idea,
my problem is that i cant get access to the memory wihtout a working rom
on it And now i also dont get into the recovery CWMS.
I thouzhg power+vol up would do it but it doesnt work
I think i destroyed my brand new phone.
but thanks for helping.
It's not broken.
Try Power + Vol. down. Possibly you need to retry this several times to get into the bootloader.
its not destroyed dont worry..
Run an RUU and all will be good again. Whats your CID ?
That is the problem I cannot put up software on the device
so how should i run a ruu?
Where can i get the CID from wihtout starting the phone?
I hope you have a trick how I can save the device.
angeloski said:
That is the problem I cannot put up software on the device
so how should i run a ruu?
Click to expand...
Click to collapse
You run it from your Windows desktop. Download your appropriate RUU here for example (as it takes a loooooong time).
Connect your phone to your computer via USB.
Double Click the RUU-file.
Answer the Questions and the update will start.
Remember: Your device will be reset to factory default and your data on sd card will be gone so.
Edit: You will still have to start it with power + vol. down buttons pressed (as far as I remember).
angeloski said:
That is the problem I cannot put up software on the device
so how should i run a ruu?
Where can i get the CID from wihtout starting the phone?
I hope you have a trick how I can save the device.
Click to expand...
Click to collapse
To get into the bootloader try this.
Press and hold volume down, then power. Hold both down together for 5 secs, let go of the power button then press the power button several times. This always works for me.
If this works then your phone is easy to fix.
Maybe you could try to reflash the boot.img from leedroid via fastboot.
Then flash a proper recovery.img via fastboot (I use clockworkmod)
As I heard you could then push the rom.zip via Adb the sdcard while in recovery. Last step would be install zip from sdcard.
Sent from my HTC One S using XDA
Have you installed supersu via install ZIP from sdcard? I think this needs go be installed before installing the Rom. I Don't Know it exactly. But like this it worked for me when coming from stock rom. Thats how it worked for me:
1. Unlock bootloader via HTCDev
2. flash recovery image via fastboot
3. Install SuperSU from zipfile in recovery
4. Flash boot.img from Leedroid
5. Install Leedroid from sdcard
So maybe you missed one of the steps.
Sent from my HTC One S using XDA
to get CID go into fastboot and type in cmd window ''fastboot getvar cid''
If your phone is branded, you will need that branded RUU, So i assume you will need o2 Germany RUU
Reflash recovery in fastboot, should give you access to sdcard back.
Sent from my HTC One S using xda premium
i did the same thing to my one s yesterday... followed all the steps for leedroid n got same frustration u have...
theres a nandroid file in the dev section... fastboot the boot.img and the recovery.img
ya phone WILL boot back up
ok guys ty for cheeering me up.
i wil try it with a ruu, where can i find a ruu for my htc one s.
the link in the previuos post ist offline.
i think it was 1.78.407.x when i looked the last time in my handy.
thanks
so my cid is
C:\Android\android-sdk\platform-tools>fastboot.exe getvar cid
cid: O2___102
finished. total time: 0.003s
Like i said it is a O2 i hope this helps finding the ruu
well check the Shipped ROM thread.. If its not there you can ask the OP Football if he has it or can get it..
Some RUU's cost $13 so if you know someone else who wants it, you could split the cost ?
so far, now am in the recovery flash but it is the same
count mount /sdcard
how can i put a file onto the sdcard when i have no access?
partionoing sdcard doesn't help
i was looking for this boot.img and recovery.img which was posted before
i dont find it can someone link me to it if he knows what was meant?
thanks
edit: i was desperate and tried:
fastboot oem enableqxdm 0
fastboot oem eraseconfig
but the second order was not successful
ist there another way to fix this usb brick
and to get access to /sdcard
new edit: now i write also in the help thread (noob friendly) i hope that is ok.
Did you already try this
http://forum.xda-developers.com/showthread.php?t=1667929
Or this
http://forum.xda-developers.com/showthread.php?t=1630459
Sent from my HTC One S using XDA
I've been at this for like 8 hours going in circles. I have about 12 hours to figure this out. I am scheduled to go back to TMO to return this phone. Please help me.
While trying to revert back to stock, upon boot, at first there is a green icon, then it turns red w/ an exclamation point and just hangs there. It seems to have booted into the recovery because where it hangs, if i touch the "home" button, it disappears and shows me the cwm recovery main menu with a few errors relating to unable to mount SD. Its a very gimpy CWM with more than half of the commands/functions missing. (see pics below)
This is what I am currently getting in order....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- Boots to image 01
- Then to 02, here its trying to load/mount stuff, notice the SD icon and load bar near the bottom
- In 03 it looks like it ran into an error and hangs there
- Not sure why but I realized it boots straight into recovery. From 03, if i touch the home button I get 04. Notice all the stuff missing from cwm options
- 05 is what my HBoot / Bootloader looks like
-------------------------------
I am able to get back into HBoot / bootloader screen and can confirm that while in that mode the PC does recognize the device. But everything I flash does not work. When I run RUUs they seem to begin a process, but once that is done ( which isnt long), I would reboot but see nothing has changed. I tried to undo that stock recovery to access to NAND backups and start the process again but that Recovery doesn't have options for backups (strange?). Anyways, but can not flash another CWM successfully.
This is what I currently see when flashing a CWM now
c:\android-sdk\tools>fastboot flash recovery recovery-clockwork-touch-5.8.3.1-vi
lle.img
sending 'recovery' (6616 KB)...
OKAY [ 0.969s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.210s
c:\android-sdk\tools>fastboot reboot
rebooting...
I am completely out of options now. I looked at all the stickies around here and other places but can not find anything that will work. I did my best to be as thorough as I can. Please let me know if there are more info that would help. Thanks ahead of time.
This is One S development forum. Questions should be posted in questions.
Simple fix. Boot into bootloader and factory reset. Reboot once again into bootloader and format /erase sd card. Remember all this is being done from bootloader and not recovery. Reboot once again into bootloader and connect usb to phone and use fastboot to push cwm or whatever recovery you want to phone. Your sd card should now be mounted.
Not entirely sure about the return to stock, but being able to mount is a huge step in the right direction. Hope this helped
Sent from my HTC One S using xda premium
Chris Boyer said:
This is One S development forum. Questions should be posted in questions.
Simple fix. Boot into bootloader and factory reset. Reboot once again into bootloader and format /erase sd card. Remember all this is being done from bootloader and not recovery. Reboot once again into bootloader and connect usb to phone and use fastboot to push cwm or whatever recovery you want to phone. Your sd card should now be mounted.
Not entirely sure about the return to stock, but being able to mount is a huge step in the right direction. Hope this helped
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Sorry if I posted in the wrong place. Usually when I ask a flashing related question there someone tells me it should be asked in Development.
Anyways, I tried that but nothing changed. Sucky thing is that current recovery I am using, I can't even make a backup, restore a backup, or even install a rom from there.
enzyme said:
Sorry if I posted in the wrong place. Usually when I ask a flashing related question there someone tells me it should be asked in Development.
Anyways, I tried that but nothing changed. Sucky thing is that current recovery I am using, I can't even make a backup, restore a backup, or even install a rom from there.
Click to expand...
Click to collapse
First and foremost you need a working recovery with a mounted sd card. Are you able to push anything via fastboot? I found it easiest to use a fastboot script. It dumbs it down to a couple mouse clicks. There is a utility for the one S called all in one. (sorry don't have link) maybe try that to install fresh recovery. One thing for certain, factory reset and then format card has to be done from bootloader mode and then push new recovery.
Sent from my HTC One S using xda premium
These are the steps I took that led me here.....
1. flashed ville_recovery_signed.img via Fastboot from here
2. re-locked the bootloader with in fastboot
3. ran RUU_Ville_U_TMOUS_1.53.531.16_Radio_0.16.31501S.02_10.18.31501S.08L_release_262073_signed from here that was from this thread.
http://forum.xda-developers.com/showthread.php?p=25850720
That should help, iv had that problem before and solved it from the post I just linked
Sent from my HTC One S using XDA Premium HD app
Moved To Q&A
Do not open question threads in the development section, thats what Q&A is for.
Chris Boyer said:
First and foremost you need a working recovery with a mounted sd card. Are you able to push anything via fastboot? I found it easiest to use a fastboot script. It dumbs it down to a couple mouse clicks. There is a utility for the one S called all in one. (sorry don't have link) maybe try that to install fresh recovery. One thing for certain, factory reset and then format card has to be done from bootloader mode and then push new recovery.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Yeah i have full control of Fastboot, just not always getting the desired final results. Yes I have the AIO pack and have tried to flash those recoveries w/o results. I mean from the log it looks like that did the trick but nothing changes after reboot, I can't get rid of the current Recovery.
stealthnoodle said:
http://forum.xda-developers.com/showthread.php?p=25850720
That should help, iv had that problem before and solved it from the post I just linked
Sent from my HTC One S using XDA Premium HD app
Click to expand...
Click to collapse
Steath! Now we are getting somewhere!
As I was going through the steps, I got the CWM from the AIO. That was before I had a chance to flash the 2nd time (step3), before I could get to the rest of the steps I allowed the phone to boot normal instead of HBoot, then it reverted back to the other recovery. But as of right now I did flash via AIO, cleared storage, factory defaulted, flashed via AIO again and now I am on step 5.
I am still sitting in the AIO CWM right now. The guide says to flash the UTB rom, which I am unfamiliar with and it appears like a custom rom. So what should I flash and what method should I use? Even though CWM is back I have no means to flash a ROM from there b/c my sd is empty. Should I .....
- flash one of the RUUs via fastboot?
-rename the RUU and push it to the SD via ADB and flash via CWM (like in the guide)?
(not sure if that method works with customRom only or RUUs as well.
enzyme said:
Even though CWM is back I have no means to flash a ROM from there b/c my sd is empty.
Click to expand...
Click to collapse
If you can mount your sdcard partition in recovery, you can then adb push a rom to it and flash it.
On your PC:
adb push yournewrom.zip /sdcard/
Then on your phone, in recovery:
Format system, data, cache
Flash zip from sdcard -> choose zip -> /sdcard/yournewrom.zip
Before you boot into the new rom, flash the boot.img (extract it from the zip) in fastboot.
adb reboot-bootloader
fastboot flash boot boot.img
fastboot reboot
Steath's advice led me to the guide and got me on the right track. Even with detailed instructions, I went in circles for awhile, but in the end I got it. I'm so relieved, its been a stressful 12hrs.
So now I just have one last question. Is it safe to extract boot.img & recovery.img and flash it with fastboot? This might even be a common practice who knows, I'm still very new to much of it.
enzyme said:
Is it safe to extract boot.img & recovery.img and flash it with fastboot? This might even be a common practice...
Click to expand...
Click to collapse
It is safe and common practice (and in many cases required to prevent bootloops) to extract the boot image from the rom you flash, and flash this boot image through fastboot.
Custom roms do not come with their own recovery (only their own boot.img). The only reason to extract a recovery from a RUU or OTA and flash it, is when you need to go back complete stock.
Edit: But if you want to switch to a different custom recovery, then yes, flashing it through recovery is safe and the proper way. (You just don't 'extract' it from anything.)
Hi, at first i would say sorry for my english
So, i want install on my htc sensation custom rom, so i unlock bootloader on htcdev website, everything gone perfectly
Second step was installing CWM recovery and phone rooting, thats gone good too. Tutorial for CWM and root install i have take from this: theunlockr.com/2012/09/20/how-to-root-the-htc-sensation-on-hboot-version-1-27-0000
In next step i did wire-trick on ControlBear 0.5 beta, but phone don't want to reboot and make JuopunutBear logo, so i try to find 0.6 beta, but i can't found it. I found 0.7 beta, and on this wersion i did wire-trick, i miss a little bit with wire (wait too long) and program send me an error, i must click Enter for exit, and i clicked. From that moment my phone don't want to boot, all time i have JuopunutBear screen. I can go in bootloader, but my recovery don't want to start, so i install recovery and root again and try to restore backup from recovery, but system still don't want to boot.
At this moment i can go to bootloader and i have unlock bootloader with htcdev, recovery and probably root, i haven't s-off. My HBOOT version is 1.27.0000
Please help me, i don't know what i should do. Maybe i still can do wire-trick? I don't know :crying: I tried to find RUU, but two RUU don't want to open, and third send me info that they can't update soft and i should download correct program for update ROM memory.
Please help me!:crying:
Hi.
Run your phone's appropriate RUU, care for the region and the model as well, to be exact. For sensation XE, it has an extra LE in its name.
Sent from my HTCSensation using Tapatalk
install 4ext recovery and then enable smartflash then restore the rom backup youve got ..(step #2 and step #3 ..from this guide)
if phone still not booted then do the extra #1 step from the same above guide ...but use the boot.img from the backup you've done (will be available at /sdcard/clockworkmod/backups)
Thanks @ganeshp !!! Phone is booting and android works Thanks a lot :* You're my hero
btw, i used method with flashing my boot.img, becouse restore from 4ext didn't work
cocaine01 said:
Thanks @ganeshp !!! Phone is booting and android works Thanks a lot :* You're my hero
btw, i used method with flashing my boot.img, becouse restore from 4ext didn't work
Click to expand...
Click to collapse
Where did u go wrong? Are you s off now?
I'm not on s-off, , becouse controlbear (0.7 beta) send me an error and i must click enter for exit, after exit my sensation don't want to boot. Probably i have waiting too long for second wire "click" on sdcard, and program send error. Now i have unlock bootloader, 4ext recovery and root, i dont know which version of controlbear i need for wire-trick. If you have good version please send me a link to download
Send from my HTC Sensation
22
I got a link for 0.5beta, I'll pm you incase in case you want to try it (I haven't. Just got it yesterday, havent had a chance)
edit:used the one click tool to root, controlbear worked like a boss, took a few tries with a wire trick, phone rebooted once but no harm done
So if my phone don't want to boot system and stuck on JuopunutBear screen i can unplug my phone, plug in again and still try to do wire-trick, for that moment when phone will have s-off?
cocaine01 said:
So if my phone don't want to boot system and stuck on JuopunutBear screen i can unplug my phone, plug in again and still try to do wire-trick, for that moment when phone will have s-off?
Click to expand...
Click to collapse
you can always try the wire trick multiple times ...even when the phone is stuck at juopunutbear screen.
however if you want ..you can revert back the phone to working condition too (except sdcard) ..controlbear has this functionality too
check troubleshoot point #4 from my soff guide for further details ( link in my signature )
This is the answer for 10 points
This is what i need. Thanks a lot. I will try to do wire-trick again in future (now i know what i need to do when phone is stuck on that screen )
Thanks a lot
Edit, If i have rooted phone, i haven't use temproot.bat ?
Hi, it's me ... again..
I have done wire-trick today, but i have problem I done it, but controlbear send me text that they can't find device after wire-trick, i have unplug phone and try to restart them. I saw joupunutbear screen - again. So first what i have do i opened troubleshot and made 4. a), but phone still stuck on this screen. so i want to go to recovery, but i havent it I have try to flash recovery, but i recieved text that is unavailable or something. So i try to flash boot.img, but i can't do it too I have opened my Bootloader in sensation and i saw that i have ***LOCKED*** and under that S-OFF RL. So if i have ***LOCKED*** bootloader i can't flash anything, right? (boot.img, recovery, itp) I should unlock bootloader again or what? I'm stuck on joupunutbear logo already and have in bootloader ***LOCKED*** and S-OFF (if it's true) Please help me ... again It's possible i haven't root
cocaine01 said:
Hi, it's me ... again..
I have done wire-trick today, but i have problem I done it, but controlbear send me text that they can't find device after wire-trick, i have unplug phone and try to restart them. I saw joupunutbear screen - again. So first what i have do i opened troubleshot and made 4. a), but phone still stuck on this screen. so i want to go to recovery, but i havent it I have try to flash recovery, but i recieved text that is unavailable or something. So i try to flash boot.img, but i can't do it too I have opened my Bootloader in sensation and i saw that i have ***LOCKED*** and under that S-OFF RL. So if i have ***LOCKED*** bootloader i can't flash anything, right? (boot.img, recovery, itp) I should unlock bootloader again or what? I'm stuck on joupunutbear logo already and have in bootloader ***LOCKED*** and S-OFF (if it's true) Please help me ... again It's possible i haven't root
Click to expand...
Click to collapse
just remove the temp root with remove bat.file or whatever it is called
Ok, i have used this, but phone still is stuck on joupunut screen.
While i do wire-trick i haven't use temp-root, becouse i had unlock bootloader via htcdev, i had root and recovery - now i havent anything
cocaine01 said:
Ok, i have used this, but phone still is stuck on joupunut screen.
While i do wire-trick i haven't use temp-root, becouse i had unlock bootloader via htcdev, i had root and recovery - now i havent anything
Click to expand...
Click to collapse
check only step 2 from here(flashing a recovery)
http://forum.xda-developers.com/showthread.php?t=1631861
edit: first do this
flash jb hboot from unlimited.io site(it is unlocked patched)
http://unlimited.io/jbhboots.htm
download the one for sensation(the ics one)
then flash the recovery.img
When I type this:
sudo ./fastboot erase cache
Click to expand...
Click to collapse
into CMD, they send me text that "sudo" isn't recognizable as command or program Maybe i'm too tired...
EDIT: Okay, i'm so stupid :/ i type that without "sudo ./" and now i have hboot 1.27.1111 and i have flashed recovery 4ext. Now i can make root again and install ROM from SD card like this one: http://forum.xda-developers.com/showthread.php?t=2531054 ?
EDIT2: recovery display info that i must do full wipe and microsd card wipe. So i can't restore backup from sd now, right? I must do full wipe with sd card too and install ROM from sd card?
cocaine01 said:
When I type this:
into CMD, they send me text that "sudo" isn't recognizable as command or program Maybe i'm too tired...
EDIT: Okay, i'm so stupid :/ i type that without "sudo ./" and now i have hboot 1.27.1111 and i have flashed recovery 4ext. Now i can make root again and install ROM from SD card like this one: http://forum.xda-developers.com/showthread.php?t=2531054 ?
EDIT2: recovery display info that i must do full wipe and microsd card wipe. So i can't restore backup from sd now, right? I must do full wipe with sd card too and install ROM from sd card?
Click to expand...
Click to collapse
first: if you are willing to flash a custom rom then there is no need to root your current one
all custom roms comes pre-rooted
second: there is no need to wipe your sdcard.where did you see that?
just make a nandroid backup from recovery just in case
then format all partitions except sdcard from recovery
flash the new rom
done
Ok, i have one backup (i made it about 2 weeks ago, when sensation worked normally), so i think i haven't make second. And my recovery is now in safe-mode, so when i wipe partitions it will be normal, right?
Tomorrow i will download Vipers 5.0.0 JB and install it Thanks a lot
cocaine01 said:
Ok, i have one backup (i made it about 2 weeks ago, when sensation worked normally), so i think i haven't make second. And my recovery is now in safe-mode, so when i wipe partitions it will be normal, right?
Tomorrow i will download Vipers 5.0.0 JB and install it Thanks a lot
Click to expand...
Click to collapse
post results
by the way what do you mean by safe-mode?
rzr86 said:
post results
by the way what do you mean by safe-mode?
Click to expand...
Click to collapse
While recovery is booting, every times when i open it, it boot from 0, for second i can see something like "can't mound sd" or something.
when boot is done, recovery recieve me text:
"ATTN: recovery is in safe mode this is because the following partition is not accessible: "cache"
Please enter the wipe menu and wipe cache!
If you changed hboot you should choose to format all partitions (except sdcard)
Afterwards please reboot recovery"
And above "reboot now" i can see " ! SAFE MODE ! "
When i go in Power Menu and chose power off, i can see:
"You are currently in safe_mode.
You means that your internal partition are not accessible.
please wipe all partitions and then reboot recovery!
reboot recovery now? "
Yes or No, i can't power off device, i must take out battery.
cocaine01 said:
While recovery is booting, every times when i open it, it boot from 0, for second i can see something like "can't mound sd" or something.
when boot is done, recovery recieve me text:
"ATTN: recovery is in safe mode this is because the following partition is not accessible: "cache"
Please enter the wipe menu and wipe cache!
If you changed hboot you should choose to format all partitions (except sdcard)
Afterwards please reboot recovery"
And above "reboot now" i can see " ! SAFE MODE ! "
When i go in Power Menu and chose power off, i can see:
"You are currently in safe_mode.
You means that your internal partition are not accessible.
please wipe all partitions and then reboot recovery!
reboot recovery now? "
Yes or No, i can't power off device, i must take out battery.
Click to expand...
Click to collapse
i am seeing this for the first time
ok then wipe cache.it won't harm the device
also did you reboot recovery?
does it show you the same message?
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.