Database Users

Stuck in Bootloader.

I know that there's probably tons of these, but here goes.
Last night, I tried installing 2.3.320, but ended up looping at the eye. I thought I had installed it wrong, so I tried to access bootstrap recovery to delete the data I hadn't cleared. I was surprised to only be able to access the stock bootloader, 30.04. Anyway, I decided to try using an SBF to restore, but I used the wrong one. Bootloader now loads with these messages, "Err:A5,70,70,00,1F" "MEM_MAP Blank" "Service Req'd".
I got my hands on the system only SBF for 2.3.320 that is floating around, but that still isn't fixing my problem.
Simply put, does anybody know of anything I can do now?

silversonic1 said:
I know that there's probably tons of these, but here goes.
Last night, I tried installing 2.3.320, but ended up looping at the eye. I thought I had installed it wrong, so I tried to access bootstrap recovery to delete the data I hadn't cleared. I was surprised to only be able to access the stock bootloader, 30.04. Anyway, I decided to try using an SBF to restore, but I used the wrong one. Bootloader now loads with these messages, "Err:A5,70,70,00,1F" "MEM_MAP Blank" "Service Req'd".
I got my hands on the system only SBF for 2.3.320 that is floating around, but that still isn't fixing my problem.
Simply put, does anybody know of anything I can do now?
Click to expand...
Click to collapse
Think you're boned. Shoulda read some of the thread at mydroid before taking this on. Most ppl are bricking, with it. You appear to fall into that category.

Go Back to TBH there maybe some help now.
But the 23.15 may also big the big bone.
ouch

This is awful. I'm a guide on another forum for androids and I'm telling people not to try the new update until there is a full sbf available. I'm so sorry. You are stuck..for now.

Well, Verizon's gonna let me swap, so I'll just have to wait until Tuesday and root the new phone.

I'm preparing to root my X and am trying to get a rescue plan in place prior to rooting. The one thing I can't find is a list of what SBF files can safely be used for a given bootloader revision. I posted this in a thread at another forum. Does what I'm asking for not make sense? Or am I completely missing something?
There should be some sort of sticky for SBF'ing the X. I realize that sbf links cannot be posted but it would sure be nice to know which files are needed to properly sbf a semi bricked phone, especially if using the wrong one will fully brick a phone.
What I've gleaned from this thread...
"No if you were stuck on the M that shows that you should already be updated, put your phone into flash mode and make sure (turn of your phone press the camera down volume and power button). It should say boot loader 30.04 if it shows 30.03 then dont use the link provided. If it is 30.04 go download the sbf from ncdubs link and run it using RSD 4.8 and that should be enough for the phone to get past the M logo. Dont it asap because you never know when that link will be dead. Man I was so scared yesterday because i thought my phone was bricked haha but that link that i found in another forum did the job."
"If you are on 2.3.20, use the 2.3.15 SBF.
If you are on 2.3.320, use the SBF's from TBH"
It would be nice to have a running list detailing which sbf file needs to be used for a given bootloader,
i.e. if bootloader is 30.03 use the 2.3.15 sbf or the x.x.xx sbf
if bootlader is 30.04 you can safely use the x.x.xx sbf
and so on.
Surely this won't be in violation of anyone's terms of service would it?
I'm not rooted yet but I'm trying to wade through multiple posts at multiple sites to put together a rescue package prior to rooting and can't find what I believe to be concise information anywhere.
Click to expand...
Click to collapse

http://www.mydroidworld.com/forums/...rikes-back-2-3-320-update-must-rooted-69.html
Post #682 - CZ from TBH is working on a way to restore soft bricked X's,and is making good headway!

bricked, verizon is overnighting one, should have a good clean one tomorrow.

SerialKilla said:
.....link deleted, as this forum won't allow me to post outside links..... yet...
Post #682 - CZ from TBH is working on a way to restore soft bricked X's,and is making good headway!
Click to expand...
Click to collapse
Thanks for the link, I'll be following the thread closely. Sorry to hear you're X is in a semi bricked state. At this point I'm quite wary of doing anything to the X but I believe I have a rescue in place. My phone shows to be 2.3.151 and I found VRZ_MB810_2.3.15_1FF_01.sbf so I believe I should be able to safely recover should I brick it. I rooted using Z4 and the bootstrap, then proceeded to freeze the bloat. I'll run like this until UD for the X comes out then depending on SBF requirement / availability will consider trying it out. UD2 is really sweet on the D1 and I've read it's even nicer on the X.
I must be in the minority because I kind of like blur. I did freeze all of the social networking stuff and installed gallery3d, I would continue to use the blur gallery if it synced with picasa.
edit: SerialKilla I see a new rescue sbf was released, did it work for you?

