Hi all,
I've searched high and low for the answer to this before posting, so I apologize in advance if I simply couldn't find it.
In trying to flash a ROM I managed to seriously mess myself up by wiping literally everything off my phone- my nandroids, my ROM file, everything. I'm running CWM v6.0.2.7 and trying to use adb sideload <rom>, but I keep getting the error "failed to write data 'protocol' no status". I've searched for that specific error and haven't found much about it that was able to help me. I get this message using Hasoon's amazing toolkit or by doing the sideload manually via the command prompt.
Any ideas? My phone's a pretty brick right now, which is entirely my fault- I just hope someone can help me out of this mess I got myself into!
Thank you so much in advance!
[EDIT]
I resolved the issue by switching from CWM and moving to TWRP and tried the sideload a few more times. I would often get the message that my device wasn't connected, but with some patience I got it to work. Good luck to anyone else who encounters this issue!
aladara said:
Hi all,
I've searched high and low for the answer to this before posting, so I apologize in advance if I simply couldn't find it.
In trying to flash a ROM I managed to seriously mess myself up by wiping literally everything off my phone- my nandroids, my ROM file, everything. I'm running CWM v6.0.2.7 and trying to use adb sideload <rom>, but I keep getting the error "failed to write data 'protocol' no status". I've searched for that specific error and haven't found much about it that was able to help me. I get this message using Hasoon's amazing toolkit or by doing the sideload manually via the command prompt.
Any ideas? My phone's a pretty brick right now, which is entirely my fault- I just hope someone can help me out of this mess I got myself into!
Thank you so much in advance!
Click to expand...
Click to collapse
you need to put the phone INTO sideload mode
Lloir said:
you need to put the phone INTO sideload mode
Click to expand...
Click to collapse
I have done that through the recovery and left it on that screen, that is when the errors pop up.
I know i'm a little late, but just in case somebody else goes looking for help on this.
I was stuck and kept getting the same error. everything was up to date and i was in ADB Sideload. Turns out after I wiped everything I never rebooted my phone. I rebooted back into recovery and it gave me the option to install SuperSu and root my phone (although it was previously rooted). Once I did that I was able to go back into ADB sideload and all worked well! Hope this helps somebody out there.
lebnan60 said:
I know i'm a little late, but just in case somebody else goes looking for help on this.
I was stuck and kept getting the same error. everything was up to date and i was in ADB Sideload. Turns out after I wiped everything I never rebooted my phone. I rebooted back into recovery and it gave me the option to install SuperSu and root my phone (although it was previously rooted). Once I did that I was able to go back into ADB sideload and all worked well! Hope this helps somebody out there.
Click to expand...
Click to collapse
But what if you have no rom on your phone ?
cyberusman said:
But what if you have no rom on your phone ?
Click to expand...
Click to collapse
The sideload command is used WHEN you have no rom on your SDcard/phone. If you can boot into your phone (access home screen) you can just activate USB Debugging and connect to PC and just move files normally.
The Sideload protocol is used when you can't access your home screen (When you are in a bootloop) and all you can access is the Recovery. So you activate Sideload from the recovery and on your PC you use adb sideload "rom file" without the quotes and then the ROM installs directly from your computer storage.
There is also a feature in ADB called adb push, you literally push the file to your phone SDCard, its like you copy and paste a file. But since i never used it i don't know if you do it while in the bootloader or recovery or not. But I think you can.
I know this is quite some time later, but I was wiping my Nexus 7 to sell. Tried the TWRP Sideload feature and could sideload a ROM...great! So wiped the entire device clean and attempted sideload....failed! Wasn't a good feeling at all...so looked around and found this tidbit of info. Rebooted (to recovery), prompted for Root, accepted, and then sideload worked perfectly.
Of note, I couldn't sideload the gapps right afterwards, so had to reboot into Recovery again to re initiate Sideload, and got gapps installed too.
Thanks for the tip!
lebnan60 said:
I know i'm a little late, but just in case somebody else goes looking for help on this.
I was stuck and kept getting the same error. everything was up to date and i was in ADB Sideload. Turns out after I wiped everything I never rebooted my phone. I rebooted back into recovery and it gave me the option to install SuperSu and root my phone (although it was previously rooted). Once I did that I was able to go back into ADB sideload and all worked well! Hope this helps somebody out there.
Click to expand...
Click to collapse
Glad it helped! I've been meaning to post an update, also. I've run into the issue where the newest version of TWRP doesn't re-root the device as mentioned initially. I've been using a beta version of TWRP needed for some of the newer Kit Kit roms and had to flash an older version of TWRP to get ADB Sideload working again.
Basically I would flash an older version of TWRP, re-boot (and it would ask to root the device) ADB Sideload an older rom, such as CM 10.1 or another Jellybean rom and from there you can boot up the system and make any changes needed.
Sadly I keep wiping my phone clean and running into these issues. Hopefully I've learned my lesson
Related
Hey guys,
I've done something rather stupid....
Basically I've ended up with no OS on my phone so it won't boot (obviously).
I can't flash any .zip roms because I can't access the internal storage (as it won't boot)
I have a 1.14... O2 RUU that won't install as my hboot version was updated to 1.35, so installing that RUU is not an option either.
I can't find any RUU's on the internet (thanks HTC) and adb 'sideloading' is not working because it does not recognise that the drivers are installed.
Any help would be appreciated.
PS: If anyone has a recent RUU that I could use I would be very grateful!
update your twrp to the most recent OR use CWM 6 by myself, sideload takes a good couple of minutes to "turn on" so leave your phone in sideload connected to the pc for about 2-5minutes and it SHOULD see it. it's easier to sort it out this way now than trying to find an RUU. IF you can't get sideload to work AT ALL i have an ALPHA build of TWRP with which you can adb push rom's onto your "sdcard" with. let me know via pm
thanks
-Lloir
Lloir said:
update your twrp to the most recent OR use CWM 6 by myself, sideload takes a good couple of minutes to "turn on" so leave your phone in sideload connected to the pc for about 2-5minutes and it SHOULD see it. it's easier to sort it out this way now than trying to find an RUU. IF you can't get sideload to work AT ALL i have an ALPHA build of TWRP with which you can adb push rom's onto your "sdcard" with. let me know via pm
thanks
-Lloir
Click to expand...
Click to collapse
Thanks I'll try this, just waiting for my phone to charge
I did this just today as well, I accidentally wiped my whole system and now i have no os, but i do have a recovery and bootloader.... I dont know what to do, please help me I'm a noob at this
Tainted_Noob said:
I did this just today as well, I accidentally wiped my whole system and now i have no os, but i do have a recovery and bootloader.... I dont know what to do, please help me I'm a noob at this
Click to expand...
Click to collapse
Relock bootloader then put the phone in usb mode, run RUU
Worked for me before.
Sent from my HTC One X+ using Tapatalk 2
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...
Hey guys, if this is in the wrong section feel free to move it. For whatever reason there still isn't a sub-section for the Pantech Flex...
Anyways, long story short, I had some issues with the stock setup and so I used the built-in Reset option under Settings -> Backup & Reset..
This resulted in a soft-brick of sorts, I can't get past the AT&T logo screen, and since it had just been reset, USB Debugging is NOT enabled.. *sigh*
So, I'm trying to use Fastboot to flash/boot CWM so I can recover from this little predicament (I hadn't successfully flashed CWM yet).. but on 99% of Fastboot commands, I get the following error:
Code:
C:\> fastboot flash recovery cwm.img
sending 'recovery' (8076 KB)...
OKAY [ 0.608s]
writing 'recovery'...
FAILED (remote: Not Support !!)
finished. total time: 0.608s
Which leads me to believe I need to unlock some things.. and upon looking around (the VERY limited information for this device...) I found a few suggestions of using "fastboot oem unlock", however it gives the same "FAILED (remote: Not Support !!)" command..
Anyone know anything that may help? Thanks guys!
You probably should be able to get out of trouble with this thread: http://forum.xda-developers.com/showthread.php?t=2472487
Ur lucky its soft brick!
Mine got super hard bricked.....
There are many ways to solve soft brick....
Just go cwm and flash a right rom for u.....
If u dont have cwm feel free to search in the forum......
Sent from my iPad mini using Tapatalk HD
Thy Boss said:
Ur lucky its soft brick!
Mine got super hard bricked.....
There are many ways to solve soft brick....
Just go cwm and flash a right rom for u.....
If u dont have cwm feel free to search in the forum......
Sent from my iPad mini using Tapatalk HD
Click to expand...
Click to collapse
OP stated that they have not had any luck getting CWM to work.
And to OP - sorry! I just double checked the instructions I linked to, but realized you need adb working for the method if you are already on JB. Please let me know if you are ICS or JB and I'll see if I can't give you better direction...
es0tericcha0s said:
OP stated that they have not had any luck getting CWM to work.
And to OP - sorry! I just double checked the instructions I linked to, but realized you need adb working for the method if you are already on JB. Please let me know if you are ICS or JB and I'll see if I can't give you better direction...
Click to expand...
Click to collapse
Sadly yes, I'm already on JB.. My apologies for the slow reply, didn't get notifications like I thought I had set.
Also, I've gotten it to boot up, but the launcher seems to have been erased and so I get a black screen. Status bar still appears but I can't pull it down to access settings. Navigation buttons respond to input but are still useless without a launcher.
On another note, I've tried flashing a few zips via stock recovery's adb sideload mode, everything from cwm to an entire (stock and otherwise) rom, even just a launcher since that should be all I need, but every time I tried to sideload, it would get to 49% and suddenly "Installation Aborted!" Not sure why that doesn't work... *sigh*
FalloutState said:
Sadly yes, I'm already on JB.. My apologies for the slow reply, didn't get notifications like I thought I had set.
Also, I've gotten it to boot up, but the launcher seems to have been erased and so I get a black screen. Status bar still appears but I can't pull it down to access settings. Navigation buttons respond to input but are still useless without a launcher.
On another note, I've tried flashing a few zips via stock recovery's adb sideload mode, everything from cwm to an entire (stock and otherwise) rom, even just a launcher since that should be all I need, but every time I tried to sideload, it would get to 49% and suddenly "Installation Aborted!" Not sure why that doesn't work... *sigh*
Click to expand...
Click to collapse
Got yourself a tricky one here.
http://forum.xda-developers.com/showpost.php?p=37320624&postcount=88
Use that modded stock recovery to have proper adb access in recovery, and do: adb install launcher.apk (non /system version with that command, and launcher.apk can be named anythingyouwant.apk)
I kind of think that isn't going to be enough though.
If that doesn't work, it might be worth trying to fastboot boot a version of CWM, have the rom you need on the SD card and use that to flash. CWM won't stay, but if you boot and all is well, that can be re-added easily. Let's get the easy option out of the way first though.
es0tericcha0s said:
Got yourself a tricky one here.
http://forum.xda-developers.com/showpost.php?p=37320624&postcount=88
Use that modded stock recovery to have proper adb access in recovery, and do: adb install launcher.apk (non /system version with that command, and launcher.apk can be named anythingyouwant.apk)
I kind of think that isn't going to be enough though.
If that doesn't work, it might be worth trying to fastboot boot a version of CWM, have the rom you need on the SD card and use that to flash. CWM won't stay, but if you boot and all is well, that can be re-added easily. Let's get the easy option out of the way first though.
Click to expand...
Click to collapse
I saw that first link while searching for solutions, however that dropbox link is dead. @timmythanoob, do you still have this file available?
As far as your second idea of using "fastboot boot xxx.img" or whatever have you, the issue with that is that the "boot" command is one of the Fastboot commands I mentioned in the OP that gives the "Remote: Not Support!!" error, which from what I can find is an issue with "aboot" in the JB update...
If I can get ahold of timmythanoob's recovery image with ADB access, then even if adb install'ing a launcher doesn't work, I could still have WAY more options to work with and I'm confident that with full ADB access I could restore the device to working order... IF someone can get me that recovery w/ adb :|
EDIT: Actually I don't think even timmythanoob's recovery image will work since I don't have access to the "fastboot boot" command... I really think my only options are PDL mode and sideloading a zip in recovery. PDL won't work because of the lack of PDL's for our device (and Pantech refusing to give me one), and sideloading a zip in recovery, for whatever reason, always seems to fail with an Installation Aborted... -_-
Anyone have any ideas?
Sorry, a lot of the info for this phone is mixed and matched between instructions for ICS and JB. So, basically, it seems you are boned. Only way to properly get fastboot to work would be to downgrade the aboot, which you can't do because you have to be rooted and booted while on JB to do so. Same thing with CWM on JB. Have to be rooted and booted. :/ Sorry man.
Last resort I can see would be trying to flash the JB OTA zip via stock recovery:
http://forum.xda-developers.com/showpost.php?p=46025559&postcount=164
But even that guy who obviously knows these devices a bit better than we do says it probably wouldn't work for someone in your situation a bit later in that thread:
http://forum.xda-developers.com/showpost.php?p=46209691&postcount=174
But that's pretty much your last option at this stage other than sending it into Pantech so they can use their firmware flashing tool since they won't share it with anyone.
I tried that JB OTA, didn't work. 49% and then Installation Aborted. I was going to send it to Pantech but I imagine they won't help since thanks to my recovery attempts, in the bootloader screen it shows as being rooted and tampered with.
Sucks man. One of the downsides of their being so many different devices out there. Only so many developers to go around and that combined with little to no support from Pantech... :/
I'm going to claim OP resurrection rights and bring this back up in hopes that someone can help. Anyone know anything?
Sent from my YP-G1 using Tapatalk
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/
Q&A for [RECOVERY] TWRP Recovery 2.8.1.0 - Apollo
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY] TWRP Recovery 2.8.1.0 - Apollo. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
droiduzr2 said:
My device is "bricked". I screwed up safestrap install and my device just boots to the grey kindle screen.
Click to expand...
Click to collapse
Just to clarify: does your device
get stuck forever at
spontaneously restart after
get stuck forever at a blank screen after
the "grey kindle screen"?
I managed to recover from the third alternative, but then I had adb access while the screen was blank...
draxie said:
Just to clarify: does your device
get stuck forever at
spontaneously restart after
get stuck forever at a blank screen after
the "grey kindle screen"?
I managed to recover from the third alternative, but then I had adb access while the screen was blank...
Click to expand...
Click to collapse
my device boots up and stays at grey kindle screen
nothing happens after
That doesn't tell us anything.
How can I check if recovery is installed successfully? I could rollback to 309 and update with stock 310. Then I had to root and followed the instructions in the first post. Adb showed something with in and out, I rebooted and nothing seemed to have changed.
Wher I start with vol + It shows only reboot and factory reset.
Bruder Torgen said:
How can I check if recovery is installed successfully? I could rollback to 309 and update with stock 310. Then I had to root and followed the instructions in the first post. Adb showed something with in and out, I rebooted and nothing seemed to have changed.
Wher I start with vol + It shows only reboot and factory reset.
Click to expand...
Click to collapse
If you're not booting into TWRP, then it probably didn't install.
Try using Flashify.
Great, I had to sideload Flashify apk and install it via adb install, then it worked , I could see the difference
Till now all seems great although the way to reach it is not described perfectly (as I normally have only to do with windows systems, too many steps I had to find out by myself and I never knew if the tablet will be still alive after the next step )
Pretty Good Work , thanks a lot for all your effort !!!!
Factory Reset?
droiduzr2 said:
my device boots up and stays at grey kindle screen
nothing happens after
Click to expand...
Click to collapse
I see... I suppose you have checked, and adb doesn' t work..
(Otherwise, although a long shot, it may be worth double-checking.)
BUT, you say you can get into recovery (Power+VolumeUp, I assume):
droiduzr2 said:
I can get into that weird looking recovery that does not allow fastboot.
Click to expand...
Click to collapse
The Amazon stock recovery should have a 'Factory Reset' option.
Have you tried that one? (WARNING: all your data will likely be gone; not sure if it helps with the OS, though...)
BTW, do you remember _how_ exactly messing up SafeStrap happened?
If you provide details, someone with a more intimate understanding of how SafeStrap works
may have an idea how you might go about getting your device back to life again.
draxie said:
I see... I suppose you have checked, and adb doesn' t work..
(Otherwise, although a long shot, it may be worth double-checking.)
BUT, you say you can get into recovery (Power+VolumeUp, I assume):
The Amazon stock recovery should have a 'Factory Reset' option.
Have you tried that one? (WARNING: all your data will likely be gone; not sure if it helps with the OS, though...)
BTW, do you remember _how_ exactly messing up SafeStrap happened?
If you provide details, someone with a more intimate understanding of how SafeStrap works
may have an idea how you might go about getting your device back to life again.
Click to expand...
Click to collapse
Thank you for the detailed response.
Yes, I did install safestrap. I admit I did not fully understand what I was doing. I thought I would just wipe everything to have a clean system as we usually do for most devices. I wiped the system also which deleted the system rom.
Upon reboot it just sits at the grey kindle screen never booting past. I played around with the buttons and stumbled upon the power and vol+.
I got into Kindle system recovery and did the wipes but nothing boots up because I deleted the system os.
Would ADB work from the Kindle recovery screen?
Remember I have no OS on the device now.
Please let me know what to do now?
Where are the Kindle drivers for Win7 which has ADB driver for it. The problem is windows will not recognize the device I don't think.
14.3.2.4 can have twrp?
I want to install the nuxus rom into my HDX 8.9 with twrp.
I just wonder if I can install the twrp to my 14.3.2.4 version HDX.
Can I ?
by the way, I cannot find a step-by-step twrp install procedure.
If someone posts a youtube video, it will be awesome.
vandy_andy said:
I want to install the nuxus rom into my HDX 8.9 with twrp.
I just wonder if I can install the twrp to my 14.3.2.4 version HDX.
Can I ?
by the way, I cannot find a step-by-step twrp install procedure.
If someone posts a youtube video, it will be awesome.
Click to expand...
Click to collapse
No, you need to downgrade to a firmware version older than x.3.2.4.
http://forum.xda-developers.com/showthread.php?t=2782159
EncryptedCurse said:
No, you need to downgrade to a firmware version older than x.3.2.4.
http://forum.xda-developers.com/showthread.php?t=2782159
Click to expand...
Click to collapse
Thank you for the answer.
So , so far no easy way.
Apollo first release of TWRP started at .0 flashed renamed files each increment up to and including .2.4 I know I can redo the downgrade and anything else I need to do once I get a usable ui
well like a dumbA I tried to upgrade via rename bin to zip got to .2.4 lost any recovery and black screen.... I do have root and adb shell permission and it does boot ,charge etc. Just no display for most part like any launcher .. ( I still got super user prompt for ADB shell )...I also wiped data for all user and system apps via titanium backup not sure if that made black screen or not .... need to flash stock .2.4 recovery? To fix black screen? Or do I need to push a Specific file ? That of which I do not know the details of . Because I don't know which files would have been deleted by titanium backup . The device has been sitting for a few weeks now I figure it's time to get it up and running any help would be appreciated thanks
jimyv said:
Apollo first release of TWRP started at .0 flashed renamed files each increment up to and including .2.4 I know I can redo the downgrade and anything else I need to do once I get a usable ui
well like a dumbA I tried to upgrade via rename bin to zip got to .2.4 lost any recovery and black screen.... I do have root and adb shell permission and it does boot ,charge etc. Just no display for most part like any launcher .. ( I still got super user prompt for ADB shell )...I also wiped data for all user and system apps via titanium backup not sure if that made black screen or not .... need to flash stock .2.4 recovery? To fix black screen? Or do I need to push a Specific file ? That of which I do not know the details of . Because I don't know which files would have been deleted by titanium backup . The device has been sitting for a few weeks now I figure it's time to get it up and running any help would be appreciated thanks
Click to expand...
Click to collapse
Well, if you have adb access and root, you can try this
jeryll said:
Well, if you have adb access and root, you can try this
Click to expand...
Click to collapse
actually I had seen this and had thought I might give that a shot but I do not have any recovery the flash of. 2.4 borked the recovery ..I know this because I tried to boot into it several times before flashify geek out on my paid subscription because my Google stopped working. That's why I attempted to wipe the data for all the apps. So I can attempt to use flashify to restore stock recoveryI believe it was when I picked option in Titanium Backup to wipe all data for system and user apps. Not really because of the fact I did not have a functioning recovery. I do not believe because I had rebooted the serval times and still had a working system until I wiped the data. Maybe if I had a copy of the stock image recovery I could attempt to flash it then try that...? I did extract the .2.4 files but didn't spot recovery image
jimyv said:
actually I had seen this and had thought I might give that a shot but I do not have any recovery the flash of. 2.4 borked the recovery ..I know this because I tried to boot into it several times before flashify geek out on my paid subscription because my Google stopped working. That's why I attempted to wipe the data for all the apps. So I can attempt to use flashify to restore stock recoveryI believe it was when I picked option in Titanium Backup to wipe all data for system and user apps. Not really because of the fact I did not have a functioning recovery. I do not believe because I had rebooted the serval times and still had a working system until I wiped the data. Maybe if I had a copy of the stock image recovery I could attempt to flash it then try that...? I did extract the .2.4 files but didn't spot recovery image
Click to expand...
Click to collapse
if you need recovery.img for Thor here is one, confirmed its working here
if you need stock recovery.img for Apollo here is one + md5 file here, its for 14.3.1.0 (md5 hash: acb175637241e6ecaf6dfef5ba7f343b)
jeryll said:
if you need recovery.img for Thor here is one, confirmed its working here
if you need stock recovery.img for Apollo here is one + md5 file here, its for 14.3.1.0 (md5 hash: acb175637241e6ecaf6dfef5ba7f343b)
Click to expand...
Click to collapse
Apollo first release of TWRP started at (.0) flashed renamed files each increment up to and including( .2.4 )I know I can redo the downgrade and anything else I need to do once I get a usable ui
not unless the recovery is black screen also. What is strange is when it is booted and I tried adb shell I did get su prompt ,,, just no launcher or notification bar etc..this is what I'm thinking let me know if I am mistaken. I should grab and flash a stock recovery image via the same as flashing this recovery with PC. Push. 3.2 build prop file to system then try this. http://forum.xda-developers.com/show....php?t=2793253 with .2.4 WiFi was off before black screen and OTA had been re- enabled I believe.and this is probably important to I do actually have a lock screen. And poweroff menu I am going to try that command now..
access denied going to reboot everything and try again
this is double posted in main thread with @ggow
Maybe a silly or noob question, but I have no answer (maybe I missed it although I read this thread) ..
I'm on TWRP 2.8.1.0 (and have Nexus 2.0.5). Is there an easy update way to 2.8.5.0 ? I can't imagine that I've to go back to stock rom ?!
Bruder Torgen said:
Maybe a silly or noob question, but I have no answer (maybe I missed it although I read this thread) ..
I'm on TWRP 2.8.1.0 (and have Nexus 2.0.5). Is there an easy update way to 2.8.5.0 ? I can't imagine that I've to go back to stock rom ?!
Click to expand...
Click to collapse
It's as simple as flashing the new image.
This is no different than any other device.
I thought the root for 4.5.2 and there's no root for 4.5.3 this is why I didn't update and disabled OTA. How can this method is for 4.5.3 only and it requires root? I think I miss something here. Please, help me to get it