Related
First of all, ALL THE CREDITS go to CellZealot from TeamBlackHat !
This was only possible with the files that he provided!
I was just a simple "guinea pig" that killed a Razr testing theories about downgrading it back to Gingerbread ! :angel:
So lets, f.... do it.
<Warning> By continuing to read and deciding to start this procedure, YOU ARE ON YOUR OWN! I, CellZealot, TeamBlackHat & XDA-Developers WILL NOT be held responsible for any personal or material damage that might incur from the actions described here! That's your decision to go on, so deal with it! YOU ARE WARNED! <Warning>
Requirements:
- Stock ICS SBF fastboot firmware package. Google is your friend.
- a PC x86 computer with a usb port
- Linux operating system. (Ubuntu, Arch, Gentoo, Slackware, Debian, whatever distro you choose...)
- Linux O.S. knowledge. You must be familiar with the command prompt (Bash Shell) and the commands! That's up to you.
- This software package -> http://www.multiupload.nl/VL33M4I4A3
- The "fastboot" program from the Android SDK (latest version that you can find.)
- a software bricked Razr, that only shows itself as a "OMAP4430" device, under Win. "Device Manager", when plugged. Give it a try under a Windows computer, just to make sure.
- MicroUSB to USB cable. The one that came with your Razr.
- The Razr must be charge to the minimum required the bootloader to enable the flashing process. There are other ways to charge your phone without the stock charger. You can search here on XDA for it.
PS: The factory service cable, allows you to bypass the battery check, by allowing the Razr to receive 5v straight from the usb port. As per CellZealot explanation on third post.
Optional but HIGHLY RECOMMENDED !
- a Motorola Factory/Service Cable. You can build your own or buy one! I recommend buying from "TeamBlackHat" as they make high quality cables and adapters! If you prefer, you can just buy the adapter and use your own MicroUSB cable with it.
About the expected end result: your Razr in FastBoot mode, ready to be flashed with a stock firmware.
<Procedure>
- download the package "spyder_bl.7z" and unpack to a empty directory to avoid any confusion.
- you will end up with 3 files - "omapflash-lnx", "pbrdl.bin" & "brdl.bin"
- make the "omapflash-lnx" file executable
- plug the phone to pc and press the power button for 2 seconds, till it apears as a "Texas Instruments" device under the usb list (lsusb) or in the kernel log.
Now you must be quick and start typing in this order:
sudo ./omapflash-lnx pbrdl.bin
sudo ./fastboot flash brdl brdl.bin
You should get a "Okay" status on both of them.
Check your Razr screen and it shall be on "FastBoot AP Mode". From here, you can keep flashing on Linux or boot up Windows and use RSD, wich is more user friendly besides being GUI-Oriented.
Some facts about the 3 files: they are all "signed files" by Motorola, that's why it is safe to use. The OMAP4430 cpu on the Razr is factory programmed to only execute signed code, that's why we needed to find an exploit to execute unsigned code. Examples are the KExec, Boot Manager & Safestrat. All of them available here on XDA in their respective threads.
Peace.
:good:
PS: Do not thank me or my posts. This guide was only possible due to CellZealot support. You must thank him, if for some reason it helped you recover your phone. Copy that?
PS: Thanks also XDA-Developers for this amazing community!
EDIT: Corrected the part about the Factory Service Cable. It does not allow you to charge the Razr but rather supply the necessary juice for the phone to work without a minimum charge. Thanks again, CellZealot!!!
I've tried & failed to brick my phone~ It's now nearly impossible to brick this phone :good:
Just some notes from my journey,
pbrdl.bin only accept few commands... so no oem unlock
pbrdl.bin is 1st-loader for USB boot (mbmloader.bin is for NAND boot)
brdl.bin is just mbm.bin (motorola boot manager)
Thank you for the excellent writeup and for the recommendations for TBH Factory Cable/Adapters!
You are very welcome and congratulations on fixing your phone and being in a very exclusive club of users who have brought their devices back from the brink of the abyss...the truly bricked phone. Also big kudos for going to great lengths to research and attempt many complex means to fix a device you had broken yourself rather than returning it to your carrier under warranty. Your ultimate success is richly deserved.
A couple of points I wanted to clarify.
The Factory Cable/Adapter does not charge the device at all, but bypasses the battery and smart charging circuit altogether and powers the device directly by supplying +5v on pins 1 and 4. It will always power on the device no matter what state the battery is in or without a battery at all.
The other thing is that depending what the circumstances are that lead to the corrupt boot loader, restoring the device can be even easier and not require flashing the firmware.
In my case, I had specifically overwritten the mbmloader and as soon as I repaired that successfully the phone booted up perfectly fine and fully rooted with everything exactly as I had left it the night I hosed it!
cellzealot said:
Thank you for the excellent writeup and for the recommendations for TBH Factory Cable/Adapters!
You are very welcome and congratulations on fixing your phone and being in a very exclusive club of users who have brought their devices back from the brink of the abyss...the truly bricked phone. Also big kudos for going to great lengths to research and attempt many complex means to fix a device you had broken yourself rather than returning it to your carrier under warranty. Your ultimate success is richly deserved.
A couple of points I wanted to clarify.
The Factory Cable/Adapter does not charge the device at all, but bypasses the battery and smart charging circuit altogether and powers the device directly by supplying +5v on pins 1 and 4. It will always power on the device no matter what state the battery is in or without a battery at all.
The other thing is that depending what the circumstances are that lead to the corrupt boot loader, restoring the device can be even easier and not require flashing the firmware.
In my case, I had specifically overwritten the mbmloader and as soon as I repaired that successfully the phone booted up perfectly fine and fully rooted with everything exactly as I had left it the night I hosed it!
Click to expand...
Click to collapse
Thanks once again, my friend. Corrected as per your definition, the section about the FS Cable.
Peace.
:good:
Thank you for this valuable guide, it is a true unbricking solution for the RAZR. Some mirrors of the spyder_bl.7z file. Just in case
http://www.mediafire.com/?z5gp1ztvwj81qr4
http://www.4shared.com/archive/BtfH6ML8/spyder_bl.html
Sorry my english so bad
My droid razr can't to flash brdl.bin
Just show waiting device
How to fix it?
I'm has do all procedure...
Tq b4...
prue said:
Sorry my english so bad
My droid razr can't to flash brdl.bin
Just show waiting device
How to fix it?
I'm has do all procedure...
Tq b4...
Click to expand...
Click to collapse
Ehm...Why did you try this??? Have you read careful enough what this is about?? I'm pretty sure your problem can be solved much easier than this way. Depending on your problem you have with your device I suggest you to open up a new thread in general section (or Q&A Section) and ask for help. BUT:
Don't flash anything to your phone if you don't know exactly what you're doing!.
dtrail1 said:
Ehm...Why did you try this??? Have you read careful enough what this is about?? I'm pretty sure your problem can be solved much easier than this way. Depending on your problem you have with your device I suggest you to open up a new thread in general section (or Q&A Section) and ask for help. BUT:
Don't flash anything to your phone if you don't know exactly what you're doing!.
Click to expand...
Click to collapse
problem solved master
i'm forget to use latest version of fastboot
now mw droid razr has startup normaly
tq all...
but now get new problem device always on fastboot n show "recipe failed"
maybe you can help me 4 this case...
Have same problem with other omap device Huawei U9500 (OMAP4440), but your advice not working unfortunately.
After the message about sending a file, nothing happens, the phone to mode fastboot not pass.
Any advice?
Hi all! XT926 is here)
Tell me please can I restore bootloader on my xt926 through this method? Right now when i connect common usb cable to moto and type "lsusb" i see:
ID: 05c6:f006 Qualcomm, Inc.
But when I connect the cable on Windows, the device appears and disappears in the system (I can hear the sound) infinite time, until I remove the cable.
Hello, need to root ZTE V790. Please help. Thank you very much.
Rooting ZTE V790
After series of serching, I was able to root zte V790 through the help of a chinese forum:
bbs.hiapk.com/thread-4620917-1-1.html :good:
Tools to Download
1. Download drivers.
mediafire.com/?f7h1f7i7skggmtg
2. Download V790 Root Tool
pan.baidu.com/share/link?shareid=379900&uk=255085915
DISCLAIMER: I AM NOT RESPONSIBLE IF YOU BRICK / RUIN YOUR PHONE IN ANY WAY. THE FOLLOWING ARE THE STEPS I HAVE FOLLOWED TO SUCCESSFULLY ROOT MY ZTE V790
Procedures:
1.Extract and Install all drivers in the computer.
2.Turn Off the phone and take the sim card out.
3.Turn on the phone. Ensure that the battery is not less than 50%.
4.Plug the usb cable from phone to computer. Ensure that the phone USB debugging is ticked.(Home>Settings>Developer options>USB Debugging). Phone USB computer connection should be "connected as an installer", this can be done by unticking Media device MTP or Camera PTP.
5.Run the Root Tool.exe. (Note that this is in chinese but there are few english words just Follow on screen prompts. It will automatically detect the phone if the drivers are installed correctly)
6.Phone will restart after the process is completed. (Whole process take about 2 to 5 minutes)
7.Once the phone has turned on, You can now see the Superuser icon and Root explorer. Congratulations, you are now rooted.:highfive:
If unsuccessful, repeat all the steps.
Hit Thanks.
astigjaps said:
After series of serching, I was able to root zte V790 through the help of a chinese forum:
bbs.hiapk.com/thread-4620917-1-1.html :good:
Tools to Download
1. Download drivers.
mediafire.com/?f7h1f7i7skggmtg
2. Download V790 Root Tool
pan.baidu.com/share/link?shareid=379900&uk=255085915
DISCLAIMER: I AM NOT RESPONSIBLE IF YOU BRICK / RUIN YOUR PHONE IN ANY WAY. THE FOLLOWING ARE THE STEPS I HAVE FOLLOWED TO SUCCESSFULLY ROOT MY ZTE V790
Procedures:
1.Extract and Install all drivers in the computer.
2.Turn Off the phone and take the sim card out.
3.Turn on the phone. Ensure that the battery is not less than 50%.
4.Plug the usb cable from phone to computer. Ensure that the phone USB debugging is ticked.(Home>Settings>Developer options>USB Debugging). Phone USB computer connection should be "connected as an installer", this can be done by unticking Media device MTP or Camera PTP.
5.Run the Root Tool.exe. (Note that this is in chinese but there are few english words just Follow on screen prompts. It will automatically detect the phone if the drivers are installed correctly)
6.Phone will restart after the process is completed. (Whole process take about 2 to 5 minutes)
7.Once the phone has turned on, You can now see the Superuser icon and Root explorer. Congratulations, you are now rooted.:highfive:
If unsuccessful, repeat all the steps.
Hit Thanks.
Click to expand...
Click to collapse
Wow, thanks.. Finally rooted mine. You're the man :highfive:
Astig ka nga!
help
jessiegoran said:
Wow, thanks.. Finally rooted mine. You're the man :highfive:
Astig ka nga!
Click to expand...
Click to collapse
tol bat ayaw gumana saakin ? na stock ako sa zte boot logo
Help
Hi every one, I bought ZTE V790 Movistar Motion, (in Venezuela) I've rooted and Install a Vietname Rom, Now my Phone Is (Model Number: V8403 Based version Viettel_V8403B01 Build Number VIETTEL_V8403V1.0.0B09) and it's a stupid Rom, I've tried to install another rom from Russian Site but my phone refuse it!!! I want my Phone Back I Don't want this Vietname Version Pleas HELP
Oh yes!!!
thanks for this tutorial bro.. it worked for me!!
now my phone is rooted!!
you're great dude..
thanks a lot..
BTW.. if i managed to root my phone is there any way i can unlock the SIM slots?
SIM2 is already unlocked but SIM1 slot is still locked.
thanks again dude..
it says adb is out of date...
Some tips:
1) If the device is not recognised in the root tool. Install JoinMe as well, it contains another USB driver.
2) If you are stuck in ZTE logo or "waiting for device", just enable an option in Windows Update to automatically search and install device drivers. Windows will ask this when you select 'Trouble shooting' if installing drivers fails.
3) You may need to install USB drivers in total three times from: ZTE USB driver, JoinMe and Windows Update.
ZTE 790 Root
My ZTE v790 still gets stuck in ZTE Logo.
Android driver still missing after selecting auto update drivers.
I'm using XP and it's online.
I reinstalled both the ZTE Drivers and Join ME.
Any other suggestions?
English version of ROM for v90
Hello
is there any English version ROM for v790? I have bought zte v790, android 2.3.6 and unfortunately there is plenty of useless applications in Chinese, as well as Chinese system communicates and the worst thing is that the browser is very difficult to get Google or any proper websites like facebook for example. I can do root and thank you for the instruction but then i will need to install ROM in english version. Is there any way to get English version for v790?
Thank you!
Mk
Heya,
I'm looking for android 4.0 rom for this phone too. Any know where i can find one? I've found Russian one but that's far from what I'm looking for.
Thanks
kptbomba said:
Heya,
I'm looking for android 4.0 rom for this phone too. Any know where i can find one? I've found Russian one but that's far from what I'm looking for.
Thanks
Click to expand...
Click to collapse
every rom has every language, just change it through the settings. i didn't find it very hard to guess where to click as there are icons and the language list has "english" in english. funny that.
Found the fix to getting stuck at ZTE Logo!
Hi guys,
Like Furiku, i kept getting stuck at the ZTE Logo when attempting the steps from the OP.
After doing some research, i found another spanish-language guide that included the Moto Helper drivers. Installing the drivers did the trick.
As i am a new user and cannot yet post links, please search for the file indicated below on google, install, and do the steps again. I'm using Windows 8 and there comes a point when it goes beyond the ZTE Logo to a green screen which looks pixelated, and i thought i might have ruined my phone. Gave me a 3-second heart attack. Then the Moto Helper drivers kicked in, and it rebooted, and now the SuperUser icon is there.
Please note that I am making the same disclaimer as the OP: Do this at your own risk. Follow instructions to the letter. We cannot be held responsible for issues that may lead to a damaged/bricked phone.
Google this file and DL: MotoHelper_2.1.32_Driver_5.4.0.exe
No go with Android 4
AzmoD3uS said:
Hi guys,
Like Furiku, i kept getting stuck at the ZTE Logo when attempting the steps from the OP.
After doing some research, i found another spanish-language guide that included the Moto Helper drivers. Installing the drivers did the trick.
As i am a new user and cannot yet post links, please search for the file indicated below on google, install, and do the steps again. I'm using Windows 8 and there comes a point when it goes beyond the ZTE Logo to a green screen which looks pixelated, and i thought i might have ruined my phone. Gave me a 3-second heart attack. Then the Moto Helper drivers kicked in, and it rebooted, and now the SuperUser icon is there.
Please note that I am making the same disclaimer as the OP: Do this at your own risk. Follow instructions to the letter. We cannot be held responsible for issues that may lead to a damaged/bricked phone.
Google this file and DL: MotoHelper_2.1.32_Driver_5.4.0.exe
Click to expand...
Click to collapse
I've installed all the drivers. On the English words displayed (after being told to press any key & doing so), I get "fastboot error: protocol fault (no status)" & "< waiting for device >" with the phone's display stuck on the ZTE logo. I think that the problem is that my phone uses Android 4 (Jelly Bean) whereas other phones successfully rooted are using Android 2 (Gingerbread). Any ideas?
astigjaps said:
After series of serching, I was able to root zte V790 through the help of a chinese forum:
bbs.hiapk.com/thread-4620917-1-1.html :good:
Tools to Download
1. Download drivers.
mediafire.com/?f7h1f7i7skggmtg
2. Download V790 Root Tool
pan.baidu.com/share/link?shareid=379900&uk=255085915
DISCLAIMER: I AM NOT RESPONSIBLE IF YOU BRICK / RUIN YOUR PHONE IN ANY WAY. THE FOLLOWING ARE THE STEPS I HAVE FOLLOWED TO SUCCESSFULLY ROOT MY ZTE V790
Procedures:
1.Extract and Install all drivers in the computer.
2.Turn Off the phone and take the sim card out.
3.Turn on the phone. Ensure that the battery is not less than 50%.
4.Plug the usb cable from phone to computer. Ensure that the phone USB debugging is ticked.(Home>Settings>Developer options>USB Debugging). Phone USB computer connection should be "connected as an installer", this can be done by unticking Media device MTP or Camera PTP.
5.Run the Root Tool.exe. (Note that this is in chinese but there are few english words just Follow on screen prompts. It will automatically detect the phone if the drivers are installed correctly)
6.Phone will restart after the process is completed. (Whole process take about 2 to 5 minutes)
7.Once the phone has turned on, You can now see the Superuser icon and Root explorer. Congratulations, you are now rooted.:highfive:
If unsuccessful, repeat all the steps.
Hit Thanks.
Click to expand...
Click to collapse
jessiegoran said:
Wow, thanks.. Finally rooted mine. You're the man :highfive:
Astig ka nga!
Click to expand...
Click to collapse
How do you install the CFW????
Please help
Thanks
Is there any custom ROM for this phone?
Why when I plug jt my computer it says it's a V790 when it's a t2 lite
First, sory for my bad English
I'd tried to root my kindle but I make mistake with build.prop and now it's bricked
I'd tried almost methods in this forum but adb still dont regconize my kindle,so i cant do anything like " adb shell, adb root...." to fix it
Pls help me to fix my kindle
?
tuilakhang said:
First, sory for my bad English
I'd tried to root my kindle but I make mistake with build.prop and now it's bricked
I'd tried almost methods in this forum but adb still dont regconize my kindle,so i cant do anything like " adb shell, adb root...." to fix it
Pls help me to fix my kindle
Click to expand...
Click to collapse
Whatever you do do not do a factory reset and less you are about to drop it in the mailbox
http://forum.xda-developers.com/showthread.php?t=2781665. Post 66. And Have you read and tried last three pages here ? http://forum.xda-developers.com/showthread.php?t=2588608 and check read last three pages of http://forum.xda-developers.com/showthread.php?t=2782159 and include read OP on both thoroughly... If you have follow directions to T ..Too no avail .. Then there is probably no help to be had for you I apologize... That is without fastboot capabilities and an unlocked boot loader.
I'd read this and can't get it so well
My problem is adb don't regonize my device, and I can't do anything with adb command
jimyv said:
Whatever you do do not do a factory reset and less you are about to drop it in the mailbox
http://forum.xda-developers.com/showthread.php?t=2781665. Post 66. And Have you read and tried last three pages here ? http://forum.xda-developers.com/showthread.php?t=2588608 and check read last three pages of http://forum.xda-developers.com/showthread.php?t=2782159 and include read OP on both thoroughly... If you have follow directions to T ..Too no avail .. Then there is probably no help to be had for you I apologize... That is without fastboot capabilities and an unlocked boot loader.
Click to expand...
Click to collapse
I'd read this and can't get it so well
My problem is adb don't regonize my device, and I can't do anything with adb command
?
tuilakhang said:
I'd read this and can't get it so well
My problem is adb don't regonize my device, and I can't do anything with adb command
Click to expand...
Click to collapse
you followed all the directions on how to install sdk and uninstall old drivers ect http://forum.xda-developers.com/showthread.php?t=2588608 again the last 3 pages here are about installing the sdk to get it to see ....like I said before if you have done this and follow through and not just looked at it and thought it might not work then there's probably no help for you. Sorry folks if you don't understand and know how to use this info..there is hardly no help for you because currently there is not a 1 click solution...besides a call to amazon.....
You have the JDK & Android SDK installed? Occasionally I had issues connecting to adb when recreating previous bootloops & soft bricks. It seems that it gets hung up in a stat that Windows doesn't like. The only way I could get adb to function at these times was to run a Linux distro or on a Linux machine. You can download the wubi installer for dual booting Unbuntu, which is what 99% of people that have had issues have done to regain adb access. Linux just seems to play better with Android & the Android SDK tools, which really isn't surprising.
GSLEON3 said:
You have the JDK & Android SDK installed? Occasionally I had issues connecting to adb when recreating previous bootloops & soft bricks. It seems that it gets hung up in a stat that Windows doesn't like. The only way I could get adb to function at these times was to run a Linux distro or on a Linux machine. You can download the wubi installer for dual booting Unbuntu, which is what 99% of people that have had issues have done to regain adb access. Linux just seems to play better with Android & the Android SDK tools, which really isn't surprising.
Click to expand...
Click to collapse
I installed Ubuntu but when I open it, adb is not found, pls help me 2 use Ubuntu
Second, I just asked some friends have the old kindle verson, they say I should use Factory cable, will it work ????
tuilakhang said:
I installed Ubuntu but when I open it, adb is not found, pls help me 2 use Ubuntu
Second, I just asked some friends have the old kindle verson, they say I should use Factory cable, will it work ????
Click to expand...
Click to collapse
NO. This is not an OMAP device & it does NOT use uBoot, so factory cable is useless. Try a different USB port. Also, if you installed Linux, you still have to install the Java JDK & the Android SDK. There are some guides for setting up a build environment, which is pretty much what you need to do to really be able to use the tools in Windows or Linux. Taske a look here: Setting up a build environment in Unbuntu
You don't need Python or Gnu, nor the modules, but you must sdet up the JDK & the SDK & then set the paths.
tuilakhang said:
I installed Ubuntu but when I open it, adb is not found, pls help me 2 use Ubuntu
Second, I just asked some friends have the old kindle verson, they say I should use Factory cable, will it work ????
Click to expand...
Click to collapse
as I said maybe something will come through QPST
at least QPST detects Kindle HDX 8.9 (gray logo and then a black screen) with factory cable
I also lock the device after editing build.prop
but I lack the knowledge and skills to continue this way (in order not to kill the device)
thread(chinese) http://blog.csdn.net/syhost/article/details/20435957
amazonhdx said:
as I said maybe something will come through QPST
at least QPST detects Kindle HDX 8.9 (gray logo and then a black screen) with factory cable
I also lock the device after editing build.prop
but I lack the knowledge and skills to continue this way (in order not to kill the device)
thread(chinese) http://blog.csdn.net/syhost/article/details/20435957
Click to expand...
Click to collapse
Yeah, I don't read chinese & google doesn't do a very good job translating it, so, not gonna even try.
HOWEVER, I do know that you will need the Lab126 HSUSB driver. I don't remember if this was the one I used, but it was similarly named, I think this is for the BC radio stack diagnostic bulk mode originally & worked for the HDX. http://www.driverscape.com/download/lab126-hs-usb-diagnostics-0800-(com39)
Actually, I remember playing with this & thinking it could be useful for some of the early HDX issue I ran across too: http://forum.xda-developers.com/showthread.php?t=2582142
GSLEON3 said:
Yeah, I don't read chinese & google doesn't do a very good job translating it, so, not gonna even try.
HOWEVER, I do know that you will need the Lab126 HSUSB driver. I don't remember if this was the one I used, but it was similarly named, I think this is for the BC radio stack diagnostic bulk mode originally & worked for the HDX. http://www.driverscape.com/download/lab126-hs-usb-diagnostics-0800-(com39)
Actually, I remember playing with this & thinking it could be useful for some of the early HDX issue I ran across too: http://forum.xda-developers.com/showthread.php?t=2582142
Click to expand...
Click to collapse
Ths 4 your guide and I will try with it and feed back tonight
stuck in same problem
my device still can't be recognized, still the same when it first bricked
GSLEON3 said:
Yeah, I don't read chinese & google doesn't do a very good job translating it, so, not gonna even try.
HOWEVER, I do know that you will need the Lab126 HSUSB driver. I don't remember if this was the one I used, but it was similarly named, I think this is for the BC radio stack diagnostic bulk mode originally & worked for the HDX. http://www.driverscape.com/download/lab126-hs-usb-diagnostics-0800-(com39)
Actually, I remember playing with this & thinking it could be useful for some of the early HDX issue I ran across too: http://forum.xda-developers.com/showthread.php?t=2582142
Click to expand...
Click to collapse
how can I download Lab126 HSUSB, I enter your link and download driver toolkit, but I can't see Lab126... and it's a paid license
tuilakhang said:
how can I download Lab126 HSUSB, I enter your link and download driver toolkit, but I can't see Lab126... and it's a paid license
Click to expand...
Click to collapse
You'll have to search around for it. Lab126 is the company that makes the HDX. That page only shows you the various driver names, the correct com port & identifies what device you want to see in device manager once you get QPST set up properly.
GSLEON3 said:
You'll have to search around for it. Lab126 is the company that makes the HDX. That page only shows you the various driver names, the correct com port & identifies what device you want to see in device manager once you get QPST set up properly.
Click to expand...
Click to collapse
I had google it and I can't find any lnk for this driver, can you give me this driver or link I can down
tuilakhang said:
I had google it and I can't find any lnk for this driver, can you give me this driver or link I can down
Click to expand...
Click to collapse
try it http://www.mediafire.com/download/xnjxkd49dn9d75j/QualcommDrv.zip
or it http://kindle-sdk.s3.amazonaws.com/2ba63011a73a0a0d0f35e001696677ec92a825cb.zip
amazonhdx said:
try it http://www.mediafire.com/download/xnjxkd49dn9d75j/QualcommDrv.zip
or it http://kindle-sdk.s3.amazonaws.com/2ba63011a73a0a0d0f35e001696677ec92a825cb.zip
Click to expand...
Click to collapse
ths 4 your sharing, but it's not work with me too, I has tried with 2 laptop and 3 or 4 cables, but it's not work too, don't have any signal when I connect it. I can't understand why I can't be
tuilakhang said:
ths 4 your sharing, but it's not work with me too, I has tried with 2 laptop and 3 or 4 cables, but it's not work too, don't have any signal when I connect it. I can't understand why I can't be
Click to expand...
Click to collapse
if kindle bricked (for example after a failure edit build.prop - gray logo and black screen), pc not detect device with standart microusb cable, driver can not be installed, adb not working.
but if use factory cable (buy or make), then the device connect as a usb bulk. you may install the first driver to it.
further steps to recovery does not exist yet
amazonhdx said:
if kindle bricked (for example after a failure edit build.prop - gray logo and black screen), pc not detect device with standart microusb cable, driver can not be installed, adb not working.
but if use factory cable (buy or make), then the device connect as a usb bulk. you may install the first driver to it.
further steps to recovery does not exist yet
Click to expand...
Click to collapse
So, What shoud I do to connect my kindle?
tuilakhang said:
So, What shoud I do to connect my kindle?
Click to expand...
Click to collapse
if kindle bricked (gray logo, thor not installed), just wait until a way to recover
hi all. i search for root or recovery for this device i d'ont found anything, On the other hand there is assistance and development for similar devices MT 6735 like gionee.
What exactly is your device? Some MTK device gets a somewhat unstable support because they are popular or someone wants to work on it
A_Random_Guy said:
What exactly is your device? Some MTK device gets a somewhat unstable support because they are popular or someone wants to work on it
Click to expand...
Click to collapse
hi : my device is LG K220DS, is there a support for this device, i like the MIUI roms i hope it will be ported for our device.
elhattak7 said:
hi : my device is LG K220DS, is there a support for this device, i like the MIUI roms i hope it will be ported for our device.
Click to expand...
Click to collapse
Your device doesn't seem to have one unfortunately
Possible boost mobile version of the LG X Power
Ok I have the Boost Mobile version of the LG X Power. I found a video on youtube. It is putting the root file in the root of the phone. Let me explain. You download a superSU file. You connect the phone to the computer PC. Put the root file in the list of files in the directory. That makes it stand out. To install you go into the recovery on the phone. You don't install it. It is part of the system. Turn off phone. Hold power down and volume down. You enter recovery. You highlight the superSU file and select. It should root the phone. This is the way the very first android phones got rooted. I'm to tired now to try it. Heres the video. Tell me what you think.
How to ROOT ANY Android Device! without PC Using SuperSU [2017]
I'm to new to post a link. I still want to provide help. Just paste the above in a you tube search. Good night All
Does not work. Tried today. It couldn't be that easy.
Open Developer mode
Been searching high and low. Found the below instructions on how to open developer mode on the LG X power. As it says follow at own risk. I did it and got it open to developer mode. I hope this furthers us down a path to root.
Declaration
Do this on your own risk. You device's warranty may be void after following these instructions. If any thing goes wrong and you just end up with a bricked or semi-bricked device then nieghter our site or any of these app devolopers will be responsible.
Your device must have atleat 60% of charge.
Goto Settings -> Security and enable the "Unknown sources".
For your safety, please take backup of your importent stuffs.
Turn on USB debugging mode from Developer Options on your LG X power. To turn on USB debugging you have to enable Developer options, GoTo settings -> About and tap multiple times on build number.
Looking to help
UPDATE
Got my phone into developer mode. Did the things to make it ready to take code easier. With the above it failed to install. So it didn't kill the phone. It only lead to another dead end. If you do watch the video. He claims you need to install recovery first then root. That is backwards. You root first. Then you go into the app store and download a recovery. Or find one in here to download.
As I read in this forum I find old information. Most stuff on this phone or even others I have found is outdated. The stuff on this phone was from 2016. Other info how to fix a brick phone is from 2014. Which is making things harder. Technology moves much faster. Most things said about this phone in 2016 have been changed or patched. I use the search bar to only find what I need. Still its old.
Not trying to be negative about the forum. I just want to learn. Anybody out there with good information on the LG X power from boost mobile. Please help me? LG is a hard nut to crack. Is there a nutcracker out there?
Hello everyone,
I've been tinkering with my kindle attempting to flash TWRP so I could flash other ROMs on my Kindle Fire HDX 7 (3rd generation) but I have seemed to soft brick the device after using unlock.bat from https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982/post70881555#post70881555
The unlock.bat was supposed to unlock my bootloader, but now the device won't power on. If I plug it into the windows a bunch of partitions appear and windows prompts me if I want to format the various drives. If I plug my kindle into Linux, the 7 (i think) partitions show folders various different system functions.
Someone wrote in a separate forum that it's possible to restore kindle if I using something called eMMC Raw tool, but didn't really give any clear instructions.
If anyone could help me recover my device, that would be greatly appreciated. Thank you.
For some reason I can't upload a picture of the various files in the partition.
Side note: could I theoretically put CM 12 or anything else on one of the partitions instead of the stock ROM?
Praxxer1 said:
Hello everyone,
I've been tinkering with my kindle attempting to flash TWRP so I could flash other ROMs on my Kindle Fire HDX 7 (3rd generation) but I have seemed to soft brick the device after using unlock.bat from https://forum.xda-developers.com/ki...r-firmware-t3463982/post70881555#post70881555
The unlock.bat was supposed to unlock my bootloader, but now the device won't power on. If I plug it into the windows a bunch of partitions appear and windows prompts me if I want to format the various drives. If I plug my kindle into Linux, the 7 (i think) partitions show folders various different system functions.
Someone wrote in a separate forum that it's possible to restore kindle if I using something called eMMC Raw tool, but didn't really give any clear instructions.
If anyone could help me recover my device, that would be greatly appreciated. Thank you.
Click to expand...
Click to collapse
Unlock.bat did not "soft brick" your device as the actions it performs are totally benign. More likely you got sloppy and flashed an incompatible aboot (via dd) or erased aboot and don't know how to recover. Me thinks it is the latter. Keep reading; you'll eventually stumble on posts that describe corrective actions. I will edit this post with a link as time permits.
You do not need "eMMC Raw Tool" whatever that is.
edit: https://forum.xda-developers.com/ki...ing-bootloader-firmware-t3463982/post75284993
Davey126 said:
Unlock.bat did not "soft brick" your device as the actions it performs are totally benign. More likely you got sloppy and flashed an incompatible aboot (via dd) or erased aboot and don't know how to recover. Me thinks it is the latter. Keep reading; you'll eventually stumble on posts that describe corrective actions. I will edit this post with a link as time permits.
You do not need "eMMC Raw Tool" whatever that is.
edit: https://forum.xda-developers.com/ki...ing-bootloader-firmware-t3463982/post75284993
Click to expand...
Click to collapse
Ah. I wish I had seen that thread before I started the process! You may be right about the compatible boot. I couldn't find the original aboot_vuln.mbn file mentioned in the thread I was following, but managed to find aboot.img file and flashed that hoping it was the same. I could have sworn though, that the device stopped working the second after I clicked the unlock.bat file (executed outside the fastboot screen), but could be wrong.
Only problem about the thread you linked, device isn't responding to any ADB or fastboot commands, but still shows that my PC recognizes the device as a fire device.
Thank you for your time, I'll keep reading through the thread you linked.
Praxxer1 said:
Only problem about the thread you linked, device isn't responding to any ADB or fastboot commands, but still shows that my PC recognizes the device as a fire device.
Click to expand...
Click to collapse
Likely a Windows driver issue. Suggest installing Motorola Device Manager here which includes composite USB drivers that work reliably with HDX devices. Need need to run MDM; just install it. After connecting the device you will need update the driver via Windows Device Manager. Bit of hit and miss with a non-functioning device. Cables and USB ports also play a huge role, especially with fussy bootloader/fastboot communications. Avoid external hubs, USB3 ports and add-on expansion cards. Change cables, ports, etc. Good luck.
Davey126 said:
Likely a Windows driver issue. Suggest installing Motorola Device Manager here which includes composite USB drivers that work reliably with HDX devices. Need need to run MDM; just install it. After connecting the device you will need update the driver via Windows Device Manager. Bit of hit and miss with a non-functioning device. Cables and USB ports also play a huge role, especially with fussy bootloader/fastboot communications. Avoid external hubs, USB3 ports and add-on expansion cards. Change cables, ports, etc. Good luck.
Click to expand...
Click to collapse
Thanks Davey, I'll definitely give it a try. Just as a bit more information on my situation, the device manager on windows does read Fire Device "ADB composite driver". I also have it connected to the PC using a Fastboot Cable. I will give all of this a try when I get home from work today.
If I am able to communicate with the device after installing the MDM drivers, should I attempt to restore the device? Or try to unlock and flash the stock ROM?
Praxxer1 said:
Thanks Davey, I'll definitely give it a try. Just as a bit more information on my situation, the device manager on windows does read Fire Device "ADB composite driver". I also have it connected to the PC using a Fastboot Cable. I will give all of this a try when I get home from work today.
If I am able to communicate with the device after installing the MDM drivers, should I attempt to restore the device? Or try to unlock and flash the stock ROM?
Click to expand...
Click to collapse
- dump the fastboot cable (all but useless on a HDX); this isn't a generic Android device
- ADB composite drivers come in many flavors; HDX bootloader only likes a few of them
- if/when you reestablish communication first step is to restore aboot and install TWRP; unlocking and ROM installation come later
- do not attempt to reinstall stock; frustration and heartache consume those who do
- again, this is not a run-of-the-mill Android gizmo; many of the tricks you learned in kindergarden do not apply to Amazon tablets
Davey126 said:
- dump the fastboot cable (all but useless on a HDX); this isn't a generic Android device
- ADB composite drivers come in many flavors; HDX bootloader only likes a few of them
- if/when you reestablish communication first step is to restore aboot and install TWRP; unlocking and ROM installation come later
- do not attempt to reinstall stock; frustration and heartache consume those who do
- again, this is not a run-of-the-mill Android gizmo; many of the tricks you learned in kindergarden do not apply to Amazon tablets
Click to expand...
Click to collapse
Lol I feel like I'm in kindergarten tinkering with this HDX. How do I restore aboot? clearly the image I flashed with was not the correct bootloader. Should I attempt to extract aboot from the stock ROM? Or would you be able to share you tool set/point me to a working link for aboot, TWRP, and ROMs (I've looked at 4 threads so far without working links)?
UPDATE: I managed to install the ADB MOT Composite driver, but still no response to simple ADB and Fastboot commands
Thanks again
Praxxer1 said:
Lol I feel like I'm in kindergarten tinkering with this HDX. How do I restore aboot? clearly the image I flashed with was not the correct bootloader. Should I attempt to extract aboot from the stock ROM? Or would you be able to share you tool set/point me to a working link for aboot, TWRP, and ROMs (I've looked at 4 threads so far without working links)?
UPDATE: I managed to install the ADB MOT Composite driver, but still no response to simple ADB and Fastboot commands
Thanks again
Click to expand...
Click to collapse
Not uncommon. Unfortunately, there is no 'fix script' moving forward as each situation is unique. If aboot is too damaged to support basic communication it's pretty much game over for the average laymen. You will need to comb the threads for information nuggets that may apply to your situation. Or cut your losses and move on. I am not big on trying to unbrick these pups unless one well versed in low level trouble shooting. Lousy ROI; has to be a labor of love including copious time researching, trying and (likely) failing. Good luck.
@draxie - for awareness; read back a few posts for context.
1-Click is your friend
Davey126 said:
Not uncommon. Unfortunately, there is no 'fix script' moving forward as each situation is unique. If aboot is too damaged to support basic communication it's pretty much game over for the average laymen. You will need to comb the threads for information nuggets that may apply to your situation. Or cut your losses and move on. I am not big on trying to unbrick these pups unless one well versed in low level trouble shooting. Lousy ROI; has to be a labor of love including copious time researching, trying and (likely) failing. Good luck.
@draxie - for awareness; read back a few posts for context.
Click to expand...
Click to collapse
Right... the symptoms described are the normal state of affairs
after 'fastboot erase aboot' and 'unlock.bat' does no such thing.
The post linked above and/or my original "Bulk mode" post both
have the necessary instructions to recover. Alternatively, 1-Click
can handle this, assuming access to either MacOS or Linux (for
the time being).