edthesped said:
Thanks for the link, I'll be following the thread closely. Sorry to hear you're X is in a semi bricked state. At this point I'm quite wary of doing anything to the X but I believe I have a rescue in place. My phone shows to be 2.3.151 and I found VRZ_MB810_2.3.15_1FF_01.sbf so I believe I should be able to safely recover should I brick it. I rooted using Z4 and the bootstrap, then proceeded to freeze the bloat. I'll run like this until UD for the X comes out then depending on SBF requirement / availability will consider trying it out. UD2 is really sweet on the D1 and I've read it's even nicer on the X.
I must be in the minority because I kind of like blur. I did freeze all of the social networking stuff and installed gallery3d, I would continue to use the blur gallery if it synced with picasa.
edit: SerialKilla I see a new rescue sbf was released, did it work for you?
Click to expand...
Click to collapse
I haven't seen the new .sbf yet...where did you see it? If it's just the sytem only fix, that won't work on mine - I need the full .sbf, or whatever it'll be that CZ and P3 are working on. P3 said to expect something in less than 36 hours, but I haven't seen anything as of yet. Too early yet I think - but I know they've had success in their progress, so fingers crossed!

SerialKilla said:
I haven't seen the new .sbf yet...where did you see it? If it's just the sytem only fix, that won't work on mine - I need the full .sbf, or whatever it'll be that CZ and P3 are working on. P3 said to expect something in less than 36 hours, but I haven't seen anything as of yet. Too early yet I think - but I know they've had success in their progress, so fingers crossed!
Click to expand...
Click to collapse
Sorry, it was the system only sbf, I d/l'ed it as a backup and judging by it's size it isn't a full system sbf. Hopefully you'll be rocking again by this time tomorrow.

[Q] Root gone WRONG!

Okay so today i decide to root my phone. I heard alot about custom roms and other tweaks that make your phone do all this cool stuff. Well i try and download a custom rom, i did use the droid 2 bootstrap, and i believe i backed up on ROM Manager. after that i went and looked at roms and i downloaded Tanzanite ROM. at first i thought i was in a boot loop and i got scared because i rooted my phone last week and downloaded a custom rom wrong and it was in a boot loop. So when i thought this time it was in a boot loop, i hold X and Power button and get recovery options. i factory reset it then rebooted it, it then started up on Tanzanite ROM. I was quite happy with it, then when i try to look at my apps, they are all GONE ! There is no Market and i have no 3G coverage. I was upset and i dont know what to do. I am scared if i do something it will go into a bootloop or i will be stuck with this ROM forever. I NEED HELP ! PLEASE ! i cant afford another phone replacement. Please help me ! Please, experts, people who had this issue, somebody just please help. Thanks.

You're not stuck. There's always SBF.

