Database Develop

KFHD System.img Recovery Tool

THIS IS NOT A CUSTOM RECOVERY!!!
KINDLE FIRE HD 8.9 ONLY!!! USE AT YOUR OWN RISK!!
This is an update to the KFHD_SRTool, now for use with the Kindle Fire HD 8.9
This is ONLY for use with 8.9" models, not for use with 7" unless you replace system.img with your own backup.
A factory cable is not needed to enable fastboot on this model. Even if the device is in a loop and ADB can not recognize it. I have personally put my device in a loop to confirm it works. To enable fastboot use option 1 from the tool
Instructions:
1. Download and unzip the tool of your choice from the link below (I have confirmed you can downgrade from 8.1.4 to 8.1.3)
2. Run SR Tool
That's it, wait for the tool to finish. Be patient this can take a few minutes. To exit fastboot use option 6 or hold down the power button for 10-20 seconds. When you reboot the first time it may seem to loop once but this is normal and will boot up. Once again be patient, especially if you chose to erase cache and userdata. The system needs to rebuild those partitions. Hope this helps some of you in the community. Again sorry for the size of the download, this is why I made this a separate tool instead of combining it with the HD7 version.
Downloads:
KFHD_SRTv2.1- 8.1.4
KFHD_SRTv2.0- 8.1.3
KFHD_SRTv1.3- 8.1.2
UPDATES:
12-24-12
System v8.1.4
12-12-12:
System backup from v8.1.3 KFHD_SRTool_v2.0
Option menu has changed
New options: Install of GoogleServicesFramework.apk, enable fastboot with device powered on or off.
Option 4 removed due to new option of enable fastboot
DOWNGRADE:
I no longer own this device so I cannot make backups of newer system versions, for the time being here are instructions for downgrading to 8.1.4:
1.) Download boot and recovery imgs(these are backups from 8.1.4) from this LINK and place in the folder where you have access to fastboot or inside the KFHD_SRTool_v2.1 folder
2.) Use KFHD_SRTool_v2.1 to flash system.img.
3.) Erase userdata and cache
4.) Open a cmd prompt from the folder where you placed the previously downloaded .img's.
Use these cmds:
Code:
fastboot -i 0x1949 flash boot boot.img
fastboot -i 0x1949 flash recovery recovery.img
5- Reboot.
Thanks to mdblaze for bringing to my attention that a factory cable is not needed with this device
Again Thanks to kinfauns for the how to on backing up and restoring system software.

Thank you for adding the 8.9 to your tool onemeila. I appreciate the work you've done.
I can confirm this does work to fix an hd stuck on the kindle fire logo. Thanks again.

I can't download it :/
When I click "download anyway" it just refreshes the page.

FroyoShark said:
I can't download it :/
When I click "download anyway" it just refreshes the page.
Click to expand...
Click to collapse
Don't know what is going on there. I just went to the link and had no problem. Try again and let me know. If it doesn't work pm me and I'll send you another link.

onemeila said:
Don't know what is going on there. I just went to the link and had no problem. Try again and let me know. If it doesn't work pm me and I'll send you another link.
Click to expand...
Click to collapse
Hmm, it lets me download it on my desktop, but no matter what browser I try to download it on with my laptop it does the same thing. Weird.
---------- Post added at 05:11 PM ---------- Previous post was at 04:39 PM ----------
I got it working, but how do I get Apex launcher working again after the update?

FroyoShark said:
Hmm, it lets me download it on my desktop, but no matter what browser I try to download it on with my laptop it does the same thing. Weird.
---------- Post added at 05:11 PM ---------- Previous post was at 04:39 PM ----------
I got it working, but how do I get Apex launcher working again after the update?
Click to expand...
Click to collapse
Yeah sorry I made those backups before the update. Download from the play store, go into your file manager and move it from /data/app/ folder to /system/app/ folder then reboot.
Did you have to re-root.

onemeila said:
Yeah sorry I made those backups before the update. Download from the play store, go into your file manager and move it from /data/app/ folder to /system/app/ folder then reboot.
Did you have to re-root.
Click to expand...
Click to collapse
That worked, thanks. I did have to re-root. Maybe make it so it installs the OTA Rootkeeper as well?

FroyoShark said:
That worked, thanks. I did have to re-root. Maybe make it so it installs the OTA Rootkeeper as well?
Click to expand...
Click to collapse
OTA Rootkeeper does not work. There are a couple system apps that can be altered to stop updates, I can't think of them but they are in another thread. Now that you have your device working I would recommend making a backup of your own of all the partitions. If you mess something else up outside the system partition this restore tool won't fix it. Very easy to do check out this thread:
http://forum.xda-developers.com/showthread.php?t=1930656

Firstly, good work. Play store wouldn't open for me, so I ended up needing to manually copy all files from gapps onto the device. It seems that you might be missing the gapps framework permission files. It's painfully slow however, and apps are constantly closing. I full wiped using fastboot.

synergye said:
Firstly, good work. Play store wouldn't open for me, so I ended up needing to manually copy all files from gapps onto the device. It seems that you might be missing the gapps framework permission files. It's painfully slow however, and apps are constantly closing. I full wiped using fastboot.
Click to expand...
Click to collapse
Yeah the google framework was installed as user app on those backups. I don't like installing things as system apks if its not necessary, just more chances of problems. I'm in the process of adding an option to install that separately, via adb. At first I was just trying to keep everything as close to out of the box as possible so people would just have a clean slate, but its nice to have the options of add-ons in one shot if they are wanted.
I was in a hurry when I made the mods to this version for the 8.9 and just haven't had the time to look back over it. So I apologize if something is off. Please let me know if you or anyone catches something. Was it slow after the the restore?

Is this one version 8.1.2 or 8.1.3?
Need a rootable.

timnan said:
Is this one version 8.1.2 or 8.1.3?
Need a rootable.
Click to expand...
Click to collapse
The backup was done right out of the box after root, so it would be as close to factory as possible. It should be 8.1.2, but 8.1.3 is rootable also. I lost root after the update and was still able to root.

Bricked over a dpi change!
onemeila said:
THIS IS NOT A CUSTOM RECOVERY!!!
KINDLE FIRE HD 8.9 ONLY!!! USE AT YOUR OWN RISK!!
About an hour ago I ran a tool to change dpi on my Kindle 8.9 and was greeted with the unpleasant notice that my 8.9 could not boot. System goes to the screen that asks if I want to do a factory restore. That of course fails. Downloading your recovery prog, will try it in the morning, anything need to do other than follow your bouncing ball?
Thanks
[email protected]@dog
---------- Post added at 02:45 AM ---------- Previous post was at 02:36 AM ----------
onemeila said:
THIS IS NOT A CUSTOM RECOVERY!!!
KINDLE FIRE HD 8.9 ONLY!!! USE AT YOUR OWN RISK!!
To come in next version:
Install of GoogleServicesFramework.apk after erase of cache and userdata, thought about adding this after writing this post.
If anyone wants see other options included let me know.
.
Click to expand...
Click to collapse
Have you added Install of GoogleServicesFramework.apk yet?
Click to expand...
Click to collapse

[QUOTE/]
Have you added Install of GoogleServicesFramework.apk yet?[/QUOTE]
Posting link now

Works as Advertised Thank you Onemeila!
onemeila said:
[QUOTE/]
Have you added Install of GoogleServicesFramework.apk yet?
Click to expand...
Click to collapse
Posting link now[/QUOTE]
Started to use KFHD_SRT v 1.3 When I woke up this morning, had to look for GSFa before starting, then spotted your answer to me, still on my laptop! Sooo I went with KFHD_SRT v2.0 instead. Didn't even finish my first cup of coffee and you had me back up. Needless to say, I think I will stay away from the dpi tool that caused this to begin with. One question, (not sure if I ever used option 5). is it included in Option 3??
I think I owe you something, will take care of it before the weekend.

[email protected]@dog said:
Posting link now
Click to expand...
Click to collapse
One question, (not sure if I ever used option 5). is it included in Option 3?? [/QUOTE]
No it is not. I prefer not to install apps as system apps unless it is necessary. There is no sense in potentially causing more problems. Also the more you install as system, the more you will lose and have to redo if you get an update.

I bricked this device playing with permissions to get app store installed. This tool really saved me.
I used option 4 then 3 and all is well.
Installed Google resources manually as the tool lost the device. Every thing except Gmail that I have in the screenshot works.
Thanks a bunch
{
"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"
}
Sent from my KFJWI using Tapatalk 2

Is it work with 8.1.4?
Hi,
I trying root my kindle 8.9, but is not working, my system version is 8.1.4 is this the problem? I follow steps, but SR Tool, is not detecting my kindle it just stay on <waiting for device>. I tried option 1, to start adb and i got message that adb is outdated, after that i tried option 3 and stay on waiting for device.
I now my kindle show up in adb devices list, after install right drivers, but recovery continue waiting for device.
edited 1: any help very appreciated.
edited 2: finaly all works fine.
thanks.

drr00t said:
Hi,
I trying root my kindle 8.9, but is not working, my system version is 8.1.4 is this the problem? I follow steps, but SR Tool, is not detecting my kindle it just stay on <waiting for device>. I tried option 1, to start adb and i got message that adb is outdated, after that i tried option 3 and stay on waiting for device.
I now my kindle show up in adb devices list, after install right drivers, but recovery continue waiting for device.
edited 1: any help very appreciated.
edited 2: finaly all works fine.
thanks.
Click to expand...
Click to collapse
Thats good you got it to work but if you were just trying to root this was not the tool to use. This tool is used to unbrick your device. It will give you root access but at the moment it is for v8.1.3. So as soon as you have wifi connected it is going to upgrade again to 8.1.4 and you will lose root.

Confirmed- downgrading from 8.1.4 to 8.1.3 is possible with this tool without having to flash other partitions.

[Q] TWRP 2.5.0.0 Unresponsive

Hello,
I while ago I decided to root my HTC to get some extra stuff. I used a guide on youtube that seemed to be reasonably well made and followed everystep of the process. But before I could root it I had to unlock the bootloader and install TWRP recovery. I got the latest version and proceeded to the next step, where I encountered my problem. After flashing the recovery everything seemed to be well except that my phone wasn't actually rooted. I decided to redo some of the last steps. This is where things get a bit tricky. I have done this quite a while ago (maybe 3-4 months) and don't exactly remember the steps that I repeated but I think I've also flashed TWRP a second time, as well as some other steps. And when it came to the part where I needed to use the recovery I found out that the recovery doesn't work. I can't press anything on the screen, I can however press the lock button and lock the device but when the *slide to unlock* appears it stops working again. I was running out of time and decided to leave it for another time but time has passed and I never really got the time to tinker with it any more since university started and I'm more busy then ever. This has left me with no ability to root or even update my phone.
This brings me to today, when I restored my phone completely forgetting what has happened. It got back to Android 4.1 and I can't do anything about it.
I hope to sort this out and finally root the phone. But even getting rid of TWRP to the original recovery so I could just update my phone would be very helpfull.
Thank you very much.

aleks945 said:
Hello,
I while ago I decided to root my HTC to get some extra stuff. I used a guide on youtube that seemed to be reasonably well made and followed everystep of the process. But before I could root it I had to unlock the bootloader and install TWRP recovery. I got the latest version and proceeded to the next step, where I encountered my problem. After flashing the recovery everything seemed to be well except that my phone wasn't actually rooted. I decided to redo some of the last steps. This is where things get a bit tricky. I have done this quite a while ago (maybe 3-4 months) and don't exactly remember the steps that I repeated but I think I've also flashed TWRP a second time, as well as some other steps. And when it came to the part where I needed to use the recovery I found out that the recovery doesn't work. I can't press anything on the screen, I can however press the lock button and lock the device but when the *slide to unlock* appears it stops working again. I was running out of time and decided to leave it for another time but time has passed and I never really got the time to tinker with it any more since university started and I'm more busy then ever. This has left me with no ability to root or even update my phone.
This brings me to today, when I restored my phone completely forgetting what has happened. It got back to Android 4.1 and I can't do anything about it.
I hope to sort this out and finally root the phone. But even getting rid of TWRP to the original recovery so I could just update my phone would be very helpfull.
Thank you very much.
Click to expand...
Click to collapse
The background information is helpful but you have given us nothing to go on.
Post a fastboot getvar all except remove the imei and serialno?
What are you trying to accomplish? Return to Stock? S-OFF?

