[Q] RSDlite - can I cancel halfway to fastboot myself? - Moto X Q&A

I'm tring to use RSDlite from a virtualbox vm, but its going really, really slow. I'm some 40 minutes in and its only on step 6 - I don't think it will complete before the battery goes dead.
If I cancel it now and do all the fastboot flashing by hand through my host os, will I screw anything up?

vonwhoopass said:
I'm tring to use RSDlite from a virtualbox vm, but its going really, really slow. I'm some 40 minutes in and its only on step 6 - I don't think it will complete before the battery goes dead.
If I cancel it now and do all the fastboot flashing by hand through my host os, will I screw anything up?
Click to expand...
Click to collapse
its never safe to stop a flashing process. Depending on when you stop it you could royally screw your phone up. Certain files can get corrupted that won't allow you to enter fastboot mode anymore (im not aware of exactly which those are but i think there are many). It shouldn't take that long to flash your phone so im not sure what the problem is. If it has been stuck on the same step forever then maybe it has failed or something. You def don't want your phone battery to go dead because there may be no way to charge it again if there is no bootable rom on there. I believe fastboot may still allow your phone to charge but Im not sure if thats true. I know it didn't used to be able to but i think it may now. Personally, i would stop the rsdlite process before i let the phone battery drain. Then hopefully your phone will fully boot from there and i would charge it to 100% before trying to flash it again.

If my memory is correct then step 6 is the system.img file - the main OS of the phone. It is the big file that will not only take the longest but it is also the one that will fail the easiest as it is so big. On an older XP machine it takes 5 minutes or so to transfer/flash that file.
I have had the process hang during the transfer of the system.img file before. One time I had to reboot my computer and I rebooted the phone. This will leave the phone unable to boot but with enough key presses you can get into fastboot still - I don't recommend this!
When it happened a second time I only rebooted the computer, and not the phone. You can start the flashing process again without restarting the phone unless it has crashed. You should be able to manually flash with fastboot starting with the step that that failed.

I did some googling - it looks like VirtualBox has some problems with USB speed in Windows XP as a guest.
I ended up killing the RSD flash, and doing it by hand, which went way, way faster. I was able to flash the whole thing in the time it took to send the first 2 files, which only adds up to 1.7 meg.
For what its worth, I killed the flash during step 6, which is system, you are correct. I think this may have actually saved me since it had the boot and recovery images already.
edit: and it appears the phones do charge in fastboot. I had more charge when it rebooted after the successful flash than I started with.

Good to hear you got it working. And yes, the phone should (slowly) charge when in fastboot.

Related

Help! I need to get back to stock rom on droid bionic!

