I have the verizon htc droid 4g lte and I am running viper 2.2 with the twap recovery, but my phone can no no longer be seen
with the unblocking tool that I use to get the bootloader unlocked with the first time. when I hook it up to my computer, I can
see both my internal and external card, and I can even read and write to them, but when it comes to the programs recognizing
my phone like they did before, they want. They will no longer recognize my phone. I can flash a few roms,but nothing that requries me to be s-off.
I tried 10.1, but the phone gets stuck when installing the appz part of the rom. So, I am guessing, it must be because I am not s-off. I want to get to s-off now,but I can't.
Any advice would be great. thanks.
MR_PERFECT said:
I have the verizon htc droid 4g lte and I am running viper 2.2 with the twap recovery, but my phone can no no longer be seen
with the unblocking tool that I use to get the bootloader unlocked with the first time. when I hook it up to my computer, I can
see both my internal and external card, and I can even read and write to them, but when it comes to the programs recognizing
my phone like they did before, they want. They will no longer recognize my phone. I can flash a few roms,but nothing that requries me to be s-off.
I tried 10.1, but the phone gets stuck when installing the appz part of the rom. So, I am guessing, it must be because I am not s-off. I want to get to s-off now,but I can't.
Any advice would be great. thanks.
Click to expand...
Click to collapse
Presumably, your bootloader is still unlocked? Rather than using a script or automated tool, follow the manual procedure in this thread for Part 2: Apply SuperCID. After this, reboot your phone to the bootloader and verify SuperCID with fastboot getvar cid, it should return 11111111. Once this is verified, you can follow the instructions for Facepalm S-OFF. Finally, after achieving S-OFF, revert your CID to normal again using the manual instructions for Part 6: Revert your CID to stock.
BTW, use a more meaningful title next time and this post belongs in the q&a/troubleshooting section, not general.
Related
I am an unfortunate rookie, and have made mistakes, hence the name. I want to return my phone to stock from htcdev unlock, s-on, hboot 1.5. with a boot loop on meanom ICS for the evo 3d. I have tried to use older ruu shooters. Relock with fastbot oem lock, and then pg86img. However with the bootloop I can not access anything unless I unlock again, and then go into recovery. This is all that I can think of at the moment that might help.
Kill the rookie!!! PLEASE HELP!!
I had much the same problem with my cdma, hboot 1.5, S-On shooter. When I was S-On none of the ICS roms would work. The all bootlooped on me. If you follow the rooting method found here on xda, it will get you back to a stock Rooted GB Rom.
go into hboot -> fastboot USB-> run command dos -> fastboot cwm-4.0.1.4-shooter.IMG -> flash the 2.17 firmware-> enjoy.
I had to S-off with Juopunutbear, then re-run that root/flash to get past the bootloops.
Sent from my Shooter using xda app-developers app
Unfortunately I have tried that and it still is not working.
My only suggestion would be to try it a few times, other then that, its above my head.
Sent from my shooter using xda app-developers app
rookiemistake said:
I am an unfortunate rookie, and have made mistakes, hence the name. I want to return my phone to stock from htcdev unlock, s-on, hboot 1.5. with a boot loop on meanom ICS for the evo 3d. I have tried to use older ruu shooters. Relock with fastbot oem lock, and then pg86img. However with the bootloop I can not access anything unless I unlock again, and then go into recovery. This is all that I can think of at the moment that might help.
Kill the rookie!!! PLEASE HELP!!
Click to expand...
Click to collapse
Have you tried one of the ruu exe files that you run from your computer? If you are trying to go stock, you should be able to relock the bootloader and run the ruu and that's it.
Sent from my ICS 3VO with Tapatalk 2
First of all I want to thank everyone that has been attempting to assist me with my problem. I have tried to relock since I am on htcdev unlock and then run an ruu force via my computer. I get an installation aborted error when trying to flash pg86img via recovery. I don't know what else to say.
You can't flash a bootloader zip from recovery. You have to flash it from hboot. Also make sure the zip is named correctly "PG86IMG.zip" without the quotes. Also make sure the zip is on the root of your sd as in not in any folders. Once you've named the zip correctly and placed it correctly then power off the phone. Hold down the volume down button and tap the power button. You should boot into the bootloader wait until the phone recognizes the zip and follow the on screen instructions. Hopefully this helps.
#Root-Hack_Mod*Always\=LTE
Thank you again. I tried your directions, it did recognize the pg86img. However it did not give me any instructions to follow. It did however allow me to be able to a partial stock state. My software version is still on the teamgenesis sense v2.9 cdma. Although I do like some of the features on this rom, I would still like to be able to get the OTA of ICS when it is released. Any suggestions?
rookiemistake said:
Thank you again. I tried your directions, it did recognize the pg86img. However it did not give me any instructions to follow. It did however allow me to be able to a partial stock state. My software version is still on the teamgenesis sense v2.9 cdma. Although I do like some of the features on this rom, I would still like to be able to get the OTA of ICS when it is released. Any suggestions?
Click to expand...
Click to collapse
To get the ota release (if it ever comes ) I do believe you will need to be locked and running the existing gingerbread rom. While I am not positive, I think the system uses the props file to determine if an update is applicable, and it will likely not recognize the teamgenesis rom version as being upgradeable.
Now I will likely get flames for saying this, but if you want to put the meanrom v2.4 of ICS on the phone, it can be done with s-on, you just need to follow the correct process. I ran that rom for a while, and it is very stock like, stable, and has a few enhancements that you will not find on a non-rooted stock rom. I never found anything wrong or not working with that rom.
To get it to load, first I downloaded flashimagegui from market, put the meanrom zip file on the sd card and made sure I had a recovery that I could get into. I am using TWRP v2.1.1, lots of folks talk about others like ext4, and I am only going to say use whichever you like, after all it is your phone.
Then with the phone unlocked via the htc method, I started the flashimage app, and browsed to the meanrom file. It extracted the kernel and flashed it. Once that was done, with clear cache buttons selected, rebooted to recovery, and used the install menu selection of TWRP to again flash the same rom file. Once it flashed the file, selected clear cache and dalvik just to be safe, selected reboot system, and it worked great.
Have a great weekend.
So, apparently I am still doing something wrong. I have put the pg86img on the root, relocked to the bootloader, and let it run it's course. However, it will get through with reading it and stops and does not finish anything with loading the system information. I have also tried to run the ruu via usb connection. I keep running into a c++ issue saying runtime error. I have wiped everything and thankfully I did make a backup of the rom and other information that I was runing so I can currently fall back on that.
I am on hboot 1.5, 2.17, and teamgenesis ICS rom for evo 3d.
Apparently there have been rumors that Sprint has finally released the ICS OTA, not that it really matters anymore, but I have run into a few interesting glitches, such as WIFI not staying connected while asleep or disconnecting.
If I have to I am willing to pay to do a netmeeing with someone in order to be able to fix this.
Sorry if it sounds like I am getting frustrated, but I have tried every walkthrough that I have found and have not had any luck with any of them.
Please help.
I forgot to say I am s-on
Hello. So I've tried multiple times flashing ROMs to my device, and have always had problems somewhere along the line. The furthest I got was successfully flashing this ROM, but it ended up in a boot loop. I believed it was due to my device being S-ON, even though I've successfully rooted and unlocked my bootloader via HTCdev and thus I've been attempting to get S-OFF. I tried JuopunutBear but got an error message related to checking my adb and fastboot drivers (Which I'm fairly sure are up to date and working) and I think the problem is I am on HBOOT 1.57. I've been attempting to downgrade using this guide (Which uses Revolutionary to get S-OFF in which case I wouldn't need JuopunutBear). I only got a bit of the way in, however, before I got stuck. After relocking my device it tells you to put the RUU zip on your device, but my computer isn't detecting my device and I'm stuck in the bootloader. I've tried shutting it off, trying all the options in the bootloader, taking out the battery, entering commands into adb, and probably some other things I've forgot, but I'm still stuck on the bootloader and my device isn't detected at all on my computer (Either in command prompt or in the explorer window).
Essentially what I'm asking here is:
How do I get my phone unstuck from bootloader?
Do I need S-OFF to be able to flash ROMs?
If I don't need S-OFF, what was I doing wrong? Should I try a different ROM?
And I suppose I may as well ask if that's a worthwhile ROM. I want something that optimizes my device and allows for custom themes, but otherwise I'm not too picky.
Specs:
Windows Vista (With ADB and fastboot, as well as HTC Sync and other phone drivers. Essentially I think I have all the software I'd need installed.)
HTC EVO 3D CDMA with Virgin Mobile as the carrier.
HTCdev unlocked bootloader
S-ON
HBOOT 1.57
Stock ROM
4ext recovery
Any and all help would be greatly appreciated!
(Also I apologize if I didn't give all the information needed or if I posted this in the incorrect spot. I figured this would be the most appropriate spot since although I have issues with specific processes it's also a fairly general request for help.)
UPDATE: I tried re-unlocking my phone using HTCdev so I'm no longer stuck in bootloader. I'm going to be trying the HBOOT Downgrade Toolkit guide again sometime today or tomorrow to see if I can get it working. I think one of the problems before was that I didn't put the RUU on the sdcard beforehand and then my device wasn't being recognized so i couldn't put it there then. If I put it on beforehand I should be able to update successfully and get past the step I was stuck on before.
If you're son u can only flash sence ROMs.
Sent from my PG86100 using xda app-developers app
cj_302 said:
If you're son u can only flash sence ROMs.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
Er, I'm not quite sure what you're saying here.
UPDATE: I tried re-unlocking my phone using HTCdev so I'm no longer stuck in bootloader. I'm going to be trying the HBOOT Downgrade Toolkit guide again sometime today or tomorrow to see if I can get it working. I think one of the problems before was that I didn't put the RUU on the sdcard beforehand and then my device wasn't being recognized so i couldn't put it there then. If I put it on beforehand I should be able to update successfully and get past the step I was stuck on before.
It will be your hboot causing the problems.
Most recoveries allow you to mount usb storage so you can use that option to connect to your pc and move the ruu across without removing your sdcard etc.
Download G Cloud Backup for Android, up to 8 GB Free.Use this code: [KWLYRO] at signup and we'll both earn space: https://play.google.com/store/apps/details?id=com.genie9.gcloudbackup
Oh how i loathe this POS phone
i have this as my work support phone. It wouldn't reliably stay powered up, any time I did turn it on it took 20+ minutes to acquire data/cell/3g signal. turning on maps crashed the phone. so i figured i'd install a new rom
I have lots of experience with sony ericsson, nexus 4, nexus 7 2012, 2013, acer 10.1 tab. i've done all this stuff before, but i cannot get cyanogen 10 or 11 to install properly, and now my phone sits with a spinning logo doing nothing
i:
unlocked the bootloader as per instructions at htc dev
setup ADB on the phone
first jsut copied the c11.zip to the sd card and tried to install that, same issue on with the HTC logo
used hansoon's kit to sideload c10. claims to have installd, now just spins the logo.
any help would be great.
simonsgray said:
Oh how i loathe this POS phone
i have this as my work support phone. It wouldn't reliably stay powered up, any time I did turn it on it took 20+ minutes to acquire data/cell/3g signal. turning on maps crashed the phone. so i figured i'd install a new rom
I have lots of experience with sony ericsson, nexus 4, nexus 7 2012, 2013, acer 10.1 tab. i've done all this stuff before, but i cannot get cyanogen 10 or 11 to install properly, and now my phone sits with a spinning logo doing nothing
i:
unlocked the bootloader as per instructions at htc dev
setup ADB on the phone
first jsut copied the c11.zip to the sd card and tried to install that, same issue on with the HTC logo
used hansoon's kit to sideload c10. claims to have installd, now just spins the logo.
any help would be great.
Click to expand...
Click to collapse
You give a lot of info in your sig, but nothing there or in your post if you're s-off or on and which recovery you're using. Since, you're Canadian you probably need s-off to flash the latest T-Mobile ruu for the radio. And ext4 seems to be the most trouble-free recovery for the amaze. If s-on you can probably still get CM working if you were already on ICS and flash with smart flash enabled in 4ext. If you're still having issues then try pushing the kernel with adb from hboot wth your pc.
I hope this helps.
Odysseus1962 said:
You give a lot of info in your sig, but nothing there or in your post if you're s-off or on and which recovery you're using. Since, you're Canadian you probably need s-off to flash the latest T-Mobile ruu for the radio. And ext4 seems to be the most trouble-free for the amaze. If s-on you can probably still get CM working if you were already on ICS and flash with smart flash enabled in 4ext. If you're still having issues then try pushing the kernel with adb from hboot wth your pc.
I hope this helps.
Click to expand...
Click to collapse
Thanks man. sig is a little out of date, i havent' needed xda as much since jumping to nexus. TWRP and i didn't do the s-off stuff. it says it needs a stock rom and i just havea spinning cyanogen mod. i will try install the 4ext and see if that changes the results.
Odysseus1962 said:
You give a lot of info in your sig, but nothing there or in your post if you're s-off or on and which recovery you're using. Since, you're Canadian you probably need s-off to flash the latest T-Mobile ruu for the radio. And ext4 seems to be the most trouble-free recovery for the amaze. If s-on you can probably still get CM working if you were already on ICS and flash with smart flash enabled in 4ext. If you're still having issues then try pushing the kernel with adb from hboot wth your pc.
I hope this helps.
Click to expand...
Click to collapse
Tried to install this RUU http://www.androidruu.com/getdownlo...1.41.661.3_release_258801lhwl8053lp8g5hcp.zip
but i get an error status 7 because the file_getprop assert fails.
was trying to install stock so i can do th s-off thing
simonsgray said:
Tried to install this RUU http://www.androidruu.com/getdownlo...1.41.661.3_release_258801lhwl8053lp8g5hcp.zip
but i get an error status 7 because the file_getprop assert fails.
was trying to install stock so i can do th s-off thing
Click to expand...
Click to collapse
If you want to flash back to the stock ICS image you need to first relock your bootloader. When you relock it will say relocked when in hboot. The procedure is to place the image in the root of your external SD card and select from hboot. It should recognize and flash back to stock, however everything other than your external SD gets wiped in the process. So you need to make sure you have a good recent backup. Also, you remember when you first HTC dev unlocked they sent you an image to push to unlock? Well, I hope you saved it, because you'll need it again to re-unlock the bootloader after flashing the firmware image, but before attaining s-off.
However, if you were already on your carrier's latest ICS firmware before you started flashing different ROMs, you probably already have their latest radio. If you install the latest 4ext and enable smart flash, you'll probably succeed in installing any of the source built ROMs (ASOP, CM, PACman, evervolv) without s-off, because ROMs built from the source don't have the CID flag in their binaries.
If you still decide to go back and attain s-off the procedure is as follows: 1) relock your bootloader 2) flash the latest stock firmware for the carrier that sold your device. 3) Unlock your bootloader again using the image and commands you previously did to HTC dev unlock the first time, 4) get s-off using the wire-trick 5) flash the hacked hboot (and another radio if you desire, but not required for most ROMs) 6) super CID to remove all carrier locked file / partition limitations and protections 7) Flash your preferred recovery. Because you're now s-off you can use TWRP, CWM, or 4ext since the protected partitions are no longer an issue. 8) Flash any ROM you want provided it's based on ICS or later (below won't work because the radio is incompatible).
Edit: One other thing to note before starting any of this make sure your battery is fully charged. Also, the first time you boot after installing CM or any ASOP based ROM it can take quite some time to go through the process before you get to the login screen. For me it usually takes a little under 10 mins. It may at first appear to be a little sluggish until the rom settles, usually about 10-15 mins.
I hope this helps
Hi there. So im a huge noob and could use an experienced persons help. I have this Amaze 4G that i unlocked bootloader for, had running Android 4.3 Evervolv rom and all was well. I then needed to sim unlock and the code didn't work and I read I needed to unroot and flash stock. I'm trying to do just that using Hasoons toolkit but can't get much help since the thread is closed. My HBOOT is 1.93.0002 and I try to do the Mainver Error fix and It says device not found. I definetly have the drivers updated as I had to go through all that just to have my device detected in fastboot. I wan't to flash stock Telus RUU. Can anyone please help me?
-Note I also accidentally relocked bootloader without downgrading or unrooting. I quickly unlocked it again, but my device was wiped so I can't boot into any rom. I only have 4EXT recovery and bootloader/fastboot available. I am S-on. Can anyone point me or describe a step by step process to get unrooted or and flashed to stock telus? I will gladly donate $$ for any helpful info as well!
butthurtlocker said:
Hi there. So im a huge noob and could use an experienced persons help. I have this Amaze 4G that i unlocked bootloader for, had running Android 4.3 Evervolv rom and all was well. I then needed to sim unlock and the code didn't work and I read I needed to unroot and flash stock. I'm trying to do just that using Hasoons toolkit but can't get much help since the thread is closed. My HBOOT is 1.93.0002 and I try to do the Mainver Error fix and It says device not found. I definetly have the drivers updated as I had to go through all that just to have my device detected in fastboot. I wan't to flash stock Telus RUU. Can anyone please help me?
-Note I also accidentally relocked bootloader without downgrading or unrooting. I quickly unlocked it again, but my device was wiped so I can't boot into any rom. I only have 4EXT recovery and bootloader/fastboot available. I am S-on. Can anyone point me or describe a step by step process to get unrooted or and flashed to stock telus? I will gladly donate $$ for any helpful info as well!
Click to expand...
Click to collapse
First let's take things one step at a time. If s-on you should still be able to run any of the source built AOSP ROMs like evervolv, PAC, or CM. So if you want to get your handset up and running all you need to do is just push one into your SD card either in recovery or with an adaptor on your PC. Just download one of them to your PC. If you have adb working on it when you enable usb debugging in recovery you'll have access to both your internal SD partition and your SD card. Then just copy the zip to one of them. Then turn off the usb and flash the ROM as usual. Once your phone is back up and running you can read the threads to find out what you need to do the other things you want on your device.
I hope this helps
Ciao
Odysseus1962 said:
First let's take things one step at a time. If s-on you should still be able to run any of the source built AOSP ROMs like evervolv, PAC, or CM. So if you want to get your handset up and running all you need to do is just push one into your SD card either in recovery or with an adaptor on your PC. Just download one of them to your PC. If you have adb working on it when you enable usb debugging in recovery you'll have access to both your internal SD partition and your SD card. Then just copy the zip to one of them. Then turn off the usb and flash the ROM as usual. Once your phone is back up and running you can read the threads to find out what you need to do the other things you want on your device.
I hope this helps
Ciao
Click to expand...
Click to collapse
Thanks for the reply man! That's the thing i have a few issues. First off i can't mount storage via 4ext recovery it always just says failed. I also have no SD card to load a ROM onto. And even when i was up and running i couldn't unroot. I have the toolkit and every guide says to hit mainever fix but my device was never recognized even though i have all the drivers
In recovery format your internal SD then reboot back into recovery. This should allow you to at least be able to mount it. It's file system probably got corrupted while you were monkeying around. Then follow the instructions I posted above. This should at least get you back up and running. For the other procedures you're going to need an external SD card, because you won't be able to flash the factory image from your internal storage unless you're familiar with adb. I don't believe you can do the mainver fix until after s-off, but I'm not 100% on that since I'm s-on and never tried it. Once you're back up and running then we'll try to proceed with the other steps.
This isnt a big problem man if you have recovery you can doo any thing and do as odysseus says
Sent from my HTC_Amaze_4G using Tapatalk
The cell is not rebooting into the system, it stays on the HTC logo until the battery runs out.
I can boot into TWRP with no problem. :good:
I think all system got wiped. :crying:
I downloaded from HTC the: RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4.exe
But it is not working because it can't connect, I supposed it needs the system to work.
How can I unbrick my cell? I have never flashed a ROM before from TWRP, so I don't know exactly what is the file I need to download or the commands. The good news is that I do devOps so I'm used to the shell.
Can someone give me some guidance? :fingers-crossed:
Thanks!
That isn't the right RUU for the AT&T version. You would need to have the US Developer's Edition, or else have s-off and change to the Dev Ed CID or SuperCID, to use the "Brightstar" RUU. If you have the AT&T version, and still on the ATT CID, you need to use an AT&T RUU. I have them listed here: https://forum.xda-developers.com/showthread.php?t=2751432
You don't need a working system/OS to use RUU. But you will need to be in bootloader-fastboot mode (in recovery won't work), and relocked bootloader to RUU (unless s-off, in which case unlocked bootloader is okay). IF you meet all the requirements, and still having USB connection issues, you should try to re-install HTC Sync and HTC Drivers, try another USB cable, and try another USB port on the PC.
If you choose to flash a ROM in TWRP, all you need to do is get a ROM from one of the development threads:https://forum.xda-developers.com/htc-one-m8/development
https://forum.xda-developers.com/htc-one-m8/orig-development
Then you can copy the ROM to the phone's storage using TWRP (to browse the storage); or alternately put the ROM on SD card, using a USB card reader. Then go to "Install" in TWRP and flash the ROM. This also assumes you phone is on relatively recent firmware (Lollipop or Marshmallow is okay for the current ROMs).
Thanks!
For some reason my device is S-On but it is rooted and I have installed TWRP
Please watch this image, it is a picture of the radios, data and all that. thanks!
http://prntscr.com/f11z85
I'm currently downloading the official RUU 4.28.502.1 (Android 5.0.2) from the list you sent me. thanks
By the way, I remember I paid for SunShine to s-off my device some time ago. For some reason, I did S-on again. I'm an idiot right!
I download today SunShine but it is an APK, how don't know how to install it with no system. am I screwed?
From the radio number on your screenshot, I believe it's on AT&T firmware (radio numbers for this phone starting "4.0...." are unique to AT&T). So therefore, the AT&T RUU should work.
But if you want me to determine more definitely, do fastboot getvar all, and post the output (delete IMEI and serial number before posting).
You can't use sunshine with no OS. I agree that making the phone s-on was a mistake, as it serves little purpose unless you were returning the phone to HTC for warranty. But s-off is not needed to recover the phone. Simply using the proper RUU should work.
Once the phone is running properly again (can boot into OS) you can use the sunshine app, and should be able to s-off for no extra $, if you like.