I'm stupid, I get it.
I just got an Asurion replacement DNA the other day and I wanted to S-Off, Root, Recovery Image, and new KitKat ROM.
So, I was able to use Rumrunner, and that worked out fine.
I rooted my DNA and then loaded TWRP 2.6.3, and that worked fine as well.
My intent was to load GPE and I d/l'd it to my phone (not knowing it was a corrupt download).
So I got into recovery, wiped, wiped, reset, and loaded the ROM - and it puked all over itself.
Now, I have a phone that is in recovery, has no image, and I can't figure out how to put one on it.
I'm running Mint Linux, but I have access to a W7 laptop if I need it.
It's my daily driver, I'm frustrated, upset, and stupid. And I could certainly use some help.
Thanks
In a terminal window (thanks .torrent), I typed: adb devices (then sudo adb devices) and got nothing in return.
I've tried sideloading; the ROM loads according to the terminal window, but I don't see anything happening on the phone (no failures though).
I've tried pushing a ROM to the phone but the terminal window says that it doesn't see the device. That doesn't make sense because I can sideload (apparently).
ugh.
Yehudah said:
In a terminal window (thanks .torrent), I typed: adb devices (then sudo adb devices) and got nothing in return.
I've tried sideloading; the ROM loads according to the terminal window, but I don't see anything happening on the phone (no failures though).
I've tried pushing a ROM to the phone but the terminal window says that it doesn't see the device. That doesn't make sense because I can sideload (apparently).
ugh.
Click to expand...
Click to collapse
This question has been answered at least a dozen times, "Help I wiped my internal storage", blah blah blah.
Download the rom you want on your computer. Put it in the same directory as your ADB stuff (mine is C:\android, I don't know what yours is).
Plug phone into computer, make sure you have ADB enabled on your phone, open a command prompt, verify you have ADB working by typing "adb devices"
You should see your device listed.
Boot phone into recovery >advanced >ADB sideload
Follow instructions at top of sideload screen to sideload rom from computer to phone.
In the future a little searching would get you to all this information, rather than starting a new thread... :good:
Enjoy
P.S. ALWAYS verify your MD5 before flashing, and ALWAYS have a backup made to fall back on.
I know it's been done to death. I searched and read every thread that was like mine and did everything in each thread.
It was the last thing I did that worked. RUU from .torrents links. That worked. I'm still rooted, Next time I'll make sure I have I backup I can restore - won't make this mistake again.
Thanks for the low level chastising, I deserved it. And thanks for the info, ad nauseum.
After a two day ordeal, I finally got my DNA back to where it was before I borked it up last week.
Because of what I did; I needed to use Rumrunner to unlock, RUU to get back to where the phone worked, ADB and Fastboot to get the recovery image set up and put a ROM on the phone.
When it was all said and done, .torrent walked me through getting the phone fixed. Without him, I'd still be banging my head against my desk.
Thanks to the developers who created Rumrunner, and who developed the Android tool kits that helped me overcome my stupidity. Because of their ability to create great applications, I've learned more about Linux and how my phone works than I ever did before....just wish it hadn't taken this to cause that.
Thanks to all, you guys ROCK! :good:
Yehudah said:
After a two day ordeal, I finally got my DNA back to where it was before I borked it up last week.
Because of what I did; I needed to use Rumrunner to unlock, RUU to get back to where the phone worked, ADB and Fastboot to get the recovery image set up and put a ROM on the phone.
When it was all said and done, .torrent walked me through getting the phone fixed. Without him, I'd still be banging my head against my desk.
Thanks to the developers who created Rumrunner, and who developed the Android tool kits that helped me overcome my stupidity. Because of their ability to create great applications, I've learned more about Linux and how my phone works than I ever did before....just wish it hadn't taken this to cause that.
Thanks to all, you guys ROCK! :good:
Click to expand...
Click to collapse
At least you learned from your mistakes.
Sent from my HTC6600LVW using XDA Premium 4 mobile app
thayl0 said:
At least you learned from your mistakes.
Sent from my HTC6600LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Are you using an HTC 6600 as your daily driver? LOL I had one of those, loved it.
Yehudah said:
Are you using an HTC 6600 as your daily driver? LOL I had one of those, loved it.
Click to expand...
Click to collapse
I'm not use haven't looked I'm using whatever it installed. lol
Related
so i decided to root my phone today, and flash a custom rom. i am using the t-mobile variant.
i used the all in one toolkit to unlock bootloader, and everything was going good, but i think i might have forgot to install superuser? i am not sure what went wrong. but i was trying to flash android revolution hd, and it was stuck in the bootloop. so i thought i needed to flash the boot.img like i had to in past devices. did that, but still nothing.
i go into CWM and now i can't access the sd card. so i did a wipe and it still won't mount on my computer. did a little reading around, and someone suggested relocking the bootloader, and flashing stock recovery file (i don't think i got the right one), and then unlocked the bootloader and reflash CWM, and that sideloading a rom would work. everytime i try to sideload a rom, i get a device not found error, but fastboot responds to other adb commands. i did make a backup in CWM, but i moved it from the phone to my laptop, but i have no idea how to even use it. adb push to device does nothing. =/
i really really really hope i didn't brick my phone. anyone have some insight? help? i tried looking for a RUU but it seems there isn't one for t-mobile.
so i am able to flash recovery, and get into it, when i try to mount sdcard in the options, it doesn't say anything. stuck in bootloop still. can't sideload. can't push. really really wish it had an external sd card which would make issues like this a bit easier to solve.
Nah, mods don't delete threads like this. Thread moved to T-Mobile HTC One Q&A (and don't post questions anywhere other than the Q&A section in the forum of your device's variant )
fastboot won't respond to adb commands because it's fastboot not adb. i would use the toolkit and install TWRP recovery and load up TWRP. from there you can adb sideload or do other adb commands once you get it loaded.
orvon.freeman said:
I advise this due to the fact you can use adb commands.
relock bootloader then run an RUU here is the one from AT&T http://forum.xda-developers.com/showthread.php?t=2287036&highlight=ruu.
Click to expand...
Click to collapse
Do not attempt to flash an AT&T RUU to your T-Mobile device. In the best case scenario, it should fail(due to S-ON). I would not recommend fooling around with RUUs on different carrier-branded devices.
As for the OP, I'm not sure what to recommend. Most internal storage-only devices won't mount in USB. Wiping your internal storage was the worst thing that you could have done. I'm not sure why adb sideload won't work if normal adb commands and fastboot commands are being accepted. Have you tried a different USB port? I know it sounds strange, but sometimes that can make a difference.
unremarked said:
Do not attempt to flash an AT&T RUU to your T-Mobile device. In the best case scenario, it should fail(due to S-ON). I would not recommend fooling around with RUUs on different carrier-branded devices.
As for the OP, I'm not sure what to recommend. Most internal storage-only devices won't mount in USB. Wiping your internal storage was the worst thing that you could have done. I'm not sure why adb sideload won't work if normal adb commands and fastboot commands are being accepted. Have you tried a different USB port? I know it sounds strange, but sometimes that can make a difference.
Click to expand...
Click to collapse
just thought about that. Each carrier is diff my bad. good catch unremarked.
I looked for a nandroid that you could use with the toolbox to flash it is t-mobile http://forum.xda-developers.com/showthread.php?t=2182823
orvon.freeman said:
this is the wrong section for this. This belongs in QA not dev. Next time read the rules http://forum.xda-developers.com/showthread.php?t=2158147
Good luck
Click to expand...
Click to collapse
pandaball said:
Nah, mods don't delete threads like this. Thread moved to T-Mobile HTC One Q&A (and don't post questions anywhere other than the Q&A section in the forum of your device's variant )
Click to expand...
Click to collapse
appreciate it, xda forums sure has grown since when i was on here with my g2/my4g slide, lots of subforums, and in a haze of having soft bricked my phone, i posted in the wrong section. sorry!
TygerByte said:
fastboot won't respond to adb commands because it's fastboot not adb. i would use the toolkit and install TWRP recovery and load up TWRP. from there you can adb sideload or do other adb commands once you get it loaded.
Click to expand...
Click to collapse
unremarked said:
Do not attempt to flash an AT&T RUU to your T-Mobile device. In the best case scenario, it should fail(due to S-ON). I would not recommend fooling around with RUUs on different carrier-branded devices.
As for the OP, I'm not sure what to recommend. Most internal storage-only devices won't mount in USB. Wiping your internal storage was the worst thing that you could have done. I'm not sure why adb sideload won't work if normal adb commands and fastboot commands are being accepted. Have you tried a different USB port? I know it sounds strange, but sometimes that can make a difference.
Click to expand...
Click to collapse
i did what tygerbyte suggested several times with no success. then i decided to reinstall htc drivers, restart the laptop, and use a different usb port like unremarked suggested, i am able to sideload now! flashing my backup i made in CWM right now, hopefully this will give me a working phone again before i try to flash a custom rom again lol.
i have my fingers crossed.
thanks for the suggestions everyone. ill post back in a bit with results.
just wanted to update, i was able to flash android revolution after several tries / freezing, but phone is back on and functional now.
thanks for walking me through this, i would have gone insane if i bricked my one.
mky4b11 said:
just wanted to update, i was able to flash android revolution after several tries / freezing, but phone is back on and functional now.
thanks for walking me through this, i would have gone insane if i bricked my one.
Click to expand...
Click to collapse
Isn't it the worst feeling, thinking you have bricked your $600 phone? I soft-bricked my husbands Bionic once, stayed up all night long and finally figured out I had skipped a step.
The BEST feeling, though, is realizing that you can, and did, recover from what appeared to be a catastrophic fail. Congratulations!
Phone: ATT HTC One X +
Hi everyone,
This problem has been beat to death on this site but it's very hard to follow with other phones and trying to find the files and everything needed to fix it. This is my first time to try and root a phone so I tried to piece it together and screwed it up. Still trying to learn.
So far I successfully unlocked the bootloader through the HTCDEV site so I have SDK with fastboot and adb. I found OneXRoot but it just said "waiting for device". So, I found RootBoot-1.14.206.16-O2, ran it from the file I downloaded it to and not the fastboot/adb location (might have been the problem) and it said "waiting for device" so I unplugged my phone and plugged it back in. It was supposed to restart my phone 3 times and root my phone through magic but instead it restarted once and only goes to HTC white screen.
I've looked all through for a solution and the best thing I've come across was this link http://forum.xda-developers.com/showthread.php?p=30863908 . I was going to try this but I don't know my CID and my phone doesn't boot to figure it out. Am I headed in the right direction?
My goal here was to root the phone to get rid of HTC Sense. I'm thinking I should flash the boot.img or do the kernal thing. Not sure though it's very confusing. Right now I need to get it to boot so I can try the root again (the correct way, whatever that might be). Any help would be very appreciated, my phone is a paper weight right now.
http://teamw.in/project/twrp2/131 downloaded the recovery image here and going to try that. It says the batter is too low now so i'm guessing it will work after the battery is recharged. That's direction I am taking atm.
Update: I've finally figured out how to get the TWRP recovery booted. Now working on trying to get my phone to boot up an OS of some sort. Very slowly but surely.
bullmurf said:
Phone: ATT HTC One X +
Hi everyone,
This problem has been beat to death on this site but it's very hard to follow with other phones and trying to find the files and everything needed to fix it. This is my first time to try and root a phone so I tried to piece it together and screwed it up. Still trying to learn.
So far I successfully unlocked the bootloader through the HTCDEV site so I have SDK with fastboot and adb. I found OneXRoot but it just said "waiting for device". So, I found RootBoot-1.14.206.16-O2, ran it from the file I downloaded it to and not the fastboot/adb location (might have been the problem) and it said "waiting for device" so I unplugged my phone and plugged it back in. It was supposed to restart my phone 3 times and root my phone through magic but instead it restarted once and only goes to HTC white screen.
I've looked all through for a solution and the best thing I've come across was this link http://forum.xda-developers.com/showthread.php?p=30863908 . I was going to try this but I don't know my CID and my phone doesn't boot to figure it out. Am I headed in the right direction?
My goal here was to root the phone to get rid of HTC Sense. I'm thinking I should flash the boot.img or do the kernal thing. Not sure though it's very confusing. Right now I need to get it to boot so I can try the root again (the correct way, whatever that might be). Any help would be very appreciated, my phone is a paper weight right now.
http://teamw.in/project/twrp2/131 downloaded the recovery image here and going to try that. It says the batter is too low now so i'm guessing it will work after the battery is recharged. That's direction I am taking atm.
Click to expand...
Click to collapse
Press the power down button while turning on your device to see if you can get to boot loader - this will give you the basic information about your device.
Use the original RUU from the following post to flash your device in bootloader mode (I think it should work...):
http://forum.xda-developers.com/showthread.php?t=2140442
Use this to unlock your bootloader / root your device / blah blah blah. Too many people have succeeded in rooting / unlocking their device through this. So, there is a good chance that you will too...
http://forum.xda-developers.com/showthread.php?t=1994961
Addicted2xda said:
Press the power down button while turning on your device to see if you can get to boot loader - this will give you the basic information about your device.
Use the original RUU from the following post to flash your device in bootloader mode (I think it should work...):
http://forum.xda-developers.com/showthread.php?t=2140442
Use this to unlock your bootloader / root your device / blah blah blah. Too many people have succeeded in rooting / unlocking their device through this. So, there is a good chance that you will too...
http://forum.xda-developers.com/showthread.php?t=1994961
Click to expand...
Click to collapse
OK it looks like the OS was wiped before it was backed up with a rom folder to use after rooting. Now I have no OS so I can't get to files to put on a ROM or do much of anything. It's not booting past the HTC screen because there is no OS now ^^. I have no idea what to do about that. Going to try to figure out how to put a new OS on there. Any help would be appreciated.
bullmurf said:
OK it looks like the OS was wiped before it was backed up with a rom folder to use after rooting. Now I have no OS so I can't get to files to put on a ROM or do much of anything. It's not booting past the HTC screen because there is no OS now ^^. I have no idea what to do about that. Going to try to figure out how to put a new OS on there. Any help would be appreciated.
Click to expand...
Click to collapse
If your device is locked - you can get the current RUU of your specific device from the post I have mentioned.
BTW what is your hboot version?
If your device is unlocked - install TWRP using hasoon's toolkit and then use sideload to copy / install a custom ROM...
Addicted2xda said:
If your device is locked - you can get the current RUU of your specific device from the post I have mentioned.
BTW what is your hboot version?
If your device is unlocked - install TWRP using hasoon's toolkit and then use sideload to copy / install a custom ROM...
Click to expand...
Click to collapse
"use sideload to copy / install a custom ROM..." OK I don't know anything about this but it will point me in the right direction. I have the phone unlocked. The HBOOT version is 1.40.0000. I'll see if I can do what you suggested, thanks.
Update: Atempting an adb sideload using TWRP which seems to be the only option for me.
ADB Sideload
What is ADB sideload?
--------------------------------------------------------------------------------
ADB sideload is a new feature that was added to AOSP recovery in Jelly Bean. As of version 2.3, TWRP now supports ADB sideload mode. ADB sideload is a different ADB mode that you can use to push and install a zip using one command from your computer. Most likely ADB sideload won't be very useful for your average recovery user, but ADB sideload can be a huge time-saver for a ROM developer.
How do I use ADB sideload?
--------------------------------------------------------------------------------
1.Have a recovery installed on your device that supports ADB sideload like TWRP 2.3 or higher
2.Have newer ADB binaries installed on your computer. If it's been a while since you installed ADB on your computer, you may need to get the latest ADB binaries in platform-tools from the Android SDK. You will need version 1.0.29 or higher. You can find your current version by typing "adb version" at the command line.
3.Set the device into ADB sideload mode. In TWRP you do this by going to Advanced then ADB Sideload.
4.From the command line, type adb sideload /path/to/rom.zip
The file will be copied to your device to whatever the current storage location is that you have selected in the mount page. It will always be placed in the root of that storage location and named sideload.zip (e.g. /sdcard/sideload.zip) and it will automatically delete / overwrite any existing sideload.zip you may have on your device. As soon as the file is copied to your device, it will automatically be installed. When the install is finished you will be presented with a reboot system button so that you can reboot to test your zip.
Note that sideload mode is a separate ADB mode. While in sideload mode, regular ADB commands will not work. Once the zip has been copied to the device and the install starts (or if you hit the cancel button) regular ADB mode will resume.
Click to expand...
Click to collapse
I can't link on this board yet so I quoted the sideloading instructions for a .zip from the TWRP website. I have the latest version of SDK and when I try to sideload it gives me a list of commands in the command prompt. I looked through them and didn't see sideload as a command. What's the easiest way to sideload this zip so I can install it in TWRP to get my phone booted? I know you can do "adb install \path.apk) but I don't have an rom in .apk format, only zip.
bullmurf said:
I can't link on this board yet so I quoted the sideloading instructions for a .zip from the TWRP website. I have the latest version of SDK and when I try to sideload it gives me a list of commands in the command prompt. I looked through them and didn't see sideload as a command. What's the easiest way to sideload this zip so I can install it in TWRP to get my phone booted? I know you can do "adb install \path.apk) but I don't have an rom in .apk format, only zip.
Click to expand...
Click to collapse
Update: after trying the same thing 100 times it decided to send "sideload". command line was adb sideload name.zip. Installing Viper ROM for HOX+ atm. I'll see if it fixes all of my problems. Thanks for all of the help to this point. I'll type up a guide of what went wrong with my root and how we managed to get it fixed.
Update: Phone is booting to HTC white screen and then shutting off. Now trying to figure that one one out.
Update" Phone is booting to HTC white screen now and staying there. In TWRP under reboot is says "no os installed, do you still wish to reboot". Still digging in the forums to figure this one out and how to fix it. I installed the Viper ROM fine but when it asked to reboot now it just rebooted to HTC white screen. Missing something here? The phone is S-ON, does that make a difference in using the TWRP?
Is there an RUU exe file I can run from my computer? I relocked the phone but the links you gave me are for installing the ap through google play. Not sure how you do that with a phone that wont boot past htc screen.
Update: I've found an RUU application from these boards that is supposed to work for HOX+ so i'm downloading it. It really is taking forever to find the information I need along the way from this board but it's here....somewhere...I think...Will keep plugging away but feel free to throw me a bone ever once in a while! =)
Update: The version that worked for others isn't the same version I have. Going to dig again for 1.19.502.1 version.
Update: Found the version in the last place I thought it would be...HTC website...Downloading it and just hoping its and application I can run on my computer.
Problem Fixed:
Problem: While trying to root phone I didn't back it up. Unlock was successful but root was not. OS was lost and phone would not boot past HTC white screen.
Solution: Relocked phone using fastboot oem relock. Downloaded manual ROM installation of the same version and intalled it while phone plugged in.
Thanks for the help in pointing me in the right direction. Now to try and root it again to install viper. If it screws up I know how to get back :laugh:
bullmurf said:
Problem Fixed:
Problem: While trying to root phone I didn't back it up. Unlock was successful but root was not. OS was lost and phone would not boot past HTC white screen.
Solution: Relocked phone using fastboot oem relock. Downloaded manual ROM installation of the same version and intalled it while phone plugged in.
Thanks for the help in pointing me in the right direction. Now to try and root it again to install viper. If it screws up I know how to get back :laugh:
Click to expand...
Click to collapse
I would suggest you to use hasoon's all in one toolkit
I went with another Rom. Honestly I tried the toolkit and ity worried fine at first but later it wouldn't work for me. After doing this for two straight days I learned to do it the hard way. New Rom is great. trying to explore my new freedoms now. I really want to change my lock screen.
bullmurf said:
I went with another Rom. Honestly I tried the toolkit and ity worried fine at first but later it wouldn't work for me. After doing this for two straight days I learned to do it the hard way. New Rom is great. trying to explore my new freedoms now. I really want to change my lock screen.
Click to expand...
Click to collapse
There is a great lockscreen called CLocker
Addicted2xda said:
There is a great lockscreen called CLocker
Click to expand...
Click to collapse
looking for it now. Trying to figure out how to replace the ring one from HTC. Is that possible? Probably in the boards somewhere
bullmurf said:
looking for it now. Trying to figure out how to replace the ring one from HTC. Is that possible? Probably in the boards somewhere
Click to expand...
Click to collapse
You will find it in the playstore itself
You need to set lockscreen to None
Addicted2xda said:
You will find it in the playstore itself
You need to set lockscreen to None
Click to expand...
Click to collapse
Thanks again man. I got it and the ring is gone \0/ Phone looks freakin amazing now with that lock screen and Elegancia rom. Glad you stopped by to help :good: Still learning my way around the forums and my rooted phone. It's great to not be stressed about bricking it ^^
suppils soars
bullmurf said:
Problem Fixed:
Problem: While trying to root phone I didn't back it up. Unlock was successful but root was not. OS was lost and phone would not boot past HTC white screen.
Solution: Relocked phone using fastboot oem relock. Downloaded manual ROM installation of the same version and intalled it while phone plugged in.
Thanks for the help in pointing me in the right direction. Now to try and root it again to install viper. If it screws up I know how to get back :laugh:
Click to expand...
Click to collapse
Hi there, I'm a noob and got the same problem, by mistake I formatted the system folder of my phone, now I'm stuck in the white HTC screen too, could you please post the links for the tools you used to bring the phone back to life? some instructions would be great to, thanks in advance...
mrmagoogt said:
Hi there, I'm a noob and got the same problem, by mistake I formatted the system folder of my phone, now I'm stuck in the white HTC screen too, could you please post the links for the tools you used to bring the phone back to life? some instructions would be great to, thanks in advance...
Click to expand...
Click to collapse
If you have installed TWRP - go to hasoon's thread, download the toolkit and use the function adb sideload to copy a rom your choice.
Flash the ROM using TWRP. Flash the kernel from hasoon's toolkit.
Addicted2xda said:
If you have installed TWRP - go to hasoon's thread, download the toolkit and use the function adb sideload to copy a rom your choice.
Flash the ROM using TWRP. Flash the kernel from hasoon's toolkit.
Click to expand...
Click to collapse
Thanks, phone is rooted but has CWM v6.0.2.7 installed, however, I can see the "install zip from sideload" option, when I choose this option it says "Now send the package you want to apply to the device with "adb sideload <filename>"", I don't know how to do that...
mrmagoogt said:
Thanks, phone is rooted but has CWM v6.0.2.7 installed, however, I can see the "install zip from sideload" option, when I choose this option it says "Now send the package you want to apply to the device with "adb sideload <filename>"", I don't know how to do that...
Click to expand...
Click to collapse
Flash TWRP man!
If you just browse through the forum - you will see that CWM is discouraged....
Addicted2xda said:
Flash TWRP man!
If you just browse through the forum - you will see that CWM is discouraged....
Click to expand...
Click to collapse
Thanks, I used a script to charge my battery, relock bootloader and installed ruu file to get back to stock, rooted again using Hasoon2000's all in one kit...
i need some help. i just bought my htc one tonight, and of course the first thing i want to do after i turn it on is root. but i can't get fastboot to recognize it. i've reinstalled the drivers a few times, googled my heart out, and can't seem to come up with an answer.
now before a lynch mob starts, please, i'm very frustrated, and i'm fighting the urge to just throw the phone into the wall. (at this point i think it's the only thing i haven't tried).
i read somewhere about firmware and windows 8.1 (which i'm on). my phone is still on 4.1.2. i think i read 4.3 is the only one that works with windows 8.1. but there are no updates available to me.
i greatly appreciate any help here. it's such a let down to get a shiny new phone, and being stuck... once i figure out the fastboot problem i should be good to go. i want to say i had this problem a while back with my htc one x, but it was so long ago i don't remember how i fixed it. in the middle there i switched to the s3 and that rooted without a hitch.
i don't know what i did but the phone magically decided now it wants to do the att update, it's downloading pretty slow but i'll see what happens.
ck4794 said:
i need some help. i just bought my htc one tonight, and of course the first thing i want to do after i turn it on is root. but i can't get fastboot to recognize it. i've reinstalled the drivers a few times, googled my heart out, and can't seem to come up with an answer.
now before a lynch mob starts, please, i'm very frustrated, and i'm fighting the urge to just throw the phone into the wall. (at this point i think it's the only thing i haven't tried).
i read somewhere about firmware and windows 8.1 (which i'm on). my phone is still on 4.1.2. i think i read 4.3 is the only one that works with windows 8.1. but there are no updates available to me.
i greatly appreciate any help here. it's such a let down to get a shiny new phone, and being stuck... once i figure out the fastboot problem i should be good to go. i want to say i had this problem a while back with my htc one x, but it was so long ago i don't remember how i fixed it. in the middle there i switched to the s3 and that rooted without a hitch.
Click to expand...
Click to collapse
Im sure you did this, but did you make sure in HBOOT its highlighted in red "FASTBOOT USB"? And you are in the platform tools folder of the android sdk? How about ADB? Does "adb devices" (Without quotations) work?
Let me know.
GalaxyUser50 said:
Im sure you did this, but did you make sure in HBOOT its highlighted in red "FASTBOOT USB"? And you are in the platform tools folder of the android sdk? How about ADB? Does "adb devices" (Without quotations) work?
Let me know.
Click to expand...
Click to collapse
i haven't gotten there yet. still trying to do the update. for some reason i can only download 10 or 15 mb at a time. it seems like it's timing out, maybe losing connection. after a restart it downloads for a while again. so basically it's going to be a loooong night to get this update done. and some prayer that the update is not corrupted.
ck4794 said:
i haven't gotten there yet. still trying to do the update. for some reason i can only download 10 or 15 mb at a time. it seems like it's timing out, maybe losing connection. after a restart it downloads for a while again. so basically it's going to be a loooong night to get this update done. and some prayer that the update is not corrupted.
Click to expand...
Click to collapse
Are you trying this on wifi or data?
ck4794 said:
i haven't gotten there yet. still trying to do the update. for some reason i can only download 10 or 15 mb at a time. it seems like it's timing out, maybe losing connection. after a restart it downloads for a while again. so basically it's going to be a loooong night to get this update done. and some prayer that the update is not corrupted.
Click to expand...
Click to collapse
you need to s-off your phone before taking that update !!!
and you need a windows 8 or windows 7 PC ... you'll never get fastboot on windows 8.1 and hboot 1.44.000 might as well give up on that.
clsA said:
you need to s-off your phone before taking that update !!!
and you need a windows 8 or windows 7 PC ... you'll never get fastboot on windows 8.1 and hboot 1.44.000 might as well give up on that.
Click to expand...
Click to collapse
no that seemed to do the trick. installed the update this morning. the phone is now on 4.3 and fastboot works just fine.
ck4794 said:
no that seemed to do the trick. installed the update this morning. the phone is now on 4.3 and fastboot works just fine.
Click to expand...
Click to collapse
ok good ...try rumrunner if you want s-off
clsA said:
ok good ...try rumrunner if you want s-off
Click to expand...
Click to collapse
thanks. it's been a hot minute since i've had an htc phone, can you remind me why i would want s-off after i already have the device rooted?
ck4794 said:
thanks. it's been a hot minute since i've had an htc phone, can you remind me why i would want s-off after i already have the device rooted?
Click to expand...
Click to collapse
This pretty well sums it up
S-OFF – What And Why?
In their devices, HTC have installed a sort of security check whose level is determined by S-OFF/S-ON. Essentially, this security level is a flag stored on the device’s radio that checks signature images for any firmware before it is allowed to be written to system memory. This hinders using any custom ROMs, splash images, recovery etc., and also restricts access to the NAND flash memory. However, when security level is set to S-OFF, the signature check is bypassed, allowing a user to upload custom firmware images, unsigned boot, recovery, splash and HBOOT images, as well as official firmware that has been modified, this enabling maximum customization of your HTC Android device.
Furthermore, S-OFF also reduces restrictions on accessing the NAND flash memory on the device, allowing all partitions (including /system) to be mounted in write mode while the operating system is booted.
Source: http://www.addictivetips.com/mobile...on-htc-android-phones-with-unrevoked-forever/
Click to expand...
Click to collapse
Hey guys,
I've been slackin' on the updates of my rom lately and thought it was finally time to do a proper update. I got my HTC one in the US around release and rooted it back then. However, now I was trying to install Android Revolution on it and the installation went fine (well, at least so I thought) up until the time I was going to boot it. It constantly keeps on re-booting me into the TWRP menu, even though the rom seems to be installed.
I was looking around and found out about ADP push http://forum.xda-developers.com/showthread.php?t=2325853
However, I get stuck on the step where I'm supposed to get up my Serial number in the terminal. It seems as if the command runs through but comes up with nothing, just a blank space. At first I simply ignored this and moved on to the next step. However, my computer doesn't seem to acknowledge the command ./adb push NameOfRom.zip /data/media/
Where do I go from here?
Thank you
Mr. Harrow
Mr_Harrow said:
Hey guys,
I've been slackin' on the updates of my rom lately and thought it was finally time to do a proper update. I got my HTC one in the US around release and rooted it back then. However, now I was trying to install Android Revolution on it and the installation went fine (well, at least so I thought) up until the time I was going to boot it. It constantly keeps on re-booting me into the TWRP menu, even though the rom seems to be installed.
I was looking around and found out about ADP push http://forum.xda-developers.com/showthread.php?t=2325853
However, I get stuck on the step where I'm supposed to get up my Serial number in the terminal. It seems as if the command runs through but comes up with nothing, just a blank space. At first I simply ignored this and moved on to the next step. However, my computer doesn't seem to acknowledge the command ./adb push NameOfRom.zip /data/media/
Where do I go from here?
Thank you
Mr. Harrow
Click to expand...
Click to collapse
I found this http://forums.androidcentral.com/htc-one/332846-hi-i-have-htc-one-m7-its-stuck-twrp.html
Shouldn't have to go through the hassle of going through that process though? Seeing as there's a zip of the android revolution on the phone which is installable, but nevertheless doesn't boot. Please help a fella out?
Try to wipe all but SD card, flash rim like normal, then pull the recovery logs (found in advance settings) and post it here if it won't boot
Also know that many HTC phones when unlocked through htcdev, need you to flash the kernel through fastboot after flashing the ROM, if you're unsure if you need to do this boot to bootloader and note all it says on this screen and then check your device forum for specifics on this
Sent from my Nexus 4 using XDA Premium 4 mobile app
Also make sure you got the correct rom from the correct forum. There are multiple One forums now and it's not the first time it's happened..
PS. ./adb is only for Linux - is that what you are running?
And I know the stuff is on /data/media but try this:
adb push nameofrom.zip /sdcard/
Just to be clear. Phone boots normally. All functions seem to work. After a minute or two phone locks up, then reboots. If phone is powered down it boots into recovery then locks up/freezes.
Apologize for length of this question but I wanted to be thorough. I have tried several things to resolve this, lots of reading and think I know a lot of things that are not causing the problem.
I installed the Andrenaline ROM, it ran fine for a couple of days then the phone started rebooting over and over again. Note it does not do this in TWRP (shutdown and reboot by itself) nor does it do it inHBoot. Only when I actually try to use the phone or apps after booting up. Initially I did the following all successfully:
I rooted using firewater using this thread http://forum.xda-developers.com/showthread.php?t=2632385 following the root all was fine and according to plan. No issues.
I then followed this thread http://forum.xda-developers.com/showthread.php?t=2498746
Finishing with this http://forum.xda-developers.com/htc-one-max/development/romsense6-adrenaline-4-4-2verizon-t2842331
Wanting to fix this and learn. I decided to go back to square one and even though TWRP seemed to be working I thought I should start there since I can see that I am rooted and have S off and the phone is unlocked.
That means I booted into the phone. Quickly ran adb and started in doing these steps:
adb devices #to make sure it was there
adb reboot bootloader #as per instructions all went well it booted into fastboot
fastboot flash recovery openrecovery-twrp-2.7.1.1-t6vzw.img
# Here seems to be the issue as it just says waiting for device ..... and nada thing happens. So while adb sees the device, runs the reboot of the bootloader it seems to be losing the connection or something at that point.
I am sure I have done something incorrectly. Can anyone lead me in the right direction toward resolving this? Any help would be greatly appreciated.
If somebody can just give me an idea of where the problem might be I would appreciate that. I thought about trying a different rom but system is so unstable I don't think I could get it loaded.
------------------------------------------------------------------------------------------------------------------
I think I was fooled because it ran well for a couple of days before I had issues. After re-reading the OP on the Adrenaline ROM page for about the 100th time I finally noticed ...
IF YOU HAVE ISSUES RUNNING CUSTOM KERNELS ON YOUR HTC ONE MAX, FLASH THIS IMMEDIATELY AFTER FLASHING THE ROM:
http://forum.xda-developers.com/devd...ct/dl/?id=7779
Click to expand...
Click to collapse
Flashing this from TWRP seems to have solved the issue. Thanks to all who at least read the question my apologies for wasting your time. I really did think I had read and seen everything. Actually read the whole thread and still missed that line in the opening post. Thanks to IAmTheOneTheyCallNeo for being so thorough and Flyhalf205 for having provided this. I can now go back to enjoying this fantastic ROM.
Glad you resolved it on your own. Good job
However, your issue with fastboot sounds like you don't really have working fastboot. While in fastboot, you do a "fastboot devices" instead of ADB devices. Then for recoveries it's a fastboot flash recovery nameofrecovery.img
Also, fastboot commands require a locked or re-locked bootloader to work for flashing things.
Neo
Forum Moderator
you are right
Thanks for the heads up. You are correct I have been working around this by using TWRP. I will do some research on how to get a working fastboot tomorrow. I am a linux only person but assume that being on Linux if I can get adb to work fastboot should work right?
Great call that you caught that it's really helpful to have a direction to head in.
IAmTheOneTheyCallNeo said:
Glad you resolved it on your own. Good job
However, your issue with fastboot sounds like you don't really have working fastboot. While in fastboot, you do a "fastboot devices" instead of ADB devices. Then for recoveries it's a fastboot flash recovery nameofrecovery.img
Also, fastboot commands require a locked or re-locked bootloader to work for flashing things.
Neo
Forum Moderator
Click to expand...
Click to collapse
statmonkey said:
Thanks for the heads up. You are correct I have been working around this by using TWRP. I will do some research on how to get a working fastboot tomorrow. I am a linux only person but assume that being on Linux if I can get adb to work fastboot should work right?
Great call that you caught that it's really helpful to have a direction to head in.
Click to expand...
Click to collapse
As a matter of fact, I downloaded the necessary tools for Linux which contain working fastboot and adb (They are not the same thing and two different entities). If I have time tonight I'll zip it up and upload it for you with command line install instructions for your Linux system. If not the it'll be tomorrow.
Neo
Forum Moderator
IAmTheOneTheyCallNeo said:
As a matter of fact, I downloaded the necessary tools for Linux which contain working fastboot and adb (They are not the same thing and two different entities). If I have time tonight I'll zip it up and upload it for you with command line install instructions for your Linux system. If not the it'll be tomorrow.
Neo
Forum Moderator
Click to expand...
Click to collapse
Above and beyond the call sir. That would certainly save me time, effort and confusion. I know just enough to blow a toe or two off. Tomorrow or whenever you have time. Beggars and idiots should not be demanding and feeling like the latter after this fiasco. Really appreciate your help and support.
statmonkey said:
Above and beyond the call sir. That would certainly save me time, effort and confusion. I know just enough to blow a toe or two off. Tomorrow or whenever you have time. Beggars and idiots should not be demanding and feeling like the latter after this fiasco. Really appreciate your help and support.
Click to expand...
Click to collapse
Download this file and unzip it: Androidv4.zip
then, navigate to the Android folder within terminal and launch the ADB-Install-Linux.sh:
Code:
. ADB-Install-Linux.sh
It will install adb and fastboot for linux.
It will install adb and fastboot for linux.[/QUOTE]
Again many thanks.
I have some meetings this evening but will install and test in the morning. Sure it will work well.
Last question
IAmTheOneTheyCallNeo said:
Download this file and unzip it:
then, navigate to the Android folder within terminal and launch the ADB-Install-Linux.sh:
Code:
. ADB-Install-Linux.sh
It will install adb and fastboot for linux.
Click to expand...
Click to collapse
Fastboot is now working properly. Thank you for your assistance.
No more questions. Worked all the way through the process from start to finish to make sure it was correct. Now 100% confident I have it and that it is correct. Thanks again for all the help.