I have had a Defy+ for a year and in general it has run without issue. I recently had a problem with being unable to get a GPS fix and Motorola advised me to do a factory reset. This appeared to work in respect that I got my GPS fix back but my phone would randomly reboot. It seemed to reboot when the data signal was poor. Motorola said it was most likely an app. It wasn't because after another factory reset it kept rebooting without me installing any of my own apps. I gave up and have gone back to my old Defy which works fine (with the same SIM card I had in the Defy).
Tonight I decided to get my Defy+ back to it's original state to see if that made any difference as I had tinkered with a few of the system apk files. Having looked up on here I have installed RSD Lite, Motorola drivers, downloaded the UK retail 2.3.6 rom from here http://sbf.droid-developers.org/phone.php?device=28 and put the Defy+ in Bootloader mode. Running RSD Lite in administrator mode and with the SBF file renamed to Defy.sbf and in the PC root directory I get the following error log :
22:31:43, June 23, 2014
Line: 902
ERROR: The file selected is an invalid superfile.
Please enter in a valid superfile.
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\PST_FP_FlashFileIO.cpp
22:31:43, June 23, 2014
Line: 552
ERROR: The superfile specified does not exist
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
On the face of it the SBF file appears to be possibly invalid. But I can't see anywhere else to get it from.
It's ages since I tinkered with the Defy so I am a bit rusty on this. Anyone any ideas?
Related
Hi all,
My sister's Defy+ was stuck in bootloop, she tried the usual wipe cache, wipe data/factory reset but it didn't work. When I got it I tried it again and the data wipe never actually finished (the battery got empty after half an hour)
I charged it and tried to flash Retail French SBF from sbf.droid-developers.org / umts_jordanplus / list.php
After a while, during "Flashing Code Group 39", it just fails with the following error:
Code:
ERROR: Flash failure: Phone[0000]: Error flashing subscriber unit. Device API Error: 0xE003003F Address: 0xBFA54800 Command: ADDR (Error Code: e003003f),
Detailed Error Details: Direction of the Error=2000, Command Value=200000, Code Group Number=39
The phone is now stuck in bootloader with "code corrupt". I tried to flash it again but I always get the same error, with a different address but still in code group 39.
Do you know anything I could try ?
I am afraid it is a hardware failure -- to me it looks like the flash memory is corrupted or something, what do you guys think ?
Anne-Laure said:
Hi all,
My sister's Defy+ was stuck in bootloop, she tried the usual wipe cache, wipe data/factory reset but it didn't work. When I got it I tried it again and the data wipe never actually finished (the battery got empty after half an hour)
I charged it and tried to flash Retail French SBF from sbf.droid-developers.org / umts_jordanplus / list.php
After a while, during "Flashing Code Group 39", it just fails with the following error:
Code:
ERROR: Flash failure: Phone[0000]: Error flashing subscriber unit. Device API Error: 0xE003003F Address: 0xBFA54800 Command: ADDR (Error Code: e003003f),
Detailed Error Details: Direction of the Error=2000, Command Value=200000, Code Group Number=39
The phone is now stuck in bootloader with "code corrupt". I tried to flash it again but I always get the same error, with a different address but still in code group 39.
Do you know anything I could try ?
I am afraid it is a hardware failure -- to me it looks like the flash memory is corrupted or something, what do you guys think ?
Click to expand...
Click to collapse
Yes, I'm afraid you might be right, it is mostly a hardware failure.
Sent from my Nexus 7 using Tapatalk
Also before giving up, try flashing dfp231 (any region). I was getting this error on a different group, and that helped my phone get back to life. Otherwise, it's gone
Sent from my MB526 using Tapatalk 4
I checked and the one I tried to flash was actually dfp231... so I guess it's time to give up .
Thanks to both of you for your input, I wanted a second opinion before anouncing the bad news to my sister.
Anything I should do to mark the thread as answered ?
Not really, though you could change the thread title to add solved to it
Sent from my MB526 using Tapatalk 4
I remember similar faults when corrupting a Defy in the past, the reason was an inconsistant SBF.
In may case the SBF was curruptedt within the download network.
I tried one SBF, I tried a socond one, a third. Three or four SBFs were faulty.
You can try another download channel with another hardware and you can try several SBFs.
But always confirm a loaded battery, maybe your battery doesn't funtion very well and caused partition faults.
You may try a battery from a working Defy.
bianchifan said:
I remember similar faults when corrupting a Defy in the past, the reason was an inconsistant SBF.
In may case the SBF was curruptedt within the download network.
I tried one SBF, I tried a socond one, a third. Three or four SBFs were faulty.
You can try another download channel with another hardware and you can try several SBFs.
But always confirm a loaded battery, maybe your battery doesn't funtion very well and caused partition faults.
You may try a battery from a working Defy.
Click to expand...
Click to collapse
Code corrupt in bootloader usually means a damaged eMMC.
I have a Motorola Droid Razr M (XT907) that upon last reboot decided to stop at the Motorola Logo and won't continue the boot process. I can get into Fastboot and Recovery, but so far, neither has been helpful. I have read several threads concerning similar issues, but have not found a solution yet. This phone has not been previously rooted or unlocked and to my recollection the latest OTA has been installed.
When in Fastboot, it says Device is locked. Status code 0.
I'm working on a Windows 7 PC. I have installed Motorola Device Manager and the Motorola USB drivers. When the phone is in Fastboot, it is recognized in my device manager as Mot Single ADB Interface. When I run Motorola Device Manager it replies:
There are no updates for your device at this time.
Current Version:
98.12.4.xt907.verizon.en.us
I have also installed RSD Lite version 6.1.5. When I run it, it shows my connected device, however all of the fields look so:
ESN: N/A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: N / A
DRM Version: N / A
I have not been able to find the correct FXZ image to repair the phone and fear it may well be lost. I'm only 12 days away from phone upgrade eligibility and it's cost prohibitive to upgrade early, so I'd like to repair the phone enough to use it for the next 12 days.
Any and all suggestions would be great.
Thanks
Go through this threadhttp://forum.xda-developers.com/showthread.php?t=2869432 thoroughly. It contains everything you need to know. In short, flash your phone to stock KitKat 4.4.2 the .10 build, not the .15 build, unlock your bootloader and then it's up to you whether you continue on stock or flash a custom ROM. Do check (http://forum.xda-developers.com/showthread.php?t=3042687) that you have the latest drivers and the latest version of RSD Lite installed and if you have trouble with flashing check to make sure you're using the correct cable...
My Sons Moto X Play (UK sim free XT1562) this morning was showing a bootloader screen with "Start Up Failed" then "Your device didnt start up successfully. Use the Software Repair Assistamt on computer to repair your device". Then further down it says "hab check failed for boot / failed to verify hab image boot / failed to validate boot image". I'm guessing an update occured overnight which failed somehow?
Anyway, found a copy of the image file "X_Play_UK_Retail_XT1562_LPD23.118-10_CFC.xml.zip" and popped it on a SD card. Started boot loader, changed to recovery mode (stock UPD23.118-10), choose "apply update from sdcard" but get the message "Internal and external memory cannot be mounted". Trying it again gives "E:error opening /sdcard: Permission denied". Tried a wipe data/factory reset and wipe cache then repeat, but get the same messages.
I'm at a bit of a loss now. Any help would be much appreciated. Thanks
I would flash stock rom with RSDLite from the computer. If you dont want it to wipe everything make sure to edit the flashfile.xml and servicefile.xml and remove <step operation="erase" partition="userdata"/> and <step operation="getvar" var="max-sparse-size"/>
You will lose root and custom recovery after that though.
This message appears to me once and I reflashed with RSDLite, and until now, everything is ok
Thanks guys. Couldn't get RSDLite to recognise the phone though.
Then noticed that the image I'd downloaded was an older version (5.1.1) of android. Managed to find a new 6.0.1 version here. Still not working with flash from SDcard, but got reading about ADB, installed it and flashed each part of the rom seperately and now it works. Hooray!
Got another problem now - the phone is insisting on using a google account previously used on the phone. I know my sons email address and password which I verified works on the PC, but the phone just loops round and asks for it again each time I enter it. Doesn't seem to be an option to skip for now either - very weird!
bacus said:
Thanks guys. Couldn't get RSDLite to recognise the phone though.
Then noticed that the image I'd downloaded was an older version (5.1.1) of android. Managed to find a new 6.0.1 version here. Still not working with flash from SDcard, but got reading about ADB, installed it and flashed each part of the rom seperately and now it works. Hooray!
Got another problem now - the phone is insisting on using a google account previously used on the phone. I know my sons email address and password which I verified works on the PC, but the phone just loops round and asks for it again each time I enter it. Doesn't seem to be an option to skip for now either - very weird!
Click to expand...
Click to collapse
Make sure to install the moto x play drivers prior to opening RSDLite. You also have to be in download mode in the recovery options.
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Clearly your rom has a problem explaining why the email security loops unless you arent connected to internet...
Did install the moto drivers when I tried RSDLite but no good. Anyway, that's not a problem now since I've got firmware on the phone and it now boots.
The issue with it not accepting the password for the google account has probably been made worse by me. In my frustration, I changed the google password. I've now read that after you do this, you have to wait 72 hours before you can re-auth a phone with that account. Shame. Will now wait and see what happens after that.
Thanks again
Update - after waiting the 72 hours, the phone has now accepted the new google account password so we're back in business.
My son was very happy to get his phone back.
Thanks all
Hi everybody. For some reason, I got an unknown country code after trying to update to Android N and failing in root (I did something wrong and endeded in a bootloop) My TWRP of the stock N does not work and stuck in lenovo logo. I returned to my last working TWRP and everything worked ok except that I couldn't update because an error caused by not having a country code. I tried a lot of things but in the end, I restore the tablet to stock. I did the first update OTA just to check, and it worked. I did the second via ADB, but it resulted in something like /country reported in the tablet (something like, easyimage code = ), and I lost the country code again. Trying to change with ####6020# results in an error about cannot find OTA patch on sd card. I read that copying easyimage.zip to the sd card worked on other tablets to change the country code, but not for me, I always get the error. Does anybody known how to restore the ability to change the country code, without going again to stock and start over?
Acorrales said:
Hi everybody. For some reason, I got an unknown country code after trying to update to Android N and failing in root (I did something wrong and endeded in a bootloop) My TWRP of the stock N does not work and stuck in lenovo logo. I returned to my last working TWRP and everything worked ok except that I couldn't update because an error caused by not having a country code. I tried a lot of things but in the end, I restore the tablet to stock. I did the first update OTA just to check, and it worked. I did the second via ADB, but it resulted in something like /country reported in the tablet (something like, easyimage code = ), and I lost the country code again. Trying to change with ####6020# results in an error about cannot find OTA patch on sd card. I read that copying easyimage.zip to the sd card worked on other tablets to change the country code, but not for me, I always get the error. Does anybody known how to restore the ability to change the country code, without going again to stock and start over?
Click to expand...
Click to collapse
hi . try to dial *#*#682#*#* and let me know
Sent from my SM-A520F using Tapatalk
Good afternoon.
Finally, after posting this thread in March, I had enough time for try to update my Huawei P8 Lite. As pointed before, I was coming from Compilation ALE-L21C40B181.
I used Firmware Finder for Huawei to check the Telefonica Spain update to Android 6.0, and found the version is ALE-L21C40B508.
I downloaded the ROM in two ways: Using the App to force a VPN connection and download it, and using this webpage.
The update.zip I downloaded from Firmware Finder didn't worked, as it failed at 5%.
I copied this failed update.zip from the folder where it downloaded, to dload_ota, and tried to do a Local Instalation. It didn't recognized the file.
I copied it to External SD>dload and it recognized it. Tried to update, and again: Failed at 5%.
Finally, I decided to use the web-downloaded .zip, and replaced the External SD faulty file, but didn't deleted the dload_ota faulty file.
When I used the B508 downloaded from Fordroid, it worked amazing! However, as the .zip file is very heavy, I tried to delete them.
Guess what? I can't delete the dload_ota faulty .zip
Also, when I checked I lost the Root Access, I thought in a probably easy way to root it. Following what I learned from my Motorola XT907, I tried pressing Vol Up + Vol Down + Power to enter to Bootloader Mode, before checking on internet the tutorials.
Something weird happened: IT TRIED TO UPDATE AGAIN
Someone knows how to solve both issues? (I will try to find the rooting method after, but now I want to solve both the .zip undeletable file + update retrying)
I just did a Factory Reset to find if that could solve the problem (and believe me: I didn't wanted to do it in any way), and the file dissapeared. I don't know what was going on, but everything solved with a Factory Reset
Now I'm wondering why the phone told me my phone is Rooted, if I'm using a Stock ROM ._. but I'll find that later.