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".
Hi guys, I am having an issue i cant seem to resolve on my razr i. apologies if this has already been covered in another thread (or 10, which is usually the way with these things because nobody reads the other threads) I have been through a load of other threads but cannot seem to resolve my issue so i started my own.
Right, I have switched from iphone to razr and am not stupid when it comes to jailbreaking etc so thought rooting the razr wouldnt be a problem. when trying to root it it failed and i am stuck at the fastboot menu, however, everything on the menu is disabled so i cant use it. i get the usual message:
fastboot reason: flash failure
fastboot max download size: 100mb
usb connected
if i try to use anything on the menu i get the following message:
fastboot menu disabled.
my phone is not unlocked and not rooted. i have barely done anything to it other than install a couple of free apps. i am unable to progress past this screen. the phone is GB and is on 4.0.4
any help you guys can give would be greatly appreciated. again, apologies if this has already been covered, none of the solutions i found were able to resolve my issue. as i said, i had no problems jailbreaking my old iphone, i am a bit of a n00b when it comes to droids...
AW: [Q] razr i problems - fastboot menu
Are you able to run fastboot commands ? Cause in that case you might be able To unlock bootloader and reflash the software .
Sent from my XT890 using xda premium
xX_Alex_Xx said:
Are you able to run fastboot commands ? Cause in that case you might be able To unlock bootloader and reflash the software .
Sent from my XT890 using xda premium
Click to expand...
Click to collapse
I am not able to do anything. if i scroll to any of the options on the menu as soon as i hit the volume up key it just returns a message advising the fastboot menu is disabled.
**edit
ah commands not menu options. not sure how i go about doing that. i am 100% new to droid...
ged flanders said:
Hi guys, I am having an issue i cant seem to resolve on my razr i. apologies if this has already been covered in another thread (or 10, which is usually the way with these things because nobody reads the other threads) I have been through a load of other threads but cannot seem to resolve my issue so i started my own.
Right, I have switched from iphone to razr and am not stupid when it comes to jailbreaking etc so thought rooting the razr wouldnt be a problem. when trying to root it it failed and i am stuck at the fastboot menu, however, everything on the menu is disabled so i cant use it. i get the usual message:
fastboot reason: flash failure
fastboot max download size: 100mb
usb connected
if i try to use anything on the menu i get the following message:
fastboot menu disabled.
my phone is not unlocked and not rooted. i have barely done anything to it other than install a couple of free apps. i am unable to progress past this screen. the phone is GB and is on 4.0.4
any help you guys can give would be greatly appreciated. again, apologies if this has already been covered, none of the solutions i found were able to resolve my issue. as i said, i had no problems jailbreaking my old iphone, i am a bit of a n00b when it comes to droids...
Click to expand...
Click to collapse
Had the same problem, I used the recommendation in this thread, 5th post and it worked, but afterwards need to re-download apps from PlayStore:
http://forum.xda-developers.com/showthread.php?p=36612151
Follow the instructions exactly - you need the drivers and RSD lite on Windows PC, then connect the phone via usb cable that came with it; and you'll need a full unzip program (cost) so you can move the unzipped files into RSD lite. Get the right flash file though - there's a list in the linked post if you don't want GB retail which I used. Important: this only works for ICS 4.0.4 and don't try to downgrade to an earlier version than what's currently on your phone e.g. v.39 to v.31, for example.
Good luck.
AW: [Q] razr i problems - fastboot menu
If the solution from mervluk does not work (It didn't work for me either) , you should try if you are able to use the fast boot commands .
To do that simply connect your phone to the PC. Then download fast boot , if you do not already have that. It is in the .zip from the RAZR I root thread.
The go to the downloaded folder. There hold shift and perform a right mouse click. Then choose" start a command prompt here "or something similar (don't know how the option is called in English).
Then type in
fastboot reboot
When the phone reboots you might be able to unlock your phone and flash the software.
BUT BE AWARE! YOU WILL LOSE YOUR WARRANTY!!
So you better try the other solution first. This should be your last option.
If you don't know how to unlock the bootloader look in the RAZR I forum or pn me .
Alex
Sent from my XT890 using xda premium
mervluk said:
Had the same problem, I used the recommendation in this thread, 5th post and it worked, but afterwards need to re-download apps from PlayStore:
http://forum.xda-developers.com/showthread.php?p=36612151
Follow the instructions exactly - you need the drivers and RSD lite on Windows PC, then connect the phone via usb cable that came with it; and you'll need a full unzip program (cost) so you can move the unzipped files into RSD lite. Get the right flash file though - there's a list in the linked post if you don't want GB retail which I used. Important: this only works for ICS 4.0.4 and don't try to downgrade to an earlier version than what's currently on your phone e.g. v.39 to v.31, for example.
Good luck.
Click to expand...
Click to collapse
thanks buddy. i will give this a whirl and let you know how i get on. fingers crossed!
mervluk - your advice worked a treat. i got it working again. thanks !
now i am working again, what cool tricks do people advise. is it worth rooting it ? what can i do once it is rooted? am i able to network unlock it myself ?
ged flanders said:
mervluk - your advice worked a treat. i got it working again. thanks !
now i am working again, what cool tricks do people advise. is it worth rooting it ? what can i do once it is rooted? am i able to network unlock it myself ?
Click to expand...
Click to collapse
Glad about that. This phone can be a bit of a so-and-so. ics is being updated ota to Jelly Bean 4.1.2, which I've avoided so far to keep fm (although not activated on the supplied software). I did succeed with unlocking the bootloader (loose warranty - important) following the whole complicated procedure on Moto's website - but couldn't myself use the shortcuts on here. (Then had to set up again and re-download everything from the PlayStore). It required the Moto-supplied key. I then rooted, though I think the JB ota download unroots again? You can't use RSD lite with JB.
With JB the procedures are different, and a modified JB European (not for use with GB) firmware is now available on another thread which is impressing some posters. But I think just be a bit cautious as there does not appear to be any fix for the "service code corrupt" bootloader error yet. Looks like the options are very restricted whilst no-one understand the interaction between Google Android and the intel atom chipset.
I have a network unlock key from one of the commercial suppliers (cellunlocker.net), but haven't needed to try and use it yet!
My phone connects fine with adb. I tooted with towelroot, i have the D415 (see screenshot) i have run the commands on a pc several time with no errors. I tried it with my terminal emulator severaIm times and it says "decixe not found) HAHHA its just funny to me. I want to unlock this bootloader i even tried a factory cable (for kindle and only once) no dice. I get download mode and thats it. I know I must be doing somethimg wrong but damned if i can figure what. Pc is windows 764 bit. I like to have a custom rexovery and i have heard i can put onw like this (locked) but i did that to another device and to make it short it sits in a drawer being brand new and broken. Apparently those instructioms are correct because there are many success stories. I followed the directions like this is my last phone for a whi
PHP:
le. Can someone help me out please? Thank you
Holy....... 64bit! Im not futureman!!!!
Do you need to unlock the bootloader on d415? I taught you could flash a custom recovery without unlocking... (I don't own one!)
I ave twrp on it. So far i havent been able to do anything but a nandroid and restore with it. I am now at a pc so i can dl from devhost. We shall see, (i doubt it,)
whodisname said:
I ave twrp on it. So far i havent been able to do anything but a nandroid and restore with it. I am now at a pc so i can dl from devhost. We shall see, (i doubt it,)
Click to expand...
Click to collapse
The bootloader on the LG-D415 is unlocked out of the box.
Wow, and all these instructions!! I figured after i put twrp on it it was cool but it didnt flash the rom, omly had one cuz dev host doesnt dl on cell phones so well,
whodisname said:
My phone connects fine with adb. I tooted with towelroot, i have the D415 (see screenshot) i have run the commands on a pc several time with no errors. I tried it with my terminal emulator severaIm times and it says "decixe not found) HAHHA its just funny to me. I want to unlock this bootloader i even tried a factory cable (for kindle and only once) no dice. I get download mode and thats it. I know I must be doing somethimg wrong but damned if i can figure what. Pc is windows 764 bit. I like to have a custom rexovery and i have heard i can put onw like this (locked) but i did that to another device and to make it short it sits in a drawer being brand new and broken. Apparently those instructioms are correct because there are many success stories. I followed the directions like this is my last phone for a while. Can someone help me out please? Thank you
Click to expand...
Click to collapse
For starters, you need the fastboot executable for Windows to unlock the device, not ADB. The minimal ADB version, also applies to fastboot, is 1.0.31. Secondly, you must enable fastboot mode on the device beforehand. Thirdly, unless LG has changed things in the last month or so, the bootloader on the LG-D415 is unlocked.
To enable fastboot mode, see http://forum.xda-developers.com/lg-l90/general/guide-fastboot-l90-d415-t2827825
To unlock the bootloader, see http://forum.xda-developers.com/lg-l90/general/guide-unlock-bootloader-t-mobile-l90-t2836457. Shouldn't be necessary tho . Won't hurt anything to go thru the process however.
Thank you, i have fastboot and adb (fixed a bricked kindle last week!!) I wasnt sure about the bootloader and iwasnt gunna be without a recovery like i was with my lg lucud!!!
And excuse my unintelligible post above. New size screen?
Hello.
My Nexus 6 is out of warranty, so I'm doing my best to get it working myself because I can't get it replaced for free.
So, several months ago, my Nexus 6 (running Android 6.0.1 MOB30O) restarted on its own and showed a "Device is corrupt" message before booting (information at g.co/ABH; red error). I was concerned about the security of my device, so I performed a factory reset. Upon trying to set the phone up again, I found that after connecting to Wi-Fi, the phone would loop indefinitely while periodically saying that Google Play Services has crashed. I once tried leaving it overnight while it was "Checking connection" or whatever, and it still did not move to the next phase of setup. I have tried this on several different networks, and when I intentionally use a wrong password, the phone doesn't connect. So, I have no reason to believe the Wi-Fi connection is the problem. I have tried performing a factory reset from Android Recovery dozens of times, and it still doesn't work. So, I'm effectively limited to the boot menu to interact with my phone (so, I can't access Developer Options because I can't set up my phone). Also, most of the times I boot up my phone, I still get that red error during boot.
So, I've been trying to reflash stock Android. I tried using Nexus Root Toolkit to do that several times, and it never works (I get to a part in the process where it says to set up the phone and enable Developer Options, but I still can't set up the phone). I then decided I would try to do it myself since that tool wasn't fixing the problem. I am able to get ADB connected using the "Apply update from ADB" option within Android Recovery, but whenever I try to sideload one of the Shamu factory images, I get a C++ (I think) error:
Code:
loading: 'C:\Users\dpowell\Downloads\shamu-mob30o.zip'...
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
I just updated all the ADB-related stuff from within Android Studio, so it all should be up-to-date.
So, I don't know what to try next. I've used Nexus Root Toolkit to root my Nexus 7 successfully, but I've never tried to modify my Nexus 6 before it stopped working. Regardless of what images I try to put onto the Nexus 6, it always shows MOB30O as the current image in the bootload menu.
Any thoughts or suggestions? I really would like to get this device working again, and Motorola would charge me $170 to replace it because it's not under warranty anymore.
Thank you for your help.
dpowell11 said:
Hello.
My Nexus 6 is out of warranty, so I'm doing my best to get it working myself because I can't get it replaced for free.
So, several months ago, my Nexus 6 (running Android 6.0.1 MOB30O) restarted on its own and showed a "Device is corrupt" message before booting (information at g.co/ABH; red error). I was concerned about the security of my device, so I performed a factory reset. Upon trying to set the phone up again, I found that after connecting to Wi-Fi, the phone would loop indefinitely while periodically saying that Google Play Services has crashed. I once tried leaving it overnight while it was "Checking connection" or whatever, and it still did not move to the next phase of setup. I have tried this on several different networks, and when I intentionally use a wrong password, the phone doesn't connect. So, I have no reason to believe the Wi-Fi connection is the problem. I have tried performing a factory reset from Android Recovery dozens of times, and it still doesn't work. So, I'm effectively limited to the boot menu to interact with my phone (so, I can't access Developer Options because I can't set up my phone). Also, most of the times I boot up my phone, I still get that red error during boot.
So, I've been trying to reflash stock Android. I tried using Nexus Root Toolkit to do that several times, and it never works (I get to a part in the process where it says to set up the phone and enable Developer Options, but I still can't set up the phone). I then decided I would try to do it myself since that tool wasn't fixing the problem. I am able to get ADB connected using the "Apply update from ADB" option within Android Recovery, but whenever I try to sideload one of the Shamu factory images, I get a C++ (I think) error:
I just updated all the ADB-related stuff from within Android Studio, so it all should be up-to-date.
So, I don't know what to try next. I've used Nexus Root Toolkit to root my Nexus 7 successfully, but I've never tried to modify my Nexus 6 before it stopped working. Regardless of what images I try to put onto the Nexus 6, it always shows MOB30O as the current image in the bootload menu.
Any thoughts or suggestions? I really would like to get this device working again, and Motorola would charge me $170 to replace it because it's not under warranty anymore.
Thank you for your help.
Click to expand...
Click to collapse
Hello,
The error you get from adb is coming from a problem with latest ADB Rev.25.0.4
Check this: https://issuetracker.google.com/issues/37139736
In Android studio are you able to revert to a previous version, no?
Rev.25.0.3 should work...
I assume your bootloader is locked?!
Good luck...
5.1 said:
Hello,
The error you get from adb is coming from a problem with latest ADB Rev.25.0.4
Check this: https://issuetracker.google.com/issues/37139736
In Android studio are you able to revert to a previous version, no?
Rev.25.0.3 should work...
I assume your bootloader is locked?!
Good luck...
Click to expand...
Click to collapse
Yes, my bootloader is locked.
Thank you, that fixed the ADB problem. I just saw that they actually have a Rev.25.0.5 now, so I am using that.
I tried sideloading first one of the Android 7 images, and that didn't work. So, I tried MOB30O again, and that also didn't work. Here's the error I'm getting:
Code:
E:footer is wrong
E:signature verification failed
Installation aborted.
The Shamu files I was trying to flash are the ones found at https://developers.google.com/android/images#shamu. Is this not what I'm supported to be using?
I don't know how relevant this is, but again, I'm using the "Apply update from ADB" option in Android Recovery, and all I did from my command line is "adb sideload [file]".
Thank you.
dpowell11 said:
Yes, my bootloader is locked.
Thank you, that fixed the ADB problem. I just saw that they actually have a Rev.25.0.5 now, so I am using that.
I tried sideloading first one of the Android 7 images, and that didn't work. So, I tried MOB30O again, and that also didn't work. Here's the error I'm getting:
The Shamu files I was trying to flash are the ones found at https://developers.google.com/android/images#shamu. Is this not what I'm supported to be using?
I don't know how relevant this is, but again, I'm using the "Apply update from ADB" option in Android Recovery, and all I did from my command line is "adb sideload [file]".
Thank you.
Click to expand...
Click to collapse
Hey,
WTF
You can't sideload a factory image
Download a proper OTA here: https://developers.google.com/android/ota#shamu
And try again.
Good luck...
5.1 said:
Hey,
WTF
You can't sideload a factory image
Download a proper OTA here: https://developers.google.com/android/ota#shamu
And try again.
Good luck...
Click to expand...
Click to collapse
Yeah, I understand about 40% of what I'm doing. Thanks for helping.
So, I sideloaded N6F26Y, which is 7.1.1. Here is the debug info I got:
Code:
Installing update...
Target: google/shamu/shamu:7.1.1/N6F26Y/3821691:user/release-keys
Patching system image unconditionally...
E:unknown command [log]
E:unknown command [log]
Writing bootloader...
Writing radio...
script succeeded: result was [1.000000]
Install from ADB complete.
So, it looks to me like that worked, but at the top of my screen, it still says 6.0.1/MOB30O. Also, it always makes me slightly nervous to see error messages. Do I need to reboot to bootloader in order for changes to take effect? Does it look like anything went wrong?
I know that manually messing with the operating system is potentially risky, so I didn't want to continue from here without knowing if there's anything else I needed to do.
Thank you so much for your help.
dpowell11 said:
Yeah, I understand about 40% of what I'm doing. Thanks for helping.
So, I sideloaded N6F26Y, which is 7.1.1. Here is the debug info I got:
So, it looks to me like that worked, but at the top of my screen, it still says 6.0.1/MOB30O. Also, it always makes me slightly nervous to see error messages. Do I need to reboot to bootloader in order for changes to take effect? Does it look like anything went wrong?
I know that manually messing with the operating system is potentially risky, so I didn't want to continue from here without knowing if there's anything else I needed to do.
Thank you so much for your help.
Click to expand...
Click to collapse
Hey,
You know everyone has to start somewhere. 40% is not that bad. :good:
Factory reset once again, just in case. And reboot.
Should be good now (hopefully). Let me know...
Cheers...
5.1 said:
Hey,
You know everyone has to start somewhere. 40% is not that bad. :good:
Factory reset once again, just in case. And reboot.
Should be good now (hopefully). Let me know...
Cheers...
Click to expand...
Click to collapse
Dude. It works.
Man, this phone had been out of commission for months. I am so happy to have it working again.
Thank you very much for your help. I really appreciate it a bunch.
dpowell11 said:
Dude. It works.
Man, this phone had been out of commission for months. I am so happy to have it working again.
Thank you very much for your help. I really appreciate it a bunch.
Click to expand...
Click to collapse
Hey,
Great! I'm glad for you...
Keep reading on this site. There's plenty of usefully threads, infos, etc...
Enjoy your phone...
Cheers...
Or as bricked as these Qualcomm devices CAN be?
Hey all,
The TL;DR is basically where the list starts
I was running Blu's TWRP v45, the latest PureFusion, Blu's latest Custom kernel, had OB15 firmware underneath. I had been SO USED to simply downloading the newest firmware from kamilmirza's AFH page and just flashing it + it being totally fine that I did it without thinking for OB16. I wasn't too worried because about a week ago I had flashed the unofficial Oreo Lineage and it worked just fine! Plus, I just assumed if it died I could just restore a backup or re-flash the older OB. But as soon as I flashed the new firmware/modem by itself this time on an otherwise perfectly running device, I only saw the OnePlus splash screen. No booting, no access to recovery, no NOTHIN.
I tried flashing the beta TWRP version afterward via fastboot but no dice. Also tried temporary booting via fastboot to it, flashing Blu's again, booting to that. Everything the same result. Splash screen & nothing more. I then went to the extent of trying to format all the partitions and flash a boot.img or do a "-w update" or "flashall" command via fastboot. Because everything out in the universe is a recovery-flashable-zip, it seems like there's no way I can flash the necessary OTA stuff to bring it back to life!
My only remaining idea is getting this damn unbrick tool to work (duhh). I can see the Qualcomm HS-USB QDLoader 9008 in device manager after doing the Vol Up (only) and plugging the cable in. BUT the MSMDownloadTool just cannot see the device. Not in bootloader, not in the weird Vol-Up/cable state. [This is with Qualcomm drivers QUD.WIN.1.1 Installer-10037.3 Setup.exe, the official OnePlus drivers, ADB & Fastboot installed.]
Sorry for long explanation. In the end, what I'm left with is:
Blank formatted partitions (I hope... I'm not even positive they wound up formatted from the fastboot commands)
Fastboot is detected, but no ADB devices are found
Can get to bootloader, but nothing else
No recovery access - Flashing beta akhilnarang Oreo recovery does nothing. Flashing stock recovery does nothing. Flashing Blu_Spark recovery does nothing. (The fastboot commands succeed though each time somehow)
So far the only suggestion I've received is trying the MSMDownloadTool/unbrick process on another computer.
Does anyone have ANY ideas? From my experience, it seems like what might help me would be if a folder with the specific partition images existed for the OTAs, like how Google offers. (boot.img, recovery.img, user-data.img, system and so on). Am I wrong in thinking that? OnePlus has told me this simply does not exist and cannot give me anything like that (don't know why, when they already offer all the OTA flashables...)
PS - OnePlus support just absolutely refuses to even let me communicate to a "level 2" representative to ask a couple of the more technical questions about it. I can't understand why. They are insisting I start an RMA and send it for repair. They even initially scheduled a time for me to talk to higher level rep and then thought up a reason to cancel it via email an hour or so later...
Edit: Just in case the thread gets large and people don't read further posts, this is using:
Windows 10 Pro 64-bit
Test mode for the driver signing is enabled. Have the watermark bottom right of desktop
It's with the stock DASH cable
Tried multiple ports
Unfortunately it just doesn't show up in MSM at all, even with hitting 'enumerate' button multiple times
Tried starting the tool BEFORE the device is plugged in, as well as after
This is what Device Manager shows (attached) but just nothing in MSM all the way up & down
HOW IT GOT SOLVED:
At the end of the day, I had to fight and convince OnePlus support to grant me a remote session with Level 2 Support.
(Attached final image) These two password protected RAR files had almost identical tools as the Unbrick tutorial on XDA.
The major difference was that MSMDownloadTool was version 3.0.8 ***does anyone have this version??*** I can't get into these RARs. The 3.0 tool circulating did not work for me. We might need the newer version as time goes on?? Otherwise, the process was identical.
Unfortunately, the image they used was for 7.1.1. I had to unlock the bootloader and after doing that and getting OB15 & the RR build I wanted, etc, I then realized my phone was force-encrypted as well.
The only toolkit that worked for force decrypting once everything else worked was:
OnePlus_3_3T_5_64bit_TOOLKIT_by_Neisor
Finally, something like 3 clean flashes later, we Gucci.
Thanks for the attempted help to those that did! Hopefully this can help someone else.
Which Windows do you have? Have you tried MSMtool in safe mode? Or disabling Driver Signature Verification (any Windows after XP). I have got my phone so messed up that it was showing many lines with red "failed" text nearly on everything. No OS, no recovery, no boot, I think even modem was failed. This screen but I had way more fails https://forums.oneplus.net/attachments/win_20160928_21_31_49_pro-jpg.459494/
As long as you can turn your phone off and on, it's doable. But you need to do that USB plugging + volume up thing while phone is totally off (you can hear Windows making bling when you connect it while pressing volume up, but phone itself stays screen off). And there shouldn't be anything on the screen before/while MSMtool do its job.
You can try different USB ports too.
Eremitus said:
Which Windows do you have? Have you tried MSMtool in safe mode? Or disabling Driver Signature Verification (any Windows after XP). I have got my phone so messed up that it was showing many lines with red "failed" text nearly on everything. No OS, no recovery, no boot, I think even modem was failed. This screen but I had way more fails https://forums.oneplus.net/attachments/win_20160928_21_31_49_pro-jpg.459494/
Click to expand...
Click to collapse
Hahaha yes...... That's why I made this post though! It SEEMS like it should be possible to recover from this since fastboot commands + bootloader work! It SEEMED like it would be easy to recover from if anything went wrong... But, here I am.
Oh yeah forgot to mention ~
Windows 10 Pro 64-bit
Test mode for the driver signing is enabled. That part of the process went totally fine with BIOS and installing stuff, etc.
Also, shot in the dark but might @Funk Wizard have any ideas? Sorry to call out for this
Hopefully someone knows better how to solve this. For me the MSMtool part is always the hardest part too, usually it finds the phone, but throws some strange "Sahara communication failed" error. I noticed that even different USB cable can be a problem, but since your Windows finds "Qualcomm HS-USB QDLoader 9008" I guess that's not the case. Does it say something after that "Qualcomm 9008" -thing? For me it shows (COM3 or COM4 depending on which port it's in).
btw, I messed up my phone in nearly similar case, flashing wrong firmware when using leaked H2OS ROM.
Eremitus said:
Hopefully someone knows better how to solve this. For me the MSMtool part is always the hardest part too, usually it finds the phone, but throws some strange "Sahara communication failed" error. I noticed that even different USB cable can be a problem, but since your Windows finds "Qualcomm HS-USB QDLoader 9008" I guess that's not the case. Does it say something after that "Qualcomm 9008" -thing? For me it shows (COM3 or COM4 depending on which port it's in).
Click to expand...
Click to collapse
Yeah sorry again for not being more clear lol
It's with the stock DASH cable
Tried multiple ports (but no USB 2 ports hmm)
Unfortunately it just doesn't show up in MSM at all, even with hitting 'enumerate' button multiple times.
Also tried starting the tool BEFORE device plugged in as well as after
This is what Device Manager shows (attached) but just nothing in MSM all the way up & down
If I find a solution I'll definitely put it in OP for others
purplepenguin said:
Yeah sorry again for not being more clear lol
It's with the stock DASH cable
Tried multiple ports (but no USB 2 ports hmm)
Unfortunately it just doesn't show up in MSM at all, even with hitting 'enumerate' button multiple times.
Also tried starting the tool BEFORE device plugged in as well as after
This is what Device Manager shows (attached) but just nothing in MSM all the way up & down
If I find a solution I'll definitely put it in OP for others
Click to expand...
Click to collapse
Hmm, ok.
Stock dash cable works, so that part is ok. Also usb3.0 ports should work too, atleast for me. So everything else seems to be ok except the MSMtool itself
Try different cable, bin there done that!!
purplepenguin said:
Yeah sorry again for not being more clear lol
It's with the stock DASH cable
Tried multiple ports (but no USB 2 ports hmm)
Unfortunately it just doesn't show up in MSM at all, even with hitting 'enumerate' button multiple times.
Also tried starting the tool BEFORE device plugged in as well as after
This is what Device Manager shows (attached) but just nothing in MSM all the way up & down
If I find a solution I'll definitely put it in OP for others
Click to expand...
Click to collapse
I hope you find a solution, since my experience sounds similar to yours Ill share it and maybe you can find something to help out.
I was exactly where you are for about 3 hours last night.
Boot would always get stuck at the splash screen. Could boot into Fastboot, tried using the Skipsoft tool to fastboot flash a stock image but it kept failing.
As far as the Unbrick Tutorial goes, I know the first thing I kept messing up was thinking I needed to press the power button while holding the volume up and connecting to the PC
Also when I tried to manually update the driver on "Qualcomm 9088" it said it was already up to date.
Then I just ran the MSMTool it flashed 6.0.1 back on my phone and I was back in business.
Im sure this is the guide you followed: Here
I found another on the oneplus forums that is essentially the same but goes into a little more detail in the steps: Here
Since I was back completely Stock including Recovery I went ahead and sideloaded OB16 to get the firmware and modem then went about rooting, unencrypting etc...
Lost a few days worth of files but I'm back running LunuxOS Oreo right now.
Good luck I know how you feel. :good:
I've got it revived! I'll update OP. Sadly, it required OnePlus's intervention.
Hi. Trying to do brute force to get the passowrd here, don't you know how many characters that was? It will take days in my machine to search from 3 to 9 characters...
I think it is impossible to you to know, but if you know if they used only letters or something like that, it would be very useful
guilhermeferrari said:
Hi. Trying to do brute force to get the passowrd here, don't you know how many characters that was? It will take days in my machine to search from 3 to 9 characters...
I think it is impossible to you to know, but if you know if they used only letters or something like that, it would be very useful
Click to expand...
Click to collapse
Sorry man. The OnePlus guy was ready an hour early before our appointment time. So I didn't have time to set up screen recording or anything
if I had to narrow it down more itd only be like 4-9 chars lol I know that's not much help... Definitely let me know if you get it open though please! It would probably help a lot of us!
purplepenguin said:
Sorry man. The OnePlus guy was ready an hour early before our appointment time. So I didn't have time to set up screen recording or anything
if I had to narrow it down more itd only be like 4-9 chars lol I know that's not much help... Definitely let me know if you get it open though please! It would probably help a lot of us!
Click to expand...
Click to collapse
Well, I know the password. It's 10 character long. 7+3(7english small latter with 3 Numbers).
L2 Driver password is very very very very very loooooooong. can't even count accurately.
namefaisal said:
Well, I know the password. It's 10 character long. 7+3(7english small latter with 3 Numbers).
L2 Driver password is very very very very very loooooooong. can't even count accurately.
Click to expand...
Click to collapse
Jeez so wait you got it open or not?? Confused lol
Got the newer download tool ??
Yeah, I got it open
purplepenguin said:
Jeez so wait you got it open or not?? Confused lol
Got the newer download tool ??
Click to expand...
Click to collapse
Yeah it's the new 3.08 msmdownloadtool. OnePlus3T_28_A.57_171012.zip
I know the password and I won't share that but I will upload an UNLOCKED zip on google drive tonight. L2 Drivers too.
New Files without Password
namefaisal said:
Yeah it's the new 3.08 msmdownloadtool. OnePlus3T_28_A.57_171012.zip
I know the password and I won't share that but I will upload an UNLOCKED zip on google drive tonight. L2 Drivers too.
Click to expand...
Click to collapse
Latest 3.08 msmdownloadtool re-archived without password from OnePlus3T_28_A.57_171012.zip
https://drive.google.com/file/d/1kp2SBmhAByydol97o0yVlurVue9Ow8Aq/view?usp=sharing
And the L2+ driver.zip re-archived without password
https://drive.google.com/file/d/1JL_sRg86CczUeZ2cfw8GY6rxc43myif8/view?usp=sharing
@Sam Nakamura
namefaisal said:
Latest 3.08 msmdownloadtool re-archived without password from OnePlus3T_28_A.57_171012.zip
https://drive.google.com/file/d/1kp2SBmhAByydol97o0yVlurVue9Ow8Aq/view?usp=sharing
And the L2+ driver.zip re-archived without password
https://drive.google.com/file/d/1JL_sRg86CczUeZ2cfw8GY6rxc43myif8/view?usp=sharing
Click to expand...
Click to collapse
This totally worked for me. Yes it put me back on 7.1.1 but I have been having issues trying to flash Oxygen ROMS and getting them to take. Phone is back to bone stock which I wanted for now and is working great. Thank you for sharing,
cdorrell12000 said:
This totally worked for me. Yes it put me back on 7.1.1 but I have been having issues trying to flash Oxygen ROMS and getting them to take. Phone is back to bone stock which I wanted for now and is working great. Thank you for sharing,
Click to expand...
Click to collapse
You are most welcome.
Sadly everyone gets unbricked with these files but My device didn't. I have to send the device to the service center now. It seems my case is a hardware issue. Tough luck
namefaisal said:
Latest 3.08 msmdownloadtool re-archived without password from OnePlus3T_28_A.57_171012.zip
https://drive.google.com/file/d/1kp2SBmhAByydol97o0yVlurVue9Ow8Aq/view?usp=sharing
And the L2+ driver.zip re-archived without password
https://drive.google.com/file/d/1JL_sRg86CczUeZ2cfw8GY6rxc43myif8/view?usp=sharing
Click to expand...
Click to collapse
thanks a lot saved my day !!
purplepenguin said:
@Sam Nakamura
Click to expand...
Click to collapse
Sorry, I just saw your mentioning somehow I missed it, happy you got your phone back already, unfortunately not independent for big OP, did you guys already share this new 3.08 MSM-download-tool to the well established threads or did you I missed this too? This information and according files should be shared with the community and easy to find for those poor souls who unintentionally killed their beloved device...
---------
Edit: further sharing isn't necessarily needed, you did already a pretty good job by naming the thread and describing the situation thoroughly, only suggestion could be to link the updated MSM-download-tool download to the first post with some hint, just an idea though...
Cheers
Sent from my OnePlus 3T using XDA Labs