Hi guys! Maybe the tittle is getting you confused, but it's so, now you're gonna unbrick and revive your Droid pro and also install de last update ( 4.7.3.XT610.Verizon.en.US) for your phone. "IT MEANS IT'S ONLY FOR VERIZON MODEL". Just follow the next instructions and you'll get it .
I know like me, many of you have gotten a brick in your phone or have your phone bricked for the time being. The first step that we'll do is unbricking the phone.
First:
Mod Edit link removed
Second:
Extract both archives, install one of the two installers of RSD, once RSD is installed, search for the DROIDPRO_2.26.20.sbf file that extracted.
Third:
Let's get your droid pro into bootloader mode,for this keep volume up and volume down keys + power button at the same time for 5 seconds, if do it right you'll get onto a screen like this,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now, connect your phone by usb cable to you computer, (Remember to have installed drivers in your pc) RSD show that your droid is online, click on the search button and select DROIDPRO_2.26.20.sbf file, once this is done click on start button and RSD will begin to flash the phone, wait for the process , when it finishes, your phone will reboot and alive again!
For update your for to the last version just go> Settings>About phone>check update after first update and reboot, phone will show a pop up message with a new update, download and install all necessary times.
Hope I could have helped you :fingers-crossed:
Very useful post, since noone before mentioned the bootloader mode, only fastboot that didn't work in my case. I need to try this when I get my phone back from a magician who is trying to fix it....
Regarding the post itself, you should clearly declare that the SBF is from American (VERIZON) model, since it will brick European ones even more than they already are
A question regarding the SBF file that you have provided..
Is it SBF of Stock GB 2.3.4..???
Imagine that I have rooted my phone but now I want to remove Root from my phone permanently, so in that case can I follow these steps to get the pure Stock ROM..???
I am totally new to Motorola and coming from hTC, so that's why asking so many questions..
Mohammad Hashir said:
A question regarding the SBF file that you have provided..
Is it SBF of Stock GB 2.3.4..???
Imagine that I have rooted my phone but now I want to remove Root from my phone permanently, so in that case can I follow these steps to get the pure Stock ROM..???
I am totally new to Motorola and coming from hTC, so that's why asking so many questions..
Click to expand...
Click to collapse
That the Pre-final update for "Verizon" motorola droid pro, android 2.3.3. And yes, If Your phone is the Verizon droid pro, you can flash this firmware. Don't worry, ask all what you need
migui0401 said:
That the Pre-final update for "Verizon" motorola droid pro, android 2.3.3. And yes, If Your phone is the Verizon droid pro, you can flash this firmware. Don't worry, ask all what you need
Click to expand...
Click to collapse
Yes I have "Verizon" version.. After flashing SBF of GB 2.3.3, I will get OTA of GB 2.3.4, right..??
Thank You..
Mohammad Hashir said:
Yes I have "Verizon" version.. After flashing SBF of GB 2.3.3, I will get OTA of GB 2.3.4, right..??
Thank You..
Click to expand...
Click to collapse
Yes, just go to settings, about phone and check update.
migui0401 said:
Yes, just go to settings, about phone and check update.
Click to expand...
Click to collapse
Why don't you work on developing CM9 and CM10..???
EDIT: Can't I use ADB commands on Droid Pro..?? I tried entering "adb devices" into Command Prompt to list attached devices but it showed nothing in the list.. Phone was connected with the PC in Charge Only mode..
EDIT 2: The link to RSD Lite is not working..
Mohammad Hashir said:
Why don't you work on developing CM9 and CM10..???
Click to expand...
Click to collapse
I'm student and really don't have time for developing a new rom, I'm considering, but for the time being, I cant.
Mohammad Hashir said:
Why don't you work on developing CM9 and CM10..???
EDIT: Can't I use ADB commands on Droid Pro..?? I tried entering "adb devices" into Command Prompt to list attached devices but it showed nothing in the list.. Phone was connected with the PC in Charge Only mode..
EDIT 2: The link to RSD Lite is not working..
Click to expand...
Click to collapse
First, which rom are you using? Is usb debugging on? Do you have the correct drivers?
Download RSD here: http://pc.cd/5cL
migui0401 said:
First, which rom are you using? Is usb debugging on? Do you have the correct drivers?
Download RSD here: http://pc.cd/5cL
Click to expand...
Click to collapse
I am using the Stock GB 2.3.4, and yes USB Debugging is enabled.. I have the drivers installed..
Mohammad Hashir said:
I am using the Stock GB 2.3.4, and yes USB Debugging is enabled.. I have the drivers installed..
Click to expand...
Click to collapse
I don't know but, maybe ADB is not supported in stock. Now, i'm going to flash stock firmware in my phone, i'll let you if ADB works for me.
I bricked my phone, flashed the SBF using RSD Lite but still getting bootloop, Droid logo in red color coming again and again..
Please help..
EDIT: I got it working now, after flashing the SBF, I went into recovery (R+M then Volume up and down keys) and performed "wipe data/factory reset" and "wipe cache partition", and now it is working..
Thank You..
Mohammad Hashir said:
I bricked my phone, flashed the SBF using RSD Lite but still getting bootloop, Droid logo in red color coming again and again..
Please help..
EDIT: I got it working now, after flashing the SBF, I went into recovery (R+M then Volume up and down keys) and performed "wipe data/factory reset" and "wipe cache partition", and now it is working..
Thank You..
Click to expand...
Click to collapse
Every time you flash the firmware over a custom rom, you must do a factory reset from recovery.
migui0401 said:
Hi guys! Maybe the tittle is getting you confused, but it's so, now you're gonna unbrick and revive your Droid pro and also install de last update ( 4.7.3.XT610.Verizon.en.US) for your phone. "IT MEANS IT'S ONLY FOR VERIZON MODEL". Just follow the next instructions and you'll get it .
I know like me, many of you have gotten a brick in your phone or have your phone bricked for the time being. The first step that we'll do is unbricking the phone.
First:
Download RSD Lite 6.1.x from here: http://pc.cd/5cL
And the SBF files from here https://my.pcloud.com/#page=publink&code=XZ3EMZwDjXjAu2s7BETYRGNfKhWL5MpSa7
Second:
Extract both archives, install one of the two installers of RSD, once RSD is installed, search for the DROIDPRO_2.26.20.sbf file that extracted.
Third:
Let's get your droid pro into bootloader mode,for this keep volume up and volume down keys + power button at the same time for 5 seconds, if do it right you'll get onto a screen like this,
Now, connect your phone by usb cable to you computer, (Remember to have installed drivers in your pc) RSD show that your droid is online, click on the search button and select DROIDPRO_2.26.20.sbf file, once this is done click on start button and RSD will begin to flash the phone, wait for the process , when it finishes, your phone will reboot and alive again!
For update your for to the last version just go> Settings>About phone>check update after first update and reboot, phone will show a pop up message with a new update, download and install all necessary times.
Hope I could have helped you :fingers-crossed:
Click to expand...
Click to collapse
These links no longer work :crying:
Can someone please help me with these sbf files.
I bricked my Droid Pro would love getting it back.
Thanks
Newyork! said:
These links no longer work :crying:
Can someone please help me with these sbf files.
I bricked my Droid Pro would love getting it back.
Thanks
Click to expand...
Click to collapse
Try again.
migui0401 said:
Try again.
Click to expand...
Click to collapse
Tried.
:crying:
Newyork! said:
Tried.
:crying:
Click to expand...
Click to collapse
Try the links on the Op first post. In the beginning of the thread.
migui0401 said:
Try the links on the Op first post. In the beginning of the thread.
Click to expand...
Click to collapse
Thanks!!
Downloading it now, will try tomorrow.
I hope i won't need anymore help
migui0401 said:
Every time you flash the firmware over a custom rom, you must do a factory reset from recovery.
Click to expand...
Click to collapse
Hello,
and if I try push power + R +M and there is onluy sign "!" and Android symbol? And there is no possible to choose any option to wipe data?
baroo89 said:
Hello,
and if I try push power + R +M and there is onluy sign "!" and Android symbol? And there is no possible to choose any option to wipe data?
Click to expand...
Click to collapse
Press both volume buttons when you see the exclamation mark, and you will get the menu.
Related
hi
I flashed my defy using the nandroid backup with the fixed sbf attached.
and the phone bricked to the motorola start screen
looking up at the forums
I then tried flashing with the 2.3.4 orange version
and the phone flashed normally,
but as its the UK version of the firmware, I am now not able to connect to any of the mobile networks in india. and so I want to
downgrade to the original froyo that my phone came with..
the same
please help me
please
ashwanikoul said:
I then tried flashing with the 2.3.4 orange version
and the phone flashed normally,
Click to expand...
Click to collapse
Did you flash the full sbf when you did this?
yes the full sbf..
please... guys....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
why dont you read the big effing warning!
this is the warning:
Simplestas said:
NO DIRECT DOWNGRADE
please don't flash sbf or you'll have serious problems going back to Froyo.
Click to expand...
Click to collapse
walter79 said:
cgxx.smg version:
Code:
[COLOR="Red"]CG31.smg version is 5[/COLOR]
CG32.smg version is 1
CG33.smg version is 1
CG34.smg version is 1
CG35.smg version is 2
[COLOR="Red"]CG39.smg version is 5[/COLOR]
CG42.smg: signature not found!
CG45.smg version is 0
CG47.smg version is 2
CG61.smg version is 1
CG64.smg version is 1
CG65.smg version is 1
Click to expand...
Click to collapse
walter79 said:
Android 2.3.4 "Gingerbread" !!BETA!!
!!! No downgrade for all Android 2.3.4 to FROYO ; NO DIRECT ROOT!! Use only the nandroid backup.
Click to expand...
Click to collapse
Downgrade to Froyo with Nandroid Backup + Fixed SBF
what you have to do right now,
you go and search edited leaked gingerbread 2.3.4 sbf for that.
the edited sbf gingerbread 2.3.4 automatically rooted.
but the problem is i don't have the link for that.
but i'm sure i ever see that in this forum.
why you have to search that edited 2.3.4 sbf?
because normal leaked gingerbread 2.3.4 can't be rooted!
if you cannot root, you can't install custom recovery..
if you cannot install recovery, you cannot restore froyo nandroid backup!
and froyo nandroid backup + froyo fixed sbf is the only hope right now.
sorry mate..
next time be prepared and be careful to read the warnings.
see I was not stupid not to read the warning but, since my phone bricked after flashing the custom nandroid 2.3.4and the fixed sbf.. I tried flashig again with indian roms 2.2, but it would get stuck in the bootloader loop, then I had no choice but to flash with 2.3.4 full sbf and my phone came alive.. but for the network problem and the battery getting heated up, I loved the gingerbread
but I now need desperate help
okay mate, since you only have 3 post you cannot asking for help on devs section.
i'll try to help searching edited-rooted-gingerbread sbf for you.
hope they'll answer and give me a link.
here, i ask them in devs section:
http://forum.xda-developers.com/showpost.php?p=15340284&postcount=188
okay, Walter79 answer my question.
thanks to him.
good news for you
detailed instructions how to downgrade to froyo
after you accidently flash full sbf of leaked gingerbread 2.3.4
big thanks to:
_shadow_ from forum.androidfan.ru | link
djkail from xda | link
walter79 from xda | link
Click to expand...
Click to collapse
download this (these are painly big ass files):
-this unique eclair sbf: It's a unique eclair release with version 5 of cg31 and cg39 (same with leaked gingerbread), so you can flash directly to it.
-superoneclick root for defy
-custom recovery app for defy
-rsd lite 4.9
-moto usb drivers: for 32 bit, for 64 bit.
-cee froyo nandroid backup
-cee froyo fixed+edited sbf *EDIT* *AGAIN*
Click to expand...
Click to collapse
here's the steps:
- please, next time you'll have to be more careful, it's not a cheap device for some people
- make sure you have > 80 % battery
- power your phone with volume down still pressed to enter stock recovery,
- press vol.up+vol.down to show the menu
- then do "wipe data/factory reset" and "wipe cache" --> must do this!!
- reboot from stock recovery, immediately press and hold volume up for 5 seconds, then release to enter bootloader mode,
- make sure drivers and rsd lite have been installed before
- then plug your usb to computer, open rsd lite and flash that unique eclair sbf, wait untill it finish and defy got to main menu
- now you are on eclair. do not play with camera for now, i'm afraid it will broke your flashlight
- turn off usb debugging, set usb connection as mass storage,
- extract and copy cee froyo nandroid backup to \sdcard\goapkrev\backup | it should be like this: \sdcard\goapkrev\backup\ThisIsTheFolderOfCEENandroid\
- and copy custom recovery app somewhere you can access it later
- set usb connection as none
- turn on usb debugging, get root with superoneclick root for defy, reboot
- turn off usb debugging
- open custom recovery installer with file manager, open that app. Tap install recovery, then reboot recovery
- do wipe data, then wipe cache ----> must do!!
- select backup/restore, select restore, then select Froyo CEE Nadroid *EDIT*
- reboot system now, but immediately press and hold volume up for 5 seconds, then release to enter bootloader mode
- on bootloader mode, plug usb, open rsd lite, flash the fixed sbf of cee froyo
- wait untill the progress done, and defy run up on main menu.
- done, you should be happy now, it's froyo again. It's cee froyo (the stable one, many devs use it)
- install baseband switcher to suits your baseband region.
Click to expand...
Click to collapse
thanks a lot, I am in the process now to flash to eclair.. and am downloading the cee froyo nandroid
how do I install the baseband ?
ashwanikoul said:
thanks a lot, I am in the process now to flash to eclair.. and am downloading the cee froyo nandroid
how do I install the baseband ?
Click to expand...
Click to collapse
don't use ordinary eclair,
it's unique eclair with version 5 of CG31 and CG39,
use that unique full sbf eclair on the tutorial.
----------------
just download the baseband switcher apk, copy to your SD-Card,
then install, select your region.
you have to be get root, but don't worry,
because it seems Froyo CEE Nandroid backup already rooted,
just install and select your region.
happy to helps someone, sharing knowledge is caring.
you should do some, sometimes.
god!!
double post...
sorry.
I am now flashed with eclair, the one you sent the link to, and am not able to gain root access, using superoneclick, it just keeps waiting for the device?
any idea why?
ashwanikoul said:
I am now flashed with eclair, the one you sent the link to, and am not able to gain root access, using superoneclick, it just keeps waiting for the device?
any idea why?
Click to expand...
Click to collapse
is it usb debugging on? it should be on.
okay, if you have set it on,
try to set usb debugging off, then on again, it should be working.
if it still fails, close superoneclick, run it again.
yes usb debugging is off, I set it on and yep it rooted..
thanks again..
now just waiting for the nandroid froyo to get downloaded,
I don.t know how I can return the favour..
thanks a lot
GOD! i'm so sloppy.
i forget to add this line:
- select backup/restore, select restore, then select Froyo CEE Nadroid EDIT
go check the tutorial again,
sorry..
glad you haven't yet to that step, thats important!
please, confirm if you have read this
please, confirm if you have read the updated one
yes I have, I love you.. for caring so much
ashwanikoul said:
yes I have, I love you.. for care so much
Click to expand...
Click to collapse
because if you do not do that step,
it will ruin what you've done so far..
will go to endless boot loop..
------------------
oh ya, some information for people like you who accidently flash full gingerbread
------------------
when you install CM7, and want to go back to froyo,
you can't use that method of nandroid backup of froyo + fixed sbf.
because CM7 using different custom recovery,
CM7 is using bootmenu (consist of special 2ndInit + newest CWM)
normaly, if people want to go back to froyo from CM7:
they go to from stock recovery, wipe data+cache, go to bootloader, flash full sbf froyo, done.
but, for you, it is different.
use the latest tutorial i gave you earlier.
you have to go to that unique eclair first,
and remeber when on that eclair do not play with camera.
i think that's chinese sbf, and some says chinese sbf could damage flashlight.
maybe i just wrong about that, but play safe is better for your camera.
can I install CM7 to my phone after the steps you told me, go to froyo again,
and if I can how do I do that?
or you suggest I should not.?
ashwanikoul said:
can I install CM7 to my phone after the steps you told me, go to froyo again,
and if I can how do I do that?
or you suggest I should not.?
Click to expand...
Click to collapse
Yes, you still can use CM7
this tutorial is for your case only:
So you want to play again? Okay here CM7 tutorial for you..
- uninstall custom recovery app which already installed
- Copy CM7 RC1 v2 zip, Google Apps and Bootmenu Installer 1.7 to your SD Card
- Enable USB Debugging
- Install bootmenu installer 1.7 via File Manager, go to the app and click "Install 2ndInit Recovery" button. Wait for the led turn green.
- Disable USB Debugging, reboot
- Automaticly ended up on bootmenu
- Select custom recovery, "wipe cache partition" then "wipe data/factory reset"
- Select "install zip from sdcard", "choose zip from sdcard", then select CM7, then gapps
- Select "Go Back" then "reboot your system now"
- After all set, use baseband switcher app (already installed with cm7 package) to switch baseband which suit your region.
*if you want to go to custom recovery,
just reboot, when blue LED lights flashing, immediately press volume down.
select Custom recovery then Stable recovery.
DO NOT install bootmenu installer again when you are on CM7, surely will ****ed up your phone.
*if you want to go to froyo again,
just do the earlier tutorial.
Click to expand...
Click to collapse
[GUIDE] Comprehensive "Rooted Android 2.3.4 with unlocked bootloader" instructions
This is a guide on how to go from Froyo to rooted Gingerbread. Also, I'm on AT&T. Others beware. I take no responsibility if you hard or soft brick your phone.
I went from a rooted install running Gingerblur v4.5, but this will likely work regardless of what you have installed, since fastboot overwrites everything.
I didn't actually discover or develop any of this, but I figured someone might like to have a comprehensive guide, instead of searching through 500 different threads like I did.Known/potential issues:
- Fingerprint scanner not functional False alarm
- Avoid using RSDLite for *anything* if you installed the OTA 2.3.4 build
- Battery reading is sometimes inaccurate
- If you have a limited RAM issue, read here http://forum.xda-developers.com/showthread.php?t=1169409Step 0 - BACK UP EVERYTHING. Use Titanium backup, or just copy everything off your phone, whatever. This will leave you with an unlocked, rooted, but otherwise stock Motorola phone. Once this is done, set your USB mode to "None"
Step 1 - Install moto drivers
For x64 windows, use these: http://forum.xda-developers.com/attachment.php?attachmentid=634880&d=1308872277
For x32, http://www.multiupload.com/QNFILE4F07 (I havent tested these, I run Win7 x64)
Step 2 - Unlock your bootloader Note: some have hard bricked using RSDLite to install 1.8.3 over 4.5.91. Read warning here: http://forum.xda-developers.com/showthread.php?t=1160408
Download latest moto-fastboot from here: http://forum.xda-developers.com/showthread.php?t=1138092 *the win32 version worked for me, and I run 64bit windows 7*
Follow instructions here: http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
Step 3 - Flash stock Gingerbread image (you can do this without restarting your phone from the unlock bootloader step)
Follow instructions here: http://forum.xda-developers.com/showthread.php?t=1163342
Step 4 - Flash CWM Recovery
Instructions here: http://forum.xda-developers.com/showthread.php?t=1138541
Step 5 - Install root
Instructions here: http://forum.xda-developers.com/showthread.php?t=1159572
Note: I used my phone's USB Mass Storage mode to put the .zip on my external SD card. To get to recovery mode, shut down the phone. Then hold the power and volume up buttons until you see "fastboot." Use the volume down key to cycle through until you see "Android Recovery" then press volume up again. This will get you into the CWM environment, where you can navigate the menus to install the root .zip.
Step 6 - Restore your stuff
Now you should have a factory fresh Gingerbread / MotoBlur installation (didn't you miss the bloat?), with the addition of the superuser app. For tethering, I use Barnacle (requires root). I used Titanium Backup to uninstall any apps I don't want (anything beginning with AT&T, Blockbuster, Y!, etc.) and to reinstall all of my apps.
Feel free to make any corrections, or ask questions. Hopefully someone finds this useful. All credit to the OP of each thread I linked to.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nice for you to localize everything, ATT users will be grateful.
I went from a rooted install running Gingerblur v4.5, but this will likely work regardless of what you have installed, since fastboot overwrites everything.
Click to expand...
Click to collapse
Does this include the official 4.5.91? So many warnings about hard bricking since people flashed it.
From what I can tell, hard bricking only occurs when you use RSDLite to flash an older motorola SBF once you've gone to gingerbread. But someone else should chime in on that one - I never got a notice for an OTA update.
humjaba said:
From what I can tell, hard bricking only occurs when you use RSDLite to flash an older motorola SBF once you've gone to gingerbread. But someone else should chime in on that one - I never got a notice for an OTA update.
Click to expand...
Click to collapse
I didn't either. I downloaded a .zip and installed via stock recovery from a thread in the General Atrix forum.
Deggy said:
Does this include the official 4.5.91? So many warnings about hard bricking since people flashed it.
Click to expand...
Click to collapse
Nope, this one is the completely safe one.
Kennethpenn said:
"These are completely safe to flash. They don't mess with your bootloader like the OTA or SBF."
In the thread.
Magnetox said:
Nope, this one is the completely safe one.
Kennethpenn said:
"These are completely safe to flash. They don't mess with your bootloader like the OTA or SBF."
In the thread.
Click to expand...
Click to collapse
Just to clarify. I can NOT proceed to unlock my BL. Is that correct?
Deggy said:
Just to clarify. I can NOT proceed to unlock my BL. Is that correct?
Click to expand...
Click to collapse
What firmware did you flash? Can you link me to the thread you downloaded from?
Magnetox said:
What firmware did you flash? Can you link me to the thread you downloaded from?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1159604
Deggy said:
http://forum.xda-developers.com/showthread.php?t=1159604
Click to expand...
Click to collapse
Ah you have the deadly firmware
You simply cannot use RSD to flash down to 1.83 or 1.26 etc.
Or you will brick.
Clarify in Q&A, make your own thread with your question.
Taken from this thread kennethpenn said:
"What if I already flashed the official 4.5.91?
If you flashed the official update from XDA or by downloading through a dev-blur server (note: this excludes this ROM), you should avoid flashing SBF files in RSD Lite. We've confirmed this problem exists when users flash the 1.8.3 build specifically. It may happen with other SBF files, though."
So it looks like you can flash 2.3.4 builds via CWM. But double check by asking in Q&A.
Check out this thread.
http://forum.xda-developers.com/showthread.php?t=1163009
Fruit cakes basically dont touch your bootloader, they're basically modified sbf files that only contain the needed files to flash stuff. There's a 1.8.3 fruitcake in there as well as a 2.3.4 fruitcake.
An HKTW fruitcake is in development.
Fruitcake is the .sbf equivalent file that is flashable via CWM.
The big question is this - can you RSDflash the unlocked bootloader SBF by itself once you have the firmware of death? Once you have the bootloader unlocked, everything is gravy.
I don't know the answer
theres the moto-fastboot file i was looking for!
much appreciated.
Now there's a guide
I just did this like 3 hours before this guide came out. Though it at least seems like I was going to all the right threads that are in this guide anyways.
humjaba said:
The big question is this - can you RSDflash the unlocked bootloader SBF by itself once you have the firmware of death? Once you have the bootloader unlocked, everything is gravy.
I don't know the answer
Click to expand...
Click to collapse
From my understanding, if you flashed the official firmware of death you CANNOT use RSD in any way. All of your flashing has to be done via CWM and fruitcakes. Full .sbfs will brick your phone. Hard brick. As in #@$% ME hard brick.
humjaba said:
Step 6 - Restore your stuff
Now you should have a factory fresh Gingerbread / MotoBlur installation (didn't you miss the bloat?), with the addition of the superuser app. For tethering, I use Barnacle (requires root). I used Titanium Backup to uninstall any apps I don't want (anything beginning with AT&T, Blockbuster, Y!, etc.) and to reinstall all of my apps.
Click to expand...
Click to collapse
Weren't there some reports of issues restoring via TB after flashing Ken's beta 4.5? I'd have to search through his thread, but I thought it presented an issue or two.
So I guess no sweet Roms for me. Still haven't found a good thread to root my phone. I'm not sure if the FOD would mess with the rooting part of it.
SoberGuy said:
Weren't there some reports of issues restoring via TB after flashing Ken's beta 4.5? I'd have to search through his thread, but I thought it presented an issue or two.
Click to expand...
Click to collapse
I chose the batch "Restore missing apps with data" option from Ti Backup and it worked flawlessly.
humjaba said:
I chose the batch "Restore missing apps with data" option from Ti Backup and it worked flawlessly.
Click to expand...
Click to collapse
Perhaps it was settings then and not apps. Appreciate the information. I'll be doing that tonight
after i unlocked the bootloader
i flashed CWM
then i use CWM to flash 2.3.4 GB beta 4 zip from kenn
i like it better my way
I've been thinking about it for a while but decided to give it a try today . The step that tells me to hold up I get but then how so I power down to activate fastboot ?
Sent from my Atrix-4G, stock 2.3.4 (rooted)
DopeHack said:
I've been thinking about it for a while but decided to give it a try today . The step that tells me to hold up I get but then how so I power down to activate fastboot ?
Sent from my Atrix-4G, stock 2.3.4 (rooted)
Click to expand...
Click to collapse
hold volume down button while booting up, then hold volume up after fastboot is selected to activate it.
after that, you use fastboot commands on your computer.
But I was using the automatic unlocker . I still need to put in commands myself?
Sent from my Atrix-4G, stock 2.3.4 (rooted)
DopeHack said:
But I was using the automatic unlocker . I still need to put in commands myself?
Sent from my Atrix-4G, stock 2.3.4 (rooted)
Click to expand...
Click to collapse
Did you ask in that thread?
Sent from my MB860 using xda premium
DopeHack said:
But I was using the automatic unlocker . I still need to put in commands myself?
Click to expand...
Click to collapse
I believe the automatic unlocker will pause and should give clear instructions ask you to do specific things that have to be done by a human (power down and reboot into certain mode, etc), you just need to follow these instructions. After that, you just hit enter to continue.
If you are unable to follow these instructions, probably it's too much for you...
To reboot into fastboot, for example: press the power button, to turn off the phone; then hold the volume down button, press the power button again, you'll see "Fastboot", then release volume down, press volume up, you enter the "fastboot" mode
Too much for me lol I know how to get to all the menus that its telling me to go to but nothing else happens. the guide said nothing about typing in anything which is why I choose it. Especially since the automatic root worked easy as pie ...
Sent from my Atrix-4G, stock 2.3.4 (rooted)
You want help, laugh when people who are trying to help say it might be too much for you, yet you provide us close to absolute no information.
What guide are you following? We might know, but it still is your job to provide a link.
What is the step you are stuck at?
Why, what isn't going according to plan? What do you see happening in your sceen / phone?
If you can't explain properly, provide some screenshots.
You say you can get to all the menus it tells you to, yet in the first step you can't seem to get into fastboot. Your speech is unclear and what you want is hard to understand.
My opinion is you aren't ready to unlock your bootloader. You know very little about your phone or how it works. That's the community's fault really, with all these automatic scripts, which are really nice if you know what you're doing, but end up promoting easy ignorance in people like you.
I just hope in a month or two you are not one of those writing "OMG, please, I arrempted to downgrade by SBF and know my phone won't boot, what gives???"
Read up on some information a learn how these things work. It is the best you can do. Owning an android device and modding it can be great fun, but it does require some effort on your part. If I were you, I would learn how to unlock my bootloader with pudding, just to understand what is actuallly going on.
Either that, or you can learn how to ask for help properly and politely. Your choice.
Also, wrong section, This is not Q&A.
My girlfriend was rushing me so I tried to type up something quick but I used this
http://forum.xda-developers.com/showthread.php?t=1182871
As you can see like I can see it does not say I need to type anything in the cmd (which I have seen in YouTube videos and isn't that hard) but thought hey automatic sounds good so I gave it a try I don't have any problems getting the phone to fast boot or rsd as I've used the stock recovery to clear cache in an attempt to fix something. The part I'm stuck at is step 6
You are right I don't know alot about android which is why I didn't start messing with my phone the day I got it but I've been all over this site (well the atrix at least) and YouTube.
I appreciate any help and sorry for the misplaced thread
Sent from my Atrix-4G, stock 2.3.4 (rooted)
DopeHack said:
My girlfriend was rushing me so I tried to type up something quick but I used this
http://forum.xda-developers.com/showthread.php?t=1182871
Click to expand...
Click to collapse
this one is better
http://forum.xda-developers.com/showthread.php?t=1302423
doesnt give you the soft brick i think
So, let's see if I got this, you are having trouble at the part it says it should restart? Or before that? After you choose the number and press enter, what happens?
This could be a driver problem... If windows is not recognizing a device, it's common... Which windows are you using? I used to have some problems on XP and vista...
Newbleeto said:
So, let's see if I got this, you are having trouble at the part it says it should restart? Or before that? After you choose the number and press enter, what happens?
This could be a driver problem... If windows is not recognizing a device, it's common... Which windows are you using? I used to have some problems on XP and vista...
Click to expand...
Click to collapse
Right where it says it should restart and go into fastboot nothing happens I could hold that power button all day. I knew vista would bring an issue into the mix cause it never made the sound for connecting the phone but the SD cards show up
Sent from my Atrix-4G, stock 2.3.4 (rooted)
sanriver12 said:
this one is better
http://forum.xda-developers.com/showthread.php?t=1302423
doesnt give you the soft brick i think
Click to expand...
Click to collapse
This is the one I read before thanks hopefully my girlfriend will disappear for a hour or two (she doesn't want me to ruin my phone) so I can work on it .
so with this one I can use fauxs 1.3 or 1.45Ghz kernal with cm7 I've been craving that ice cream sandwich ..
Sent from my Atrix-4G, stock 2.3.4 (rooted)
Computer is down for a while seems like it wasn't meant to be but Im still going to get it done
Sent from my Atrix-4G, stock 2.3.4 (rooted)
I actually had to use a Vista system to get this to work.
Now, when the instructions say it should "Restart", at that point, have you been in "Fastboot" yet? Have you been to the part where you have to enter your "Unique ID"?
This is important to know because throughout the bootloader-unlocking process the phone should be restarted a couple of times. It sounds like you have at least gotten through the part where it flashes "Pudding" but it sounds like you haven't done the "fastboot" part yet.
Are you referring to "Step 6" in the actual post or within the script? If the power button does not work then just pull the battery. As long as it is not in the process of doing something you should be fine.
I also want to point out that the program you are using only requires that you type in your Unique ID, everything else is automated, not to mention the file contains everything you need including adb, fastboot, RSDlite, Superuser, Pudding, and a working recovery so it makes it very easy for the end user to not have to find everything on their own. The script unlocks the bootloader, roots your phone, and flashes CWM recovery.
Either way, please provide more details if you are still having issues. Good luck.
DopeHack said:
Right where it says it should restart and go into fastboot nothing happens I could hold that power button all day. I knew vista would bring an issue into the mix cause it never made the sound for connecting the phone but the SD cards show up
Sent from my Atrix-4G, stock 2.3.4 (rooted)
Click to expand...
Click to collapse
live4nyy said:
I actually had to use a Vista system to get this to work.
Now, when the instructions say it should "Restart", at that point, have you been in "Fastboot" yet? Have you been to the part where you have to enter your "Unique ID"?
This is important to know because throughout the bootloader-unlocking process the phone should be restarted a couple of times. It sounds like you have at least gotten through the part where it flashes "Pudding" but it sounds like you haven't done the "fastboot" part yet.
Are you referring to "Step 6" in the actual post or within the script? If the power button does not work then just pull the battery. As long as it is not in the process of doing something you should be fine.
I also want to point out that the program you are using only requires that you type in your Unique ID, everything else is automated, not to mention the file contains everything you need including adb, fastboot, RSDlite, Superuser, Pudding, and a working recovery so it makes it very easy for the end user to not have to find everything on their own. The script unlocks the bootloader, roots your phone, and flashes CWM recovery.
Either way, please provide more details if you are still having issues. Good luck.
Click to expand...
Click to collapse
I wasn't blaming vista I was just saying cause I've had problem with that is in the past.
I've basically done nothing haven't flashed or wiped my phone yet I was basically stuck at or around the first step cause it first asks for RSD protocol and then it says restart phone but the power button has no effect why in that mode nd when I pull the battery to manually put it in fast boot nothing happens nd I get some kind of batch error when it trays to get my unique id...
But got the computer back today so I'm gonna work on it again
Thanx for help ... will update you guys when I can
sanriver12 said:
this one is better
http://forum.xda-developers.com/showthread.php?t=1302423
doesnt give you the soft brick i think
Click to expand...
Click to collapse
Actually, I followed the method you linked (old netbook running XP) and got a softbrick on the automatic reboot after flashing pudding. I was so busy watching RSD Lite do its thing that I didn't catch that my phone had actually rebooted; it selected fastboot mode on its own so I was able to issue the unlock command. It took.
"7.Plug your device into your computer. RSD Lite should recognize your device and say “Model: NS Flash Olympus” and “Connected…” The acronym 'NS' may be different for your device people!!"
its not doing this(i have rsdlite 4.5.5 because i cant find 5.5)
edit: got on to next problem
Thanks everyone
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from Atrix 4G running CM7 ICS Final @ 1.2Ghz
If cpu not recognizing ur device in fastboot try restarting ur cpu. If u updated drivers u have to restart the cpu before it will see ur device.
Sent from my MB860 using xda premium
Ninjas and Developers ...
... I have a Defy 525 MB actually brick, spent MS2Ginger4 and after the first restart did not carry over.
... not applied the SBF-Fixed and maximum I can do is to connect the device, but is boot looping.
I have only the logo image (M) when I apply any xxx ROM 4.5.1 or later, otherwise is just black with white light.
I guess my problem could be solved if I could apply the wipes, but when I access the original recovery menu commands are not accepted when tightening button to select (Power)
below is a picture of what happens ... I think not mount command can not apply the wipes
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
E: Can not mount / cache / recovery / command
E: Can not mount / cache / recovery / caller
E: Can not mount / cache / recovery / log
E: Can not open / cache / recovery / log
E: Can not mount / cache / recovery / last_log
E: Can not open / cache / recovery / last_log
Click to expand...
Click to collapse
It's impossible to get out of it, have tested dozens of sbf files, drivers of different versions, all updated, rsd lite different versions (also updated)
I tried windows 7 on windows XP 64 and 32
Is there any way to apply the wipes without the recovery? is there any way to fix the recovery?
... indeed, a dead end.
I have no money to another smartphone, I have no phone.
Please Help Me.
Thanks
SOLVED: New Windows, New Drivers and New RSD, brought defy back to life
Click to expand...
Click to collapse
hey,
look at this what Casper87 original have post, just rename the zip to update.zip put it on sdcard and try to apply with stock recovery
Casper87 said:
here it's a update file made by @nepotu ,wich contains bootmenu 1.1.8 , TWRP 2.1.0 , multiboot 0.5.3 and CWM 5.0.6
http://db.tt/o0kNpJMv
Click to expand...
Click to collapse
i think that work
Edit:
Ooh missed that u have flashed some full sfb after u got this error, than this update do nothing for u without su rights cwm or the other stuff don't work.
what sfb u flash at last?
ok finally bl7 can be root look at this -»
Chamelleon said:
Finally with help from people from many other forums Defy with BL7 was rooted.
For now we have no script to make it on the phone without wipe but I'm very happy that it's working.
Rooting Procedure
1. Wipe phone twice (2x make Wipe Data/Cache in stock recovery)
2. Flash 4.5.1-134 DFP-231 CN or 4.5.1-134 DFP-231 Retail.en.EU CEE (It doesn't matter what version of this two You flash but it must be the same with version from point 4).
3. Wipe again (Data/Factory Reset)
4. Flash rooted SBF 4.5.1-134 DFP-231 CN Rooted SBF Part.1, 4.5.1-134 DFP-231 CN Rooted SBF Part.2 or 4.5.1-134 DFP-231 Retail.en.EU CEE Rooted SBF
Click to expand...
Click to collapse
but without wipe the cache think it don't work, u can try to flash first part and than wipe.
Defy mit Android 4.0.4 CM9 RockZ
tks, but didnt work ...
when i flash rooted SBF, the phone enter on a booterror screen (bootloader)
... with a regular SBF 4.5.1-134_DFP-2312xxxxx.sbf the phone starts without boot error - but in bootlooping, when i enter on the recovery menu, i can change the options (navigate) but when press the powerbutton to select an option nothing happens ...
is like if i doesnt press anything
excuses for this poor english
have u flashed the right two sbfs to get this work?
is that over all in bootmenu? u can't enter a custom recovery or adb?
have u flash the bootmenu cwm update file?
think ur problem is that u can't get root rights to get the bootmenu work right, without su that is a better screensaver
Defy mit Android 4.0.4 CM9 RockZ
AnTerNoZ said:
have u flashed the right two sbfs to get this work?
is that over all in bootmenu? u can't enter a custom recovery or adb?
have u flash the bootmenu cwm update file?
think ur problem is that u can't get root rights to get the bootmenu work right, without su that is a better screensaver
Defy mit Android 4.0.4 CM9 RockZ
Click to expand...
Click to collapse
If u can read correctly his phone does not boot even after flashing sbf...
@op u sure sbf flashing completed correctly? U should try again
hav u flashed full sbf? Which one?
u need to tell us what things u did in order to recover?
Sent from my MB526 using xda premium
nogoodusername said:
If u can read correctly his phone does not boot even after flashing sbf...
Click to expand...
Click to collapse
ooh ^^ my mistake, i mixed up recovery and bootmenu >.> i just have more to sleep than 2h to read right what's going on ^^ SORRY
Defy mit Android 4.0.4 CM9 RockZ
okay you can do one more thing if your mobile is in warranty.
flash some sbf which makes your phone look like it has crashed and then take it to service centre near you and then convince the service guy that its DOA(motherboard has crashed) and so he will replace it...
since in my country a third party company (reddington) looks after motorola's service so the service guy knew nothing about bootloader and my mobiles state was completely dead so he replaced the motherboard(he told me motorola has instructed to replace the motherboard if phone is not able to start)..and got the phone working
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
sorry for the posting on a wrong area
Click to expand...
Click to collapse
... I need others tools, custom and experimental SBf's, others (and radical) ways to recovery my Defy ... No hope for a while ...
Ninjas cannot help me ...
...
radical.. go to a motorola service center and say u pay for a revert to stock ROM, because ur data is expensive or save the world or something like that. this reflash were rewriting the board from defy with this special omap tool and the bin file... that's really radical..
sry, the only thing i think that worked for u, was the rooted sbf's flashed. i wish ur defy good luck to revival from the nirvana:thumbup:
Defy mit Android 4.0.4 CM9 RockZ
Back to life
... I explained that I did everything to revive Motorola, reading several times to update the drivers and the RSD I could revive the device ... removed the old drivers and RSD, cleaned the registry, installed everything updated and did not work.
yesterday i formatted my notebook and installed Windows 7 Ultimate 64 in English, flash a 134_DFP-4.5.1-231 before taking on technical assistance (hopeless) and to my surprise the starts moved from bootloop.
Lesson is:
on a clean install of windows with drivers and RSD updated with the correct SBF file, your motorola is more likely to come back to life.
I tried everything, for 10 days and several times - today I can say with certainty, the problem was in the operating system of the notebook.
Thank you to everyone who helped
omarvin said:
... I explained that I did everything to revive Motorola, reading several times to update the drivers and the RSD I could revive the device ... removed the old drivers and RSD, cleaned the registry, installed everything updated and did not work.
yesterday i formatted my notebook and installed Windows 7 Ultimate 64 in English, flash a 134_DFP-4.5.1-231 before taking on technical assistance (hopeless) and to my surprise the starts moved from bootloop.
Lesson is:
on a clean install of windows with drivers and RSD updated with the correct SBF file, your motorola is more likely to come back to life.
I tried everything, for 10 days and several times - today I can say with certainty, the problem was in the operating system of the notebook.
Thank you to everyone who helped
Click to expand...
Click to collapse
That's great to hear that ur moto is on the right way now, shame on Microsoft
what ROM u want to flash now? i recommend CM9
Defy mit Android 4.0.4 CM9 RockZ
I think the device may not even be bricked, who go through this need should test the entire environment out of the device before taking to the service.
I used MS2Ginger and 7.2 CM ... now I'm happy with the ICS
Thank you AnTerNoZ ...
Good morning again.
After my recent post about my cellphone as half-dead, I'm looking for rescue the information on the Internal Storage (We are talking of almost 3.5 GB of personal information). I know what ANY custom recovery can help me with this mission...
But after almost 4 hours trying with no success, I don't know what to do. :crying:
Step 1: Plug USB cable
Step 2: Vol+ Vol- and Power Button
Step 3: Select AP Fastboot
Step 4: On cmd write fastboot flash recovery "name of recovery here with .img"
On this step, I ALWAYS got this:
(bootloader) Variable not supported!
target max-download-size: 30MBStep 5: On cmd write fastboot reboot
Step 6: As fast as you can, press Vol+ for enter to the recovery
Alright. That's the process what everyone's using, right? Well, it isn't working for me, as I got always to the same recovery :s
Android system recovery <3e>
KDA20.62-10.1
What can I do? I used even the guide of ATTACK [GUIDE][FAQ][KK] How to Root, Boot Unlock & More
With no success...
I have Stock KK 4.4.2 what ends in .15 and Unlocked Fastboot
What recovery file are you trying to flash? Also, are you using the Moto fastboot? I believe this issue happens if you are using normal fastboot. Mfastboot is downloadable from that thread you linked
Sent from my RAZR M on BlissPop Lollipop 5.0.2 from Tapatalk
xKroniK13x said:
What recovery file are you trying to flash? Also, are you using the Moto fastboot? I believe this issue happens if you are using normal fastboot. Mfastboot is downloadable from that thread you linked
Sent from my RAZR M on BlissPop Lollipop 5.0.2 from Tapatalk
Click to expand...
Click to collapse
Uhm... I downloaded the mfastboot file what the guide had...
Download Mfastboot [MIRROR] - Refer to Mfastboot setup
Click to expand...
Click to collapse
I just unzip it on a empty folder (C:\Motorola RAZR M XT907\MFastboot in this case) and used mfastboot what he says on the guide.
I'm trying to flash any of these 3 recoveries:
TWRP-2.8.2.0-RAZR_M_KKBL.img
TWRP2710-RAZR_M-KITKAT.img
CWM6049-RAZR-HD_M-KITKAT.img
xKroniK13x said:
What recovery file are you trying to flash? Also, are you using the Moto fastboot? I believe this issue happens if you are using normal fastboot. Mfastboot is downloadable from that thread you linked
Sent from my RAZR M on BlissPop Lollipop 5.0.2 from Tapatalk
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Try putting it somewhere with no spaces in the path, like C:\xt907
Sent from my RAZR M on BlissPop Lollipop 5.0.2 from Tapatalk
xKroniK13x said:
Try putting it somewhere with no spaces in the path, like C:\xt907
Sent from my RAZR M on BlissPop Lollipop 5.0.2 from Tapatalk
Click to expand...
Click to collapse
Still same problem (6 failed attempts with every recovery)... I think I'm going to need learn how to use HouseOfMoto (I don't have ANY idea how to use it).
Use Flashify.
Sent from my Moto G™
ATTACK said:
Use Flashify.
Sent from my Moto G™
Click to expand...
Click to collapse
Uhm sorry... But how I'm going to use flashify if I'm trying to recover the information from a damaged Android?
Pedreo1997 said:
Uhm sorry... But how I'm going to use flashify if I'm trying to recover the information from a damaged Android?
Click to expand...
Click to collapse
You never stated that you couldn't boot to the OS in the OP.
After reading your other post, I believe you have a bad eMMC(?) and your device may be stuck in R/O. If that is the case your phone is non-recoverable. Your only option is to 'try' and restore via RSD or similar - but its unlikely to fix the issue.
Sent from my Moto G™
ATTACK said:
You never stated that you couldn't boot to the OS in the OP.
After reading your other post, I believe you have a bad eMMC(?) and your device may be stuck in R/O. If that is the case your phone is non-recoverable. Your only option is to 'try' and restore via RSD or similar - but its unlikely to fix the issue.
Sent from my Moto G™
Click to expand...
Click to collapse
Well sorry...
I don't know how I got the cellphone to work... and then I made a mistake and well :/
After use HouseOfMoto, my cellphone finally got out of the bootanimation, but constantly ending com.android.phone
I got the idea of put the cellphone on Airplane mode. The cellphone is again on the same problem :crying:
Do you know how it worked the first time? And if that is a sign of life?
Pedreo1997 said:
Well sorry...
I don't know how I got the cellphone to work... and then I made a mistake and well :/
After use HouseOfMoto, my cellphone finally got out of the bootanimation, but constantly ending com.android.phone
I got the idea of put the cellphone on Airplane mode. The cellphone is again on the same problem :crying:
Do you know how it worked the first time? And if that is a sign of life?
Click to expand...
Click to collapse
Did you perform a FULL install on House of Moto? What FXZ did you use? Maybe try redownloading or confirm hashes to make sure there just wasn't an issue with the FXZ.
Sent from my RAZR M on BlissPop Lollipop 5.0.2 from Tapatalk
xKroniK13x said:
Did you perform a FULL install on House of Moto? What FXZ did you use? Maybe try redownloading or confirm hashes to make sure there just wasn't an issue with the FXZ.
Sent from my RAZR M on BlissPop Lollipop 5.0.2 from Tapatalk
Click to expand...
Click to collapse
Uhm... What do you mean with FULL install? Remember what I'm trying to recover some folders if it's possible. Stock recovery, and I'm using VZW_XT907_4.4.2-KDA20.62-15.1_1FF.xml.zip and believe me: The only available download site lasts downloading 6 hours. It's A LOT of time.
Pedreo1997 said:
Uhm... What do you mean with FULL install? Remember what I'm trying to recover some folders if it's possible. Stock recovery, and I'm using VZW_XT907_4.4.2-KDA20.62-15.1_1FF.xml.zip and believe me: The only available download site lasts downloading 6 hours. It's A LOT of time.
Click to expand...
Click to collapse
You never noted that you wanted to recover things. I'd deal with the phone app force quitting and copy things to your computer via the USB. After you get everything you need, try a full wipe. If you don't want to do a re-download of the firmware, at least verify the hashes. A good tool for this is "Hash My Files." Make sure it matches what the website says it should be. If it doesn't, you will have to redownload.
Sent from my RAZR M on BlissPop Lollipop 5.0.2 from Tapatalk
xKroniK13x said:
You never noted that you wanted to recover things. I'd deal with the phone app force quitting and copy things to your computer via the USB. After you get everything you need, try a full wipe. If you don't want to do a re-download of the firmware, at least verify the hashes. A good tool for this is "Hash My Files." Make sure it matches what the website says it should be. If it doesn't, you will have to redownload.
Sent from my RAZR M on BlissPop Lollipop 5.0.2 from Tapatalk
Click to expand...
Click to collapse
It's the 2nd comment about that issue. I'm going to need to re-post what I said in my previous post, instead of say "following what I said on my previous post..."
Pedreo1997 said:
Uhm... Good afternoon.
I really don't know what happened to my XT907. I was playing Castle Clash, and then, suddenly...
- Smart Launcher Pro stopped
- GApps stopped
- Messenger stopped
- Amazon MP3 stopped
- WhatsApp stopped
And 4 or 5 more apps stopped. I nned to say what I wasn't using any of that apps but Smart Launcher Pro and WhatsApp.
So I selected the common Power Button... Power Off... Then I used the common Power Button for Turn On my XT907...
Stuck on the boot animation. It makes the sounds as receiving WhatsApp messages and that, but it's eternally on the boot animation (it isn't a bootloop)
What to do in this case?
(I need to add something else: I used the volume up button and every time I use it, the cellphone vibrates)
Click to expand...
Click to collapse
ATTACK said:
You never stated that you couldn't boot to the OS in the OP.
After reading your other post, I believe you have a bad eMMC(?) and your device may be stuck in R/O. If that is the case your phone is non-recoverable. Your only option is to 'try' and restore via RSD or similar - but its unlikely to fix the issue.
Sent from my Moto G™
Click to expand...
Click to collapse
I never wanted to say this but... you're right.
After trying to flash with RSDflasher, HouseOfMoto and RSDLite... I reached nothing. Now, I really don't care now for DCIM and that, I just want to get my cellphone again alive :crying: