Some easy videos for our best droid turbo phone
How to put Droid TURBO in Recovery Mode | Hard Re…: http://youtu.be/NdeHst-zyWY
How to put Droid TURBO in AP Fastboot Flash Mode …: http://youtu.be/Yh_YlBXRUPg
Anyone know what the Barcode and BP modes are for?
I am not sure about the barcode mode. But the bp tools are for diag modes and tools on your pc
Related
How do I flash the SPF file just in case I get a bricked Pro? I have a rooted Droid Pro with ClockworkMod Recovery installed from the Droid 2 Bootstrap.
I know how to go into CWM Recovery but only from the bootstrap... let's say my Droid Pro gets bricked and it doesn't start up and only gets stuck in a boot loop, then how do I flash the SBF file?
Thanks for the help, wish there was a fool-proof guide, I'm too spoiled from the ease of flashing a Droid Incredible.
You don't need CWM recovery to flash the stock SBF, you need it for installing CMW backups.
If your phone is bricked, use the stock recovery and flash the stock SBF. Stock recovery: R + M + Power on.
And after you get a working phone, re-flash CWM Recovery & the bootstrap, and use the backup you have.
When I try power + R + M all I get is an exclamation mark and the android logo?
Tell me if this is right...
I hold down both up/down volume buttons and then turn on, and then it shows me the Motorola locked bootloader screen that says "Plug in USB for programming"
Say I plug in my USB to my PC that has Moto Drivers & RSD Lite can I just flash the SBF that way? Nobody has really said literately how to do it, so I don't truly know since I have zero experience flashing Moto phones.
To flash SBF:
- Turn on USB debugging
- Connect phone to PC in PC mode
- Open RDS Lite as ADMINISTRATOR (right click on the .exe and go to run as Administrator)
- Select your SBF
- Click Start
@class: You're right and I'm wrong, I got recovery and boot loader modes mixed up.
al2x: Try what @class said.
@Class said:
To flash SBF:
- Turn on USB debugging
- Connect phone to PC in PC mode
- Open RDS Lite as ADMINISTRATOR (right click on the .exe and go to run as Administrator)
- Select your SBF
- Click Start
Click to expand...
Click to collapse
Is there a way to flash the SBF from a Mac (no RSD Lite) ?
sbf from Mac command line
John Markley said:
Is there a way to flash the SBF from a Mac (no RSD Lite) ?
Click to expand...
Click to collapse
Rephrasing my own question - Is there a way to flash sbf using Mac OSX unix command line (Terminal)? JM
mydroidworld.com/forums/droid-pro-discussions/6042-droid-pro-sbf-file-2-26-20-full-rsdlite.html
2nd post is the Droid Pro SBF Files. They are at 2.26.20 so you will have to do a 14mb update after the SBF install.
You will need RSDLite to unbrick your droid.
megaupload.com/?d=N1MPCX1U
- PASSWORD IS: alabama - You will also need the alabama password to extract the compressed file!
If you need any help with a bricked android phone, let us know here!
@Class said:
When I try power + R + M all I get is an exclamation mark and the android logo?
Click to expand...
Click to collapse
click the @ symbol. use the vol+ and vol- buttons to scroll and the enter button on the keyboard to select
So I had issues with my phone not long after updating to 4.4.2 using the houseofmoto method (about a month or two) phone was randomly rebooting itself so I flashed 4.4.2 back onto my phone after unlocking the bootloader. Now I can't seem to get the NV edit to work to get gsm unlocked for use in the US. Any help would be appreciated. I've tried the cdma ws method and both of the radiocomm methods with no luck. pretty sure I'm doing something wrong.
TogaDuck said:
So I had issues with my phone not long after updating to 4.4.2 using the houseofmoto method (about a month or two) phone was randomly rebooting itself so I flashed 4.4.2 back onto my phone after unlocking the bootloader. Now I can't seem to get the NV edit to work to get gsm unlocked for use in the US. Any help would be appreciated. I've tried the cdma ws method and both of the radiocomm methods with no luck. pretty sure I'm doing something wrong.
Click to expand...
Click to collapse
Are you booting into Fastboot mode, and then from there rebooting into Factory mode, before attempting the edit? Also, are you letting the phone sit for about five minutes or so after the edit before rebooting?
Edit: you may get better luck with responses if you post directly in the GSM unlock threads, as there are already lots of people subscribed to those threads.
In the past I've just booted directly to BP Tools mode and both of the how to guides say to boot into bp tools mode but I shall give your boot options a try.
The CDMA Workshop method requires booting into BP Tools, but the RadioComm method requires booting into Factory mode.
I haven't tried the CDMA WS method, but the RadioComm method worked fine for me. In the introductory post, he mentions BP Tools, but only to say that it doesn't work with RadioComm, and that you need to boot into Factory mode instead.
http://forum.xda-developers.com/showthread.php?t=2166542
got it working using the cdma ws method. selected ap fastboot then rebooted to boot menu selected bp tools mode reapplied the edit and is now working.
If it helps, here's the bit I was referencing from the intro post in the RadioComm thread. I highlighted the relevant bits in red.
cellzealot said:
(snip)
That method requires booting into BP Tools mode from the boot menu and loading the Qualcomm diagnostic device interfaces.
The problem is that there are no signed 64bit drivers available and you must force load the drivers on Win7/8 64 bit for the diagnostic port in order to see the device properly and have NV read/write access.
This has been a stumbling block for many users and makes the NV editing unnecessarily difficult.
This method uses Factory boot mode and allows RadioComm to have full diagnostic mode access via the Motorola USB Networking driver that loads normally with the standard USB driver set. I will demonstrate 2 different ways to perform the edit, one manual and one using a preconfigured SEEM table file that writes the value in a single operation.
(snip)
Click to expand...
Click to collapse
Glad you got it working though!
I tried the code *#*#3646633#*#* didn't work also tried MTK Engineering Mode Start but it says that it cannot find engineermode app help please
mine doesn't either, are you rooted
it also says for mediatek devices only
Hi
, I have a 32 GB Nexus 7 2013 (mobile) edition . A few days back it went into continuous reboot mode after an automatic overnight update. I tried to flash the stock factory image (from Google site) (version - razorg-mmb30s-factory-091a2b26 ) but ended up in the DLoader 9008 mode. At present the screen is completely dark, not even a flicker of backlight. I have tried all varieties of key combinations including long Power press (for upto 2 min), Power+Vol Down, Power+Vol Up, Power+Vol Up+Vol Down, etc but no change. It just turns off momentarily and switches on to the same mode which shows up in the Windows Device Manager under ports (COM4) but no there's no disk/storage/Android device entry. I have disconnected the battery and tried everything again but to no avail. I guess the boot image is corrupted. My only hope lies in trying to flash the stock/unbrick image via Qualcomm Qfil tool to somehow restore the bootloader and get the fastboot mode. However that requires the specific firehose 8960 MBN programmer image specific to this tablet which I cannot find anywhere. Can anyone upload these or tell me how to generate them from the Google stock image?
P.S. I have fair experience with linux command line tools too, so a Linux solution would be equally welcome
Thanks in advance.
Hey yall, I've put myself in a dumb position.
I bricked my phone to the point where any time I boot up my phone, it only shows "QUALCOMM CRASH DUMP". Not to mention both fastboot and recovery are gone from the picture. My only real option is EDL mode.
I was able to find a couple methods and was able to dump userdata.bin (219GB) using the first link's method.
Recovering data from Mi 4c able to get only to fastboot (StackExchange)
[GUIDE] How to dump and write back the storage on most of Qualcomm devices
I'm fairly out of my element with all this and I haven't figured out how to mount it properly, so I'm not really sure what to do from this point on. Any info is a great help, even if you have to break the news that my work may be for nought.