Recently I swiched my laptop from XP to Ubuntu, and I love it. But the other day I screwed my phone up and obviously was no longer was able to use RSD lite, but I did download the root and recovery for linux. I tied several times to get my phone back to 6.12.173 but kept getting errors so I had to try something else. So I copyed all the .imgs in the "Files" portion which had been extracted and put them in my "Platform-tools" folder. Put the phone in fastboot. Brought up terminal and wrote all the images to the phone. Now it wasnt a full complete rewrite of everything. I still had my modified boot logo, but it did get the phone back to working. from there I took the ota to .181 and used the root and recovery for linux to root the phone and I was back in business and able to get my rom and tweaks back on the phone. Just thought that I'd put this out there incase someone else gets in the same bind I was in. Btw I got back to .173 faster this way than if I had used RSD.
Which/what tools are you using? adb and fastboot?
Refer to this topic:
http://forum.xda-developers.com/showthread.php?t=1453660
Thank you..
bahathir said:
Which/what tools are you using? adb and fastboot?
Refer to this topic:
http://forum.xda-developers.com/showthread.php?t=1453660
Thank you..
Click to expand...
Click to collapse
Yep. When the phone was in fastboot I typed "fastboot devices" into the terminal and it brought up the device id. Then I wrote the system, preinstall, radio, recovery, and emstorage .img. In the terminal it was "fastboot flash system system.img"
I should mention that I only needed to rewrite the system .img but since I was in there I figured I would rewrite them all I just wasnt worried about the .bin files so they were left out.
pacman377 said:
I should mention that I only needed to rewrite the system .img but since I was in there I figured I would rewrite them all I just wasnt worried about the .bin files so they were left out.
Click to expand...
Click to collapse
Since you are using GNU/Linux, in the thread, I made a simple scripts to parse the sbf's xml file, and produces correct fastboot's coomands to flash all the needed img/bins .
http://forum.xda-developers.com/showpost.php?p=22041585&postcount=44
Good luck.
bahathir said:
Since you are using GNU/Linux, in the thread, I made a simple scripts to parse the sbf's xml file, and produces correct fastboot's coomands to flash all the needed img/bins .
http://forum.xda-developers.com/showpost.php?p=22041585&postcount=44
Good luck.
Click to expand...
Click to collapse
Sweet I'll give it a shot.
Related
No matter what I do, I cannot get a single thing to flash anymore with CWM. I'm on the dark side rom, unlocked bootloader & rooted, 4.5.91, and using romracers 4.0.1.5 cwm recovery. I even tried tenfars and the one rom manager gives me, but the problem persisted. Is there any fix for this because it is getting VERY frustrating!
The only fix available would be to figure out what you've done. The CWM versions all work fine and don't require a fix. It's something at your end and with the information you've given, there's not much to go on.
It must corrupt the files when I transfer them from the computer to the phone. I've downloaded straight from the source and MANY other sources of the exact same rom/kernal/ect... and it all ends up not working. Is it better to download on the phone? Oh, missed one detail but I don't think it matters, I'm using a mac and when I download a file it auto unzipps, then I just re-compress it and throw it on the phone. Would that affect anything?
change ur cable... try different machine...
Same problem
I've encountered the same problem! I flashed darkside on my rooted AT&T Atrix, (unlocked bootlader, rooted). My friend borrowed my phone and saw the AT&T system update and installed it. the phone reboots and I couldn't move past that, then i got the little green android dude with the /!\ sign behind him. Tried factory resetting, restoring from backup, and even flashing over Gingerbread, but nothing worked! If you have found a fix, an answer would really be appreciated!
dcben09 said:
I've encountered the same problem! I flashed darkside on my rooted AT&T Atrix, (unlocked bootlader, rooted). My friend borrowed my phone and saw the AT&T system update and installed it. the phone reboots and I couldn't move past that, then i got the little green android dude with the /!\ sign behind him. Tried factory resetting, restoring from backup, and even flashing over Gingerbread, but nothing worked! If you have found a fix, an answer would really be appreciated!
Click to expand...
Click to collapse
Not the same problem! You tried to OTA on an unlocked bootloader.
CaelanT said:
Not the same problem! You tried to OTA on an unlocked bootloader.
Click to expand...
Click to collapse
Would you happen to know how I might go about fixing it?
Gfrt94yn said:
Oh, missed one detail but I don't think it matters, I'm using a mac and when I download a file it auto unzipps, then I just re-compress it and throw it on the phone. Would that affect anything?
Click to expand...
Click to collapse
That's probably your problem right there. Use a Windows machine to download to, put the zip file on your phone from Windows, do a FULL fastboot wipe, and try flashing the ROM. (Or download right to your phone).
Sorry, I don't use a mac, so can't help there. I can tell you that just zipping files without the correct compression settings will cause the flash to fail.
e.g. If using 7-Zip you need to set Archive format to "zip" and Compression level to "store" when creating flashable zip files or they won't work.
In any event, do a FULL fastboot wipe before flashing:
reboot to recovery
wipe dalvik
wipe cache
reboot to fastboot
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
fastboot reboot (to recovery)
flash ROM
There are a couple of scripts in the forums which are almost completely automated to do this.
Actually I figured this out forever ago (moved on to new phone), but I'll still help. Anyway download the file DIRECTLY to your phone, no computers!! Then place it on root of sd card (for convenience, you don't have to) and flash. Problem solved! if that doesn't work, the file is most likely corrupt or the way your phone downloaded it is outta wack. Hope this helped
Sent from my SAMSUNG-SGH-I727 using XDA App
Gfrt94yn said:
Actually I figured this out forever ago (moved on to new phone), but I'll still help. Anyway download the file DIRECTLY to your phone, no computers!! Then place it on root of sd card (for convenience, you don't have to) and flash. Problem solved! if that doesn't work, the file is most likely corrupt or the way your phone downloaded it is outta wack. Hope this helped
Sent from my SAMSUNG-SGH-I727 using XDA App
Click to expand...
Click to collapse
Please see my post right before your post. Your problem was downloading to a MAC and the files being unzipped. Then when you zipped them back up it was not done correctly. Computers are not the problem!
SOLVED, see post #6
I have been trying out the various roms for Atrix
I tried the same zip of Neutrino EE 2.9 that I used to flash that rom before (since it worked great!) This time I also flashed the gtalk and sync addons. I did the usual wiping of everything.
Now the phone bootloops at the moto logo, and when I try to boot back into TWRP, I get stuck at the TWRP splash screen.
My computer isn't recognizing the device on fastboot either. DANG!
can someone help me out?
=JKT= said:
I have been trying out the various roms for Atrix
I tried the same zip of Neutrino EE 2.9 that I used to flash that rom before (since it worked great!) This time I also flashed the gtalk and sync addons. I did the usual wiping of everything.
Now the phone bootloops at the moto logo, and when I try to boot back into TWRP, I get stuck at the TWRP splash screen.
My computer isn't recognizing the device on fastboot either. DANG!
can someone help me out?
Click to expand...
Click to collapse
okay, I just found out that I can access adb in the state that recovery is in.
Is it possible to reflash either the rom or the recovery from a shell in here? or would that be "bootstrapping" since I'm already in recovery?
perhaps I can adb push a backup to /system?
of course the ./adb reboot bootloader doesn't work
I'm using a mac and I've had trouble getting fastboot to recognize my device in the past...I think last time I just borrowed someone's pc to do it.
You could use what's left of the recovery to flash a fresh recovery. The same one or a different one, doesn't matter. That might make the recovery work properly.
Can't test it right now, but I think the process would go something like this (recovery means on the phone, computer means on the computer):
Code:
[I]recovery>[/I] mount /sdcard
[I]computer>[/I] adb push recovery.img /sdcard/
[I]recovery>[/I] flash_image recovery /sdcard/recovery.img
[I]recovery>[/I] umount /sdcard
[I]recovery>[/I] reboot recovery
Note once again that this is untested, it's straight from my head, so it might need adjustments.
ravilov said:
You could use what's left of the recovery to flash a fresh recovery. The same one or a different one, doesn't matter. That might make the recovery work properly.
Click to expand...
Click to collapse
thanks for the idea. I can't access any of the functions of the recovery. it's just a splash screen. ADB recognizes the device on my computer though. I can adb push files...I'm wondering if I can push something from a backup to my phone through adb. I guess I'd need to push the /system and /boot to it. I can't seem to get mmcblk0p12 to mount though...
edit: I didn't see the code you added.
I tried it and got this message:
error scanning partitionsfailed with error: -1
I can't seem to get any partitions to mount (ie mmcblk0p12 etc)
I'm nervous about totally borking recovery since it's my only access to the phone right now. I might have to borrow a pc to get fastboot to work.
=JKT= said:
I might have to borrow a pc to get fastboot to work.
Click to expand...
Click to collapse
Might be a good idea. Macs are clearly doomed on this.
(Yet another reason I dislike them. )
Internal partitions might be borked, that could be why you can't mount them. That's why I suggested you flash recovery via /sdcard (external sdcard). However, I agree trying to overwrite recovery in this unstable state is kinda risky. Functional fastboot would be much better.
[SOLVED]
ravilov said:
Might be a good idea. Macs are clearly doomed on this.
(Yet another reason I dislike them. )
Internal partitions might be borked, that could be why you can't mount them. That's why I suggested you flash recovery via /sdcard (external sdcard). However, I agree trying to overwrite recovery in this unstable state is kinda risky. Functional fastboot would be much better.
Click to expand...
Click to collapse
SOLVED!!
First I found out that if I type fastboot -i 0x22b8 before every command, they worked fine.
then I stumbled across moto-fastboot, which is apparently a special fastboot for moto devices.
I used that to flash a new recovery the standard way and it worked out just fine.
Thanks so much for your help, ravilov!!
No problem, glad you have it up and running again.
And yeah... I thought you knew about moto-fastboot already, it's a pretty well known thing around here? :dunno:
Either way, now at least you have a working fastboot on your own computer.
Might want to change the thread title to "SOLVED".
ravilov said:
No problem, glad you have it up and running again.
And yeah... I thought you knew about moto-fastboot already, it's a pretty well known thing around here? :dunno:
Either way, now at least you have a working fastboot on your own computer.
Might want to change the thread title to "SOLVED".
Click to expand...
Click to collapse
I've only had the Atrix for about a week. Still learning the ropes: coming from an HTC device, so I'm used to doing things a certain way and relearning some basics lol
Cheers!
Sent from my MB860 using xda app-developers app
Hello All,
I posted this on the post for Android Revolution and seem to have run out of interest. This was my post.
Hello,
I messed up and flashed the boot file before I installed the rom file in the internal storage. Now the phone wont boot at all. Can you help me fix this please.
I've tried to search for answers but cant find anything.
I can get into fastboot mode and into CMW mode. So I am able to enter sideload mode but cant get the phone to take the sideload.
I'm afraid I may have formatted the storage too.
Can anyone help me please?
Steve the noob.
Right now I am completely bricked. Tried everything, reinstalled SDK, tried sideloading in a couple of ways, stuck in bootloader or CMW. Try to load and sticks on white HTC page.
PLEASE HELP. I followed all of the directions except for loading the boot first.
Is there a factory reset like the old Oden system that could save me?
Can you get into fastboot?
If so you need to then flash the boot.img via fastboot.
Type fastboot flash (name of file).img in command prompt and you should be good to go!
which boot image?
Looks like you took the wrong version for your phone. You have an AT&T / Telus phone. You can not take an International ROM for your phone.
Only AT&T / TELUS ROMs will work on your phone.
I forgot, you can not bricked your phone since our HTC ONE X+ are S-ON, you just missed something to have it going.
stevespens said:
which boot image?
Click to expand...
Click to collapse
Which CWM are you on? Lloir or the other guys? VERIFY YOU HAVE THE PROPER RECOVERY INSTALLED. IF YOU ARE ON THE AT&T MODEL USE THE AT&T RECOVERY
You can run an RUU (verify proper carrier and model) while at the fastboot screen, or install TWRP and try to sideload using that from the SDK PLATFORM TOOLS FOLDER. You mentioned you have the SDK installed but I need to stress DO NOT USE THE TOOL KIT IT IS WORTHLESS. Make sure you have the official HTC drivers installed that come with HTC SYNC using generic drivers from the tool kit usually yields worthless resutls.
I cant get the rom on the phone. It's completely stuck in a boot loop. Only thing I can do is go into bootloader or CWM. I need to sideload a rom. But it wont let me.
stevespens said:
I cant get the rom on the phone. It's completely stuck in a boot loop. Only thing I can do is go into bootloader or CWM. I need to sideload a rom. But it wont let me.
Click to expand...
Click to collapse
I looked at your android revolution thread. STOP USING THE TOOL KIT. It is a POS.
Kraizk said:
I looked at your android revolution thread. STOP USING THE TOOL KIT. It is a POS.
Click to expand...
Click to collapse
OK. Gotcha. Thanks for the help.
Now what do I do? I am bricked.
stevespens said:
OK. Gotcha. Thanks for the help.
Now what do I do? I am bricked.
Click to expand...
Click to collapse
Read my previous post I gave you instructions. http://forum.xda-developers.com/showpost.php?p=39261003&postcount=5
OK...
Let's start with the correct Recovery for your phone, download link -> Click me!
N.B. -> Rename this file like this -> TWRP2recovery
Put this file in your platform-tools of SDK folder.
Put your phone in bootloader (fastboot USB)
Type this : fasboot devices (Enter... you should have your serial in return)
Then type : fastboot flash recovery TWRP2recovery.img (Enter)
Again type : fastboot erase cache (Enter)
Unplug your USB cable and hit Power button one time
Select Recovery
Hit Power button one time to reboot in Recovery
Try to sideload an ATT&T / TELUS ROM ONLY
Go for Elegancia AT&T/TELUS ROM for this time. (Choose one of your choice in the Download section here)
What are the results?
Well, thanks for all your efforts, but it's a lost cause. I tried the last posters suggestions and it wont let me flash the recovery at all. It's done. I have insurance so I'm just going to smash it and file a claim. I give up. I wont do that again.
Which error you have when you try to flash the recovery? Is your phone recognized at least when you are typing : adb devices ?
stevespens said:
Well, thanks for all your efforts, but it's a lost cause. I tried the last posters suggestions and it wont let me flash the recovery at all. It's done. I have insurance so I'm just going to smash it and file a claim. I give up. I wont do that again.
Click to expand...
Click to collapse
Have you tried just running the RUU? People say it takes a few times. Your phone is not bricked if you can get into fastboot.
Sent from my HTC One X+ using xda premium
thanks for coming back.
Lets give this a try.
Lucky Thirteen said:
Which error you have when you try to flash the recovery? Is your phone recognized at least when you are typing : adb devices ?
Click to expand...
Click to collapse
I got this when I typed "fastboot devices",,,
Then when I typed fastboot recovery to load the file, it showed this
just tried a dif file path and got this
Oh, by the way, my bootloader has been relocked. Can I fix this through bootloader?
First let's install your SDK folder correctly then you will see, it will work flawlessly.
Have a look at my screenshot, see how mine look simple compare to yours.... Yes, I have two devices plugged.
Install your SDK tool like it is explained in this thread.
The version numbers are different but the installation stay the same.
EDIT : What is your computer OS? I will point you to the good htc drivers.
I just got my Prime back from RMA. They fixed the unlocking issue and downgraded to ICS. Nvflash looks confusing but I'll give it a go now. What do I do after? Do I just flash TWRP 2.5 and then use the upgrade bootloader in the Hairybean thread? Then just flash androwookie 2.2?
I am pretty confused now. I can only find instructions for JB.
Thanks...
NVFlash problem
Following this: http://androidroot.mobi/t3_nvflash/
When I try the first step: fastboot -i 0x0b05 flash staging ebtblob.bin
I get signature mismatch on the Prime. And in the command window I get the *attached*.
Looks like I can't even use Nvflash. According to this video: http://www.youtube.com/watch?v=dghGX3NjJaE
sahilcc7 said:
Looks like I can't even use Nvflash. According to this video: http://www.youtube.com/watch?v=dghGX3NjJaE
Click to expand...
Click to collapse
Do not listen to that guy who replied on YouTube to you.
If you are on ICS on prime it is doable.
We never had the security update that stopped us doing it while on ICS. I think that only happened to the tf700.
If you are still on ICS on prime you should be fine.
Any idea why I get that error? I couldn't find out how to do it though Linux so I used windows. (Linux noob).
sahilcc7 said:
Any idea why I get that error? I couldn't find out how to do it though Linux so I used windows. (Linux noob).
Click to expand...
Click to collapse
I'm not really sure mate.
Make sure USB debugging is on in developer options.
I have attached the files I used when doing it in case my fastboot is different. I have 2 fastboot.exe's here and I think this is the one I used.
Everything should be in the folder in the zip to do the process so just open a command window in there and try it.
Also if you are using front usb ports on a computer try the back ones.
Ok I'll try that. Do I follow the instructions here? And do I need to be in fastboot?
http://androidroot.mobi/t3_nvflash/
sahilcc7 said:
Ok I'll try that. Do I follow the instructions here? And do I need to be in fastboot?
http://androidroot.mobi/t3_nvflash/
Click to expand...
Click to collapse
Yes, they are the instructions you need and yes you need to be in fastboot for the first part of the instructions. (These are all fastboot commands on your instructions.)
I get an error after pressing error on the computer:
AdbWinapi.dll is missing from your computer
Didn't get this when doing it from platform-tools in SDK.
Tried copying your files to the platform tools folder. It gave me the same error I had originally. Signature mismatch. It says 'sending stagging' OKAY. then it says 'writing stagging....' FAILED..
Is something wrong with my prime?
After doing more research, it appears that the 'failed remote invalid' error seems to be from something in the bootloader being corrupted. I also tried unlocking again using the app and get the unknown error ; is this normal? How can I completely reflash ICS on it using a microSD card? Or even upgrade it to JB and forget about NVFlash.. Maybe flashing TWRP 2.5 ICS could help?
I am really annoyed now that I can't manage to do anything with this tablet. Finally unlocked, now can't flash anything. ICS is really slow and I would like a fast custom JB rom on it.
EDIT: I tried Ubuntu and still get the same error. Looks like my bootloader is corrupted... how can I install JB/reflash ICS bootloader?
Kept trying but NVFlash wouldn't work.. Kinda the whole point of me asking them to downgrade to ICS - I'm guessing they did something wrong and maybe because JB was installed first, NVFlash didn't like it.
So I installed 4.1.1 via microSD and that worked. Now let's hope I can install TWRP and flash some Hairybean!
So I should not be doing this on so little sleep, obviously. I have a Verizon HTC Droid DNA, Moonshine S-off, TWRP, and I had CarbonROM on it, but I was having issues so after some fumbling around and trying different things, I was at a loss. So I wiped all data and formatted. Well, before this, for some damn reason, I think I turned USB Debug off. Now I can't get into Fastboot USB. Am I totally screwed? My PC won't communicate with the phone.
HELP!
Actually its difficult to be "totally screwed" you can always hold the power + volume down until the phone boots into HBoot. Once your in HBoot again fastboot should work if it doesn't then that generally a driver issue. Once your back in HBoot you can select fastboot and that will give you the option to boot back into recovery. Once you get into recovery again I would select sideload and flash the ROM using "adb sideload <rom name>" making sure your in the adb directory and so is the ROM. Hope this helps.
Yeah, I can still get into fastboot (just not fastboot usb) and recovery, but my PC and phone aren't talking when they were before I started screwing around.
Sent from my Nexus 7 - Carbon Rom
Kevin5377 said:
Yeah, I can still get into fastboot (just not fastboot usb) and recovery, but my PC and phone aren't talking when they were before I started screwing around.
Sent from my Nexus 7 - Carbon Rom
Click to expand...
Click to collapse
PC driver issue, go into device manager and load new driver
I'll take a look
Sent from my Nexus 7 - Carbon Rom
Yeah, I'm not even getting the Windows sound like I connected anything. Usually it'll tell you no drivers or unsuccessful installation or something!
Holy crap... well you were right... it was a driver issue. I reinstalled the HTC drivers and I got FASTBOOT USB now... thank goodness!
I feel like my brain isn't working. How do I now get my .zip on my device using fastboot so I can then get into recovery and flash it?
Nevermind... booted to recovery, used adb to push my .zip to device
Glad you got it figured out.
It's always fun to watch people talk to themselves. :laugh:
I think I did the exact as you. Tried to get fancy with things too early in the morning and ended up formatting data. I was wondering how you pushed the zip for the ROM onto your device using adb? I can get adb to discover my device as long as its in recovery but I'm not sure of the commands it takes to push a file like that onto your sdcard in order to reflash it in recovery.
Any help greatly appreciated.
trickster2369 said:
Glad you got it figured out.
It's always fun to watch people talk to themselves. :laugh:
Click to expand...
Click to collapse
Even more fun when they answer themselves
hawkstwelve said:
I think I did the exact as you. Tried to get fancy with things too early in the morning and ended up formatting data. I was wondering how you pushed the zip for the ROM onto your device using adb? I can get adb to discover my device as long as its in recovery but I'm not sure of the commands it takes to push a file like that onto your sdcard in order to reflash it in recovery.
Any help greatly appreciated.
Click to expand...
Click to collapse
First, make sure your .zip is in the same folder as your adb. Then in your cmd window, (assuming you're in the correct directory) type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends.
And yes, I know first hand how amusing it is, and somewhat gratifying watching someone figure it out on their own. I could not, however, have done it without you guys. I assumed since my phone was communicating not 10 minutes earlier with my PC, it wasn't a driver issue. But in the end, that's exactly what it was.
Kevin5377 said:
First, make sure your .zip is in the same folder as your adb. Then in your cmd window, (assuming you're in the correct directory) type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends.
And yes, I know first hand how amusing it is, and somewhat gratifying watching someone figure it out on their own. I could not, however, have done it without you guys. I assumed since my phone was communicating not 10 minutes earlier with my PC, it wasn't a driver issue. But in the end, that's exactly what it was.
Click to expand...
Click to collapse
Enjoy
Kevin5377 said:
First, make sure your .zip is in the same folder as your adb. Then in your cmd window, (assuming you're in the correct directory) type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends.
And yes, I know first hand how amusing it is, and somewhat gratifying watching someone figure it out on their own. I could not, however, have done it without you guys. I assumed since my phone was communicating not 10 minutes earlier with my PC, it wasn't a driver issue. But in the end, that's exactly what it was.
Click to expand...
Click to collapse
Thanks that worked! Back to loving viper.
I Have a similar problem
Kevin5377 said:
First, make sure your .zip is in the same folder as your adb. Then in your cmd window, (assuming you're in the correct directory) type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends.
And yes, I know first hand how amusing it is, and somewhat gratifying watching someone figure it out on their own. I could not, however, have done it without you guys. I assumed since my phone was communicating not 10 minutes earlier with my PC, it wasn't a driver issue. But in the end, that's exactly what it was.
Click to expand...
Click to collapse
Hey i'm new to this and i also formated my phone when installing a new rom i can still get into twrp and when i plug in the phone to the computer fastboot usb shows up and it makes the sound on the computer however when i type adb devices in the cmd its blank could someone please walk me through the adb stuff sorry for being a noob
I also have a OTG cable but i tried to plug in a 16GB FAT32 flash drive but twrp didnt recognize it. it says unable to mount
Thanks a bunch
Adb commands are done with the phone booted into recovery. Fastboot commands are done with the phone booted to, well, Fastboot.
Sent from my ViperDNA
Kevin5377 said:
Adb commands are done with the phone booted into recovery. Fastboot commands are done with the phone booted to, well, Fastboot.
Sent from my ViperDNA
Click to expand...
Click to collapse
Thanks a bunch but i plugged in a bunch of flash drives until one was recognized and then was able to restore my old ROM... WHEW