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/
Related
Hi there everyone, i am in need of assistance.
I have follwed the guide on here for downgrading my phone usin the ADB commands and all is good up until the actual downgrading stage. After a few attempts i had managed a temp root (i think) using command line.
" adb shell " brought back the # so i know i did that right, but when it comes to pushing the rom file to my sd card it comes back adb not found in which case i cannot reboot the bootloader if that doesnt work.
Is there something i am doing wrong or is the file im uusing just not compatible, "PC10IMG.zip"
If there is another way to downgrade after temp root with maybe a different rom file i would be very grateful if someone could help me.
Any questions you have to help me, just let me know
Thanks
Sent from my HTC Vision using XDA App
Im still very new at this but i'll thrown in my two cents here.
After you've gotten temporary root status '#' and you've set your version to 1.00.000.0 following the guide, your next step is it push the stock ROM used to downgrade into your sd card.
At this point make SURE you are not in the adb shell, (aka you dont see the #)
so make sure you exit first.
Another thing is to make sure the ROM you want to push, the "...._PC10IMG.zip" file is in the correct directory, same directory as your CMD.
Lastly the push process takes time so dont be impatient, unlike the other files you pushed before which were more or less instant, this one will take at least a minute and the CMD may look idle so really just have to wait.
when the results show, you can then proceed with reboot bootloader command.
hope it helps.
i got stuck after this point, i keep getting a cid error, which is a totally differnt issue from your above question.
Cut to the chase, I can no longer get into recovery. I am trying to use adb in command prompt, but am running into a roadblock where $ comes up, and no commands will work. I quite literally have no idea what to do. I just want to go back to normal. I know it's my fault for trying new things, but if the phone still boots up, there must be a way out of this hell. Please can anyone have mercy on me and help? What information must I provide? VM670 is the phone. I think it's on stock ROM cause the UI is all virgin mobile looking.
Edit: I tried to restore some BCDS backup or something in Rom manager. Now my screen is just black, but I can hear it boot up. Is my phone toast?
mcnic05 said:
Cut to the chase, I can no longer get into recovery. I am trying to use adb in command prompt, but am running into a roadblock where $ comes up, and no commands will work. I quite literally have no idea what to do. I just want to go back to normal. I know it's my fault for trying new things, but if the phone still boots up, there must be a way out of this hell. Please can anyone have mercy on me and help? What information must I provide? VM670 is the phone. I think it's on stock ROM cause the UI is all virgin mobile looking.
Edit: I tried to restore some BCDS backup or something in Rom manager. Now my screen is just black, but I can hear it boot up. Is my phone toast?
Click to expand...
Click to collapse
I am not sure if I remember correctly, but when $ pops up, don't you have to type "su" (without the quotations) to allow superuser actions or something? What I mean is, before you type any other command, you must first type "su", press enter (when you do the $ should turn into a # or something), then proceed with the rest of the commands.
when I type su, it waits a second, then tells me permission denied I believe.
Can you post the set of instructions that you are following?
I was just able to get into recovery for some reason! It was the one I remember with orange text this time. (older version?) I wiped everything.... but had no ROM to flash. -_- trying something now.
After 2 days of trying to fix my phone, I give in, make an account and ask for help here. No more than 5 minutes later my phone is back to just how I want it for no reason at all. I am so utterly baffled right now. Thanks sweetnsour for being there . love this place
Simply get root (GingerBreak or Super One Click) , then install recovery with Rom Manager.
Sent from my LG-P500 using Tapatalk
mcnic05 said:
when I type su, it waits a second, then tells me permission denied I believe.
Click to expand...
Click to collapse
Are you root your phone? Use, depending your stockROM, z4root (2.2 and some 2.2.1), Gingerbread (2.2.1, 2.2.2) or SuperOneClick + Gingerbread exploit + some ADB commands (2.3.3)
When you rooted, you can flash customrecovery using commands or, in case of CWM, Clockworkmod apk.
mcnic05 said:
when I type su, it waits a second, then tells me permission denied I believe.
Click to expand...
Click to collapse
Because when you typed su , your phone will appear the super user permission , it only give you 9 seconds to allow the su...... But you just see the black screen
Need 10 posts to comment in developers forum. So I'll just thank everyone for their help! And say how much faster bobzhomes build is than others I've used. Love it.
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
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