Related
Hi
I rooted my KF using kindle fire utility 0.9.5 -successfully.
After flashing gede ROM, KF is boot looping (there is a CM9 logo with the android guy flashing on the screen)---rebooting KF brings me back to the same screen
I have absolutely no access to the device. Kindle unbrick v.1--does not do anything, it gives: waiting for device
kindle fire utility gives: device offline
adb device gives: error: device not found
however, when i plug in the KF into my computer, under Device Manager--the KF is listed as "Galaxy" with a yellow triangle. No longer listed as kindle.
Please help! Thanks
Does this sound like it may apply to you?
http://forum.xda-developers.com/showthread.php?p=25400963
&
http://forum.xda-developers.com/showthread.php?p=20317299
soupmagnet said:
Does this sound like it may apply to you?
http://forum.xda-developers.com/showthread.php?p=25400963
&
http://forum.xda-developers.com/showthread.php?p=20317299
Click to expand...
Click to collapse
Thank you for your response. the KF is fully charged so power is not an issue. The biggest issue is I have no access to the device in order to do anything. Device cannot be recognized and it reads as a Galaxy in device manager
Oh, that problem...
OK, read these
Driver information:
http://forum.xda-developers.com/showthread.php?p=23747671
Hardware ID information and reply from gedemis w/fix:
http://forum.xda-developers.com/showthread.php?p=25444709
soupmagnet said:
Oh, that problem...
OK, read these
Driver information:
http://forum.xda-developers.com/showthread.php?p=23747671
Hardware ID information and reply from gedemis w/fix:
http://forum.xda-developers.com/showthread.php?p=25444709
Click to expand...
Click to collapse
Thanks soupmagnet. However still no progress. my device is still bootlooping.
How can I get into recovery while it is still bootlooping.
I am quite (100%) certain the issue you are describing is a dead battery. It is the only issue known that causes the boot logo to flash like that. Your battery most likely died while asleep as some roms don't sleep or shut down properly.
I'm willing to bet if you pay attention and follow the steps from the links I originally gave you, you'll be able to fix your device.
soupmagnet said:
I am quite (100%) certain the issue you are describing is a dead battery. It is the only issue known that causes the boot logo to flash like that. Your battery most likely died while asleep as some roms don't sleep or shut down properly.
I'm willing to bet if you pay attention and follow the steps from the links I originally gave you, you'll be able to fix your device.
Click to expand...
Click to collapse
Qem is saying that as soon as the ROM was flashed and went into boot mode, the kindle kept bootlooping the ROM intro over and over.
Turning the KF on and off does nothing as the KF is trying to boot into the ROM but never gets past the intro screen (blue-ish android cartoon, CM9 type intro).
Because of the bootlop, there is no way to get into recovery physically and when connected to the computer, the kindle is being shown as a galaxy unit with no drivers, probably due to the flashed ROM.
mrslax said:
Qem is saying that as soon as the ROM was flashed and went into boot mode, the kindle kept bootlooping the ROM intro over and over.
Turning the KF on and off does nothing as the KF is trying to boot into the ROM but never gets past the intro screen (blue-ish android cartoon, CM9 type intro).
Because of the bootlop, there is no way to get into recovery physically and when connected to the computer, the kindle is being shown as a galaxy unit with no drivers, probably due to the flashed ROM.
Click to expand...
Click to collapse
My apologies. Apparently I misunderstood that portion of the first post and it's likely I'm just getting threads confused. So again, I apologize.
Based on this newly discovered information, I'm willing to bet you have Clockwork Mod recovery installed as opposed to TWRP. Yes? or No?
soupmagnet said:
My apologies. Apparently I misunderstood that portion of the first post and it's likely I'm just getting threads confused. So again, I apologize.
Based on this newly discovered information, I'm willing to bet you have Clockwork Mod recovery installed as opposed to TWRP. Yes? or No?
Click to expand...
Click to collapse
Qem can't post links so I posted her response instead.
"Again, thanks for your response. Yes I have clockwork Mod.
At first the KF kept bootlooping to the KF intro screen followed by a small portion of the ROM intro.
After multiple resets the intro just continues forever.
Here is a link to what it looks like. Its been like this even after powering off and on.
http://www.youtube.com/watch?v=npx9HIbF5Po"
Any ideas for bootloop
soupmagnet said:
My apologies. Apparently I misunderstood that portion of the first post and it's likely I'm just getting threads confused. So again, I apologize.
Based on this newly discovered information, I'm willing to bet you have Clockwork Mod recovery installed as opposed to TWRP. Yes? or No?
Click to expand...
Click to collapse
Please do you have any ideas re:bootloop. I am stuck.
Qem said:
Please do you have any ideas re:bootloop. I am stuck.
Click to expand...
Click to collapse
Yes. I'll try to explain it in a way that you'll understand.
You have Clockwork Mod
You need TWRP
no way to mount TWRP
soupmagnet said:
Yes. I'll try to explain it in a way that you'll understand.
You have Clockwork Mod
You need TWRP
Click to expand...
Click to collapse
Thanks.
However did you see the you-tube link in chat #9?
I do not have any access to the device (in order to install TWRP) because no application (KF utility, Kindle unbrick, cmd prompt) can find the device: "ERROR: device not found".
The only place in which the device is found is in device manager but it lists the KF as "Galaxy".
May be I might be missing something...
You need to flash a different rom, like cm7, older version of cm9, or MoDaCo, just long enough to install TWRP. CWM will not install later versions of cm9.
You can mount your sdcard in TWRP, or if your drivers are working properly, you can use the "push" command in adb to transfer another rom.
soupmagnet said:
You need to flash a different rom, like cm7, older version of cm9, or MoDaCo, just long enough to install TWRP. CWM will not install later versions of cm9.
You can mount your sdcard in TWRP, or if your drivers are working properly, you can use the "push" command in adb to transfer another rom.
Click to expand...
Click to collapse
I am having the same issue.
The problem is we flashed CWM, then a CM9 rom. Now just runs the aminamtion.zip boot screen and does nothing. it is unable to get into fastboot or CWM. inorder to flash another rom to install TWRP
KF has internal sdcard... cant mount TWRP
soupmagnet said:
You need to flash a different rom, like cm7, older version of cm9, or MoDaCo, just long enough to install TWRP. CWM will not install later versions of cm9.
You can mount your sdcard in TWRP, or if your drivers are working properly, you can use the "push" command in adb to transfer another rom.
Click to expand...
Click to collapse
Thanks. I appreciate your help.
Pardon me I am desperate to get my KF in a working condition.
However the KF does not have an external SD card. Therefore to mount TWRP on the sdcard, I need access to the device. This access is what i dont have... The sdcard on the KF is internal and I cannot open any folders in the KF due to the bootloop
Qem said:
Thanks. I appreciate your help.
Pardon me I am desperate to get my KF in a working condition.
However the KF does not have an external SD card. Therefore to mount TWRP on the sdcard, I need access to the device. This access is what i dont have... The sdcard on the KF is internal and I cannot open any folders in the KF due to the bootloop
Click to expand...
Click to collapse
No, you're misunderstanding me.
If you want to install the TWRP from inside the rom (i.e. using gscript or smirkit), you have to access recovery (in your case, CWM) to mount your sdcard. It will mount to your computer as an external drive, like a thumb drive. While mounted, transfer a rom that will work with CWM from your computer to your sdcard, then flash it in recovery to have a working rom to install TWRP.
Otherwise, if you want to use the command line method to install TWRP...
fastboot flash recovery /path/to/twrp2.1.img
...but considering KFU says "offline", that is out of the question unless you can get your drivers working.
soupmagnet said:
No, you're misunderstanding me.
If you want to install the TWRP from inside the rom (i.e. using gscript or smirkit), you have to access recovery (in your case, CWM) to mount your sdcard. It will mount to your computer as an external drive, like a thumb drive. While mounted, transfer a rom that will work with CWM from your computer to your sdcard, then flash it in recovery to have a working rom to install TWRP.
Otherwise, if you want to use the command line method to install TWRP...
fastboot flash recovery /path/to/twrp2.1.img
...but considering KFU says "offline", that is out of the question unless you can get your drivers working.
Click to expand...
Click to collapse
So I was able to find drivers for the "Galaxy" (http://pastebin.com/nhbaaWMu) and installed it. This enabled KFU to recognize my device as "online".
However there are two issues (1) there is no access to the drive. it mounts like an external drive, but does not open/explore. like an external drive or USB would.
(2) when i try to go into recovery mode via KFU, KFU gets stuck.
When you say fastboot flash recovery /path/to/twrp2.1.img, does the "path/to/twrp2."1-- mean the actual file path to where TWRP is located on my computer or is the "path/to" part of the cmd line input
Qem said:
When you say fastboot flash recovery /path/to/twrp2.1.img, does the "path/to/twrp2."1-- mean the actual file path to where TWRP is located on my computer or is the "path/to" part of the cmd line input
Click to expand...
Click to collapse
Actual path to file.
[Edit:] I've heard one of the roms here won't mount the sdcard in TWRP but I'm not sure which one. It may be gedeRom.
still boot looping affter fastboot+twrp2
soupmagnet said:
Actual path to file.
[Edit:] I've heard one of the roms here won't mount the sdcard in TWRP but I'm not sure which one. It may be gedeRom.
Click to expand...
Click to collapse
Thank you for your help thus fat, I appreciate it. However I still have not fixed the issue...
I tried it (actual path to file), it still said "waiting for device".
after a while, I held held power button to manually reboot, still nothing.
I also uninstalled and re installed the drivers... nothing
using KFU to boot into normal mode still returns "system cannot find the drive specified."
at wits end...
Pardon the typo..
soupmagnet said:
Actual path to file.
[Edit:] I've heard one of the roms here won't mount the sdcard in TWRP but I'm not sure which one. It may be gedeRom.
Click to expand...
Click to collapse
In prev post, I meant thanks for your help thus "far" and not "fat"
sorry for the typo
So I made a mistake and I tried to flash the newest aokp build 3 without a backup. I got my new phone a while back and never made a backup.
I flashed build 3 and (accidentally) some old gapps and I kept getting stuck on the Google screen.
Next I tried pushing files through the Gnex tool kit and manually through fastboot. I keep getting errors that there is no insecure boot or that the device is not connected. attempts at a temporary insecure boot on the tool kit fail.
Next I tried a wipe and then just installing build 3 without google apps so I could add the correct one after boot, but it is again stuck.
So now I'm really not sure what to do. Any suggestions?
Rule number 1 : STOP using toolkits!!
now, can you get into cwm recovery?
Yes, I can gt into twrp everything I did except for trying to push the last files was through twrp
by the way, I have a Verizon Nexus
And as a side comment: The tool kit was used as a last ditch effort. The toolkit had nothing to do with bricking the device. The toolkit has been extremely useful for unlocking and rooting multiple devices quickly.
You could eithther try to flash back to stock or you could boot into TWRP & adb push a different ROM. (You did try Wipe Data / Factory Reset right?)
MK17 said:
Yes, I can gt into twrp everything I did except for trying to push the last files was through twrp
by the way, I have a Verizon Nexus
And as a side comment: The tool kit was used as a last ditch effort. The toolkit had nothing to do with bricking the device. The toolkit has been extremely useful for unlocking and rooting multiple devices quickly.
Click to expand...
Click to collapse
I think what thegtfusion was trying to say was: if you wouldn't have used a toolkit in the past, you would have known how to fix your bootloop.
Buy anyway:
1) Boot into recovery and plug into your PC
2) Open a command prompt (in the folder where you have adb.exe and fastboot.exe)
3) Push the ROM (and kernel if it doesn't come with it) you want to flash to your device: adb push /path/to/ROM.zip /sdcard/
4) Reboot into fastboot mode
5) Erase your old ROM: fastboot erase system
6) Erase your old kernel: fastboot erase boot
7) Reboot into recovery
8) Wipe /data and /cache
9) Flash your ROM & kernel in recovery
10) Reboot. Done.
EDIT: Ninja'd by 3rdstring!
Screwing up is part of the learning process. It's actually a great way to learn how your phone really works.
Thanks for the reply. For some reason I can't get my device to be recognized on my new computer. I downloaded drivers, adb and fastboot and rebooted everything but it didn't work. I'll have to retry again on my other computer tomorrow.
MK17 said:
Thanks for the reply. For some reason I can't get my device to be recognized on my new computer. I downloaded drivers, adb and fastboot and rebooted everything but it didn't work. I'll have to retry again on my other computer tomorrow.
Click to expand...
Click to collapse
Try uninstalling all drivers and reinstalling them.
Sent from my Galaxy Nexus using xda premium
Drivers
Thanks for the drivers. I uninstalled all of the drivers and used the universal one. Everything seems to work until I run 'adb devices' and my Galaxy Nexus is not listed.
I feel that my device is not getting seen because of something I have wrong, but after adb, fastboot, and the correct drivers I'm not sure.
PS - Even with the universal driver I still have to run adb and fastboot from the original directory that I installed them correct? I don't run them from the driver in anyway correct?
MK17 said:
Thanks for the drivers. I uninstalled all of the drivers and used the universal one. Everything seems to work until I run 'adb devices' and my Galaxy Nexus is not listed.
I feel that my device is not getting seen because of something I have wrong, but after adb, fastboot, and the correct drivers I'm not sure.
PS - Even with the universal driver I still have to run adb and fastboot from the original directory that I installed them correct? I don't run them from the driver in anyway correct?
Click to expand...
Click to collapse
did you install android-sdk (and added adb/fastboot to your $PATH) or are you using binary versions of adb and fastboot downloaded elsewhere?
if it's the latter, commands should be run from the directory where you extracted them.
about the drivers, i think you need to go to device manager and update drivers manually to the ones you installed (refered here in the post before mine), assuming you're on windows.
sent from my i9250
You're booted into TWRP when trying adb?
Fixed! I ended up booting into recovery and the device was recognized in adb there. I was able to push fresh copies of aokp build 3 and gapps (my original build 3 download started failing) and now I just got done initiating swagger!
MK17 said:
Fixed! I ended up booting into recovery and the device was recognized in adb there. I was able to push fresh copies of aokp build 3 and gapps (my original build 3 download started failing) and now I just got done initiating swagger!
Click to expand...
Click to collapse
he didnt have usb debugging on.
sent from my i9250
Just for understanding, USB debugging is only activated through recovery?
It's also under settings >> developer options so you can use adb while the android is running.
3rdstring said:
It's also under settings >> developer options so you can use adb while the android is running.
Click to expand...
Click to collapse
Of course,but that is hard to get to when your phone doesn't boot
MK17 said:
Of course,but that is hard to get to when your phone doesn't boot
Click to expand...
Click to collapse
USB Debugging needs to be enabled in Android for ADB to work in Android.
CWM and TWRP have USB Debugging enabled by default, so ADB will work fine in recovery with no other action from the user.
Hi everyone, i have medium to advanced experience with flashing tools, android drivers, adb, fastboot, recovery mode and so on.
This evening once i installed the OTA Update for my Galaxy Nexus (which was running Android 4.2) the process failed at the end (as usual -.-) and i got stuck at bootloader.
I've wiped it completely ending up with no OS installed on it, nothing on SDCARD (Internal storage in this case).
The problem is that, i have no drivers installed on my PC for this phone.
I've already downloaded the latest version of Android 4.2 to flash (.zip), but there's no way i can transfer the file to the phone without the drivers.
I already tried GNex toolkit but it's stuck on "waiting adb device" (i have no fastboot drivers installed and can't install them because i can't find a easy way to do so).
NexusRootToolkit fails on pushing the zip to the phone and flash also won't work.
Any idea of what can i do now?
I may even pay on paypal for a quick help to get my phone back on working
Get into the bootloader and use fastboot, or if you have a custom recovery installed (sounds like you don't) then you can adb push from there. ADB doesn't exist in the bootloader, only fastboot. Those are your options.
ttabbal said:
Get into the bootloader and use fastboot, or if you have a custom recovery installed (sounds like you don't) then you can adb push from there. ADB doesn't exist in the bootloader, only fastboot. Those are your options.
Click to expand...
Click to collapse
Actually i do have a custom recovery which is CMW, but i can't seem to get my internal storage mounted using i'ts options.
I will try to push the .zip using the ADB on the recovery mode.
After checking the logs i can now see :
Enable to mount /usb-otg
(Using NexusRootToolkit i just flashed TWRP as recovery mode)
Solved : adb push <romname.zip> /sdcard/<romname.zip>
After the push was completed, i flashed the new .zip using TWRP in recovery mode.
Has anyone found a solution to this? Same thing has happened to me and I'm freaking out.
NPasta said:
Has anyone found a solution to this? Same thing has happened to me and I'm freaking out.
Click to expand...
Click to collapse
You mean besides the post right above yours?
Solved : adb push <romname.zip> /sdcard/<romname.zip>
After the push was completed, i flashed the new .zip using TWRP in recovery mode.
Click to expand...
Click to collapse
Save the pain, just flash the stock ROM from fastboot already....
Mach3.2 said:
Save the pain, just flash the stock ROM from fastboot already....
Click to expand...
Click to collapse
This. I don't see what the problem is here.
marcelloLins said:
i have medium to advanced experience with flashing tools, android drivers, adb, fastboot, recovery mode and so on.
I already tried GNex toolkit but it's stuck on "waiting adb device" (i have no fastboot drivers installed and can't install them because i can't find a easy way to do so).
NexusRootToolkit fails on pushing the zip to the phone and flash also won't work.
Click to expand...
Click to collapse
If you have the experience you say you have why do you use a Toolkit? Just learning for myself.
Look for efrant posts, they are the best and most comprehensive even for medium-advanced experience.
With him you will learn everything you need to know, including getting out of trouble and out of.............toolkit.
Just in case (you never know in life) do you have android-sdk installed on your pc?
Good luck in your learning curve ( I am still and will always be in it)
help-a-noob
Having similar problem: no OS installed. Got bootloader and TWRP. adb push doesn't work: computer can't find device. how do I get to fastboot? HALP!
HALP...
That's classic..
Read this:
http://forum.xda-developers.com/showthread.php?t=1812959
Then follow this:
http://forum.xda-developers.com/showthread.php?t=1626895
gunner1937 said:
If you have the experience you say you have why do you use a Toolkit? Just learning for myself.
Look for efrant posts, they are the best and most comprehensive even for medium-advanced experience.
With him you will learn everything you need to know, including getting out of trouble and out of.............toolkit.
Just in case (you never know in life) do you have android-sdk installed on your pc?
Good luck in your learning curve ( I am still and will always be in it)
Click to expand...
Click to collapse
Yep, i do have it installed, mainly because i'm a developer myself ; )
I've solved it already, as i've said, pushing the rom using ADB.
The upgrade to 4.2.1 probably failed because i've had the phone rooted.
Thanks for all the support and links by the way
marcelloLins said:
The upgrade to 4.2.1 probably failed because i've had the phone rooted.
Click to expand...
Click to collapse
You are mistaken, root doesn't stop a system update. I can vouch for that myself, even though i know that it doesnt matter just from reading some people's posts around here.
You weren't exactly explicit on your first post, so I presume you didnt/dont have the correct baseband version for that specific OTA to apply. Very common.
Oh and if you've never been able to OTA update successfully, it's not "usual" for the rest of us. You should work towards becoming more verbose and objective when troubleshooting. That will make you more experienced.
Sent from my i9250
marcelloLins said:
Yep, i do have it installed, mainly because i'm a developer myself ; )
I've solved it already, as i've said, pushing the rom using ADB.
The upgrade to 4.2.1 probably failed because i've had the phone rooted.
Thanks for all the support and links by the way
Click to expand...
Click to collapse
Hey, I have this exact problem. My os is gone and all i have is my cwm.
I am also having trouble installing adb, my comp doesn't recognize my nexus.
Please help, thanks!
dicksonjoe said:
Hey, I have this exact problem. My os is gone and all i have is my cwm.
I am also having trouble installing adb, my comp doesn't recognize my nexus.
Please help, thanks!
Click to expand...
Click to collapse
Try installing the ADB Drivers manually in order for your PC to recognize it.
Have you tried putting it other modes such as Download Mode and check if your pc installs any driver?
You will have to ADB PUSH the OS image to your internal memory and use CW to flash the rom from the sdcard, but you will need the drivers installed or adb wont be able to see your phone
i have the same problem you had...
i read some stuff and installed adb, sdk and whatever...
im trying the " adb push" command, but i think im doing something wrong.
the rom is on c:\users\edgar\downloads
rom name is abc.zip (i renamed)
what is the correct command format i must type??
thanks guys...
edgarzin said:
i have the same problem you had...
i read some stuff and installed adb, sdk and whatever...
im trying the " adb push" command, but i think im doing something wrong.
the rom is on c:\users\edgar\downloads
rom name is abc.zip (i renamed)
what is the correct command format i must type??
thanks guys...
Click to expand...
Click to collapse
Use "adb sideload c:\users\edgar\downloads\abc.zip". "adb push" is for transferring files from PC to phone, not flashing.
AndyYan said:
Use "adb sideload c:\users\edgar\downloads\abc.zip". "adb push" is for transferring files from PC to phone, not flashing.
Click to expand...
Click to collapse
thanks, but isnt it what am i supposed to do? transfer the zip file to sdcard and then flash using twrp?
for example usb mount via twrp dont work for me
edgarzin said:
thanks, but isnt it what am i supposed to do? transfer the zip file to sdcard and then flash using twrp?
Click to expand...
Click to collapse
adb sideload does both transferring and flashing within a single command. The "sideloaded" ZIP gets saved as "sideload.zip" under the root of the storage.
Sent from Samsung Galaxy Nexus @ CM11
AndyYan said:
adb sideload does both transferring and flashing within a single command. The "sideloaded" ZIP gets saved as "sideload.zip" under the root of the storage.
Sent from Samsung Galaxy Nexus @ CM11
Click to expand...
Click to collapse
Thanks!! Now its working! in twrp, advanced mode, adb sideload, then i executed the command you told me!!! saved my phone
Hi. I recently rooted my phone Xperia S (LT26i) and unlocked its bootloader. I had installed CWM and TWRP recovery in the phone and I have ADB and Fastboot(Android SDK) in my computer. I had earlier flashed CWM but it wasn't working so I flashed TWRP. I had downloaded a custom ROM and Gapps in the PC and I extracted the zip files and copied them into the phone (this was a mistake). I went into TWRP and did factory reset, erased cache and wiped dalvik cache unknowingly:silly: Now I can't flash ROM or Gapps and I cannot boot normally. Earlier, ADB used to recognize the device and now it doesn't. When I turn on the phone, the Sony logo appears and pink light glows. But it doesn't go beyond that. It repeatedly restarts the phone till the splash screen. Now I can't boot the phone normally Please help, guys.
P.S. I saw a post suggesting to enter a code in the Terminal module of TWRP but it's not working.
Megaiamepic said:
Hi. I recently rooted my phone Xperia S (LT26i) and unlocked its bootloader. I had installed CWM and TWRP recovery in the phone and I have ADB and Fastboot(Android SDK) in my computer. I had earlier flashed CWM but it wasn't working so I flashed TWRP. I had downloaded a custom ROM and Gapps in the PC and I extracted the zip files and copied them into the phone (this was a mistake). I went into TWRP and did factory reset, erased cache and wiped dalvik cache unknowingly:silly: Now I can't flash ROM or Gapps and I cannot boot normally. Earlier, ADB used to recognize the device and now it doesn't. When I turn on the phone, the Sony logo appears and pink light glows. But it doesn't go beyond that. It repeatedly restarts the phone till the splash screen. Now I can't boot the phone normally Please help, guys.
P.S. I saw a post suggesting to enter a code in the Terminal module of TWRP but it's not working.
Click to expand...
Click to collapse
I'v got almost similar problem right now, but beyond that I'v flashed custom kernel to mine.
I hope someone will post here soon
edit: the kernel name is Open SEMC
but I think I can get to fast boot, so changing kernel should not be problem. But how to get some ROM to the phone, when I can't connect it anyhow?
Megaiamepic said:
Earlier, ADB used to recognize the device and now it doesn't. When I turn on the phone, the Sony logo appears and pink light glows. But it doesn't go beyond that. It repeatedly restarts the phone till the splash screen. Now I can't boot the phone normally Please help, guys.
P.S. I saw a post suggesting to enter a code in the Terminal module of TWRP but it's not working.
Click to expand...
Click to collapse
What do You menan by now not recognizing in adb? While being in adb? Are You able to boot to twrp?
fipsix said:
I'v got almost similar problem right now, but beyond that I'v flashed custom kernel to mine.
I hope someone will post here soon
edit: the kernel name is Open SEMC
but I think I can get to fast boot, so changing kernel should not be problem. But how to get some ROM to the phone, when I can't connect it anyhow?
Click to expand...
Click to collapse
If You both are able to boot into recovery(twrp), I recommend You boot into twrp, connect the phone to pc. Then Let the drivers install. After it, start the adb, use this command to command to check if Your device is connected:
Code:
adb devices
Copy the ROM zip to the folder of adb.
Then push the file to sdcard using:
Code:
adb push finlename.zip /sdcard
where filename.zip is Your ROM.
Mirhawk said:
What do You menan by now not recognizing in adb? While being in adb? Are You able to boot to twrp?
If You both are able to boot into recovery(twrp), I recommend You boot into twrp, connect the phone to pc. Then Let the drivers install. After it, start the adb, use this command to command to check if Your device is connected:
Code:
adb devices
Copy the ROM zip to the folder of adb.
Then push the file to sdcard using:
Code:
adb push finlename.zip /sdcard
where filename.zip is Your ROM.
Click to expand...
Click to collapse
I tried using the adb command but it says "error device not found"
Megaiamepic said:
I tried using the adb command but it says "error device not found"
Click to expand...
Click to collapse
You are using windows, right? Do You see the phone connected in the "Device Manager"? It might but under "Other Devices" by the name "Sony Xperia S"
Mirhawk said:
You are using windows, right? Do You see the phone connected in the "Device Manager"? It might but under "Other Devices" by the name "Sony Xperia S"
Click to expand...
Click to collapse
That's what I've done in the end. Bud I had problem with drivers for my xperia, it seemed that drivers were wrong or something. So I uninstalled them, downloaded new one and voila :good:
fipsix said:
That's what I've done in the end. Bud I had problem with drivers for my xperia, it seemed that drivers were wrong or something. So I uninstalled them, downloaded new one and voila :good:
Click to expand...
Click to collapse
Do post which drivers You installed with a link. It might help the other member.
Mirhawk said:
Do post which drivers You installed with a link. It might help the other member.
Click to expand...
Click to collapse
Ooh sorry, totally forgot about that. I dont have direct link, but I will upload them somewhere tommorow.
drivers
I hope those are the right ones, because I donwloaded tons of em
http://ulozto.cz/x4tSiM6N/drivers-fastboot-adb-flashtool-by-velcis-ribeiro-rar
Last night I attempted to root my Fire 8.9 2nd gen.. I used a video on youtube to follow the procedure (not sure if I can link it here? if so, let me know). I managed to get twrp installed, but when it rebooted it got stuck on the kindle fire logo. The color of the text "Fire" changes from Orange to Blue on boot and stays that way. I can turn it off and then back on, and hold volume up to get into twrp. Problem is, when I say to mount storage, or connect it to the computer, nothing happens, so I'm in this limbo where I can't recover back to stock or install a ROM.
Maybe I'm not doing something right when trying to mount the internal storage? I've tried on Windows 7, OS X "El Capitan" and an Ubuntu variant.
I don't have a factory cable, just the cable that came with it.
Thanks for any help!!
enjoyingsilence said:
Last night I attempted to root my Fire 8.9 2nd gen.. I used a video on youtube to follow the procedure (not sure if I can link it here? if so, let me know). I managed to get twrp installed, but when it rebooted it got stuck on the kindle fire logo. The color of the text "Fire" changes from Orange to Blue on boot and stays that way. I can turn it off and then back on, and hold volume up to get into twrp. Problem is, when I say to mount storage, or connect it to the computer, nothing happens, so I'm in this limbo where I can't recover back to stock or install a ROM.
Maybe I'm not doing something right when trying to mount the internal storage? I've tried on Windows 7, OS X "El Capitan" and an Ubuntu variant.
I don't have a factory cable, just the cable that came with it.
Thanks for any help!!
Click to expand...
Click to collapse
Does adb recognize your kindle when it's in TWRP? If it does, then enable sideloading in TWRP (under the advanced menu) and try adb sideload /path/to/ROM.zip to flash a ROM.
monster1612 said:
Does adb recognize your kindle when it's in TWRP? If it does, then enable sideloading in TWRP (under the advanced menu) and try adb sideload /path/to/ROM.zip to flash a ROM.
Click to expand...
Click to collapse
Thanks for the reply. Sort of.. If I boot it to fastload or fastboot, w/e it's called, I can open adb shell, but the prompt is odd. If I try to su , it won't work. If I boot into twrp then do adb sideload, it just doesn't work at all.
The computer sees the device though, fortunately.
enjoyingsilence said:
Thanks for the reply. Sort of.. If I boot it to fastload or fastboot, w/e it's called, I can open adb shell, but the prompt is odd. If I try to su , it won't work. If I boot into twrp then do adb sideload, it just doesn't work at all.
The computer sees the device though, fortunately.
Click to expand...
Click to collapse
Try booting into Ubuntu. Are you able to access the kindle's internal storage from within TWRP?
monster1612 said:
Try booting into Ubuntu. Are you able to access the kindle's internal storage from within TWRP?
Click to expand...
Click to collapse
Will I need adb drivers for Ubuntu? If so, where can I get them?
I can see the internal storage from twrp, yes.. when I try to format the sd card (the internal one, there's no removable option) or partition, It seems to give errors.
enjoyingsilence said:
Will I need adb drivers for Ubuntu? If so, where can I get them?
I can see the internal storage from twrp, yes.. when I try to format the sd card (the internal one, there's no removable option) or partition, It seems to give errors.
Click to expand...
Click to collapse
No adb drivers are needed for Ubuntu - you just need to make sure the android-tools-adb and android-tools-fastboot packages are installed (you'll need the 'universe' component enabled in the "Software and updates" settings to install them via apt-get). The kindle doesn't have an external sdcard, so you wouldn't be able to use a removable one. If you're trying to wipe/format the internal sdcard and other partitions, use the Wipe -> advanced wipe menu in TWRP.
monster1612 said:
No adb drivers are needed for Ubuntu - you just need to make sure the android-tools-adb and android-tools-fastboot packages are installed (you'll need the 'universe' component enabled in the "Software and updates" settings to install them via apt-get). The kindle doesn't have an external sdcard, so you wouldn't be able to use a removable one. If you're trying to wipe/format the internal sdcard and other partitions, use the Wipe -> advanced wipe menu in TWRP.
Click to expand...
Click to collapse
Got # prompt on ubuntu terminal. What steps are next to restore?
Edit: Su does not work, there's no root here. If it makes any difference in what to do next.
enjoyingsilence said:
Got # prompt on ubuntu terminal. What steps are next to restore?
Edit: Su does not work, there's no root here. If it makes any difference in what to do next.
Click to expand...
Click to collapse
If you have the # instead of the $ in the terminal, that means you're probably authenticated with root already. In that case, do apt-add-repository universe && apt-get update && apt-get install android-tools-adb android-tools-fastboot - this will automatically enable the universe repo, update the list of available packages, and install the adb and fastboot packages if they aren't already installed.
monster1612 said:
If you have the # instead of the $ in the terminal, that means you're probably authenticated with root already. In that case, do apt-add-repository universe && apt-get update && apt-get install android-tools-adb android-tools-fastboot - this will automatically enable the universe repo, update the list of available packages, and install the adb and fastboot packages if they aren't already installed.
Click to expand...
Click to collapse
Sorry, I should've been more clear. I've added in the universe repository, and installed android-adb-tools as well as android-tools-fastboot. When I said I have # at prompt, that was after typing adb shell. It seems to let me browse through the tablet, a good indicator it's connected and working. My apologies!
Now that I have connectivity from my linux box to the tablet over usb, what are the next steps to recover it? If I type adb shell <enter> whoami, it says root. So we have root access to the tablet. Yay!
enjoyingsilence said:
Sorry, I should've been more clear. I've added in the universe repository, and installed android-adb-tools as well as android-tools-fastboot. When I said I have # at prompt, that was after typing adb shell. It seems to let me browse through the tablet, a good indicator it's connected and working. My apologies!
Now that I have connectivity from my linux box to the tablet over usb, what are the next steps to recover it? If I type adb shell <enter> whoami, it says root. So we have root access to the tablet. Yay!
Click to expand...
Click to collapse
Exit adb shell if you're in it already. Now in the linux terminal, type adb push /path/to/ROM.zip /sdcard, where the /path/to/ROM.zip is where your CM/other ROM zip is located on your PC. Repeat this process for any other zips you desire to flash, like xposed, gapps, etc. This should hopefully put the files in the internal storage, from where TWRP can find and flash them. Good luck!
(Side note: assuming you can boot into TWRP, you should be able to view & manipulate the kindle's internal storage from Ubuntu with nautilus or another GUI-based file manager.)
monster1612 said:
Exit adb shell if you're in it already. Now in the linux terminal, type adb push /path/to/ROM.zip /sdcard, where the /path/to/ROM.zip is where your CM/other ROM zip is located on your PC. Repeat this process for any other zips you desire to flash, like xposed, gapps, etc. This should hopefully put the files in the internal storage, from where TWRP can find and flash them. Good luck!
(Side note: assuming you can boot into TWRP, you should be able to view & manipulate the kindle's internal storage from Ubuntu with nautilus or another GUI-based file manager.)
Click to expand...
Click to collapse
I'm not sure I have a good working rom at this point. Where might I find the latest one? Also, if I wanted to flash this back to the original FireOS... what would be the steps to do that? Thanks for your help!
edit: Found the latest CM ROM and Gapps files. Just need options for full recovery back to FireOS if needed in the end.
enjoyingsilence said:
I'm not sure I have a good working rom at this point. Where might I find the latest one? Also, if I wanted to flash this back to the original FireOS... what would be the steps to do that? Thanks for your help!
Click to expand...
Click to collapse
CyanogenMod has somewhat stable CM12.1 nightlies available for download here, although I think they're starting to slow down now. If you wanted to flash back to the stock OS, Hashcode created a ROM zip for Amazon OS 8.4.1 (the 8.4.3 version was hosted on the now-defunct goo.im), and you may find the link in this thread. That particular version is a bit outdated, but it shouldn't be too hard to manually upgrade.
monster1612 said:
CyanogenMod has somewhat stable CM12.1 nightlies available for download here, although I think they're starting to slow down now. If you wanted to flash back to the stock OS, Hashcode created a ROM zip for Amazon OS 8.4.1 (the 8.4.3 version was hosted on the now-defunct goo.im), and you may find the link in this thread. That particular version is a bit outdated, but it shouldn't be too hard to manually upgrade.
Click to expand...
Click to collapse
Would a nightly build be wise? I'd be worried about it being unstable....
Thanks for the factory reset link.
enjoyingsilence said:
Would a nightly build be wise? I'd be worried about it being unstable....
Thanks for the factory reset link.
Click to expand...
Click to collapse
My 1st and 2nd attempt to flash resulted in a failure. Not sure why...
enjoyingsilence said:
My 1st and 2nd attempt to flash resulted in a failure. Not sure why...
Click to expand...
Click to collapse
Try updating your TWRP. Here's Hashcode's thread that links to a download for the latest version (2.8.7.0 as of the time of writing). It's a .zip, so you can flash it in TWRP.
monster1612 said:
Try updating your TWRP. Here's Hashcode's thread that links to a download for the latest version (2.8.7.0 as of the time of writing). It's a .zip, so you can flash it in TWRP.
Click to expand...
Click to collapse
Thanks. I was able to update twrp and get the 23rd of Dec's nightly CM12 build installed. It didn't seem to work properly though, and gapps wouldn't install. So I've resigned to the fact that I need to put the original OS back on it. After updating twrp, this doesn't seem possible. When I connect it to the computer, all I'm getting is error: device offline when typing adb shell. This is in linux and windows.
I tried connecting it and mounting the usb storage, then dragging over the fireos images, but after installation it went into this reboot loop due to a corrupt something or other... Now, I can't get cm or the original os back on it.
So, some updates... it's still dead.. but here goes:
I tried to copy the original os as found in the link you gave above to the fire via the usb storage mode, but after install and reboot it keeps failing as I mentioned due to corrupt data (the amazon os is throwing that error). so I tried adbsideload... it kept telling me that i needed 1.0.32 or newer of adb. After obtaining that, I was able to sideload the original OS image to no avail.
So I tried the recovery tool: KFHD System.img Recovery Tool but I used the wrong one (the one that isn't for 8.9 inch fire hd tablets)... and now it's stuck at the fire logo (orange/yellow in color). Turning off on again and holding volume up to get to twrp no longer works as it's been de rooted, I believe.
Any suggestions?
enjoyingsilence said:
So, some updates... it's still dead.. but here goes:
I tried to copy the original os as found in the link you gave above to the fire via the usb storage mode, but after install and reboot it keeps failing as I mentioned due to corrupt data (the amazon os is throwing that error). so I tried adbsideload... it kept telling me that i needed 1.0.32 or newer of adb. After obtaining that, I was able to sideload the original OS image to no avail.
So I tried the recovery tool: KFHD System.img Recovery Tool but I used the wrong one (the one that isn't for 8.9 inch fire hd tablets)... and now it's stuck at the fire logo (orange/yellow in color). Turning off on again and holding volume up to get to twrp no longer works as it's been de rooted, I believe.
Any suggestions?
Click to expand...
Click to collapse
The volume up to enter TWRP no longer works because the bootloader's been returned to stock. Regardless, you should be able to boot into fastboot. First, make sure the kindle's turned off completely and not plugged into your PC. Then type fastboot -i 0x1949 getvar product. When you see <waiting for device>, plug the kindle in. The kindle should now show a fastboot screen, and the terminal will have outputted a string looking like "Jem-PVT-Prod-04". At this point, if both of those are true, then you should either locate your backups of the stock software or download it for your device. If you haven't made backups, then you can try this tool to attempt to restore. If that tool doesn't work, I have a backup that I'd be willing to share if necessary. In any case, once you have the stock system images, you should flash them as instructed by Hashcode here (skip to the "Flashing back to stock" section). Good luck!
monster1612 said:
The volume up to enter TWRP no longer works because the bootloader's been returned to stock. Regardless, you should be able to boot into fastboot. First, make sure the kindle's turned off completely and not plugged into your PC. Then type fastboot -i 0x1949 getvar product. When you see <waiting for device>, plug the kindle in. The kindle should now show a fastboot screen, and the terminal will have outputted a string looking like "Jem-PVT-Prod-04". At this point, if both of those are true, then you should either locate your backups of the stock software or download it for your device. If you haven't made backups, then you can try this tool to attempt to restore. If that tool doesn't work, I have a backup that I'd be willing to share if necessary. In any case, once you have the stock system images, you should flash them as instructed by Hashcode here (skip to the "Flashing back to stock" section). Good luck!
Click to expand...
Click to collapse
Thanks for the reply. Surely I must be overlooking something.
I downloaded the kindle fire HD recovery tool from the link you provided (the post by onemeila) - KFHD_SRTv2.1-8.14. Opened the SR Tool file, and used option 2 to restore su and such. When it rebooted, nothing happened... stayed stuck on the orange kindle fire screen.
Next, I obtained the boot and recovery img files from the KFHD System.img Recovery thread by onemeila, and put them in the root of the KFHD_SRT_v2.1 folder. I also copied the system.img that comes with the KFHD_SRT_v2.1 file to the root of it, instead of the folder I was in. Then I issued the kindle the following commands from an administrative command prompt... there weren't any errors:
fastboot -i 0x1949 flash boot boot.img
fastboot -i 0x1949 flash recovery recovery.img
fastboot -i 0x1949 flash system system.img # This one will take a few minutes
fastboot -i 0x1949 reboot
It rebooted, but has remained stuck on the orange kindle fire screen.
enjoyingsilence said:
Thanks for the reply. Surely I must be overlooking something.
I downloaded the kindle fire HD recovery tool from the link you provided (the post by onemeila) - KFHD_SRTv2.1-8.14. Opened the SR Tool file, and used option 2 to restore su and such. When it rebooted, nothing happened... stayed stuck on the orange kindle fire screen.
Next, I obtained the boot and recovery img files from the KFHD System.img Recovery thread by onemeila, and put them in the root of the KFHD_SRT_v2.1 folder. I also copied the system.img that comes with the KFHD_SRT_v2.1 file to the root of it, instead of the folder I was in. Then I issued the kindle the following commands from an administrative command prompt... there weren't any errors:
fastboot -i 0x1949 flash boot boot.img
fastboot -i 0x1949 flash recovery recovery.img
fastboot -i 0x1949 flash system system.img # This one will take a few minutes
fastboot -i 0x1949 reboot
It rebooted, but has remained stuck on the orange kindle fire screen.
Click to expand...
Click to collapse
Do you have adb installed system-wide? If you do, try cd'ing to the directory where you placed the boot, recovery, and system images and then running those commands again. If you don't, then move the files to the folder where the adb and fastboot executables are located and run the commands in that folder.