Database Develop

Reverting back to Stock(Stock recovery image/stock rom)

Ok i know a thread of this kind has probably been made a couple of times, and i apologize for this, but i have been searching every where to find a way to make my nexus one back to stock. I know once the bootloader is locked i cant reverse that but i just want to have the original stock recovery image. I currently have amonRA 1.7.0 recovery image. I have tried everything possible that i know, and as I must mention im not a really a good adb user. I mostly know how to use custom recovery images, load roms, themes, mods, etc. I have read a couple of threads where it would help me revert back original state but i just cant figure it out. I would very much appreciate it if someone would help me out and give me a step by step procedure i can use to flash a recovery image.
I currently have my nexus on ERD79 stock rom, no mods no nothing.
Firmware is 2.1(not 2.1update1)
thanks for the help!

http://forum.xda-developers.com/showthread.php?t=614850
this puts everything back to original even recovery img.. this is full instructions
and once its "unlocked" it cant be Relocked.. it stays unlocked
http://forum.xda-developers.com/showthread.php?t=614057
the PASSIMG
Step 2. unzip the original shipping ROM and put it somewhere you can find.
Step 3. Plug in Nexus One with USB to computer (enable usb and debug modes)
Step 12. Skip to step 13 if you want to keep recovery (assuming you have a modified recovery such as Amon_RA's recovery). If not
fastboot flash recovery recovery.img
Step 13. fastboot reboot

Thanks for this but i came across this thread and to be honest i got lost after it asked to put the unziped file where i can find it.
Can you give me an idea where i could put it?
Oh and i downloaded the passimg.zip and i couldnt extract it, my comp said file is invalid.
thanks again.

Ok ill see if i can unzip it for you sir
or you can try it this way too
http://www.mediafire.com/file/e5t4504thl2ry42/recovery.rar
there you go man recovery image from the thread posted before
1. Plug the phone into the computer
2. Reboot into fastboot by holding TrackBall + Power (you should see three Androids on skateboards and the words 'fastboot USB' in red)
3. On the computer, open a command prompt cd to the sdk/tools directory (we will assume the SDK is located in C:\android-sdk and the recovery file is in the root of the sdk/tools directory for the following steps)
4. With the phone connect via USB, open up a cmd prompt
Code:
adb reboot recovery"
5.
Code:
adb devices
A device name and 'recovery' should be returned
6.
Code:
adb push recovery.img /sdcard/recovery.img
recovery.img is located on android-sdk/tools dir
7.
Code:
adb shell flash_image recovery /sdcard/recovery.img
This permanently flashes the recovery.img to your phone, you can now boot into it by holding Vol- while powering on the device
8. Reboot
Click to expand...
Click to collapse

i apologise if this seems like a noob question, but i searched everywhere, and couldn't find the answer.
I followed the steps to flash the stock recovery to my nexus, and when i boot into the recovery mode to test it, it's just a blank screen with an error triangle and a little android standing next to it.
Is this what the stock recovery is meant to be? or did something go wrong in the process?

Yeah that should be the stock recovery, you should be able to press the power button and volume up and get a blue text list saying reboot system now, apply sdcard:update.zip.... etc.

yes, thank you very much for clearing that up for me

see my guide: [UNROOT] Unroot al android devices which was also posted on the front page. this step allows you to get a stock recover image specifically for YOUR GOOGLE NEXUS PHONE, not just generic google nexus phones

hate to revive a thread thread but im having the same delima.
i just bought a nexus one from CL and it was loaded up with a 2.3 rom. Im guessing its not using stock kernals, baseband, etc etc.
Im trying to get it back to stock EVERYTHING. i know i cant relock the bootloader but other than that, i want to revert it back to what you get right when you open the box. im not even sure what a recovery image is... but if its different when u flash different roms, i would like that stock too lol.
i know about the passingimg method but i wasn't sure if thats compatible with all roms (kind of like how unlocking iphones only works with certain basebands). i also wasn't sure if that'll return everything to stock, kernal, OS, modem, radio, recovery (?), etc.
im not very familiar with adb either. can anyone PLEASE help me out?
this is the method im talking about http://forum.xda-developers.com/wik...des_&_Tutorials#Unroot_.2F_Restore_your_Nexus
would the passingimg get EVERYTHING back to stock? or would it leave the custom recovery, kernal, or something else etc.

[Q] Bricked Phone

Hi,
I recently got asked by a friend to flash his google nexus one phone. like a mug i said yes and now i have a issue where it turns on, vibrates 7 times and stays at the splash screen with the x on it. I can boot into the fast boot / recovery mode but nothing works.
this happened after i tried to root the phone, it said waiting for device and didnt do anything so i killed the app (Superoneclick) the phone disappeared from device manager and now wont go past the splash screen.
Does anyone have any idea how i can get it back? .. thanks in advance for any help.
James

I'm guessing, since you used S-O-C, the bootloader is not unlocked. The only way I know how to fix it is if you OEM unlock it. You'll need fastboot and your Android SDK setup correctly.
Once you have the setup done, change directories to the tools folder, wherever you put your sdk. Boot your phone into fastboot by holding the trackball while powering it on.
Code:
cd C:\asdk\tools\
Plug your phone into USB, and check if the computer sees it
Code:
fastboot devices
Unlock the bootloader (THERE IS NO GOING BACK! You can never re-lock a Nexus)
Code:
fastboot oem unlock
Now you can flash a boot.img and system.img (preferably pre-rooted) from fastboot, and it should boot normally. If the phone boots, the phone is perma-rooted, and won't need any other rooting procedure (you just need to flash a rooted rom). Next time, be a little more careful

Hi wdfowty
at running the risk of asking for more help and making you cross could you post some links to these downloads?
I am a total newbie to these phones and want to make sure i have the right apps.
thanks again for the help and the quick response... and if i manage to get this phone back believe me it will be the last one i try to flash !!
cheers
James

Nah, you've got me wrong. I'm all about helping people that are willing and able to be helped.
Follow this guide, it'll walk you through the steps to set up your sdk and unlock the bootloader. The guide is a little dated, so the info might not be 100%, but it's generally everything you'll need to know. If you get stuck, feel free to ask.

Hi again,
when i run the command fastboot devices i get an error AdbWinApi.dll is missing.
it tells me to reinstall the app but i have done that and also run all the updates and i still get the same error?
Interstingly i also get the phone to fastboot and it says in red text on the phone fastboot.usb but i cant see anything in device manager that says Nexus one etc?
any more help appreciated.... worst case you dont fancy a christmas break over in England do you?
cheers
james

jamesabennett said:
Hi again,
when i run the command fastboot devices i get an error AdbWinApi.dll is missing.
it tells me to reinstall the app but i have done that and also run all the updates and i still get the same error?
Interstingly i also get the phone to fastboot and it says in red text on the phone fastboot.usb but i cant see anything in device manager that says Nexus one etc?
any more help appreciated.... worst case you dont fancy a christmas break over in England do you?
cheers
james
Click to expand...
Click to collapse
With the latest version of the SDK tools, they changed the directory for adb and fastboot. Unfortunately I'm not on my Windows machine... but check in the directory where you have the SDK extracted to and look for a platform-tools directory (iirc). From there, you should see fastboot.
So basically where it says this "Type: cd C:\android-sdk-windows\tools" change it to "C:\android-sdk-windows\platform-tools". Keep in mind that directory name may change... again, I'm not on my Windows machine right now.

Hi again,
thanks for the continued help. I have managed to get past that, i have OEM unlocked the phone and managed to copy the flash image to the device using the commands in the link you sent me.
problem i have now is when i go into recovery the phone again just pulls up the splash screen and vibrates 7 times.
i believe what should happen according to the link is to follow the 6 steps below.. even i can do that, but the phone doesnt get that far
//Turn phone off -> Hold Volume Down, hold Power button
//Press Volume Down to highlight Recovery -> press Power to select Recovery
//Backup/Restore -> Nand backup
//Wipe -> Wipe data/factory reset
//Wipe -> Dalvik Cache
//Flash zip from sdcard -> alpha-r##-update-modacocustomrom-nexusone-desire-withadditions-signed.zip (Or whatever other ROM you're using.)
another point is it runs a couple of lines of blue txt relating to the sd card, but it flashes up and dissapears too quickly for me to be able to read it and send across to you.
thanks again and if you can work this out i owe you a beer !!
James

jamesabennett said:
Hi again,
thanks for the continued help. I have managed to get past that, i have OEM unlocked the phone and managed to copy the flash image to the device using the commands in the link you sent me.
problem i have now is when i go into recovery the phone again just pulls up the splash screen and vibrates 7 times.
i believe what should happen according to the link is to follow the 6 steps below.. even i can do that, but the phone doesnt get that far
//Turn phone off -> Hold Volume Down, hold Power button
//Press Volume Down to highlight Recovery -> press Power to select Recovery
//Backup/Restore -> Nand backup
//Wipe -> Wipe data/factory reset
//Wipe -> Dalvik Cache
//Flash zip from sdcard -> alpha-r##-update-modacocustomrom-nexusone-desire-withadditions-signed.zip (Or whatever other ROM you're using.)
another point is it runs a couple of lines of blue txt relating to the sd card, but it flashes up and dissapears too quickly for me to be able to read it and send across to you.
thanks again and if you can work this out i owe you a beer !!
James
Click to expand...
Click to collapse
Have you flashed the recovery image using fastboot, or did you only copy the recover image to the sdcard? Step IV in that guide.

It sounds like you need to reinstall your recovery.
Download the recovery found here: http://forum.xda-developers.com/showthread.php?t=611829
Rename that file to recovery.img and place it somewhere you can remember
Boot the phone into fastboot by holding down the trackball and pressing power button.
Code:
fastboot devices
Code:
fastboot flash recovery C:\path\to\recovery.img
If all went well, there should be no errors. On the phone, use the volume keys to select "Bootloader". It will take you to a white screen with the blue text (ignore it, it's looking for update files like "PASSIMG.zip"). Select recovery, and it'll boot into recovery. If you see menu items, you are good!

I ran the fastboot command and used the flash image ending 2.0.0
this is driving me round the bend !!

What happened when you used the fastboot flash command? Did you see a bar on the top right of the phone?

wdfowty said:
It sounds like you need to reinstall your recovery.
Download the recovery found here: http://forum.xda-developers.com/showthread.php?t=611829
Rename that file to recovery.img and place it somewhere you can remember
Boot the phone into fastboot by holding down the trackball and pressing power button.
Code:
fastboot devices
Code:
fastboot flash recovery C:\path\to\recovery.img
If all went well, there should be no errors. On the phone, use the volume keys to select "Bootloader". It will take you to a white screen with the blue text (ignore it, it's looking for update files like "PASSIMG.zip"). Select recovery, and it'll boot into recovery. If you see menu items, you are good!
Click to expand...
Click to collapse
i do that and it accepts the recovery file and the progress bar goes up on the right hand side and the cmd prompt says its all good. then when i select recovery the phone goes to the black background with the four coloured cross and the unlocked padlock, vibrates 7 times and just hangs on that screen
beleive it or not it booted up a moment ago and the phone worked like it did before with v2.2 on it. so i am happy now it can be recovered... i just dont know what to do to straighten it out!

yes. the bar goes up on the right hand side of the phone. and i have definitely unlocked it as it now says unlocked at the top of the menu.

Have you tried to reimage the phone with the passimg method? Directions are provided in the wiki, under the unlock/restore heading:
http://forum.xda-developers.com/wik...des_&_Tutorials#Unroot_.2F_Restore_your_Nexus
Follow PASSIMG method (filename is case sensitive).
The link to the files is on the word "here" on step 2.
Use FRG33.
Sent from my Nexus One using XDA App

[stock rom][3.0.1] P7100BUKDF + bootloader unlock

Just received my Tab, and minutes before somebody gave me this update, which is indeed newer than the KD9 I had.
ODIN download mode
- Turn your device off and unplug it
- Wait 30 seconds (screen off doesn't mean the device has finished turning off)
- Press-and-hold the power button and very shortly after (0.5 seconds, but not simultaneously) press-and-hold the left volume button
- Release the buttons as soon as you see something on screen. You should be looking at a USB icon and a digging Android.
- Make sure the digging Android is flashing. If the USB icon is flashing, press the left volume button to switch to the Android.
- Press the right volume button to select and enter download mode
Bootloader unlock
Flashing this firmware will also unlock the bootloader.
Included languages
Deutsch
English (UK)
English (US)
Espanol
Italiano
Nederlands
Portugues
Instructions (Windows)
- Download and extract the attached Odin zip file
- Download and extract the ROM (you should end up with three .tar.md5 files)
- Go into bootloader mode, as described above
- Start Odin
- Look at the attached Odin screenshot, make sure of the following:
--- Re-Partition: NOT checked
--- Auto Reboot: checked
--- F. Reset Time: checked
--- Flash Lock: NOT checked
--- Phone EFS clear: NOT checked
--- Phone Bootloader Update: NOT checked
- Press the big BOOTLOADER button on the right and select the "BOOTLOADER_P7100BUKC8.tar.md5" file
- Press the big PDA button on the right and select the "PDA_SIGNED_HRI83_BUKDF.tar.md5" file
- Press the big PHONE button on the right and select the "MODEM_HRI83_BUKDF_REV_03.tar.md5" file
- Connect your device with the USB cable
- Wait a few seconds, Odin should say it is now connected
- Hit the Start button, and wait until the device boots
- Press the Thanks button below this post and/or donate
Random notes
"adb reboot recovery", "adb reboot download" and "adb reboot bootloader" now appear to be working, they weren't on the KD9 ROM my device came with.
Download
Here is the link: http://www.multiupload.com/LWN6RHF8WJ
NOTICE: FLASHING ALSO WIPES YOUR SD-CARD !

Chainfire said:
Just received my Tab, and minutes before somebody gave me this update, which is indeed newer than the KD9 I had.
Click to expand...
Click to collapse
Nice gift!
My bootloader was locked before this update, and I did not attempt to unlock it. Download mode tells me the OEM lock is now unlocked. Please confirm! (I may be a dumbass )
Click to expand...
Click to collapse
Do you see the open padlock on the boot logo screen?

bcmobile said:
Nice gift!
Do you see the open padlock on the boot logo screen?
Click to expand...
Click to collapse
Yes. I don't think it used to on the old firmware. What is the verdict ?
EDIT: Misread. I do see a padlock, but it is locked !

Just noticed... "adb reboot recovery" and "adb reboot download" now work. They didn't work on the KD9 ROM the device came with.

Chainfire said:
Just noticed... "adb reboot recovery" and "adb reboot download" now work. They didn't work on the KD9 ROM the device came with.
Click to expand...
Click to collapse
Yay! They do work if you do a adb reboot from the shell, but anyway, that's history now.
If you see the open padlock, you're in business. Im guessing that ROM was not meant for general public... in fact, if it came from where I think it came from, it wasn't
EDIT: So it has the stock recovery menu as well? Can you possibly do a system/boot/recovery dump to save us the pain of Odin?
EDIT2:
Chainfire said:
Yes. I don't think it used to on the old firmware. What is the verdict ?
EDIT: Misread. I do see a padlock, but it is locked !
Click to expand...
Click to collapse
fastboot oem unlock
I love Samsung... now

No Chinese at all, what a pity......
is it android 3.0.1 or android 3.1?

My device (bought in a vodafone ita store) has P7100BUKDF ROM and was already unlocked.

Myeah I was able to flash root after flashing this firmware, so it does unlock, it appears.
EDIT: Someone on twitter confirmed this unlocked the bootloader for him as well.

Thanks, good to have you on board ;-)
Maybe you should mention that this wipes the ENTIRE device, so including the SD-Card (The internal one)
Edit: Seems like I've lost root..
(Duh.. Title: Stock Rom..)
Edit 2: Reboot Recovery results in a Andy and an Exlamation mark
Rooted it with the fastboot method

gjroeleveld said:
Thanks, good to have you on board ;-)
Maybe you should mention that this wipes the ENTIRE device, so including the SD-Card (The internal one)
Edit: Seems like I've lost root..
(Duh.. Title: Stock Rom..)
Edit 2: Reboot Recovery results in a Andy and an Exlamation mark
Rooted it with the fastboot method
Click to expand...
Click to collapse
If you press enough buttons the menu appears in recovery

Added the SD-CARD wipe notice for ya

How do root this firmware ?
Thanks

http://forum.xda-developers.com/showthread.php?t=1079781 ?

any one know the difference between this one and stock rom? would be interesting to see if samsung changed anything.

Has anyone tried flashing with Heimdall in Linux?

As for the question about the difference with the original ROM I can tell that as mentioned in the first post more languages are supported.
The rest seems about the same as the previous rom.

Yes, it's also the only change I noticed from the stock room, but in my case is great since now it supports Portuguese (my native language).

I just unlocked my bootloader following your steps. It shows unlocked when booting back up but now it is not recognized by my pc when connecting through usb. I tried rebooting both pc and tablet. I also tried uninstalling the drivers from Samsung and reinstalling it but still no go. I have a Galaxy Tab 10.1v from Google I/O and the usb is gone. I cannot even charge from usb now. Are the files posted the correct ones for this device because it is not working. Does anyone have the correct ones? Any help would be appreciated.

The Google I/O Tab as far as I know is not a 10.1v, thus you shouldn't be using these files on it!

Yeah I figured that out now. I was following the root guide and I thought I was supposed to use this. Everything seems to work but the usb. But I can still connect to Odin and reflash. Is there anyway to get it back?

[Q] Dell S10 Pro - Need help in Updating

Hi,
Sorry for posting in this as I couldnt find any thread for S10.
I have a S10 Pro with the following version of ROM installed.
Android 3.2
Build Version : 201107271412 (This is a strange as I couldnt find this in any other....)
Kernel Verrsion : 2.6.36.3-00055-gdb0a63d
Is it possible to update it to 569 or any custom ROM?
Thanks and Regards,
manakun

Well you listed everything but the actual useful version info: what is the oem version?
Do you understand how to use nvflash?
As you're the first one with that rom: there's no way to restore to it after you flash something over it, I'd recommend making a backup of it.
It might be possible to update to 568/9 with the 546 recovery, if you are willing to make a backup of your rom i'll give you the instructions to update.
You'll need nvflash regardless though, I dont know offhand if <whatver rom version you have>'s rec will allow you to update even.

TheManii said:
Well you listed everything but the actual useful version info: what is the oem version?
Do you understand how to use nvflash?
As you're the first one with that rom: there's no way to restore to it after you flash something over it, I'd recommend making a backup of it.
It might be possible to update to 568/9 with the 546 recovery, if you are willing to make a backup of your rom i'll give you the instructions to update.
You'll need nvflash regardless though, I dont know offhand if <whatver rom version you have>'s rec will allow you to update even.
Click to expand...
Click to collapse
Thanks for you prompt reply.
The OEM Version is GALLO1A155111
I havent used nvFlash but I shouldnt have problem using it. Will make a backup. I dont mind if it cannot be restored.
Awaiting your instructions.
Thanks,
manakun

I am yet to update S10.
Help appreciated.

Things you'll need to know:
How to use the command line
How to install drivers on windows
Windows vista or newer
Download usbNvidiaBootdriver.zip
Download NVflash.zip
Download 568 bootloader.bin
Put Device into APX mode
Hold down power and reset button
Install apx driver
Extract nvflash
Boot device into APX mode
Command to do so: "nvflash --bl <path to bootloader.bin> --go"
<path to bootloader.bin> is whereever you saved bootloader.bin to
Begin dumping each partition
Command to do so: "nvflash -r --read <N> <filename>"
<N>: number of partition to dump
Partition List - XDA wiki
Partitions we need to dump 551: 2, 3, 4, 6, 7, 8, 11
Filename is whatever you wish to name file, recommended to name them after their partition number, eg p2, p3, p4, etc
After you have it dumped please 7zip and upload somewhere
Updating to a different rom uses similar steps if you cannot use "check for updates" from inside rom
If you do not know how to use the command line, there are tutorials on the internet.
If you are using a x64 version of windows, you will need to put your device in "test signing mode" or "disable driver signature verification mode", there are also instructions on the internet.

Thanks for your prompt reply.
However I am not able to put the device into APX mode.
I tried pressing and holding the Power Btn and Reset button simultanouesly(near the sdcard slot) but the DELL logo doesnot appear.
Is my procedure wrong?
Sorry for a dumb question.

manakun said:
Thanks for your prompt reply.
However I am not able to put the device into APX mode.
I tried pressing and holding the Power Btn and Reset button simultanouesly(near the sdcard slot) but the DELL logo doesnot appear.
Is my procedure wrong?
Sorry for a dumb question.
Click to expand...
Click to collapse
Yes, try readimg here: http://forum.xda-developers.com/wiki/Dell_Streak_7/Flashing_Guide
Woops! This is for a S10 not S7!

the dell logo is not supposed to appear in apx mode, it will simply be a black screen and detected as in apx mode when connected to windows.
once you boot into apx mode will the dell logo appear

TheManii said:
the dell logo is not supposed to appear in apx mode, it will simply be a black screen and detected as in apx mode when connected to windows.
once you boot into apx mode will the dell logo appear
Click to expand...
Click to collapse
Thank you. I have entered into APX and able to get the content of the partition.
I have sent the uploaded link in PM.
I would appreciate if you guide me in flashing the official PKG.

Thank you for uploading it, I assume you have attempted to directly update to 568/9?
Since you have made a backup of your rom I would recommend simply trying downloading the 569 update pkg and updating from it.
Download 569 pkg from xda wiki
Put pkg on external sdcard
Go into recovery mode
Reset device with reset pin (required)
Hold down power and volume up until you enter recovery mode (may take multiple attempts)
"flash update pkg from sdcard" (i forget exact wording, but it should be obvious from list)
select pkg and follow onscreen instructions
If that doesnt work I'll upload the 546 recovery, I dont fully understand the S10 update process (the part where it decides if the pkg is a valid upgrade, it's very selective about upgrades).
Since you've been able to use apx mode and understand how it wont be any more difficult then what you've already done.
I havnt had internet since monday because of hurricane sandy, so I cant upload everything right away.
------------------------------
Are you positive the last 2 digits of the rom version is '11'?
This is the first time i've heard of an S10 rom not being 15 (ie mainland china), 11 is for hong kong devices.
Could I ask for details on where you got this device and when? If you're not comfortable with saying it in public you can pm me.

TheManii said:
Thank you for uploading it, I assume you have attempted to directly update to 568/9?
Since you have made a backup of your rom I would recommend simply trying downloading the 569 update pkg and updating from it.
Download 569 pkg from xda wiki
Put pkg on external sdcard
Go into recovery mode
Reset device with reset pin (required)
Hold down power and volume up until you enter recovery mode (may take multiple attempts)
"flash update pkg from sdcard" (i forget exact wording, but it should be obvious from list)
select pkg and follow onscreen instructions
If that doesnt work I'll upload the 546 recovery, I dont fully understand the S10 update process (the part where it decides if the pkg is a valid upgrade, it's very selective about upgrades).
Since you've been able to use apx mode and understand how it wont be any more difficult then what you've already done.
I havnt had internet since monday because of hurricane sandy, so I cant upload everything right away.
------------------------------
Are you positive the last 2 digits of the rom version is '11'?
This is the first time i've heard of an S10 rom not being 15 (ie mainland china), 11 is for hong kong devices.
Could I ask for details on where you got this device and when? If you're not comfortable with saying it in public you can pm me.
Click to expand...
Click to collapse
Thanks for the instructions. However I was not able to enter into recovery mode. Tried couple of times.
Advice appreciated.
BTW, is it possible to flash all the partitions manually using nvflash?