majmoz said:
The background information is helpful but you have given us nothing to go on.
Post a fastboot getvar all except remove the imei and serialno?
What are you trying to accomplish? Return to Stock? S-OFF?
Click to expand...
Click to collapse
Tell me what background information do you need and I'll get everything.
The goal is to get a working recovery, which ever one it would be I don't really care. I just want to be able to update the firmware.

reboot into the bootloader. flash the latest twrp for your device using fastboot flash recovery recoverynamehere.zip
profit

jdgreat4 said:
reboot into the bootloader. flash the latest twrp for your device using fastboot flash recovery recoverynamehere.zip
profit
Click to expand...
Click to collapse
If you could give me a more detailed guide I would toatally do that, because I'm pretty noobish when it comes to this kind of stuff.

aleks945 said:
Tell me what background information do you need and I'll get everything.
The goal is to get a working recovery, which ever one it would be I don't really care. I just want to be able to update the firmware.
Click to expand...
Click to collapse
like he said before, post the output of "fastboot getvar all" except your IMEI and SERIALNO
---------- Post added at 11:06 AM ---------- Previous post was at 11:05 AM ----------
aleks945 said:
If you could give me a more detailed guide I would toatally do that, because I'm pretty noobish when it comes to this kind of stuff.
Click to expand...
Click to collapse
do you have adb and fastboot on your computer?
Do you have HTC drivers installed?

alray said:
like he said before, post the output of "fastboot getvar all" except your IMEI and SERIALNO
---------- Post added at 11:06 AM ---------- Previous post was at 11:05 AM ----------
do you have adb and fastboot on your computer?
Do you have HTC drivers installed?
Click to expand...
Click to collapse
I don't know what adb is, sorry. And no I don't, I had to do everything on my friend's laptop because it didn't seem to work on my machine (W8.1 compared to his W7).
Edit. But I do have acces to it pretty much all the time.

aleks945 said:
I don't know what adb is, sorry. And no I don't, I had to do everything on my friend's laptop because it didn't seem to work on my machine (W8.1 compared to his W7).
Click to expand...
Click to collapse
yes better to use windows 7
go ahead and download adb and fastboot from here: http://forum.xda-developers.com/showthread.php?t=2317790
download and install HTC sync from here: http://www.htc.com/us/support/software/htc-sync-manager.aspx
Once installed, uninstall HTC sync but keep the drivers installed
post back when done

alray said:
yes better to use windows 7
go ahead and download adb and fastboot from here: http://forum.xda-developers.com/showthread.php?t=2317790
download and install HTC sync from here: http://www.htc.com/us/support/software/htc-sync-manager.aspx
Once installed, uninstall HTC sync but keep the drivers installed
post back when done
Click to expand...
Click to collapse
The downloads are complete, just waiting on the instalation. The computer is quite old and slow unfortunatelly.
Thank you again
EDIT. Everything is done.

aleks945 said:
The downloads are complete, just waiting on the instalation. The computer is quite old and slow unfortunatelly.
Thank you again
EDIT. Everything is done.
Click to expand...
Click to collapse
ok so connect your phone with he usb cable to the computer, reboot it in bootloader mode (hold power and vol -). in bootloader select "fastboot"
then lauch the adb command prompt and type "fastboot getvar all". post the output here but edit out the imei and serialno before.

alray said:
ok so connect your phone with he usb cable to the computer, reboot it in bootloader mode (hold power and vol -). in bootloader select "fastboot"
then lauch the adb command prompt and type "fastboot getvar all". post the output here but edit out the imei and serialno before.
Click to expand...
Click to collapse
Here it is.
{
"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"
}
Link since image seems to be really tiny.
http://i.imgur.com/9cZZRA9.jpg

aleks945 said:
Here it is.
Link since image seems to be really tiny.
http://i.imgur.com/9cZZRA9.jpg
Click to expand...
Click to collapse
you can flash twrp 2.6.3.3
download the file and save it in the same folder where you have installed minimal adb and fastboot
then open the command prompt and with the phone in bootloader/fastboot mode enter these commands:
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
What do you want to achieve then? Custom rooted rom? stock rooted rom (latest version)? or you simply what to root the rom you currently have?

alray said:
you can flash twrp 2.6.3.3
download the file and save it in the same folder where you have installed minimal adb and fastboot
then open the command prompt and with the phone in bootloader/fastboot mode enter these commands:
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
What do you want to achieve then? Custom rooted rom? stock rooted rom (latest version)? or you simply what to root the rom you currently have?
Click to expand...
Click to collapse
Latest stock rooted ram would be the final goal.

aleks945 said:
Latest stock rooted ram would be the final goal.
Click to expand...
Click to collapse
you can flash this rom: http://www.androidrevolution.org/downloader/download.php?file=One_6.09.401.5_odexed.zip
its the stock rom for 6.09.401.5

alray said:
you can flash this rom: http://www.androidrevolution.org/downloader/download.php?file=One_6.09.401.5_odexed.zip
its the stock rom for 6.09.401.5
Click to expand...
Click to collapse
Doesn't my phone have to be rooted to be able to instal another rom?

aleks945 said:
Doesn't my phone have to be rooted to be able to instal another rom?
Click to expand...
Click to collapse
no just flash the rom from twrp recovery then you can root it if you want.

[HELP] MemoPad 7 (176CX) stuck after OTA

