Develop Bugs

[Help] Reviving a dead KF

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?

Trying to fix an M8

So I randomly have a corrupted data partition on my M8. I'm unlocked and S-off but was only running a rooted stock ROM.
What happened:
I went to go turn my screen on and hitting the power button did nothing. I thought maybe the battery was dead. Plugged the phone in and the battery charging screen came up. It said the battery was at 52%. I ended up holding the power button for awhile and it finally powered on. It took forever to load and I'm presented with this screen. It doesn't matter what password I put in, I always get this screen next. I can get into recovery but, again, it takes FOREVER to load and won't mount the userdata partition.​
Here is what I've tried so far:
I've tried wiping through recovery but /data won't mount.
I've tried to flash a rom.zip through bootloader but I can't get it to RUU mode. The device just restarts normally when I run fastboot oem rebootRUU.
I've tried to run a RUU from my PC but it fails for the same reason as above. I'm thinking the RUU tries to run the fastboot OEM rebootRUU command because it just restarts like normal.
I've tried fastboot flashing userdata.img. That fails.
I've tried formatting with mkfs.
These guys are recovering OnePlus Ones through a debugging port. I'm trying to figure out if I might be able to do the same thing since the One M8 and the OnePlus One have a very similar chipset. I have ZERO experience with any of this so I'm looking for a little help. Unfortunately the OnePlus guys aren't responding to my PM's.
Thanks for any help!