I assume you have a working recovery, you may need to be make sure the battery has enough charge.
I'm not positive, but the S10 might be like the S7 wherein it wont go into recovery mode if the battery is below 60%. Even if it is charged entering recovery takes multiple tries even if you're doing it correctly.
If you can boot into android, you can simply use adb.
Enable "android adb debugging" from settings, install the adb drivers (fastboot+adb.zip from the dev subforum) and do "adb reboot recovery" from the command line.
Adb.exe is included in the mentioned zip.
Then try again, if the recovery does not want to do a pkg update, i'll upload the 568 recovery and we can try after flashing that.
If that still doesnt work I'll keep providing more files until it does, i would like to avoid having the user (ie anyone else attempting to repeat this in the future) do a full flash.
I would strongly prefer figuring out the minimum steps needed to force update a S10, as fullflashes did far more damage then they helped for the S7 due to someone providing a fullflash including their device specific data and nuking dozens of devices that way.
Just as much I'm not sure you can flash bootloader.bin from nvflash on the S10, i've attempted it and it didnt stick. It could be user error and fastboot may be able to flash it, the rest should either be flashable or not relevent.
If it were not for the bootloader, I could simply provide 569 as an update.zip flashable with CWM/S10, but I dont know offhand if the 551 bootloader is compatable with 569 as it's android 3.1 vs 3.2.