SBF is your best friend. And a word of advice to you. ALWAYS find out what kind of recovery is out for your phone before you do ANYTHING like rooting or flashing. For Moto phones, SBF is your friend. HTC has RUU's.
Here is the guide to SBF your phone:
http://forum.xda-developers.com/showthread.php?t=770224
(Be sure to get the RSDlite 4.9 and the latest Moto drivers which you can find on Moto's website)
Here is the SBF file to download:
h t t p://www.mydroidworld.com/forums/droid-2-discussion/5323-tbh-mydroidworld-present-droid-2-2-3-20-triple-threat.html
This will get you back to 100% out of the box stock.
Good luck and let us know if you get it fixed. If you have any problems or questions, feel free to PM me.

I fixed the problem. Thanks guys but i would like to know, what is SBF and what does it do? Everytime i do a new ROM i am scared of the outcome. It bootlooped once and got a new one. I will always be scared when my phone re-boots. Alot of feedback i got, has mentioned SBF and i have yet to know what it does and yet to know what it means.

I could be wrong, but I think SBF stands for System Backup File. It basically is a file that came from Motorola. Motorola uses it to get the phone back to its out of the box state, meaning it returns the phone to the same state as when you got it.
You use it if you have no way to fix your phone. As long as you can get into bootloader mode, you should be able to use the SBF. It's actually pretty hard to 100% brick these phones.
Most phone has some sort of recovery utility like this. For example, HTC has RUU (ROM Update Utility) which will do the same thing as an SBF for Moto phones. I don't actually know what other brand phones have, because I've only ever rooted HTC and Moto phones.
Also, when you flash a ROM, you say you bootloop right? Be sure before you flash a new ROM to wipe data and cache in clockwork recovery. This should prevent bootloops.

[Q] Bricked? RSDLite won't work

I was flashing ROMs and had DLed a bunch from a site exclusively for RAZR M phones and some guy had put a bunch of stuff for the XT910 and I accidentally flashed a AOKP GSM zip and now I can't flash anything or RSDLite back to stock, which was always my failsafe out of a soft brick. I still have TWRP and I was able to restore my backup but boot and system files only, data wouldn't restore. Now my phone will boot to the custom splash screen but it just loops. And I first get the red Moto M circle and do NOT get the unlocked boot loader warning. So any help? I will post the RSDLite results when I get home.
ok heres the site I got the file from, this guy should be hung...surdu_petru...http://www.androidfilehost.com/?w=developers&did=70

noone? help is needed please! OK well I restored to a TWRP recovery i had and it worked partially, as long as i unchecked the data partition, the boot and system partitions stuck, so now my unlocked bootloader warning is back as is my custom ROM splash screen, but in a bootloop. I tried RSDLite flashing it again and the 4.1.1 firmware seemed to work but still loops. 4.1.2 and 4.0.4 wont flash because of the "get var, OEM" issue. I had this happen once before aswhile back but was using CWM recovery and juyst switched to TWRP, which fixed it, but not so lucky this time around. So I am wondering if i flash some other partitions like the persist forthe radio, esp since i flashed a xt910 GSM file which is why my phone now thinks its a xt910. Any ideas? please!!!

ok PROBLEM SOLVED. aFTER LOSING THE CUSTOM RECOVERY BY TRYING TO FASTBOOT WITH RSDLITE I DID THE "delete the Getvar and OEM LINES FROM THE FACTORY FIRMWARE OF 4.1.2 (THE .78 VERSION) AND SINCE THE xt910 ROM WAS 4.2.2 AND MY RADIO HAD PREVIOUSLY BEEN UPDATED TO .78, I FIGURED THE .78 4.1.2 WOULD BE MY BEST SHOT, AND SO IT WAS. THAT "GETVAR" ISSUE IS DEFINATE PROBLEM THAT SHOULD BE RESOLVED ANYWAY. wELL ANOTHER TRAGEDY AVERTED, AND IM GETTING PRETTY GOOD AT THIS, LOL, AVOIDING MISTAKES WOULD BE BEST THO. sO BEWARE OF THE "ANDROIDFILEHOST" SITE, THEY HAVE A GUY POSTING XT910 ROMS UNDER XT907 FOLDER! almost cost me a phone Close this thread

Edit does not work on either of my razr m phones
one last note, I thought i was unable to get the radio/modem working again as a resullt of flashing a GSM ROM for the XT910, but that issue was fixed with a Firmware flash, or FXZ file, through RSDLite. The issue is actually the RAZR Ms US GSM unlock (NV edit using RadioComm) that is still not working. As with my other RAZR M (LOCKED, rooted, and SS installed) I can not seem to get it working by using RC or DFS, and I am really starting to think the .78 or .94 update killed this edit just as it did the bootloader unlock, even though everyone says it doesnt and that this edit can be performed on locked, unrooted and completely updated devices. If so then....
CAN SOMEONE EXPLAIN WHY BOTH MY LOCKED AND UNLOCKED RAZR M DEVICES WILL NOT ACCEPT THE US GSM EDIT???? PLEASE?

Here is my Feedback for you...
rocketrazr99 said:
one last note, I thought i was unable to get the radio/modem working again as a resullt of flashing a GSM ROM for the XT910, but that issue was fixed with a Firmware flash, or FXZ file, through RSDLite. The issue is actually the RAZR Ms US GSM unlock (NV edit using RadioComm) that is still not working. As with my other RAZR M (LOCKED, rooted, and SS installed) I can not seem to get it working by using RC or DFS, and I am really starting to think the .78 or .94 update killed this edit just as it did the bootloader unlock, even though everyone says it doesnt and that this edit can be performed on locked, unrooted and completely updated devices. If so then....
CAN SOMEONE EXPLAIN WHY BOTH MY LOCKED AND UNLOCKED RAZR M DEVICES WILL NOT ACCEPT THE US GSM EDIT???? PLEASE?
Click to expand...
Click to collapse
The Reason why it doesn't accept the Us GSM edit Is because the Motorola Droid Razr M is not a gsm phone it is a CDMA phone with LTE. Thus it will not work on any GSM providers unless that provider is like straight talk with multiple networks supported otherwise the phone is stuck on verizon wireless or any other carrier you bought it from. Have A Good Day. By the way my two old accounts got banned for no reason. if you want to know what experience i have look at my devices on the accounts Droidxpert and Droidxpert1. Thanks

rocketrazr99 said:
one last note, I thought i was unable to get the radio/modem working again as a resullt of flashing a GSM ROM for the XT910, but that issue was fixed with a Firmware flash, or FXZ file, through RSDLite. The issue is actually the RAZR Ms US GSM unlock (NV edit using RadioComm) that is still not working. As with my other RAZR M (LOCKED, rooted, and SS installed) I can not seem to get it working by using RC or DFS, and I am really starting to think the .78 or .94 update killed this edit just as it did the bootloader unlock, even though everyone says it doesnt and that this edit can be performed on locked, unrooted and completely updated devices. If so then....
CAN SOMEONE EXPLAIN WHY BOTH MY LOCKED AND UNLOCKED RAZR M DEVICES WILL NOT ACCEPT THE US GSM EDIT???? PLEASE?
Click to expand...
Click to collapse
The phones will accept the edit and will work on GSM if you unlock with RadioComm. He ran into issues because he didn't unlock with RadioComm.
Sent from my Droid RAZR MAXX HD using xda app-developers app

ImDroidxpert said:
The Reason why it doesn't accept the Us GSM edit Is because the Motorola Droid Razr M is not a gsm phone it is a CDMA phone with LTE. Thus it will not work on any GSM providers unless that provider is like straight talk with multiple networks supported otherwise the phone is stuck on verizon wireless or any other carrier you bought it from. Have A Good Day. By the way my two old accounts got banned for no reason. if you want to know what experience i have look at my devices on the accounts Droidxpert and Droidxpert1. Thanks
Click to expand...
Click to collapse
Sorry but they both unlocked. The issue was (I think) that I was typing "01" but only needed to actually type "1" and then the window shows "01". It was something like that anyway.

soft bricked now
Now my problem is I wiped the whole phone by mistake and cant restore since i lost CWM and cant RSDLite any firmware since the latest was already on it and some error message showed that i had flashed an earlier version or somthing, IDK. But I read that to fix it i need a newer firmware to run on RSDLite, of which none exists. So my phone is soft bricked until Kitkat gets released for the M, which is never, lol

rocketrazr99 said:
Now my problem is I wiped the whole phone by mistake and cant restore since i lost CWM and cant RSDLite any firmware since the latest was already on it and some error message showed that i had flashed an earlier version or somthing, IDK. But I read that to fix it i need a newer firmware to run on RSDLite, of which none exists. So my phone is soft bricked until Kitkat gets released for the M, which is never, lol
Click to expand...
Click to collapse
You don't need to run a newer firmware, you just need to run one that's equivalent to what you have now. You got the TZ fail because you tried to flash an older FW.

RikRong said:
You don't need to run a newer firmware, you just need to run one that's equivalent to what you have now. You got the TZ fail because you tried to flash an older FW.
Click to expand...
Click to collapse
It was actually more than just that. I cant remember but saw a thread about it saying that it had an old firmware and a present firmware and it needs a newer firmware, but I am onm the newest one already so I have to wait for one to get pushed out, idk. Now i can get as far as flashing process 17/21, which is the system flash, when te phone returns a fail. i will try a few tricks i learned from prior luck

rocketrazr99 said:
It was actually more than just that. I cant remember but saw a thread about it saying that it had an old firmware and a present firmware and it needs a newer firmware, but I am onm the newest one already so I have to wait for one to get pushed out, idk. Now i can get as far as flashing process 17/21, which is the system flash, when te phone returns a fail. i will try a few tricks i learned from prior luck
Click to expand...
Click to collapse
OK, Rik was right, I didnt have to wait for a new firmware release. I kept trying to flash the most recent version of 4.1.2 and kept hitting a wall at 17/21, which is the flashing of the system image. Occasionally it would fail before that at 16/21, which is CDROM files. That always happened the first attempt after I unhooked the phone and restarted everything, so I started thinking, what is causing the flash to fail for no apparent reason. Then it finally hit me....it was as if my phone was running out of storage space. But that just isnt possible when you are flashing with RSDLite since it wipes out everything first. So I then remembered that my PC has very little room left on its hard drive. Could it be that RSDLite needed more space to work? Hmmmmm, so I deleted a few videos and moved the firmware file to that area (it may or may not help) of the drive and tried again. After the initial fail at 16/21 I was met with a successful flash, although it took a very long time to flash the system image, which I attribute to low disk space. So there you have it.... of course I had to modify the XML file and remove the "getvar" line, and realized I had forgot a golden rule.... all programs and apps need a certain amount of disk drive space in order to operate, and RSDLite is no exception! So now my locked phone will get the carrier unlock edit and Safestrap installed with an extra ROM in slot 1, then it goes on eBay, lol. I have my other RAZR M in semi retirement, it has the BL unlocked as well as the carrier, but I couldnt pass up a new Nexus 5 for $250, but I will surely be swapping the SIM card back and forth because I really miss my RAZR M already. Wish they would make a RAZR M with the processing power of the Nexus 5. Anyhow, PLEASE CLOSE THIS THREAD, TY.

Use this I used it when I bricked mine
Sent from my XT907 using Tapatalk

http://forum.xda-developers.com/showthread.php?t=2249773
Sent from my XT907 using Tapatalk

I'm having a similar problem with my xt907. The phone will boot and loop on the boot loader. I have tried to restore with rsd lite bit haven't had any luck. Any suggestions, I know it may not be enough information. If you ask I might be able to give you more details.
---------- Post added at 10:33 PM ---------- Previous post was at 10:28 PM ----------
Also I can't get into recovery.

ImDroidxpert said:
The Reason why it doesn't accept the Us GSM edit Is because the Motorola Droid Razr M is not a gsm phone it is a CDMA phone with LTE. Thus it will not work on any GSM providers unless that provider is like straight talk with multiple networks supported otherwise the phone is stuck on verizon wireless or any other carrier you bought it from. Have A Good Day. By the way my two old accounts got banned for no reason. if you want to know what experience i have look at my devices on the accounts Droidxpert and Droidxpert1. Thanks
Click to expand...
Click to collapse
I am sorry to say that you are uninformed and the XT907 CAN have van NV edit which allows it to be used on GSM networks. The phone is already setup to be comparable with GSN since Verizon made it a "global" handset, but....they also blocked any GSM capabilities in the U.S., until of course you do the NV edit. So please remove your post.

Rooting the mystery Moto C - XT1754

Hello, Ya all... hope you're doing fine.
I searched for days to find a serious guide to root moto c, xt1754, and wasnt successful. Now, am an older guy and I sure cant dive as deep as you do into that area Had me a fine Moto G and rooted it with XDA know how pretty good. Unfortunately this device got stolen a few weeks ago. Since am not a rich man and that I needed a new device, I got the Moto C. I can see for myself thats a pretty simple piece... but till am able to get a better Moto - I'd like to root XT1754 either. So, is anyone willing to help me? Could I use the files I once successful used for Moto E and G, logically updated?
Is Moto C another kind Moto E?
Hope I'd describe my case well enough for you. I also truly hope someone might have mercy with me and can let me know what I've to do.
Wish you all a Good Time at All.
Tyd27

In short, no, you cannot use the same files as on previous gen Moto's. The reason behind it... quite simple: they have absolutely nothing in common. This Moto C sports an MTK processor, to begin the long list of differences.
What you can try is this:
1. Unlock your bootloader. Either via Motorola Developer Website, or via fastboot oem unlock.
adb reboot bootloader
fastboot oem unlock
OR
fastboot oem unlock UNLOCK_CODE_FROM MOTOROLA
Once you're done with that, re-enable USB Debugging and OEM UNLOCK ( if you need to turn it back on ).
Then install the latest Magisk app from www.tiny.cc/latestmanager
At this stage, you will need your original boot image ( from here: https://www.needrom.com/download/moto-c-4g-xt1754-nrd90m-054-row-official-rom/). You will need to register there, and wait basically until forever for that firmware file to finish downloading. Open that up with 7zip and extract it. Find the file called boot-signed.img.
Patch it using Magisk.
move that patched_boot.img in your ADB directory.
adb reboot bootloader.
fastboot flash boot patched_boot.img
At this point, 2 options:
a. It will flash, in which case you will do fastboot reboot
b. it will not flash, in which case you will get an error ( boot image not signed etc)
If the first option occurs, you might get a "corrupt" error screen upon reboot. Follow the steps and let the phone do a factory reset. If it reboots properly, re-install Magisk and enjoy root.
if it does not want to reboot properly... you'll congratulate yourself on having the firmware handy

So, thanx alot for this answer. Am happy that someone took care now coz i really dont like unrooted devices. Well, the other side is am 58 now and not a professional at phones. Rooted a few motos with xda help and all went good. Unfortunately my last moto g got stolen and fir what reason ever else i chose to get moto c. Probably it was realky damn ****n stupid. Until i can afford another moto i going to try everything to root moto c. I'll read your reply now before i start doing it. Too bad that there is no way rooting it like moto g. Does it mean i wont have twrp neither?
Have a Good Day.
Tyd27

Definitely no TWRP on it, until someone with the knowledge will port it. That's just how it goes with MTK Devices and their closed source, I'm afraid.

Hi can u make a custom recovery for moto c xt1754

https://forum.xda-developers.com/android/development/recovery-twrp-3-1-1-0-moto-c-t3703184

Hey all! Just got my hands on a Moto G7 XT1962-1, and managed to brick it.

So shortly after getting this phone today, I absolutely loved it, and the Android Pie OS running on it, however I felt it was missing something. So I downloaded TWRP onto my PC, unlocked the bootloader and went to install TWRP. It kept giving me issues, and I kept persisting. Finally said f**k it and had it live boot to the phone to see if I could install it that way, went to the home screen and didn't see the TWRP system app which I thought was odd, so I tried again and this time, had it install to Memory B, and so I swiped to restart, say a flash of my battery charging indicator on the screen and since then it's had a black screen. I've been at this for 6 hours as of now, and it's driving me insane. I've done as many 'fixes' as I can think of and I'm coming up empty handed. Any help will do.

Sounds like you are going to need to use a blankflash on it. Good info here: https://forum.xda-developers.com/moto-g7/how-to/blankflash-moto-g7-xt1962-5-river-reteu-t4020263

@[email protected] Thank you so much! I'm looking into this now! I'll get back to you with my results.
Edit: I managed to get it into the bootloader, by following the steps in the link, [email protected], provided. I managed to access the phone in Lenovo Moto Smart Assistant, and I'm currently downloading the firmware for my device.

Retrocommander said:
@[email protected] Thank you so much! I'm looking into this now! I'll get back to you with my results.
Edit: I managed to get it into the bootloader, by following the steps in the link, [email protected], provided. I managed to access the phone in Lenovo Moto Smart Assistant, and I'm currently downloading the firmware for my device.
Click to expand...
Click to collapse
You'll get it back. Always scary when it first happens, but it is great that there are current blankflash options for these phones. I bricked a moto G4+ and had to use a Z blankflash with a whole lot of coding to get it back. Good luck.

[email protected] said:
You'll get it back. Always scary when it first happens, but it is great that there are current blankflash options for these phones. I bricked a moto G4+ and had to use a Z blankflash with a whole lot of coding to get it back. Good luck.
Click to expand...
Click to collapse
Hey! So sorry to keep you hanging when I said I'd keep you updated, haha! I did manage to get the phone working and I decided to relock the bootloader and keep it that way. Thank you again for your help! Maybe when I get some money coming in (gotta love this pandemic) I can send you a thank you through Venmo or something, so you can get a coffee, my treat!