Database Users

Stuck on M screen... what a mess!

Ok, here's the quick and the dirty: rooted Dx with bloatware removed. Read that the update won't work if I removed bloatware, so...
1. Downloaded 928droid's back to stock .zip file. Put on SDCARD root
2. Downloaded ROM manager /clockwork to install the ROM. Did not work. Phone rebooted and nothing changed.
3. Tried the update install just in case and it also (still) didn't work.
4. Tried bootstrap, mount and storage, go to format system, mount system = nothing. Phone stuck on M screen after restart.
5. Go into android recovery mode. Try to install 340update.zip (renamed to update,zip), won't work. Phone still stuck on M screen.
6. Tried wipe data cache in recovery mode. Still stuck on M screen
7. Tried restoring factory data. Still stuck on M screen.
Right now, I don't care about the update. I just want my phone working again.
Can someone please help me???
I'm not a super techie but can get through good instructions.

You have to flash an SBF, rdslite 4.8 and the gift 2 or newer... lame bootloader
Sent from my DROIDX using XDA App

Super noob question, please be gentle ...

Here's the background: I have a droid x, rooted with the latest z4root. Previously deleted some of the bloat (and yes, completely deleted with no backup).
As most of you know, I cannot use the official ota update from verizon (continually fails to install whether I keep root on or off). Currently have system version 2.3.15 mb810 verizon.en.us and (if it means anything), android version 2.2.
To further complicate this, I have no access to any kind of windows machine, pure Mac only.
Here's the $ 64,000 question; can I simply revert to a factory wipe (to reload all the crap I deleted), update via the official update and then reroot via z4root? Do I need to make a backup of some sort and if so, using what? Or, am I going to lose all data to date?
Any help will be greatly appreciated by this very non-technical, wanna-be rooter.
Please, no flames regarding the winbloze ...
Again, thanks in advance if you have the patience to try and help me. I'm terrified of bricking my phone.
DC
PMs are fine, too
Sent from my DROIDX using XDA App

Factory reset will only delete user data, it doesn't reinstall stock apps.

You will lose your apps and data with this method, but it's the cleanest way to do it. If you choose not to wipe data you may end up with an unstable phone. To be honest since you're coming from a stock image rather than one of the "roms" around here you might be able to get away with it. Just skip step 6. I'm still going to go with the clean route though.
Make sure your phone is fully charged!
1) Get Titanium Backup and back up all your app data.
2) Get Droid X Bootstrapper and install it.
3) Get Rom Manager, goto Download Roms and get the stock 2.2 image. Remember where it downloads to!
4) Go into Droid X Bootstrapper and reboot into (clockworkmod) recovery. In recovery you use the volume up/down keys to go up/down, the camera key to select and the back button to go back.
5) In recovery go into backup and restore, and make a backup. When it's done hit the back button to get to the main menu.
6) Choose to wipe data and then also wipe cache.
7) Go into mounts and storage, mount system and data (you'll know they are mounted because the option will now say "unmount system")
8) Choose install zip from SD card, and pick the image that Rom Manager downloaded.
9) Reboot system
If you get stuck in a boot loop, pull the battery out. Put the battery back in, and then hold down the home and power buttons until a triangle with an exclamation point pops up. Press the search button to get into the stock recovery. Wipe data/cache.

Try the sbf file for your version. Way more simple than the post above and you will be able to upgrade with the new OTA.
Sent from my DROIDX using XDA App

Why bother getting back to a stock .15 build in order to update when you can just go straight to the 2.3.340 and get the same result quicker without having to unroot and then reroot?
My Droid World has all of the necessary pieces in zip files to upgrade the bootloader, kernel, radio, and system. Just flash them in the order that they appear on the post restart between each update.
MDW Update Post

He has a Mac.

milan616 said:
He has a Mac.
Click to expand...
Click to collapse
They aren't sbf files so it doesn't matter, it can be done entirely from the phone. It's just a series of zip file that need to placed on the sd card and installed via clockwork recovery.

Whoops! That's what I get for only reading the first half of your post

pjsockett said:
Why bother getting back to a stock .15 build in order to update when you can just go straight to the 2.3.340 and get the same result quicker without having to unroot and then reroot?
My Droid World has all of the necessary pieces in zip files to upgrade the bootloader, kernel, radio, and system. Just flash them in the order that they appear on the post restart between each update.
MDW Update Post
Click to expand...
Click to collapse
I've downloaded all the files and moved them to my SD card. When I reboot into recovery and select update.zip I get an error saying it can't find the file. I don't see update.zip anywhere on my SD card. Do I need to have this on my card before installing the .zip files?

Are you using the droid x bootstrapper and rebooting into recovery , also mounting system?
Sent from my DROIDX using XDA App

use the "choose zip file" option instead of the "update zip file" option.
seems the same but is different .