I was able to reboot to recovery from adb.
I get "Version check not allow update" error when I try to update from 568/9 pkg file.
Is it possible for you send me the 568 recovery img? And would appreciate on guiding me on how to flash using nvflash.
BTW, The 551 I have is Android 3.2.

i will upload the 568/9 recs, if that still doesnt work ill upload 569 as an update zip and you can flash with cwm
edit:
568
bootloader.bin
recovery.img
569
bootloader.bin
recovery.img
to flash a recovery (or any file in general)
boot into apx mode
nvflash -r --download <N> <filename>
<N> is the partition number
<filename> is the path to the file being flashed
flash the 568 rec and try using the 569 rec, you can attempt to flash the bootloader if you wish.
Keep in mind that flashing the bl is seperate from using it to boot in step 1, that step only loads it into memory and is lost on reboot.
the partition numbers are in the wiki.
if none of these work i'll provide more files until it does

Thanks for the upload.
Didn't have any luck with 568/9 recovery.
Strange behaviour with S10...still getting the Version mismatch Error...
I have flashed Clockwork Mod 6.0.1.2 . Would really appreciate if you could upload the update.zip.
It should work with CWM(hopefully). Worst case scenario..should try manually flashing the required partitions.

I'll upload 569 as an update.zip, it wont help you for new released roms in the future, but who knows when dell will release another update.