Hello,
A fellow colleauge of mine had a MemoPad 7 (176CX) which received an OTA update last week. After the installation the tablet restarted and then a dead droid appeared on the screen with an error message "no command found" then the device restarts automatically and everything starts again (dead droid - no command - reboot - dead droid...). So, it's in a boot loop. (As far as I know the device was rooted and he made a mistake to no un-root before the OTA update but it's irrelevant now)
As he asked for help I checked the XDA forums and found that my idea about reinstalling the factory default firmware should solve the problem. But I'm a little bit afraid of the continous boot loop. How will be able to reflash the firmware when the device keeps rebooting?
Any advice will be helpful.
Thanks in advance.

I know what to do, don't worry. Get into recovery (it's annoying to get into recovery, you need to spam all buttons randomly while the no command screen is up), reboot to bootloader, and boot into a Temporary CWM using a PC.
Reply with questions.
---------- Post added at 01:19 PM ---------- Previous post was at 01:19 PM ----------
I know what to do, don't worry. Get into recovery (it's annoying to get into recovery, you need to spam all buttons randomly while the no command screen is up), reboot to bootloader, and boot into a Temporary CWM using a PC.
Reply with questions.
---------- Post added at 01:22 PM ---------- Previous post was at 01:19 PM ----------
Sorry for the double post.
---------- Post added at 01:22 PM ---------- Previous post was at 01:22 PM ----------
Sorry for the double post.

Hello,
Thanks for the reply. Unfortunatelly the issue seems to be a little bit more complicated.
So, things I checked:
- boot into droidboot with Vol+ + Power - works well, able to boot into droidboot. But see this strange notice in the bottom:
FASTBOOT INIT....
e:Failed to mount device '/dev/block/sda1' as installer partition using fs_type
ition using fs_type 'vfat'
continue fastboot process
E:installer device ignored
FASTBOOT CMD WAITING...
E:installer device ignored
E:No valid installer medium found
Could not open /sys/devices/virtual/backlight
Now, I can select Reboot Droidboot - no luck
Reboot - no luck
Recovery - reboot into bootloop
Power off - yeah, it works and turns of the device.
If I try to boot into Fastboot with Vol - + Powoer receive the dead droid with the No command message.
Any idea where can I go forward?
Nandr0idC0nsumer said:
I know what to do, don't worry. Get into recovery (it's annoying to get into recovery, you need to spam all buttons randomly while the no command screen is up), reboot to bootloader, and boot into a Temporary CWM using a PC.
Reply with questions.
---------- Post added at 01:19 PM ---------- Previous post was at 01:19 PM ----------
I know what to do, don't worry. Get into recovery (it's annoying to get into recovery, you need to spam all buttons randomly while the no command screen is up), reboot to bootloader, and boot into a Temporary CWM using a PC.
Reply with questions.
---------- Post added at 01:22 PM ---------- Previous post was at 01:19 PM ----------
Sorry for the double post.
---------- Post added at 01:22 PM ---------- Previous post was at 01:22 PM ----------
Sorry for the double post.
Click to expand...
Click to collapse

waces said:
Hello,
Thanks for the reply. Unfortunatelly the issue seems to be a little bit more complicated.
So, things I checked:
- boot into droidboot with Vol+ + Power - works well, able to boot into droidboot. But see this strange notice in the bottom:
FASTBOOT INIT....
e:Failed to mount device '/dev/block/sda1' as installer partition using fs_type
ition using fs_type 'vfat'
continue fastboot process
E:installer device ignored
FASTBOOT CMD WAITING...
E:installer device ignored
E:No valid installer medium found
Could not open /sys/devices/virtual/backlight
Now, I can select Reboot Droidboot - no luck
Reboot - no luck
Recovery - reboot into bootloop
Power off - yeah, it works and turns of the device.
If I try to boot into Fastboot with Vol - + Powoer receive the dead droid with the No command message.
Any idea where can I go forward?
Click to expand...
Click to collapse
X2 With the OTA missing partition. Seemed like a straight forward update but completely screwed up my tablet. SOL for the moment. I imagine this post will become popular very quick.

Try the following:
Boot into DROIDBOOT
Download & Install Android Studio
Go into a cmd and type "fastboot devices"
If it shows a device, than:
Use a temp CWM session to flash 182.

Hello,
Nope, in Droidboot the PC cannot see and connect any device.
fastboot devices - return with empty line
fastboot getvar - return with <waiting for device>

minor correcftion. was able to access the device with fastboot devices and it shows the connected device as well. i followed the steps described here : http://forum.xda-developers.com/android/help/instructions-reviving-me170c-me170cx-t3017466 but no luck. what did i missed?

