Related
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
as the title asks, should I run the update I just got from AT&T? I read several differing opinions for different phones. some say don't, as it may relock the bootloader, others say it won't even let you complete the process if any /systems files are altered, some of mine are. Any input would be greatly appreciated.
ps it would suck if I lost root, as I can't establish a usb connection with my pc and wouldn't be able to reroot.
NoobDude said:
as the title asks, should I run the update I just got from AT&T? I read several differing opinions for different phones. some say don't, as it may relock the bootloader, others say it won't even let you complete the process if any /systems files are altered, some of mine are. Any input would be greatly appreciated.
ps it would suck if I lost root, as I can't establish a usb connection with my pc and wouldn't be able to reroot.
Click to expand...
Click to collapse
you will lose root. Just did it. I had to replace TWRP with stock recovery. However, i noticed speed improvements here and there. i have not really tested new radio yet... not enough time yet
thanks for the super speedy response, it's really appreciated! :good:
NoobDude said:
thanks for the super speedy response, it's really appreciated! :good:
Click to expand...
Click to collapse
i noticed my bootloader was still unlocked and i installed the cwm recovery,then booted into recovery. And when i went to leave recovery, it told me that my root may be lost and ask if i wanted to fix it. said yes and root appears to be back. then i installed latest TWRP(2.5) and all is ok! :good:
Edit:
after installing TWRP i did a backup (just in case). and after the back up it asked to fix permissions. said ok(as i thought maybe i lost root again) and it booted in android and root appears to be rooted. I tested with android terminal
a recovery can't be flashed in recovery with s-on** though, can it? To flash a new recovery you need to use adb no?
pardon my brain fart above..... so when you updated it erased your recovery? and the only way to install a recovery is via a usb connection? in other words, if I install the update while in my predicament, I'd loose recovery and root...
NoobDude said:
a recovery can't be flashed in recovery with s-on** though, can it? To flash a new recovery you need to use adb no?
pardon my brain fart above..... so when you updated it erased your recovery? and the only way to install a recovery is via a usb connection? in other words, if I install the update while in my predicament, I'd loose recovery and root...
Click to expand...
Click to collapse
you would boot into bootloader(fastboot) and flash the recovery:
$ sudo fastboot flash recovery <nameofrecovery>.img
edit: changed (hboot) to (fastboot) sorry if there was confusion, but it was late.
Orrrrr go and flash the AT&T update in it's Rom format. It's in Android Development.
can I flash the kernel in recovery though? I though with s on I had to do it from a computer using adb?
edit: ya there's no way I can flash the boot.img, that I know of at least, until I can get my usb connection working.
Are your drivers installed
yes and no. I installed HTC sync, the driver installer from Lucky 13s how to root post, and the ones from Hasoons tool. I tried installing then all separately, together, every which way. Currently all those programs are installed, yet in my device manager, nothing from HTC appears. It's like thy're installed but not. I backed up my phone right after I rooted it, nothing modified, its like it just came out the box only with root. I restored that "rom" and STILL it will not connect! I plug my phone in and NOTHING happens, it only charges. Tried different USB chords and plugged them into every USB port on the computer front and back, nothing , nadda, zip. I'm currently running vista, and am on the verge of dropping 100$ on Windows 7 and praying it fixes the problem. I've googled the CRAP out of this issue, and all i found are people who had FAILED installations. I've yet to get a failed message though. I swear i'm the only person with this issue. And its making me MAD... :crying:
NoobDude said:
yes and no. I installed HTC sync, the driver installer from Lucky 13s how to root post, and the ones from Hasoons tool. I tried installing then all separately, together, every which way. Currently all those programs are installed, yet in my device manager, nothing from HTC appears. It's like thy're installed but not. I backed up my phone right after I rooted it, nothing modified, its like it just came out the box only with root. I restored that "rom" and STILL it will not connect! I plug my phone in and NOTHING happens, it only charges. Tried different USB chords and plugged them into every USB port on the computer front and back, nothing , nadda, zip. I'm currently running vista, and am on the verge of dropping 100$ on Windows 7 and praying it fixes the problem. I've googled the CRAP out of this issue, and all i found are people who had FAILED installations. I've yet to get a failed message though. I swear i'm the only person with this issue. And its making me MAD... :crying:
Click to expand...
Click to collapse
do yourself a favor and get yourself a Live CD of Ubuntu. Ubuntu is free and the perferred OS for android. i swear by it. You can dual boot your vista and Ubuntu if you partition your hard drive. then after install and you boot into Ubuntu, hit ctrl-alt-t to open a terminal and type
Code:
sudo apt-get install android-tools-adb
when you type sudo you will have to enter your password, and it will not show it as you type
then
Code:
sudo apt-get install android-tools-fastboot
then restart the computer into Ubuntu
download the boot.img
press ctrl-alt-t
cd to the file directory (usually cd Downloads)
and type:
sudo fastboot flash boot <name of boot>.img
TheJokah said:
do yourself a favor and get yourself a Live CD of Ubuntu. Ubuntu is free and the perferred OS for android. i swear by it. You can dual boot your vista and Ubuntu if you partition your hard drive. then after install and you boot into Ubuntu, hit ctrl-alt-t to open a terminal and type
Code:
sudo apt-get install android-tools-adb
when you type sudo you will have to enter your password, and it will not show it as you type
then
Code:
sudo apt-get install android-tools-fastboot
then restart the computer into Ubuntu
download the boot.img
press ctrl-alt-t
cd to the file directory (usually cd Downloads)
and type:
sudo fastboot flash boot <name of boot>.img
Click to expand...
Click to collapse
Im very familiar with Ubuntu i have 12.04 dual booted on my acer chromebook and ran plenty of programs with terminal. Im going to take your advice right now and get cracking! Thanks a lot man!
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'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
So i just decided to join the rest of the world and get myself a rectangle. so i researched the 1 to 200 dollar range for weeks until i found my new shiny metal friend with great specs and a price that wouldn't keep me up at night. the le max 2 x829. but i love tech and was really looking forward to pushing this phone and learn about all it could do! i was really excited.
Until i started to learn about the many confusing programs needed to install custom roms or make a recovery file. things like that All of which need like 6 different programs all of which seem to need some other program in order to functional. I can't seem to even find a starting point! I HAVE NEVER FELT THIS STUPID IN MY ENTIRE LIFE. Someone please help. what programs do i need for a new os ? How does adb fit into the chain of programs needed to mod android? is twrp the first program needed? how does it all sort...fit to gather? Thanks for any help!
Man, honestly this forum is made to help people, but also people should use the search button. This question has been answered a million times already.
Long story short:
- Connect the phone to the PC and install the drivers (including ADB)
- Unlock bootloader (usually it's already unlocked)
- Download TWRP on your PC
- Install TWRP following the developer's steps
- Download your custom ROM
- Put the ROM on the internal memory
- Boot into TWRP
- Install the new ROM according to the instructions given by the developer and you're done...
valy_cta said:
Man, honestly this forum is made to help people, but also people should use the search button. This question has been answered a million times already.
Long story short:
- Connect the phone to the PC and install the drivers (including ADB)
- Unlock bootloader (usually it's already unlocked)
- Download TWRP on your PC
- Install TWRP following the developer's steps
- Download your custom ROM
- Put the ROM on the internal memory
- Boot into TWRP
- Install the new ROM according to the instructions given by the developer and you're done...
Click to expand...
Click to collapse
including adb? what other drivers do i need? xposed? supersu? ...i have done my research by the way...its just not making alot of sense..thats all. i know all you old pros have probably been at it for years but i never even held a smartphone until 6 days ago ha ha
valy_cta said:
Man, honestly this forum is made to help people, but also people should use the search button. This question has been answered a million times already.
Long story short:
- Connect the phone to the PC and install the drivers (including ADB)
- Unlock bootloader (usually it's already unlocked)
- Download TWRP on your PC
- Install TWRP following the developer's steps
- Download your custom ROM
- Put the ROM on the internal memory
- Boot into TWRP
- Install the new ROM according to the instructions given by the developer and you're done...
Click to expand...
Click to collapse
Also how do you download twrp on you're pc ? it won't let me i have it on my phone but it just keeps leading me to a website to download again.
Serialjwalker said:
Also how do you download twrp on you're pc ? it won't let me i have it on my phone but it just keeps leading me to a website to download again.
Click to expand...
Click to collapse
Do you have it installed on the phone or just downloaded? If it's installed, jump over that step. If it's just downloaded, connect the phone to the pc by cable, transfer the files :cyclops:
I understand your concern. It's because there are a few ways of doing it, and so novices might be confused when comparing two different tutorials.
This one is very complete: https://forum.xda-developers.com/le-max-2/how-to/protocol-backup-stock-rom-flash-stock-t3517151
1. Connect your phone, it is supposed to install drivers automatically.
1.1 If not, you'll need to google it, but I believe this toolkit will help you. In fact, this tool is capable of doing all the process for you by simply clicking on some buttons.2. Install ADB Drivers. There are a few options and it is basically
2.1 @greenManGaming recommends 15 seconds ADB installer.
2.2 (Alternative) Minimal ADB and Fastboot. I've used this one.
2.3 (Alternative) ADB and Fastboot (newer) or Universal ADB and Fastboot (older) from the same dev.
OBS: I'm not sure if the toolkit requires or not one of these options to work properly or if it already does this task.3. Download TWRP (on your computer).
3.1 Follow the instructions from the official page. In short, put the img into the ADB folder.4. Follow the commands in the the tutorial mentioned.
4.1 In short, unlock the bootloader, boot twrp, complete backup, reboot into the system, copy the backup to your PC/Cloud service, get back to fastboot mode, flash twrp, then flash your ROM.
OBS: Suggestion for only booting TWRP at the first time is perfectly optional, you can flash it since the beginning but in this case you wouldn't be able to backup the original recovery and everything as the phone came, in case you need go back to request an RMA.
razmth said:
I understand your concern. It's because there are a few ways of doing it, and so novices might be confused when comparing two different tutorials.
This one is very complete: https://forum.xda-developers.com/le-max-2/how-to/protocol-backup-stock-rom-flash-stock-t3517151
1. Connect your phone, it is supposed to install drivers automatically.
1.1 If not, you'll need to google it, but I believe this toolkit will help you. In fact, this tool is capable of doing all the process for you by simply clicking on some buttons.2. Install ADB Drivers. There are a few options and it is basically
2.1 @greenManGaming recommends 15 seconds ADB installer.
2.2 (Alternative) Minimal ADB and Fastboot. I've used this one.
2.3 (Alternative) ADB and Fastboot (newer) or Universal ADB and Fastboot (older) from the same dev.
OBS: I'm not sure if the toolkit requires or not one of these options to work properly or if it already does this task.3. Download TWRP (on your computer).
3.1 Follow the instructions from the official page. In short, put the img into the ADB folder.4. Follow the commands in the the tutorial mentioned.
4.1 In short, unlock the bootloader, boot twrp, complete backup, reboot into the system, copy the backup to your PC/Cloud service, get back to fastboot mode, flash twrp, then flash your ROM.
OBS: Suggestion for only booting TWRP at the first time is perfectly optional, you can flash it since the beginning but in this case you wouldn't be able to backup the original recovery and everything as the phone came, in case you need go back to request an RMA.
Click to expand...
Click to collapse
more questions....twrp will only load onto my phone and not my pc? also there are no adb driver folders just an exe. what do i do about that?
someone tell me how to delete this thread...i am just going to sell my smartphone i can't look at it anymore. every thing i try to do with it it resists every single inch of the way. nothing works according to instructions. i thought this would be fun but its hell... i give up! ...it wins going to trade this thing for the first 30 dollar burner phone i can find
Huge drama for nothing. Sell the thing, it's obviously not for you. If you can't follow some simple instructions, then it's better to sell it to some guy who likes to try at least.
valy_cta said:
Huge drama for nothing. Sell the thing, it's obviously not for you. If you can't follow some simple instructions, then it's better to sell it to some guy who likes to try at least.
Click to expand...
Click to collapse
maybe they are laid out to be simple but nothing is working as instructed. i have been at it for a week . so far installing firefox is the best i can seem to do lol simple? theres nothing simple about the gangbang of programs you need to do stuff on these phones. none of which can actually be compelled to function under any circumstances at least for me.
Serialjwalker said:
maybe they are laid out to be simple but nothing is working as instructed. i have been at it for a week . so far installing firefox is the best i can seem to do lol simple? theres nothing simple about the gangbang of programs you need to do stuff on these phones. none of which can actually be compelled to function under any circumstances at least for me.
Click to expand...
Click to collapse
If you are not familiar with giving commands with command prompt, installing drivers and needed software (android studio or minimal adb install) then you are in for a challenge, if you are not willing to learn its better to sell the phone or use it with de preinstalled android.
i find myself quite skilled( have flashed several brands of phoned in the last 5 years) and it took me a couple of days to figure out what to do and how to install twrp and my first rom, there are no one click shortcuts for this phone
Why need to install rom? It already work.
Serialjwalker said:
more questions....twrp will only load onto my phone and not my pc? also there are no adb driver folders just an exe. what do i do about that?
Click to expand...
Click to collapse
Did you try watching different videos to have a big picture of the process? It would be the first step. Even if you don't understand English, simply watch it. You'll see what would happen after each action.
Then check the written tutorial. Not a big issue at all. Really. Even for newbies, I've been one when I had a Galaxy 5, my first android that doesn't even needed to flash a custom ROM.
Whether you think you can, whether you think you can't, you're right.
The command to load the TWRP will be done on your PC, however, only your phone will load it. In short, you'll be commanding your phone through your PC.
When you install Minimal ADB and Fastboot, it will install its files in a default folder. Inside its default folder is where you should place the TWRP image.
Sent from my Le X820 using Tapatalk