Guys,
First of all, hello to all! So, I followed a tutorial to install Froyo on my Defy. Now I'm stuck with my phone trying to boot as soon as i put the battery on, but it never makes it past the "M". I can get into recovery. I wiped data, cache and tried to install the "update.zip" but it aborts saying "signature verification failed." I have the boot file (that was the next step) to install using RSDlite 4.9 but the phone is not even recognized any of my USB ports. Any ideas? Thanks to all in advanced.
press volumn up buton and power button on boot , once you saw the backlit is on , release the button , you will see the rsd litle showing your usb .
dont worry . i think it is your first time to use RSD only
yea i been through that ( doesnt work on vista )
you need to install rsd lite and 2.51 UK Firmware ( no usa )
google it and you will find it or on this forum
install usb driver from motorola webiste
install rsd lite
put uk firmware in ... C drive/ program files / motorola / rsd lite
install driver
If your phone is stuck on " M " then pull battery out
turn on and quicky press power + vol up ( i think ) before M even appear
wait till it say your boot loader and your battery
plug phone in
start rsd lite
on ... look up your uk firmware that you you recently put in rsd lite folder
then you should see your phone connected on the 1 slot
then hit start or something and wait it out .
Thanks guys! But I've been messing around with this thing for so long, I drained the battery. I had to run it up to the local phone store to get it charged. I'll pick it up in a couple of hours and give your advice a try.
Hey guys! it worked! I'm up and running. Now, anyone has a link to bypass this Welcome to Motoblur screen. Is there a Custom Froyo or Gingerbread Rom out there without Motoblur?
Alright... I'm up and running, but no camera!!! Heck, it was a learning experience. I guess I'll go back to 2.1 now. LOL
So the Chinese ROM was rooted. I installed Clockworkmod and restored from the backup i had made of the original 2.1 OS. I'm back to a rebooting phone not making it past the "M" I went back to RSDlite and realized the boot file said 2.2 only. Can anyone assist me finding the right one to go back to original. I haven't been able to find a thread about reverting back to original.
The more I read, the smarter I get seems like the only thing I'm missing here is the SBF file for my original T-Mobile OS. I'm looking at the motorola website, but I can't find it. Can anyone point me to it? Thanks all! Oh yeah, this is the first android phone i mess with so my apologies.
There is no us sbf file. You have to flash a uk version and restore 3g with the posted fix. You can find the links to available sbf files on this forum. They are not available thru moto's site.
Sent from my ME525 using Tapatalk
Just to make sure I got it right. After using clockworkmod to restore to my factory backup, I need to use the UK sbf to be able to boot to it. Correct?
I found the sbf for Central Europe with no Motoblur. Does anyone know of any issues with it?
well the only way to fix this if you previously backed up your rom/files with recovery ( good thing i did this ). If not then you have to live with what you got.
I backed up my original firmware using clockworkmod. I flashed to the Chinese 2.2 but my camera didn't work. Since the camera is important to me, the Chinese Froyo was a deal breaker. I installed clockworkmod again and "recovered" from my original backup but now my defy won't boot. Did I miss a step?
Your data from the backup may cause issues when rolling backwards. Install an eclair sbf, then restore. That worked for me.
On another note there is a fix for the camera. Check the forums.
Sent from my ME525 using Tapatalk
Bricked Defy and not recognized by my USB
I also bricked my phone when going back to stock from cm7. My phone is able to go into boot loader. But it is not recognized by my desktop PC/RSDlite. I tried in linux with SBF_Flash. I tried with my laptop also. no luck . anyone please help me!
arulshoponline said:
I also bricked my phone when going back to stock from cm7. My phone is able to go into boot loader. But it is not recognized by my desktop PC/RSDlite. I tried in linux with SBF_Flash. I tried with my laptop also. no luck . anyone please help me!
Click to expand...
Click to collapse
Just try and install the Motorola Drivers in your desktop and open RSDLite and press 'show devices' button. It will surely show the details of your phone.
Then point RSDLite to the stock SBF and flash away.
kvigneshkrish said:
Just try and install the Motorola Drivers in your desktop and open RSDLite and press 'show devices' button. It will surely show the details of your phone.
Then point RSDLite to the stock SBF and flash away.
Click to expand...
Click to collapse
Thanks! Vignesh. But i have drivers installed. Tried uninstalling and reinstalling drivers. But did not help
Edit:
I missed to mention. My defy did not connect to desktop even before bricking.
arulshoponline said:
Thanks! Vignesh. But i have drivers installed. Tried uninstalling and reinstalling drivers. But did not help
Edit:
I missed to mention. My defy did not connect to desktop even before bricking.
Click to expand...
Click to collapse
If you hear the USB plugged in sound in your Pc, it's a messed up driver installation. If you don't hear the sound, it can be a bad cable, or a faulty microusb port (assuming that your pc usb works fine). Try once in a different pc and with a different microusb cable.
nsm1234 said:
If you hear the USB plugged in sound in your Pc, it's a messed up driver installation. If you don't hear the sound, it can be a bad cable, or a faulty microusb port (assuming that your pc usb works fine). Try once in a different pc and with a different microusb cable.
Click to expand...
Click to collapse
I do not hear any sound from desktop/laptop.
I think I stuck in boot loop. When I try to power on the phone, it just shows CM7 boot logo for few seconds then restarts again shows the boot logo... this happens continually. When I try to enter into recovery, it does not go to CWM recovery instead it goes to stock recovery. I am still able to enter into boot loader. In boot loader, it says battery OK connect USB to program. When I connect USB, it is recognized by phone and says transfer mode: USB. But my PC does not shows up the phone.
I tried re-installing drivers and RSDlite many times but no luck. But I have nandroid backup of CM7. Is there any possibilities to enter into CWM recovery?
Any help is appreciated.
Edit:
I tried even different USB cables and PCs also.
I've been researching this problem all night/morning and I'm at my wits end Hoping you guys can help me think through it..
First things first: I'm using a macbook, with the most updated version of the SDK platform tools. My nexus 7 was already rooted and flashed with a 4.4.2 ROM.
I tried to flash the Lollipop factory image onto my 2012 Nexus 7 Wifi yesterday by running './flash-all.sh'. First few times, it errored out (alternating between 'broken pipe' errors and fastboot just flat out not seeing my device). Finally, after rebooting my laptop and continuously running 'fastboot devices' until a device Id actually turned up, I managed to run ./flash-all.sh
The script progressed, errored out on flashing the boot loader, successfully erased pretty much everything including recovery, flashed the system image, and then failed while trying to validate the bootloader version (since it had errored out).
Now I'm stuck in a situation where 'fastboot devices' does not return anything (I've tried 3 different USBs and every single port on 2 different macbook + a linux tower) and I can't get into recovery because it errors out with a 'boot failed' message over the 'Google' icon screen.
I've ruled out the possibility of a driver issue since I'm on a macbook, although I'm going to try installing hte SDK onto my Windows 7 tower later tonight, just to see what happens. Can anyone think of anything else I can try to recover my Nexus 7? I dont even care about flashing Lollipop will do haha.. even stock is fine.
So for whatever reason I cannot unlock my boot loader and I cannot download most apps. As of now I have deleted every app except for the system apps. I'm rooted with towelroot, and I have approx 3gb free for downloading apps. I can download clash of clans, but I can't download anything else. I've tried to clear my cache. I've tried to uninstall the updates from the play store. I even moved everything (pictures downloads and music) to my SD card. Nothing will work. I thought (because I don't know much about this) maybe if I unlock my boot loader and get a custom ROM I'll be able to download stuff. I can't unlock my boot loader. When I'm in fast boot mode and try running fastboot devices nothing shows up. I also tried RSDlite and the only way a device shows up is if the phone is turned on. When I try to change it to bootloader from RSDlite itself my phone will go to bootloader but RSDlite doesn't acknowledge that its in fast boot. Can anyone help me out..? Or should I just deal with it and save up some money and get a new phone?
Have 6.4.0 drivers installed, RSD Lite 6.1.6 installed, phone in fastboot mode connected via USB to computer under Windows XP or 7, and that's it! You're ready to flash )
What step you stuck on?
I'm using windows 8 and I know theres the problem, so I looked it up and fixed it. I have RSDlite 6.1.6. And for whatever reason it doesn't show my device when it is in fastboot mode. It'll show the device when its turned on, but in fastboot nothing shows up.
ripplyxion said:
I'm using windows 8 and I know theres the problem, so I looked it up and fixed it.
Click to expand...
Click to collapse
Fixed how? I couldn't get Win 8 to work with RSD.
I have a rooted RP2 MR1 on android9. I tried to unroot the device since I am trying to sell the phone. I went into magastik and clicked Complete Uninstall. After the phone restarted it booted into Recovery Mode. I cannot get past this. I can go into the Bootloader from Recovery Mode. I have tried ADB but my phone isn't be recognized.
Not sure what I am doing wrong, or if this can be fixed. Any help is appreciated!
danielahl137 said:
I have a rooted RP2 MR1 on android9. I tried to unroot the device since I am trying to sell the phone. I went into magastik and clicked Complete Uninstall. After the phone restarted it booted into Recovery Mode. I cannot get past this. I can go into the Bootloader from Recovery Mode. I have tried ADB but my phone isn't be recognized.
Not sure what I am doing wrong, or if this can be fixed. Any help is appreciated!
Click to expand...
Click to collapse
To get my phone to be recognized, I had to try two different cables, as well as follow this video to install the standard adb drivers.
New user so I can't post the full link, so add this after the .com/ of youtube
watch?v=1TxjSa8gemM
From there look up the stock ROMs installer for the RP2 and follow the instructions for that.
I just ran into the same problem. I uninstalled through magisk then rebooted. now i can get to recovery and bootloader but phone wont boot. I tried reinstalling factory image from razer's website but adb gets stuck at waiting for device. I have used 6 differnt drivers and 5 different cables including a samsung sync and transfer cable i went out and bought today hoping the cable was the issue. any update on how you fixed it or advice from anyone else would be greatly appreciated as this is my only phone.
vrracing said:
I just ran into the same problem. I uninstalled through magisk then rebooted. now i can get to recovery and bootloader but phone wont boot. I tried reinstalling factory image from razer's website but adb gets stuck at waiting for device. I have used 6 differnt drivers and 5 different cables including a samsung sync and transfer cable i went out and bought today hoping the cable was the issue. any update on how you fixed it or advice from anyone else would be greatly appreciated as this is my only phone.
Click to expand...
Click to collapse
Are you using the ADB/Fastboot that Razer recommends on their site? I had this problem too until I updated my ADB/Fastboot.
Yeah, I feel like an idiot. It's been a while since I've used adb. I ended up moving the fastboot file into the same folder as the the image I was trying to flash and had my phone working 30 minutes later. I meant to reply but it was 6 am and I went to sleep. Lol
Hello everyone,
I have a very peculiar problem with getting my Essential Phone to work again. It was lying around for roughly two years as I switched to another phone. Seeing as one of my relatives needs a new phone and has really low requirements I thought I could try to set it up again. I downloaded the official drivers again (Version 1.0.0 I think) as well as the last official release of fastboot images (February 2020).
Before I switched to a new Phone I had the Essential running with Lineage OS and remember wiping it with fastboot -w after I got the new device.
Now when I try to flash anything the device won't respond. It shows up when fastboot devices is used in the bootloader, but all fastboot commands get no answer whatsoever. I then switched from the official fastboot drivers to the latest android drivers which then gave me the sending x to y message when I try to flash anything, but nothing actually happens.
Interestingly enough, I can reboot to bootloader just fine and the Lineage Recovery is still accessible eventhough it shows an:
E: Failed to bind mount /mnt/staging/emulated/media/0 on storage/emulated: No such file or directory
on the bottom which leads me to believe that my device partitions may be corrupted outside of the recovery partition and the phone is bricked. In recovery adb commands can be used and I can reboot to bootloader for example.
When trying to sideload via the "Appy Update" function of the Lineage Recovery, I get an:
Error applying update: 26 (ErrorCode::kDownloadMetadataSignatureMismatch))
everytime. I tried different methods and Roms but nothing worked so far.
Can anyone help me with regards to bypassing signature verification entirely or point me in the direction of another solution?
Thanks for reading, I hope you have a nice day!
McMeth said:
Hello everyone,
I have a very peculiar problem with getting my Essential Phone to work again. It was lying around for roughly two years as I switched to another phone. Seeing as one of my relatives needs a new phone and has really low requirements I thought I could try to set it up again. I downloaded the official drivers again (Version 1.0.0 I think) as well as the last official release of fastboot images (February 2020).
Before I switched to a new Phone I had the Essential running with Lineage OS and remember wiping it with fastboot -w after I got the new device.
Now when I try to flash anything the device won't respond. It shows up when fastboot devices is used in the bootloader, but all fastboot commands get no answer whatsoever. I then switched from the official fastboot drivers to the latest android drivers which then gave me the sending x to y message when I try to flash anything, but nothing actually happens.
Interestingly enough, I can reboot to bootloader just fine and the Lineage Recovery is still accessible eventhough it shows an:
E: Failed to bind mount /mnt/staging/emulated/media/0 on storage/emulated: No such file or directory
on the bottom which leads me to believe that my device partitions may be corrupted outside of the recovery partition and the phone is bricked. In recovery adb commands can be used and I can reboot to bootloader for example.
When trying to sideload via the "Appy Update" function of the Lineage Recovery, I get an:
Error applying update: 26 (ErrorCode::kDownloadMetadataSignatureMismatch))
everytime. I tried different methods and Roms but nothing worked so far.
Can anyone help me with regards to bypassing signature verification entirely or point me in the direction of another solution?
Thanks for reading, I hope you have a nice day!
Click to expand...
Click to collapse
I've been reading around a little, it seems like it could be a recovery issue? try the official lineage recovery if you're not already. If you can get fastboot working at all try to reflash the stock rom and go from there.
I had a similar problem. Use a windows computer with the essential drivers (you can download from reddit) and use the official cable
DO NOT use the cable supplied with the Essential phone for data transfer, it is likely to brick your phone. Use a high quality one from a reputable manufacturer!