[Q] Trying to upgrade to rooted .596 but nothing but errors - please help

ok ive tried everything in the sticky thread regarding reverting back to froyo using the 2.3.34 SBF file. i flash the file, root, and use the bootstrap to load the Blur_Version.2.3.340 Part 1 and Part 2 files from the sticky thread, but i get the following error.
Verifying Current System....
assert failed: apply_patch_check (/system/app/AccountAndSyncSettings.apk)
then gives a bunch of numbers....then shows the sd file i was trying to apply with "Status 7) Installation Aborted.
i figured the SBF was bad so i redownloaded it from somewhere else, same errors. i even tried to load up the 3 parts to GB .588 hoping to then goto .596, same error.
finally i installed maderstcok340 update file using recovery. everything worked and i was able to install the GB updates. but once i rebooted the phone after it said everthing was successful, it loads into the bootloader screen and wont let me out of it.
im so frustrated. does ANYONE have any idea why this isnt working???

SBF to 2.3.340 (Froyo), root, install Droid 2 Bootstrapper, then install the two part 596 rooted build.
I recommend using Linux to SBF. There's a bootable disc floating around the forums somewhere that you can use. Just Google for it.
Root using Z4root, then install the Droid 2 Bootstrapper application. Be sure that it is the DROID 2 version. The Droid X version doesn't work with Gingerbread.
Lastly, you need to boot into ClockworkMod Recovery. To do this open the Droid 2 Bootstrapper application and select the top button, when it gives you the success message press the reboot button to reboot into ClockworkMod Recovery.
Lastly lastly, wipe data, then install both part one and part two of the Gingerbread zip files. NOTE: You must install both the zip files one right after the other, if you leave recovery before flashing part two you will have to SBF.
Completely lastly, reboot the phone, and if you bootloop boot into stock recovery and wipe data/cache.
Hope this helps ^_^
Sent from my DROIDX using XDA App

ive done all of this. my problem is after i SBF, root and load the bootstrap, the install of the zip gives me the error seen above in bold. i cant get past the installation. is something wrong with the SBF??

i finally got it to work. the SBF i downloaded was bad. i found a new file and used it, now its working just fine.

