Related
Hey guys I'm a newbie here and I am probably way over my head but I have an issue. I did something stupid and edited some build props to try to get a game to work. Now when I start my kindle its stuck on "starting applications: updating kindle". Like I said I'm really new to all this rooting stuff and even just android products. I have a jailbroken iPhone 4 and I thought all this we b cool to try. I successfully rooted my kindle fire he 7 a few days back and was having fun with the play store but I got way over my head and now I'm stuck. I need to know how to restore or reset my kindle thru the computer bc it doesn't even turn on.. Oh and by the way I'm really bad with all this adb, recovery, fastboot stuff like I said newbie.. PLEASE HELP
lacoursiere18 said:
Hey guys I'm a newbie here and I am probably way over my head but I have an issue. I did something stupid and edited some build props to try to get a game to work. Now when I start my kindle its stuck on "starting applications: updating kindle". Like I said I'm really new to all this rooting stuff and even just android products. I have a jailbroken iPhone 4 and I thought all this we b cool to try. I successfully rooted my kindle fire he 7 a few days back and was having fun with the play store but I got way over my head and now I'm stuck. I need to know how to restore or reset my kindle thru the computer bc it doesn't even turn on.. Oh and by the way I'm really bad with all this adb, recovery, fastboot stuff like I said newbie.. PLEASE HELP
Click to expand...
Click to collapse
You will need to get into fastboot somehow to fix it.
You are new to adb but you had to have had the drivers installed to root, so when you connect it to the computer does it show up in your device manager?
If yes, then you can get into fastboot by opening a cmd prompt where you have access to adb. If you used the qemu root tool then the files you need will be in there.(Or since you will need it anyway, download KFHD Restore tool from here: LINK, you will want v1.2.3, it also has adb files you'll need). To open a cmd prompt from that folder, hold shift and right click on the folder. There should be an option to "open cmd prompt from this location", or something to that affect.
In the cmd prompt use these cmds(press enter between each cmd):
Code:
adb shell
su
reboot bootloader
After you are in fastboot then follow the directions in the Restore Tool post from the link above.
If you can't get into fastboot that way then you will need a factory cable, You can make your own or here is where you can buy one: Factory Cable by Skorpn. I've also heard of people purchasing on amazon but not as quality as Skorpn's
onemeila said:
You will need to get into fastboot somehow to fix it.
You are new to adb but you had to have had the drivers installed to root, so when you connect it to the computer does it show up in your device manager?
If yes, then you can get into fastboot by opening a cmd prompt where you have access to adb. If you used the qemu root tool then the files you need will be in there.(Or since you will need it anyway, download KFHD Restore tool from here: LINK, you will want v1.2.3, it also has adb files you'll need). To open a cmd prompt from that folder, hold shift and right click on the folder. There should be an option to "open cmd prompt from this location", or something to that affect.
In the cmd prompt use these cmds(press enter between each cmd):
Code:
adb shell
su
reboot bootloader
After you are in fastboot then follow the directions in the Restore Tool post from the link above.
If you can't get into fastboot that way then you will need a factory cable, You can make your own or here is where you can buy one: Factory Cable by Skorpn. I've also heard of people purchasing on amazon but not as quality as Skorpn's
Click to expand...
Click to collapse
Now when I plugged it in the first time I saw it in the device manager with a yellow triangle and an explantion mark. Yes I was definetly rooted bc I had the google play store and access to a lot. When you say you can open a command prompt where you have access to adb.. what do you mean. Like I said a newbie. I know where command prompt is on my computer but Im not sure about this adb thing. Could you explain step by step Windows XP. And the folder your talking about is the one you provided the link for? Sorry so many ?'s I really appreciae you time.
anybody... PLEASE
You are in the wrong forum. This is for 2nd generation Kindle Fire 2/Kindle Fire HDs, and you obviously have an original 1st generation Kindle Fire.
You need to take a step back for a second and do a little research before you proceed and get a better idea of what's going on. A great place to start is a thread in the Amazon Kindle Fire General forum titled "Kindle Fire for Beginners". It will give you a better understanding of how things work and possibly how to fix it.
Outside of that, there are tools and utilities to help you along the way but in your situation, you really need to understand why your Kindle isn't working properly for them to do you much good.
Oh, and if you're looking for "step-by-step" instructions from someone, it probably won't happen. The information is there, you just have to find it. You wouldn't start working on your car without having the knowledge to do so, therefore why would you try with a technological piece of equipment?
That being said, if you have a question or need help understanding something in particular, I'm sure there will be plenty of people who would be wiling to assist you.
"That's a special kind of stupid. The kind that makes me laugh"
soupmagnet said:
You are in the wrong forum. This is for 2nd generation Kindle Fire 2/Kindle Fire HDs, and you obviously have an original 1st generation Kindle Fire.
You need to take a step back for a second and do a little research before you proceed and get a better idea of what's going on. A great place to start is a thread in the Amazon Kindle Fire General forum titled "Kindle Fire for Beginners". It will give you a better understanding of how things work and possibly how to fix it.
Outside of that, there are tools and utilities to help you along the way but in your situation, you really need to understand why your Kindle isn't working properly for them to do you much good.
Oh, and if you're looking for "step-by-step" instructions from someone, it probably won't happen. The information is there, you just have to find it. You wouldn't start working on your car without having the knowledge to do so, therefore why would you try with a technological piece of equipment?
That being said, if you have a question or need help understanding something in particular, I'm sure there will be plenty of people who would be wiling to assist you.
"That's a special kind of stupid. The kind that makes me laugh"
Click to expand...
Click to collapse
Nice quote.. Well at least I know now who not to talk too in this forum. If YOU CAN READ in my origanl post it says I have a Kindle Fire HD 7!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! That being said I have done a lot of research on this throughout the day and I am planning on attempting what the origanl replier was talking about. Don't be a ****, life's to short.
lacoursiere18 said:
Nice quote.. Well at least I know now who not to talk too in this forum. If YOU CAN READ in my origanl post it says I have a Kindle Fire HD 7!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! That being said I have done a lot of research on this throughout the day and I am planning on attempting what the origanl replier was talking about. Don't be a ****, life's to short.
Click to expand...
Click to collapse
Ok i'm going to back up a little bit and appologize for calling you a ****. But, maybe you need re read what you wrote or maybe I took you text out of context. For a newbie on this site, you came accross pretty offensive. But I took your advice and read the Kindle Fire for Begginers and learned quite a bit. I will def have to re read it several times but it helped. So again I apologize and thank you
lacoursiere18 said:
Nice quote.. Well at least I know now who not to talk too in this forum. If YOU CAN READ in my origanl post it says I have a Kindle Fire HD 7!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! That being said I have done a lot of research on this throughout the day and I am planning on attempting what the origanl replier was talking about. Don't be a ****, life's to short.
Click to expand...
Click to collapse
Yes I did read what you wrote, and you said when you plug the device in, all you see is the "yellow triangle". Typically speaking, the "yellow triangle" is typical of a modified bootloader which can only be found on the original Kindle Fires. It is possible we aren't speaking about the same yellow triangle so I apologize for making the assumption. But when you see as many egregiously ignorant questions I see from new users every day, and the extraordinary number of users that don't know the difference between the different KF devices, you'll see how easy it is to make that mistake.
I've helped a lot of people around here, and my "matter of fact" way of going about it has prevented a lot of unneeded mishaps, so for that, I won't apologize. And if you think I'm a **** for expecting a new user to adhere to the policies and guidelines set forth by XDA and research basic tasks like using the command prompt and ADB, so be it. But the fact still remains, people here are more likely to give you general instructions and expect you to know how to carry them out on your own, than spend the time to write out explicit step-by-step instructions for something that takes more than a few lines of text to explain, and in such a way that someone who knows nothing about it can understand.
Take my advice or don't, but whether you think so or not, I am trying to help by getting you going in the right direction, so you can get your problem solved in a more efficient manner.
soupmagnet said:
Yes I did read what you wrote, and you said when you plug the device in, all you see is the "yellow triangle". Typically speaking, the "yellow triangle" is typical of a modified bootloader which can only be found on the original Kindle Fires. It is possible we aren't speaking about the same yellow triangle so I apologize for making the assumption. But when you see as many egregiously ignorant questions I see from new users every day, and the extraordinary number of users that don't know the difference between the different KF devices, you'll see how easy it is to make that mistake.
I've helped a lot of people around here, and my "matter of fact" way of going about it has prevented a lot of unneeded mishaps, so for that, I won't apologize. And if you think I'm a **** for expecting a new user to adhere to the policies and guidelines set forth by XDA and research basic tasks like using the command prompt and ADB, so be it. But the fact still remains, people here are more likely to give you general instructions and expect you to know how to carry them out on your own, than spend the time to write out explicit step-by-step instructions for something that takes more than a few lines of text to explain, and in such a way that someone who knows nothing about it can understand.
Take my advice or don't, but whether you think so or not, I am trying to help by getting you going in the right direction, so you can get your problem solved in a more efficient manner.
Click to expand...
Click to collapse
ok now I am stuck. I have got my adb drivers installed and I believe correctly. I use the cmd prompt to navigate to the folder and execute those commands given. My kindle now has a Fastboot logo, that it nothing else. I went to use the tool in the LINK given and I try option 3? EDIT: ok so I hit option 3 and it went through its thing. It restarted my kindle and it was stuck on the highlighted kindle fire logo forever....
lacoursiere18 said:
ok now I am stuck. I have got my adb drivers installed and I believe correctly. I use the cmd prompt to navigate to the folder and execute those commands given. My kindle now has a Fastboot logo, that it nothing else. I went to use the tool in the LINK given and I try option 3? EDIT: ok so I hit option 3 and it went through its thing. It restarted my kindle and it was stuck on the highlighted kindle fire logo forever....
Click to expand...
Click to collapse
Ok i am officially out of luck and knowledge. I truned off my kindle when it was stuck on the highlighted kindle logo. I went to restart and now my computer does not recognize it. I am starting form scracth I deleted everything on my computer I dont know what to do
lacoursiere18 said:
Ok i am officially out of luck and knowledge. I truned off my kindle when it was stuck on the highlighted kindle logo. I went to restart and now my computer does not recognize it. I am starting form scracth I deleted everything on my computer I dont know what to do
Click to expand...
Click to collapse
You're still ok, I sent you a PM on what you'll need to do.
fire is upgrading, starting applications stuck
onemeila said:
You're still ok, I sent you a PM on what you'll need to do.
Click to expand...
Click to collapse
I have also the similar problem with my hdx 7, it stuck at "fire is upgrading, starting applications", i have tried factory reset, but it proved to be useless. I have talked to Amazon, they ask me to send my hdx back them(without any repayment) and buy a new one. So amazon will not help solve this problem, then do u have a solution pls?
Hi, I recently ran into the same problem with the "fire is upgrading, starting applications" screen and could not solve it yet. First of all let me tell you the facts:
Kindle Fire HD 7 (3rd generation)
FireOS 4.5.5.1 (no update available when checking for update on the Kindel Fire itself)
Developers mode enabled
adb is unauthorized (unfortunately)
OTA was unfortunately on
Rooted with Kingroot
I was playing around with my Kindle and checked out Kingroot and rooted my Kindle with it. Unfortunately I got distracted forgot to disable OTA updates and guess there lies the problem of my misery, i.e. the sudden Kindle Fire update over night with the starting applications message (where the starting applications takes a long time, i.e. never ends). Hence, I can not operate my Kindle Fire, and moreover I cannot access it over adb since the device is unauthorized. Side note, I'm using Linux and OSX and have Win7 in a VM (if there are OS specific solutions/tools for solving my problem). I'm not in possession of a factory cable (also don't have tools to build one). However if someone has a suggestion there it is welcome.
Now to my questions:
Will I need the factory cable?
If not, where should I focus on first?
If yes, any tips and tricks are welcome.
Hope someone can help me here, thanks.
buschko said:
Hi, I recently ran into the same problem with the "fire is upgrading, starting applications" screen and could not solve it yet. First of all let me tell you the facts:
Kindle Fire HD 7 (3rd generation)
FireOS 4.5.5.1 (no update available when checking for update on the Kindel Fire itself)
Developers mode enabled
adb is unauthorized (unfortunately)
OTA was unfortunately on
Rooted with Kingroot
I was playing around with my Kindle and checked out Kingroot and rooted my Kindle with it. Unfortunately I got distracted forgot to disable OTA updates and guess there lies the problem of my misery, i.e. the sudden Kindle Fire update over night with the starting applications message (where the starting applications takes a long time, i.e. never ends). Hence, I can not operate my Kindle Fire, and moreover I cannot access it over adb since the device is unauthorized. Side note, I'm using Linux and OSX and have Win7 in a VM (if there are OS specific solutions/tools for solving my problem). I'm not in possession of a factory cable (also don't have tools to build one). However if someone has a suggestion there it is welcome.
Now to my questions:
Will I need the factory cable?
If not, where should I focus on first?
If yes, any tips and tricks are welcome.
Hope someone can help me here, thanks.
Click to expand...
Click to collapse
Short update:
I now have a factory cable but I'm stuck at the moment. My first try was to get TWRP and somehow get into recovery. Thus I started with booting into fastboot with the factory cable and issued
Code:
fastboot -i 0x1949 flash recovery recovery.img
and the command succeeded. Then I wanted to issue:
Code:
fastboot -i 0x1949 oem idme bootmode 5001
however, the command got stuck and nothing happened. I just tried a reboot and after that I was able to issue the command. Thus I started my Kindle again and it shortly flashed and went black. Nothing further. Thus reset and start again. Now it just gets stuck in the grey Kindle Fire screen. If I try to boot into recovery (power + volume down) also nothing happens.
Can anyone give any tips here?
buschko said:
Short update:
I now have a factory cable but I'm stuck at the moment. My first try was to get TWRP and somehow get into recovery. Thus I started with booting into fastboot with the factory cable and issued
Code:
fastboot -i 0x1949 flash recovery recovery.img
and the command succeeded. Then I wanted to issue:
Code:
fastboot -i 0x1949 oem idme bootmode 5001
however, the command got stuck and nothing happened. I just tried a reboot and after that I was able to issue the command. Thus I started my Kindle again and it shortly flashed and went black. Nothing further. Thus reset and start again. Now it just gets stuck in the grey Kindle Fire screen. If I try to boot into recovery (power + volume down) also nothing happens.
Can anyone give any tips here?
Click to expand...
Click to collapse
Next update. I switched from my MacBook with OSX to my Desktop with Linux. Now I can issue more than one fastboot command in a row. However I'm stuck again. I issued the following commands:
Code:
fastboot -i 0x1949 oem format
fastboot -i 0x1949 flash boot hijack.img
fastboot -i 0x1949 flash system system.img
fastboot -i 0x1949 continue
Now I wait for the Amazon logo with the orange underline, however, I'm continue to see the fastboot screen. Thus I'm stuck again.
Hence, I just powered off and on again and then I was able to issue fastboot commands again. Continued with
Code:
fastboot -i 0x1949 flash boot recovery.img
fastboot -i 0x1949 oem format
fastboot -i 0x1949 continue
Now the amazon arrow was there. Repeated the last command chain, and I ended up in TWRP.
Hello,
My 3rd gen stock Fire HDX also stuck at "Fire is upgrading..." screen. This thread say there is no solution but looks like you found a way to get TWRP on it. Is this correct? If so, once you get TWRP, you can recover right?
I am on ubuntu14?
When I do a fastboot -i 0x1949 oem format, it just hangs at <waiting for any device>
How to get fastboot to see device, what mode do you boot your HDX to? Do I need to use a fastboot usb cable or will the stock HDX usb cable work?
When I run adb command it show the device D0FCA... unauthorized
Thx
Any clear solution on this problem ?
Stuck on "updating kindle".
Now first of all let me get started. I really will tip over PayPal for a beer for anyone who helps with that, because I've spent the whole day and can't get it to work.
Let me first of all explain my situation. I bought a Kindle 7 yesterday for the family business so that the staff can consult e-mails and access Google while being able to block most apps such as Facebook so they don't mess around (they already do it enough with their personnal phones ) and having read a bit about applications that would allow me to creates multiple users, I realised that I had to be rooted.
Now I had rooted my Galaxy S4 in the past and remembered it being an incredibly easy process so I figured, eh, might aswell give it a go, and that's when all the issues started.
I realised that this needs to be done using Bin4ry's method after installing the ADB drivers (hopefully I got all of this right). But here's where the first issue starts.
When I try to install the ADB drivers, I get the following error code :
So at first I was trying to restart my computer but came to the conclusion that it wasn't the issue. So I tried another method !
I tried installing the ADB directly from the Android SDK, using the link and such, which seemed to work well since I didn't have an error message and now the device was actually asking me to authorize for usage as ADB or whatever the message it says.
So I was optimistic and all, but then came the second problem... I tried running Bin4ry's program but now the issue was something else. When it tried running it, instead of saying device absent, it was now saying the the ADB was out of date (see below). After reading online, I was told thats its because the Android ADB and Bin4ry's one are conflicting, so some people suggested killing them in task manager, which I tried but also said they would come back automatically (which they also did). After that I found an ADBFIX little program, but had no clue where to find the Android ADB....
The reason I'm saying all that and making such a long post is to basically say that I've tried as far as my knowledge goes... I've checked the forums and everything, but most ''killing issues'' applied to HTC devices and not directly Amazon...
Please, I'd love help of any kind ...
Thanks..
Simon
s15.postimg(dot)org/ccwn8hbaz/ADB1.jpg
s14.postimg(dot)org/uf795dlz5/ADB2.png
s24.postimg(dot)org/y4ni1pf05/ADB3.jpg
I was told that since I had under 10 posts, I couldn't post any links, but had taken screenshot of my error messages.. Please replace the (dot) in the links above to hopefully help you understand my issues.
You may just want to use Towelroot and not mess with ADB at all. I've seen reports that it works on the newer hdx, so it might work on our kindles as well.
http://lifehacker.com/towelroot-roots-android-kitkat-devices-in-one-tap-no-p-1592226618
Just tried, unfortunately was told that this device isn't supported ...
What generation Kindle did you buy?
Korgot said:
Let me first of all explain my situation. I bought a Kindle 7 yesterday . . .
Click to expand...
Click to collapse
You know the newest Kindle (4th gen) isn't rootable yet. 2013 models (3rd gen) use Firerooter (KFSOWI modding community on Google+). This forum is for earlier models.
So I got a Kindle Fire HD 8.9 from a relative (who recently passed away…see why this is relevant later) and I immediately attempted to root and unlock it so I could put real Android on it. Big mistake for me.
For one, it was on the 8.5.1 software. For two, I probably should have researched a bit more, so yes, my fault here.
I rooted using the weird looking Chinese apk (can't remember the name atm), worked fine, no problems. Then I followed a guide on here (but I think it was for the 8.4.x firmware) using flashfire11.apk to flash the appropriate kfhd8 TWRP recovery and the freedom. However, once I used that tool and flashed, the Kindle only goes to the "kindle fire" logo and doens't do anything else.
If I enter the fastboot commands in Terminal (yes, I'm using a Mac, but I can switch to Windows if need be) and plug the device in when powered off, it does go to fastboot mode, but so far I have not been able to get anything (Terminal or CMD Prompt) to see my Kindle when I plug it in. Any suggestions on how to de-brick this thing? Major points to you if you can help.
EDIT: The fact that the original owner is no longer here is important because (1) I don't know the relative's email address/account they ordered the Kindle with, and (2) since I can't boot it I don't know the serial number, which means (3) I can't send it in to Amazon to get fixed/replaced.
Bump. Any ideas/tips? I managed to copy off a com.amazon.kindle folder which had what looked like books in them before the bricking happened. Not sure if there's a way to extract the user's email address from any of the files?
Stupidly enough, while I was downgrading to 5.2.1 for rooting the device, I got the device updated to 5.3.3.0 or something like it, once updated, the device did not boot at all, effectively bricking anything, recovery, fastboot, adb, anything.
It appears that the preloader thing is indeed trying to preload (d'oh) but as lots of posts dot mention, the aftv2-tools are unable to read/write from/to the mmc in any way. Handshaking does work since it prevents the device from continuing to uboot, I presume. Otherwise, with no handshake in place, the device keeps going through uboot and preloader for a couple of times until blocks.
Of course I presume its uboot since screen and everything is dead, just looking at the kernel dmesg once the kindle is plugged in.
It seems I'm screwed since the aftv people says so at AFTV News that as well, but, does anyone know if there is any other possible to recover/unbrick using any other approach or jtag?
marianXOS said:
Stupidly enough, while I was downgrading to 5.2.1 for rooting the device, I got the device updated to 5.3.3.0 or something like it, once updated, the device did not boot at all, effectively bricking anything, recovery, fastboot, adb, anything.
It appears that the preloader thing is indeed trying to preload (d'oh) but as lots of posts dot mention, the aftv2-tools are unable to read/write from/to the mmc in any way. Handshaking does work since it prevents the device from continuing to uboot, I presume. Otherwise, with no handshake in place, the device keeps going through uboot and preloader for a couple of times until blocks.
Of course I presume its uboot since screen and everything is dead, just looking at the kernel dmesg once the kindle is plugged in.
It seems I'm screwed since the aftv people says so at AFTV News that as well, but, does anyone know if there is any other possible to recover/unbrick using any other approach or jtag?
Click to expand...
Click to collapse
None that have been publicly acknowledged/confirmed.
My device is on the exactly same situation. =/
I'm hoping that on future we can have some way to fix this scenario. It seems like the only way out is using SP Flash Tool for reflashing the whole device.
However, I don't see we getting the Authentication file at any day. I have already kinda given up on my device.
matheusbonela said:
My device is on the exactly same situation. =/
I'm hoping that on future we can have some way to fix this scenario. It seems like the only way out is using SP Flash Tool for reflashing the whole device.
However, I don't see we getting the Authentication file at any day. I have already kinda given up on my device.
Click to expand...
Click to collapse
I done the same thing it bricked my tablet. It seems to me that the lesson I learned is that you can't downgrade your device. But how does one flash it using that tool. I do have it but I can't seem to find the correct files to do so.
Rbohannon89 said:
I done the same thing it bricked my tablet. It seems to me that the lesson I learned is that you can't downgrade your device. But how does one flash it using that tool. I do have it but I can't seem to find the correct files to do so.
Click to expand...
Click to collapse
You can't; need a scatter file which is not available for this device. Many have tried without success.
im also having this problem. handshake ok but no command response
what is solution
marianXOS said:
Stupidly enough, while I was downgrading to 5.2.1 for rooting the device, I got the device updated to 5.3.3.0 or something like it, once updated, the device did not boot at all, effectively bricking anything, recovery, fastboot, adb, anything.
It appears that the preloader thing is indeed trying to preload (d'oh) but as lots of posts dot mention, the aftv2-tools are unable to read/write from/to the mmc in any way. Handshaking does work since it prevents the device from continuing to uboot, I presume. Otherwise, with no handshake in place, the device keeps going through uboot and preloader for a couple of times until blocks.
Of course I presume its uboot since screen and everything is dead, just looking at the kernel dmesg once the kindle is plugged in.
It seems I'm screwed since the aftv people says so at AFTV News that as well, but, does anyone know if there is any other possible to recover/unbrick using any other approach or jtag?
Click to expand...
Click to collapse
Sai Nyan Linn said:
Amazon fire 5th generation is making by downgrade i
Result this black screan and dead ...
Pc driver manager into mtk port
I need sp flashtool or Solution
Please ... my all best friend ....
Click to expand...
Click to collapse
Please sir, do not make double posts into multiple forrums. It can get confussing.
Anyway, if your device is bricked from doing a downgrade, you may be in luck.
There is a thread here for unlocking the bootloader, and one of the steps to unlock the 5th gen fire 7 is to do just like you have. Brick by downgrade.
Go-to here.
https://forum.xda-developers.com/amazon-fire/development/unlock-fire-t3899860
Hello guys, I'll try to explain what happened giving just a few context that may help give me some right direction to recover the user data that were in the phone.
As this thread got longer than I expected, summarising:
Moto G XT1033 drained battery, got into bootloop, only fastboot was working, couldn't get into recovery mode ("boot up failed"). When I tried to replace battery, after power on it's now bricked (as "qhsusb_bulk" in PC). My main goal, save user data (whatsapp folder mainly), to flash and restore Android.
Whole situation detailed, what happened:
I have a Motorola Moto G 16GB Music Edition Dual SIM XT1033 (Music edition) 2014, sold in Brazil. It was working for all these years fine, avoided upgrading Android KitKat from 4.4 because it just worked fine. In past months I noticed the battery holding less and less charge, but as I intended to buy a new phone soon I didn't care.
Unfortunately, couple days ago I heard the sound of notification "low battery... powering off". Then I plugged the charger cable and waited some time, after that, I thought it would just boot up normally, it showed "M" loading screen, with the animation etc, but it went to black screen and loop to loading screen again and again.
I tried to hold power and volume down, it went to fastboot, and when I tried start "recovery mode" but it would just say "boot up failed".
I searched for threads and people who had issue like mine and in fact, I found someone who described exactly the same problem I had, user named @ravibhat here: https://forum.xda-developers.com/moto-g/help/moto-g-bootup-problem-recovery-mode-t3122492
While he didn't say he was able to fully flash his smartphone and get it back working, he said he was able to recover all his user data. I was really trying to follow his steps to at least, recover all user data, BUT, before that, my Moto G got hard bricked.
As I have another Moto G XT 1033, the exact same model as this one, but with a working battery, I thought it would be plausible to replace the battery so I could have more safety when fixing the phone, but it didn't work as that. Instead, after I disconnect and reconnect the battery, the Moto G is now hard bricked, as it doesn't boot up anymore, not even holding power + volume buttons, holding for 60s or 120s, none, nada. Rarely, the LED light blink once, nothing more. I connected to PC and it recognized as "qhsusb_bulk", after disconnecting and connecting the phone back to Windows 7, it automatically tried to install drivers and now it would just show "Qualcomm HS-USB QDLoader...." in device manager .
Now I have two issues, first, make it come back to state where I could open fastboot. Second, try to dump/save all user data, to then make a total flash/factory reset to see if I can get it working again.
After searching for hard brick and "qhsusb_bulk", I found this thread (https://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798) and this (https://forum.xda-developers.com/moto-g/general/guidy-to-unbrick-hard-bricked-moto-g-t3875035) that says it will recover from it, but it didn't mention IF IT WILL compromise or delete all user data. Will it?
I don't want to just go and try a bunch of (possible danger) commands and guides without having some experienced people giving advices on how to perform actions, or even if it's possible to "make some backup" of current situation, "copying whole partition", etc, before installing and flashing anything.
Device INFO:
Android version was 4.4. No Root. Bootloader is LOCKED. No customizations.
ADB Debugging state is unknown, probably it was just the default value.
What I want:
I want to get a copy of all my internal storage data, eg: WhatsApp folder, etc. Better if I could get whole storage image and just flash OS and boot loader to get back as it was...
Trying to flash it in any way that causes data loss would be my last option, but @ravibhat who had same issue few years ago couldn't even get it back working again.
What @ravibhat found out:
He thought bootloader UNLOCK would wipe all internal memory user data, but he did it and still could get all files using TWRP 2.8.x.x.
"To root the phone, I’ll have to UNLOCK the Bootloader."
"ADB can be used to backup using PUSH, PULL (may or may not require Android USB Debugging enabled)": he couldn't get it to work using adb push/pull.
Please, I would really appreciate any help from anybody, also from following users @ravibhat , @lost101 , @Teddy Lo , @Kamin4ri , @oversleeper , @jdawc7 , @sd_shadow , @SahilTech , @liveroy , @bouba148 , @bejunk , @Wolfcity, @skad00sh, @FabioSan.
After searching for hard brick and "qhsusb_bulk", I found this thread (https://forum.xda-developers.com/mot...oto-g-t2833798) and this (https://forum.xda-developers.com/mot...oto-g-t3875035) that says it will recover from it, but it didn't mention IF IT WILL compromise or delete all user data. Will it?
Click to expand...
Click to collapse
It should not delete the user data. I'm saying this out of logic though, I've never tested it.
Technically the Motorola qboot utility will ripristinate the bootloader only, without modifying any other area of the memory.
oversleeper said:
It should not delete the user data. I'm saying this out of logic though, I've never tested it.
Technically the Motorola qboot utility will ripristinate the bootloader only, without modifying any other area of the memory.
Click to expand...
Click to collapse
Thanks @oversleeper, I was a bit afraid because of the "blank-flash.bat" name.. but as I don't know of any other method of beginning this recovery other than unbricking using this qboot bat script, I will end up giving it a chance.
As I said before, Windows 7 auto installed the "Qualcomm HS-USB QLoader 9008" driver as soon as it recognized the "qhsusb_bulk". Do you think I should try to uninstall it and start from step 1 on this guide (https://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798) installing the "Riff BOX JTAG drivers + Driver Signature Enforcement Overrider"?
Yes, I suggest that you install the driver's as advised in that old thread. Also, you will need to use the right qboot utility, for the right model and version of the bootloader that you have or it won't work. Unfortunately I can't help with that, you will need to search the internet and may luck be with you.