Database Develop

Installing KK on KFHD, too confusing, help appreciated

Hey guys, I've got a KFHD 7" running system 7.4.9 and I was able to root it today successfully and I would like to install the LiquidSmotth 4.4.4 ROM on it.
The problem that I'm having is that I need a recovery likw TWRP 2.7+ but the instructions are way too complicated and they mention a 2nd bootloader which requires a special cable, what the hell, is it that complex?
I appreciate if anyone can point out a more human way of getting TWRP 2.7 or CWM for KK on my Kindle v 7.4.9.
Thanks!

theplagueisback said:
Hey guys, I've got a KFHD 7" running system 7.4.9 and I was able to root it today successfully and I would like to install the LiquidSmotth 4.4.4 ROM on it.
The problem that I'm having is that I need a recovery likw TWRP 2.7+ but the instructions are way too complicated and they mention a 2nd bootloader which requires a special cable, what the hell, is it that complex?
I appreciate if anyone can point out a more human way of getting TWRP 2.7 or CWM for KK on my Kindle v 7.4.9.
Thanks!
Click to expand...
Click to collapse
Alright. Let's get you started.
First of all,use the Kindle fire system restore tool to downgrade to 7.4.6 OR 7.2.3. Either will do. Next,root it using the Bin4ry tool and download the TWRP 2.7.0.0 image with the freedom boot image that is corresponding to your software version. Then,flash them using FireFlash or Flasher or manual method.
Bingo.
Sent from my device running CyanogenMod 11

SafinWasi said:
Alright. Let's get you started.
First of all,use the Kindle fire system restore tool to downgrade to 7.4.6 OR 7.2.3. Either will do. Next,root it using the Bin4ry tool and download the TWRP 2.7.0.0 image with the freedom boot image that is corresponding to your software version. Then,flash them using FireFlash or Flasher or manual method.
Bingo.
Sent from my device running CyanogenMod 11
Click to expand...
Click to collapse
Hi man, I'm getting "No such file or directory" when I try to reboot in fastboot mode, here's the output:
Code:
C:\AndroidSDK\sdk\platform-tools>adb devices -l
List of devices attached
D025A0A024121UQQ device
C:\AndroidSDK\sdk\platform-tools>adb shell su -c "reboot bootloader"
[-] exec: No such file or directory
C:\AndroidSDK\sdk\platform-tools>
When I ran that command on the Kindle I got a root prompt and I allowed it.
Under the device manager I have listed: N2A ADB Mode / Kindle ADB Mode | HD 7

theplagueisback said:
Hi man, I'm getting "No such file or directory" when I try to reboot in fastboot mode, here's the output:
Code:
C:\AndroidSDK\sdk\platform-tools>adb devices -l
List of devices attached
D025A0A024121UQQ device
C:\AndroidSDK\sdk\platform-tools>adb shell su -c "reboot bootloader"
[-] exec: No such file or directory
C:\AndroidSDK\sdk\platform-tools>
When I ran that command on the Kindle I got a root prompt and I allowed it.
Under the device manager I have listed: N2A ADB Mode / Kindle ADB Mode | HD 7
Click to expand...
Click to collapse
Turn it off,type in this:
Code:
fastboot -i 0x1949 getvar product
and plug it in.

SafinWasi said:
Turn it off,type in this:
Code:
fastboot -i 0x1949 getvar product
and plug it in.
Click to expand...
Click to collapse
The problem is, I don't have a fastboot cable and I would like to try to enter fastboot without buying that cable if possible.

SafinWasi said:
Turn it off,type in this:
Code:
fastboot -i 0x1949 getvar product
and plug it in.
Click to expand...
Click to collapse
Ok, I did that and it kept saying "aiting for device".
i'm going to try again, hold on.

theplagueisback said:
The problem is, I don't have a fastboot cable and I would like to try to enter fastboot without buying that cable if possible.
Click to expand...
Click to collapse
This command will work with a normal cable if you have root.

SafinWasi said:
This command will work with a normal cable if you have root.
Click to expand...
Click to collapse
So I ran it again and it kept says "waiting for device", my Kindle is rooted with "Mulai Root" and I used root checker to confirm that it is rooted.
I turned the Kindle off.
I issued the command on the command prompt.
The command prompt said "waiting for device".
I plugged in the USB cable.
The Kindle turned on.
The Kindle booted all the way to the launcher.
The command prompt kept saying "waiting for device".
I would appreciate any more ideas.
Thank you!

theplagueisback said:
So I ran it again and it kept says "waiting for device", my Kindle is rooted with "Mulai Root" and I used root checker to confirm that it is rooted.
I turned the Kindle off.
I issued the command on the command prompt.
The command prompt said "waiting for device".
I plugged in the USB cable.
The Kindle turned on.
The Kindle booted all the way to the launcher.
The command prompt kept saying "waiting for device".
I would appreciate any more ideas.
Thank you!
Click to expand...
Click to collapse
Odd... can you use FireFlash?

SafinWasi said:
Odd... can you use FireFlash?
Click to expand...
Click to collapse
Yes, I just installed and ran it using root access. But I'm running system 7.4.9, what should I do now with the app open to downgrade?
The program states "Warning: current bootloader is not kfhd7-u-boot-prod-7.2.3.bin"

Can you help me using FireFlash to downgrade?
Thanks

The culprit was the chinese or vietnamise root, I rooted again using qemu and now I was able to boot into fastboot mode.

I hae a big problem, I sued the Kindle Fire First Aid to restore to 7.2.3 and now my kindle stays on the boot logo.
How can I restore it now?
EDIT: Never mind, it actually booted up.

Hey, I managed to get downgraded and now I'm on this part:
TWRP 2.7.0.0 image with the freedom boot image that is corresponding to your software version.
I'm confused if I should install a 2nd-bootloader or not, I installed fire flash already, let me know if you can help me with a link with the next steps to perform.
Thanks

I think I kind of managed to do it, the problem now is that TWRP loads but the ROM I flashed didn't boot (Liquid Smotth 4.4.4), I'm going to start a new thread.
Thanks

[Q] Memopad 7 170C root fails. help!

I'm trying too root my Asus memo pad 7 (170C), I've tried EVERY method, using KingoRoot, SuperOneClick, Frameroot, motochopper. None of them worked.
So I decided to do the rooting stuff myself, first I tried on Windows 8, the fastboot driver was not recognized, I installed the PdaNet, It recognizes the device now, the problem is when I run "fastboot oem unlock" or "fastboot oem unlock0x0b05" (ASUS VendorID), it returns : "FAILED (remote: unknown OEM command)"
I enter bootloader with "adb reboot bootloader" or by pressing Volume Up and Power.
I have also tried in Ubuntu 14.04, It doesn't even recognize the device in fastboot, and yes I run fastboot as root, still no chance "fastboot devices" returns nothing, and "fastboot oem unlock" returns "Waiting for device"
I did run "usbls" command, and it was clear that the OS has recognized the tablet, but why the fastboot does not?
Here is some information of my specs: ASUS MemoPad 7 (170C) Windows 8.1 64bit AND/OR Ubuntu 14.04
Bootloader: DroidBoot Provision Os, DroidBoot Ver: WW_MeMO_Pad-11.2.3.28-20141230 IFWI Version: 64.25
PLEASE somebody save my life as I'm stuck with it for a very long time!

arman92 said:
I'm trying too root my Asus memo pad 7 (170C), I've tried EVERY method, using KingoRoot, SuperOneClick, Frameroot, motochopper. None of them worked.
So I decided to do the rooting stuff myself, first I tried on Windows 8, the fastboot driver was not recognized, I installed the PdaNet, It recognizes the device now, the problem is when I run "fastboot oem unlock" or "fastboot oem unlock0x0b05" (ASUS VendorID), it returns : "FAILED (remote: unknown OEM command)"
I enter bootloader with "adb reboot bootloader" or by pressing Volume Up and Power.
I have also tried in Ubuntu 14.04, It doesn't even recognize the device in fastboot, and yes I run fastboot as root, still no chance "fastboot devices" returns nothing, and "fastboot oem unlock" returns "Waiting for device"
I did run "usbls" command, and it was clear that the OS has recognized the tablet, but why the fastboot does not?
Here is some information of my specs: ASUS MemoPad 7 (170C) Windows 8.1 64bit AND/OR Ubuntu 14.04
Bootloader: DroidBoot Provision Os, DroidBoot Ver: WW_MeMO_Pad-11.2.3.28-20141230 IFWI Version: 64.25
PLEASE somebody save my life as I'm stuck with it for a very long time!
Click to expand...
Click to collapse
Because these Asus tablets use Intel processors, I do not believe that fastboot works. You did not indicate that you had tried the RootZenFone tool in your post above. See this thread:
http://forum.xda-developers.com/memo-pad-7/help/me170cx-k01a-root-t2985421
I have rooted two of these tablets using this method, and it worked perfectly on both of them.

CYoung234 said:
Because these Asus tablets use Intel processors, I do not believe that fastboot works. You did not indicate that you had tried the RootZenFone tool in your post above. See this thread:
http://forum.xda-developers.com/memo-pad-7/help/me170cx-k01a-root-t2985421
I have rooted two of these tablets using this method, and it worked perfectly on both of them.
Click to expand...
Click to collapse
Yes I did try the RootZenFone tool, but it didn't work either.
Unfortunately I forgot to "Forget the wireless networks" (I just disabled the WiFi), and the RootZenFone failed rooting my device...
Is there any way to get it work again?

HELP ME!!
Anybody got an idea?
Would it be helpful if I Re-Flash the Asus official ROM to my tablet and start over? If it is, how can I do that?
PLEASE somebody help me!

arman92 said:
Anybody got an idea?
Would it be helpful if I Re-Flash the Asus official ROM to my tablet and start over? If it is, how can I do that?
PLEASE somebody help me!
Click to expand...
Click to collapse
Yes, you can go into bootloader mode and restore the factory rom, which will likely downgrade you to 4.3 again. Then you can do the OTA update and use the RootZenFone again. This time, remember to follow the instructions EXACTLY, and you should do fine.
Edit: I do not have the two I set up right now, but they both were visible to my desktop in fast boot mode. They responded to fast boot device. Beyond that, I never tried fastboot oem unlock. Did you try just typing fastboot to see the comand set? You might try that.

Done! I'm Root
CYoung234 said:
Yes, you can go into bootloader mode and restore the factory rom, which will likely downgrade you to 4.3 again. Then you can do the OTA update and use the RootZenFone again. This time, remember to follow the instructions EXACTLY, and you should do fine.
Edit: I do not have the two I set up right now, but they both were visible to my desktop in fast boot mode. They responded to fast boot device. Beyond that, I never tried fastboot oem unlock. Did you try just typing fastboot to see the comand set? You might try that.
Click to expand...
Click to collapse
I've followed the instructions in this page : http://forum.xda-developers.com/android/help/instructions-reviving-me170c-me170cx-t3017466
I successfully made it flash the Asus official ROM, but every time the freaking "Unfortunately Asus Demo has stopped" showed up.
I tried 4 different ROMs, still I got the error. I tried the RootZenFone-1.4.6r.apk everytime, no chance. The rooting process was interrupted by the "Unfortunately Asus Demo has stopped"
Then I figured out that when the tablet is connected to a power source (e.g. USB charge or PC), the error come up more frequent, so I disconnected the USB cable and tried the RootZenFone again, after a fresh ROM recovery, this time it successfully finished the rooting process. Huurrraaaay!!
So for every one else that has the same issue: just disconnect the USB cable and you are good to go!
Thanks for everyone that helped.

Stuck in Teamwin after system restore

I just gave my KF HD 7" to my friend and he wanted me to set it back up as a KF since i had Cyanogen Mod cm-12.1-20160126-NIGHTLY installed on it but haven't used it in a while (read 1-2 years). He was messing around with it before i could get to it and thought hitting Restore to Factory settings would fix it. The device is now stuck on a flashing teamwin logo screen and wont go any further no matter what i've tried. My computer wont recognize the kindle to let me in from cmd so i've reached the limits of my modding knowledge. Could someone please point me in the right direction so i can fix this for him.

If you're running Windows, you should install the Kindle drivers from this post. Also run the nifty 15 second ADB installer found here on XDA, and answer Yes to the "install ADB & fastboot" and "install ADB system wide" questions, and no to the "install device drivers" question. Reboot when the installations are completed, then power off the kindle completely, type fastboot -i 0x1949 getvar product into a command prompt/terminal on your PC, and plug in the kindle (preferably with a fastboot cable/adapter if you have one) when you see <waiting for device>. If you get a string beginning with "tate", then fastboot is working properly. At that point, you should reflash TWRP and the freedom-boot and 2nd bootloader images as directed in Hashcode's thread. (download the files in Step 2, then follow steps 5 and 6 to flash TWRP and the other files.)

Or once you get fastboot working you could use the SRT tool to flash it back to stock with root.

install the Kindle drivers from this post.
Downloaded but installation fails every time with no given reason so i tried a universal adb driver to no avail.
run the nifty 15 second ADB installer found here
Did this with no problems.
I started the fastboot in cmd and it says "waiting for device" but when i plug the kindle in after turning it off completely (i think, best i can do is hold power button till screen turns off and stops flashing teamwin) yet still cant seem to find it. Any suggestions?

TheN3wguy said:
install the Kindle drivers from this post.
Downloaded but installation fails every time with no given reason so i tried a universal adb driver to no avail.
run the nifty 15 second ADB installer found here
Did this with no problems.
I started the fastboot in cmd and it says "waiting for device" but when i plug the kindle in after turning it off completely (i think, best i can do is hold power button till screen turns off and stops flashing teamwin) yet still cant seem to find it. Any suggestions?
Click to expand...
Click to collapse
Are you running Windows 8, 8.1, or 10?
Sent from my Amazon Jem using XDA Labs

monster1612 said:
Are you running Windows 8, 8.1, or 10?
Click to expand...
Click to collapse
Oh god sorry i thought i had said im running windows 10

TheN3wguy said:
Oh god sorry i thought i had said im running windows 10
Click to expand...
Click to collapse
No worries. All you need to do to get the fastboot drivers to install is to follow these instructions to temporarily disable driver signature enforcement. Once you've done that, install the drivers and reboot. After that, fastboot should recognize the kindle.

Above steps worked and KF is now working correctly thanks!

monster1612 said:
If you're running Windows, you should install the Kindle drivers from this post. Also run the nifty 15 second ADB installer found here on XDA, and answer Yes to the "install ADB & fastboot" and "install ADB system wide" questions, and no to the "install device drivers" question. Reboot when the installations are completed, then power off the kindle completely, type fastboot -i 0x1949 getvar product into a command prompt/terminal on your PC, and plug in the kindle (preferably with a fastboot cable/adapter if you have one) when you see <waiting for device>. If you get a string beginning with "tate", then fastboot is working properly. At that point, you should reflash TWRP and the freedom-boot and 2nd bootloader images as directed in Hashcode's thread. (download the files in Step 2, then follow steps 5 and 6 to flash TWRP and the other files.)
Click to expand...
Click to collapse
it doesn't say my device when i connected it helppp
but i can get fastboot working by adb reboot bootloader but i don't know what to do after

AndroidLove231 said:
it doesn't say my device when i connected it helppp
but i can get fastboot working by adb reboot bootloader but i don't know what to do after
Click to expand...
Click to collapse
Once you're in fastboot mode (rebooting into the bootloader from Android, for example), does fastboot -i 0x1949 devices show that the Kindle's connected?

Unable to access TWRP or restore to stock

Hello everyone,
I have a MotoG 2014 titan XT1064. It was rooted, bootloader unlocked with CyanogenMod 13 running. But it was crashing all the time, so I decided to change its ROM. I couldn't do it though. When I go to the fastboot menu and try to access the recovery option, it's stuck at the blue teamwin screen. For some reason when I try the normal powerup it doesn't boot anymore, everything I see is a "blue Motorola logo powered by android".
Before it bricked I installed a TWRP app to no avail. Also I've tried installing TWRP via fastboot flash recovery 3.1.1-0 img. First there's a msg "(bootloader) has-slot:recovery: not found" then it says sending recovery, writing recovery OKAY. I downloaded the stock firmware for my version (XT1064_TITAN_RETUAWS....xml). It happens the same thing. When I try to fastboot flash the firmware, it's the same as when I try flashing the TWRP: "has-slot:recovery/boot/system/logo...: not found", then OKAY msgs.
I've no glue of what's going on.
Additional information:
- I use debian stretch
- The cellphone is charging alright
- Fastboot recognizes it but adb doesn't
Thanks a lot anyway! Any help is appreciated