Dear Sir/Madam,
Before Spring Break, I rooted my droid bionic using motofail for windows. I do not know what the software version is, but I will include the software (motofail) in this email. On Thursday March 28, 2012 I decided to try installing ROMs to my Droid Bionic. I saw that Liberty Rom, Blurr3d Rom, and Eclipse Rom were cool roms. so first, I got Bootstrap (I will include it in this email) Bootstrap is a .apk file. I also got ROM manager, titanium backup, and one more, but i do not recall what it was. I made a backup of the stock ROM with ROM manager. and i installed bootstrap. little did i know that if something bad happens to the phone during a ROM install, you cannot restore a previous backup. So i cannot get my stock ROM back on. later on, before i had a problem with bootsrap i installed liberty ROM. then i got board with it then got blurr3d. then i got eclipse ROM. that's when i started to have problems. After i installed the eclipse ROM, noticed that i could not get any cell service or data service. I could get data from wifi though. So i freaked out and got liberty ROM. i read up on it and someone said i should get safestrap. Safestrap is like bootstrap but it is safer because you can access the recovery menu from boot and not have to access it through an application on the phone like with bootstrap. So after i got safestrap i installed it, rebooted it and made a back up. Before i made the backup i put plurr3d back on becasue i thought that the radio files from eclipse were not compatible with the radios on the bionic for some reason. This was all on Thursday. well, this time, it took 3-4 hours for blurr3d to get passed the welcome to andorid please touch the android to continue screen. on the screen it said, "please wait... this may take a few mins" after about 20 mins i got worried so I pulled the battery and rebooted the phone. and got back to the same screen. After i got back to the welcome to android screen, i had to go to football practice and dinner afterwards. when i got home, which was 3-4 hours later, I checked on the phone and it was past that screen and i was able to add my gmail account to it. For some reason or another, the cell and data services were not working. so i left it at that for a day or so and on Friday, I tried using what a lot of people are saying on the Internet which is, RSD lite. you can use RDS lite to flash a stock ROM onto the droid bionic. at that point, i thought that if i got the stock ROM back on, the radios would start working again. well, when I put the phone into fastboot mode it said,
AP Fastboot Flash Mode (S)
0A.61
Battery OK
OK to Program
Connect USB
DATA Cable
It also said the same thing when i connected the USB cable to the phone and the computer. RSD lite did not recognize the phone so i tried for a couple hours with the same result. Later on, I read that restarting the computer with the phone in AP Fastboot while the phone was plugged in would get the phone to say,
AP Fastboot Flash Mode (S)
0A.61
Battery OK
OK to Program
Transfer Mode:
USB Connected
This worked, but RSD lite still would not recognize the phone. So then i remembered that i had a stock ROM backup with bootstrap and i did. so i un-installed safestrap (one of the worst mistakes i made so far) and installed bootstrap. so i booted into recovery via bootstrap to restore to stock ROM. things did not go as planned... for some reason or another, it booted up normally. without going to recovery. then it wont to the dual core screen then the bionic eye screen with someone's ROM underneath it (it didn't say someones ROM but it said some one's name then the word ROM) then blurr3d ROM booted up and it kept crashing. so i ended up staying up to around 2-4 AM trying to fix that. i ended up saying forget this and going to sleep.
When i woke up in the morning, i looked at the phone and i had my data and my cell service back so i was confused so i started texting my friends and when i tried to go tot he home screen, nothing happens. but what i learned earlier is that when i reboot the phone, my data and cell service goes away for a couple of hours. So here i am now with my droid bionic, and cant do anything but text and call. i can only call when i get a text from someone, open up the text, and click on the phone number and click call when it brings me to the contact page for the number. I am also not able to access the home screen, the settings folder, or anything besides the notification bar. i really need my phone to use email, games, software (learning how to write java code), and for school in some instances. Any help would be greatly appreciated.
Thank you for your time,
NH85
Seems to me...you lost data along the way.
A possible reason rsdlite is not recognizing your phone might be because you dont have the proper moto drivers installed.
Try this rsdlite and install the correct drivers for your pc...http://dl.dropbox.com/u/63864500/rsd_drivers.zip
Make sure your battery does not die!
Boot into AP fasboot (power and down volume)
Use the cable that came with your phone.
See if rsdlite recognizes the phone.
If it does, you can flash the full 902 xml file (make sure your pc has 4g of RAM tho)
Do you have the full 902 xml file...if not, let me know.
Drivers
Dear Sir/Madam,
I have the correct drivers installed. When i connect the phone regulry once it is all booted up, i am able to access the sd card and the internal storage via windows explorer.The problem is that the phone refuses to connect to the computer in fastboot mode. i do not want to risk rebooting unless it is guaranteed to work 100% because I can still text and call on it for some reason. Every time the phone is restarted, the radios stop working for a while and i need to be able to text my parents where and when to pick me up from school.
Thank you for your time,
NH85
i notice that you didn't once mention a wipe data or otherwise cleaning of previous ROM before flashing another (correct me if im wrong). also DO NOT have bootstrap and safestrap installed at the same time, this could be what caused all your problems. in order to switch between the two (which i've had to do for webtop issue), you have to return to STOCK +root, uninstall the currently used strapper, reboot, then install the other. things start getting even hairier if you forget that safestrap has both a safe/non-safe system. you need to be doing the switch on the non-safe system if necessary.
the purpose of safe-strap isn't that it can boot to recovery, it's that it *creates a an isolated ROM installation while preserving your "safe" system in case things like everything your experiencing occur. from what i can tell, you did not change to safe system before flashing new ROMs, again correct me if im wrong. at any rate, a bit of advice for the future is follow directions to the dot, but before even attempting the install read through AT LEAST 3 or 4 pages of user feedback to see what the common issues or install goofs are!
that being said...
having your computer recognize the phone as storage device does not necessarily mean you have the right drivers installed, however it does mean that you probably have the right cable (this is important, bionic is finicky without the proper moto cable). you will know if you have the right drivers if you see in device manager Motorola ADB. when you plug your USB cable in, there should be an option for "PC Mode" which will force the computer to search for the drivers you claim to have installed correctly. if not found, here is your chance to install them properly and test RSD to make sure device is detected.
nh85 said:
Dear Sir/Madam,
I have the correct drivers installed. When i connect the phone regulry once it is all booted up, i am able to access the sd card and the internal storage via windows explorer.The problem is that the phone refuses to connect to the computer in fastboot mode. i do not want to risk rebooting unless it is guaranteed to work 100% because I can still text and call on it for some reason. Every time the phone is restarted, the radios stop working for a while and i need to be able to text my parents where and when to pick me up from school.
Thank you for your time,
NH85
Click to expand...
Click to collapse
Obviously you don't.
Mass storage and ADB are not the same drivers.
If you are in fastboot mode and your device doesn't connect, it's most likely your missing or don't have the fastboot drivers installed on your computer properly.
Once you get the ADB driver from motorola you can use fastboot start flashing.
The information you need is here
http://forum.xda-developers.com/showthread.php?p=22758211 .
I had trouble using RSD to flash the .902 FXZ.
What I had to do is extract the .img files from the ZIP, and use fastboot through CMD to get everything up and running.
Just open up the XML file inside the zip, it will show you the commands you need to type to flash each section and when to reboot the bootloader

