This is a mess:
*MACGYVER is my only way to power up, battery shows '?' and pop up warning about it being INVALID. (New battery hooked to wall charger normally still reads ? and wont boot)
*Stock RECOVERY is not working (get error about loading cache/recovery).
*BOOTLOADER is NOT being recognised by RSDlite, maybe because of battery problem? The usb connection/disconnection noise happens when phone is running & connected, but it doesn't appear in my computer, sounds like its connecting then disconnecting randomly. *Debugging is on, usb connection set to mass storage.
*NO ROOT, I've tried four methods, now I'm looking at the THIS but I don't yet understand it.
Trying to root first, so I can run battery calibration and hopefully fix that, then use RSD to install suitable SBF, install CWM, then back to CM9 ICS and never never never mess with my phone again!
Help with rooting first would be good. Do I just use CMD to run the ADB commands??? But the phone won't show up in laptop.
NEXT: Short of this, what can I do to fix my invalid battery?
THEN: Can I upgrade stock recovery? Do I need to wait for bootloader to be unlocked?
build number: 3.4.2-107_JDN-9
android: 2.2.1 (upgraded within system from stock eclair)
kernel: 2.6.32.9-g8431013 system
version:version.34.4.9.MB525.T-Mobile.en.US
HELP PLEASE!
you have not said what your phone is and what version of android are your using.
You can try to find a battd.bin file from another ROM and copy that into system/bin using root explorer.
if you give people a little more info it maybe a little easier to point you in the right direction.
I know CG version 231 will not root but there is 2 SBF files you have to flash that are fixed pre rooted
kelbygreen said:
you have not said what your phone is and what version of android are your using.
You can try to find a battd.bin file from another ROM and copy that into system/bin using root explorer.
if you give people a little more info it maybe a little easier to point you in the right direction.
I know CG version 231 will not root but there is 2 SBF files you have to flash that are fixed pre rooted
Click to expand...
Click to collapse
thats a bit better information i hope in edited OP
notes1 said:
This is a mess:
*MACGYVER is my only way to power up, battery shows '?' and pop up warning about it being INVALID. (New battery hooked to wall charger normally still reads ? and wont boot)
*Stock RECOVERY is not working (get error about loading cache/recovery).
*BOOTLOADER is NOT being recognised by RSDlite, maybe because of battery problem? The usb connection/disconnection noise happens when phone is running & connected, but it doesn't appear in my computer, sounds like its connecting then disconnecting randomly. *Debugging is on, usb connection set to mass storage.
*NO ROOT, I've tried four methods, now I'm looking at the THIS but I don't yet understand it.
Trying to root first, so I can run battery calibration and hopefully fix that, then use RSD to install suitable SBF, install CWM, then back to CM9 ICS and never never never mess with my phone again!
Help with rooting first would be good. Do I just use CMD to run the ADB commands??? But the phone won't show up in laptop.
NEXT: Short of this, what can I do to fix my invalid battery?
THEN: Can I upgrade stock recovery? Do I need to wait for bootloader to be unlocked?
build number: 3.4.2-107_JDN-9
android: 2.2.1 (upgraded within system from stock eclair)
kernel: 2.6.32.9-g8431013 system
version:version.34.4.9.MB525.T-Mobile.en.US
HELP PLEASE!
Click to expand...
Click to collapse
Flash with Froyo sbf and see
Related
when i got my moto defy for xmas last year, i had my older brother root it for me. i really had no idea how to safely use root, but i liked being able to overclock and all the other features. the phone was a little buggy just because it was on 2.1 and no updates yet. once an update came out, i installed it and got a great performance increase. later, i realized that it was not working right. whenever i hold down an on-screen button, the touch sensitivity "timed out" after only about 1.5 seconds, unless i kept my finger moving around on the screen. and every few times i reboot the phone, this glitch goes away until i reboot again and then it is back. root was also taken away, and none of the one click roots work. also, when the 2.2 update came out, i got the error message when rebooting after installing the update and it did not work. i tried wiping the phone several times, no luck. i am now interested in fashing a custom rom and rerooting. would this fix it? there must be a special way to do it since my phone is so messed up. i would like 2.2 or 2.3, and 720p vid would be cool too. the version i have now is 2.1.1, so can anybody suggest a rom that is stable and will work ok?. one more question, when i flash a rom, will it leave my apps and settings alone or do i have to start over?
Have you tried using SuperOneClick to root the phone? (You'll need to install the Motorola drivers for it to work.)
In most cases, you will lose your apps and settings when you flash a new ROM. But, if you figure out a way to root it, you can back everything up in Titanium Backup first, and restore it afterward.
If you just want to start from scratch, try wiping everything in the stock recovery. To get into the stock recovery, power off the phone, hold in the volume- button then also press and hold the power button. After a few seconds you should see a triangle with an exclamation mark in the middle, and a little green android guy below that. Then press the volume+ and volume- buttons at the same time, and a menu should appear. Use the volume buttons to navigate the menu, and the power button to select an option. Select "wipe data/factory reset" and also "wipe cache partition".
If that doesn't work, I'd recommend flashing a new Froyo sbf using RSD Lite. Here's a quick tutorial:
1) Install the Motorola drivers and RSD Lite on your computer. See this guide for installing Moto drivers and RSD Lite:
http://forum.xda-developers.com/showthread.php?t=853674
2) Download the sbf file that you want to flash, and save it to your PC. Many sbf files can be found here: http://forum.xda-developers.com/showthread.php?t=966537 WARNING: If you flash a full stock SBF file, in most cases you will lose the ability to downgrade to earlier firmware versions. NEVER flash a full stock SBF file with a higher Android version than 2.2 (Froyo). Any stock firmware with Android version 2.3 or higher is made for the DEFY+, which has different camera hardware than the DEFY. If you flash the stock DEFY+ firmware, your camera will be broken and you won’t be able to downgrade back to Froyo again.
3) Make sure the phone battery is fully charged. Power off your phone, then hold in the volume+ button and the power button at the same time. After about 5 seconds, release the buttons. The bootloader should display – it will show the version and a battery check. (If that doesn’t work, pull the battery, then put it back in while holding the volume+ and power buttons.)
4) Start RSD Lite on your computer, then connect the phone with a USB cable. In RSD Lite, the Status column should say “Connected…”. Click on that, and some information about your phone should show up under Device Properties. Next, click the “…” button and browse to select the SBF file that you want to install. After opening it, information about the file should show up under File Properties. Then click “Start” and wait for the flashing process to complete. Wait until the phone has fully rebooted and RSD Lite says “Pass” before closing RSD Lite and disconnecting the USB cable. As an extra precaution, I usually power off the phone before disconnecting the cable.
Then you should be able to root, install custom recovery, and flash custom ROMs to your heart's content.
Good luck!
Thanks! Sorry to be a noob, but how do I know if a rom /sbf will work? Doesn't it matter what android version I have now? 2.1.1 is it
Sent from my MB525 using XDA App
Most custom ROMs for the defy require that you upgrade to Android 2.2 (Froyo) first. I can explain how to do that, if you like. What country are you from, and what cellular service are you using?
Before doing anything to your phone, you should read this guide: http://forum.xda-developers.com/showthread.php?t=1216982
Take a backup using titanium backup. This takes Care of all app and games. Then flash froyo. Go hd to install a custom rom like cm7. Guides are there for this. Restore all app and games with data from titanium backup
all this stuff is like you are speaking french to me. could somebody link me a sbf that has 720p video capability, 2.2 of some sort, and that is going to work with my current version(2.1.1)? i am still confused if the glitch i described will be fixed, and if it matters that i installed an update from motorola after i rooted. i really hate to be such a noob, but i don't have time to read all the guides and stuff. thanks for all the help, i just need a little more detail as i am very new to all this. I have T-Mobile USA
and one more thing: i just looked at some of the sbf's in the guide you showed me, the only 2.2 US file was from Megaupload, and F***King SOPA shut it down. now we feel the effects of this horrible law.
The best base (Froyo 2.2.2) for using a custom rom :
http://sbf.droid-developers.org/umt...RDNFRYORTCEE_P016_A016_HWp3_Service1FF.sbf.gz
Flash and enjoy CM7, Miui...
But honestly you need to read a little bit before... Or I can explain in french to you if you prefer... :-D
ritchrocko said:
all this stuff is like you are speaking french to me. could somebody link me a sbf that has 720p video capability, 2.2 of some sort, and that is going to work with my current version(2.1.1)? i am still confused if the glitch i described will be fixed, and if it matters that i installed an update from motorola after i rooted. i really hate to be such a noob, but i don't have time to read all the guides and stuff. thanks for all the help, i just need a little more detail as i am very new to all this. I have T-Mobile USA
and one more thing: i just looked at some of the sbf's in the guide you showed me, the only 2.2 US file was from Megaupload, and F***King SOPA shut it down. now we feel the effects of this horrible law.
Click to expand...
Click to collapse
If your DEFY has a greenish-yellow camera lense (as most do), you won't get 720p video capability no matter which sbf you use. (Unfortunately, it's a hardware limitation.) Most custom ROMs will enable you to take widescreen videos, though.
You don't need to use a T-Mobile USA sbf, by the way; you can use any Froyo (Android 2.2) sbf you want (except for Chinese ones, which will burn out your camera flash). You just have to change the cellular radio baseband afterward, to match the frequencies used by T-Mobile USA. That's easy to do; just use the "DEFY baseband switcher" app: http://forum.xda-developers.com/showthread.php?t=1052745 (Many custom ROMs, like CM7, already include the basebandswitcher app.)
Since you don't want to search through the forums for a guide on how to flash an SBF, here's one I wrote for a friend a while ago:
Flashing SBF firmware with RSD Lite
Follow this guide to flash firmware files (with .sbf filename extension) on the Motorola DEFY. This is useful for “de-bricking” a phone that won’t boot (provided the bootloader still works), or if you want to do a clean install of the Motorola stock firmware. I don’t recommend flashing SBF files unless absolutely necessary, however, since the process is dangerous: there is a slight possibility that your phone could become “hard-bricked” if something goes wrong. (A phone is hard-bricked when you can’t even access the bootloader to flash new firmware.) It is much safer to flash or modify firmware using ClockworkMod custom recovery, which doesn’t mess with the bootloader. (See step 3 for more info.)
Before flashing any new firmware on your phone, I strongly recommend reading this Beginners Guide: http://forum.xda-developers.com/showthread.php?t=1216982
WARNINGS:
A corrupted SBF, power failure on a critical part of the formatting, or some weird issues while creating partitions can lead to a “hard-bricked” phone (i.e., a phone that can’t even be restored by flashing new firmware, because you can’t get into the bootloader). It is recommended that you flash your phone from a laptop with a fully charged battery, to reduce the risk of losing power while flashing. Use good cables, and be sure that the PC doesn’t go to sleep during the flashing process.
If you flash a full stock SBF file, in most cases you will lose the ability to downgrade to earlier firmware versions. NEVER flash a full stock SBF file with a higher Android version than 2.2 (Froyo). Any stock firmware with Android version 2.3 or higher is made for the DEFY+, which has different camera hardware than the DEFY. If you flash the stock DEFY+ firmware, your camera will be broken and you won’t be able to downgrade back to Froyo again. (You can, however, install DEFY+ firmware without losing downgradeability, using the “fixed SBF” method. See this guide for more information: http://forum.xda-developers.com/showthread.php?t=1216982 )
The Chinese version of the DEFY has a different kind of LED for the camera flash. Using the camera flash with that firmware can permanently damage the LED.
Before installing any new firmware on your phone, backup your stock firmware, so that you can return your phone to its original state in case you ever need to send it to Motorola for repair. The firmware for the US T-Mobile version of the DEFY was never released as an SBF file, so you won’t be able to restore the phone to its original state unless you have a full system backup of the stock firmware. (See note at step 3 of the guide below.)
1) Install the Motorola drivers and RSD Lite on your computer.
See these guides for installing Moto drivers and RSD Lite:
http://forum.xda-developers.com/showthread.php?t=853674
http://forum.xda-developers.com/showthread.php?t=897445
2) Flashing new firmware using RSD Lite will erase everything on your phone’s internal memory (but not the SD card), so backup your contacts, settings, and any apps you’ve downloaded. I recommend using Titanium Backup, which is available free on the Android Market.
Note: your phone must be rooted before installing Titanium Backup. You can root the DEFY using SuperOneClick. Rooting the phone voids the warranty, but you can use SuperOneClick to un-root it if needed. See this guide: http://www.addictivetips.com/mobile...d-samsung-captivate-with-super-one-click-app/
As explained in the guide, you need to unmount the SD card and enable USB debugging before running SuperOneClick. The latest version of SuperOneClick can be downloaded here: http://forum.xda-developers.com/showthread.php?t=803682
3) Download the sbf file that you want to flash, and save it to your PC. If you are doing a “clean install” of CyanogenMod 7, I recommend using the 3.4.2-179-2 CEE DEBLUR sbf. Links to download it can be found in this thread: http://forum.xda-developers.com/showthread.php?t=966537
It would be a good idea to keep that file on your PC, in case you ever need to de-brick.
4) Optional step: before flashing an SBF file, it is a good idea to wipe data and cache in the stock recovery. (I usually forget to do that, though, and I haven’t had any problems.) To get into the stock recovery, power off the phone, hold in the volume- button then also press and hold the power button. After a few seconds you should see a triangle with an exclamation mark in the middle, and a little green android guy below that. Then press the volume+ and volume- buttons at the same time, and a menu should appear. Use the volume buttons to navigate the menu, and the power button to select an option. Select "wipe data/factory reset" and also "wipe cache partition". (At least, that is the procedure on Android 2.2. If I remember correctly, on Android 2.1 you had to tap somewhere on the touchscreen to get the menu to display, and the touchscreen was also used to navigate the menu.)
5) Make sure the phone battery is fully charged. Power off your phone, then hold in the volume+ button and the power button at the same time. After about 5 seconds, release the buttons. The bootloader should display – it will show the version and a battery check. (If that doesn’t work, pull the battery, then put it back in while holding the volume+ and power buttons.)
6) Start RSD Lite on your computer, then connect the phone with a USB cable. In RSD Lite, the Status column should say “Connected…”. Click on that, and some information about your phone should show up under Device Properties. Next, click the “…” button and browse to select the SBF file that you want to install. (WARNING: read the above warnings about file versions and downgradeability.) After opening it, information about the file should show up under File Properties. Then click “Start” and wait for the flashing process to complete.
7) Wait until the phone has fully rebooted and RSD Lite says “Pass” before closing RSD Lite and disconnecting the USB cable. As an extra precaution, I usually power off the phone before disconnecting the cable.
8) Root the phone using SuperOneClick. See this guide: http://www.addictivetips.com/mobile...d-samsung-captivate-with-super-one-click-app/
As explained in the guide, you need to unmount the SD card and enable USB debugging before running SuperOneClick. The latest version of SuperOneClick can be downloaded here: http://forum.xda-developers.com/showthread.php?t=803682
9) If you're not going to install a custom rom and you used an sbf that is not for T-Mo USA, you'll have to change the baseband frequencies. Install the baseband switcher app: http://forum.xda-developers.com/showthread.php?t=1052745 Open the app and click on the “Americas” tab, and select one of the “US T-Mobile” options. (The “US T-Mobile 3.4.2-107-9” option works well for me.) The phone will have to be rebooted again.
re: 2.3.6 Upgrade issue.
I may have made a mistake.
I recently updated my atrix to 2.3.6. It installed successfully but I decided to flash it back to 2.3.4, which I'm currently regretting.
When I turn my Atrix 4G on, It says 'failed to boot 1'.
If I hold the Volume up and power buttong it says:
'Failed to boot 1, PwrReason: Power_cut, Starting fastboot protocol support'.
Im tried to flash the roms using RSDLite:
att-2.3.4_pudding_preroot and also the
official 2.3.6
The error is:
Failed flashing process. Unable to retrieve interface handle.
I tried to unlock bootloader cmd, but wasn't successful.
Any ideas guys?
As an update, i tried to use fastboot to load images.
Instructions to root Atrix 4G running Gingerbread:
-----------------
Download and Extract Fastboot Files to your C: drive (Download Link)
Connect your phone to the computer via USB
Put your phone in fastboot mode (restart phone holding volume down button)
Open a command prompt and navigate to C:/moto-fastboot-win32
type “moto-fastboot.exe flash preinstall preinstall.img” press enter
---------------
it says:
sending preinstall OK
writing preinstall... Failed remote 00180004.
I can't see to write to boot, system or any component?
Do I need to unlock the bootloader? Sorry this stuff is all new to me, and trying to piece it together.
Please use the search, I faced the same issue, you will have to create a factory cable and using RSDLite, flash the 2.3.6, you cannot flash the 2.3.4
Sent from my MB860 using Tapatalk
Hi Tommy,
I saw you're thread but it wasn't clear what steps you took.
Did you modify the Atrix USB Cable in order to install a 2.3.6 sbf file using rsdlite?
I'm wondering if there is another way.
OP - Flash the 2.3.6 sbf file with RSD lite 5.6 - should get you back up and running just fine...
I tried flashing the:
1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012
and got this error in rsdlite
internal error while programming phone.
Then after that if I try it again, or try the pudding 2.3.4 one the error changes to:
Failed flashing process. Unable to retrieve interface ahndle 0x7027.
re: 2.3.6 Upgrade issue
First off let me say I know absolutely nothing of development but I figured I'd be brave enough to experiment any way. So I tried upgrading yesterday with partial success, there was no separate .img files at the time though . I'm rooted and have an unlocked bootloader; what I did was extract the zip file from the cache folder onto my PC then removed ap20bl.img seeing that I read all the horrors of possibly re-locking bootloader and bricking I then zipped the file and named it update.zip and booted the phone to CWM Recovery and tried installing that way. I realized after failing the install since it prompted that it couldn't find the ap20bl.img that there must me a script. Knowing that there'd probably be a size check I did this any way....used a bl.img from the 2.3.4 fruitcake and renamed it to ap20bl.img still failing therefore I assume that it really did check the file size. I then located the updater script and removed references to the ap20bl.img file. I tried install again this time saying something about E:\ unfortunately I don't recall exactly what.....so to take care of that I deleted the cache (probably a bad idea). That got rid of that error but from that point I got an error 6 ever since. I decided to reboot the phone which booted fine. Checked "About Phone" and it said the current version was 4.5.141, I was very happy about that; checked that the phone was still rooted and it was. Calls worked, bluetooth worked.....BUT ....it came time to check the wireless....."ERROR". Yip, no more WiFi. I rebooted to CWM and did a factory reset...rebooted again checked WiFi...now said "Turning on, Turning off, Error". So.......I rebooted to fastboot and sent the 2.3.4 radio (.91), rebooted and still got the error. I decided even though I read not to, to go back to 2.3.4 so I rebooted CWM, did the necessary wipes and reinstalled the 2.3.4 fruitcake then checked WiFi which now worked (or so I thought)....the connection dropped after a while then said error when I checked its status so I rebooted and it worked fine only to have the same issue again. I then did necessary wipes and tried Neutrino 2.1 EE seeing that it was the only ROM I had with me at work still having the same WiFi issue. At this time I haven't done anything else with the phone but hopefully this information will help developers or anyone else
Your only hope is the Motorola Factory Cable, yes it is configured differently, in it the red and brown cable are joined, please see my thread for reference, also you will find lot of articles on the internet, you will not be able to flash without it, been there, done that
Sent from my MB860 using Tapatalk
I have Motorola Bravo with 2.1 Update 1 ATT. Can anyone help me to upgrade it to CM7 from quarx?
I want to know what are the tools I can use to root, install recovery.
anidesh said:
I have Motorola Bravo with 2.1 Update 1 ATT. Can anyone help me to upgrade it to CM7 from quarx?
I want to know what are the tools I can use to root, install recovery.
Click to expand...
Click to collapse
Why dont you upgrade first to froyo?
Connect to internet, go to settings -> about phone -> I dont remenber the next
Else if you can upgrade via OTA update,
http://forum.xda-developers.com/showthread.php?t=1559109
and flash SBF with RSD Lite!
We will continue after you upgrade to froyo!
Thanks
Please excuse me for being lazy. I should have searched more before posting my query. I found your guide of upgrading from Froyo before posting my query.
Anyway... thanks once again.......
I will upgrade to Froyo and then upgrade to quarx CM7 build. [Does wifi hotspot and USB tethering works in quarx CM7 build?]
anidesh said:
Please excuse me for being lazy. I should have searched more before posting my query. I found your guide of upgrading from Froyo before posting my query.
Anyway... thanks once again.......
I will upgrade to Froyo and then upgrade to quarx CM7 build. [Does wifi hotspot and USB tethering works in quarx CM7 build?]
Click to expand...
Click to collapse
Of course, everything is working fine.
You can also use MIUI too everything is working , but I recommend CM7 it has official support from Quarx, ICS CM9 its officially supported.
I am able to upgrade to Froyo successfully using instruction provided in your thread. I am able to root also successfully using your instruction. But 2nd init Defy is not working. Whenever I install 2nd init Defy, my phone goes into boot loop. I have disabled USB debugging post install and restarted phone. I tried both latest version and stable version of recovery. In all cases, I am getting boot loop. Any pointers?
anidesh said:
I am able to upgrade to Froyo successfully using instruction provided in your thread. I am able to root also successfully using your instruction. But 2nd init Defy is not working. Whenever I install 2nd init Defy, my phone goes into boot loop. I have disabled USB debugging post install and restarted phone. I tried both latest version and stable version of recovery. In all cases, I am getting boot loop. Any pointers?
Click to expand...
Click to collapse
When you install 2init and you run it, you press on install recovery, whatever you want, I always choose lastest.
It will ask you for root permissions twice. Later when installed led notificarion eill show green.
Turn off the phone then turn it on when motorola logo is shown you will see notification light in blue, press vol down button, and thats all.
Everything is performed as you have said. At last step when I turn on the phone. I am not getting blue light, I am getting always Motorola Red Logo continuously [boot loop?].
Dont know whether its related but I will try putting my getting another SD card.
Thanks all your support.
anidesh said:
Everything is performed as you have said. At last step when I turn on the phone. I am not getting blue light, I am getting always Motorola Red Logo continuously [boot loop?].
Dont know whether its related but I will try putting my getting another SD card.
Thanks all your support.
Click to expand...
Click to collapse
Did you press volume down button when blue light?
It will go inmediatly to boot manager!
anidesh said:
I am able to upgrade to Froyo successfully using instruction provided in your thread. I am able to root also successfully using your instruction. But 2nd init Defy is not working. Whenever I install 2nd init Defy, my phone goes into boot loop. I have disabled USB debugging post install and restarted phone. I tried both latest version and stable version of recovery. In all cases, I am getting boot loop. Any pointers?
Click to expand...
Click to collapse
Leave Debugging enabled after 2nd-Init installs and restart.
anidesh said:
Everything is performed as you have said. At last step when I turn on the phone. I am not getting blue light, I am getting always Motorola Red Logo continuously [boot loop?].
Dont know whether its related but I will try putting my getting another SD card.
Thanks all your support.
Click to expand...
Click to collapse
Its not SD Card related. Did you update to Froyo with the OTA or SBF? I used the SBF myself and have never had any 2nd-init issues after installing it. One thing you can try is Factory Reset. Turn on the phone holding Power+Volume Up, then press Volume Up+Volume Down on the screen with a green triangle. Then select Wipe Data\Factory Reset. What this does is deletes everything on /data partition; old eclair data may still be there preventing the tools to work properly if you updated with OTA. Sometimes latent data is still left behind after flashing the sbf and this also helps with that as well.
Since you plan on installing custom roms, you can skip the Blur Setup by typing "eebluroffee" on the very first screen after flashing the sbf. Just hold down the menu button and it will bring up the soft keyboard. There's nothing to select to type into, just type the command and it will eventually work. Sometimes it takes a few tries to get it to work. Then just root and install 2nd-Init as usual.
Here is the link to the thread with the latest version of 2nd-Init Defy. The ones on our forum are outdated, but usually work perfectly (always for me).
Updated 2nd-Init 2.3 Thread
Thanks a lot. Finally I am able to install 2nd Init by replacing latest apk in installer created by josuearisty.
Thanks skeevy420 for the hint. Now I am able to upgrade bravo to latest CM7 from Quarx.
Mine is the oldest Bravo (its a engineering sample from Motorola).
anidesh said:
Thanks a lot. Finally I am able to install 2nd Init by replacing latest apk in installer created by josuearisty.
Thanks skeevy420 for the hint. Now I am able to upgrade bravo to latest CM7 from Quarx.
Mine is the oldest Bravo (its a engineering sample from Motorola).
Click to expand...
Click to collapse
If it is an engineering sample, it may have an unlocked boot loader...
marquae11 said:
If it is an engineering sample, it may have an unlocked boot loader...
Click to expand...
Click to collapse
I first though that as well. But if it did, it lost it by flashing the sbf and going retail.
@anidesh -- if you've never, ever, ever flashed an sbf on you're phone can you run the following two commands on Android Terminal Emulator without quotes "su" then "dd if=/dev/disk/mmcblk1p15 of=/mnt/sdcard/boot.img" and upload the boot.img to Mediafire or similar.
If you have flashed the sbf, then don't bother since if you had an unlocked bootloader you just lost it.
I already flashed retail sbf so I lost it. I have one more engineering sample. Its battery connection has problem. If I am able to fix it then I will get image you are asking.
anidesh said:
I already flashed retail sbf so I lost it. I have one more engineering sample. Its battery connection has problem. If I am able to fix it then I will get image you are asking.
Click to expand...
Click to collapse
Have you tried making a MacGyver Cable? Although that won't work if it is a problem with the internal connection.
If it is just a battery connection problem then an OEM Motorola Factory Cable will work -- they send power directly to the phone where the standard usb cable only sends power to the battery. Only problem is they cost around $40 USD. Although if you flash roms a lot they are worth buying since you can flash the sbf and roms with 0% battery. There are sites with mods on how to make one, just google and you'll find one. If I remember correctly, Epsylon3 has a post with a tutorial on how to make one.
skeevy420 said:
Have you tried making a MacGyver Cable? Although that won't work if it is a problem with the internal connection.
If it is just a battery connection problem then an OEM Motorola Factory Cable will work -- they send power directly to the phone where the standard usb cable only sends power to the battery. Only problem is they cost around $40 USD. Although if you flash roms a lot they are worth buying since you can flash the sbf and roms with 0% battery. There are sites with mods on how to make one, just google and you'll find one. If I remember correctly, Epsylon3 has a post with a tutorial on how to make one.
Click to expand...
Click to collapse
If someone wants to try new items to MIUI between this...
link..http://forum.xda-developers.com/showthread.php?t=1535035
skeevy420 as work with the rom pikachu edition
Hello,
hope you can help me.
today i tried (noob as i am) to downgrade my phone from JB to GB. for some reason i needed (wanted) to flash the kernel and somewhere in that process when i connected my phone to my pc in the wrong way, windows told me to better format it. i was unable to connect to RSD lite and tried a bunch so i deceided to do so. and all was gone. stuck on motorola logo and stuff. finally managed to flash kernel with rsd but now i cant install any roms. im not alowed. and have the most basic bootinstaller ever (only 4 options).
i feel like i need to root my phone again but cant figure out how. or maybe the solution is something else i dont know. can anyone help me with this?
marzell88 said:
Hello,
hope you can help me.
today i tried (noob as i am) to downgrade my phone from JB to GB. for some reason i needed (wanted) to flash the kernel and somewhere in that process when i connected my phone to my pc in the wrong way, windows told me to better format it. i was unable to connect to RSD lite and tried a bunch so i deceided to do so. and all was gone. stuck on motorola logo and stuff. finally managed to flash kernel with rsd but now i cant install any roms. im not alowed. and have the most basic bootinstaller ever (only 4 options).
i feel like i need to root my phone again but cant figure out how. or maybe the solution is something else i dont know. can anyone help me with this?
Click to expand...
Click to collapse
are you able to put your phone in bootloader mode ? and witch version you use to flash your phone with RSD use one of those
http://sbf.droid-developers.org/umts_milestone2/list.php
yes i used the retail british 2.4
i am able to flash sbf file but it still wont go past moto logo and stock recovery cant install any roms. not allowed to install or something like that.
1 get to recovery mod (x button+power) do a wipe data then full reset
2 update the last boot loader with rsd
3 repeat step 1
4 sbf your phone with retail 2.3.6 like retail brazil then be patient and your phone will power up after many reboot (before that prepare (bootstrap.apk) in memory card)
5 root your phone using super one click then install bootstrap and get bootstrap recovery and you can install CM10 now it will make your phone boot normally
jakkokko said:
1 get to recovery mod (x button+power) do a wipe data then full reset
2 update the last boot loader with rsd
3 repeat step 1
4 sbf your phone with retail 2.3.6 like retail brazil then be patient and your phone will power up after many reboot (before that prepare (bootstrap.apk) in memory card)
5 root your phone using super one click then install bootstrap and get bootstrap recovery and you can install CM10 now it will make your phone boot normally
Click to expand...
Click to collapse
thank you i will try this. the battery is currently drained, so i need to recharge first. using wall charger (usb unit) but it didnt charge yet. keeps telling me the batt is low. any tips for that? only thing i found on here is to use a wall charger.
use this for low battery problem
http://forum.xda-developers.com/showthread.php?p=10163846
jakkokko said:
use this for low battery problem
http://forum.xda-developers.com/showthread.php?p=10163846
Click to expand...
Click to collapse
this worked as far as the batery problem, pita to do thou. now hope i can root the thing, since i did not yet succeed to run the adb drivers..
update: well, i fear the worst. after the last time flashing the sbf it wont turn on anymore. guess i did screw up the wire-DIY. will update if there is any good news. but for now it seems i should start looking for a new phone.,.
Hi!
I know that that I am mentioning now very old device as Motorola Defy MB525 green lense.
I wanted to flash Cyanogenmod 10.1 again in my Defy. I did full wipe and removed some folders on SD card reffering to old apps.
And it seems I messed up with Clockworkmod Recovery folder on SD and I left myself without it. And I tried to reinstall it using official guide found here: wiki.cyanogenmod.org/w/Install_CM_for_jordan[/url]
But I did not unpack all the files, so the installation was not fulfilled and I got like empty Android boot menu 0.6.1 without possibility to boot an operating system or to do anything (got errors whatever I choose: E:Error in /system/bootmenu/script/recovery.sh)
I have read tons of online materials and forums, and I could only restore stock Defy ROM 2.3.4 using RSD lite.
And I didn't find solution how to reinstall the boot menu :crying: So that is why I am asking you for help.
I can run only Download Mode and this useless Android Boot Menu.
How to reinstall Android boot menu/install custom recovery back?
I like my Defy and I do not want to put it in the drawer yet
Thank you in advance!
Vixificent
The bootmenu is housed in the partition system.
All you have to do is flash the stock firmware, root with Framaroot (app) and install the bootmenu and recovery with 2nd init (app). After this simply download the rom and gapps, you do wipe cache, data, dalvik cache and flash it (first rom, then gapps).
cristiand391 said:
The bootmenu is housed in the partition system.
All you have to do is flash the stock firmware, root with Framaroot (app) and install the bootmenu and recovery with 2nd init (app). After this simply download the rom and gapps, you do wipe cache, data, dalvik cache and flash it (first rom, then gapps).
Click to expand...
Click to collapse
Thank you for your reply and suggestion! But the thing is that I cannot boot the device, so usage of any apk is not possible. When I run my Defy it goes directly to Android Boot menu 0.6.1, which is not installed properly (source files missing, eg. ".sh" files).
Should I try to root it via computer? Then, how to do it with only Download Mode available?
Any help would be appreciated!
Vixificent said:
Thank you for your reply and suggestion! But the thing is that I cannot boot the device, so usage of any apk is not possible
Click to expand...
Click to collapse
YOu can recover your device using an appropriate .sdf file and a program called RSD Lite. There are many how-tos on this - the first one I found was http://www.locslikes.com/motorola-defy/unbrick-and-restore-to-default-sbf/. You'll also find a number of tutorials on these forums.
robbak said:
YOu can recover your device using an appropriate .sdf file and a program called RSD Lite. There are many how-tos on this - the first one I found was http://www.locslikes.com/motorola-defy/unbrick-and-restore-to-default-sbf/. You'll also find a number of tutorials on these forums.
Click to expand...
Click to collapse
Quite a late answer, but the solution offered by robbak worked perfectly! Thank you!
Vixificent said:
Quite a late answer, but the solution offered by robbak worked perfectly! Thank you!
Click to expand...
Click to collapse
I have a similar issue. How did you do the fix you used? The SBF files don't seem to be on the site you were referred to anymore.
Years ago, my unmodified (not rooted) Defy (running Android 2.2.1) started to boot loop, so I eventually did a factory reset. That worked for a while, although certain apps were suddenly no longer compatible) and then suddenly the defy froze on the Moto logo (not even cycling to the Blur screen) and I could no longer get to the reset screen.
However I could still get to the bootloader, so I tried to use RDS lite.
I got one sbf to say it passed, but the phone did not reboot. (I could only find 2 SBF's for the US and only got one to work). Now RDS will detect whether the phone is on or off (and if on I'll get a white LED) and I can flash the sbf still, but otherwise the phone is completely bricked - can't get to reset OR bootloader screen.
When I plug the phone into the USB the white LED comes on, but I can't raise ANYTHING on the screen (reset screen or bootloader screen, holding down the volume up or down w/ the power button). However pressing the power button alone does cause the computer to recognize hardware is plugged in, or alternately disconnected. RSD tells me a device is connected, but the only info given is the bootloader version and AP ID info (whatever that is). However, when I load the SBF, the phone lights up and says SW update in progress...
RSD tells me the phone is being rebooted and has passed, but screen goes dark and all I see i the white LED again.
I tried these two SBFs:
T-Mobile_MB525_6.19.0_1FF.sbf
JORDN_U3_6_36_0_SIGNED_USAJRDNTMOB1B4B5DE1028_0R_J ORDANTMO_P022_HWp3_Service1FF.sbf
Only the 1st one works.
I am not that tech savy regarding Android, so i am looking for some help.
Thanks!
Hi DefyVictim,
I understand your concerns - the restore process is a little bit complicated, but still not impossible. There is a strange procedure how to get your phone connected in such a way that RSD lite sees it. In the link given by robbak there is a video which is an exactly described tutorial. Did you follow it carefully?
It goes like - you need to FIRST get the bootloader and then connect it to the PC. If I understood it right, you tried to get the bootloader after you got the phone connected - which did not work.
I had a similar issue but finally figured it out. Oh, and there was just another thing - the battery was too low, so I had to do quite risky McGyver method to charge the battery somehow (no charging when your phone is bricked!), but be careful, this is potentially dangerous. Nothing happend for me, because I charged my phone for a minimum of time (like half an hour) to get it working.
Check this thread if you face battery low warning:
https://forum.xda-developers.com/showthread.php?t=892026
I know now it is a pain to get a SBF file, but not sure if the T-mobile should be working unless your phone wasn't coming from T-mobile (?)