hi guys i flashed cg7 on to my milestone using open recovery, i then stupildly cleaned my sd card and lost open recovery. im now trying to put gapps on my phone but crnt install it as rsd keep failing to flash it fails straight away. so now i crnt update anything as it i crnt install vulnerable sbf cus rsd fails.please any help
It's quite possible that your sbf is too long of a file name and there's a programming bug in RSD that will not allow a certain length for your sbf.
http://androidforums.com/droid-all-...hing-process-0x7100-rsd-lite.html#post1274587
I used that link to flash my sbf properly and it helped. It's odd that that's what you need to do, but it seems to work
yea looked at that didnt work looked at error log and got this something to do with device id
Device API Error: 0xE003003F Command: ERASE
File: D:\test_dev_usb\flash\code\flashdll\ErasingOp.cpp
Device ID: 0
Have you tried re-downloading the sbf file? People are saying that sometimes they get errors like that from corrupted downloads.
Do you have a sd card reader or a common notebook or a different phone or whatever device that can mount a microsd card?
if so, put you micro sdcard there and extract there a new openrecovery update.zip and boot again in recovery.
Related
The title mostly sums it up, I have a Nexus One and unlocked the bootloader to install CM 6.0. I tried Amon's RA recovery image but kept getting file corrupted errors from the .zip files even after verifying the md5 checksums. I was able to get past that problem thanks to Fubaya in another thread pointing out that there are recovery images that allow you to ignore the checksums.
I have now been able to load ROMs from .zip off the SD card, but no matter which one I try (eViL's Sense, CM6, Kang-O-Rama or stock) or how many times I try it, I can't get it to load past the 'X' with the padlock screen at boot. It will sit there for about a minute, then reboot into recovery. I have wiped everything on the phone multiple times but no luck. It just sits there until I pop the battery out. Any idea's what could cause this problem? The recovery image does not show any errors and looks like it flashes successfully
the file corruption errors are a bit troubling.. have you tried re-installing the recovery before proceeding? perhaps the flashing itself is not being done correctly.
often times being stuck at the X can be fixed by wiping the dalvik-cache from recovery, but your problem might be deeper than that.
try putting on amonRA's recovery again and see if that makes a difference.
Uh yeah, you shouldn't be getting any checksum errors. Sounds like something isn't transferring correctly.
As I understand it as long as you have the recovery on there properly (you HAVE to install it correctly AND remove a few files if you're using the stock ROM otherwise it'll wind up at the stock recovery!) you'll "never" be able to brick your phone, with the exception of when flashing the radio apparently..
But flashing with corrupted files still doesn't seem like a great idea, so I'd figure out why this is happening. Can you pull the card out of the phone, put it in a card reader, and check the checksum with md5sum or whatever checksum the particular ROM used... md5 isn't very popular anymore, but it is fast and probably still used a lot for non-secure things, like verifying a transfer etc..
I've tried reflashing recovery multiple times and never seem to have a problem getting in there, either with Clockwork or with Amon. I also tried copying the .zip files back off of the SD card and re-checked the md5sum, it looks like the file is still unmodified so I have a hard time believing that it's corrupt. It does this with multiple SD cards as well, so I don't think its the card either.
I was able to get CM 6 to boot a couple times but the first time didn't seem to work right some error kept popping up that needed to be force closed over and over. So I reflashed and then was stuck in a boot loop with the CM logo. Since then, I have not been able to flash with anything.
Does this sound like some sort of hardware problem with the phone itself?
what radio are you running
4.06.00.12_7. I had Froyo running on here previously, and like I mentioned above, it booted into CM6 once but never came back after a second reboot. I tested and was able to make a call when it was running.
Flash the Recovery via ADB, not the SD card.
Do you still get checksum errors then?
I can't seem to get the phone to show up as an ADB device, I just get "device not found". After doing some reading, it looks like I did not enable USB debugging before flashing. Is there a way to enable this from recovery?
EDIT- Looks like the driver had uninstalled, I now have the driver back up and it shows up under ADB Device as being in recovery.
I copied the Kang-o-rama-1.0-Final.zip over via ADB and then tried to flash from SD Card from within Amon. It still shows E:Corrupt file: with a random file from within the zip as failing and then says verification failed.
Is it possible there is some sort of corruption elsewhere in the phone besides the SDCard that is causing these errors? It seems that whatever is causing the corrupt file errors (even though the .zip files pass the md5sum) is likely the root problem I am experiencing. Any ideas what else I could try to fix this?
Running 2.3.3, build number is CL 49208, using a Mac. Unlocked bootloader with fastboot. Used recovery-RA-passion-v2.2.1. Put the su-2.3.6.1 on my phone. Finally got it to reboot in recovery. Installed CM7.0.3. Oh, and I bought this phone in China (it's legit). Also, I used info from lots of sources before I finally found a recent post here that suggested the su zip file. One of those things I put in my sdcard is Radio_20100203_2_Signed_PASSION.img. Don't know if that helps. I couldn't find a more updated radio image.
The plan is to install CM7 so I can run openvpn.
It stops and cycles through the CM7 load screen -- turquoise android on a skateboard with an arrow circling around. Goes no further.
What did I miss? How do I fix it? Thanks.
Sounds like your in a bootloop.
Did you flash GAPPS also?
Here's more infos for radio, ect...
http://forum.xda-developers.com/showthread.php?t=744605
Has happened to me before. I removed the SD card and scanned it for errors on my PC. Worked after that. HTH.
Sent from my Nexus One using XDA App
Uhh...I can't put a microsd card in my computer -- I don't think.
Would you recommend updating the radio image? I'm thinking the 5.12.00.08, since my phone is in fact Korean. Do I still need the GAPPS image? Can I flash that image into my phone, or do I need to put it on the root of the sdcard?
cat3rpill3r said:
Uhh...I can't put a microsd card in my computer -- I don't think.
Would you recommend updating the radio image? I'm thinking the 5.12.00.08, since my phone is in fact Korean. Do I still need the GAPPS image? Can I flash that image into my phone, or do I need to put it on the root of the sdcard?
Click to expand...
Click to collapse
They make an adapter for micro sd card t ofit a USB port.
You can try new radio but If it's bootlooping I think your problem is elsewhere.
Did you check MD5SUM of the ROM before flashing?
Fortunately, my neighbor has a plethora of microsd adapters.
I did not check the sum. I read a few suggestions about doing that, but I couldn't figure out how, so I just trusted that what I had was fine. Lesson learned.
Let me get this straight: I need to put the GAPPS image on the sdcard AND flash the GAPPS image from fastboot? If I do update the radio image, do I need to reinstall CM7?
Put cm7 rom and gapps on sd card,
boot into recovery and flash rom then gapps, reboot.
Its highly recommends you do radio via fastboot.
To check md5sum, you can use one of the many free app from market.
Ok, ran checksum in fastboot. Not really sure what I'm looking for, so I'll just post what happened. In every case except gapps and su, the numbers returned were the same on the sdcard as in the tools file on my mac. Gapps and su are only on the sdcard.
For the CM7 zip, it returned: MD5(pathtofile)= 98d06d6a58c7de87d40269bfe0ae0e7b
For the RA img: 3def709ab1c9e051a92a1c8b1504a36a
For the Radio img: 310d85c4998163818f7dcdef730c2a12
For the gapps zip: 2f6a93654d1cfe191ff709b360ad60fc
For the su zip: b23147cb55eba3ae32a996a913fa54ea
I'm too new to the forum to post the link where I'm getting my instructions.
The CM7 version is update-cm-7.0.3-N1-signed, the RA is recovery-RA-passion-v2.2.1, the radio img is Radio_20100203_2_Signed_PASSION (the updated radio link you posted had removed the radio img because of some sort of violation), and gapps zip is gapps-passion-ERE36B-2-signed.
Still having the bootloop problem. I tried to find the most updated versions of everything I could. Is there a compatibility issue somewhere?
Another thought:
Do I need to flash the su zip from my sdcard in recovery? I don't know what that will do, so I haven't tried it yet.
There are a couple of files that Amon-RA suggests I delete in order to prevent calling the stock recovery:
/system/etc/install-recovery.sh
/system/recovery-from-boot.p
Any idea how I can check for and delete these using fastboot via mac terminal?
You can't delete them from fastboot. Use fastboot to boot off the new recovery and delete them in there through adb.
Code:
fastboot boot recovery "c:\location\to\recovery.img"
Can you be more specific? I use fastboot to flash the recovery image, and when I'm in recovery on the phone, I use adb from my computer? Or I can access a command line in the phone?
Well, you use fastboot to flash the recovery. Then you use the command I posted below so you can boot directly into that recovery. Once in there, you use adb on the computer to go into the phone, mount the system partition (which can be done under the mounts and storage menu in recovery) and then find those files and remove them.
But you really only need to delete those files if you want to stay running stock Android. If you have a custom recovery on the phone, that is all you need to install CM, and CM doesn't contain the files that revert the recovery back to stock.
Just got it to work. It was, in fact, a compatibility issue. The gapps zip was for a different version. I found a different zip (for Gingerbread) at: http://goo-inside.me/gapps. If you have Gingerbread, choose a zip with gb in the name.
I put the package on my SDcard and renamed it to update.pkg and then tryed to install it by the Software Update via update.pkg option in the recovery and then as it was going it suddenly says SDCard not enough space, I cleared up the SD and then put it in and then the next run it says FOTA Model Name Mismatch or something like that.
I'd like help, my build is 19534, I want to get it to the new 21700 build that would occur from updating...
Did you do the recovery.img using the "fastboot" method..?
I did the recovery.img as you said and then installed the package it went through
Thanks.
After flashing Cyoanogen 10, I powered the device off and when I powered it back on I got stuck at the Bootloader Unlocked screen. I read somewhere that I should try wiping /sdcard. Bad idea. So I try to use RSD to flash a stock rom from the development section but after I decompress the files and are about to flash I get the error message "Please check input file. Either XML format is wrong or image files associated with it are missing." I have no idea what to do at this point. Any help would be appreciated.
Have you tried this method http://forum.xda-developers.com/showthread.php?t=2231249
I see you said you tried a method from the development section so idk if you gave this one a try i did it yesterday and it flashed stock jb fine.
I will try this method. Thanks for the link. I will let you know how it goes.
Still got the same error...I wonder what the problem is?
EDIT: It actually won't even let me decompress it before the error pops up.
where is your the zip located that your trying to flash try putting it on your desktop then go back to rsd and decompress and flash that worked for me when i was getting a error.
Well the original file is in downloads but after removing the two lines with getvar it is now in my documents.
move the zip that you edited to your desktop and try that.
This time it decompressed but now when I start flashing it fails saying on the first slot "phone failed to switch to fastboot mode" and the second slot says "failed flashing process. Unknown fastboot command..."
EDIT: Well it says battery low now so we might have to wait a while. *sigh*
Dang dude i never ran into that error are you in fastboot mode when you try to flash?
Yep. I am definitely in fastboot.
EDIT: Ok when I try to flash the edited file that has the getvar lines removed I get the XML error. When I try to flash the original file the flash fails. For a split second before it says flash failed it says there was a fastboot error with getvar. But the one without getvar doesn't work...
try replacing the xml by dowloading the modified xml as it says in the post just drag modified xml to your zip and it should replace the old one.
So to replace the file just drag it into the zip folder? Never done this before lol
exactly it should replace it since they have the same name.
It says that the battery is low and I know that if it dies in the middle of flashing it can really screw things up. Its been charging from the outlet for a while but it still says that its low...is it even charging?
not sure btw have you tried reflashing cm10 if so what recovery are your using?
I'm using a Motorola Photon Q clockworkmod. I've seen various posts saying that it works fine with the Atrix HD. I have a thread called "Did I screw up?" (Terrible name for a thread I know) that explains how I got into this situation.
EDIT: No I haven't been able to reflash.
o just took a look at the thread now i see why you cant reflash im sorry dude i never been in a situation like this best of luck.:fingers-crossed:
You know why I can't reflash? I want to know how my phone died.
i meant reflash cm10 not the stock rom since you said you wiped out all of your data.
I just moved the modified file from the thread that you linked me to the zip and it said copying files for a second. Then I went back to rsd and selected the zip and it said "target directory exists. Replace?". I clicked ok then it starts to decompress then it says this new error message "Error!!!!!
Failed to create MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml
Please check if the file path is too long to create or if there is enough free disk space." I probably did something wrong...
I tried following this link to manually install 5.0 on my device. Using a youtube video (link of video is on the image) But came across this problem the problem where i cant flash the the zip file to the phone and an error comes up saying: E: Error executing updater binary in zip ' /sdcard/download/blur version ...... i kept trying but it wouldnt work. I also tried factory reseting it and deleting all the dalvik cache, it still came back with the same response. And i have a custom recovery (twrp recovery). So what do i do?? Help me <<NEED URGENTLY>>
try to flash the rom via fastboot, using the commands on 4.2 on this thread
You need a XML zip of the rom , to have the XML zip of yours rom search in here and download the file regards yours model and OS version that you wanna...
download is very slow, download, unzip, to the some folder of mfastboot and give the commands a try, while the phone is conected via USB to the PC, you must have motorola driver update, to know if you have the drivers, just plug the phone on normal on mode, and see if you can copy and past files to the phone...
If you follow this procedure you will erase everything on the phone, so do a backup...
Or find a TWRP backup of the OS you wanna and use it.