Thank you. Thats alright. But I guess Dell wont be releasing another update for S10.

update-S10-Stock-569-1.zip
I do not have the original update script, though I believe I have a close approximation.
If there's any issue installing it let me know, you'll need either CWM or TWRP to install it, install those in the same manner as the stock recovery. Links are in the dev subforum, make sure you grab the S10 ones and not the S7 ones.

Thanks for the upload.
I have installed the CWM and flashed the zip as specified in the following link.
http://forum.xda-developers.com/showthread.php?t=1780133
However, the system doesnot load after the flash.
I get the Dell Logo and it doesnot boot.
Would appreciate your support.

Try these in order until something works:
Did you try fac resetting from CWM?
If that doesnt work, try flashing the 569 bootloader.bin again.
If that still doesnt work try flashing CM9mod (and fac resetting) (to see if anything boots)
If it still doesnt work after those, I'll upload an nvflash dump as a last resort
How far does the bootlogo go? Does it blink once? Does it go to the animated swirl?
Initial dell logo: cpu works
1st blink, to dell logo: kernel is loading
Animated swirl: android userland is loading

Boot Loop When Flashing ROMs

Hey guys I'm not exactly experienced with troubleshooting these kinds of problems. Hopefully I can learn something with the help of the community. I'll go ahead and lay out the situation and problem.
Problem:
Whenever I flash a rom with CWM, the phone will either A: Get stuck on a blank screen with the green LED on or B: Go through the boot animation and crash on "preparing android" and loop the process.
Info:
My AT&T Atrix HD has an unlocked bootloader, I have had several successful flashes in the past, and they have all worked well. I am able to flash the stock firmware back to the phone and it will load just fine. I have tried to go back to stock and start over, but I keep getting the same result. I've tried multiple roms with no change. This started happening when I was trying to load HoloBlur X according to the directions. It went through the whole installation in CWM without errors, but boot looped until it went dead. I did format and clear all the caches and all that too.
I'm not really sure what I'm missing here. I just hope someone might have a suggestion for me.
Thanks in advance for any help!