[HELP] Battery too low for AP Fastboot.

This morning I flashed last nights CM12.1 Nightly. After it finished I hit reboot and let it do its thing for awhile, only to come back to a blank screen, I rebooted thinking I'd just hop into safestrap, flash a recovery, and be back to normal, but for God knows why, it wasn't letting me get into safestrap.
The next logical step was to run it through unbricking procedure which since RSDlite doesn't like me I have a batch file setup to run it through the manual commands which worked at first, but then I found myself sitting at the stock boot animation for an extended period of time. Not being sure of how long this normally takes because I haven't had to unbrick this phone in awhile, I just let it go.
Realized it was stuck, and decided I'd run through manually and see how that went. Went through the commands, got a couple errors for a low battery but just running the command again seemed to get it through, then I finished, told it to reboot, and then it went right ****ing back into AP Fastboot, saying that there was a boot failure and that cdrom and system weren't flashed correctly. No big deal right? So I go back to run the commands to flash them all again, and now the battery level has completely made me it's new *****.
I have no money to purchase a factory cable, but I feel that if given instructions I could handle it myself. I've seen that the RAZR has a way to get around the low battery level but it didn't seem to work on the Bionic. SO, if anyone has any words of advice, instructions, or methods they want me to try, any and all help would be greatly appreciated. :good:
I know this won't be helpful, but I ran into the same problem. The only solution I found was to use a different battery.
Keep searching around...i found a work-around, but I couldn't tell you exactly where. It involved using an extra usb cable, splicing, and 'straight wiring' the battery. It worked for me is all I can say.
Sent from my HTC6500LVW using Tapatalk
Luckily only cdrom and system didn't flash properly, simply by plugging the USB into AC power first was able to trick the phone into thinking the battery was fine. I was able to get those flashed and it booted just fine.

Fastboot.exe has stopped working - Phone Corrupt

