Rogers HTC one xl
2.14 s-on, bootloader unlocked at htcdev, running the new Cleanrom (sense 5), everything was fine.
Now in a bootloop as a result of running the Beastmode 3.5 installer
Can't get into fastboot with "power + volume down, wait for flashing leds to stop, screen to go black, then let go of power and continue to hold volume"
not sure why. I've been in fastboot many times and know the procedure.
Obviously next step would be to adb reboot bootloader, go into recovery and flash my backup....
But... list of devices attached: zilch.
Any idea?
dkom1 said:
Rogers HTC one xl
2.14 s-on, bootloader unlocked at htcdev, running the new Cleanrom (sense 5), everything was fine.
Now in a bootloop as a result of running the Beastmode 3.5 installer
Can't get into fastboot with "power + volume down, wait for flashing leds to stop, screen to go black, then let go of power and continue to hold volume"
not sure why. I've been in fastboot many times and know the procedure.
Obviously next step would be to adb reboot bootloader, go into recovery and flash my backup....
But... list of devices attached: zilch.
Any idea?
Click to expand...
Click to collapse
With the new 4.2.2 Android version ADB has a security feature that has to be authenticated on the users screen before the phone can be accessed.
You also need to check your ADB version: 1.0.29 or 1.0.31?
1.0.29 - Will not see your device/gives a "device offline" output.
1.0.31 - Will give a prompt on your device asking for authentication. This is the one you want.
To check your ADB version, nav to your ADB folder in cmd prompt and type "adb version" no quotes.
If it gives you 1.0.29, you need to update using your SDK manager.
To do this you need to nav to your /tools folder in your SDK folder. Here you will type "android" no quotes. Then follow the upgrade process.
Just hold volume down, the next time it starts the boot loop you should get into bootloader.
Sent from my Evita
Uh oh - tried the above with no luck. Just flashed Viper XL 4.2 in TWRP - but now it's just in a loop between the htc dev warning screen, the htc one screen, then off.
Volume down doesn't work. ADB doesn't see it (just installed the new one).
Help please.
Myrder said:
With the new 4.2.2 Android version ADB has a security feature that has to be authenticated on the users screen before the phone can be accessed.
You also need to check your ADB version: 1.0.29 or 1.0.31?
1.0.29 - Will not see your device/gives a "device offline" output.
1.0.31 - Will give a prompt on your device asking for authentication. This is the one you want.
To check your ADB version, nav to your ADB folder in cmd prompt and type "adb version" no quotes.
If it gives you 1.0.29, you need to update using your SDK manager.
To do this you need to nav to your /tools folder in your SDK folder. Here you will type "android" no quotes. Then follow the upgrade process.
Click to expand...
Click to collapse
Do you have link for this adb 1.0.31 version? I got same error device not found when using Android 4.0.3 sense 4 ROM?
Swyped From BlueICESense_JBE
For you, that doesn't matter. Which OS are you on?
Windows, make sure you have the proper drivers and the SDK tools are properly installed. If you ha e them installed, navigate to your /sdk-tools/tools folder in a cmd prompt and type android. That will five you the SDK update manager.
Ubuntu/Linux, make sure your udev rules are set up correctly.
Sent from my Alienized Evita using XDA Premium IV
Myrder said:
For you, that doesn't matter. Which OS are you on?
Windows, make sure you have the proper drivers and the SDK tools are properly installed. If you ha e them installed, navigate to your /sdk-tools/tools folder in a cmd prompt and type android. That will five you the SDK update manager.
Ubuntu/Linux, make sure your udev rules are set up correctly.
Sent from my Alienized Evita using XDA Premium IV
Click to expand...
Click to collapse
I'm on Windows 7 and I tried both Android 4.2.2 and Android 4.0.3 same result......I might think HTC driver not installed properly as well ......check my other thread S-OFF_Htc One XL driver I don't want clutter with this on his thread.......
Swyped From BlueICESense_JBE
dayz3r0 said:
Uh oh - tried the above with no luck. Just flashed Viper XL 4.2 in TWRP - but now it's just in a loop between the htc dev warning screen, the htc one screen, then off.
Volume down doesn't work. ADB doesn't see it (just installed the new one).
Help please.
Click to expand...
Click to collapse
Is the volume down button broken? Usually if it doesn't work it's a timing error.
Sent from my Evita
timmaaa said:
Is the volume down button broken? Usually if it doesn't work it's a timing error.
Sent from my Evita
Click to expand...
Click to collapse
Volume down got it into bootloader - seems like it was a timing issue. Had tried a bunch, so kind of surprising. Going to flash back to the old ROM and do s-off and a bunch of other upgrades then try again. Thanks for your help.
No problems.
PS. If someone helps you on XDA, press the thanks button.
Sent from my Evita
Related
Phone: HTC ONE XL
Carrier: Rogers LTE
Hey guys,
I have a problem that hopefully someone can help me with. Any help is much appreciated. I got my phone a year ago and I rooted it and unlocked it immediately. I removed the stock ROM and put Clean Rom 4.5 on it. Today, I realized my phone could be manually updated to jelly bean, so i wanted to install CM 10.1.
During installation, I just put the boot.img of the Rom in my folder that contained adb, fastboot, etc and I was at the step of loading recovery to install the rom, my phone could not get into the recovery and just kept restarting over and over again. I can still get into the bootloader. I read online to try and type "fastboot erase cache", but that isnt working because my computer can no longer recognize the phone. When I go into bootloader and into fastboot, my computer makes the sound like the USB is recognized but when I type the command "adb devices", no device is showing up.
I'm guessing that my first step to hopefully solving this issue is to find a way to have my device show up when I type "adb devices" but my attempts so far have been futile.
Key Points:
- Can't get past HTC boot screen (keeps looping)
- can still access bootloader
- no device seen when command "adb devices" has been typed.
Any help is greatly appreciated.
EDIT: I should add that when this occured (the looping), I tried to flash "recovery clockwork touch 5.8.2.7" and I was accidentally following a guide meant for the European HTC One X. The recovery image that I should have used (and did use to flash Clean Rom) is "TWRP 2.2.0 evita".
Cheruksr said:
Phone: HTC ONE XL
Carrier: Rogers LTE
Hey guys,
I have a problem that hopefully someone can help me with. Any help is much appreciated. I got my phone a year ago and I rooted it and unlocked it immediately. I removed the stock ROM and put Clean Rom 4.5 on it. Today, I realized my phone could be manually updated to jelly bean, so i wanted to install CM 10.1.
During installation, I just put the boot.img of the Rom in my folder that contained adb, fastboot, etc and I was at the step of loading recovery to install the rom, my phone could not get into the recovery and just kept restarting over and over again. I can still get into the bootloader. I read online to try and type "fastboot erase cache", but that isnt working because my computer can no longer recognize the phone. When I go into bootloader and into fastboot, my computer makes the sound like the USB is recognized but when I type the command "adb devices", no device is showing up.
I'm guessing that my first step to hopefully solving this issue is to find a way to have my device show up when I type "adb devices" but my attempts so far have been futile.
Key Points:
- Can't get past HTC boot screen (keeps looping)
- can still access bootloader
- no device seen when command "adb devices" has been typed.
Any help is greatly appreciated.
EDIT: I should add that when this occured (the looping), I tried to flash "recovery clockwork touch 5.8.2.7" and I was accidentally following a guide meant for the European HTC One X. The recovery image that I should have used (and did use to flash Clean Rom) is "TWRP 2.2.0 evita".
Click to expand...
Click to collapse
ADB is a program that gives you control of your phone "terminal" or "command line" remotely. It requires you to be booted into your ROM with USB debugging turned on so ofcourse it won't show any devices while in bootloader.
There are at least 20 threads that ask this same question. How do I know? I've answered at least that amount just myself. Please use the search function in the future prior to asking. I'm so tired of wasting time answering the same questions over and over.
Download TWRP 2.3.3.1 <- latest version that works properly without any issues with any ROMs
Check MD5 <- If you don't have an md5 checker google and download one. This will verify the download is good.
Put your phone in bootloader/fastboot
fastboot flash recovery recoveryfilename.img
fastboot erase cache
fastboot reboot-bootloader
Select recovery from bootloader menu
Flash your rom from recovery.
exad said:
ADB is a program that gives you control of your phone "terminal" or "command line" remotely. It requires you to be booted into your ROM with USB debugging turned on so ofcourse it won't show any devices while in bootloader.
There are at least 20 threads that ask this same question. How do I know? I've answered at least that amount just myself. Please use the search function in the future prior to asking. I'm so tired of wasting time answering the same questions over and over.
Download TWRP 2.3.3.1 <- latest version that works properly without any issues with any ROMs
Check MD5 <- If you don't have an md5 checker google and download one. This will verify the download is good.
Put your phone in bootloader/fastboot
fastboot flash recovery recoveryfilename.img
fastboot erase cache
fastboot reboot-bootloader
Select recovery from bootloader menu
Flash your rom from recovery.
Click to expand...
Click to collapse
Hey, thanks for the reply. Yeah, I read up on ADB after i posted the thread. I learnt that you can't use ADB commands in the bootloader. I've been trying to flash the recovery but i keep getting "waiting for device". (regardless of what command i try). I don't think its the USB drivers because I downloaded the latest HTC drivers (in fact there is a thread about the latest USB drivers for HTC, which is where I downloaded from) and there isn't any exclamation points in device manager. Not really sure what the issue is, any additional help would be appreciated.
Thanks.
EDIT:
Originally Posted by DvineLord
try using this application if you think your device drivers are dirty but installed correctly for usb devices
USBDeview just uninstall whatever devices you want reinitialized especially since they can change even with rom changes so it is good to clear some old ones out by sorting them based on Last Plug/Unplug Date.
Found that in another thread, going to try that. Hopefully that will work.
Cheruksr said:
Hey, thanks for the reply. Yeah, I read up on ADB after i posted the thread. I learnt that you can't use ADB commands in the bootloader. I've been trying to flash the recovery but i keep getting "waiting for device". (regardless of what command i try). I don't think its the USB drivers because I downloaded the latest HTC drivers (in fact there is a thread about the latest USB drivers for HTC, which is where I downloaded from) and there isn't any exclamation points in device manager. Not really sure what the issue is, any additional help would be appreciated.
Thanks.
EDIT:
Originally Posted by DvineLord
try using this application if you think your device drivers are dirty but installed correctly for usb devices
USBDeview just uninstall whatever devices you want reinitialized especially since they can change even with rom changes so it is good to clear some old ones out by sorting them based on Last Plug/Unplug Date.
Found that in another thread, going to try that. Hopefully that will work.
Click to expand...
Click to collapse
I just install the latest HTC sync. It installs the latest driver.
Also, try to avoid using a USB hub if you are.
Make sure HTC Sync isn't running when you are using fastboot/adb
Worst case scenario, you could always create a VM or something to get it going.
exad said:
I just install the latest HTC sync. It installs the latest driver.
Also, try to avoid using a USB hub if you are.
Make sure HTC Sync isn't running when you are using fastboot/adb
Worst case scenario, you could always create a VM or something to get it going.
Click to expand...
Click to collapse
I can now run the fastboot commands, but in the twrp recovery I can't access my SD card. I'm currently following a guide to see if I can fix it, but yeah thats where I am at. Also, a window popped up in my windows 8 saying "You need to format the disk...". Should I do that or what, Im not exactly sure.
Thanks
Yes format it.
Sent from my HTC One X using xda app-developers app
Am I capable of running CM10.1 Nightlies?
exad said:
Yes format it.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Alright, following a video tutorial (http://forums.team-nocturnal.com/showthread.php/1050) and factory reset the phone. My SD card is wiped clean but I can mount it through the TWRP recovery. Since I don't have a ROM now, I'm debating what I should do: a) Go back to Clean ROM 4.5, b) Install CM 10.1 Nightlies or c) Install Clean ROM 6.5.
***TAMPERED***
***UNLOCKED***
S-ON
HBOOT 1.11.0000
Is there anything I should know before attempting to flash CM 10.1/Clean ROM 6.5 or should I return to Clean ROM 4.5.
Thanks for the helps. Really appreciate it.
Either should work fine. Cleanrom will have somewhat bettery battery life.
Sent from my HTC One X using xda app-developers app
exad said:
Either should work fine. Cleanrom will have somewhat bettery battery life.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
another good tip is that when you are in fastboot mode and write "adb devices" not will work because adb will just work when your phone is turned on inside the android, and fastboot not will work if you arent in mode fastboot
So I got this help in the CM Q&A but while I've rooted man devices (mostly with oDin and one-click utilities) I've never used ADB and now I'm wanting to go from a sense to AOSP ROM and can't find active links to ADB or tutorials other than (type something here), youtube hasn't been help either, can someone help e out? I had a hboot 1.85 XL so I had it easy when I rooted.
LINKS
3.18 RUU Downloaded
S-Off Thread: http://forum.xda-developers.com/show....php?t=2155071 open in tab but the instructions aren't user friendly
Downgrade Touchscreen: http://forum.xda-developers.com/show....php?t=2159863
TWRP Recovery: http://goo.im/devs/OpenRecovery/evita downloaded
***openrecovery-twrp-2.3.3.1-evita.img or 2.3.3.0 are recommended at the time of this post***
OPTIONAL- Remove red text from splash screen: http://forum.xda-developers.com/show....php?t=2156368
INSTRUCTIONS
Thanks to @InflatedTitan for this breakdown.
While waiting for the RUU to download...
1. Download the 2 files for s-off and place in adb folder.
2. Download the recovery of choice and put in adb folder.
3 (optional) download the remove red text file and put in adb folder.
4. You'll have to downgrade touchscreen if you want to use aosp *SEE NOTE BELOW*. Head to original dev sticky to download files from h8rift. Put those in adb folder
_________________________________________
1. S-off! Make sure you confirm in bootloader (it usually works easier from a sense rom btw.) 4.2.2 roms need updated adb but it may work.
2. When you ruu, it doesn't touch sdcard. But I would quickly mount and backup your pics and whatnot just in case.
3. Enter fast boot. Run the ruu on the computer. It'll bring you back to 100% stock.
4. Once you up and running, enter fast boot again and send twrp. (Instructions below, insert whatever recovery image you're pushing)
Quote:
fastboot flash recovery openrecovery-twrp-2.3.3.1-recovery-evita.img
5. I recommend to get rid of the ugly ass red text on splash. Follow Liam's thread to rid it.
6. While in fastboot go ahead and downgrade touchscreen following h8rifts instructions.
7. Now you're golden to flash anything you want :thumbup:
*Note as of the 06/26 Nightly, you do NOT need to downgrade your touchscreen. However if you encounter any touch-related problems using TWRP 2.3.3.x, you should flash the downgrade in fastboot to move on. I'd recommend 2.5.0.0 on the latest touchpanel firmware. It works for me but if you run into trouble, downgrade the touchscreen and flash the recommended TWRP recovery.
ADB is a command line shell for accessing your phone remotely using linux commands. So many linux command line commands will work within adb. To become an ADB master, use linux command line.
As for downloading ADB and fastboot...
https://dl.dropboxusercontent.com/u/19685555/fb-adb.zip
I guess I'll stick to sense based ROM's because that wasn't helpful but thanks.
Edit after hours searching came across helpful info, but after changing the directory and putting int adb reboot bootloader i get "error device not found" when my phone is connected, any clue?
USFguy said:
I guess I'll stick to sense based ROM's because that wasn't helpful but thanks.
Click to expand...
Click to collapse
eh? What is it you want to know?
Here's a link to adb breakdown and commands? I googled "adb commands" and it was the first link...............
http://forum.xda-developers.com/showthread.php?t=2141817
Is this what you were looking for?
exad said:
eh? What is it you want to know?
Here's a link to adb breakdown and commands? I googled "adb commands" and it was the first link...............
http://forum.xda-developers.com/showthread.php?t=2141817
Is this what you were looking for?
Click to expand...
Click to collapse
"error: device not found"
USFguy said:
"error: device not found"
Click to expand...
Click to collapse
this is what i got....
USFguy said:
this is what i got....
Click to expand...
Click to collapse
is your phone plugged in with the rom booted and USB debugging turned on?
exad said:
is your phone plugged in with the rom booted and USB debugging turned on?
Click to expand...
Click to collapse
yeah, i uninstaleld HTC sync then went into device manager and updated the driver and it worked, I'm s-off and now waiting for RUU to finish
USFguy said:
yeah, i uninstaleld HTC sync then went into device manager and updated the driver and it worked, I'm s-off and now waiting for RUU to finish
Click to expand...
Click to collapse
current issue is in regards to "Quote:
fastboot flash recovery openrecovery-twrp-2.3.3.1-recovery-evita.img
"
I have openrecovery-twrp-2.3.3.1-recovery-evita.img in my c:\fb-adb folder and running the command from there but it's saying "error: cannot load 'openrecovery-twrp-2.3.3.1-recovery-evita.img'
USFguy said:
current issue is in regards to "Quote:
fastboot flash recovery openrecovery-twrp-2.3.3.1-recovery-evita.img
"
I have openrecovery-twrp-2.3.3.1-recovery-evita.img in my c:\fb-adb folder and running the command from there but it's saying "error: cannot load 'openrecovery-twrp-2.3.3.1-recovery-evita.img'
Click to expand...
Click to collapse
That means you're typing the filename wrong. Type the first few letters and then press tab. It will auto complete the file name for you.
exad said:
That means you're typing the filename wrong. Type the first few letters and then press tab. It will auto complete the file name for you.
Click to expand...
Click to collapse
i'm actually getting the no devices connected again since the ruu finished running.
Press and hold power until the phone shuts off then press and hold volume down until the bootloader comes on then try again
Sent from my HTC One X using xda app-developers app
USFguy said:
current issue is in regards to "Quote:
fastboot flash recovery openrecovery-twrp-2.3.3.1-recovery-evita.img
"
I have openrecovery-twrp-2.3.3.1-recovery-evita.img in my c:\fb-adb folder and running the command from there but it's saying "error: cannot load 'openrecovery-twrp-2.3.3.1-recovery-evita.img'
Click to expand...
Click to collapse
Twrp 2.6 works great. No real reason for 2.3.3.1 anymore but nostalgia.
Sent from my HTC One XL using xda premium
I am really confused since having to use ADB and flashboot. I am thoroughly confused that someone has not simply written step by step instructions for this in a sticky so newbies like myself can follow. With that in mind I am trying to change from CWM to TWRP. I have the files but completely oblivious on how to get things to work again. I go into a command propt and start adb or flashboot but cant seem to get it to find the device. Now I cannot find the instructions I used to install CWM. Can somoene kindly help with either a link or instructions to make this change so I can be good and flash some ROM's?
Thanks,
crazysane said:
I am really confused since having to use ADB and flashboot. I am thoroughly confused that someone has not simply written step by step instructions for this in a sticky so newbies like myself can follow. With that in mind I am trying to change from CWM to TWRP. I have the files but completely oblivious on how to get things to work again. I go into a command propt and start adb or flashboot but cant seem to get it to find the device. Now I cannot find the instructions I used to install CWM. Can somoene kindly help with either a link or instructions to make this change so I can be good and flash some ROM's?
Thanks,
Click to expand...
Click to collapse
1) Power your phone off and once its off hold down power + volume down until its booted into HBOOT/Fastboot mode (bootloader).
2) Place your TWRP img file in the platform-tools folder where your adb/fastboot files are.
3) Shift + Right click inside of the platform-tools folder and open as a command prompt.
4) If you're not already, switch to fastboot mode and assure it says "Fastboot USB" or just fastboot at the top (don't remember if it says USB or not) and then in the command window type the following command and press enter: 'fastboot flash recovery name.img'. Replace "name" with the file name of your TWRP img.
5) It should say "successful" and then from there you can navigate to your new TWRP recovery via the bootloader by navigating with the volume keys and selecting the "Recovery" option by pressing the power button once its selected.
Download links for latest TWRP: http://teamw.in/project/twrp2/226
Direct download link for latest TWRP can be found here
S1L3nTShaDoWz said:
1) Power your phone off and once its off hold down power + volume down until its booted into HBOOT/Fastboot mode (bootloader).
2) Place your TWRP img file in the platform-tools folder where your adb/fastboot files are.
3) Shift + Right click inside of the platform-tools folder and open as a command prompt.
4) If you're not already, switch to fastboot mode and assure it says "Fastboot USB" or just fastboot at the top (don't remember if it says USB or not) and then in the command window type the following command and press enter: 'fastboot flash recovery name.img'. Replace "name" with the file name of your TWRP img.
5) It should say "successful" and then from there you can navigate to your new TWRP recovery via the bootloader by navigating with the volume keys and selecting the "Recovery" option by pressing the power button once its selected.
Download links for latest TWRP: http://teamw.in/project/twrp2/226
Direct download link for latest TWRP can be found here
Click to expand...
Click to collapse
Really appreciate what you said but I am running into the issue in the command prompt. When I type the commands it says
error: device not found
I have rebooted both phone and computer but it never seems to find the device now and not sure what to do.
Do you have any suggestions on do I start adb and run any commands, SU, fastboot, or what? I know its working because the computer sees the devices by an external drive. The phone is able to go into fastboot on reboot as well. I just do not know where my dilemma is.
Do you have USB debugging enabled under developer options?
adavit said:
Do you have USB debugging enabled under developer options?
Click to expand...
Click to collapse
yes I do and as I said it sees the device as other storage.
crazysane said:
Really appreciate what you said but I am running into the issue in the command prompt. When I type the commands it says
error: device not found
I have rebooted both phone and computer but it never seems to find the device now and not sure what to do.
Do you have any suggestions on do I start adb and run any commands, SU, fastboot, or what? I know its working because the computer sees the devices by an external drive. The phone is able to go into fastboot on reboot as well. I just do not know where my dilemma is.
Click to expand...
Click to collapse
I'd assume this means you haven't installed the proper drivers? Well actually I'm not really sure these even relate to the fastboot drivers BUT worth a shot to fix your problem!
Download HTC Sync Manager from here and install it and let it install the proper drivers for your M8 (with phone powered on of course) and once they are installed and it's done make 100% sure you UNINSTALL HTC Sync Manager after, only the program, not the drivers themselves.
After that re-attempt it and also as the other guy said, enable USB debugging all though I don't think it will do anything unless the phones booted into Android(may be wrong).
Also see if you can get ADB to work while the phone is running. Instructions for testing ADB would be turn the phone on, enable USB debugging and in the command prompt type
Code:
adb devices
and if it pops up your device then you should be good. If it doesn't then it's most likely related to the drivers and I would recommend you uninstall all drivers and remove every trace of them. My prefered method of uninstalling them is using Device Manager (windows tool) to uninstall the drivers and then use USBDeview to remove the rest/traces/etc.
S1L3nTShaDoWz said:
I'd assume this means you haven't installed the proper drivers? Well actually I'm not really sure these even relate to the fastboot drivers BUT worth a shot to fix your problem!
Download HTC Sync Manager from here and install it and let it install the proper drivers for your M8 (with phone powered on of course) and once they are installed and it's done make 100% sure you UNINSTALL HTC Sync Manager after, only the program, not the drivers themselves.
After that re-attempt it and also as the other guy said, enable USB debugging all though I don't think it will do anything unless the phones booted into Android(may be wrong).
Also see if you can get ADB to work while the phone is running. Instructions for testing ADB would be turn the phone on, enable USB debugging and in the command prompt type
Code:
adb devices
and if it pops up your device then you should be good. If it doesn't then it's most likely related to the drivers and I would recommend you uninstall all drivers and remove every trace of them. My prefered method of uninstalling them is using Device Manager (windows tool) to uninstall the drivers and then use USBDeview to remove the rest/traces/etc.
Click to expand...
Click to collapse
OK finally found the phone and flashed putting TWRP on it for recovery. Thank you very much. Using the ADB and FASTBOOT are things I guess I truly need to learn. So, with that I thank you and now I feel good about beginning my ROM flashing.
crazysane said:
OK finally found the phone and flashed putting TWRP on it for recovery. Thank you very much. Using the ADB and FASTBOOT are things I guess I truly need to learn. So, with that I thank you and now I feel good about beginning my ROM flashing.
Click to expand...
Click to collapse
May I ask what you did to get it working? Was it the developer options? HTC Sync Manager drivers? something else?
& you're welcome!
crazysane said:
yes I do and as I said it sees the device as other storage.
Click to expand...
Click to collapse
Sorry, I was kinda skimming your reply and watching TV at the same time (big mistake lol). I'm glad that you were able to get everything work.
S1L3nTShaDoWz said:
May I ask what you did to get it working? Was it the developer options? HTC Sync Manager drivers? something else?
& you're welcome!
Click to expand...
Click to collapse
I basically went in and did the adb devices. Once it seemed to see it I had to do the adb reboot bootloader then do the flashboot flash recovery twrp img. Now I have it working and about to flash santod's NuSense ROM since I used it on my thunderbolt that was recently replaced by this. Wish me luck LOL.
I am new to htc
i am flashing a custom rom for first time on htc
what do i have to know?
and what is needed?
and i am stuck on soft brick and cant mount internal storage
i am using
hboot 2.15
it shows tampered
and twrp 2.8
Tampered is shown because you probably unlocked your bootloader on the HTC dev site (which is the first thing you should do anyway)
Now, taking in consideration what you said in the Candy thread, can you enter in fastboot mode? You can do this by entering in bootloader (with phone off, keep pressed the vol down and press power). On the bootloader screen navigate with vol up/down and select with power button. Enter fasboot from there and while you connect the phone to pc via USB you should notice on uour screen a line saying "fastboot USB"
After this you shoul be able to flash the kernel in that mode. You should have ADB installed for this on your pc (it is done by installing the Android SDK) and the ADB/fastboot drivers working.
Let us know how it goes so far then we can go further
Sent from nowhere over the air...
Rapier said:
Tampered is shown because you probably unlocked your bootloader on the HTC dev site (which is the first thing you should do anyway)
Now, taking in consideration what you said in the Candy thread, can you enter in fastboot mode? You can do this by entering in bootloader (with phone off, keep pressed the vol down and press power). On the bootloader screen navigate with vol up/down and select with power button. Enter fasboot from there and while you connect the phone to pc via USB you should notice on uour screen a line saying "fastboot USB"
After this you shoul be able to flash the kernel in that mode. You should have ADB installed for this on your pc (it is done by installing the Android SDK) and the ADB/fastboot drivers working.
Let us know how it goes so far then we can go further
Sent from nowhere over the air...
Click to expand...
Click to collapse
Do i need to s off
and ive noticed that even after flashing rom system folder is empty except for bin and by the way my device is t mobile
S-off is not mandatory but is good to have as the whole flashing process will be much easier. Is it somewhere in the bootloader screen written UNLOCKED? Above or below the "tampered"...
Sent from nowhere over the air...
Rapier said:
S-off is not mandatory but is good to have as the whole flashing process will be much easier. Is it somewhere in the bootloader screen written UNLOCKED? Above or below the "tampered"...
Sent from nowhere over the air...
Click to expand...
Click to collapse
unlocked yes i did it but i cant flash the rom it wont be pushed into system at all
please my mind is not clear can you give me a link for kernal pleaseee
Kernel that you must flash in fastboot is the file boot.img located in the system folder in the ROM"s zip....that is, you'll have to open the zip you're flashing, go to system and extract that boot.img file. Save it on your pc in the same location where fastboot and adb are installed then open a command prompt there. You can flash it using the "fastboot flash boot boot.img" command
Edit: Here's an XDA tutorial how to do it in detail
http://forum.xda-developers.com/showthread.php?t=1752270
Sent from nowhere over the air...
Rapier said:
Kernel that you must flash in fastboot is the file boot.img located in the system folder in the ROM"s zip....that is, you'll have to open the zip you're flashing, go to system and extract that boot.img file. Save it on your pc in the same location where fastboot and adb are installed then open a command prompt there. You can flash it using the "fastboot flash boot boot.img" command
Edit: Here's an XDA tutorial how to do it in detail
http://forum.xda-developers.com/showthread.php?t=1752270
Sent from nowhere over the air...
Click to expand...
Click to collapse
ive restored from ruu
Rapier said:
Kernel that you must flash in fastboot is the file boot.img located in the system folder in the ROM"s zip....that is, you'll have to open the zip you're flashing, go to system and extract that boot.img file. Save it on your pc in the same location where fastboot and adb are installed then open a command prompt there. You can flash it using the "fastboot flash boot boot.img" command
Edit: Here's an XDA tutorial how to do it in detail
http://forum.xda-developers.com/showthread.php?t=1752270
Sent from nowhere over the air...
Click to expand...
Click to collapse
Why my device wont s-off its always telling me to f***off
eswarvf said:
Why my device wont s-off its always telling me to f***off
Click to expand...
Click to collapse
What RUU Worked?
eswarvf said:
Why my device wont s-off its always telling me to f***off
Click to expand...
Click to collapse
În order to properly s-off, you might need a certain ROM to be installed. Have you tried to get s-off having that stock ROM you got after RUU?
Sent from nowhere over the air...
Can s-off be achieved without an installed ROM?
bobby2x420 said:
Can s-off be achieved without an installed ROM?
Click to expand...
Click to collapse
Only by a j-tag device but I don't know how that works. The software methods presented here needs a ROM as far as I know
Sent from nowhere over the air...
bobby2x420 said:
What RUU Worked?
Click to expand...
Click to collapse
Ya it worked (not androidruu though) i had to search a lot i got tired of it
Long story short, I had an issue with my HTC One X that I received from a friend. It would load up and then immediately restart about 15 seconds after getting to lock screen. I was just stuck in a boot loop.
So I decided to flash a new rom onto the phone, but neither I nor my friend had created a backup so now my OS is wiped.
I can boot into recovery mode, though. I'm not sure what the first screen is called, but it's the one with the skating androids. It tells me:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.45.0622
eMMC-boot
Jun 11 2012,14:36:28
Click to expand...
Click to collapse
When I enter into recovery, it appears that I have TWRP v2.3.1.0.
In here, I cannot install any roms. They appear to fail. Installing says:
Zip Install Complete
Updating partition details...
Running boot script...
Finished running boot script.
Installing '/sdcard/pac.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Error flashing zip '/sdcard/pac.zip'
Updating partition details...
Click to expand...
Click to collapse
Failed
Click to expand...
Click to collapse
I had read somewhere that I need to upgrade my TWRP in order to properly install roms, but at the current moment, running adb devices in a command prompt pointed at my adt bundle folder does not work. It just has a blank list.
Attached is a photo with what I think are the most relevant things I've downloaded/installed so far.
It does look like I can connect my phone to the computer via Mount USB Storage, but sideloader does not work since adb devices is blank.
Any thoughts?
kpxexpress said:
Long story short, I had an issue with my HTC One X that I received from a friend. It would load up and then immediately restart about 15 seconds after getting to lock screen. I was just stuck in a boot loop.
So I decided to flash a new rom onto the phone, but neither I nor my friend had created a backup so now my OS is wiped.
I can boot into recovery mode, though. I'm not sure what the first screen is called, but it's the one with the skating androids. It tells me:
When I enter into recovery, it appears that I have TWRP v2.3.1.0.
In here, I cannot install any roms. They appear to fail. Installing says:
I had read somewhere that I need to upgrade my TWRP in order to properly install roms, but at the current moment, running adb devices in a command prompt pointed at my adt bundle folder does not work. It just has a blank list.
Attached is a photo with what I think are the most relevant things I've downloaded/installed so far.
It does look like I can connect my phone to the computer via Mount USB Storage, but sideloader does not work since adb devices is blank.
Any thoughts?
Click to expand...
Click to collapse
The first screen with the skating Androids is your bootloader, FYI. Adb commands aren't used for flashing a recovery, fastboot commands are used. You do indeed need to update TWRP, the version you currently have installed isn't compatible with any current ROMs. Click the guide link in my signature, there are instructions on anything you need to do there.
Transmitted via Bacon
timmaaa said:
The first screen with the skating Androids is your bootloader, FYI. Adb commands aren't used for flashing a recovery, fastboot commands are used. You do indeed need to update TWRP, the version you currently have installed isn't compatible with any current ROMs. Click the guide link in my signature, there are instructions on anything you need to do there.
Transmitted via Bacon
Click to expand...
Click to collapse
I think I have my phone on Fastboot right now. I have the white screen that has FASTBOOT USB written on it with
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWERDOWN
Click to expand...
Click to collapse
underneath the control options. I've attached a picture below.
I Shift + Right Clicked to open command prompt in the folder with fastboot.exe and my recoveryfilename.img file.
In the command prompt, I enter in the command
Code:
fastboot flash recovery "recoveryfilename.img"
and it just stays on
Code:
< waiting for device >
I still can't figure out how to update my TWRP without an OS.
kpxexpress said:
I think I have my phone on Fastboot right now. I have the white screen that has FASTBOOT USB written on it with
underneath the control options. I've attached a picture below.
I Shift + Right Clicked to open command prompt in the folder with fastboot.exe and my recoveryfilename.img file.
In the command prompt, I enter in the command
Code:
fastboot flash recovery "recoveryfilename.img"
and it just stays on
Code:
< waiting for device >
I still can't figure out how to update my TWRP without an OS.
Click to expand...
Click to collapse
What OS are you running on your PC? Did adb/fastboot work at any point?
timmaaa said:
What OS are you running on your PC? Did adb/fastboot work at any point?
Click to expand...
Click to collapse
I'm running Windows 8.1 Pro. ADB worked once. I was able to get it to detect in recovery. ADB Devices would give me the customary string of numbers followed by "RECOVERY" and then I rebooted the phone for some reason and it stopped working. Oh, during that time I was also able to move stuff to the phone via ADB Sideload, but I would get pretty much the same errors when installing, which I later found out was because my TWRP was too old. I can't seem to get it to connect via ADB/Fastboot anymore. I can, however mount via TWRP.
kpxexpress said:
I'm running Windows 8.1 Pro. ADB worked once. I was able to get it to detect in recovery. ADB Devices would give me the customary string of numbers followed by "RECOVERY" and then I rebooted the phone for some reason and it stopped working. Oh, during that time I was also able to move stuff to the phone via ADB Sideload, but I would get pretty much the same errors when installing, which I later found out was because my TWRP was too old. I can't seem to get it to connect via ADB/Fastboot anymore. I can, however mount via TWRP.
Click to expand...
Click to collapse
There's your problem. Windows 8.1 isn't compatible with fastboot. You'll need to get access to a PC with a lower version of Windows so you can update TWRP.
timmaaa said:
There's your problem. Windows 8.1 isn't compatible with fastboot. You'll need to get access to a PC with a lower version of Windows so you can update TWRP.
Click to expand...
Click to collapse
Oh, really? Will 8 or 7 work?
I used a Windows 7 laptop and was able to update my TWRP to v2.7.0.8!
Seem to still be unable to detect devices via adb devices command.
Ok. Had to update my drivers.
I'm following your instructions on How To Install A ROM with TWRP Recovery, and now my issue is that it is saying
Code:
error flashing zip '/sdcard/pac.zip'
I've included a picture below.
kpxexpress said:
Oh, really? Will 8 or 7 work?
I used a Windows 7 laptop and was able to update my TWRP to v2.7.0.8!
Seem to still be unable to detect devices via adb devices command.
Ok. Had to update my drivers.
I'm following your instructions on How To Install A ROM with TWRP Recovery, and now my issue is that it is saying
Code:
error flashing zip '/sdcard/pac.zip'
I've included a picture below.
Click to expand...
Click to collapse
You're gonna need to get s-off so you can update your firmware. In order to get s-off you'll need to flash the Kickdroid ROM. Once you've flashed Kickdroid you can go to the Rumrunner s-off site and get s-off. Then follow the instructions in my guide thread to update your firmware.
timmaaa said:
You're gonna need to get s-off so you can update your firmware. In order to get s-off you'll need to flash the Kickdroid ROM. Once you've flashed Kickdroid you can go to the Rumrunner s-off site and get s-off. Then follow the instructions in my guide thread to update your firmware.
Click to expand...
Click to collapse
Alright, so I managed to get the Kickdroid ROM working! So right now I at least have a working phone that I can use! Thanks a TON for getting me this far.
Rumrunnner seems to not be working right for me. I'm in ADB recovery and can confirm an ADB connection, but it's still displaying
Code:
ERROR: run rumrunner again and READ (no adb connection to device. Debugging on? Drivers?)
But it's a start. I'll have to make sure I'm following all instructions carefully.