waces said:
minor correcftion. was able to access the device with fastboot devices and it shows the connected device as well. i followed the steps described here : http://forum.xda-developers.com/android/help/instructions-reviving-me170c-me170cx-t3017466 but no luck. what did i missed?
Click to expand...
Click to collapse
Fastboot? AWESOME! You're covered, Jimmy. (If you didn't have access to fastboot, you would be six callers ahead of us...)
Download this temp CWM:
https://www.androidfilehost.com/?fid=23991606952604606
open the batch file (with droidboot open on the tablet, and tethered to the pc), and type "ACCEPT". Now, type "T4", and click enter, and a temporary CWM session should open.
Now, (you'll need a external SD card), flash this file:
http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/ME176C-WW-3_2_23_182.zip
And you should be on KitKat... and take OTAs from there to get to lollipop. Use the same temp CWM and flash SuperSU to get root.

{
"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"
}
---------- Post added at 01:50 PM ---------- Previous post was at 01:17 PM ----------
Just wondering... did you end up fixing the device? You don't seem to be very active on this fourm.

Nandr0idC0nsumer said:
Fastboot? AWESOME! You're covered, Jimmy. (If you didn't have access to fastboot, you would be six callers ahead of us...)
Download this temp CWM:
open the batch file (with droidboot open on the tablet, and tethered to the pc), and type "ACCEPT". Now, type "T4", and click enter, and a temporary CWM session should open.
Now, (you'll need a external SD card), flash this file:
And you should be on KitKat... and take OTAs from there to get to lollipop. Use the same temp CWM and flash SuperSU to get root.
Click to expand...
Click to collapse
Wondering if you could help me for a sec... I followed what you have here and all works fine but the sd card won't mount, I've formatted with both file systems but no. I'm very new but learning, what did I miss?

jakeco2u said:
Wondering if you could help me for a sec... I followed what you have here and all works fine but the sd card won't mount, I've formatted with both file systems but no. I'm very new but learning, what did I miss?
Click to expand...
Click to collapse
Tell me the exact steps you took.
Did you take the OTAs to Lollipop?

Nandr0idC0nsumer said:
Tell me the exact steps you took.
Did you take the OTAs to Lollipop?
Click to expand...
Click to collapse
Yes, was rooted, OTA to Lollipop and tablet stuck in bootloop. I followed your post and was not able to install your link but had success with WW_V12.10.1.17. The tablet stated it had been installed so I went back and reboot but its still stuck in the bootloop. Hope that makes sense.
Like I said, I'm new to working on these so be nice. Should I install firmware and source code from the Asus website?

jakeco2u said:
Yes, was rooted, OTA to Lollipop and tablet stuck in bootloop. I followed your post and was not able to install your link but had success with WW_V12.10.1.17. The tablet stated it had been installed so I went back and reboot but its still stuck in the bootloop. Hope that makes sense.
Like I said, I'm new to working on these so be nice. Should I install firmware and source code from the Asus website?
Click to expand...
Click to collapse
Did you factory reset after installing the WW_V12.10.1.17 ROM?

Nandr0idC0nsumer said:
Did you factory reset after installing the WW_V12.10.1.17 ROM?
Click to expand...
Click to collapse
I did, back to bootloop.

jakeco2u said:
I did, back to bootloop.
Click to expand...
Click to collapse
Did the Lollipop OTA finish? (As in, did you see all the BIOS updating text?)

Nandr0idC0nsumer said:
Did the Lollipop OTA finish? (As in, did you see all the BIOS updating text?)
Click to expand...
Click to collapse
I'm not sure if the bios updated (I assume we are talking about the first OTA round before the problem). It had finished the download, the droid was shown for a bit, and when I came back after about 1/2 hr. to check on it the 'Asus powered by Android' screen kept cycling about every minute. I didn't see bios updating text. BTW thank for the help...
And as the OP stated in fastboot i get:
E:installer device ignored
continue the fastboot process
E:failed to mount device '/dev/block/sda1' as installer partition using fs_type
ition using fs_type 'vfat'
FASTBOOT CMD WAITING...
E:installer device ignored
E:No valid installer medium found
Could not open /sys/devices/virtual/backlight

jakeco2u said:
I'm not sure if the bios updated (I assume we are talking about the first OTA round before the problem). It had finished the download, the droid was shown for a bit, and when I came back after about 1/2 hr. to check on it the 'Asus powered by Android' screen kept cycling about every minute. I didn't see bios updating text. BTW thank for the help...
And as the OP stated in fastboot i get:
E:installer device ignored
continue the fastboot process
E:failed to mount device '/dev/block/sda1' as installer partition using fs_type
ition using fs_type 'vfat'
FASTBOOT CMD WAITING...
E:installer device ignored
E:No valid installer medium found
Could not open /sys/devices/virtual/backlight
Click to expand...
Click to collapse
Try downloading each ROM from the OP, and flashing them in order.

Nandr0idC0nsumer said:
Try downloading each ROM from the OP, and flashing them in order.
Click to expand...
Click to collapse
Sorry, which ROMs? Are we talking about the firmware and kernels from the Asus website? I'm not seeing any ROMs in this post except the one you posted and the Asus one. And again, thanks for taking the time...

jakeco2u said:
Sorry, which ROMs? Are we talking about the firmware and kernels from the Asus website? I'm not seeing any ROMs in this post except the one you posted and the Asus one. And again, thanks for taking the time...
Click to expand...
Click to collapse
Sorry, didn't make what to download clear enough.
ME176C/X K013 ROMS AND UPDATES:
WW .182 ROM
http://dlcdnet.asus.com/pub/ASUS/Eee...3_2_23_182.zip
WW OTA 191
http://fota.asus.com/delta_package/e...104/update.zip
https://drive.google.com/file/d/0B5G...ew?usp=sharing
http://www26.zippyshare.com/v/49210353/file.html
WW OTA 198
http://www21.zippyshare.com/v/f1NwNFH5/file.html
WW OTA 199
http://www.mediafire.com/download/ec...c8j/update.zip
WW OTA 201
http://www48.zippyshare.com/v/PtRl8YI9/file.html
WW Lollipop release
http://www.mediafire.com/download/2v...1/lollipop.zip
download each one of those (sorry, lots of downloads lol) and flash them each in order using a temp CWM. then do a factory reset and reboot.
EDIT: some links are down. I'm assuming you already have the 182 ROM.
Flash the 182 ROM, and then flash all the updates you can download in order.

Nandr0idC0nsumer said:
Sorry, didn't make what to download clear enough.
ME176C/X K013 ROMS AND UPDATES:
WW .182 ROM
http://dlcdnet.asus.com/pub/ASUS/Eee...3_2_23_182.zip
WW OTA 191
http://fota.asus.com/delta_package/e...104/update.zip
https://drive.google.com/file/d/0B5G...ew?usp=sharing
http://www26.zippyshare.com/v/49210353/file.html
WW OTA 198
http://www21.zippyshare.com/v/f1NwNFH5/file.html
WW OTA 199
http://www.mediafire.com/download/ec...c8j/update.zip
WW OTA 201
http://www48.zippyshare.com/v/PtRl8YI9/file.html
WW Lollipop release
http://www.mediafire.com/download/2v...1/lollipop.zip
download each one of those (sorry, lots of downloads lol) and flash them each in order using a temp CWM. then do a factory reset and reboot.
Click to expand...
Click to collapse
OK, I tried to download these links most are dead and the three that did download came up as errors when attempting to flash them.
I'm going to try and explain the best I can with pictures as I can only assume I'm doing something wrong.
This is what I get when I go into fastboot, or droidboot or whatever.
OK, I install update from Asus website(as its the only file that hasn't caused an error.
After the install...
Wipe data...
Reboot... I don't know why it asks for root on reboot???
Then starts bootloop...
Any thoughts? Or should I just toss it.. It seems there has to be a way but it's beyond my skill set. Thanks again for the help.

[GUIDE] Unbrick your device or recover from bootloop

Assalamu alaikum people,
Those on the telegram group know that I bugged you a lot about needing data partition. Because of my experience with unbricking and recovering the device, I can tell you a sureshot method that works to restore the device. Do not use this method if your device already works. There seems to be a lot of files inside the data partition which are necessary for the stock ROM to work. This method asks you to wipe data partition and so system update will not work. This should be a last resort. .
Many people seem to have come to the situation where they are in fastboot, and it says frp locked, so they cannot flash new twrp. And the system seems to be in bootloop and it does not work. What to do from there?
1. Download this file ->https://www.androidfilehost.com/?fid=673956719939832337.
2. In your SDCard, create a folder called TWRP and inside it, create a folder called BACKUPS (all in capitals). Inside this, create a folder called 7xtwrpbackup (small letters) and paste the contents of the zip that you have downloaded into this.
3. Boot to twrp in your device and go to restore. There you should see a folder 7xtwrpbackup. If you select it, you will get a checkbox below with recovery_ramdisk like this
{
"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"
}
4. Select Yes and after restore complete, go back and select reboot and reboot to recovery.
5. Now, the new twrp will boot. In the new twrp, I want you to first go to wipe -> advanced wipe -> select dalvik/art cache, cache, data, internal storage and system.
6. Come back once again and select wipe, and this time, select format data. It will ask you to type yes. After that is done, come back once again.
7. Now select install and in that, install the openkirin RR image from telegram group or here -> https://forum.xda-developers.com/honor-view-10/development/rom-t3753555 (This step is optional because openkirin RR has a greater chance of booting than stock ROM. You can skip this step and directly boot stock)
8. Your system must boot now. If it boots, then all partitions are good. You can boot stock.
9. You can now can download stock from my post here and repeat from step 5-> https://forum.xda-developers.com/9-lite/development/stock-img-unlock-indian-version-t3767569
If this does not work, then look at the second method in the next post

Second method
If your first method does not work, then you can try this second method. Make sure you have enough data left in your internet connection (1.8 GB ish) before starting the process. Please note that this method will lock your bootloader, install stock recovery, flash the stock system and boot your phone. Of course, even if it relocks the bootloader, you can still unlock it using your code.
1. Download the zip
https://www.androidfilehost.com/?fid=746010030569970895
2. Extract it into sdcard directly (i.e. extract it to the root folder of your sdcard)
3. Make sure you have enough battery left (atleast 15%). Power off your phone. Now, press and hold vol up + Vol down + power buttons until the honor logo comes. Then, you can release all the keys. The system will go into emui recovery and restore your phone.
You will have stock phone at the end of the process.
Note:-If you still have bootloop at Honor logo, then power off the phone. Hold vol up + power button until the honor logo comes. It will boot into stock recovery. From there, you can do a factory reset and erase cache partition. Then the phone will definitely boot up.

Bricked my device Twrp doesn't work
Hello, I have bricked my honor 9 lite AL10(Indian Version). I have formatted my vender directory through Twrp by mistake now my device shows erecovery and reboots. Fastboot is working fine and FRP and Devices both shows unlocked means I can flash through fastboot. I don't want to lose my internal memory data.
Help me to unbrick my device !! :crying:

Oushal kDee said:
Hello, I have bricked my honor 9 lite AL10(Indian Version). I have formatted my vender directory through Twrp by mistake now my device shows erecovery and reboots. Fastboot is working fine and FRP and Devices both shows unlocked means I can flash through fastboot. I don't want to lose my internal memory data.
Help me to unbrick my device !! :crying:
Click to expand...
Click to collapse
Download vendor partition from here https://forum.xda-developers.com/9-lite/development/stock-img-unlock-indian-version-t3767569

Hello i am siddharth, i have relocked my oem by fastboot oem relock -------- after that yes/no option came i click on yes. It starts factory formatting after completion of formatting when the phone starts its showing your device has failed verification and got stuck in it. When i press reboot option it will directly comes to erecovery mode wher the option came to download new recovery when i connect my phone with wifi it starts searching for some time after that system update failed.
When i starts mobile directly to fastboot mode by pressing volume down button and power button the white screen with android comes appear i.e fastboot mode screen. In that screen in green colour i found that
Phone Relock
FRP lock
When ever i m trying to find the device in fastboot mode by typing fastboot devices my device showing there but no other command is working such as fastboot oem unlock -------, fastboot flash system system.img, all the time it comes Failed.
I have downloaded many UPDATE.APP and tried to load that by dload method but every time after 5% it come Failed to install.
I have downloaded UPDATE.APP form ur given link also. This is only the image in which my phone comes upto 23% install after dat failed.
Nothing working for me. Kindly help me.
Mail me if there is any solution @
[email protected]

i have tried first method it failed and says 'no partition selected for restore'
and their is no option to select partition what should i do plz help

None of the method worked for me my device still bootloops no matter what system.img or rom zip file i flash. The emui recovery method didn't work for me as it loaded up to 5% and then failed instantly. Please help me unbrick my 9 lite bro. Could you provide me the boot.img? i think my phone got bricked because i tried to i install magisk on treble rom (i guess?). But anyway PLEASE HELP ME (

Try extracting kernel.img from an update and flash that. It fixed it for me.

hi twrp is bootlooping as well
cant access
---------- Post added at 07:15 PM ---------- Previous post was at 06:52 PM ----------
hey i used the twrp from the link made a backup restored it now a get bootloop cant get into twrp it goes in ti it then it fcs then am back to bootloader unlocked warning

hi anyone got custom.img and userdata.img from this LLDL31C432B130 800130 a need to restore my device

Same Problem
[email protected] said:
i have tried first method it failed and says 'no partition selected for restore'
and their is no option to select partition what should i do plz help
Click to expand...
Click to collapse
Even I'm facing the same problem, if anyone has solution plz help.
---------- Post added at 10:15 AM ---------- Previous post was at 10:10 AM ----------
[email protected] said:
i have tried first method it failed and says 'no partition selected for restore'
and their is no option to select partition what should i do plz help
Click to expand...
Click to collapse
Even I'm facing the same problem.

mine goes to 5% doesnt do anything and then it fails

aveemashfaq said:
If your first method does not work, then you can try this second method. Make sure you have enough data left in your internet connection (1.8 GB ish) before starting the process. Please note that this method will lock your bootloader, install stock recovery, flash the stock system and boot your phone. Of course, even if it relocks the bootloader, you can still unlock it using your code.
1. Download the zip
https://www.androidfilehost.com/?fid=746010030569970895
2. Extract it into sdcard directly (i.e. extract it to the root folder of your sdcard)
3. Make sure you have enough battery left (atleast 15%). Power off your phone. Now, press and hold vol up + Vol down + power buttons until the honor logo comes. Then, you can release all the keys. The system will go into emui recovery and restore your phone.
You will have stock phone at the end of the process.
Note:-If you still have bootloop at Honor logo, then power off the phone. Hold vol up + power button until the honor logo comes. It will boot into stock recovery. From there, you can do a factory reset and erase cache partition. Then the phone will definitely boot up.
Click to expand...
Click to collapse
But this is for L31
---------- Post added at 08:06 AM ---------- Previous post was at 08:05 AM ----------
My phone's frp and bootloader locked,and phone is booting to erecovery,what to do

need help with LLD-AL10C675 indian version
I have flashed a cutom treble rom phh-treble to be specific,used it for couple of days and then tried instaling the magisk from magiskmanager and after its done when i reboot it shows error mode with message Func no:10(boot img ) and func no:2 , i can boot into fastboot mode both frp and phone unlocked ,can some please help me to get back my phone into a usable condition thank you

sunny_deed said:
I have flashed a cutom treble rom phh-treble to be specific,used it for couple of days and then tried instaling the magisk from magiskmanager and after its done when i reboot it shows error mode with message Func no:10(boot img ) and func no:2 , i can boot into fastboot mode both frp and phone unlocked ,can some please help me to get back my phone into a usable condition thank you
Click to expand...
Click to collapse
To help you a full firmware is required and that's not available for (India c675) yet!
Before any modification to system you should have a full firmware in hand.

BS4388 said:
To help you a full firmware is required and that's not available for (India c675) yet!
Before any modification to system you should have a full firmware in hand.
Click to expand...
Click to collapse
yea that was a pretty big mistake i made without looking for it, i have been told by someone that we can pull out all the require d imgs from a phone in good working condition, i asked in the hopes that someone would be generous enough to do that for me , thank you ,and also does anyone have any idea about when the full firmware will be released

sunny_deed said:
yea that was a pretty big mistake i made without looking for it, i have been told by someone that we can pull out all the require d imgs from a phone in good working condition, i asked in the hopes that someone would be generous enough to do that for me , thank you ,and also does anyone have any idea about when the full firmware will be released
Click to expand...
Click to collapse
What's wrong with the version (675) from here :-
https://www.mobileheadlines.net/download-huawei-honor-9-lite-firmware-files/

Sparkrite said:
What's wrong with the version (675) from here :-
https://www.mobileheadlines.net/download-huawei-honor-9-lite-firmware-files/
Click to expand...
Click to collapse
there is no Fullota version in there

sunny_deed said:
there is no Fullota version in there
Click to expand...
Click to collapse
Go:
https://forum.xda-developers.com/9-lite/development/stock-rom-indian-firmware-c675-t3813875

sunny_deed said:
there is no Fullota version in there
Click to expand...
Click to collapse
My bad, I was only trying to help.............
Anyway you have it now (post above) thanks to @BS4388 and @VigneshS007 .

[Superseded] Crossflash US Unlocked Pie to your Bootloader Unlocked V40

SUPERSEDED: Go Here​
Prerequisites:
V35 Engineering Bootloader flashed to your device (Stock bootloader will NOT work for this)
USB 2.0 (USB 3.x does not work well with ADB or Fastboot)
The V40 Pie Conversion Tool
Be in fastboot mode before attempting this
Patience
ADB and Fastboot DRIVERS. Platform tools are already included in the archive
Windows. The tool is not designed for Linux.
This will NOT sim unlock your phone[/CENTER]
Note: I'm not responsible for any bricks that come about from using this tool. Once you crossflash, there's NO going back unless you have backups of your partitions, or a KDZ specifically for your device. I'm going to say this again, DO NOT use USB 3.x while attempting this. You will run into errors. You won't see anything for a little bit when it gets to flashing system_a and vendor_a because it has to load those images into ram.
Download the tool: Google Drive
1. Download the archive and unzip the tool.
2. Navigate to the folder you unzipped the tool to.
3. Enter the folder and inside the folder you should find "V40PIECONVERSION.cmd". Ignore the one with the "Stock Boot" at the end. All it does is flash the stock boot image instead of the TWRP that is required to do this.
4. Execute the batch file and follow the instructions. When the batch file is done, Pie will be flashed, but it will not boot due to encryption. We're going to disable that.
5. Boot TWRP by performing a master reset. To perform a master reset: Press and hold Vol- and Power. When you see the "V40 ThinQ" logo release the power button and quickly press back down. Keep holding Vol- and Power until you see a factory reset screen. Finally, follow the prompts (yes) and you should be in TWRP.
TWRP Instructions​
Head over to the wipe menu and format data (to remove encryption).
Next, head over to mount and mount vendor. Mount ONLY vendor.
Now, open a command prompt, navigate to the folder where you extracted the tool, and open a command prompt inside the folder (Type "CMD" in File Explorer's Address Bar)
{
"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"
}
Execute the adb command:
Code:
adb pull /vendor/etc/fstab.judypn
Edit the file (fstab.judypn) in your favorite text editor and on the /data mountpoint change "forceencrypt" to "encryptable".
Save and Close the file and push the file back with the command:
Code:
adb push fstab.judypn /vendor/etc
Now that encryption is disabled, you NEED to flash back the ORIGINAL boot image that's included with the tool. In order to do that, we need to get back into fastboot.
To get back into fastboot, we need to: Make sure USB is still plugged into the phone. Press and hold VOL+ (Or vol up). Power off the phone (Via TWRP reboot menu) while still holding vol+. Keep holding VOL+ until you see download mode flash for a brief second and you should be in fastboot. The fastboot you see now isn't the V35 Engineering Bootloader. It's the stock pie bootloader. Wiping the laf_a partition allows access to fastboot on devices that are locked (Nearly all US Carriers).
Finally, run the commands:
Code:
fastboot flash boot_a boot_a.image
and
Code:
fastboot format userdata
You should run into an "encryption unsuccessful" screen. Just hit reset phone. You may have to reboot once or twice to get to the setup screen.
For those of you that want root, here's a patched Magisk boot image: Google Drive
You can flash it by running the command:
Code:
fastboot flash boot_a magisk_patched.img
Make sure you open a command prompt in the directory you downloaded the image in. If you don't have adb and fastboot in your environment path, just place it in the V40PIEConversion folder and flash it from there.

How do you get the v35 bootloader on stock Att ?

Evilmonstertruck said:
How do you get the v35 bootloader on stock Att ?
Click to expand...
Click to collapse
Contact @vbenkovskyy on Telegram. He is an awesome guy. Of course, it isn't free, but his prices are better.

Confirmed working - thanks Xsavi for an excellent guide!

Would this method work on the T-Mobile variant? Is there a fee [anywhere]?
---------- Post added at 04:16 PM ---------- Previous post was at 04:12 PM ----------
Can someone comment on this?

avaie said:
Would this method work on the T-Mobile variant? Is there a fee [anywhere]?
---------- Post added at 04:16 PM ---------- Previous post was at 04:12 PM ----------
Can someone comment on this?
://youtu.be/nSeqIfQeWi4
Click to expand...
Click to collapse
No T-Mobile is not supported

avaie said:
Would this method work on the T-Mobile variant? Is there a fee [anywhere]?
---------- Post added at 04:16 PM ---------- Previous post was at 04:12 PM ----------
Can someone comment on this?
://youtu.be/nSeqIfQeWi4
Click to expand...
Click to collapse
Ainz is right. You'll end up with a brick if anything.

Confirmed working on my att variant. ? Thanks again for the great guide ?

pp342261 said:
Confirmed working on my att variant. Thanks again for the great guide
Click to expand...
Click to collapse
You are very welcome! Feel free to contact me if you run into any issues.
On the plus side, your b-slot is untouched throughout all of this, so you can use that to re-root or flash backups should something go wrong, or update. Enjoy the pie.

Xsavi said:
You are very welcome! Feel free to contact me if you run into any issues.
On the plus side, your b-slot is untouched throughout all of this, so you can use that to re-root or flash backups should something go wrong, or update. Enjoy the pie.
Click to expand...
Click to collapse
Will this work on the LG V40 International?

rmgibbs1861 said:
Will this work on the LG V40 International?
Click to expand...
Click to collapse
Yes it will.

rmgibbs1861 said:
Will this work on the LG V40 International?
Click to expand...
Click to collapse
One more question, How will further updates be done after cross flashing? Thank you!

rmgibbs1861 said:
One more question, How will further updates be done after cross flashing? Thank you!
Click to expand...
Click to collapse
By flashing System, Vendor, and boot.

Very confusing. Which variants of V40 this is going to work for?

How to get the v35 engineering bootloader on the phone the only method ive heard about is through octoplus jtag?

twoxa said:
Very confusing. Which variants of V40 this is going to work for?
Click to expand...
Click to collapse
Well it worked for all US Carriers except for T-Mobile

had my sprint v40 bootloader unlocked from octoplus and tried this cause i hate sprint SW (activation screen).it flashed everything from batch file fine but when i went to boot into twrp it booted into normal recovery with the rainbow circle "erasing" then rebooted into os but it was all korean and the android version was 8.1. wtf lol? trying it again now, yes im using "V40PIECONVERSION" not the stock one.

jass65 said:
had my sprint v40 bootloader unlocked from octoplus and tried this cause i hate sprint SW (activation screen).it flashed everything from batch file fine but when i went to boot into twrp it booted into normal recovery with the rainbow circle "erasing" then rebooted into os but it was all korean and the android version was 8.1. wtf lol? trying it again now, yes im using "V40PIECONVERSION" not the stock one.
Click to expand...
Click to collapse
Did you check to make sure you are on Slot A and not B? Becuase i remember when i had everything flashed the first time i tried to boot TWRP in Slot A and somehow ended up switching to Slot B

Ainz_Ooal_Gown said:
Did you check to make sure you are on Slot A and not B? Becuase i remember when i had everything flashed the first time i tried to boot TWRP in Slot A and somehow ended up switching to Slot B
Click to expand...
Click to collapse
thats what it ended up being. xSavi helped me out :good:

Hi guys,
I have a Sprint V40 bought off of Taobao that was rooted, sim unlocked, and crossflashed to US Cellular 11d but after I installed Pix3lify trying to get gestures on 8.1 I lost root. I don't seem to be able to get into fastboot, either with Vol- + cable or via adb, but I have an unlocked bootloader and I can get to download mode. Factory reset just reboots. Any tips as to how can I get root back, or upgrade to Pie? Can anybody please explain how to switch from slot a to slot b and vice versa?
Jeff