Hello my lovely Nexus family,
I need your help! I've searched all over the web and these forums, and have yet to find a single thing that would help me.
After making a stupid mistake from tinkering, my phone was stuck on the "Google" screen. Not a big deal, just a simple wipe and fresh flash (and yeah, that's what I wanted anyways), right? So I went straight to Wugfresh's Nexus Root Toolkit to full wipe. It did the whole process of flashing MRA58R to the phone until I got to "sending sparse 'system'" on the terminal window. "Fastboot.exe has stopped working. Windows is finding a solution....." suddenly appeared while the terminal was processing everything. When the phone decided to reboot after thinking it had finished, it came back with the "Phone Corrupt" message.
I don't know what to do, as this is the 9,999th time I've flashed a phone, and I've never seen this before (obviously) so I'm not really sure what to do.
If I'm missing any details, which I feel I am, do not hesitate to ask.
May be obvious no... But you didn't actually say...
Will phone boot into fastboot if you have it powered off, the first pressing and holding volume down, then pressing and holding power until the phone boots?
scryan said:
May be obvious no... But you didn't actually say...
Will phone boot into fastboot if you have it powered off, the first pressing and holding volume down, then pressing and holding power until the phone boots?
Click to expand...
Click to collapse
Yes, I'm able to boot into fastboot with the phone powered off using the physical buttons. I'm also able to get working commands from the terminal.
Then what is the issue? Flash The image manually, re-install fastboot if needed... Or better yet download the image from google manually, check MD5, extract the main zip, as well as the update zip inside... using the fastboot that comes with it to flash all partitions?
One flash went wrong... So ok try again. And don't use the toolkit so you can actually follow whats going on (and because the only posts with troubles seem to be from people using toolkits)
scryan said:
Then what is the issue? Flash The image manually, re-install fastboot if needed... Or better yet download the image from google manually, check MD5, extract the main zip, as well as the update zip inside... using the fastboot that comes with it to flash all partitions?
One flash went wrong... So ok try again. And don't use the toolkit so you can actually follow whats going on (and because the only posts with troubles seem to be from people using toolkits)
Click to expand...
Click to collapse
I've done more than one flash today. My next will make 20 in the same hour with failed results. I'll try flashing the bits of the file manually and see how that works.
It could even be the computer I'm using. I'll report back soon.
Are you using the same fastboot.exe every time and getting the same error? Did you verify MD5
So, I got home, hopped on my laptop and got to work as usual. I used the factory provided cable and the problem was solved. I believe it has something to do with either the cord I was using to transfer the data, or the computer I was using.
Other than that - PROBLEM. SOLVED.
If the fastboot exe was fail ("stopped working") the cable was less likely the issue, most likely just the binary on that computer.
Perfect example of why not to use a tool kit until "after" you know how to do it manually.

Partition Map please?!

Long story short, I hard-bricked this thing to Hell. I'm in Download mode and have QFIL but I don't have a saved fstab so I can't flash the rom properly.
Someone wanna kindly post one, please??
Much obliged.
jake5253 said:
Long story short, I hard-bricked this thing to Hell. I'm in Download mode and have QFIL but I don't have a saved fstab so I can't flash the rom properly.
Someone wanna kindly post one, please??
Much obliged.
Click to expand...
Click to collapse
What firmware are you on?
kountry83 said:
What firmware are you on?
Click to expand...
Click to collapse
Heh. So, after a long day i neglected to plug my phone in to charge before the battery totally died and now it's stuck in a bootloop. This seems to be a somewhat common issue with this phone when it's been modded. Understandable but managable quirk. Usually I can just fastboot flash boot and it seems to resolve the problem, then I reboot-bootloader (after a successful boot) and re-flash my magisk_patched boot. For some reason, my stock boot image trick didn't work so I tried again, specifying boot_a and boot_b, just to make sure i hit the right slot. Still no luck. So I pulled out the heavy guns and ran flashall.bat (edited to NOT delete userdata). Being tired, annoyed, frustrated, in a hurry at 1:30AM, and tired of re-flashing this damn thing, I realized as it rebooted to a BLACK DEATH SCREEN that I really fu***d up and flashed MATA Q.032 update!
So currently it's boned.
But it automatially seems to be dropping itself into DOWNLOAD mode so I believe that means I should be able to use QFIL to restore partitions and upload at least enough partitions to get into a fastboot-able state and then run the correct flashall of the latest AURA CHERYL2.
jake5253 said:
Heh. So, after a long day i neglected to plug my phone in to charge before the battery totally died and now it's stuck in a bootloop. This seems to be a somewhat common issue with this phone when it's been modded. Understandable but managable quirk. Usually I can just fastboot flash boot and it seems to resolve the problem, then I reboot-bootloader (after a successful boot) and re-flash my magisk_patched boot. For some reason, my stock boot image trick didn't work so I tried again, specifying boot_a and boot_b, just to make sure i hit the right slot. Still no luck. So I pulled out the heavy guns and ran flashall.bat (edited to NOT delete userdata). Being tired, annoyed, frustrated, in a hurry at 1:30AM, and tired of re-flashing this damn thing, I realized as it rebooted to a BLACK DEATH SCREEN that I really fu***d up and flashed MATA Q.032 update!
So currently it's boned.
But it automatially seems to be dropping itself into DOWNLOAD mode so I believe that means I should be able to use QFIL to restore partitions and upload at least enough partitions to get into a fastboot-able state and then run the correct flashall of the latest AURA CHERYL2.
Click to expand...
Click to collapse
This struck a chord with me as I'm currently suffering from the same bootloop problem and I'm using the same fix kind of, except when it happens I use "fastboot restart recovery" from the bootloader and then flash a boot.img backup I have on my SD. My last phone was a MATA and I still have the images in my SDK directory, definetly going to clean it up now

Scared myself

I got myself stuck in fastboot. When i hold down the power button on the device it goes right back into fastboot. I cannot get the device to show up via adb devices to do a recovery flash. I'm not sure what to do next. The only thing i think im able to do at this point is to use miflash and use the stock fastboot image. Unfortunately, i am having a really hard time finding any download sources for it with a decent download speed. Meanwhile my phone is sitting at the fastboot screen and i cant seem to turn the device off so i am worried about the battery dying. i dunno if it charges on that screen. If someone has a faster mirror to the stock fastboot image, i would be grateful. I swear it seems like the official server has it out for me as the download speed seems to continually go down.. currently at 10 hour wait
Finally got the file and was able to flash it with miflash and im back to normal.. whew. why cant i delete my own post

Categories

Resources