Hi, I unfortunately don't know a lot about what I am doing here (the root of all my trouble), I'll try to get the info straight:
Motorola Droid Razr (XT910), bought in Dubai, using it in UK, so I didn't receive OTA updates. I decided to try update to ICS using RSD Lite, but the flashing got stuck at system_signed. I gave it a lot of time (hours) before I switched off the phone and tried again, which is when things started going haywire:
During my following attempts, the battery ran low, so I couldn't go on trying (soft brick). I made a patched "factory cable" as per instructions in this forum somewhere, the cable works and powers the phone for flashing.
Now all it does is coming up with the fastboot screen, which reads:
AP Fastboot Flash Mode (S) (Flash Failure)
0A.6C
[...]
Device is LOCKED. Status code: 0
Battery OK
OK to Program
Transfer Mode:
USB Connected
...which suggests to me it would be ok to be flashed, if only I could get it to accept the files. Being a big numpty, I am unfortunately not quite sure what was the exact version that was on there before (big mistake, I know that now), it was 2.3.6 and I suspect it must have been a MEA version, since it was bought there(? - also, when I first switched it on, all was in arabic).
What I have tried so far was:
* using several different fastboot firmware files with RSD Lite 5.7, all of which do not get over the step '1/xx flash cdt.bin "cdt.bin_signed"' - it just hangs supposedly "In process..." forever. I noticed all of these have an "ota" folder (although they vary considerably in size between <1 and 2.5 GB) - maybe all the ones I downloaded are only updates? Is there an actual, base operating system image somewhere?
After many failed attempts, I got desperate and tried files for different regions at random. The ones I tried so far:
SPDREM_U_01.6.5.1-73_SPU-11-M1-2_SIGNEuropeAustraliaEMEA_USASPDRRTGB_HWp2b_Service1FF_fastboot.xml
SPDREM_U_01.6.5.1-73_SPU-11-M1-2-ULB_1C.85P_0A.6B_DATDE_CFC_HWp2b_SIGNED.xml
SPDREM_U_01.6.5.1-167_SPU-15-M2-3_SIGNEuropeAustraliaEMEA_USASPDRRTGB_HWp2b_Service1FF_fastboot
SPDREM_U_01.6.7.2-180_SPU-19-TA-11.6_SIGNEuropeAustraliaEMEA_USASPDRICSRTCEE_HWp2b_Service1FF_fastboot.xml
SPDREM_U_01.6.7.2-180_SPU-19-TA-11.6_SIGNEuropeAustraliaEMEA_USASPDRICSRTGB_HWp2b_Service1FF_fastboot.xml
SPYDERIRD_U.01.26.0_SPD-IRD-21_SIGN_ASIA_RETAIL_HKTW.xml
SPYDERIRD_U.01.26.0_SPD-IRD-21_SIGN_MEA_RETAIL.xml
The only thing I am quite sure about is that it is not LATAM.
* I tried manually flashing the various image files with moto-fastboot, fastboot, and eprj-mfastboot, both the Windows and the Linux versions, with pretty much always the same result: it would flash some files (e.g. ebr, mbr, devtree), but not what I think are the crucial ones: boot, system, also logo.bin. As there are so many possible combinations, I have not tried every file from every firmware I downloaded with every possible program, but as far as I can tell, the results were the same. I did get some error messages about signing (indicating wrong region) sometimes, but most of the time it just hangs forever while supposedly transferring the files.
* I also tried the DroidRAZRUtility, both 1.51 and 1.6, which both invariably fail at the first step of flashing the "allow-mbmloader-flashing-mbm.bin" file on there.
So, I am out of ideas now. Please, someone tell me I have overlooked something obvious. Also, please tell me I haven't bricked the thing for good.
Is there not a way to write something new into it's memory on an even more basic level (I am thinking Linux' dd here), or to read out which region it is currently locked to? I repeat, all I get is the Fastboot screen, I can get into the Fastboot menu, but none of the options gets me anywhere else, (stock) recovery does not work... My last idea is that it might still be a power issue despite the "factory cable", and to try and crack it open and power it at the battery contacts for flashing - but the fact that some flashing works, and the other files don't fail because it goes dead, but because it rejects them, suggests to me it is not a power problem.
Any suggestions appreciated, thanks!
Try flashing SPDREM_U_01.6.7.2-180_SPU-19-TA-11.2_SIGNEuropeAustraliaEMEA_USASPDRICSRTGB_HWp2b_Service1FF_fastboot
with rsd lite.
Those failures are because of two things:
1. You are trying wrong sbf for another region
2 and/or you are trying to flash an older firmware.
Please note that now your only bet is to flash ICS firmware, and try various regions untill you find your right one.
Also if you manually flash use eprj-mfastboot , others fail to flash corectly.
Again for the power issue, when RSD throws an error , look at the phone, if it says "Low battery, cannot program" then the factory cable is bad, if not there is no power problem.
Don't worry your phone is not dead, you only need to find the correct sbf file, try more variants with rsd lite, it must work.
Mine had problems flashing correct sbf's, it was my system. Even with correct drivers and lastest RSD it would not work, nor with my other laptop, but working fine on my old xp install on a macbook. I could however install stuff individually using fastboot flash command. Sorry that I dont have a solution but I just wanted to let you know that sometimes it can be your computer/os install.
still trying
@Killer2k8: Thanks for the encouragement, I will try with the file you suggested with eprj-mfastboot.
As per power: I seem to have tried so many times that the battery is way deeply uncharged (I hope it isn't permanently damaged once I get the phone to charge at all again), so anyway, I crack'd'er open and tried powering directly at the battery contacts (battery disconnected, of course). As you would guess from what you wrote, that did not make any difference to my problems... But also, it proves my factory cable is good, as I can even flash the few files that work if no power is connected at the battery contacts, powering through the cable only. Some files will transfer correctly, and when it says "writing", the phone will just reboot, causing an error - that's why I thought of power issue, e.g. the actual flashing process requiring more power than just the transfer... Anyway, that issue did not go away even with direct power. - Will see what happens once I find the right files for me...
I'm good with flashing ICS, that's what I wanted to do in the first place. And thanks for the encouragement!
@drolgnir: Thanks, I had the same idea, as initially I had tried everything from Win7 running in VirtualBox (at first, I only found all the tools for Win, should've really researched better before starting this), I thought maybe it doesn't have the proper low-level access to the USB ports. Anyway, since trouble hit me, I tried also on three different Linux machines (2 different dirtros), and also again on the virtual Win, and on many, many different USB ports on these (just in case it was a USB power issue), all to no avail. I guess Killer2k8's suggestion sounds most promising at the moment... Cheers anyway.
no luck - situation deteriorating..?
Sorry for the many posts, I hope someone is still reading this...
So, I tried the file you suggested. I flashed manually, not RSD, with "fastboot" from eternity project, which is the Linux equivalent to "eprj-mfastboot.exe", as far as I can tell (download from the same post as the Win version).
I could flash cdt.bin, ebr, mbr. Note that these are all just 16kB.
When trying logo.bin, it sent it ok, but during 'writing logo.bin...', the phone just switched off. After restart, same again. Same also with boot_signed.
Since then, things got worse: whenever I try to switch on now, it flashes ~1/4 of the red "M" logo, then flashes the AP fastboot screen, and repeats that a few times before staying off (sometimes not, just switches off right away). I can still get into the Boot Mode Selection menu by holding all three buttons, but selecting AP fastboot there has the same effect. Starting with power&Vol- button shows the fastboot screen immediately, but again only for a flash...
The only thing that will stay on is the SBF Flash screen, but I don't know what to do with that..?
So, I still smell a power problem, but neither applying external power, nor using the factory cable alone made a difference. The cable is ok, I re-checked. The fact that the SBF Flash screen stays on suggests that it is not a stuck power button (someone had that problem, apparently), am I right?
So, any suggestions from here? Thanks..
Although this doesn't help, I have pretty much the exact same issue. However, I do know what/where my phone is from, it requires the central Europe update. But apart from that the issues are identical; it only boots into the flash failed fastboot menu, and any RSD attempts have failed at cdt.bin, while using the fastboot tool does not work either as I get preinfovalidation flash errors. The utilities don't work either.
Now, as you did, I also tried quite a few different versions of the firmware, and none of them worked. So what I was wondering is, is there a way for us to find out exactly what version the phone 'thinks' it is on, so we can find the same/a newer version of the firmware to update it to? Because I am quite certain I am using the files from the right region, so it must be the version that is too old.
update: still struggling, but giant leap further! Please read my tale...
...just in case anyone might find this useful, I'd like to give an update on my "patient":
I actually managed to flash ICS on there! Kind of.. What I did, was:
With the battery unplugged, I supplied external power to the phone, additional to the factory cable. The issue was that it would often flash small files, but for larger files would successfully "send" them, but in the "writing" phase the phone would just switch off. So, I supplied carefully monitored 3.7V to the contacts, which seemed to make a difference, but in the "writing" phase, Voltage dropped to below 3V where it would again switch off. Ok, you can charge a LiIon battery with max. 4.2V, and you should normally charge the battery before flashing, so I tried again while providing 4.2V. And - Success!! Voltage would drop to ~4V during "writing", but it stayed on, and allowed me to further test which Firmware the device would actually accept.
I do not believe that applying 5V from an USB cable directly to the (plugged-in) battery contacts, as mentioned in the forums somewhere, is very healthy for the battery. I reconnected the battery and tried charging it directly from the contacts, but I made sure the Voltage would always stay below 4.2V. Occasionally in my exploits, the charging circuitry would actually spring into action (confirmed by a drop and fluctuations in Voltage, and the faintest of noises from the phone itself), and I used that of course to squeeze some life back in, but most of the time it would not charge at all. I can not say what combination of flashing attempts, rebooting, un- and replugging the cable, switching and changing the charging current,... actually triggered the charging process occasionally, sorry. I could not reliably reproduce it.
In the process, I also tried the DroidRazrUtility 1.8, which interestingly flashed the AP fastboot to v 0A.74, but of course failed further on...
With the new AP fastboot, I thought maybe something more might now work, and at last I found it would now miraculously accept:
SPDREM_U_01.6.7.2-180_SPU-19-TA-11.6_SIGNEuropeAustraliaEMEA_USASPDRICSRTGB_HWp2b_Service1FF_fastboot.xml and
SPDREM_U_01.6.7.2-180_SPU-19-TA-11.6_SIGNEuropeAustraliaEMEA_USASPDRICSRTCEE_HWp2b_Service1FF_fastboot.xml
Fantastic!
First thing, before any actual booting, was to try if I could finally charge my battery again, and at last - yes!
At about 70%, I got adventurous, and unplugged the charger to put it in another power outlet. This made the phone actually boot up, but I thought that's not too bad now... But:
Now I have the following issue: After being freshly flashed (I tried several times now), it will charge as long as I don't actually switch it on, ONCE, but when it boots, after asking the setup questions and a little while on, it will switch off on its own, and then it's stuck in some variation of the bootloop (M dual core logo, pulsing M forever, OR rebooting ever and ever again at the pulsing M, OR just stuck at the M dual core). At least I now have a recovery menu. Erasing cache and data DON'T solve the issue (as proposed many times in the forums). I read a hint that it might be a kernel issue, or that it might be caused by a wrong radio.img (CDMA on a GSM phone). I checked and tested the latter by deactivating the radio in the extended settings, but it would still switch off after a short while (and it had defaulted to GSM, as it should).
So...am I stuck to wait for some new Firmware to come out, that might fix the issue? Or what should I try? Thanks in advance...
Resolved!
Long read, but I finally managed to do it. Basically, I am not 100% sure what happened, but I have a hunch:
After I thought I had solved the power issues by at least being able to charge the battery once after each re-flashing, I tried to fix the issue about the phone randomly switching off (and on - it wouldn't stay off!). I read that it might have to do with flashing failures (no error message??), or incorrect kernel or radio images...
Not long, and I ran into familiar problems again: It would flash the smaller files, but not system and cdrom; it would successfully "send" the files, but never stop "writing" them (I waited for somewhere between 10 min and an hour at each attempt), only way to stop the process was to switch off the phone, which certainly is not healthy during flashing...
...so battery started to go down again and I started to more and more clearly face a power issue again (I had disconnected the external power and didn't want to risk that McGyver approach again). As it happened, I also 'got some new USB 3.0 external hard drives at this time. I found that one would readily power up on all my USB ports, the other one could not get enough power even from some supposed 3.0 ports..
...which made me try flashing the very same firmware I was just trying (with the factory cable, of course), all the smaller files of which worked on the one computer but not the large ones (indicating I had the right firmware, at least):
SPDREM_U_01.6.7.2-180_SPU-19-TA-11.6_SIGNEuropeAustraliaEMEA_USASPDRICSRTGB_HWp2b_ Service1FF_fastboot.xml
, on another computer, on the one USB 3.0 port that had proven to supply the most power - and taa-daa! It wrote it, very quickly, without complaining!
And it booted alright (after charging it first, just in case). And it stayed on (and off, when I eventually rebooted it). I am running that ever since, and it seems ok...
Originally, I had aimed for:
SPDREM_U_01.6.7.2-180_SPU-19-TA-11.6_SIGNEuropeAustraliaEMEA_USASPDRICSRTCEE_HWp2b _Service1FF_fastboot.xml
, but I think the differences are minimal and I don't want to risk anything going wrong again, right now.
In conclusion, to me the main issues were
- finding the right firmware, stupidly not having paid attention to the original version number, and
- all sorts of different power issues!
The factory cable did not solve all of my problems.
Recharging the battery (eventually) did not solve my problems.
ADDITIONALLY, it needs to be flashed from a USB port supplying sufficient power!
This might point into the direction drolgnir suggested, but for me, it was not an OS/driver problem, but definitely power (same, fresh install of Fedora Linux on the two machines that did, and didn't work, one of them alternatively running Win 8; the Linux Mint computer I also tried doesn't have USB 3.0, the USB 2.0 ports - including an externally powered USB hub - did not work). @drolgnir: maybe it was power for you too, but you didn't notice because it was a different OS too?
...I hope this overly detailed report might help someone else too...
Hello guys,
I am really in need of help. For reason that does not matter any more I have tried to root my phone and now it is unable to start. I followed the steps listed in the below tutorial:
bbs.elephone.hk/thread-9919-1-1.html
However after following some steps, video tutorials and further confusions I ended up trying to "Firmaware Upgrade" my phone with SPFlash Tool, but unfortunately the process was ended prematurely and my phone is not able to start at all (black screen and no reaction from any button). I understand that everyone must take responsibility for the consequences followed by rooting a phone, but I wanted to ask you guys if I am able to recover the phone or I would need to buy a new one.
Here is more detailed information of what I tried and what is the problem I am experiencing:
- Error that I see when I try to "Format & Download" (or any other option / action that SPFlash tool has):
BROOM ERROR : STATUS_PRELOADER_INVALID (-1073545212)
[HINT]:
- What I tried:
1. Reinstalling the drivers because I tought that they are incorrect. Every downloaded dirver results to the same error and I believe that the issue is not related to the dirvers at all (I use Windows 7 Ultimate with the SP_Driver_v2.0).
2. Tried using different versions for SPFlash Tool, but it appears that only the latest ones works with the scatter file that I have (MT6755_Android_scatter.txt). Versions that I tried are - v5.1552; v5.1524; v5.1620; and after trying evrything I believe that the issue is not related to the used tool nor scatter file.
My conclusion is that somewhere along the way I re-formatted my phone, but since the processes ended prematurely this may have disrupted the correct format of the internal storage.
Is is possible to recover from this and if it is what steps / actions should I take to do so. I would really appreciated some help of you guys and will be glad if the phone is working back (promise to stop being a "hacker").
Best Regards,
A fellow that need helps or a new phone
I just wanted to add that I was able to recover my phone. YEY!!!!
For those of your who ran to the same problem here is what I did to restore the phone from the boot loop:
1. Remove the battery - this is quite a tricky part, but if you follow the steps and be careful there should not be any problems:
- Remove the back from the phone - since it is no meant to be easily removed you could use a plastic card and start from the top of the phone (where the ear jack is located).
- After that you would need to remove the top plastic cover - it is placed to protect the main board and all modules. You would need a small "Philips" screwdriver in order to remove all screws. Note that there is one hidden screw that is placed on the middle bottom part of the plastic cover. You could recognize it by the elephone logo placed on top of it.
- Once the plastic cover is removed you will see the connector of the battery. Remove so that the device is actually turned off.
2. Download a STOCK ROM for your device:
- The STOCK ROM for Elephone P9000Lite was downloaded from here:
4pda.ru/forum/index.php?showtopic=697579&st=20#entry47838700
All required images along with the scatter.txt file should present inside the downloaded archive.
3. Flash the ROM by using SPFlash tool:
- What I did here is to follow a tutorial that is specifically for hard bricked devices:
devs-lab.com/how-to-unbrick-mediatek-device.html
In my case I had to use the Format + Download option in SPFlash tool and select all images to be flashed. The important part was that the phone's battery had to be disconnected, all images selected by clicking the "Format + Download" option and finally hit the "Download" button. Once this is done you can connect the battery again and connect the device to your computer.
After the process is completed the device can be powered on and it should start booting.
I hope that I can help someone with these steps and that you do not give up on your phone.
Best Regards,
Happy fellow that resurrected his pone
I've bricked my other devices before and all i had to do to fix it, was remove the battery and format & download the original software. As you meantioned, with P9000 (same as with the Lite version), the problem is non-removable back cover and battery. Thank you for this tutorial, but it'd be better is somebody make a video tutorial or just add any media at all as many people might not want to do it, because of fear to break something under the back cover
Thanks for this, I am currently in the same position you were. I've cracked open the phone and am just trying to work out which connector feeds the power from the battery. I was pretty sure my problem was repairable so wasn't too stressed, but I hadn't thought to attempt to open the phone up like you did. It was surprisingly easy, and I don't think I'll have done any permanent damage. I'm hoping I can get the phone going again without any data loss, I was trying to flash recovery when I bricked it so hopefully I simply flash TWRP and she boots again.
awedxz said:
I just wanted to add that I was able to recover my phone. YEY!!!!
For those of your who ran to the same problem here is what I did to restore the phone from the boot loop:
1. Remove the battery - this is quite a tricky part, but if you follow the steps and be careful there should not be any problems:
- Remove the back from the phone - since it is no meant to be easily removed you could use a plastic card and start from the top of the phone (where the ear jack is located).
- After that you would need to remove the top plastic cover - it is placed to protect the main board and all modules. You would need a small "Philips" screwdriver in order to remove all screws. Note that there is one hidden screw that is placed on the middle bottom part of the plastic cover. You could recognize it by the elephone logo placed on top of it.
- Once the plastic cover is removed you will see the connector of the battery. Remove so that the device is actually turned off.
2. Download a STOCK ROM for your device:
- The STOCK ROM for Elephone P9000Lite was downloaded from here:
4pda.ru/forum/index.php?showtopic=697579&st=20#entry47838700
All required images along with the scatter.txt file should present inside the downloaded archive.
3. Flash the ROM by using SPFlash tool:
- What I did here is to follow a tutorial that is specifically for hard bricked devices:
devs-lab.com/how-to-unbrick-mediatek-device.html
In my case I had to use the Format + Download option in SPFlash tool and select all images to be flashed. The important part was that the phone's battery had to be disconnected, all images selected by clicking the "Format + Download" option and finally hit the "Download" button. Once this is done you can connect the battery again and connect the device to your computer.
After the process is completed the device can be powered on and it should start booting.
I hope that I can help someone with these steps and that you do not give up on your phone.
Best Regards,
Happy fellow that resurrected his pone
Click to expand...
Click to collapse
Hello all. I softbricked my phone while attempting to flash TWRP, and ended up with a phone that wouldn't present anything on screen. So I've located an old XP computer to rule out any driver issues, and using the battery removal mentioned above I was able to flash the factory 20160422 firmware which is what I believe my phone had before I started tinkering. I unticked the userdata box as I flashed it, and left the recovery box ticked which I thought would fix any corrupt recovery that my tinkering caused. The flash took some time, but I got the green tick indicating that it went well. However I still get nothing on screen, the only time I get anything is when I plug it into charge, I get a green battery charge icon for a few seconds before it fades away. If I leave it plugged in for a while, the screens starts to faintly flash sporadically. Does anyone have any advise for me? @awedxz, could you please confirm that the battery connection is on the far left, a shiny copper ribbon with a small silver rectangle plug that clicks into the board?
jiddahidda said:
Hello all. I softbricked my phone while attempting to flash TWRP, and ended up with a phone that wouldn't present anything on screen. So I've located an old XP computer to rule out any driver issues, and using the battery removal mentioned above I was able to flash the factory 20160422 firmware which is what I believe my phone had before I started tinkering. I unticked the userdata box as I flashed it, and left the recovery box ticked which I thought would fix any corrupt recovery that my tinkering caused. The flash took some time, but I got the green tick indicating that it went well. However I still get nothing on screen, the only time I get anything is when I plug it into charge, I get a green battery charge icon for a few seconds before it fades away. If I leave it plugged in for a while, the screens starts to faintly flash sporadically. Does anyone have any advise for me? @awedxz, could you please confirm that the battery connection is on the far left, a shiny copper ribbon with a small silver rectangle plug that clicks into the board?
Click to expand...
Click to collapse
Let it to charge more time
Thanks mate, this advise was spot on. It must have had 0% battery after fixing it! It's now alive and charging up. How neat that Mediatek devices can be unbricked so easily, although I'll have to be a bit more careful in future I think! My previous devices have been Motorola, HTC and Samsung devices, each with different tools and flashing techniques. Haven't bricked any of them in the past, but it's nice knowing this device will be hard to permanently brick.
chtsarts said:
Let it to charge more time
Click to expand...
Click to collapse
Had the same problem, a small cable that goes from the power button was disconnected. Connect the cable and it should run just fine
Just to chime in, I soft bricked my phone as well.
I managed to get it back to life, without taking the phone apart, so that is not a necessity.
Here's what happened: I had CM13 installed on the phone and wanted to go back to stock, so I flashed it according to the guides, also overwriting the preloader.
After that, the phone was dead, as in unable to turn on, no charger detection etc.
As is already known, this phone has an "emergency" line / device, that will turn on once you connect it to the computer and press the VOL+ button (the device will show up for a couple seconds in the Windows device manager).
So what I tried was to flash it again and again, to no avail; sp_flashtool reported the following error after trying to flash the preloader: "BROM ERROR - STATUS_EXT_RAM_EXCEPTION (-1073414139)"
Finally I tried different stock roms, from the Elephone forum.
The one that did the trick for me was the 20160304 - I loaded the scatter file into sp_flash tool and only flashed the preloader. After that, Windows suddenly recognized the phone as the preloader device, the screen turned on showing the charging image and the notification led lit up. I was able to flash the phone without errors again.
After that I flashed the rest of the stock firmware - without the preloader.
I then let the phone charge a little bit and it turned back on.
If that version of the preloader does not do the trick for you, try different ones.
No need to take the phone apart.
Good luck everyone!
For everyone's else information having this problem. I also bricked my P9000 whilst flashing TWRP and getting the RAM error. I tried every options possible but the only one that worked was to disconnect the battery. It is actually a very easy process as described as above. The battery connector is the small connector nearest to the volume buttons with the bronze coloured connector cable. It simply lifts up and your battery is disconnect. I changed the settings in SP FLASH to without battery and my phone flashed without any problems. Before this, it had been dead for over a week and all other methods failed to wake it up. Hope this helps.
---------- Post added at 11:36 AM ---------- Previous post was at 11:07 AM ----------
This video may help also
https://www.youtube.com/watch?v=irDOXh1QoKE
Hi everyone! I had the same problem (bricked phone not recognised by flash tool ecc ecc) and disconnecting the battery did the trick, but I may have messed up with some
The screen connectors and now the screen lits up but stays black. Sounds and touch screen work (I can unlock the screen because I hear the unlock sound), but the screen stays black... If I have damaged the connector (I think it's the one on the upper left, the thinner one that doesn't really click when inserted) there is not much to do, but I just wanted to know If anyone had the same issue and eventually resolved it.