Anyone? I'm still searching for help. Is it hopeless? Do I need some hardware intervention?

Install windows on a virtual machine and run the process

marcelo1998 said:
Install windows on a virtual machine and run the process
Click to expand...
Click to collapse
Thanks for the reply. I have Windows XP on a VirtualBox. So I install adb and fastboot than run the .bat file? Is that it?
Agradeço a ajuda!

imbassahy said:
Thanks for the reply. I have Windows XP on a VirtualBox. So I install adb and fastboot than run the .bat file? Is that it?
Agradeço a ajuda!
Click to expand...
Click to collapse
Yes that's right

fastboot errors, Can't flash oem - FAILED (remote: 'unknown command') [Ubuntu Linux]

I've basically two questions: First my concrete problem and second "how can I debug problems with the horrible platformTools"? Maybe you can help me solve both.
1. fastboot fails with "unknown command"
I've sucessfully build AOSP Android 10 via the instructions from Sonys Open Devices. But I'm currently stuck at the last step - flashing the images on my phone. I've successfully put the device in fastboot mode (LED is glowing blue, and "fastboot devices" lists a connected device).
But sending the vendor image fails with an "unknown command"-error
Code:
./fastboot flash oem SW_binaries_for_Xperia_Android_10.0.7.1_r1_v3_yoshino.img
Sending 'oem' (211868 KB) FAILED (remote: 'unknown command')
I'm using the newest platformTools on Ubuntu Linux 18.04. My bootloader is unlocked and I've already installed other Android Versions in the past on the phone. Any idea whats going on here and how to fix it?
2. How to debug it myself?
And as a more general approach, as some problems with fastboot/adb appear to occure almost everytime I try to use it: Any tipps on how to find the cause of the problem myself? Any logs which I should check? Any known problems which I should be aware of?

AllesMeins said:
./fastboot flash oem SW_binaries_for_Xperia_Android_10.0.7.1_r1_v3_yoshino.img
Click to expand...
Click to collapse
EDIT: Does THIS help?

SXUsr said:
EDIT: Does THIS help?
Click to expand...
Click to collapse
Unfortunaly not - I already had a pretty recent version, but did an update to the newest nevertheless. Problem stays the same.
I'm thinking about trying to flash the other parts first but I'm still reluctant, because I'm afraid that I might end up without a way to go back, if fastboot doesn't work reliably.

AllesMeins said:
I'm thinking about trying to flash the other parts first but I'm still reluctant, because I'm afraid that I might end up without a way to go back, if fastboot doesn't work reliably.
Click to expand...
Click to collapse
Try it, you can always rely on EMMA to go back. I'll happily test if you want?

SXUsr said:
Try it, you can always rely on EMMA to go back. I'll happily test if you want?
Click to expand...
Click to collapse
No luck... Tried it for boot, system, vendor and everytime the same error. But it seems to be a Linux-Problem. I tried it with my flatmates Windows 10 PC and there everything worked. But of cause this is no solution for the future. Any ideas why the phone doesn't understand the commands, when coming from my system?

AllesMeins said:
Any ideas why the phone doesn't understand the commands, when coming from my system?
Click to expand...
Click to collapse
I don't, but I assume you've set up everything properly. Can the PC see the phone under the adb devices command?

SXUsr said:
I don't, but I assume you've set up everything properly. Can the PC see the phone under the adb devices command?
Click to expand...
Click to collapse
In normal mode: yes.
$ ./adb devices
List of devices attached
BH906VHH9E device
Click to expand...
Click to collapse
In fastboot mode no - but there it is listed under fastboot devices

I wish I could be of more help, I really want to see 10 on this phone.

I managed to flash it on Windows, but version is 5 , but got loopboot afte reinstalling PIxel Experience Plus.
https://forum.xda-developers.com/xperia-xz1-compact/help/pixel-experience-10-0-plus-how-to-t4077747