you could try format system in cwm

frog1982 said:
you could try format system in cwm
Click to expand...
Click to collapse
Thank you, and I appreciate the suggestion, but I have done that multiple times with no change in result.

Your positive your unlocked? Rooted?
Sent from my PACMAN MATRIX HD MAXX

deeje00 said:
Your positive your unlocked? Rooted?
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
Absolutely positive.
I unlocked using the Motopocalypse method, and have rooted using Motochopper with the Mythtools tool.

does cwm say that it cannot mount the cache after flashing the rom

Safestrap VS. CWM
Austin Connell said:
Absolutely positive.
I unlocked using the Motopocalypse method, and have rooted using Motochopper with the Mythtools tool.
Click to expand...
Click to collapse
Are you using a version of Safestrap recovery or are you ABSOLUETLY positive that you are using a custom recovery? Most newer ROMs (4.1 and up) usually require you to use a custom recovery.

I'm sure he knows the difference between the 2.
Sent from my PACMAN MATRIX HD MAXX

Wipe and Restore
Hey guys I'm not exactly experienced with troubleshooting these kinds of problems. Hopefully I can learn something with the help of the community. I'll go ahead and lay out the situation and problem.
Problem:
Whenever I flash a rom with CWM, the phone will either A: Get stuck on a blank screen with the green LED on or B: Go through the boot animation and crash on "preparing android" and loop the process.
Info:
My AT&T Atrix HD has an unlocked bootloader, I have had several successful flashes in the past, and they have all worked well. I am able to flash the stock firmware back to the phone and it will load just fine. I have tried to go back to stock and start over, but I keep getting the same result. I've tried multiple roms with no change. This started happening when I was trying to load HoloBlur X according to the directions. It went through the whole installation in CWM without errors, but boot looped until it went dead. I did format and clear all the caches and all that too.
I'm not really sure what I'm missing here. I just hope someone might have a suggestion for me.
Thanks in advance for any help!
Click to expand...
Click to collapse
If you indeed are positive that you flashed the correct custom recovery, then follow these steps to fully Wipe, Restore to stock, and reflash.
Please read all of these steps before attempting to follow them!
** Note: I am not responsible for any damage done to your phone by following these instructions. **
Charge your device to a reccomended 80% (at least)
Make sure you have a Windows computer
Download the latest USB drivers from Motorola
Boot into your current recovery and make a nandroid backup, just in case.
Boot your device into Fastboot by powering off device and holding the Power+Volume Up+Volume Down and scrolling using the Volume Down button.
Plug your device into your computer
Download Fastboot if you don't already have it. (A simple Google search should result in a download link)
Type "fastboot erase data"
Type "fastboot erase cache"
Type "fastboot erase system"
Type "fastboot erase boot"
Type "fastboot reboot"
All of these commands should pass without conflict.
Your phone should reboot, but have no bootable OS. Don't panic if you get this error. Just manually power off your device and put it in bootloader mode once again (Power+Volume Up+Volume Down).
After that, follow these steps to flash to stock.
Download and install RSD Lite 6.1 here : www.mediafire.com/?3ckiknmwcpjolb2
Download the correct Fastboot Package for Jellybean here: http://sbf.droid-developers.org/dinara/list.php -- It should be MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip for 4.1.1 Jellybean on AT&T.
Make sure your phone is in bootloader mode with the directions in the first set of instructions and select Fastboot flash mode.
Open RSD Lite and select the downloaded Zip file in the box at the top.
Your device should appear at the list view towards the bottom of the screen. Click it and the "Start" button should be clickable. Click start and wait.
Wait for RSD Lite to say success and do not unplug it until the phone COMPLETELY BOOTS UP.
After all of this, you can now root, unlock bootloader, flash CWM, and install your custom rom. This should take care of any bootloops while installing Custom ROMs.
Click the thanks button if I helped!
PM me if you have any problems during this so I can help!