TMartin said:
So I randomly have a corrupted data partition on my M8. I'm unlocked and S-off but was only running a rooted stock ROM.
What happened:
I went to go turn my screen on and hitting the power button did nothing. I thought maybe the battery was dead. Plugged the phone in and the battery charging screen came up. It said the battery was at 52%. I ended up holding the power button for awhile and it finally powered on. It took forever to load and I'm presented with this screen. It doesn't matter what password I put in, I always get this screen next. I can get into recovery but, again, it takes FOREVER to load and won't mount the userdata partition.​
Here is what I've tried so far:
I've tried wiping through recovery but /data won't mount.
I've tried to flash a rom.zip through bootloader but I can't get it to RUU mode. The device just restarts normally when I run fastboot oem rebootRUU.
I've tried to run a RUU from my PC but it fails for the same reason as above. I'm thinking the RUU tries to run the fastboot OEM rebootRUU command because it just restarts like normal.
I've tried fastboot flashing userdata.img. That fails.
I've tried formatting with mkfs.
These guys are recovering OnePlus Ones through a debugging port. I'm trying to figure out if I might be able to do the same thing since the One M8 and the OnePlus One have a very similar chipset. I have ZERO experience with any of this so I'm looking for a little help. Unfortunately the OnePlus guys aren't responding to my PM's.
Thanks for any help!
Click to expand...
Click to collapse
Okay.
First, you can get into recovery, correct? That's how you should try to flash the ROM.zip
Can you boot into bootloader? If so, post what it says next to OS ( that's your firmware version) and I'll see if I can find an RUU.zip that you can flash through hboot.
If OS is blank (it's caused by older versions of TWRP), get into ADB/fastboot, and issue the command fastboot getvar all, then post the readout here. Delete the serial no. and IMEI from the readout for your own safety.

xunholyx said:
Okay.
First, you can get into recovery, correct? That's how you should try to flash the ROM.zip
Can you boot into bootloader? If so, post what it says next to OS ( that's your firmware version) and I'll see if I can find an RUU.zip that you can flash through hboot.
If OS is blank (it's caused by older versions of TWRP), get into ADB/fastboot, and issue the command fastboot getvar all, then post the readout here. Delete the serial no. and IMEI from the readout for your own safety.
Click to expand...
Click to collapse
I can get into TWRP but it won't mount the data partition. Are you saying I should try flashing another ROM the normal way through TWRP or try the sideload option? I tried to fastboot flash stock recovery. It says it worked but then continues to boot to TWRP.
I can get into bootloader. I'm pretty sure it's a 4.16.401.x ROM but I'll have to double check when I get home. I've tried to flash stock everything but it you know how it restarts through the process? When it restarts, it seems to want to restart to OS.
I'm about 99% sure the OS is there because it boots into Android but only gets me to the "Decrypt storage" screen.

Find 7 HARD brick after latest CM12 nightly

I think I might be screwed.
I've been updating with CM12 nightlies about every third of sixth one since the first one and never had a problem. Until today.
Downloaded the 9/21 CM 12 nightly after running my weekly Titanium backup.
Rebooted into TWRP recovery, flashed the zip file for CM12, wiped cached and rebooted. Except the phone rebooted into fastboot. Uh oh.
Phone will no only boot into fastboot, with just the power button = fastboot, power+vol up = fastboot, power+vol down = fastboot.
Plugged phone into computer with USB, PDANet recognizes the phone as having been connected but won't run because adb.exe is installed. Phone shows up in Device Manager with correct driver, listed as Android Device. Phone does NOT show up in Windows 7 Explorer. ADB does NOT work because it doesn't list any devices.
I can run fastboot and all fastboot commands from a command prompt. I've flashed several new recovery images but still cannot reboot into recovery.
I've deleted and updated drivers over and over.
I've pulled battery, SIM card, SD card in every combination I can think of.
In all cases I can only boot to fastboot.
I LOVED this phone! My best phone ever!
Any ideas?
Thanks,
-AJ

After 7 hours of fighting it, I may have posted too soon. I kept scouring threads and found a reference to run oem unlock in fastboot. That seemed to work. That got me into recovery and if I can get into TWRP I'm confident that I can fix or rebuild/reinstall everything back to good. So let's say this is solved. But if anyone else has this problem, try the oem unlock..

Starting to pull my hair out over flashing the Razer Phone

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

Pixel 2 No OS Installed, No Recovery, Limited Bootloader use

Recently I had some trouble with my pixel 2 as my magisk root had magically disappeared, because of this I decided to fix it and re-flash magisk using fastboot to flash the modified boot.img. Since then my Pixel 2 XL wont turn on, I attempted to also flash twrp as well but was met with only a frozen splash screen. Since then I've tried to re-flash the entire OS that was downloaded from the google database and yes for the right version (taimen). I've auto tried to restore it using the android flash tool available through google online as well with limited success.
So here's my current situation. Right now turning on the phone takes me straight to the bootloader screen, attempting to hold volume up or anything other button combinations does nothing but take me to the bootloader screen. Attempting to use the android flash tool now turns the phone off the instant the pc detects it, trying to flash manually with fastboot (the latest version yes) does not work and even a simply "fastboot devices" returns "???????????? fastboot" which then reboots the phone. I'm kinda at a loss of what to do here, i've had softbricks on other phones before but have always managed to fix it one way or another but this one has sadly beaten me
p.s. I've already tried 3 different cables

tcxufatime said:
Recently I had some trouble with my pixel 2 as my magisk root had magically disappeared, because of this I decided to fix it and re-flash magisk using fastboot to flash the modified boot.img. Since then my Pixel 2 XL wont turn on, I attempted to also flash twrp as well but was met with only a frozen splash screen. Since then I've tried to re-flash the entire OS that was downloaded from the google database and yes for the right version (taimen). I've auto tried to restore it using the android flash tool available through google online as well with limited success.
So here's my current situation. Right now turning on the phone takes me straight to the bootloader screen, attempting to hold volume up or anything other button combinations does nothing but take me to the bootloader screen. Attempting to use the android flash tool now turns the phone off the instant the pc detects it, trying to flash manually with fastboot (the latest version yes) does not work and even a simply "fastboot devices" returns "???????????? fastboot" which then reboots the phone. I'm kinda at a loss of what to do here, i've had softbricks on other phones before but have always managed to fix it one way or another but this one has sadly beaten me
p.s. I've already tried 3 different cables
Click to expand...
Click to collapse
https://forum.xda-developers.com/pixel-2-xl/help/pixel-2-bricked-t3889296 on the last page there are possible solutions to try. Have you tried a different port?

Also, as you can use fastboot in the bootmenu, download the twrp.img (link) to your adb.exe directory and use the adb shell to type 'fastboot boot twrp.img'.
If that works you could go to the reboot option and change the A/B slot to the other version used.
Through twrp - tools, you can also select adb mode to allow your PC adb shell to use 'adb sideload ota.zip'.
Use the ota.zip version of your current version which you download here.