Related
Hi I attempted to root my phone, got SU but was having problems flashing any roms, using any apps that required /root or accessing recovery. Figured something might not have worked and tried to unroot and start again. All steps were followed via http://forums.androidcentral.com/ve...-root-unroot-unlock-your-vz-galaxy-nexus.html
I'm stuck in the Google bootscreen with my only other option being bootloader, it still says Locked State - Unlocked. But my computer can't see my phone, Odin doesn't work and I still don't have a definitive method of restoring my phone via a MAC.
This ISN'T Resolved. I get errors when attempting to fastboot the stock image
~/Desktop/adb-fastboot/adb reboot bootloader
brings about the following error
"error: device not found"
I was already in bootloader and tried:
~/Desktop/adb-fastboot/fastboot flash boot ~/Desktop/adb-fastboot/boot.img
I get:
error: cannot load '/Users/grnmons/Desktop/adb-fastboot/boot.img'
If anybody has any ideas please let me know, I really don't know what to do at this point.
grnmons said:
Hi I attempted to root my phone, got SU but was having problems flashing any roms, using any apps that required /root or accessing recovery. Figured something might not have worked and tried to unroot and start again. All steps were followed via http://forums.androidcentral.com/ve...-root-unroot-unlock-your-vz-galaxy-nexus.html
I'm stuck in the Google bootscreen with my only other option being bootloader, it still says Locked State - Unlocked. But my computer can't see my phone, Odin doesn't work and I still don't have a definitive method of restoring my phone via a MAC.
If anybody has any ideas please let me know, I really don't know what to do at this point. Plan B is to use a PC which I can only access later in the week. If you know someone, or have a link I would really appreciate it. Also ask me anything if it can help make this clearer.
Thanks
Click to expand...
Click to collapse
Okay your bootloader is unlocked which is good, but your MAC doesn't see your phone in bootloader mode?
grnmons said:
Plan B is to use a PC which I can only access later in the week.
Click to expand...
Click to collapse
Can you bootcamp or use a virtual machine?
grnmons said:
Hi I attempted to root my phone, got SU but was having problems flashing any roms, using any apps that required /root or accessing recovery. Figured something might not have worked and tried to unroot and start again. All steps were followed via http://forums.androidcentral.com/ve...-root-unroot-unlock-your-vz-galaxy-nexus.html
I'm stuck in the Google bootscreen with my only other option being bootloader, it still says Locked State - Unlocked. But my computer can't see my phone, Odin doesn't work and I still don't have a definitive method of restoring my phone via a MAC.
If anybody has any ideas please let me know, I really don't know what to do at this point. Plan B is to use a PC which I can only access later in the week. If you know someone, or have a link I would really appreciate it. Also ask me anything if it can help make this clearer.
Thanks
Click to expand...
Click to collapse
Wrong section..but
I would def use a PC and use Odin ! Make your life easier...it takes like 3-5 Mins..takes it to stock!
Sent from my Galaxy Nexus using xda premium
All you have to do is fastboot flash those stock images of 4.0.2 google gave us. There's not even any need for Odin. You can do this right on your Mac.
Sent from my Galaxy Nexus using Tapatalk
Please uninstall and reinstall your phones drivers. Your just soft bricked is all. Once your computer sees the device you should be good.
sent from the Almighty One himself....
borgey said:
All you have to do is fastboot flash those stock images of 4.0.2 google gave us. There's not even any need for Odin. You can do this right on your Mac.
Click to expand...
Click to collapse
I can't seem to figure out how to do that. Seems like that's what got me here in the first place, the mac version might be missing files I'm missing the steps to actually do that.
Can't find any forum/site/guide that tells me how to do that. Does anybody have this?
grnmons said:
I can't seem to figure out how to do that. Seems like that's what got me here in the first place, the mac version might be missing files I'm missing the steps to actually do that.
Can't find any forum/site/guide that tells me how to do that. Does anybody have this?
Click to expand...
Click to collapse
fastboot flash (google on how to use these)
you do them when you're in bootloader mode. you need to have a ADB/Fastboot environment set up (look at root guides and do step one of it..... verifying the part of getting the environment, ignore drivers)
stock images are here: http://code.google.com/android/nexus/images.html
zephiK said:
fastboot flash (google on how to use these)
you do them when you're in bootloader mode. you need to have a ADB/Fastboot environment set up (look at root guides and do step one of it..... verifying the part of getting the environment, ignore drivers)
stock images are here: http://code.google.com/android/nexus/images.html
Click to expand...
Click to collapse
Thanks. Can you confirm that these are the steps?
1) Download the latest stock image( i will leave finding that image to you since this post can become outdated)
2) Unzip the files, and place the images into the adb-fastboot folder you created on your desktop above.
3) Open a terminal and use the following commands:
Code:
~/Desktop/adb-fastboot/adb reboot bootloader
4) Wait for bootloader to reboot on phone.
5) Then, in terminal use the following commands:
~/Desktop/adb-fastboot/fastboot flash boot ~/Desktop/adb-fastboot/boot.img
~/Desktop/adb-fastboot/fastboot flash system ~/Desktop/adb-fastboot/system.img
~/Desktop/adb-fastboot/fastboot flash recovery ~/Desktop/adb-fastboot/recovery.img
~/Desktop/adb-fastboot/fastboot flash userdata ~/Desktop/adb-fastboot/userdata.img
~/Desktop/adb-fastboot/fastboot erase cache
~/Desktop/adb-fastboot/fastboot oem lock
6) Reboot to System, and you should be returned to Stock and Unrooted
~/Desktop/adb-fastboot/adb reboot bootloader
brings about the following error
"error: device not found"
I was already in bootloader and tried:
~/Desktop/adb-fastboot/fastboot flash boot ~/Desktop/adb-fastboot/boot.img
I get:
error: cannot load '/Users/grnmons/Desktop/adb-fastboot/boot.img'
anybody have any other suggestions to this? or a follow up?
It should be easy to fix. You do not seem to have the correct driver installed.
Sent from my Galaxy Nexus using xda premium
Understood, I think I definitely did a few things wrong here. But my problem requires some kind of steps to solve. I don't mean to sound lazy but I've been running around the forums for awhile and I'm in way over my head, I was hoping someone could just list a few steps, links, SOMETHING. I'm looking for solvency here.
grnmons said:
Understood, I think I definitely did a few things wrong here. But my problem requires some kind of steps to solve. I don't mean to sound lazy but I've been running around the forums for awhile and I'm in way over my head, I was hoping someone could just list a few steps, links, SOMETHING. I'm looking for solvency here.
Click to expand...
Click to collapse
reinstall the android sdk from here that will get your drivers in order so your computer can see your phone
then fastboot flash recovery
then manually flash su (attached)
ogdobber said:
reinstall the android sdk from here that will get your drivers in order so your computer can see your phone
then fastboot flash recovery
then manually flash su (attached)
Click to expand...
Click to collapse
Thanks muchly, I feel like I'm getting closer but could you elaborate on the manual flash su step? My **** is all over the place now, my desktop is littered with files, should I be in recovery for this or still fastboot? and what is the command if you have?
grnmons said:
Thanks muchly, I feel like I'm getting closer but could you elaborate on the manual flash su step? My **** is all over the place now, my desktop is littered with files, should I be in recovery for this or still fastboot? and what is the command if you have?
Click to expand...
Click to collapse
download the gnex-su.zip and put in in the root of your sd card. then in recovery select "-install zip from sdcard" then "-choose zip from sdcard" then select the gnex-su.zip. this will give you root and install the superuser app
not to get ahead (previous post), but after your computer recognizes the phone you need to flash clockwork recovery
you need to open a terminal in the platform-tools folder of the sdk (also put the recovery.img there) and then
Code:
fastboot flash recovery name-of-recovery.img
Thanks for your help ogdobber, I'm incredibly frustrated and you must be too trying to help me, but I must have done something wrong as after I flash recovery, i still cannot access it - it continues to hang out in the Google screen.
Let me go through my steps with you and you tell me what I might have done wrong. So with my bricked phone, 1. I clicked your link and updated my SDK.
There's no indication that I did anything right here, it just shows that everything is installed and that's all I think I need here.
2. Opened up terminal fastboot flash boot (in this case) bootloader-toro-primekk15.img DONE!
3. Fastboot flash recovery (in this case) recovery-clockwork-5.0.2.0-crespo.img
DONE!
Then... nothing. Recovery doesn't load for me. Just get a boot loop. Anything I might have done wrong prior or inbetween these steps? Also, besides flashing and running commands off terminal - i assume this is considered computer recognizes my phone. Could the problem be there?
Just got your last post, I'm unfamiliar with SDK but I've since put the recovery file in there, not sure how to flash recovery. I have tried flashing recovery through terminal and surprisingly it says "-bash: fastboot: command not found"
grnmons said:
Thanks for your help ogdobber, I'm incredibly frustrated and you must be too trying to help me, but I must have done something wrong as after I flash recovery, i still cannot access it - it continues to hang out in the Google screen.
Let me go through my steps with you and you tell me what I might have done wrong. So with my bricked phone, 1. I clicked your link and updated my SDK.
There's no indication that I did anything right here, it just shows that everything is installed and that's all I think I need here.
2. Opened up terminal fastboot flash boot (in this case) bootloader-toro-primekk15.img DONE!
3. Fastboot flash recovery (in this case) recovery-clockwork-5.0.2.0-crespo.img
DONE!
Then... nothing. Recovery doesn't load for me. Just get a boot loop. Anything I might have done wrong prior or inbetween these steps? Also, besides flashing and running commands off terminal - i assume this is considered computer recognizes my phone. Could the problem be there?
Click to expand...
Click to collapse
that is for the nexus s
check your pm
ogdobber said:
that is for the nexus s
check your pm
Click to expand...
Click to collapse
If you are still having problems ...like I said before ...use Odin......since the simple process of fastboot is not working properly for you.Odin makes things so Much easier
Sent from my Galaxy Nexus using xda premium
Not sure what's going on here.. I unrooted my kindlefire with update.zip but I forgot to wipe to factory reset before i flashed update.zip and when i rebooted my kindle i noticed that A ! symbol popped up with "Sorry" that says "The application Calendar Storage (process com.android.providers.calendar) has stopped unexpectedly. Please try again" That isn't the only problem, i click force close and another prompt comes up saying "The process android.process.acore has stopped unexpectedly. Please try again" It waits a few seconds, then proceeds to do a fast reboot? It comes up with the yellow kindle fire and immediately after it boots up it shows the errors.
Not sure what to do. Tried installing TWRP but the kindle doesn't stay on long enough so right now I'm pretty unconvinced of anything..
Any help would be greatly appreciated.
You just need to fast quickly get to factory reset and reset it try from a powered off position it may give you a few seconds extra to complete the task...
Thepooch said:
You just need to fast quickly get to factory reset and reset it try from a powered off position it may give you a few seconds extra to complete the task...
Click to expand...
Click to collapse
I'm not sure how to get there.. I don't have any form of backup installed. It's on the complete default rom
Edit: Found out how to get to factory reset, only to discover that I need a 40% charge, when mine is less than 5% and won't charge any more because of my problem
Still haven't figured this out. Can't use my kindle at all until this is fixed :/
iKrotos said:
Still haven't figured this out. Can't use my kindle at all until this is fixed :/
Click to expand...
Click to collapse
You're most likely going to have to put the device into fastboot mode to fix this problem. You can quickly send a sequence of adb commands to put the device into fastboot before the system crashes...
http://forum.xda-developers.com/showthread.php?t=1638452
by using the "Getting to fastboot mode" section above. That seems sketchy at best. Otherwise, you can get a factory cable...
http://forum.xda-developers.com/showthread.php?t=1550999
and put it into fastboot mode that way. In either case, you'll want to delete the userdata partition...
Code:
fastboot -i 0x1949 erase userdata
Then the next time you boot the device normally (by changing the bootmode back to 4000 if it isn't already), the system software will remake that partition and it should boot normally.
kinfauns said:
You're most likely going to have to put the device into fastboot mode to fix this problem. You can quickly send a sequence of adb commands to put the device into fastboot before the system crashes...
http://forum.xda-developers.com/showthread.php?t=1638452
by using the "Getting to fastboot mode" section above. That seems sketchy at best. Otherwise, you can get a factory cable...
http://forum.xda-developers.com/showthread.php?t=1550999
and put it into fastboot mode that way. In either case, you'll want to delete the userdata partition...
Code:
fastboot -i 0x1949 erase userdata
Then the next time you boot the device normally (by changing the bootmode back to 4000 if it isn't already), the system software will remake that partition and it should boot normally.
Click to expand...
Click to collapse
Read the beginners guide for KF, Found about about ADB fastboot etc. Going to install ADB tomorrow and try to figure this all out. Thanks.
I can't do this. It's been over a month. My kindle is finished..
iKrotos said:
I can't do this. It's been over a month. My kindle is finished..
Click to expand...
Click to collapse
"I can't do this"
Well that explains everything, doesn't it? It's a good thing you explained your problem in such great detail or I might spend time trying to help you fix your Kindle thinking you "could" do it. Phew. Saved us all a lot of time, thank you.
I made the same mistake of flashing the stock update without wiping and factory resetting.
The device will boot, then immediately give the calendar and android.process.acore errors for about 20 seconds before rebooting. It doesn't give me enough time to do a factory reset through the menu before it restarts.
After reading up on basic guides and downloading the necessary software, I can't find a way to get to fastboot, and I'm afraid even the noob guides are just confusing me more at this point.
From what I can understand, I'll probably have to get a factory cable to force the device into fastboot, because the Kindle reboots before the PC has a chance to recognize it, but what happens then? I've read the ADB for dummies guides, and searched the forum for and I still can't really understand how to execute the commands.
Can anyone link a relevant thread, or maybe give some dumbed-down advice?
LaszloToth said:
I made the same mistake of flashing the stock update without wiping and factory resetting.
The device will boot, then immediately give the calendar and android.process.acore errors for about 20 seconds before rebooting. It doesn't give me enough time to do a factory reset through the menu before it restarts.
After reading up on basic guides and downloading the necessary software, I can't find a way to get to fastboot, and I'm afraid even the noob guides are just confusing me more at this point.
From what I can understand, I'll probably have to get a factory cable to force the device into fastboot, because the Kindle reboots before the PC has a chance to recognize it, but what happens then? I've read the ADB for dummies guides, and searched the forum for and I still can't really understand how to execute the commands.
Can anyone link a relevant thread, or maybe give some dumbed-down advice?
Click to expand...
Click to collapse
Get a factory cable and then we can work on fixing your device.
One thing you have to know about entering commands is that computers have no more intelligence than, say, an ordinary rock. Meaning, they are not able to think on their own. They don't have the capacity to make their own decisions. Everything is laid out for them via sets of instructions. ADB and fastboot are programs with their own sets of instructions embedded into them, so in order to use them, you must direct the computer to those programs. When entering commands from the command line, the computer will search only the present working directory for those commands (plus any directories in it's PATH, but that is a subject for another time). When you open a command prompt in Windows, it will start in a specific directory (folder). Normally in Windows its the "Documents and Settings" folder (if I remember correctly). When you enter a command like "adb devices", the computer will search it's own set of built in commands for the first word (command) in the command line (in this case, adb). If that command isn't in it's set of built in commands, it searches the present working directory. In all likelihood, adb will not be in in the first present working directory when the command prompt opens up so you have to redirect it. There are several ways to do this. You can make sure the directory containing adb is in your PATH, but there's a little bit of learning involved and it's unnecessary unless you intend to enter a LOT of adb commands. You can change directories (cd) to the correct folder, but if you don't know what you're doing it can get very confusing and frustrating. The easiest and most straight forward way of doing this is to locate the directory containing adb and fastboot then "Shift + right-click, on that folder and select "Open command window here". The command window that opens is where you'll enter your adb/fastboot commands. Apart from that, you must really know the commands you're using, how they're used and what they do, or you're just wasting your time.
Does or kindle gets recognized.. if so there is a chance to recover
Sent from my MB526 using Tapatalk 2
soupmagnet said:
Get a factory cable and then we can work on fixing your device.
One thing you have to know about entering commands is that computers have no more intelligence than, say, an ordinary rock. Meaning, they are not able to think on their own. They don't have the capacity to make their own decisions. Everything is laid out for them via sets of instructions. ADB and fastboot are programs with their own sets of instructions embedded into them, so in order to use them, you must direct the computer to those programs. When entering commands from the command line, the computer will search only the present working directory for those commands (plus any directories in it's PATH, but that is a subject for another time). When you open a command prompt in Windows, it will start in a specific directory (folder). Normally in Windows its the "Documents and Settings" folder (if I remember correctly). When you enter a command like "adb devices", the computer will search it's own set of built in commands for the first word (command) in the command line (in this case, adb). If that command isn't in it's set of built in commands, it searches the present working directory. In all likelihood, adb will not be in in the first present working directory when the command prompt opens up so you have to redirect it. There are several ways to do this. You can make sure the directory containing adb is in your PATH, but there's a little bit of learning involved and it's unnecessary unless you intend to enter a LOT of adb commands. You can change directories (cd) to the correct folder, but if you don't know what you're doing it can get very confusing and frustrating. The easiest and most straight forward way of doing this is to locate the directory containing adb and fastboot then "Shift + right-click, on that folder and select "Open command window here". The command window that opens is where you'll enter your adb/fastboot commands. Apart from that, you must really know the commands you're using, how they're used and what they do, or you're just wasting your time.
Click to expand...
Click to collapse
Thanks, I've read up a bit more about the ADB and Fastboot commands, and I think I have a better grasp on them now, and your explanation of where I need be as far as changing directories in the command prompt really clears things up.
From reading your advice earlier in this thread, my best option would probably be to wipe the existing user data on the device that I forgot about before re-flashing the stock Kindle update by changing directories to the folder which contains ADB.exe and Fastboot.exe, then running the "fastboot -i 0x1949 erase userdata" command once I've connected the device with a factory cable. By doing this, would I be essentially restoring the device as if it were brand new again? Aside from erasing user data, are there any other ADB or Fastboot commands that I should run?
Also, assuming the ADB drivers are installed properly, once I've plugged in the device with the factory cable, will KFU immediately recognize the device, or will I need to first run the "fastboot -i 0x1949 erase userdata" command to get it back to stock first before I get 4000 status in KFU? I'm wondering if I could just plug in the factory cable, root and flash TWRP via KFU, then wipe and factory reset the user data from within TWRP, or would that be going about it backwards?
Thanks again fro the help!
---------- Post added at 02:31 PM ---------- Previous post was at 02:24 PM ----------
kishorev said:
Does or kindle gets recognized.. if so there is a chance to recover
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
No, the KFU status is "unknown" and Windows doesn't even really have time to recognize that the device is connected via USB, since the Kindle will reboot every 15-20 seconds.
I've ordered a factory cable, so hopefully it will be a pretty straight-forward fix once I get it.
Had a similar problem of rebooting every 10 sec or so..I left it on charge overnight and it worked..it got charged decent enough for me to help recover it..
Just try charging it overnight it might just work..I always feel using factory cable shd be the last resort
Sent from my Kindle Fire using Tapatalk 2
LaszloToth said:
Thanks, I've read up a bit more about the ADB and Fastboot commands, and I think I have a better grasp on them now, and your explanation of where I need be as far as changing directories in the command prompt really clears things up.
From reading your advice earlier in this thread, my best option would probably be to wipe the existing user data on the device that I forgot about before re-flashing the stock Kindle update by changing directories to the folder which contains ADB.exe and Fastboot.exe, then running the "fastboot -i 0x1949 erase userdata" command once I've connected the device with a factory cable. By doing this, would I be essentially restoring the device as if it were brand new again? Aside from erasing user data, are there any other ADB or Fastboot commands that I should run?
Also, assuming the ADB drivers are installed properly, once I've plugged in the device with the factory cable, will KFU immediately recognize the device, or will I need to first run the "fastboot -i 0x1949 erase userdata" command to get it back to stock first before I get 4000 status in KFU? I'm wondering if I could just plug in the factory cable, root and flash TWRP via KFU, then wipe and factory reset the user data from within TWRP, or would that be going about it backwards?
No, the KFU status is "unknown" and Windows doesn't even really have time to recognize that the device is connected via USB, since the Kindle will reboot every 15-20 seconds.
I've ordered a factory cable, so hopefully it will be a pretty straight-forward fix once I get it.
Click to expand...
Click to collapse
One thing you need to realize, is that once you get custom recovery installed, you will rarely ever need to use fastboot commands. Fastboot commands really only need to be used when everything else fails. Custom recovery and the latest version of the FireFireFire bootloader have probably 90% of the functionality that fastboot has, so unless those options aren't available to you, try to avoid fastboot altogether.
Most Kindle Fire problems are fixed by wiping the system, data & cache (factory reset) partitions and reinstalling the ROM.
Your first course of action should be to get TWRP and FireFireFire installed, if they aren't already. For this you will need fastboot commands. In order to issue fastboot commands, you need to be in fastboot mode. I'm guessing this is most likely not the case. Unfortunately, without a system to boot to, or the FireFireFire bootloader (blue Kindle Fire logo) installed, you have no chance of getting into fastboot without a factory cable.
The factory cable will get you into fastboot so you can reinstall custom recovery and reinstall a new ROM. You can then use the custom recovery to install a new bootloader (never wipe to install a bootloader BTW). Chances are, that is all you need to fix your device. You should keep your device powered off (hold power button for 20 seconds), until the factory cable arrives.
Hope that helps.
soupmagnet said:
One thing you need to realize, is that once you get custom recovery installed, you will rarely ever need to use fastboot commands. Fastboot commands really only need to be used when everything else fails. Custom recovery and the latest version of the FireFireFire bootloader have probably 90% of the functionality that fastboot has, so unless those options aren't available to you, try to avoid fastboot altogether.
Most Kindle Fire problems are fixed by wiping the system, data & cache (factory reset) partitions and reinstalling the ROM.
Your first course of action should be to get TWRP and FireFireFire installed, if they aren't already. For this you will need fastboot commands. In order to issue fastboot commands, you need to be in fastboot mode. I'm guessing this is most likely not the case. Unfortunately, without a system to boot to, or the FireFireFire bootloader (blue Kindle Fire logo) installed, you have no chance of getting into fastboot without a factory cable.
The factory cable will get you into fastboot so you can reinstall custom recovery and reinstall a new ROM. You can then use the custom recovery to install a new bootloader (never wipe to install a bootloader BTW). Chances are, that is all you need to fix your device. You should keep your device powered off (hold power button for 20 seconds), until the factory cable arrives.
Hope that helps.
Click to expand...
Click to collapse
So instead of using fastboot to wipe the user data, I should use it to install TWRP? Can you give me the fastboot command for that? Or can I do that with KFU once I plug in the factory cable?
http://forum.xda-developers.com/showpost.php?p=23747804
Thanks soupmagnet, I got the factory cable today and was able to flash FFF and TWRP with fastboot commands, and it's working like it should again. You help has been much appreciated.
same problem with kindle fire.
LaszloToth said:
Thanks soupmagnet, I got the factory cable today and was able to flash FFF and TWRP with fastboot commands, and it's working like it should again. You help has been much appreciated.
Click to expand...
Click to collapse
hi, i am new here and i got exact the same problem with you, i just ordered the factory cable, can you please give the step by step procedure on solving this problem with the factory cable. your help will be appreciated, thanks.
Thepooch said:
You just need to fast quickly get to factory reset and reset it try from a powered off position it may give you a few seconds extra to complete the task...
Click to expand...
Click to collapse
:good::good::good::good::good::good: works for me thank you
ok, today i had the same problem because i didn't wipe the factory restore!
The solution WASN'T the Factory Cable (I was considering buying one)!
Very easy:
Linux and SOUPKIT! were the solution, when the tablet boots up immediately hit the install recovery, after installing recovery, just set to boot into recovery.
Now is very much you can do (ex. wipe everything and than install update.zip all over)
Very much thank you to the guy who made SOUPKIT! (u've saved my S many many times )
Dear everyone, I am in some deep trouble. I was sick of my rom and my phone was cluttered, so I did factory reset, wiped system, and wiped the internal storage. Now I can't put CM10 on my phone. I still have TWRP installed but nothing else to flash. I cant find out how to put any files onto my phone. Help please, and thanks!
download cm10 on your comp then use this to sideload it to your phone http://teamw.in/ADBSideload
I saw this, but I don't fully understand what the "command line" is. Is it just the Command Prompt or CMD?
Command prompt. Use this thread to help you get up and running: http://forum.xda-developers.com/showthread.php?t=2082084
BMP7777 said:
Command prompt. Use this thread to help you get up and running: http://forum.xda-developers.com/showthread.php?t=2082084
Click to expand...
Click to collapse
Whenever I attempt the "adb sideload" step, I get a "DNS server failure" message. I have no no idea what this means. Honestly, I am so screwed right now. I have all the files, it shows as an ADB device, and this step is screwing me over hard.
EDIT: Don't worry, I found the error to be with the phone, when I checked the ADB devices, it said my phone was in "host" mode, even though my phone said it was in ADB sideload, and my computer should say "sideload" instead of "host". So, I did a little research, and came up with the solution of using the "adb push" command. Worked like a charm! Thanks for the help though.
I am an idiot.
Today I decided I would play around with some different ROMs. All was going well. I was becoming adept at flashing, booting, restoring, repeat.
All the ROMs I had tried up to this point were 4.3. I decided to go with something different. I installed OmniRom, which went okay, other than the fact it wouldn't recognize WiFi signals.
As any modern-day geek would do, I took to Google. I found a pretty promising solution that had me flash a firmware zip. This the point at which I made my mistake. As I should have remembered, firmware is DEVICE SPECIFIC. I did not bother to look at what device it was for as I had included "2013 Nexus 7" in my Google search.
The zip I flashed was for the Oppo Find 5. Facepalm.
My device will now not boot at all. I have tried charging for an hour or two from a computer, then a wall charger. The computer does not recognize the device. I've tried every possible button combination to get into recovery, fastboot, normal boot, etc. None have worked.
Anyone have any ideas?
What kind of firmware was it? Bootloader?
Sent from my Nexus 7 (2013) using Tapatalk 4
Muikkuman said:
What kind of firmware was it? Bootloader?
Sent from my Nexus 7 (2013) using Tapatalk 4
Click to expand...
Click to collapse
It was just firmware to help with network, called "modem-4.1.zip"
Blockerville said:
I am an idiot.
Today I decided I would play around with some different ROMs. All was going well. I was becoming adept at flashing, booting, restoring, repeat.
All the ROMs I had tried up to this point were 4.3. I decided to go with something different. I installed OmniRom, which went okay, other than the fact it wouldn't recognize WiFi signals.
As any modern-day geek would do, I took to Google. I found a pretty promising solution that had me flash a firmware zip. This the point at which I made my mistake. As I should have remembered, firmware is DEVICE SPECIFIC. I did not bother to look at what device it was for as I had included "2013 Nexus 7" in my Google search.
The zip I flashed was for the Oppo Find 5. Facepalm.
My device will now not boot at all. I have tried charging for an hour or two from a computer, then a wall charger. The computer does not recognize the device. I've tried every possible button combination to get into recovery, fastboot, normal boot, etc. None have worked.
Anyone have any ideas?
Click to expand...
Click to collapse
I was able to experience a HARD BRICK myself but it was because I flashed a 4.3.1 update on top of a 4.3 once which led me to go into the TWRP recovery and delete my SYSTEM AND INTERNAL STORAGE by accident.
Don't fret my friend. If you're experiencing the supposed HARD BRICK I experienced before (wherein it does not turn on at all), all you have to do is this:
- download the WugFresh N7 toolkit and look for a thread/try to discover how to unbrick your device using that. (they have a specific option for that actually; THANK YOU WUGFRESH)
- download the necessary factory image of your choice and binaries from this page (courtesy of google https://developers.google.com/android/nexus/images)
- You will see a button for at the WugFresh toolkit with instructions on how to unbrick your thing.
Hit thanks if this helps and if you have any more questions, feel free to reply
MartCLEANRFr said:
I was able to experience a HARD BRICK myself but it was because I flashed a 4.3.1 update on top of a 4.3 once which led me to go into the TWRP recovery and delete my SYSTEM AND INTERNAL STORAGE by accident.
Don't fret my friend. If you're experiencing the supposed HARD BRICK I experienced before (wherein it does not turn on at all), all you have to do is this:
- download the WugFresh N7 toolkit and look for a thread/try to discover how to unbrick your device using that. (they have a specific option for that actually; THANK YOU WUGFRESH)
- download the necessary factory image of your choice and binaries from this page
- You will see a button for at the WugFresh toolkit with instructions on how to unbrick your thing.
Hit thanks if this helps and if you have any more questions, feel free to reply
Click to expand...
Click to collapse
There's an option for a soft-bricked device (will turn on, just stuck in a bootloop). However, I don't see the option for a hard-bricked device.
Anyway, I'll try the soft-bricked solution and see if that works.
EDIT: Yep, doesn't seem to be working. It requires the tablet to be in Fastboot mode, which I cannot get into, because the tablet will not boot at all.
Which option did you use to unbrick your tablet?
Still no luck. Any ideas?
Did you try to start into bootloader ?
Nexus off, press volume buttons and power simultaneously.
lapocompris said:
Did you try to start into bootloader ?
Nexus off, press volume buttons and power simultaneously.
Click to expand...
Click to collapse
Yes, I tried that multiple times.
You could try to download the factory image (https://developers.google.com/android/nexus/images), extract the files into the adb platform-tools folder, open a command window and run flash-all.bat
lapocompris said:
You could try to download the factory image (https://developers.google.com/android/nexus/images), extract the files into the adb platform-tools folder, open a command window and run flash-all.bat
Click to expand...
Click to collapse
I will try that. However I do not think it will work, considering the tablet will not boot, so adb will probably not work.
But it's worth a try.
lapocompris said:
You could try to download the factory image (https://developers.google.com/android/nexus/images), extract the files into the adb platform-tools folder, open a command window and run flash-all.bat
Click to expand...
Click to collapse
Yeah doesn't work. adb doesn't see the Nexus.
Blockerville said:
Yeah doesn't work. adb doesn't see the Nexus.
Click to expand...
Click to collapse
Just an update -- sending in the tablet to SquareTrade as I purchased an extended warranty. However I only have $60 coverage at the moment because I already had the screen repaired. If they can't repair it, I'll be getting $60 to put toward buying a new Nexus. I hope all goes well :fingers-crossed:.
So, Nexus devices aren't unbrickable after all?
antypas said:
So, Nexus devices aren't unbrickable after all?
Click to expand...
Click to collapse
They usually are, but if you jack up the boot loader then you're done for.
prshosting.org
Hey Blockerville,
Have you tried this: http://forum.xda-developers.com/showthread.php?t=2381582 ?
Hey guys... i have almost the same problem. I have hard-bricked my nexus 7.
I can go to the Bootloader, but i'm not able to make the pc see the device. I tried installing usb drivers in all the ways, but when in the terminal i go in the sdk directory, and i write "adb devices", it doesn't see anything.......
Is there a way to solve this problem..?
Thanks in advances.
met97 said:
Hey guys... i have almost the same problem. I have hard-bricked my nexus 7.
I can go to the Bootloader, but i'm not able to make the pc see the device. I tried installing usb drivers in all the ways, but when in the terminal i go in the sdk directory, and i write "adb devices", it doesn't see anything.......
Is there a way to solve this problem..?
Thanks in advances.
Click to expand...
Click to collapse
While in bootloader mode, try:
fastboot devices
...not adb devices.
mdamaged said:
While in bootloader mode, try:
fastboot devices
...not adb devices.
Click to expand...
Click to collapse
IT WORKS!
Writing the command "fastboot devices" it sees the device. Now what should i do? I just want to wipe all, reinstal the recovery and flash the factory image... What command i have to write?
PS: Currently recovery doesn't work, for that i need to reinstall it..
met97 said:
IT WORKS!
Writing the command "fastboot devices" it sees the device. Now what should i do? I just want to wipe all, reinstal the recovery and flash the factory image... What command i have to write?
Click to expand...
Click to collapse
Whoa, whoa, I can't tell you what to do next until I know what you've already done, or didn't do.
Please answer the following:
Did you get the correct factory image? <-- very very important
What device do you have (FLO or DEB), I'll assume you know for sure you have the Nexus 7 2013 and NOT the Nexus 7 2012 model.
Which image did you download (so I can check). FLO is wifi, DEB has the LTE.
You do know it will revert your device to like how you got it? So make backups if possible. (you can edit the batch file and remove the -w to prevent wiping).
The following is for when you make sure you have everything right, do not do the following if you are not sure, you should answer those questions above first and I will let you know if it is ok to proceed to the stuff below.
You will need at least these files in a directory before you can do it:
From the factory tgz (once unzipped):
bootloader-flo-flo-04.02.img
flash-all.bat
flash-all.sh
flash-base.sh
image-razor-kot49h.zip
And at least these files from the dev kit:
fastboot.exe
You don't need the following for this operation, but it does not hurt:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
If all that checks out and you verified everything is right, you just do:
flash-all.bat
That will flash EVERYTHING, bootloader, recovery, system, data, cache and userdata.
mdamaged said:
Whoa, whoa, I can't tell you what to do next until I know what you've already done, or didn't do.
Please answer the following:
Did you get the correct factory image? <-- very very important
What device do you have (FLO or DEB), I'll assume you know for sure you have the Nexus 7 2013 and NOT the Nexus 7 2012 model.
Which image did you download (so I can check). FLO is wifi, DEB has the LTE.
You do know it will revert your device to like how you got it? So make backups if possible. (you can edit the batch file and remove the -w to prevent wiping).
You will need at least these files in a directory before you can do it:
From the factory tgz (once unzipped):
bootloader-flo-flo-04.02.img
flash-all.bat
flash-all.sh
flash-base.sh
image-razor-kot49h.zip
And at least these files from the dev kit:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
If all that checks out and you verified everything is right, you just do:
flash-all.bat
That will flash EVERYTHING, bootloader, recovery, system, data, cache and userdata.
Click to expand...
Click to collapse
Yes, you're right........
Well: i got the right factory image, but, sorry for that, when i was searching a solution for my problem, i have found this thread, and i didn't notice that this is for the 2013 model..... well, i've got the 2012 model. And thank you for asking that........ =S
It is the wifi model...
About the backup... i don't really care about the files, i don't actually need to do a back up.
This files:
From the factory tgz (once unzipped):
bootloader-flo-flo-04.02.img
flash-all.bat
flash-all.sh
flash-base.sh
image-razor-kot49h.zip
Click to expand...
Click to collapse
can be in a casual directory? Or they should be in the sdk directory?
the command to flash is....?
Just putting this out, this is my first time rooting and 'trying to get android' on a device. I recently got a kindle fire 2nd generation but hated the UI and other stuff. My friend suggested me to try rooting it and turn it into an android tablet instead. Following the rooting guide in the forum, I have successfully rooted the device. The next step was installing the 2nd bootloader and TWRP. I followed Hashcode's guide
HTML:
http://forum.xda-developers.com/showthread.php?t=2100963
but got stuck at step 4, flashing the bootloader. I have searched the thread but have not seen anyone solving the issue I'm having. Using cmd, I got the device to boot into fastboot mode and tried to type in 'fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin'. However, it returned an error: cannot load 'otter2-u-boot-prod-10.2.4.bin' : No error. Can someone help me? Your help is much appreciated.
Extra Info:
Amazon Kindle Fire 2 on 10.4.8 (rooted and has SuperSU)
using Windows 7 as workstation
installed KFFirstAide (yes, I have tried option 40 but stuck on <waiting for device>)
Also, I have put the 'otter2-u-boot-prod-10.2.4.bin', 'otter2-twrp-2.6.3.0-recovery.img', and 'otter2-freedom-boot-10.4.6.img' files in the C:\KFFirstAide folder. (I was thinking this might be the reason why it is not working but cannot be sure)
rocketfans14 said:
Just putting this out, this is my first time rooting and 'trying to get android' on a device. I recently got a kindle fire 2nd generation but hated the UI and other stuff. My friend suggested me to try rooting it and turn it into an android tablet instead. Following the rooting guide in the forum, I have successfully rooted the device. The next step was installing the 2nd bootloader and TWRP. I followed Hashcode's guide
HTML:
http://forum.xda-developers.com/showthread.php?t=2100963
but got stuck at step 4, flashing the bootloader. I have searched the thread but have not seen anyone solving the issue I'm having. Using cmd, I got the device to boot into fastboot mode and tried to type in 'fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin'. However, it returned an error: cannot load 'otter2-u-boot-prod-10.2.4.bin' : No error. Can someone help me? Your help is much appreciated.
Extra Info:
Amazon Kindle Fire 2 on 10.4.8 (rooted and has SuperSU)
using Windows 7 as workstation
installed KFFirstAide (yes, I have tried option 40 but stuck on <waiting for device>)
Also, I have put the 'otter2-u-boot-prod-10.2.4.bin', 'otter2-twrp-2.6.3.0-recovery.img', and 'otter2-freedom-boot-10.4.6.img' files in the C:\KFFirstAide folder. (I was thinking this might be the reason why it is not working but cannot be sure)
Click to expand...
Click to collapse
Yea you are kinda right, its because you are running the command from the system32 folder, you need to be cd'd into the folder that the files are in to run that command so "cd c:\kffaide" or w/e first and then run that command. Make sure you check the md5sum of that file before you flash it so you don't end up with a hard brick.
stunts513 said:
Yea you are kinda right, its because you are running the command from the system32 folder, you need to be cd'd into the folder that the files are in to run that command so "cd c:\kffaide" or w/e first and then run that command. Make sure you check the md5sum of that file before you flash it so you don't end up with a hard brick.
Click to expand...
Click to collapse
I have checked the md5sum of the files using a program I found here on xda. I'll try to do the cd from file right now and I'll let you know how that went. Thank you for the quick reply.
Ok, I got it up to the TWRP recovery screen. But how do I continue to flash the stock in step 4 after installing cm10.2 and gapps? Also, I do not have a factory fastboot cable.
EDIT
After installing CM10.2 and gapps, I hit reboot on TWRP and has 'unfortunately, com.android.phone has stop working' message popped up on the screen. Is it because I haven't continue to the section "Flashing back to stock" in step 4?
EDIT2 (I don't think this is related to the bootloader problem but I would like some assistance)
I rebooted again and didn't get the 'unfortunately' messages again. However, when I plug it into my computer, the device doesn't charge when it is active but charges when I put it into sleep mode. Is there any way to fix this issue?
That's because a pc doesn't put out as much amperage as a charger so it doesn't charge unless it is idle. Btw I recommend flashing cm 11, it is more up to date and has has improvements made to it that I think aren't added to cm 10.2.
Sent from my LG-P769 using Tapatalk
stunts513 said:
That's because a pc doesn't put out as much amperage as a charger so it doesn't charge unless it is idle. Btw I recommend flashing cm 11, it is more up to date and has has improvements made to it that I think aren't added to cm 10.2.
Sent from my LG-P769 using Tapatalk
Click to expand...
Click to collapse
I see. Where can I find CM11 and how do I flash it? Is it just:
1.put the file into /sdcard
2.reboot into TWRP recovery
3.uh, wipe memory?
4.install CM11
5.reboot
correct me if I'm wrong. I wasn't sure if these are the correct steps because there are a lot of different guides and most of them don't have the same steps.
P.S. Since the kindle only has 8gb, is there a way to free up more memory on the device other than the needed memory space for the os?
You have to factory reset to goto it. Download latest gapps as well. It should be in the development section for kf2 here on xda. Lemme find a link.
Link found!
http://forum.xda-developers.com/showthread.php?t=2388569
As to freeing up space all I can say is delete stuff you don't need. I don't tend to get low on my hd but the again I have a 16 gb model.
Sent from my LG-P769 using Tapatalk
stunts513 said:
You have to factory reset to goto it. Download latest gapps as well. It should be in the development section for kf2 here on xda. Lemme find a link.
Link found!
http://forum.xda-developers.com/showthread.php?t=2388569
As to freeing up space all I can say is delete stuff you don't need. I don't tend to get low on my hd but the again I have a 16 gb model.
Sent from my LG-P769 using Tapatalk
Click to expand...
Click to collapse
"Factory reset to go to?" Also, I should put CM11 zip and gapp in sdcard right?
Yes, what I meant was you have to factory reset before flashing cm 11. Kinda like how Amazon os caused a few problems if you didn't factory reset first, same applies when going to cm 11 from a previous cm os.
Sent from my LG-P769 using Tapatalk
stunts513 said:
Yes, what I meant was you have to factory reset before flashing cm 11. Kinda like how Amazon os caused a few problems if you didn't factory reset first, same applies when going to cm 11 from a previous cm os.
Sent from my LG-P769 using Tapatalk
Click to expand...
Click to collapse
I'm sorry if this sounds stupid but how do I factory reset my device? I've been working on rooting to installing bootloaders and finally at the point of getting android os on it non stop. Brain cells are dying rapidly...
In twrp hit wipe and choose factory reset.
Sent from my LG-P769 using Tapatalk
stunts513 said:
In twrp hit wipe and choose factory reset.
Sent from my LG-P769 using Tapatalk
Click to expand...
Click to collapse
Thank you so much for all the help. Everything went smoothly after your advises.
Update: It was running well for a while until when it ran out of battery and I recharged it, it won't boot into CM anymore. It just boots into TWRP recovery even if I pressed the option to reboot system and normal boot... What should I do?
Hmm could be a few things, try reflashing then ROM and gapps again, I suspect something with the boot IMG or system image is messed up. If it were the boot IMG I would think it would kick into fastboot though. Feel free to do a wipe of system, cache, and dalvik cache before you flash anything(under wipe>advanced).
Sent from my Amazon Tate using Tapatalk
stunts513 said:
Hmm could be a few things, try reflashing then ROM and gapps again, I suspect something with the boot IMG or system image is messed up. If it were the boot IMG I would think it would kick into fastboot though. Feel free to do a wipe of system, cache, and dalvik cache before you flash anything(under wipe>advanced).
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
I wiped what you said and tried to flash the rom and gapp but when booting, it will still boot into TWRP.
I'll briefly explain what I did prior to the issue.
After everything was all set up, I went to see if there were any updates which there was, the nightlies for CM 11 0518. I hit download and after download was complete, I hit the option "install and reboot". After the orange kindle fire logo came up and briefly after, the blue one, it boot into TWRP. I tried to reboot again but still no changes. So I went ahead and did a factory reset and flashed the two zip files again. The devices still boots into TWRP... I have no idea what to do afterwards and here I am requesting assistance from someone who knows things like these better.
Have you tried wiping internal storage? That's a last resort, maybe somehow your selinux xattribs got messed up. A internal storage wipe would clear them. But it will wipe your sdcard area so backup anything you want to keep over adb first.
Sent from my Amazon Tate using Tapatalk
I haven't tried wiping the internal storage yet. How do I backup over adb? Also,since you said this might be a last resort method, if it fails, is there no other way to fix it? Not even restoring back to its out of the box state and start all over again with rooting and installing bootloaders etc?
PS. I don't know if it is related to what you are talking about at all but when I plug it into my computer, it doesn't recognize my kindle fire.
It should be recognized as an adb device when plugged in while in recovery, in which case your could run
Code:
adb pull /sdcard/ sdcard/
And it should pull it, though that syntax may have been a little off, seems like the syntax when pulling a entire directory isn't quite the same as when pushing one if I remember right but I might be wrong.
You could technically try to restore it with kffa by reflashing to stock, but I don't advise doing that just yet because fastboot is rather limited in comparison to twrp recovery. Twrp gives you access to Linux shell commands over adb whereas fastboot does not and gives you simpler commands.
Sent from my Amazon Tate using Tapatalk
stunts513 said:
It should be recognized as an adb device when plugged in while in recovery, in which case your could run
Code:
adb pull /sdcard/ sdcard/
And it should pull it, though that syntax may have been a little off, seems like the syntax when pulling a entire directory isn't quite the same as when pushing one if I remember right but I might be wrong.
You could technically try to restore it with kffa by reflashing to stock, but I don't advise doing that just yet because fastboot is rather limited in comparison to twrp recovery. Twrp gives you access to Linux shell commands over adb whereas fastboot does not and gives you simpler commands.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
So in short, to backup, I can just use a adb pull command?
After that, I am lost. I don't really understand what you are saying...
Yes just type
Code:
adb pull /sdcard/
and it will pull everything into the directory you are in, which gb be messy if you execute from something like kffa because vBulletin I don't believe it will create a folder called Edward and put the rules there, it will just put all the files right there so it's recommended to specify an empty directory at the end if that command. The rest of the other post was about the comparison if fastboot versus and access. Kindle fire first aid could try to restore it but if something screws up along the way you won't be able to have as much flexibility as you do with twrp to try and fix it. This is hard to explain from my phone...
Sent from my LG-P769 using Tapatalk
stunts513 said:
Yes just type
Code:
adb pull /sdcard/
and it will pull everything into the directory you are in, which gb be messy if you execute from something like kffa because vBulletin I don't believe it will create a folder called Edward and put the rules there, it will just put all the files right there so it's recommended to specify an empty directory at the end if that command. The rest of the other post was about the comparison if fastboot versus and access. Kindle fire first aid could try to restore it but if something screws up along the way you won't be able to have as much flexibility as you do with twrp to try and fix it. This is hard to explain from my phone...
Sent from my LG-P769 using Tapatalk
Click to expand...
Click to collapse
So the steps are something like:
Backup with adb
Wipe internal storage
Flash the rom and gapp?
Alternative solution:
Restore the whole device
Repeat the root process
Installing the 2nd bootloader again
Flash rom and gapp
And the rest is if I were to restore the device, it is more flexible to use kindle fire first aide than to use TWRP?