lol no, I'm not using a safestrap. I'm using a CWM Recovery.
I will give the rsd method a try tonight. thank you guys for all the help so far. luckily i have another phone to use in the meantime.

PHP:
Austin Connell said:
lol no, I'm not using a safestrap. I'm using a CWM Recovery.
I will give the rsd method a try tonight. thank you guys for all the help so far. luckily i have another phone to use in the meantime.
Click to expand...
Click to collapse
Okay. Make sure to tell us the results! Good luck!

I had very similar problems because I unwittingly attempted to flash the wrong cwm recovery file... which seems to have affected the Boatloader behaviour. I made it to #6 of the RSD steps in the help offered by lucasantarella (I was using RSD Lite 6.1.4), but the flash fails with:
Model Port No. Port Type IMEI / ESN / MEID Status Progress Result
Fastboot QINARA S 1 USB N/A Failed flashing process. Unknown fastboot command. (getvar) FAIL
Here's the complete story on the phone:
Brand new Factory Atrix HD, 4.1.1.
Installed MythTools (V1.1) on Windows XP and downloaded the USB Motorola Drivers
Used MythTools to unlock the bootloader
Installed superuser-4.3-beta2.zip
Installed ROM Manager 5.5.2.0 (which I can't use until the customized CWM for AHD is installed)
Downloaded mb886-cwm-6.0.3.6-touch-recovery-flashable-signed.zip
Using MythTools, I selected the wrong recovery file (selected a stock cwm instead) which failed to flash,
and the bootloader is now reporting a Flash failure. Here's the entire screen:
AP Fastboot Flash Mode (S)
10.9B(*) (sha-2e68372, 2012-11-17 23:33:08)
eMMC Info: Size 8GB
Device is UNLOCKED. Status Code: 3
Battery OK
Transfer Mode:
USB Connected
Fastboot Reason: Flash Failure
usb connected
When I power it down and then hold the vol + and - together, I get the following menu:
Boot Mode Selection Menu (10.9B)
Vol Up Selects, Vol Down Scrolls
Available Boot Modes:
Normal Powerup
Recovery
AP Fastboot
Factory
BP Tools
Selecting any of those puts the AHD into the stock AT&T 4.1.1 normal screen and its ready for use.
Using Myth Tools to "Reboot normally" (option A) does the same thing as Option B, "Reboot to fastboot mode", which puts me back into the fastboot screen showing "Flash failure".
It appears that I'm locked to 4.1.1... because of Bootloader problems.
Any comments/thoughts/insight? It's been a year since I did any flash/RSD work and have poured over the various pages/threads on the AHD for the last three days... Apparently I didn't read enough...
Am currently using a Motorola Bravo running the CyanogenMod-72-20120506-NIGHTLY-Kobe and was hoping to migrate up to the AHD.
-ricer1

whew!!! The Atrix HD works!!!!
I thought my phone was crippled forever.. but I followed leanix's instructions here and am running epinter's rom on my Atrix HD:
http://forum.xda-developers.com/showthread.php?p=45306485#post45306485
Many thanks to leanix for posting his MUCH needed help.
- ricer1

lucasantarella said:
If you indeed are positive that you flashed the correct custom recovery, then follow these steps to fully Wipe, Restore to stock, and reflash.
Please read all of these steps before attempting to follow them!
** Note: I am not responsible for any damage done to your phone by following these instructions. **
Charge your device to a reccomended 80% (at least)
Make sure you have a Windows computer
Download the latest USB drivers from Motorola
Boot into your current recovery and make a nandroid backup, just in case.
Boot your device into Fastboot by powering off device and holding the Power+Volume Up+Volume Down and scrolling using the Volume Down button.
Plug your device into your computer
Download Fastboot if you don't already have it. (A simple Google search should result in a download link)
Type "fastboot erase data"
Type "fastboot erase cache"
Type "fastboot erase system"
Type "fastboot erase boot"
Type "fastboot reboot"
All of these commands should pass without conflict.
Your phone should reboot, but have no bootable OS. Don't panic if you get this error. Just manually power off your device and put it in bootloader mode once again (Power+Volume Up+Volume Down).
After that, follow these steps to flash to stock.
Download and install RSD Lite 6.1 here : www.mediafire.com/?3ckiknmwcpjolb2
Download the correct Fastboot Package for Jellybean here: http://sbf.droid-developers.org/dinara/list.php -- It should be MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip for 4.1.1 Jellybean on AT&T.
Make sure your phone is in bootloader mode with the directions in the first set of instructions and select Fastboot flash mode.
Open RSD Lite and select the downloaded Zip file in the box at the top.
Your device should appear at the list view towards the bottom of the screen. Click it and the "Start" button should be clickable. Click start and wait.
Wait for RSD Lite to say success and do not unplug it until the phone COMPLETELY BOOTS UP.
After all of this, you can now root, unlock bootloader, flash CWM, and install your custom rom. This should take care of any bootloops while installing Custom ROMs.
Click the thanks button if I helped!
PM me if you have any problems during this so I can help!
Click to expand...
Click to collapse
Hey i tried this in bot rsd lite and myth tools but it won't work
I can't get back into recovery, or boot up the phone. it only boot into fast boot
my phone is locked and status code 0
I really don't know what to do.
when I use myth tools is says fastboot not found or as a command on internal or externel
or attrib internal or external
please help me

alki1979 said:
Hey i tried this in bot rsd lite and myth tools but it won't work
I can't get back into recovery, or boot up the phone. it only boot into fast boot
my phone is locked and status code 0
I really don't know what to do.
when I use myth tools is says fastboot not found or as a command on internal or externel
or attrib internal or external
please help me
Click to expand...
Click to collapse
Follow this guide http://forum.xda-developers.com/showthread.php?t=2259661

Having a tough time going back to stock. Decided to give lucasantarella's wipe and restore process a go. At step #8 I got this:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\>fastboot devices
TA30001GGN fastboot
C:\>fastboot erase data
erasing 'data'...
Invalid partition name data
FAILED (remote failure)
finished. total time: 0.105s
C:\>
I've ensured that I have the latest drivers installed and have the latest fastboot. Any help on what to try next would be appriciated. Thanks.
Edit: Would trying leanix's post on using the command lines be advisable for me at this time? PhilZ touch and CM 11 are currently installed on my device. PhilZ seems to run ok but clearing the dalvik cache doesnt seem to work and all I get is the arrow spinning around CM's head on bootup.

ifixgse said:
Having a tough time going back to stock. Decided to give lucasantarella's wipe and restore process a go. At step #8 I got this:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\>fastboot devices
TA30001GGN fastboot
C:\>fastboot erase data
erasing 'data'...
Invalid partition name data
FAILED (remote failure)
finished. total time: 0.105s
C:\>
I've ensured that I have the latest drivers installed and have the latest fastboot. Any help on what to try next would be appriciated. Thanks.
Edit: Would trying leanix's post on using the command lines be advisable for me at this time? PhilZ touch and CM 11 are currently installed on my device. PhilZ seems to run ok but clearing the dalvik cache doesnt seem to work and all I get is the arrow spinning around CM's head on bootup.
Click to expand...
Click to collapse
If you're trying to wipe user data/do factory reset through fastboot, try "fastboot -w". Also are you using the snapdragon fastboot?
Sent from my MB886 using Tapatalk