Good day ...
im having a problem with my desire s, i bought it 2 days ago with the same problem when i bought it, its already with the problem when i bought it..
it is priced low so i bought it from a guy being tempted thinking i could fix it or its just a software problem, but unfortunately i got no luck fixing it,
i can get it to bootloader (power+volume down) but i cant seem to enter the recovery from the menu and it is not charging. Tried flashing new recovery but still no luck tried installing RUU but i get an error 155 rom update utility cannot update your android phone.... The weird thing is when i try to charge the phone on wall, it enters CWM and i tried to format cache, do factory reset but theres an error unable to mount sd something like that... And my phone cant be detected using adb cause i think usb debugging is not enabled before it got bootloop, but with fastboot it can be detected...
Here is the detail of my phone:
UNLOCKED
SAGA PVT SHIP S-ON RL
HBOOT-2.00.002
RADIO-3822.10.08.04_M
eMMC-Boot
Aug 22 2011, 15:22:13
more details
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0002
(bootloader) version-baseband: 3822.10.08.
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.405.6
(bootloader) serialno: SH14PTJ06464
(bootloader) imei: ******************
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 3634mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ebd3df7d
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
Can someone tell me what RUU should i use..
THANKS IN ADVANCE GUYS :crying:
To run RUU you need to relock your bootloader.
Google and INDEX thread can tell you everything else.
(well, they could have saved me this post too, if you'd run a simple search for "error 155").
Jack_R1 said:
To run RUU you need to relock your bootloader.
Google and INDEX thread can tell you everything else.
(well, they could have saved me this post too, if you'd run a simple search for "error 155").
Click to expand...
Click to collapse
i have manage to install the ICS RUU, but sad to say still having a boot loop and still unable to go to recovery...
now i think the problem is with fired emmc chip? i hope its not :crying:
i cant seem to follow this guide http://forum.xda-developers.com/showthread.php?t=1284196 due to not able to detect my phone in adb commands.. is there a way for my phone to be detected in adb?? whenever i typed in adb shell i get an error:device not found
another noob question and im sorry for it, if i have a fried emmc chip, will i still be able to boot it in bootloader???
Patutz said:
but theres an error unable to mount sd something like that...
Click to expand...
Click to collapse
Sure you already tried another SD Card!?
Jericoacoara said:
Sure you already tried another SD Card!?
Click to expand...
Click to collapse
i dont think it pertains to the external sd, i think its on internal... well can u tell me how can my computer detect my device via adb??.. im thinking about the fried emmc.. but cant seem to know if its with the emmc issue since my device cant be detected via adb...
Patutz said:
i dont think it pertains to the external sd, i think its on internal... well can u tell me how can my computer detect my device via adb??.. im thinking about the fried emmc.. but cant seem to know if its with the emmc issue since my device cant be detected via adb...
Click to expand...
Click to collapse
If you are stuck into boot loop you can follow this guide http://forum.xda-developers.com/showpost.php?p=21569470&postcount=957 to get logcat information...
TheLegendGZ said:
If you are stuck into boot loop you can follow this guide http://forum.xda-developers.com/showpost.php?p=21569470&postcount=957 to get logcat information...
Click to expand...
Click to collapse
the problem is whenever i type adb devices i get an error no device =(
Patutz said:
the problem is whenever i type adb devices i get an error no device =(
Click to expand...
Click to collapse
First you made a mistake to flash the ICS RUU, because you could have easily check the eMMC from CWM via adb. Now you cannot.
At your current state you can go into the Recovery by choosing it from the bootloader menu, pressing Volume UP + Power when you see a black screen with an exclamation mark. But there is nothing you can do there...
And finally - since your RUU flash was successful and you still cannot boot to the OS the conclusion is obvious - you have wasted your money. Sorry about that
amidabuddha said:
First you made a mistake to flash the ICS RUU, because you could have easily check the eMMC from CWM via adb. Now you cannot.
At your current state you can go into the Recovery by choosing it from the bootloader menu, pressing Volume UP + Power when you see a black screen with an exclamation mark. But there is nothing you can do there...
And finally - since your RUU flash was successful and you still cannot boot to the OS the conclusion is obvious - you have wasted your money. Sorry about that
Click to expand...
Click to collapse
i cant enter recovery from the very beginning, i tried volume up + power but i cant see a black screen with exclamation mark..cant i flash gingerbread RUU anymore to downgrade it?
so i do have fried eMMc? :crying:
You might not have ADB drivers properly installed. If you managed to install RUU, it means your USB port is working and eMMC is likely functional.
Enter the bootloader (Power+VolDown).
Select "RECOVERY" by VolDown/VolUp and press Power.
This should get you to recovery.
Jack_R1 said:
You might not have ADB drivers properly installed. If you managed to install RUU, it means your USB port is working and eMMC is likely functional.
Enter the bootloader (Power+VolDown).
Select "RECOVERY" by VolDown/VolUp and press Power.
This should get you to recovery.
Click to expand...
Click to collapse
i cant enter recovery i tried power+voldown then i select RECOVERY.
but it just go to HTC logo colored green and white background, then after that it shut off, it doesnt go to recovery...and regarding the adb, i try in cmd to type adb then i get all the menu of adb, so i think the adb is installed properly?? by the way, are adb drivers the one included on this link? http://forum.xda-developers.com/showthread.php?t=1272595 i just put the extracted zip file on C drive and i didnt do "setx path /m "%PATH%;C:\android-tools" this command i just type in cmd cd C:\android-tools am i doin it wrong?
Patutz said:
i cant enter recovery i tried power+voldown then i select RECOVERY.
but it just go to HTC logo colored green and white background, then after that it shut off, it doesnt go to recovery...and regarding the adb, i try in cmd to type adb then i get all the menu of adb, so i think the adb is installed properly?? by the way, are adb drivers the one included on this link? http://forum.xda-developers.com/showthread.php?t=1272595 i just put the extracted zip file on C drive and i didnt do "setx path /m "%PATH%;C:\android-tools" this command i just type in cmd cd C:\android-tools am i doin it wrong?
Click to expand...
Click to collapse
You are not doing anything wrong.
The device can be detected by ADB only in a Custom Recovery or a fully booted OS with enabled USB debugging.
It cannot work in a bootloader, Stock Recovery or a bootloop with a secured (Stock) kernel.
The FASBOOT executable works in the bootloader in a "FASTBOOT USB" mode, but there is not much you can do with it, especially with the Stock hboot.
But what Jack_R1 said makes me wonder about your RUU flash. Are you completely sure that it went without errors? Because this cannot happen if your /system or /data partition is corrupted (so called fried eMMC). Moreover if it went fine the Stock recovery should be there and accessible.
amidabuddha said:
You are not doing anything wrong.
The device can be detected by ADB only in a Custom Recovery or a fully booted OS with enabled USB debugging.
It cannot work in a bootloader, Stock Recovery or a bootloop with a secured (Stock) kernel.
The FASBOOT executable works in the bootloader in a "FASTBOOT USB" mode, but there is not much you can do with it, especially with the Stock hboot.
But what Jack_R1 said makes me wonder about your RUU flash. Are you completely sure that it went without errors? Because this cannot happen if your /system or /data partition is corrupted (so called fried eMMC). Moreover if it went fine the Stock recovery should be there and accessible.
Click to expand...
Click to collapse
i tried installing the 4ext recovery and i flashed it ok but still cant get to recovery...i cant access adb since it wont be detected by the computer and i cant s-off my phone since i need to adb push...
yeah im sure that it went smooth, no errors at all, after the installation on RUU its says congratulation upgrade complete you can now use your device something like that haha not sure whats the exact words used there haha wait im goin to RUU again just to be sure that theres no error :fingers-crossed:
Here's the exact thing written on RUU... Congratulations! Your ROM update has been completed. Your Android phone is now ready for use..
hmm do you think even with that notice i can still get error during the update??? and by the way is it normal around 17% during the RUU installation after the "updating radio" around 17% it reboots then on the RUU it says waiting for device, is it normal?
amidabuddha said:
You are not doing anything wrong.
The device can be detected by ADB only in a Custom Recovery or a fully booted OS with enabled USB debugging.
It cannot work in a bootloader, Stock Recovery or a bootloop with a secured (Stock) kernel.
The FASBOOT executable works in the bootloader in a "FASTBOOT USB" mode, but there is not much you can do with it, especially with the Stock hboot.
But what Jack_R1 said makes me wonder about your RUU flash. Are you completely sure that it went without errors? Because this cannot happen if your /system or /data partition is corrupted (so called fried eMMC). Moreover if it went fine the Stock recovery should be there and accessible.
Click to expand...
Click to collapse
i have a great news for me hehe i hope so, i made some new findings on my device,
1st of all i made it to the recovery but the wierd thing is i can only go to recovery when i plugged my phone on the computer, now adb can detect my phone
2nd by following this guide http://forum.xda-developers.com/showthread.php?t=1284196&nocache=1 for the checking of Fried eMMc, i was able to get this result:
<3>[ 7.996978] mmc0: No card detect facilities available
<6>[ 7.997589] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 7.997741] mmc0: Platform slot type: MMC
<6>[ 7.997985] mmc0: 4 bit data mode disabled
<6>[ 7.998107] mmc0: 8 bit data mode enabled
<6>[ 7.998260] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 7.998504] mmc0: Slot eject status = 0
<6>[ 7.998626] mmc0: Power save feature enable = 1
<6>[ 7.998870] mmc0: DM non-cached buffer at ff817000, dma_addr 0x29be3000
<6>[ 7.998992] mmc0: DM cmd busaddr 0x29be3000, cmdptr busaddr 0x29be3300
<6>[ 8.151794] mmc0: new high speed MMC card at address 0001
<6>[ 8.152832] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB
from the result up there i dont think i got a fried emmc? or maybe i maybe wrong? please enlighten me guys i think its a good find? maybe again im wrong? so what do you think is the problem here that my htc got boot looped??
Patutz said:
i
from the result up there i dont think i got a fried emmc? or maybe i maybe wrong? please enlighten me guys i think its a good find? maybe again im wrong? so what do you think is the problem here that my htc got boot looped??
Click to expand...
Click to collapse
Something is very wrong here. And I think that your lack of understanding is a reason for the crappy explanation you are giving here.
You have a custom recovery. How come?
Charge/change your battery, see if anything changes.
amidabuddha said:
Something is very wrong here. And I think that your lack of understanding is a reason for the crappy explanation you are giving here.
You have a custom recovery. How come?
Click to expand...
Click to collapse
His RUU flash obviously didn't work. Not even sure what he's flashing.
amidabuddha said:
Something is very wrong here. And I think that your lack of understanding is a reason for the crappy explanation you are giving here.
You have a custom recovery. How come?
Click to expand...
Click to collapse
i flashed this one http://forum.xda-developers.com/showthread.php?t=1484753 thats how i get the recovery , sorry for the explanations im just being excited hoping id still get a chance to fix this phone
Jack_R1 said:
Charge/change your battery, see if anything changes.
His RUU flash obviously didn't work. Not even sure what he's flashing.
Click to expand...
Click to collapse
im flashing this RUU_SAGA_ICS_35_S_HTC_Europe_14.01.401.2_Radio_20.76.30.0835_3831.19.00.110_release_275068_signed got it from htcdev... ican i downgrade to gingerbread? can u tell me which RUU should i use?
I'm not as knowledgeable as people helping you here, but if it was me is start from scratch and i mean from scratch. Fresh install of everything, drivers etc. I'd then flash a custom rom and seeing as your not s-off. Flash the kernel. Then if its ok is maybe try a fresh download of the ruu and run that.
"Do, or do not. There is no 'try'."
- Yoda
Patutz said:
im flashing this RUU_SAGA_ICS_35_S_HTC_Europe_14.01.401.2_Radio_20.76.30.0835_3831.19.00.110_release_275068_signed got it from htcdev... ican i downgrade to gingerbread? can u tell me which RUU should i use?
Click to expand...
Click to collapse
You can downgrade, but not by a simple RUU flash.
RUU flash doesn't work when bootloader is unlocked.
I'm tired. Read instead of asking.
jugg1es said:
I'm not as knowledgeable as people helping you here, but if it was me is start from scratch and i mean from scratch. Fresh install of everything, drivers etc. I'd then flash a custom rom and seeing as your not s-off. Flash the kernel. Then if its ok is maybe try a fresh download of the ruu and run that.
"Do, or do not. There is no 'try'."
- Yoda
Click to expand...
Click to collapse
can i use any ics kernel??... the bad news is that not whenever i try the same method yesterday when i can enter recovery by putting my phone on pc, now it just loop on recovery when i plugged it in computer, it just enter recovery then shut it self then enter recovery again..
Jack_R1 said:
You can downgrade, but not by a simple RUU flash.
RUU flash doesn't work when bootloader is unlocked.
I'm tired. Read instead of asking.
Click to expand...
Click to collapse
i relocked my bootloader whenever i flash RUU but i get error that its not the right RUU, the only one that i got success in flashing RUU was the one iposted abaove... thats why im asking you guys if you know any compatible RUU for my device cause ive tried alot and still get incompatability
Related
Hello All,
I've tried my hardest to search all over the forums but I still can't figure this out. I'm highlighting all I've tried to eliminate all that junk.
I have a 32A magic and I tried updating the ROM via this post.
I actually installed the radio 6.35.08.29 a little bit lower on the post using recovery mode while it was on my SD.
My device is rooted via theunlockr.com's one click rooting.
I think this was the problem because I was supposed to install the radio 6.35.10.18 because as soon as it was finished installing and rebooting, it keeps rebooting and doesn't even get past the splash screen
Here's where the issues start making me want to pull my hair out.
The good news (from what I'm hearing) is that I can still boot into fastboot and HBoot modes, but I can't get to restore mode at all
I'm getting better with the sdk so I'm understanding fastboot etc now but the main problem I believe is that it won't recognize my device.
I am on windows 7, but yes I've installed the latest drivers and device manager is recognizing it but when I try in cmnd to type adb devices it shows "List of devices attached" and it's emtpy.
I try to type something like adb bugreport and it comes back "error: device not found"
So clearly it doesn't seem to be recognizing the device.
What I was trying to do what push another radio to the device or something but at this point I have no idea what I am to do, especially since I can't get to restore!! Grr!
Any ideas?
p.s.
I thought I'd mention that I think this may be because I didn't (and cannot) select USB debugging from the menu as I can't load the device...
May be bricked... Oh well lol
update
It's only going into fastboot mode when plugged in now.
kob123 said:
It's only going into fastboot mode when plugged in now.
Click to expand...
Click to collapse
fastboot flash radio Radio_HTC_PVT_32A_6.35.10.18.img
fastboot flash hboot hboot-1.76.2007.img
fastboot flash recovery recovery-RA-hero-v1.5.2.img
fastboot erase system -w
fastboot reboot-bootloader
make sure those files are in your tools folder
Thanks,
The files recovery-RA-hero-v1.5.2, Radio_HTC_PVT_32A_6.35.10.18, as well as hboot-1.76.2007 are all in the tools folder.
For fastboot flash radio:
I keep getting:
sending 'radio' ... okay
writing 'radio' ... INFOsignature checking...
FAILED (remote: signature verify fail)
Same thing happens for flashing hboot and recovery as well...
fastboot erase system -w
fastboot reboot-bootloader
both work fine.
Like I said, thanks HUGE so far, but still not working...
im also having the very same problem i cant even flash the sappimg or anything i dont even get the recovery
sapphier pvt 32b ship s-on h
hboot-1.33.0009 (sapp30000)
cpld-10
radio-3.22.20.17
thats all i get please help
ok i got it check it this is what i did i put the engineering-spl-hboot 1.33.2005on to sdcard and rename to update...
then turn on to recovery holding home n power...
then when the triangle picture pops up press home & end call buttons again just press it no need to hold....
once done updating place sappimg.zip on to sdcard...
power on to hboot ...
phonewill load zip file.....
let it do its thing again after done reboot and you got it!!!!!!
i had a card adapter sou will need on let me know if it helped you out....also i formatted my sdcard before i started because phone had problems mounting card when in recovery
http://forum.xda-developers.com/showthread.php?t=530527
download the update.zip
fastboot boot recovery-RA-sapphire-v1.5.2.img
(make sure you use sapphire unless you have the hero radio and spl installed otherwise the hero recovery is needed if you have the cursorsense radio which effectivly makes the magic a hero)
apply the update.zip
then you should be able to fastboot the prev instructions
just fyi make sure u check your radio on the fastboot screen before using the hero or sapphire recovery - make sure you use the proper one!
update
Hey all my problem was also with the spl as well for some reason. I also loaded the newest rogers update instead which the combination did the trick...
kob123 said:
Hey all my problem was also with the spl as well for some reason. I also loaded the newest rogers update instead which the combination did the trick...
Click to expand...
Click to collapse
yeaaa the spl is what my above tricck woulda fixed but if you loaded the latest rogers update you got no root access for now which kinda sucks
question.. i was told i need a late firmware version in order to use ics roms so i decided to do it but idk why my device cant be found via cmd
i have s off
and hboot 1.27.1100
eMMC boot
i think i bricked my phone cause w.e. rom i install it just keeps looping. idk what to do?
there is no way my phone is being recognized by windows the device is not found and i cant even find a way to put it back to stock someone please help :/
at least i need to put s-on and remove recovery so i can send it back to t-mo but i cant do anything via adb. please im really willing to donate the person that helps me please
You're phone isn't bricked if it still turns on. If you can still access recovery why don't you just perform a full wipe then flash a new rom
lileddy305 said:
question.. i was told i need a late firmware version in order to use ics roms so i decided to do it but idk why my device cant be found via cmd
i have s off
and hboot 1.27.1100
eMMC boot
i think i bricked my phone cause w.e. rom i install it just keeps looping. idk what to do?
there is no way my phone is being recognized by windows the device is not found and i cant even find a way to put it back to stock someone please help :/
at least i need to put s-on and remove recovery so i can send it back to t-mo but i cant do anything via adb. please im really willing to donate the person that helps me please
Click to expand...
Click to collapse
Your device is boot looping because the fermware version is not compatible with the ROM you flashed. To get ADB to detect your device you need to boot into Hboot and the select fastboot, then you can use ADB or fastboot commands.
It would be very helpful to post what ROM you flashed. Also you have Hboot 1.27.1100 which is part of the the firmware you need to use ICS so why you were told you need a later version is kind of confusing to me, unless you were wanting to go back to Gingerbread. Please run the following command and post back everything except your IMEI number.
Code:
fastboot getvar all
Have you tried any of the other methods
There are two things you need to look at
1) Is the device in usb debugging enabled?
2) other than using the standard ADB method there are a few other easier methods
a) Droid explorer
i can supply a link if needed
b) The sensation all in one toolkit
http://forum.xda-developers.com/showthread.php?t=1497404
if you have any other ? feel free to contact me as i have been there
kampj007 said:
There are two things you need to look at
1) Is the device in usb debugging enabled?=Invalid the OP can not currently boot to OS.
2) other than using the standard ADB method there are a few other easier methods=Invalid the OP can not currently boot to OS.
a) Droid explorer
i can supply a link if needed=Invalid the OP can not currently boot to OS.
b) The sensation all in one toolkit
http://forum.xda-developers.com/showthread.php?t=1497404=Invalid because the only tool needed by the OP from the toolkit is boot to recovery, but it uses ADB to do this and without being booted into the OS and having USB debugging enabled this will not work
if you have any other ? feel free to contact me as i have been there=Thanks for your willingness to help
Click to expand...
Click to collapse
Also about the toolkit, seeing as they will have to boot to Hboot and then select fastboot to be able to use ADB and fastboot commands. So the toolkit is not going to do the OP any good. The OP will have to either change firmware versions or flash a ROM that is compatible with the firmware version they have to solve the problem.
Wait a minute...
I have been in same situation and what i did was connect the phone via Usb and turn it on. Went into fastboot and then using the programs i talked about it allowed me to load software and change items as needed. I was able to connect through droid explorer as soon as it turned on and it helps u load into recovery and fastboot so that u can adjust as needed.
kampj007 said:
Wait a minute...
I have been in same situation and what i did was connect the phone via Usb and turn it on. Went into fastboot and then using the programs i talked about it allowed me to load software and change items as needed. I was able to connect through droid explorer as soon as it turned on and it helps u load into recovery and fastboot so that u can adjust as needed.
Click to expand...
Click to collapse
Exactly you had to boot to the Hboot and then choose fastboot for them to use the programs. Plus the OP is already S-off and can manually boot into Hboot then to recovery. So the tool kit has nothing to offer the OP at all. Yes they can be in fastboot and use Droid Explorer to copy any needed .zip be it a PG58IMG.zip or a ROM.zip, but they can also do this within their recovery by USB mass storage in recovery.
I do not mean to offend but I just do not want to see this made more complicated than it is for the OP. It is really a very simple problem and has a very simple fix.
Hello,
I am in similar situation. I cannot get my device to be recognized either. Here is what getvar all showed me:
"C:\adb>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.29.0000
INFOversion-baseband: 11.24A.3504.31_M
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.33.401.106
INFOserialno: SH164T500176
INFOimei: 355066045001866
INFOproduct: pyramid
INFOplatform: HBOOT-8260
INFOmodelid: PG5810000
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 3905mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 705f86f6
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.497s"
Any help would be appreciated. Thanks!
C:\adb>
twocrows said:
Hello,
I am in similar situation. I cannot get my device to be recognized either. Here is what getvar all showed me:
"C:\adb>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.29.0000
INFOversion-baseband: 11.24A.3504.31_M
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.33.401.106
INFOserialno: SH164T500176
INFOimei: 355066045001866
INFOproduct: pyramid
INFOplatform: HBOOT-8260
INFOmodelid: PG5810000
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 3905mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 705f86f6
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.497s"
Any help would be appreciated. Thanks!
C:\adb>
Click to expand...
Click to collapse
do you have enabled usb debugging mode from settings?
do you have installed htc drivers?
use also usb 2.0 ports not 3.0
just install htc sync and do again
rzr86 said:
do you have enabled usb debugging mode from settings?
do you have installed htc drivers?
use also usb 2.0 ports not 3.0
Click to expand...
Click to collapse
No to usb debugging mode
Yes to installed htc drivers
will make sure to use usb 3.0
twocrows said:
No to usb debugging mode
Yes to installed htc drivers
will make sure to use usb 3.0
Click to expand...
Click to collapse
wait not 3.0 use 2.0 ports
T-Macgnolia said:
Your device is boot looping because the fermware version is not compatible with the ROM you flashed. To get ADB to detect your device you need to boot into Hboot and the select fastboot, then you can use ADB or fastboot commands.
It would be very helpful to post what ROM you flashed. Also you have Hboot 1.27.1100 which is part of the the firmware you need to use ICS so why you were told you need a later version is kind of confusing to me, unless you were wanting to go back to Gingerbread. Please run the following command and post back everything except your IMEI number.
Code:
fastboot getvar all
Click to expand...
Click to collapse
Adb will recognize device while in fastboot?
I always thought fastboot cmds were for while in fastboot, and adb was for while booted to android?
Sent from my EVO using xda premium
scottspa74 said:
Adb will recognize device while in fastboot?
I always thought fastboot cmds were for while in fastboot, and adb was for while booted to android?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
No fastboot mode is a developer tool first and secondly a fail safe to be able to communicate with ADB and fastboot if something goes drastically wrong such as not being able to boot to recovery or boot to the OS either one with the device and it needs to have the OS re installed. Try booting to fastboot mode and then connect your device to your computer with working ADB and type in adb devices it will show you the device ID.
miillaaad said:
just install htc sync and do again
Click to expand...
Click to collapse
Did that, no dice
Still not seeing via adb and for whatever reason that means unable to flash new boot.img
---------- Post added at 12:52 PM ---------- Previous post was at 12:47 PM ----------
So ended up going back to stock ruu.
Got bootloader unlocked, but adb still says device not found!!
I flash new (4EXT) recovery and it says it flashes ok, but never ever works.
Tried different laptops, usb cords, and installing htc sync, uninstalling htc sync, htc sync manager, etc
All have made no difference
USB debugging is enabled
Any ideas?!?
twocrows said:
Did that, no dice
Still not seeing via adb and for whatever reason that means unable to flash new boot.img
---------- Post added at 12:52 PM ---------- Previous post was at 12:47 PM ----------
So ended up going back to stock ruu.
Got bootloader unlocked, but adb still says device not found!!
I flash new (4EXT) recovery and it says it flashes ok, but never ever works.
Tried different laptops, usb cords, and installing htc sync, uninstalling htc sync, htc sync manager, etc
All have made no difference
USB debugging is enabled
Any ideas?!?
Click to expand...
Click to collapse
Funnily enough, I never got adb recognized on stock rom.
After custom rom, it does.
twocrows said:
Did that, no dice
Still not seeing via adb and for whatever reason that means unable to flash new boot.img
---------- Post added at 12:52 PM ---------- Previous post was at 12:47 PM ----------
So ended up going back to stock ruu.
Got bootloader unlocked, but adb still says device not found!!
I flash new (4EXT) recovery and it says it flashes ok, but never ever works.
Tried different laptops, usb cords, and installing htc sync, uninstalling htc sync, htc sync manager, etc
All have made no difference
USB debugging is enabled
Any ideas?!?
Click to expand...
Click to collapse
use adb toggle app from play store
see how it goes
twocrows said:
Did that, no dice
Still not seeing via adb and for whatever reason that means unable to flash new boot.img
---------- Post added at 12:52 PM ---------- Previous post was at 12:47 PM ----------
So ended up going back to stock ruu.
Got bootloader unlocked, but adb still says device not found!!
I flash new (4EXT) recovery and it says it flashes ok, but never ever works.
Tried different laptops, usb cords, and installing htc sync, uninstalling htc sync, htc sync manager, etc
All have made no difference
USB debugging is enabled
Any ideas?!?
Click to expand...
Click to collapse
Maybe you should check everything is in order on low level, when your phone is connected to your computer, use lsusb under linux (usbview under windows) to check if the device is recognized by the OS.
OK, so I am a bit embarrassed on two counts:
1) when phone was booted up into ROM adb finally recognized it! I had a big duh moment.
2) it seems that at the root of the problem was a syntax error.
I was not renaming the recovery.img file properly. I was typing the command "fastboot flash recovery 4ext.img" and didn't rename file 4ext.img to "recovery.img" Cause when I renamed the file to "recovery.img" and then typed command "fastboot flash recovery recovery.img" I could finally boot back into recovery!
I did however have to flash boot.img after installing the newest Viper ROM. But here I am back on a great custom ROM! Thank you for all your help even if it didn't work it gave me the encouragement to keep trying.
Peace!
Sent from my HTC Sensation 4G using xda premium
Hi !
I have been trying to fix my htc one s (s4) for several days now, and i'm stuck.
I tried to update my HBOOT and get back to stock rom by flashing a RUU but I got the wrong one (signature verification fail) but I'm not sure that's what caused the problem.
When I plug my phone in in recovery (TWRP or CWM) an empty disk is detected on my computer but no sd card so i can't format it or load another ROM to be flashed.
I did a factory reset to see if it would fix it but it did not.
I have no ROM left on my phone, no backup available, adb does not work ( each adb command gets me a error:device not found ) and adb devices can't see my phone.
My HTC Drivers are updated.
Fastboot and bootloader, however, still work.
I have tried changing cable.
When I wipe dalvik in TWRP, I get this line among the other ones in the log:
/sd-ext not present, skipping
when i do a factory reset one of the line is
E: unknowv olume for path [/sd-ext]
And sometimes, although I'm not sure what triggers it, I get a bunch of
Unable to open ums lunfile (No such file or directory)
My phone is S-ON, H-BOOT is 1.14.0002
I don't know what to try anymore I hope I'm not the owner of a shiny little brick.
Does anyone have any ideas what my fix it ?
I apologize for my english if my grammar is poor, I'm French.
Any help would be appreciated. Thanks.
dominolapin said:
Hi !
I have been trying to fix my htc one s (s4) for several days now, and i'm stuck.
I tried to update my HBOOT and get back to stock rom by flashing a RUU but I got the wrong one (signature verification fail) but I'm not sure that's what caused the problem.
When I plug my phone in in recovery (TWRP or CWM) an empty disk is detected on my computer but no sd card so i can't format it or load another ROM to be flashed.
I did a factory reset to see if it would fix it but it did not.
I have no ROM left on my phone, no backup available, adb does not work ( each adb command gets me a error:device not found ) and adb devices can't see my phone.
My HTC Drivers are updated.
Fastboot and bootloader, however, still work.
I have tried changing cable.
When I wipe dalvik in TWRP, I get this line among the other ones in the log:
/sd-ext not present, skipping
when i do a factory reset one of the line is
E: unknowv olume for path [/sd-ext]
And sometimes, although I'm not sure what triggers it, I get a bunch of
Unable to open ums lunfile (No such file or directory)
My phone is S-ON, H-BOOT is 1.14.0002
I don't know what to try anymore I hope I'm not the owner of a shiny little brick.
Does anyone have any ideas what my fix it ?
I apologize for my english if my grammar is poor, I'm French.
Any help would be appreciated. Thanks.
Click to expand...
Click to collapse
Well the good thing is you don't have a bricked device your just in a bad spot atm so
Wipe the sd card in twrp from wipe menu
Download the newist ruu before you do that flash stock recovery and relock bootloader then flash the ruu
Sent from my HTC One S using Tapatalk 4
Flashalot said:
Well the good thing is you don't have a bricked device your just in a bad spot atm so
Wipe the sd card in twrp from wipe menu
Download the newist ruu before you do that flash stock recovery and relock bootloader then flash the ruu
Sent from my HTC One S using Tapatalk 4
Click to expand...
Click to collapse
First, thanks for the quick reponse.
So I flashed a custom recovery but instead of having a menu i get a red triangle and it stops. Then after several minutes the phone goes into bootloop.
Any ideas !
dominolapin said:
First, thanks for the quick reponse.
So I flashed a custom recovery but instead of having a menu i get a red triangle and it stops. Then after several minutes the phone goes into bootloop.
Any ideas !
Click to expand...
Click to collapse
I tried nevertheless to lock and run the ruu.
upon lock:
c:\fastboot>fastboot oem lock
< waiting for device >
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642040 (0x1FDDFD78)
FAILED (status read failed (Unknown error))
finished. total time: 0.944s
upon ruu:
it starts normally and then ERROR 131 error id client
and that's it.
my ruu is RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed
dominolapin said:
First, thanks for the quick reponse.
So I flashed a custom recovery but instead of having a menu i get a red triangle and it stops. Then after several minutes the phone goes into bootloop.
Any ideas !
Click to expand...
Click to collapse
I tried nevertheless to lock and run the ruu.
upon lock:
c:\fastboot>fastboot oem lock
< waiting for device >
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642040 (0x1FDDFD78)
FAILED (status read failed (Unknown error))
finished. total time: 0.944s
upon ruu:
it starts normally and then ERROR 131 error id client
and that's it.
my ruu is RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed
dominolapin said:
First, thanks for the quick reponse.
So I flashed a custom recovery but instead of having a menu i get a red triangle and it stops. Then after several minutes the phone goes into bootloop.
Any ideas !
Click to expand...
Click to collapse
"STOCK" recovery. I think you have tried with CUSTOM recovery.
Here is the link for stock recovery. The second download link is the stock recovery image
Flash stock recovery, then relock boot loader and then follow the above procedure :good:
Actually I did flash the stock recovery I just typed custom by mistake. Sorry about that. The one I flashed even came from the same link .
I searched on the forums and I might not have flashed the right ruu.
But i can't seam to find the right one, because strangely "fastboot getvar version-main" gives a blank result.
Hboot 1.14.0002
radio 1.08es.50.02.16
CID HTC_247
Hello Guys, I need your help.
I got this INSPIRE 4G from a friend. When he gave it to me, he said it needed to be flashed.
The thing is, When you press the power button, it boots straight up into Fastboot.
Here Is my Hboot Info
ACE PVT SHIP S-OFF RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.09.04.11_M2
Emmc-boot
Apr 12 2011,00:55:45
In Fastboot, i can move around with the volume buttons and power buttons(so that means the phone booting straight into Fastboot isnt a result of one of the volume buttons being stuck.)
When i try to access recovery from the Bootloader, It vibrates 6 to 8 times then the screen becomes black,it stays that way until i do a battery pull.
When i select factory reset from the bootloader, it does nothing.
WHen i select Image CRC from the Bootloader,These is what is printed on the screen.
OSBL: 0xC2C4DD79
AMSS: 0x6CC260EB
HBOOT: 0xF9E06F63
BOOT: 0x0
RECOVERY: 0x0
SYSTEM: 0x0
As the digit are displayed, the first three look okay,but the last three which are BOOT RECOVERY and SYSTEM seem to have no digits, Which kinda looks like its empty.
THESE ARE THE SOLUTIONS I HAVE TRIED.
1. I tried flashing a recovery from Fastboot, but it gives an error like this:
C:\Program Files\Minimal ADB and Fastboot>fastboot devices
HT0BFRX06133 fastboot
C:\Program Files\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
sending 'recovery' (3704 KB)...
OKAY [ 0.664s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.672s
I get the same errors when i try to flash,erase or format the rest of the partitions(BOOT,SYSTEM).
2. I have also tried the HTC RUU, it finds the device and then gets stuck when it tries to boot into Android.
I have also tried the HTC RUU Hboot update but it also fails like the RUU ROm update.
3. I have also tried to flash the STock rom as PD98IMG.zip via bootloader, but when it finds the file, it asks me to press volume up to start update, when i press volume up, it loads the file and when its suppose to flash it, it sort of skips it and move to the next. It does that until its done the asks me to press power to reboot. Since it skips the files it stays the same after reboot.
3.I have Also tried flashing Eng-Hboot as PD98IMG.zip, But it skips that also.
4. I also tried to use this command Fastboot oem boot
And this is what i get:
C:\Program Files\Minimal ADB and Fastboot>Fastboot oem boot
...
(bootloader) Error status=0x400008
(bootloader) [SD_HW_ERR] SD: read fail ..
(bootloader) DATA_TIMEOUT
(bootloader) [SD_HW_ERR] read data fail in CMD17
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(453): error 13
(bootloader) [ERR] boot image does not exist!!!
OKAY [ 1.418s]
finished. total time: 1.418s
I am begining to think that some how the partitions are corrupt or something.
PLEASE HELP ME OUT!!
@krook6023 The reason why i posted there also was because i wasnt sure what device it is wether its a DHD or INSPIRE 4G since it doesnt boot up and is stuck in bootloader,thats why i posted there also.Hope you understand and open the other thread incase someone over there has the answer to my problem.
You are almost on the right track but are doing each step wrong.
1. You are still bootloader locked so no fastboot commands will work.
2. If you want to run the RUU you have to place the phone into. Fastboot mode first. Select fastboot mode and you should see fastboot usb on phone screen and then the RUU will recognize it as long as you have an uncoerupted sd card installed.
3. PD98IMG files need to have the appropriate android-info.txt to run properly.
4. This is obvious as you don't have a boot img.
I would try the RUU method first.
spokanite said:
You are almost on the right track but are doing each step wrong.
1. You are still bootloader locked so no fastboot commands will work.
2. If you want to run the RUU you have to place the phone into. Fastboot mode first. Select fastboot mode and you should see fastboot usb on phone screen and then the RUU will recognize it as long as you have an uncoerupted sd card installed.
3. PD98IMG files need to have the appropriate android-info.txt to run properly.
4. This is obvious as you don't have a boot img.
I would try the RUU method first.
Click to expand...
Click to collapse
Thanks for your reply.But i tried 2. and made sure android-info.txt was appropriate, it just wouldnt flash. Looked like the partitions were corrupt thats why it wouldnt flash.
This is how it usually acts.
It finds the file, Loads the file on the upper right side of the bootloader with a green loading bar, after that, when its time for it to flash, normally shows up in red loading bar. It just moves as if it was flashing a 1kilobyte file. Then asks me to reboot.
After reboot nothing happens. Stays the same way.
But Right now, its even worse. After installing QHSUSB_DLOAD drivers, its refused to boot into bootloader ever since. but shows up as QHSUSB_DLOAD when connected to my pc.
Wait, you're S-Off, so you don't need to unlock. What recovery are you trying to flash?
bananagranola said:
Wait, you're S-Off, so you don't need to unlock. What recovery are you trying to flash?
Click to expand...
Click to collapse
I tried flashing CWM,TWRP,STOCK.... but non of them worked.
But as i said, after installing some drivers i found for QHSUSB_DLOAD, it no longer boots into bootloader.
But when i connect the device to a computer it only shows up as QHSUSB_DLOAD.
Any Help On that?
Nope, no idea. What drivers? From where?
bananagranola said:
Nope, no idea. What drivers? From where?
Click to expand...
Click to collapse
I found it on one of the threads.
at first, when the phone is connected to the pc, the charge light turns on and shows up as QHSUSB_DLOAD, but now no light or bootloader, just QHSUSB_DLOAD
Was it a DHD thread?
bananagranola said:
Was it a DHD thread?
Click to expand...
Click to collapse
Yea i guess so.
After the driver stopped the device from booting into bootloader, i read the README file that came with the driver and found out that it was for Some sort of Qualcomm Modem Device.
I guess thats why it bricked the device.
What thread?
bananagranola said:
What thread?
Click to expand...
Click to collapse
I cant seem to remember what thread it is. Cause I downloaded lost of the drivers from different threads. So I cant tell which one is from which thread.
Yeah, I don't think I can help you then.
Is it actually fully bricked yet? What exactly happen when you power on the device unplugged usb?
Hello Everyone. Sorry Noob here. I just want to ask for help for my "bricked" htc u11. My HTC u11 wont boot after I upgraded it to OREO.
-Phone respond to Power button. But it just give me a blank screen and it vibrates.
-When connected to a charger, phone's screen blinks with battery icon and a lightning icon inside the battery icon. (I assumed it is not charging)
-Phone can enter Fastboot mode only using the button combination and fastboot can detects the device. ADB can't detect the device due to I can't find a way to enable DEVELOPERS option/USB debbuging because phone is dead and not booting to homescreen.
-CAN'T boot to recovery/bootloader/download mode
-Secure state : S-Off
-Device State: RELOCKED
-PC device manager can detect the phone under Android USB Devices as My HTC
I tried to flash TWRP but no luck. It wont boot to recovery. Everytime I choose "Boot to recovery" in Fastboot mode the phones turn off but wont boot to recovery. the phone turns off but after a seconds the screen blinks with the battery icon.
I dont know what to do now. I hope u can help me with this. Thank You in advance. Have a great day ahead!
not Tony Stark said:
Hello Everyone. Sorry Noob here. I just want to ask for help for my "bricked" htc u11. My HTC u11 wont boot after I upgraded it to OREO.
-Phone respond to Power button. But it just give me a blank screen and it vibrates.
-When connected to a charger, phone's screen blinks with battery icon and a lightning icon inside the battery icon. (I assumed it is not charging)
-Phone can enter Fastboot mode only using the button combination and fastboot can detects the device. ADB can't detect the device due to I can't find a way to enable DEVELOPERS option/USB debbuging because phone is dead and not booting to homescreen.
-CAN'T boot to recovery/bootloader/download mode
-Secure state : S-Off
-Device State: RELOCKED
-PC device manager can detect the phone under Android USB Devices as My HTC
I tried to flash TWRP but no luck. It wont boot to recovery. Everytime I choose "Boot to recovery" in Fastboot mode the phones turn off but wont boot to recovery. the phone turns off but after a seconds the screen blinks with the battery icon.
I dont know what to do now. I hope u can help me with this. Thank You in advance. Have a great day ahead!
Click to expand...
Click to collapse
Hello, let's try and see if anyone can help you.
First of all, you should give us some information on the firmware version you were using before upgrading to Oreo.
Try to restart it in fastbboot and then connect it to the PC and type the following commands:
- fastboot devices (if it works it should recognize the device and continue with the next command);
- fastboot getvar all (tell me the information you see on the line (bootloader) version-main:
Let us know...
paulpier007 said:
Hello, let's try and see if anyone can help you.
First of all, you should give us some information on the firmware version you were using before upgrading to Oreo.
Try to restart it in fastbboot and then connect it to the PC and type the following commands:
- fastboot devices (if it works it should recognize the device and continue with the next command);
- fastboot getvar all (tell me the information you see on the line (bootloader) version-main:
Let us know...
Click to expand...
Click to collapse
Hi thank you for your reply. Yes fastboot recognizes my Device. and heres the getvar all command result.
(bootloader) boot-mode:FASTBOOT
(bootloader) unlocked:no
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) battery-soc-ok:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) variant:MSM UFS
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache 0xE000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xDAD000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xEF000000
(bootloader) secure:yes
(bootloader) serialno:HT73G1800223
(bootloader) product:HTC_Phone
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi
unfortunately I forgot the firmware version before i upgraded to oreo.
You could try to reflash oreo as you have soff, just grab an OTA file compatible with your cid and flash it in download mode
vegetaleb said:
You could try to reflash oreo as you have soff, just grab an OTA file compatible with your cid and flash it in download mode
Click to expand...
Click to collapse
I tried this already but I got an error. I'll try it again and post the error here. And i' ll check also the ota file. thanks for the reply
not Tony Stark said:
I tried this already but I got an error. I'll try it again and post the error here. And i' ll check also the ota file. thanks for the reply
Click to expand...
Click to collapse
Just flash you RUU again and you are good to go.
Most important thing: how did you update to Oreo?
Did you flash an OTA from SD card?
If yes did you pick the proper CID?
vegetaleb said:
Most important thing: how did you update to Oreo?
Did you flash an OTA from SD card?
If yes did you pick the proper CID?
Click to expand...
Click to collapse
Thru OTA
zopostyle said:
Just flash you RUU again and you are good to go.
Click to expand...
Click to collapse
Im downloading now the RUU. I will update u guys later. thanks for your help.
not Tony Stark said:
Thru OTA
Click to expand...
Click to collapse
Did you check the CID? a wrong CID can bring the phone
When going s-off via sunshine app it is only s-off till next reboot. After that it is s-on again and you can't flash firmware till you get to s-off again via sunshine app.
Trying to ruu the device is one way to go.
Send from the amazing HTC U11
zopostyle said:
Just flash you RUU again and you are good to go.
Click to expand...
Click to collapse
I downloaded the RUU and trries to flash it via fastboot. I tried the command " fastboot oem rebootRUU " but everytime i do this the phone just shut down and not booting with that black screen with htc logo. Then i need to do the buttons combination again to open the device to fastboot mode. I cant flash the RUU because i cant enter the RUU mode. I tried to flash the rom on fastboot mode and this is the error
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
any help guys? Thank you in advance
zopostyle said:
Just flash you RUU again and you are good to go.
Click to expand...
Click to collapse
vegetaleb said:
Did you check the CID? a wrong CID can bring the phone
Click to expand...
Click to collapse
Hello. I upgrsded to OREO officially. on phones settings - update.
Did you flash a custom bootloader before doign the update? You know like custom bootloader that don't show the warning message when you root your phone.
If so then it's the culprit because you have to flash back stock bootloader before trying a RUU or big OTA like nougat to Oreo.
So for now you have access to download mode?
vegetaleb said:
Did you check the CID? a wrong CID can bring the phone
Click to expand...
Click to collapse
Wrong cid and it won't flash.
Most likely took an ota on a rooted phone. Needs to be flashed back to stock.
*WARNING* do not s-on or relock the bootloader when you want to update. Just flash a signed ruu.zip from the external sdcard and you're good to go. It will unroot but it will leave s-off and unlocked bl alone. There is absolutely no reason whatsoever to s-on or lock the bootloader. Doing so will cause more problems than it solves.