Related
I recently rooted my kindle fire and installed twrp along with cm7, but I accidently did a factory reset inside cm7 and was stuck on the firefirefire logo, I used an unbrick tool, but that erased all my user data and did not help. I managed to get my boot back to 4000 and install twrp again, but it won't let me mount sd card and will only allow me to mount system.
Sorry Im a noob
Im having the same issue, trying to moun it, but I keep getting
Error mounting /sdcard!
Is there a way to fix it? Im stuck on recovery (CW)
Heres a great idea get off of the discontinued recovery and switch to touch screen clockworkmod recovery its way better when it comes to things like that
Link: http://forum.xda-developers.com/showthread.php?t=1454241
guys this has nothing to do with twrp - it's working fine
just do following:
- boot to twrp
- test adb with "adb devices"
- open shell -> "adb shell"
- issue "echo /dev/block/mmcblk0p12 > /sys/devices/platform/usb_mass_storage/lun0/file"
- now the sdcard should mount to the computer
- windows will probably respond that the volume/device needs formatted before using it
- choose quick format and let it format it as fat32 block size 4096
Thanks b63 for the fast reply. I dont have twrp I have CWM recovery, im trying to install TWRP but I get an error:
error: device not found
Is there another way to install TWRP?
Thanks
i don't know about cwm but i would try to boot to it and test if adb is working
then it should be the same - you only need adb root access
if you have this access with cwm also then there is no need to install twrp
Well if I boot into CWM
I can do adb shell
But then nothing happens
If I let Kindle boot normally (after the Yellow triangle) the screen goes black and I cant adb shell anymore
What im doing wrong or what im missing.
Thanks again
BTW
When I boot int CWM I get this message
E:Can't Mount /cache/recovery/command
stay in your recovery
after the command the sdcard should mount to your computer
check your device manger
follow the first desciption
if you can't get it gimme a pm ...
Wooooot!
Thank you so much b63!!!!I couldnt sleep for this damn problem
In the end this one help me out
echo /dev/block/mmcblk0p12 >> /sys/devices/platform/usb_mass_storage/lun0/file
I dont know why it worked with >> its the same (for this case) but I could finally mount it on windows
Now im back to CM7, really thanks!!!!!
really glad that it worked ...
b63 needs a medal lol.
Sent from my HTC Glacier using xda premium
Thanks b63 I got twrp to mount the sd card, with this:
echo /dev/block/mmcblk0p12 >> /sys/devices/platform/usb_mass_storage/lun0/file
But, when trying to install cm7 I get an error:
E:Cannot load volume /misc!
ignore it - the kf don't have a volume "misc"
Stuck in twrp!!!!
b63 said:
guys this has nothing to do with twrp - it's working fine
just do following:
- boot to twrp
- test adb with "adb devices"
- open shell -> "adb shell"
- issue "echo /dev/block/mmcblk0p12 > /sys/devices/platform/usb_mass_storage/lun0/file"
- now the sdcard should mount to the computer
- windows will probably respond that the volume/device needs formatted before using it
- choose quick format and let it format it as fat32 block size 4096
Click to expand...
Click to collapse
I can get into TWRP, but when I type in ADB DEVICES in command prompt, it says the standard daemon not running, then daemon started successfully. This is followed by List of Devices attached, but it's blank after that.
I used the Kindle Fire Utility to install drivers, and when I use ADB DEVICES Command Prompt with my T-Mo Vibrant, I can get into ADB Shell.
Any advice?
Please note, this isn't mine. I've never owned a Kindle Fire, so I'm banging myself raw with information overload on this type of device. I'm trying to help a co-worker out with his Fire that he borked. I've owned three android phones/tablets and rooted/ROMed all of them, so I follow instructions. So far, I've tried the Kindle Fire Utility and the Kindle Fire Unbrick Utility found in these forums. My co-worker didn't get to the point of making a back-up or installing the Stock Image as an Update.zip. I have the stock image downloaded, and have renamed it, but I can't get it onto the tablet at all. Selecting Mount in TWRP always locks everything up, and there is nothing to Install or Restore. So, like I said, I'm getting bloody here, but no joy.
Any help would be appreciated!
what's the status of the kf ? -> you can get into twrp - that is good - do that
what's the status of the drivers in device manager ? -> which driver loaded ?
what have you/he done/tried to get to this point?
i'm asking to give you the right method ...
b63 said:
what's the status of the kf ? -> you can get into twrp - that is good - do that
what's the status of the drivers in device manager ? -> which driver loaded ?
what have you/he done/tried to get to this point?
i'm asking to give you the right method ...
Click to expand...
Click to collapse
He says he rooted it, installed FireFireFire, and the ICS-ish launcher (name eludes me at this point). Then, it basically boot-looped (Yellow Triangle, then Kindle Fire, back to Yellow Triangle).
My first thought was ADB Shell, but the KF is apparently a stranger animal than most of the other Androids I've dealt with, so it didn't automatically pop up. I installed KFU (Kindle Fire Utility, most recent version), installed the windows drivers (I have Win7 Pro 64-bit) that came with the KFU, and attempted to get it to boot normally, recovery, or anything. Note - A couple of times (like 4 or 5 out of 100), it did make it to a full boot for a few seconds, but would crash within seconds. TWRP was not installed at that point, so I successfully pushed that with the KFU. I also downloaded the stock image, and renamed it. TWRP won't mount the SD card so that my computer can see it, so I'm losing that battle. Also, at some point along the way, the KF started attempting to connect to the PC when plugged in, with the typical USB device connected sound, but two seconds later, it acts like it is unplugged, with that sound. If the KF is visible in the Device Manager, it must be hidden, cuz I can't see it. This was not the case at first, with an Unmount icon for the Kindle being displayed in the notification (right) side of the Windows toolbar. This is in conjunction with the device now booting straight to TWRP, and not even attempting to go the normal boot route. I've also tried a Kindle Fire Unbrick Utility to restore it, with no luck. It wipes the User Data, wipes cache, downloads the update.zip, but can't mount the unit to push the data. I've never been able to get ADB to find the unit.
If I can get the update.zip to the SD root, or if I can ADB shell it, I think I've won. But I'm being blocked on both those counts.
Thanks for being willing to look into this for me!
the problem is the ics launcher - it simply don't work
would recommend to use go launcher instead, for the future
now to the problem:
one solution is to boot to twrp - there is adb root access available
maybe check and update drivers - look here:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
then delete the ics launcher .apk (don't know the exact name) with adb commands
this should make the kf startable again and nothing is lost
an other solution is to flash a new rom but i don't think that this is necessary
and never ever flash the original rom from amazon unless you want to return the device - there is a risk of bricking it and you will loose fff,twrp and root
there are prerooted stock images available for returning to stock rom:
http://forum.xda-developers.com/showpost.php?p=22393194&postcount=20
if you need closer help gimme a pm ...
b63 said:
the problem is the ics launcher - it simply don't work
would recommend to use go launcher instead, for the future
now to the problem:
one solution is to boot to twrp - there is adb root access available
maybe check and update drivers - look here:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
then delete the ics launcher .apk (don't know the exact name) with adb commands
this should make the kf startable again and nothing is lost
an other solution is to flash a new rom but i don't think that this is necessary
and never ever flash the original rom from amazon unless you want to return the device - there is a risk of bricking it and you will loose fff,twrp and root
there are prerooted stock images available for returning to stock rom:
http://forum.xda-developers.com/showpost.php?p=22393194&postcount=20
if you need closer help gimme a pm ...
Click to expand...
Click to collapse
You're giving me a lot of hope. I'll give this a try when I get home tonight, and I'll contact you with any other hurdles. THANK YOU SO MUCH!
halfway there
Ok so I have run the command under the adb shell after adb did detect the device, however when I run the command it says that "non existent directory" What am I missing?
echo /dev/block/mmcblk1p1 > /sys/devices/platform/usb_mass_storage/lun0/file
/sbin/sh: can't create /sys/devices/platform/usb_mass_storage/lun0/file: nonexis
tent directory
Getting that when i try to issue the command,
Any hint?
Majorly failed..
It seems i have completely "deleted" some system partitions and i'm currently unable to figure out how to repair them. (This is my hypothesis)
I have CWM v5.5.04
FFF 1.4
I have tried to install TWRP via fastboot and it just freezes on the TWRP splash screen and locks up.
This issue started when i saw the release of CWM v5.5.04 and flashed it using TWRP.
I' read that kindle fire for beginners thread and googled for hours unfortunately i'm unable to find any similar issue.
Any help will be appreciate it.
Also, i am able to fastboot via FFF and can't seem to adb (there's a chance i'm doing something wrong)
Also when i try to install a custom rom via CWM it locks up restarts and then unmounts the SD card. Not allowing me to remount, i have to restart CWM in order for it to read the SD card.
I have a ROM on the sd card, i can't mount SD card via CWM. The option is there i enable it but it doesn't actually mount.
Code:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
jsantiago.antonio said:
Majorly failed..
It seems i have completely "deleted" some system partitions and i'm currently unable to figure out how to repair them. (This is my hypothesis)
I have CWM v5.5.04
FFF 1.4
I have tried to install TWRP via fastboot and it just freezes on the splash screen and locks up.
This issue started when i saw the release of CWM v5.5.04 and flashed it using TWRP.
I' read that kindle fire for beginners thread and googled for hours unfortunately i'm unable to find any similar issue.
Any help will be appreciate it.
Also, i am able to fastboot via FFF and can't seem to adb (there's a chance i'm doing something wrong)
Also when i try to install a custom rom via CWM it locks up restarts and then unmounts the SD card. Not allowing me to remount, i have to restart CWM in order for it to read the SD card.
I have a ROM on the sd card, i can't mount SD card via CWM. The option is there i enable it but it doesn't actually mount.
Code:
Click to expand...
Click to collapse
Get into fastboot mode through the bootloader and flash whichever recovery you want.
You cannot use adb while in fastboot mode. You must be booted into recovery or the system software to use adb. Alternatively, you must be in fastboot mode via the bootloader to use fastboot.
To flash a ROM, you would not "mount" the /sdcard partition through recovery. That would make /sdcard available to the host computer and unavailable to the recovery.
EDIT: If you think you've screwed up your partition table, you can use FFF's...
Code:
fastboot oem format
To see if your partitions have valid filesystems, you can use parted through adb while you are in recovery...
Code:
adb shell
parted /dev/block/mmcblk0
Be careful with both of those.
In my experience, most ROMs will repair partitions like /cache and rebuild the filesystems automatically when you boot them.
kinfauns said:
Get into fastboot mode through the bootloader and flash whichever recovery you want.
You cannot use adb while in fastboot mode. You must be booted into recovery or the system software to use adb. Alternatively, you must be in fastboot mode via the bootloader to use fastboot.
To flash a ROM, you would not "mount" the /sdcard partition through recovery. That would make /sdcard available to the host computer and unavailable to the recovery.
Click to expand...
Click to collapse
I apologize for my spelling, i wrote in rush because i just got home from work and want to repair my kindle as fast i can. Haha.
I can't seem to adb on recover via CWM, it seems to either be "not working" or my drivers aren't working correctly. But i been able to adb from my kindle on recovery so i'm not so certain it's a driver problem.
I have tried to flash CWM via fastboot "successfully" but when it boots, you see the errors on the image above. And when i try to install TWRP via fastboot "succesfully" it locks up when you see the splash screen.
jsantiago.antonio said:
I apologize for my spelling, i wrote in rush because i just got home from work and want to repair my kindle as fast i can. Haha.
I can't seem to adb on recover via CWM, it seems to either be "not working" or my drivers aren't working correctly. But i been able to adb from my kindle on recovery so i'm not so certain it's a driver problem.
I have tried to flash CWM via fastboot "successfully" but when it boots, you see the errors on the image above. And when i try to install TWRP via fastboot "succesfully" it locks up when you see the splash screen.
Click to expand...
Click to collapse
See if TWRP will let you drop into a shell through adb... even if you are stuck on the splash screen.
Run parted like I noted in the previous post and get it to "print" the partition table layout (I believe 'print' is the command, but you can also use 'help' for more info). Your /cache partition should have an ext4 filesystem. If it doesn't show that, you'll have to make it... I don't remember the command offhand, but it should be pretty self-explanatory in the help.
EDIT: If that doesn't work, I'll get an output of my partition table and you can compare to what you have.
kinfauns said:
See if TWRP will let you drop into a shell through adb... even if you are stuck on the splash screen.
Run parted like I noted in the previous post and get it to "print" the partition table layout (I believe 'print' is the command, but you can also use 'help' for more info). Your /cache partition should have an ext4 filesystem. If it doesn't show that, you'll have to make it... I don't remember the command offhand, but it should be pretty self-explanatory in the help.
EDIT: If that doesn't work, I'll get an output of my partition table and you can compare to what you have.
Click to expand...
Click to collapse
I just flashed TWRP via fastboot and it's stuck on the splash screen, windows is picking up the drivers but i can't seem to run adb shell, i'm gonna try to play around with drivers and see if i can fix adb.
Edit: I'm unable to adb, just tried to adb via two different systems i keep getting device not found even though drivers seem to be working as they should. I also uninstalled and re-installed drivers about 3 times now hoping that i'm doing something wrong, and still do.
jsantiago.antonio said:
I just flashed TWRP via fastboot and it's stuck on the splash screen, windows is picking up the drivers but i can't seem to run adb shell, i'm gonna try to play around with drivers and see if i can fix adb.
Edit: I'm unable to adb, just tried to adb via two different systems i keep getting device not found even though drivers seem to be working as they should. I also uninstalled and re-installed drivers about 3 times now hoping that i'm doing something wrong, and still do.
Click to expand...
Click to collapse
"Android Phone -> Android ADB Interface" is typically loaded when the device is in fastboot mode. When you are booted into the recovery, you should be seeing "Android Phone -> Android Composite ADB Interface" in the device manager.
Take a look at this...
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
and see if you can uninstall/remove/reinstall the drivers.
If that doesn't work, go into properties for the device and look at the Hardware IDs list. Let's see what you've got.
kinfauns said:
"Android Phone -> Android ADB Interface" is typically loaded when the device is in fastboot mode. When you are booted into the recovery, you should be seeing "Android Phone -> Android Composite ADB Interface" in the device manager.
Take a look at this...
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
and see if you can uninstall/remove/reinstall the drivers.
If that doesn't work, go into properties for the device and look at the Hardware IDs list. Let's see what you've got.
Click to expand...
Click to collapse
Okay, i uninstalled and adb drivers seem to be loading correctly? when i'm on recovery i see "Android Composite ADB Interface" i'm guessing it's installed correctly this is the hardware id.
EDIT: My hunch that the error lies on the SD card, i can't mount/format/partition the SD Card & Cache partition. And CWM reboots when i try to mount anything.
PS. Thank you for making the effort to help, i deeply appreciate it.
jsantiago.antonio said:
Okay, i uninstalled and adb drivers seem to be loading correctly? when i'm on recovery i see "Android Composite ADB Interface" i'm guessing it's installed correctly this is the hardware id.
EDIT: My hunch that the error lies on the SD card, i can't mount/format/partition the SD Card & Cache partition. And CWM reboots when i try to mount anything.
PS. Thank you for making the effort to help, i deeply appreciate it.
Click to expand...
Click to collapse
That looks right to me. Can you get to an adb shell prompt? I don't think you'd have issues booting to recovery just because the /sdcard partition is inaccessible. Maybe the /cache partition because the recovery is trying to write its log file there. I don't know that I've run into that exact problem.
Have you tried both the new/old versions of CWMR? TWRP?
Have you edited the partition table at any time?
Do you have critical data on the KF somewhere that you just can't afford to lose?
CWM 5.5.04 was just released a few days ago and not all of the bugs are known/fixed yet. Personally I would use something that has more of a reputation when you're trying to troubleshoot something like this.
From what I've seen, when a rom stalls or freezes at the boot animation, the problem usually happens at the recovery level.
kinfauns said:
That looks right to me. Can you get to an adb shell prompt? I don't think you'd have issues booting to recovery just because the /sdcard partition is inaccessible. Maybe the /cache partition because the recovery is trying to write its log file there. I don't know that I've run into that exact problem.
Have you tried both the new/old versions of CWMR? TWRP?
Have you edited the partition table at any time?
Do you have critical data on the KF somewhere that you just can't afford to lose?
Click to expand...
Click to collapse
I never touch partitions because of fear to things like this happening (Oh sweet irony), i just wipe through recovery and format.
CWM v5.5.0.4: I can access the SD card, see some files including a .zip with a kernel 3.0 rom when i try to flash the rom it freezes and goes back into the "install zip from sd card" options but this time it cant find any files on the SD card. Adb drivers load of from windows, but unable to adb shell.
CWM Previous Version (Currently the one KFU installs, i forgot the version number): Doesn't mount SD Card at all. Adb drivers load of from windows, but unable to adb shell.
TWRP 2.1.1: Freezes on splash screen, Adb drivers load of from windows, but unable to adb shell.
TWRP 2.0.0 RC0: Freezes on splash screen, Adb drivers load of from windows, but unable to adb shell.
----------------
I don't have any data that i honestly worry about, i just wan't my kindle back alive. lol.
I also tried downgrading FFF from 1.3 to 1.4 just for the heck of it, no luck.
that error, is a broken emmc. I hope I'm wrong but my last android phone that did that was the emmc. Google it
Sent from my HTC Glacier using xda premium
jsantiago.antonio said:
I never touch partitions because of fear to things like this happening (Oh sweet irony), i just wipe through recovery and format.
CWM v5.5.0.4: I can access the SD card, see some files including a .zip with a kernel 3.0 rom when i try to flash the rom it freezes and goes back into the "install zip from sd card" options but this time it cant find any files on the SD card. Adb drivers load of from windows, but unable to adb shell.
CWM Previous Version (Currently the one KFU installs, i forgot the version number): Doesn't mount SD Card at all. Adb drivers load of from windows, but unable to adb shell.
TWRP 2.1.1: Freezes on splash screen, Adb drivers load of from windows, but unable to adb shell.
TWRP 2.0.0 RC0: Freezes on splash screen, Adb drivers load of from windows, but unable to adb shell.
----------------
I don't have any data that i honestly worry about, i just wan't my kindle back alive. lol.
I also tried downgrading FFF from 1.3 to 1.4 just for the heck of it, no luck.
Click to expand...
Click to collapse
Yeah, well... if it's your storage device that's busted, that's obviously not going to end well.
Your bootloader is obviously still working. You might as well try the 'fastboot oem format' because it's not going to affect anything negatively if you've never edited the partition table before. Might want to reflash your bootloader right after that though... just in case.
Do you ever get any errors when you 'fastboot flash' any partitions? I don't think it's going to help, but it wouldn't hurt to 'fastboot erase recovery' before you 'fastboot flash recovery recovery.img'. Getting a parted output would really help to see what's going on with your partitions.
I have a couple of other ideas...
Try using
Code:
fastboot boot recovery.img
to upload a recovery straight into memory and boot from that and see what happens. I'd try sticking to TWRP for now. See if that helps matters.
There's also a ICS ROM out there called 'nipad' with the boot and system partitions in fastboot flashable images. You might want to just give that a whirl and see if you can actually get it to boot.
did u fix this yet?
Sent from my HTC Glacier using xda premium
I have not, i am getting back to work from it had to go to bed last night because i had work in the morning. I just got home, gonna try what was suggested i'll give an updated in a bit.
kinfauns said:
There's also a ICS ROM out there called 'nipad' with the boot and system partitions in fastboot flashable images. You might want to just give that a whirl and see if you can actually get it to boot.
Click to expand...
Click to collapse
Do you have any links for nipad by any chance? I am google searching and not finding anything.
Edit: Is there any way i could force flash a rom via fastboot? Or perhaps do system.img etc OR find a edited recovery with a scrip that formats partitions initially?
jsantiago.antonio said:
Do you have any links for nipad by any chance? I am google searching and not finding anything.
Edit: Is there any way i could force flash a rom via fastboot? Or perhaps do system.img etc OR find a edited recovery with a scrip that formats partitions initially?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1506859
Version 4.0.3 near the bottom of the OP. Get your google translate ready unless you're fluent in chinese.
Update; It's most definitely a screwed up partition i tried every suggestion given i'm researching trying to find a solution to do anything via fastboot? I know fastboot has the ability to fastboot update from a update.zip can i somehow flash stock from this?
jsantiago.antonio said:
Update; It's most definitely a screwed up partition i tried every suggestion given i'm researching trying to find a solution to do anything via fastboot? I know fastboot has the ability to fastboot update from a update.zip can i somehow flash stock from this?
Click to expand...
Click to collapse
If you figure that one out, let me know. I've looked around for some documentation or examples, but I came up empty.
I been trying things left and right, to no avail i'm starting to accept my kindles death lol. But i do feel i'm probably doing something wrong with the ADB drivers, gonna refresh my windows install and see if i could potentially have something wrong on my end (i hope).
If i had access to ADB i could fix it i'm sure, gonna search around maybe there's a script that can be preloaded to recovery that could create/repair partions instead of doing so via adb and do it within recovery.
jsantiago.antonio said:
I been trying things left and right, to no avail i'm starting to accept my kindles death lol. But i do feel i'm probably doing something wrong with the ADB drivers, gonna refresh my windows install and see if i could potentially have something wrong on my end (i hope).
If i had access to ADB i could fix it i'm sure, gonna search around maybe there's a script that can be preloaded to recovery that could create/repair partions instead of doing so via adb and do it within recovery.
Click to expand...
Click to collapse
You can install the nipad ROM I told you about earlier. Then you can use smirkit to flash a recovery while booted into the ROM.
so yesterday i got tired of my ICS Rom. So, i went to recovery (TWRP) then recovered my old back up of stock. But since it had all the settings like when I flashed the rom, I Factory reseted it. But then suddenly it had deleted the whole stock rom! Couldn't go back. So my kindle was stuck on recovery loop over and over again. I got really impatient. So I started moving around then I mounted my Kindle to my computer and apped the ICS Rom that I used before. Then it flashed but it was still stuck on recovery. started moving more stuff on it, clicked the partitioning sd card and now I can't mount my kindle via Usb -___- and Then I new it was on Recovery fastboot. Please help! I Need this fixed. it deleted everything. and when I connected it to Adb shell, it says "Missing system/bin/sh"
Help me! i'm going to california on next week and I would like my kindle to work for me to play, listen to music, watch tv on it on the way.
Sorry for bad Grammar -___-
Do you have FFF? Is fastboot working at all? If so, have you tried fastboot oem format? (this will cause all your data to get lost), or booting/reflashing TWRP?
Dasanko said:
Do you have FFF? Is fastboot working at all? If so, have you tried fastboot oem format? (this will cause all your data to get lost), or booting/reflashing TWRP?
Click to expand...
Click to collapse
I Have FFF 1.4, have TWRP 2.1 and fastboot works. But Mounting USB don't work. In recovery it says (cannot mount /sdcard/ (Invalid argument).)
What's the output of
adb shell "parted /dev/block/mmcblk0 p"
?
Can you please explain what that means. i really don't now many of these commands. I need more like a Step-by-step. Like in ADB Shell, it says error: device not found
Luise. said:
Can you please explain what that means. i really don't now many of these commands. I need more like a Step-by-step. Like in ADB Shell, it says error: device not found
Click to expand...
Click to collapse
Means your KF is either not plugged in, or the drivers are wrong. You can't go on until the drivers are properly installed, if that's your issue. Take a look here: http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
Okay, Installed ADB Drives I think it now works it just tells me (exec '/system/bin/sh' failed: No such file or directory (2))
Can you type "fastboot getvar product" and then restart/plug in the KF?
Dasanko said:
Can you type "fastboot getvar product" and then restart/plug in the KF?
Click to expand...
Click to collapse
Yes i did and it says "Kindle"
Get TWRP (http://teamw.in/project/twrp2/79) and type "fastboot boot openrecovery-twrp-blaze-2.1.1.img" and see if you can get ADB working now.
Okay I already have TWRP Installed on 2.1.1 so Do I just go on Recovery and try to work adb shell on there instead of FFF Fastboot?
You just hinted at your ADB not working properly, try to fastboot boot into that TWRP to see if ADB works fine from it (I guess your drivers are good on the Device Manager, no errors or warnings showing up?). If it doesn't, then I guess the alternative is to try restoring the entire stock layout...
okay, I have TWRP, and when i have the usb connected to Kindle while its on Recovery, My Internet i use a Easytether so you can tell what android devices are connected and while my kindle is on recovery, The Easytether says My Kindle can connect, (but it really cant) and the ID Shows up that 0000005 number? but I Really Need My kindle to work! -__-
These issues have been fixed.
For future reference, this user was experiencing a combination of bad drivers and a corrupt sd card partition (rm 12 + mkpartfs primary fat32 start end + name 12 media).
The ADB issues were gone after fixing the drivers, without a need to reinstall TWRP.
I have a KF1 I had bought off ebay to try to repair so I know I was pretty much throwing money away but it was a rather cheap buy so I went ahead and bought it. The condition was stated "Freezes" but overall physical appearance was near mint.
On receiving the KF it would not power up, no power light, no logo, no nothing. So I plugged it in let it charge for a while. Still no light or any response from hitting or holding the power button. So I thought maybe it has a bad usb connection/battery. Took it apart and got my Multimeter out and measured voltage at the battery. 3.7V while plugged in. Took the battery out and measured voltage at the charge port solder connections, can't remember what the reading was (3.7 - 4.1 ?) but I knew the port was undamaged anyway. Pulled out my factory cable and plugged it into my computer. Still nothing. No signs of life at all.
At this point I went and did some research and found the "Firekit LiveUSB kit 1.1" followed instructions and after several attempts finally got it to boot into recovery by shorting usb bootmode trick and using the "usb_fix_parts_and_install_fff_twrp" script. However I could not do much else. It would not mount anything. No sdcard, no cache, no system, no nothing.
I did some more research and found the How To thread for fixing failure to mount xxxxx. Followed those steps but nothing worked. when trying to run parted on /dev/block/mmcblk0 it would always say "unable to stat device" or something like that. I could not do much with the recovery that was loaded with the firekit either so I thought I would download the newest recovery and try that with the "usb_fix_parts_and_install_fff_twrp" script. Once I got a newer recovery up I could use the file manager and look inside /dev/block/. There was no mmcblk0 in there at all. all that was there was a bunch of "loop" files and "ram" files. nothing else.
I did some more research and found the EMMC curruption fix by Hashcode. Tried running that several times but would always have problems using the mmc_utils. It would always hang. I thought I would try anyway to leave the mmc_utils vendor 0 and vendor 4 commands running for 5 minutes each and continue with the next steps. Moving from the next steps in that forum I was not able to get into recovery. it would always stay at the TWRP splash screen (although ADB commands would still work).
At this point I was ready to give up. I shut everything down pulled the battery out and was looking to see if I could find any info on the motherboard. When I put the battery back in it booted up the kindle and got stuck in a bootloop of the Yellow triangle (FFF) then kindle logo. Before this I always had to do the usb boot shorting method to get it to boot, so at least I'm getting somewhere. I then used fastboot commands to perform oem format and flash the xloader, fff1.4a bootloader, and recovery. succeeded on all of those so I thought I had got it working. Rebooted device and it would get to the FFF1.4a blue kindle logo, I could then hit the power button and select recovery. Unfortunately it would just sit there and not do anything.
I rebooted the device and did the fastboot command to boot the recovery image. Stuck at TWRP splash just like before. Rebooted device again and this time used fastboot commands to flash recovery followed by boot the same recovery image I just used to flash the recovery. Success! was able to get into TWRP. But I'm still stuck! lol. Can't do anything with it since it cannot mount any partition. mmcblk0 or any other partition does not exist in /dev/block/. Can't even mount the sdcard yet somehow adb push xxx /sdcard works and I can view sdcard inside the file manager in recovery. Can't wipe anything, can't install anything. Always get errors. I was able to copy recovery log to sd card from the advanced menu and pull it to my computer with adb pull.
So as to the reason I'm posting this. What now? lol. I'm at a loss for what to do.
Since you apparently have access to fastboot and can flash new bootloader and recovery images, try flashing these as well and see if it makes any difference...
http://www.adrive.com/public/fAJGAH/KF1.system.boot.PAC.zip
soupmagnet said:
Since you apparently have access to fastboot and can flash new bootloader and recovery images, try flashing these as well and see if it makes any difference...
http://www.adrive.com/public/fAJGAH/KF1.system.boot.PAC.zip
Click to expand...
Click to collapse
No luck. farthest I can get is booting into recovery after I do the fastboot commands:
fastboot flash recovery twrp2610.img
fastboot boot twrp2610.img
note: I have to flash recovery before being able to use the boot command, otherwise it stays at the TWRP splash and goes no further.
flashing the boot and system images report success although for some reason both boot and system images write in 1.23s exactly each and say OKAY. I cannot issue any reboot commands through fastboot, they all cause the kindle to reboot with no display. Have to hard reset to get back to the bootloader. Cannot boot the kernel either using fastboot (boot.img you gave me).
I'm not much of a Linux person at all, but is there some commands I can try to get a detail on all the hardware devices detected? Seems weird that it always fails to mount everything as well as not detecting any partitions or emmc.
Jeffjb said:
No luck. farthest I can get is booting into recovery after I do the fastboot commands:
fastboot flash recovery twrp2610.img
fastboot boot twrp2610.img
note: I have to flash recovery before being able to use the boot command, otherwise it stays at the TWRP splash and goes no further.
flashing the boot and system images report success although for some reason both boot and system images write in 1.23s exactly each and say OKAY. I cannot issue any reboot commands through fastboot, they all cause the kindle to reboot with no display. Have to hard reset to get back to the bootloader. Cannot boot the kernel either using fastboot (boot.img you gave me).
I'm not much of a Linux person at all, but is there some commands I can try to get a detail on all the hardware devices detected? Seems weird that it always fails to mount everything as well as not detecting any partitions or emmc.
Click to expand...
Click to collapse
There is one option that I know of. A user in the KF2 forums was able to mount the eMMC to his Linux computer, but it's slightly more advanced than entering a few commands in the terminal. If no one else chimes in with the appropriate amount of knowledge, it may be your only option.
http://forum.xda-developers.com/showthread.php?t=2391047
http://forum.xda-developers.com/showthread.php?p=44873922
The motherboard is the same on both the KF1 and KF2 so the instructions for setting it up would be the same as well. Once mounted, you may have to repartition/reformat the device accordingly.
soupmagnet said:
There is one option that I know of. A user in the KF2 forums was able to mount the eMMC to his Linux computer, but it's slightly more advanced than entering a few commands in the terminal. If no one else chimes in with the appropriate amount of knowledge, it may be your only option.
http://forum.xda-developers.com/showthread.php?t=2391047
http://forum.xda-developers.com/showthread.php?p=44873922
The motherboard is the same on both the KF1 and KF2 so the instructions for setting it up would be the same as well. Once mounted, you may have to repartition/reformat the device accordingly.
Click to expand...
Click to collapse
I have been following those threads closely for a while; will try that method once I get more practice soldering lol. I appreciate all the help.
As an update I ran the command : dmesg | grep mmc0
message returned was: mmc0: error -110 whilst initialising MMC card
I guess that means its dead? Anyone else see something like that?
I've been trying to install TWRP and Magisk to the Razer phone for upwards of 3 days now. I cannot get anything to flash through fastboot to the phone no matter what I try. At one point I even said screw it and tried flashing the stock boot image back over to re-lock my bootloader, but no luck, still won't flash.
I was originally following this tutorial here but during the flashing of the boot image it kept failing. Then I tried following the "foolproof" guide found here
I either ended up with the error of "no such file or directory" or "too many links" or "unable to identify current slot". Did a ton of Googling but ultimately came up with no solutions.
I have Android SDK and development studio installed. I have the google drivers installed. I have the Razer phone drivers installed and I have ADB and Fastboot installed.
I have all the files I need on the SD card, and when I'm flashing everything I have the files I need placed in the same folder as the ADB\Fastboot files.
I have my bootloader unlocked, developer mode on and USB debugging enabled. I am using a USB Type A to Type C cable as recommended (made by Anker if it matters). I've tried all 3 USB ports on my laptop. I've even disabled Antivirus.
I have flashed many Android devices in the past and none have given me such a headache as this one. I'm even more ticked off that I can't even get the factory boot image back over to re-lock the bootloader after now realizing that I can't install Netflix anymore because they wen't and blocked installations for Rooted android users (for whatever ridiculous reason).
I will say that for whatever reason that when I go to open command prompt by using the shift+right click I only get the option to use Windows Powershell, not Command Prompt. I also have to put a .\ in front of every command I send. I'm unsure why, but I found no work around for it.
I'd like to try to get the TWRP and Magisk installed. I'm sure I can force Netflix to install over to the phone using another method.
Open to any suggestions!
FireGuy0723 said:
I've been trying to install TWRP and Magisk to the Razer phone for upwards of 3 days now.
Click to expand...
Click to collapse
I feel for you as when things don't work, like someone says they do, it's frustrating. I personally wouldn't be doing everything through power shell but would instead press Windows Key+R to bring up the "Run" dialog box then type "cmd" for command prompt. Trying to restore "command prompt here" to Windows 10 seems stupidly hidden. I'm just not sure if using powershell is messing with your progress.
Second thought is that your Razer phone drivers may not be installed correctly. For me I spent days/hours with my main PC, I then tried another PC and got my phone flashed in minutes. What would happen is that I could send "adb" commands without issue but some of the "fastboot" commands were not working. So at the critical times when it's trying to flash the different portions of our phone, some of them were successful while the others were giving little errors here and there.
I spent a lot of time updating my adb and fastboot commands to newer ones because it seems every time you download someones resources you get a different version. Also the more phones you have owned the more times you have installed specific USB drivers for those phones and they are now hanging around messing things up. There are programs such as USBDeview that will allow you to uninstall those old drivers. For me I had HP drivers from an old tablet, OnePlus drivers, LG drivers, etc.
Munk0 said:
I feel for you as when things don't work, like someone says they do, it's frustrating. I personally wouldn't be doing everything through power shell but would instead press Windows Key+R to bring up the "Run" dialog box then type "cmd" for command prompt. Trying to restore "command prompt here" to Windows 10 seems stupidly hidden. I'm just not sure if using powershell is messing with your progress.
Second thought is that your Razer phone drivers may not be installed correctly. For me I spent days/hours with my main PC, I then tried another PC and got my phone flashed in minutes. What would happen is that I could send "adb" commands without issue but some of the "fastboot" commands were not working. So at the critical times when it's trying to flash the different portions of our phone, some of them were successful while the others were giving little errors here and there.
I spent a lot of time updating my adb and fastboot commands to newer ones because it seems every time you download someones resources you get a different version. Also the more phones you have owned the more times you have installed specific USB drivers for those phones and they are now hanging around messing things up. There are programs such as USBDeview that will allow you to uninstall those old drivers. For me I had HP drivers from an old tablet, OnePlus drivers, LG drivers, etc.
Click to expand...
Click to collapse
I've been messing with it today a bunch. I am back to following the "foolproof" guide and this time I have completely uninstalled all my old drivers for anything android or USB or ADB related and reinstalled everything.
All commands work, I am using command prompt now.
What I am getting hung up on now is even after pushing all three files to the SD card, I run the command "fastboot flash boot twrp-3.2.1-0-cheryl.img && fastboot reboot" and it bounces back with " Failed: Write to device failed (no such file or directory)"
I've double checked the file names numerous times. I have no idea what I am doing wrong now. I have tried the command "fastboot boot twrp-3.2.1-0-cheryl.img" as stated in the other tutorial and it bounces back with "failed to identify current slot".
So I'm making progress at least. I'm trying to follow the first set of instructions listed in the fool proof guide but still no luck. I also tried the "clean method" listed below on that guide and that one doesn't work either. Apparently the Fool Proof guide thinks I'm a fool!
FireGuy0723 said:
What I am getting hung up on now is even after pushing all three files to the SD card, I run the command "fastboot flash boot twrp-3.2.1-0-cheryl.img && fastboot reboot" and it bounces back with " Failed: Write to device failed (no such file or directory)"
Click to expand...
Click to collapse
I believe that when you run "fastboot flash boot twrp-3.2.1-0-cheryl.img" you are pushing the file called "twrp-3.2.1-0-cheryl.img" that is sitting on your PC's C: or whichever drive you are currently sitting in to the Razer Phone. So make sure the file is in the same directory as where you are running that command. This will then transfer it to the Razer and will reboot into TWRP.
But after you reboot into TWRP you will want to flash the version you have sitting within your SD card to the "recovery" partition. That way it is permanent.
Munk0 said:
I believe that when you run "fastboot flash boot twrp-3.2.1-0-cheryl.img" you are pushing the file called "twrp-3.2.1-0-cheryl.img" that is sitting on your PC's C: or whichever drive you are currently sitting in to the Razer Phone. So make sure the file is in the same directory as where you are running that command. This will then transfer it to the Razer and will reboot into TWRP.
But after you reboot into TWRP you will want to flash the version you have sitting within your SD card to the "recovery" partition. That way it is permanent.
Click to expand...
Click to collapse
I was finally able to get the phone to accept a flash! I ended up saying screw it and dug a old laptop out, fresh install of windows and installed all the proper drivers onto it.
It worked almost flawlessly. It was able to correctly send the twrp.img file and the phone was able to boot into twrp which is about as far as I got. As it was attempting to load twrp it would "crash" the screen would flash twice and try rebooting back to TWRP.
What ended up happening was it got stuck in a boot loop trying to boot into TWRP. (I haven't even installed TWRP.zip yet, just tried booting the .img file).
I couldn't get the phone to boot to the system anymore. I thought I had a nice $600 paperweight on my hands.
I finally got the phone to go back into the boot loader and flashed all the factory stuff back on and relocked the bootloader. So right now I'm 100% back to stock.
I'm not sure what went wrong in the boot up of the twrp.img file. I'd like to try again but I'm kinda getting sick of wiping the phone Everytime something goes wrong.
Sent from my Phone using Tapatalk
I'm wanting to get TWRP / Magisk on my Razer too, but see too many bootloop stories after attempting to flash TWRP.... making me nervous ha ha.
Sorry, not much help, but hope you get it sorted...
Peace
chris5s said:
I'm wanting to get TWRP / Magisk on my Razer too, but see too many bootloop stories after attempting to flash TWRP.... making me nervous ha ha.
Sorry, not much help, but hope you get it sorted...
Peace
Click to expand...
Click to collapse
I had mine in boot loop, I was able to get it out pretty easily. If your able to get the phone into the bootloader (I did using a fastboot command while it was in a boot loop) you can just execute the script provided by Razer and it does the rest. Took about 10 minutes and I had factory everything back on the phone. Relocked the bootloader after and done, phone fixed.
Sent from my Phone using Tapatalk
FireGuy0723 said:
I had mine in boot loop, I was able to get it out pretty easily. If your able to get the phone into the bootloader (I did using a fastboot command while it was in a boot loop) you can just execute the script provided by Razer and it does the rest. Took about 10 minutes and I had factory everything back on the phone. Relocked the bootloader after and done, phone fixed.
Sent from my Phone using Tapatalk
Click to expand...
Click to collapse
In my case I actually had to flash the stock boot.img from the May 2018 stock OS. Then I was able to use Razers guide to flash stock again. I haven't locked my bootloader since I still want to give it a try again. But I want to find a reliable way of rooting and then unrooting in case I want to do so in the feature.
So far I haven't found said documentation.
Installed Magisk v17.1 via TWRP loaded in fastboot boot (not fastboot flash boot ie not permanently installed) and so far all seems well. No boot loops when restarting...
Peace