neeed help stuck on M logo :((

helloo everyone!
basically what i did was backed up my current stock froyo rom, and then followed the steps for the "deblurred gingerbread rom" on how to flash it, i then went to reboot my phone.and got stuck on the M logo have pulled the battery several times im lost at what to do so please anyone help? i would be very grateful

you should press volume-down + camera key both, and poweron your phone to enter bootloader to flash the fixedsbf.
it will not automatically enter to the bootloader.

how do i go about flashing the fixed sbf?
i put my phone into bootloader and opened rsd lite and my phone wasnt recognised?
what am i meant to do

All the information is findable on this forum!
First; the howto flash SBF: http://forum.xda-developers.com/showthread.php?t=1032372
Second; the SBF file you need to flash: http://www.multiupload.com/KL6LSHIRCS
So with that howto you need to flash the SBF provided in this post. After that it'll work.

when i plug my phone into the computer in bootloadermode and find the sbf file in rsd and press start, nothing happens? i have motorola driver installed?

Can you post a screenshot of RSD Lite with your phone connected and the SBF selected?
Also try to reboot and try again.

i was playing around with different things and managed to get my phone mounted to rsd the phone has booted! i did a full data wipe and cache wipe and im just restoring my apps back with titanium backup, if i wanted to have all the blur services, would i now be able to restore the nand backup of the other gingerbread rom? or would i have to go through the whole process again?

If you want the Blur services now you just need to flash the MS2Ginger Nandroid in CWM.
...and the other way around offcourse. hf!

[Q] Can't load after downgrade to 7.2 Jordan

Hi all
I use to run cm-7.2 Jordan without any issues. Decided however to upgrade and test cm10 but since I didn't find it stable enough I decided to downgrade back to 7.2. The flash succeed without issues but when I reboot I get stuck with the Google logo and the os never boot up.
I tried to go through cm.7.1 but no luck there, same issue.
Any clue how i can resolve this?

llavsor said:
Hi all
I use to run cm-7.2 Jordan without any issues. Decided however to upgrade and test cm10 but since I didn't find it stable enough I decided to downgrade back to 7.2. The flash succeed without issues but when I reboot I get stuck with the Google logo and the os never boot up.
I tried to go through cm.7.1 but no luck there, same issue.
Any clue how i can resolve this?
Click to expand...
Click to collapse
Try to wipe all from stock recovery ----> Power+Vol dwn

Kayant said:
Try to wipe all from stock recovery ----> Power+Vol dwn
Click to expand...
Click to collapse
Thanks for quick reply. I tried that and the phone loaded a android character with a triangle and a exclamation mark. I don't have a good feeling about that

llavsor said:
Thanks for quick reply. I tried that and the phone loaded a android character with a triangle and a exclamation mark. I don't have a good feeling about that
Click to expand...
Click to collapse
That's good sorry forget to say you need to hold VOL dwn& Vol Up at the same time then wipe all...
Good luck

Exactly the same problem here, cannot downgrade to CM7.
Any good news?

Flash official froyo (I used ver 2.2.2)sbf via rsdlite. Root it using superoneclick and install 2init bootmenu 2.0. In custom recovery do full factory wipe follow with restore your nandroid 7.2 if you have them. If it booting hang at start screen, flash any froyo fixed sbf that contain the froyo kernel(optional). This way all your previous user data will still be intact.
Sent from my awesome rooted Defy: 2.3.6 XDA premium

So the recovery won't work and will have to start with SBF. Will wait until I have the computer environment to do so.
Thanks!

Kayant said:
Try to wipe all from stock recovery ----> Power+Vol dwn
Click to expand...
Click to collapse
farsight73 said:
Flash official froyo (I used ver 2.2.2)sbf via rsdlite. Root it using superoneclick and install 2init bootmenu 2.0. In custom recovery do full factory wipe follow with restore your nandroid 7.2 if you have them. If it booting hang at start screen, flash any froyo fixed sbf that contain the froyo kernel(optional). This way all your previous user data will still be intact.
Sent from my awesome rooted Defy: 2.3.6 XDA premium
Click to expand...
Click to collapse
Okey I have now flashed 2.2.2 sbf with RSDlite and after flash the phone still hangs during boot, now with the ugly Motoroly M instead of the Google logo from CM. So I guess I am back to square one, any idean anyone

llavsor said:
Okey I have now flashed 2.2.2 sbf with RSDlite and after flash the phone still hangs during boot, now with the ugly Motoroly M instead of the Google logo from CM. So I guess I am back to square one, any idean anyone
Click to expand...
Click to collapse
Wipe all from stock recovery that's you needed to do btw before installing cm7.... Sbf is not needed.
Go to stock recovery and wipe all your ROM should boot...
Let's Go ^_^

llavsor said:
Okey I have now flashed 2.2.2 sbf with RSDlite and after flash the phone still hangs during boot, now with the ugly Motoroly M instead of the Google logo from CM. So I guess I am back to square one, any idean anyone
Click to expand...
Click to collapse
Factory reset from stock bootmenu again. If it still hangs, flash sbf again with another factory reset afterwards just to be safe. BTW, I've had times where 3+ sbf flashes with factory resets were needed to get the phone to boot again.
One problem you might be having is if you formatted /data and /cache to ext4. Maybe it was just me, but I had to reinstall CM10, change back to ext3, flash sbf, then install CM7. Changing to ext3 and flashing CM7 didn't work -- same problem you're having. I wasn't sure if ext4 was the problem so I made sure I changed back to ext3 before sbf flashing. I'm not sure if the sbf reformats the partitions or just wipes them like a factory reset. If you've already flashed the sbf, then you can't install a CM10 rom to change back to ext3... Worse come to worse, you maybe able to install one of the custom sbf's with CM10 custom kernel preinstalled, change to ext3, flash official sbf, factory reset, then install CM7. I haven't looked into them because I make my own custom sbf's .
Bravo users are having this exact problem and my solution is to ensure that /data and /cache are ext3, flash the sbf and start from scratch -- the only guaranteed way I know of to fix this problem. Another Bravo user had the same problem and managed to fix it by changing some /data permissions over adb -- the user didn't specify the exact things done so I'm waiting on a reply with more details.

skeevy420 said:
Factory reset from stock bootmenu again. If it still hangs, flash sbf again with another factory reset afterwards just to be safe. BTW, I've had times where 3+ sbf flashes with factory resets were needed to get the phone to boot again.
One problem you might be having is if you formatted /data and /cache to ext4. Maybe it was just me, but I had to reinstall CM10, change back to ext3, flash sbf, then install CM7. Changing to ext3 and flashing CM7 didn't work -- same problem you're having. I wasn't sure if ext4 was the problem so I made sure I changed back to ext3 before sbf flashing. I'm not sure if the sbf reformats the partitions or just wipes them like a factory reset. If you've already flashed the sbf, then you can't install a CM10 rom to change back to ext3... Worse come to worse, you maybe able to install one of the custom sbf's with CM10 custom kernel preinstalled, change to ext3, flash official sbf, factory reset, then install CM7. I haven't looked into them because I make my own custom sbf's .
Bravo users are having this exact problem and my solution is to ensure that /data and /cache are ext3, flash the sbf and start from scratch -- the only guaranteed way I know of to fix this problem. Another Bravo user had the same problem and managed to fix it by changing some /data permissions over adb -- the user didn't specify the exact things done so I'm waiting on a reply with more details.
Click to expand...
Click to collapse
Okey good advice.
Here is where I am at now. I have flashed a number of different SFBs and I end up with the same situation every time. RSDLIte finish the process nicely but the phone get stuck with the flashing M. When I reboot manually I get passed the M and to the Android text/logo and there I get stuck.
I get advice to do a factory reset but how do I do that. The CW bootloader is gone and I can't get to the original boot loader either. I hit volume down and power, get to the triangle screen where I am supposed to hit the right bottom corner but nothing happens.
So I cant boot the phone to get into a menu where I can change to ext3 if this is a problem.
Please help, how can I get further?

Since I have no luck restoring stock rom I now have the following plan.
Install ClockWorkMod recovery with ADB.
Using recovery to do a factory reset and clear cache.
Flash a CM10 ROM (or any rom that will successfully boot up my phone).
From that start over to downgrade to CM9 to find a stable ROM.
The question I have now is if I will be able to use ADB with the USB connection mode I get from the bootloader (volume up+pwr button)? Or does ADB actually require that I can boot my phone and go into some other USB mode such as UMS or MTP.
Second question. Playing with restoring stock ROM i run out of battery and now my defy wont charge (only see a big question mark when loading). Seems like I get no power when USB is connected so is there a way for me to charge the battery or do I need to find another happy camper in town with a working defy that can power up my battery?

llavsor said:
Okey good advice.
Here is where I am at now. I have flashed a number of different SFBs and I end up with the same situation every time. RSDLIte finish the process nicely but the phone get stuck with the flashing M. When I reboot manually I get passed the M and to the Android text/logo and there I get stuck.
I get advice to do a factory reset but how do I do that. The CW bootloader is gone and I can't get to the original boot loader either. I hit volume down and power, get to the triangle screen where I am supposed to hit the right bottom corner but nothing happens.
So I cant boot the phone to get into a menu where I can change to ext3 if this is a problem.
Please help, how can I get further?
Click to expand...
Click to collapse
In froyo, you should hit vol up/down together to enter stock recovery.
If you have your cm7 nandroid or your gingerbread nandroid 2.3.6. In,custom recovery cm10, restore them. Your phone would not boot but you have your cm7 or gingerbread cwm by then, that you could format cache and total wipe back to ext.3 in the recovery menu, format/wipe follow with another nandroid restore and flash fix sbf from rsdlite.
But then the best way is go back totally clean by flashing stock froyo and root, install 2init with bootmenu 2.0. Then total wipe in recovery follow with restore your cm7 or gingerbread nandroids and flash the corresponding fix sbf via rsdlite.
Charging dead rom defy would need the MacGyver trick then. But some say if you leave it connected overnight in pc usb would charged it somehow but slow..
On 2nd thought.. you need to tell us yoyr defy model...green lense, red lense or the defy plus?? These models has their own characteristics in term of play around in cwm and way of flashing..
Sent from my awesome rooted Defy: 2.3.6 XDA premium

farsight73 said:
In froyo, you should hit vol up/down together to enter stock recovery.
If you have your cm7 nandroid or your gingerbread nandroid 2.3.6. In,custom recovery cm10, restore them. Your phone would not boot but you have your cm7 or gingerbread cwm by then, that you could format cache and total wipe back to ext.3 in the recovery menu, format/wipe follow with another nandroid restore and flash fix sbf from rsdlite.
But then the best way is go back totally clean by flashing stock froyo and root, install 2init with bootmenu 2.0. Then total wipe in recovery follow with restore your cm7 or gingerbread nandroids and flash the corresponding fix sbf via rsdlite.
Charging dead rom defy would need the MacGyver trick then. But some say if you leave it connected overnight in pc usb would charged it somehow but slow..
On 2nd thought.. you need to tell us yoyr defy model...green lense, red lense or the defy plus?? These models has their own characteristics in term of play around in cwm and way of flashing..
Sent from my awesome rooted Defy: 2.3.6 XDA premium
Click to expand...
Click to collapse
Thanks for very informative reply. I have a Defy 525 with red lens.

It's working.
I found a friend blessed with a defy and used that to charge the battery, tried to charge it over night with USB but it didn't work.
I then followed the steps from the last post and managed to flash a stock rom and then from there I rooted the phone with SuperOneClick, installed 2ndInit with ADB (guess you could use an apk installer from the phone as well ). I booted into recovery and flashed 7.2.0 Jordan from CM and now I am where I started a few weeks back.
Thank you all for your help.

That was the low battery problem.......
Since i had this i allways look for a full battery
If you think your defy is dead , a look for a empty battery won't be mad
Could anybody took a reminder info into beginners guide
MB525 red lense