Related
this is what i tried to do: wanted to flash a new rom from my original froyo. read through the guide and got it rooted and installed rom manager and in turn installed recovery. booted into recovery and made a backup. tried installing a rom but it wouldnt let me so at the end installed RA recovery instead. i was able to flash a different rom. mpw tried to boot to recovery to get stock rom it display just the android and exlamation mark.
i can get into bootloader but in recovery wont show a thing as if it lost the recovery program.
tried installing sdk but adb wont see the phone.
SDK version 9, windows vista
Any ideas?
You have the stock recovery...
Read the wiki. Follow the guide for unroot/restore, using passimg method and FRG33. Start again rooting (though you probably want to read a bit more first, and make sure you can connect via adb and fastboot BEFORE you mess with stuff)...
Sent from my Nexus One using XDA App
issue is i cant connect through adb or fastboot since i dont have the debug mode before it all went
You don't need adb or fastboot to follow the unroot/restore guide. I was simply suggesting that you make sure it works before you try and root again.
Unroot/restore.
Get adb and fastboot working.
Play with phone.
Sent from my Nexus One using XDA App
how can i get adb/fastboot working. i went through the guide and dozens of other websites.
adb doesnt see a phone connected even though under device manager it shows an android device.
Install the drivers when in fastboot mode, and you'll have fastboot. It's not adb.
fastboot won't help you unless your bootloader is unlocked. adb you won't get, unless you install a ROM and enable debug, or install a custom recovery - which, again, you won't be able to install without unlocked bootloader. adb doesn't work in bootloader mode, you should have found that in at least one of the "dozen guides".
So, you have 2 options:
1) you have unlocked bootloader or you want to unlock bootloader - in that case, enter the bootloader, connect usb, install fastboot drivers, install custom recovery with fastboot.
2) you don't want to unlock bootloader - then follow the correct advice given to you in danger-rat's posts above.
So, you have 2 options:
1) you have unlocked bootloader or you want to unlock bootloader - in that case, enter the bootloader, connect usb, install fastboot drivers, install custom recovery with fastboot.
2) you don't want to unlock bootloader - then follow the correct advice given to you in danger-rat's posts above.[/QUOTE]
ok problem solved and thanks. all along the dll file for fastboot was in platform-tools instead of tool within the sdk hence why fastboot never worked. unlocked the bootloader and recovered my old image. incase anyone else have this issue.
thanks
Hello,
I am totally new in this forum. I got my HTC Vivid one month ago. Today, I wanted to root it. However, it was off and never back, no LED when plugging via USB.
I unlocked BootLoader according to HTC's instruction.
Update HBoot with PH39IMG.zip
Create recovery Nandroid with VIVID_CWM_ROOT_VER2.zip
During the process flashing a Kernel in this forum, I type:
Code:
fastboot flash boot boot.img
fastboot reboot
It rebooted and I stuck in a boot loop (HTC logo just appeared again and again)
I did a Return to stock (http://forum.xda-developers.com/showthread.php?t=1416836). But I only succeeded in first step (fastboot oem lock).
I stuck in bootloader loop. The phone just response in bootloader forever.
I did recovery from Nandroid. It performed restore but not work.
Neither did with the factory reset.
I tried with another PH39IMG.zip (~35 MBs), it worked. I got my phone back.
After that, I wanted to recover since I can't connect to wifi.
Start recovery in bootloader, the phone was just dead. The PC recognized a connection (HSUSB). I download the driver (Qualcomm HS-USB QDLoader 9008
) but no effect.
I think my phone is bricked.
I will appreciate if anyone can help.
cuongcn said:
Hello,
I am totally new in this forum. I got my HTC Vivid one month ago. Today, I wanted to root it. However, it was off and never back, no LED when plugging via USB.
I unlocked BootLoader according to HTC's instruction.
Update HBoot with PH39IMG.zip
Create recovery Nandroid with VIVID_CWM_ROOT_VER2.zip
During the process flashing a Kernel in this forum, I type:
Code:
fastboot flash boot boot.img
fastboot reboot
It rebooted and I stuck in a boot loop (HTC logo just appeared again and again)
I did a Return to stock (http://forum.xda-developers.com/showthread.php?t=1416836). But I only succeeded in first step (fastboot oem lock).
I stuck in bootloader loop. The phone just response in bootloader forever.
I did recovery from Nandroid. It performed restore but not work.
Neither did with the factory reset.
I tried with another PH39IMG.zip (~35 MBs), it worked. I got my phone back.
After that, I wanted to recover since I can't connect to wifi.
Start recovery in bootloader, the phone was just dead. The PC recognized a connection (HSUSB). I download the driver (Qualcomm HS-USB QDLoader 9008
) but no effect.
I think my phone is bricked.
I will appreciate if anyone can help.
Click to expand...
Click to collapse
did u update hboot with an unlocked bootloader...thats no good
are u still can access Hboot?
sometimes, u should flash a kernel with ROM to work on it. if you still running Stock ROM, don;t flash MOD kernel like Holiraider. it will couse boot loop.
if u still able to access HBOTT, no need to worry.
@meatwad0222: I unlocked bootloader and updated hboot. It succeeded in rooting the phone. I got problem when I tried to flash a kernel.
@prahasta: I can't do anything. The phone never turned on again, even if I plugged the charger, the LED was not on. Pressing power button with volume down did not work at all. In general, I can't access to hboot.
Hm... It will be difficult.. hope it wasn't couse by hardware.
Sent from my HTC Raider X710e using xda premium
I had a similar problem..I unlocked bootloader.and flashed a new ROM. I was then stuck in boot loop..it would go all the way to the screen where it says "upgrading android" and would then reboot...the solution I found was to extract the boot image and flash it...then it rebooted normally with new ROM. Hope this helps...
Sent from my HTC PH39100 using xda premium
austin4913 said:
I had a similar problem..I unlocked bootloader.and flashed a new ROM. I was then stuck in boot loop..it would go all the way to the screen where it says "upgrading android" and would then reboot...the solution I found was to extract the boot image and flash it...then it rebooted normally with new ROM. Hope this helps...
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
if Bootloop, at least u still can access HBoot, but he can't do that.
try to connect it to PC with Full Battery. then check if your PC still detect it. if PC can detect it, try to flash Official RUU.
My laptop does not recognized it. It said that it can't find a driver for that. I searched in xda-forum and I found the driver. Right now, in the device manager of my laptop, it says Qualcomm HS-USB QDLoader 9008. I tried to flash an office RUU but it stopped at <waiting for device>
Thank for your replies.
good to hear your laptop still detect the phone.
u need to pick right RUU for your device.
used Hanson tools, choose to unlock your bootloader again (hope this work). after unlock bootloader, and u can acces HBOOT, choose fastboot mode then instal CMW/WCXs recovery. once done, try to access CWM. if u can acces CWM recovery, there is no worries anymore, u just need to instal correct ROM and Kernel.
My laptop only detects the phone as a Qualcomm chip, not as a phone. When running Hasooon tool, it stops at <waiting for device>.
Sounds like it's in dload mode.
If your phone is in dload mode then I think that is a soft brick...it is fixable, from what I read on another thread, but is more difficult...but not impossible..I had to download HTC drivers for my laptop...the following 2 sites contain the files.
http://forum.xda-developers.com/showthread.php?t=1450105
http://www.theandroidsource.com/viv...65-latest-htc-vivid-sync-driver-download.html
Sent from my HTC PH39100 using xda premium
I talked to HTC customer service for repairing. After everything was set up, I thought that I lost my warranty since I rooted my phone (in HBoot, it said RE-LOCK"). I will give a try with the "wire trick" in the thread "Juopunutbear S-OFF". Hopefully after wire those holes, I can access to the debug mode and "wake up" my phone. Otherwise, I have to spend $5 more to buy those warranty stickers on eBay and have the phone fixed.
I thought that it would be a jtag, but it was not. I did not succeed. I have to send it to HTC for repair.
I think I know the reason caused my problem. I tried to recover why I was on S-ON. Thus, the firmware will "fight" each other and the hardware will not know what it should do. The result is a software-bricked phone.
Okay so i tried to install a custom rom, but it failed, now when ever i execute adb reboot-boatloader the device goes into the boatloader but i can't use adb/fastboot as it doesn't recognize the device. I have windows 8, and it seems windows doesn't find the driver, but when I boot the phone normaly, i can access it using adb (but not fastboot). Any ideas ?
I still can execute the recovery option in the boot loader, but i have nor Zip file to install. I also changed the cid, so the stock rom won't flash.
Advice appreciated
TomFader said:
Okay so i tried to install a custom rom, but it failed, now when ever i execute adb reboot-boatloader the device goes into the boatloader but i can't use adb/fastboot as it doesn't recognize the device. I have windows 8, and it seems windows doesn't find the driver, but when I boot the phone normaly, i can access it using adb (but not fastboot). Any ideas ?
I still can execute the recovery option in the boot loader, but i have nor Zip file to install. I also changed the cid, so the stock rom won't flash.
Advice appreciated
Click to expand...
Click to collapse
I haven't use Windows 8, but so far I don't have any problem with Windows 7. I assume have already install the HTC driver. If not, you can install the HTC syn which comes with the driver.
rocktv88 said:
I haven't use Windows 8, but so far I don't have any problem with Windows 7. I assume have already install the HTC driver. If not, you can install the HTC syn which comes with the driver.
Click to expand...
Click to collapse
Yes, I already installed the HTC drivers (htc sync +d rivers, then uninstalled htc sync, as it get's annoying while plugin on off of the phone)
My biggest problem is that, now fastboot is not running in bootloader mode, so I can't even flash an image or change back the settings i did.
(And of course seems like in bootloader mode, that windows can't find the phone).
So my Idea would be to flash a Zip.rom, like the over the air updates using the recovery option. It's just that i changed the CID to GOOGLE001. :/
TomFader said:
Yes, I already installed the HTC drivers (htc sync +d rivers, then uninstalled htc sync, as it get's annoying while plugin on off of the phone)
My biggest problem is that, now fastboot is not running in bootloader mode, so I can't even flash an image or change back the settings i did.
(And of course seems like in bootloader mode, that windows can't find the phone).
So my Idea would be to flash a Zip.rom, like the over the air updates using the recovery option. It's just that i changed the CID to GOOGLE001. :/
Click to expand...
Click to collapse
Yes, you can uninstall it or use MSCONFIG to remove it on start up. : )
ok, have you try boot the phone in fastboot mode and type "fastboot devices" in command prompt?
rocktv88 said:
Yes, you can uninstall it or use MSCONFIG to remove it on start up. : )
ok, have you try boot the phone in fastboot mode and type "fastboot devices" in command prompt?
Click to expand...
Click to collapse
Jep, so what i do is, i power the phone on, it boots into stock android --> adb devices works and retunrs my phonenumber (also the windwos driver is fine while in stock android)
i do adb reboot-bootloader and it starts into the bootloader (fastboot is turned off in the settings)
and then I'm stuck, Windows can't find the phone (get a bunch of errors with unsopoorted usb device)
also adb devices and fastboot devices is not working, so i tried to execute different commands like flashing or oem unlock,
but all i get is the message<waiting on device>
TomFader said:
Jep, so what i do is, i power the phone on, it boots into stock android --> adb devices works and retunrs my phonenumber (also the windwos driver is fine while in stock android)
i do adb reboot-bootloader and it starts into the bootloader (fastboot is turned off in the settings)
and then I'm stuck, Windows can't find the phone (get a bunch of errors with unsopoorted usb device)
also adb devices and fastboot devices is not working, so i tried to execute different commands like flashing or oem unlock,
but all i get is the message<waiting on device>
Click to expand...
Click to collapse
Are you on S-off?
Anyway, I would do the RUU. restore your phone and try again with a good custom ROM. Did you check MD5 with the rom you download? You still can connect your phone with ADB. That mean your phone is not brick yet. : )
TomFader said:
Okay so i tried to install a custom rom, but it failed, now when ever i execute adb reboot-boatloader the device goes into the boatloader but i can't use adb/fastboot as it doesn't recognize the device. I have windows 8, and it seems windows doesn't find the driver, but when I boot the phone normaly, i can access it using adb (but not fastboot). Any ideas ?
I still can execute the recovery option in the boot loader, but i have nor Zip file to install. I also changed the cid, so the stock rom won't flash.
Advice appreciated
Click to expand...
Click to collapse
windows 8.1 will not work on hboot below 1.54.000 (the only 1.54 that works is from the new GPE 4.4 update).
your going to need access to a windows 7 PC long enough to update your hboot to 1.55 to be able to use fastboot with your phone again. This usually only happens while flashing a RUU not A Rom. Flashing a rom will not affect your version of hboot
clsA said:
windows 8.1 will not work on hboot below 1.54.000 (the only 1.54 that works is from the new GPE 4.4 update).
your going to need access to a windows 7 PC long enough to update your hboot to 1.55 to be able to use fastboot with your phone again. This usually only happens while flashing a RUU not A Rom. Flashing a rom will not affect your version of hboot
Click to expand...
Click to collapse
You are right, i can confirm hboot 1.54.0000 - i was flashing the RUU to convert my HTC ONE toa Google Edition.
So all I need is a windows 7 or lower pc to get fastboot running again?
That's good news, I would have searched for ages.
Yeah it's frustrating I know
If you use the 1.54.000 from the 4.4 GPe update it works also
Sent from my HTC One using Tapatalk
I've got an HTC One with Sprint running 4.2.2 (3.05.651.6). I unlocked the bootloader and rooted it using qbking77's tutorial. I haven't flashed any ROMs on my phone.
Everything has been working fine until yesterday. I took my phone out of my pocket and it was dead. I charged it up and when I turned it on it was stuck in a boot loop on the htc screen. I can get into bootloader fine and fast boot usb shows up on my phone when connected to the computer, but I can't access my TWRP recovery. It shows TeamWin screen then boot loops again.
I have re flashed the recovery and erased the cache. I have also tried to lock the bootloader using Hasoon2000's HTC One All-In-One Toolkit and by connecting to fastboot and typing in "fast boot oem lock. For the toolkit i get device not found and an error and when using the command prompt I get FAILED (status read failed (No such file or directory)). I think its possible my usb debugging may be off since I can't find any devices using adb but my pdanet can find my phone (which needs usb debugging) so I'm not sure.
If I can get it locked, I can use RUU to get back to stock.
I'm running out of options. I'm thinking I can still flash a non-stock rom to get the phone running again and then relock and go to stock. Any ideas on what my issue is and how to fix it? Any input is appreciated.
Hi,
I had unlocked boot loader through HTCdev on latest GB stock ROM. So, obviously I was S-ON.
Meanwhile, I tried many ROMs but manually flashing boot image in hastboot.
I had following status of last running mobile when I tried to get S-OFF
Bootloader status: unlocked
S-ON
HBOOT 2.00.0000
Recovery: CWM
ROM: CynovivoX (JB 4.1.2)
Yesterday, I tried to get S-off by downgrading as per following thread
http://forum.xda-developers.com/showthread.php?t=1705913
There were lots of error while script was running, but one I remember was related to goldcard.
While running RUU, It goes well till I find something Error 131, Customer ID related and than exit.
After trying script and RUU many times, my status is
Bootloader status: Relocked
S-ON
HBOOT 2.00.0000
Recovery: ? (can't see or access anymore)
ROM: -
when running fastboot devices, my device is appearing
but in adb devices, nothing there
So, is there still any possibility to recover from this bricked state?
Desperately looking for expert help as I am not developer but somehow....tried this thinking would not be that difficult business....so help.
Try running the latest RUU and restarting everything over. Make sure to pick the right RUU for your region. The latest build number should be 4.14.XXXXX...
Also, in fastboot, your device isn't supposed to be visible with command of adb devices.
Another thing u could try is to unlock the bootloader again and see if u can access recovery again. Adb works in recovery
Sent from the head of the Hammer
If you can get into fastboot but don't have a recovery installed, can't you just flash a new recovery? E.g. grab clockworkmod, connect your phone to your computer via usb and:
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-vivo.img
(obviously replace above code with actual name of .img file)
err this might be stupid, but click on bootloader > recovery.
Looks like you are already in a sub menu when you boot the bootloader.
The error while downgrading is related to you not relocking your phone before downgrading. Always relock before downgrading with an RUU.
Sent from my Nexus 5
Thanks all guys.
But problem fixed. I have unlocked the bootloader again through htcdev and it worked.
Now let me share issue for all other nondevelopers like me who may also face such issue...
runme script is suppose to push some files through adb commands and then reboot to fastboot mode to lock bootloader.
I had adb drivers installed as I got prompt from statusbar.
However still, while running downgrade script (runme), phone was not detected in adb mode and hence no file was pushed to phone. After reboot, phone detected in fastboot and OEM successfully relocked.
I am really surprised why device not found error not appeared and script not stopped. Later I came to know this by running the script without connecting phone and it ran with asking Q&A with found device, and also reading log file.
Then I ran RUU who wiped everything.
So, my device left without any ROM and with OEM locked. I can't access or install recover, ROM etc and RUU was having goldcard error.
Somehow tried to unlock again through token provided by HTCDev earlier (around 2 years back).
And thing become normal and in my control.
My advise: always check "adb devices" before running the script as I found script is misleading of found device and finally locking device. And if such thing happen, easiest one is to get in unlocked from HTCDev and restart whole process.
RmatriX1218 said:
Thanks all guys.
But problem fixed. I have unlocked the bootloader again through htcdev and it worked.
Now let me share issue for all other nondevelopers like me who may also face such issue...
runme script is suppose to push some files through adb commands and then reboot to fastboot mode to lock bootloader.
I had adb drivers installed as I got prompt from statusbar.
However still, while running downgrade script (runme), phone was not detected in adb mode and hence no file was pushed to phone. After reboot, phone detected in fastboot and OEM successfully relocked.
I am really surprised why device not found error not appeared and script not stopped. Later I came to know this by running the script without connecting phone and it ran with asking Q&A with found device, and also reading log file.
Then I ran RUU who wiped everything.
So, my device left without any ROM and with OEM locked. I can't access or install recover, ROM etc and RUU was having goldcard error.
Somehow tried to unlock again through token provided by HTCDev earlier (around 2 years back).
And thing become normal and in my control.
My advise: always check "adb devices" before running the script as I found script is misleading of found device and finally locking device. And if such thing happen, easiest one is to get in unlocked from HTCDev and restart whole process.
Click to expand...
Click to collapse
From what I'm reading, I'm getting a much clearer image of what happened. I believe your problem to be just driver errors...
The script itself is supposed to run regardless of whether phone is properly connected with proper drivers and whatnot. After all, it's just a set of commands in cmd.
But seeing as you ONLY got Error 131, you could have solved this by simply creating a goldcard.
072665995 said:
From what I'm reading, I'm getting a much clearer image of what happened. I believe your problem to be just driver errors...
The script itself is supposed to run regardless of whether phone is properly connected with proper drivers and whatnot. After all, it's just a set of commands in cmd.
But seeing as you ONLY got Error 131, you could have solved this by simply creating a goldcard.
Click to expand...
Click to collapse
Phone was connected in adb mode. This I can say by checking notifications in android and statusbar prompt in windows 7. While running script only, something got wrong getting adb mode not detected.
Anyway, Goldcard was also in my next line of action, but not sure even after creating Goldcard, I may stuck as version-main was not downgraded to 2. However, tried and got resolved with much simpler effort of unlocking through htcdev.
May be, I am also not that competent to understand developing world and only good enough to simply flash ROMs and updates as per instructions.
Anyway, thanks.