Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
me176c-boot is a custom, unlocked bootloader for the ASUS MeMO Pad 7 (ME176C(X)). Designed to be simple and flexible, it can boot into Android and/or Linux.
me176c-boot is a combination of systemd-boot (a simple UEFI boot manager) and android-efi (a simple Android bootloader).
Features
Boot into Android, Recovery and Fastboot
Unlocked bootloader, can boot into custom ROMs
Completely open-source and custom built for ASUS MeMO Pad (ME176C(X))
Flexible configuration to add further boot targets (e.g. Linux dual boot)
Download
Latest release: esp-0.3.0.zip
Older releases: Available on GitHub
Installation
Make sure that you are running Android 5.0 (Lollipop).
Download and unpack "esp.zip" from the latest release.
Make sure you have Fastboot installed.
Boot the tablet into Fastboot mode: On the stock ROM, press "Volume Down" + "Power", and release the "Power" button once the backlight turns on.
Connect the tablet to your PC, and verify that it shows up in "fastboot devices".
Flash the new EFI System Partition (ESP) extracted from the downloaded ZIP: "fastboot flash ESP esp.img"
Recommended: Configure the bootloader to use the stock charger for offline mode charging
Usage
By default, the bootloader will boot into the main Android system. You can recognize the bootloader by the green Android robot that is shown on boot.
Press "Volume Down" while booting to show the boot menu. Navigate through the menu with the "Volume Down" key. Press "Volume Up" to select an option. The "Power" button is not working inside the boot menu.
Configuration
You can access the (systemd-boot) configuration files from Recovery: go to "Mount" and select "EFI System Partiton (ESP)". Then you can access the ESP using ADB at "/esp".
Here are some links with more information how to configure the bootloader:
"systemd-boot" on ArchLinux Wiki
android-efi README ("android" boot type is supported in me176c-boot)
Booting from other partitions
There is an additional "volume" option in me176c-boot that allows booting from other partitions on the internal storage, based on their GPT partition UUID. The partition needs to be formatted as FAT32.
Examples
Using the stock charger (recommended)
Booting into main OS on charger insertion
Dual/multi boot (e.g. Android and Linux)
Limitations
The "BIOS" of the tablet can boot from the internal storage and USB(-OTG). It does not seem to be able to boot directly from external SD cards. However, it is possible to keep most of the system on the external SD card by placing only the kernel (the boot partition) on the internal storage.
The EFI System Partition (ESP) is severely limited in its size (only 16 MiB), which is usually not enough to keep more than one Linux kernel. That’s why me176c-boot supports booting from other partitions on the internal storage.
Setting up an additional ESP partition
There is an unneeded APD (ASUS Product Demo) partition on the tablet, which has a reasonable amount of storage (~300 MiB) and is therefore ideal as additional ESP partition. It contains a few demo product images/media files that are only used for the "demo mode" on the stock ROM.
Boot into TWRP recovery and make a backup of the "APD (ASUS Product Demo)" partition. Store in it a safe place in case you want to restore it.
Wipe the APD partition, and change its file system to FAT32.
Place the EFI application (e.g. Linux) on the APD partition, and use it in a boot target using the "volume" option:
Code:
# Partition UUID of the APD partition
volume 80868086-8086-8086-8086-000000000007
Troubleshooting
In some cases booting may fail or you make a mistake during the installation. In this case, first power off the tablet by holding the "Power" button until it turns off.
Recovery
Even with the bootloader entirely broken, you can still boot into Fastboot mode using the rescue mode ("DNX mode").
Download the stock ROM ("UL-K013-WW-12.10.1.36-user.zip")
Extract "esp.zip" and "droidboot.img" from the downloaded ZIP.
Extract "EFI/Intel/efilinux.efi" from "esp.zip".
Press "Volume Up" + "Volume Down" + "Power" until "Fastboot starting…" shows up on the display.
Connect the tablet to your PC, and verify that it shows up in "fastboot devices".
Code:
fastboot flash osloader efilinux.efi
fastboot boot droidboot.img
XDA:DevDB Information
me176c-boot - Custom, unlocked bootloader for ASUS MeMO Pad 7 (ME176C(X)), Tool/Utility for the Asus MeMO Pad 7
Contributors
lambdadroid
Source Code: https://github.com/me176c-dev/me176c-boot
Version Information
Status: Stable
Created 2018-04-20
Last Updated 2019-07-19
Version History
me176c-boot 0.3.0
lambdadroid said:
Tip: Using the ASUS stock charger for offline mode charging is a great way to be able to charge at any time, even when the current ROM is in a non-bootable state. It also charges a bit more efficiently than the LineageOS ROM.
me176c-boot 0.3.0 contains major improvements and new features in all three of its components. Some of the new features will be required for future versions of the LineageOS ROM, however, booting the stock ROM is still supported.
me176c-bootstrap 0.3.0:
Moved some device specific code from the kernel to the bootloader
Technical details: https://github.com/me176c-dev/me176c-acpi#global-nvs-area
android-efi 0.3.0:
Added option to load additional init ramdisks (initrd)
systemd-boot-me176c 241.0:
Updated to systemd-boot v241
Added custom "android" loader type that makes it possible to write nicer boot configurations using android-efi
Example: https://github.com/me176c-dev/android-efi#systemd-boot
Download: esp-0.3.0.zip
Note: Upgrading wipes all custom boot configurations. For example, if you have been using the stock offline charger option, you will need to re-install it after installing this update.
Click to expand...
Click to collapse
me176c-boot 0.2.0
lambdadroid said:
Redesigned charger detection: There is now an additional charger boot option that is automatically selected when the device is started due to charger insertion.
This allows customizing the boot target in this situation. Examples:
Boot into charger from stock ROM while having a custom ROM installed (in my experience it still charges slightly better with less heat): See "Using the stock charger".
Always boot into main OS: See "Booting into main OS on charger insertion"
android-efi 0.2.0:
Boot Android images from files instead of just partitions.
Pass additional kernel parameters
systemd-boot-me176c 239.0:
Boot images from other partitions on the internal storage.
This is mainly useful for dual booting, because the main EFI System Partition (ESP) is very limited in its size (only 16 MB).
Download: esp-0.2.0.zip
Note: Upgrading wipes all custom boot configurations. (You don't need to worry about this unless you have manually made changes to the bootloader configuration...)
Click to expand...
Click to collapse
me176c-boot 0.1.0
Download: esp-0.1.0.zip
Succesfully flashed the new bootloader.
The android logo is showing up and booting after that.
Scrolling throught the boot menu is also working!
Thanks for doing this!
wow. You have really outdone yourself here..... Considering this device didn't even had an untethered recovery at one point this is BIG!.... this opens up a lot more possibilities now for this tablet.... buddy you deserve recognition here
n30wav3 said:
wow. You have really outdone yourself here..... Considering this device didn't even had an untethered recovery at one point this is BIG!.... this opens up a lot more possibilities now for this tablet.... buddy you deserve recognition here
Click to expand...
Click to collapse
It really is impressive how far this device has come. For a long while I was willing to accept that despite the unlocked bootloader, we would be stuck with ZenUI for the future.
Hi, i try boot in TWRP - error Failed to execute recovery (\android.efi): Unsupported, reinstall TWRP - it s work
Skyrimus said:
Hi, i try boot in TWRP - error Failed to execute recovery (\android.efi): Unsupported, reinstall TWRP - it s work
Click to expand...
Click to collapse
So is everything working now? This could happen if you use a really old recovery and/or your (recovery) partition is corrupted.
will be possible to boot windows on the go (portable windows 10) from micro sd or a usb? maybe with a powered hub? (I made one with a normal hub, a diode and a usb cable and works as a charm)
f35suarezj said:
will be possible to boot windows on the go (portable windows 10) from micro sd or a usb? maybe with a powered hub? (I made one with a normal hub, a diode and a usb cable and works as a charm)
Click to expand...
Click to collapse
It's very much possible, but it won't work well at all due to the missing drivers.
errors flashing
I have root access on the tablet but believe the bootloader is still locked & i was trying to load your bootloader.
I am having issues.
When I press Volume Down & Power I do not get a recovery menu but rather the tablet boots in an Android Safe mode. There are a limited number of apps available and the table has the word "Safe mode" at the bottom of the screen.
If instead I press Volume Up & power i get a different menu that includes Normal Boot, Power Off, Reovery Mode then Restart Recovery
At the bottom of the tablet in Normal Boot it says "FASTBOOT CMD WAITING...."
I can see the tablet with fastboot devices but get errors when I try "fastboot flash ESP esp.img"
D:\Asus Memo Pad 7>fastboot flash ESP esp.img
target reported max download size of 536870912 bytes
sending 'ESP' (33792 KB)...
OKAY [ 1.601s]
writing 'ESP'...
FAILED (remote: flash_cmds error!
)
finished. total time: 2.401s
On the tablet it says :
NORMAL BOOT
FASTBOOT MODE
PRODUCT_NAME - K01A
VARIANT - K01A
HW_VERSION - (blank)
BOOTLOADER VERSION - unknown
IFWI VERSION - 64.33
SERIAL NUMBER - 0123456789012345678
SIGNING - ?
SECURE_BOOT - ?
FASTBOOT CMD WAITING.......
I do not remember how I rooted the tablet but obviously it cleared the serial number and input a new one.
Is there anything else I might provide that might allow you to assist me?
jziggy101 said:
I have root access on the tablet but believe the bootloader is still locked & i was trying to load your bootloader.
I am having issues.
When I press Volume Down & Power I do not get a recovery menu but rather the tablet boots in an Android Safe mode. There are a limited number of apps available and the table has the word "Safe mode" at the bottom of the screen.
If instead I press Volume Up & power i get a different menu that includes Normal Boot, Power Off, Reovery Mode then Restart Recovery
At the bottom of the tablet in Normal Boot it says "FASTBOOT CMD WAITING...."
I can see the tablet with fastboot devices but get errors when I try "fastboot flash ESP esp.img"
D:\Asus Memo Pad 7>fastboot flash ESP esp.img
target reported max download size of 536870912 bytes
sending 'ESP' (33792 KB)...
OKAY [ 1.601s]
writing 'ESP'...
FAILED (remote: flash_cmds error!
)
finished. total time: 2.401s
On the tablet it says :
NORMAL BOOT
FASTBOOT MODE
PRODUCT_NAME - K01A
VARIANT - K01A
HW_VERSION - (blank)
BOOTLOADER VERSION - unknown
IFWI VERSION - 64.33
SERIAL NUMBER - 0123456789012345678
SIGNING - ?
SECURE_BOOT - ?
FASTBOOT CMD WAITING.......
I do not remember how I rooted the tablet but obviously it cleared the serial number and input a new one.
Is there anything else I might provide that might allow you to assist me?
Click to expand...
Click to collapse
I'm afraid this package is for the ME176C (also named K013), not for the K01A. Now theoretically this doesn't mean anything, because the bootloader itself does not have any device specific code.
But given that you get an error trying to flash the "ESP" partition it is possible that your tablet never received the UEFI update (usually introduced with the update to Android 5.0). The bootloader only works on UEFI systems.
I've been having an overheating device and serious battery drain lately, is there any possibility it's related to this new bootloader? It's unlikely I know, just trying to eliminate all possible causes.
seamo123 said:
I've been having an overheating device and serious battery drain lately, is there any possibility it's related to this new bootloader? It's unlikely I know, just trying to eliminate all possible causes.
Click to expand...
Click to collapse
That's unlikely. The bootloader doesn't do much except load the kernel and then hands over all control to it. It doesn't run except very early in the boot process.
Wow, kudos. It's really nice how painless this was to install (and then to install the LineageOS you also provided)!
me176c-boot 0.2.0
Redesigned charger detection: There is now an additional charger boot option that is automatically selected when the device is started due to charger insertion.
This allows customizing the boot target in this situation. Examples:
Boot into charger from stock ROM while having a custom ROM installed (in my experience it still charges slightly better with less heat): See "Using the stock charger".
Always boot into main OS: See "Booting into main OS on charger insertion"
android-efi 0.2.0:
Boot Android images from files instead of just partitions.
Pass additional kernel parameters
systemd-boot-me176c 239.0:
Boot images from other partitions on the internal storage.
This is mainly useful for dual booting, because the main EFI System Partition (ESP) is very limited in its size (only 16 MB).
Download: esp-0.2.0.zip
Note: Upgrading wipes all custom boot configurations. (You don't need to worry about this unless you have manually made changes to the bootloader configuration...)
lambdadroid said:
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
me176c-boot is a custom, unlocked bootloader for the ASUS MeMO Pad 7 (ME176C/X). Designed to be simple and flexible, it can boot into Android and/or Linux (coming soon).
me176c-boot is a combination of systemd-boot (a simple UEFI boot manager) and android-efi (a simple Android bootloader).
Features
Boot into Android, Recovery and Fastboot
Unlocked bootloader, can boot into custom ROMs
Completely open-source and custom built for ASUS MeMO Pad (ME176C/X)
Flexible configuration to add further boot targets (e.g. Linux dual boot - coming soon)
Download
Latest release: esp-0.2.0.zip
Older releases: Available on GitHub
Installation
Make sure you are running Android Lollipop (5.0).
Extract esp.img from the downloaded ZIP.
Make sure you have Fastboot installed.
Boot the tablet into Fastboot mode: On the stock ROM, press "Volume Down" + "Power", and release the "Power" button once the backlight turns on.
Connect the tablet to your PC, and verify that it shows up when running "fastboot devices"
Flash the new EFI system partition extracted from the downloaded ZIP: "fastboot flash ESP esp.img"
Usage
By default, the bootloader will boot into the main Android system. You can recognize the bootloader by the green Android robot that is shown on boot.
Press "Volume Down" while booting to show the boot menu. Navigate through the menu with the "Volume Down" key. Press "Volume Up" to select an option. The "Power" button is not working inside the boot menu.
Configuration
It is possible to add additional boot targets using additional configuration files. You can access the configuration files from Recovery, go to "Mount" and select "EFI System Partiton (ESP)". Then you can access the ESP using ADB at /esp.
Here are some links with more information how to configure the bootloader:
systemd-boot on ArchLinux Wiki
android-efi README
Using the stock charger
You may want to use the stock ROM for (offline) charging since it charges a bit more efficiently (withless heat being generated). Ideally, this would be fixed directly in the custom ROM, but until then itis possible to configure the bootloader to use the stock boot image when booting into charging mode:
Download the stock ROM (UL-K013-WW-12.10.1.36-user.zip) and the updated charger boot configuration (charger.conf)
Extract boot.img from the downloaded ZIP.
Boot into Recovery, go to Mount and select EFI System Partition (ESP).
Connect the tablet to your PC, and verify that it shows up in adb devices.
Code:
adb push boot.img /esp/asus-charger.img
adb push charger.conf /esp/loader/entries/charger.conf
That’s it! When you plug in the charger the next time it should boot into the stock charger UI. Yay!
Booting into main OS on charger insertion
If you want to disable the separate charging mode on your tablet and always boot into the main OS,you can simply copy the primary boot configuration, and use it for the charger as well:
Boot into Recovery, go to Mount and select EFI System Partition (ESP).
Connect the tablet to your PC, and verify that it shows up in adb devices.
Download the configuration for your primary boot configuration (e.g. android.conf):
Code:
adb pull /esp/loader/entries/android.conf
Rename it to charger.conf.
Open it in a text editor and change the title to Charger.
Copy it back to your device:
Code:
adb push charger.conf /esp/loader/entries/charger.conf
Troubleshooting
In some cases booting may fail or you make a mistake during the installation. In this case, first power off the tablet by holding the "Power" button until it turns off.
Recovery
Even with the bootloader entirely broken, you can still boot into Fastboot mode using the rescue mode ("DNX mode").
Download the stock ROM (UL-K013-WW-12.10.1.36-user.zip)
Extract "esp.zip" and "droidboot.img" from the downloaded ZIP.
Extract "EFI/Intel/efilinux.efi" from "esp.zip".
Press "Volume Up" + "Volume Down" + "Power" until "Fastboot starting..." shows up on the display.
Connect the tablet to your PC, and verify that it shows up in "fastboot devices".
Code:
fastboot flash osloader efilinux.efi
fastboot boot droidboot.img
XDA:DevDB Information
me176c-boot - Custom, unlocked bootloader for ASUS MeMO Pad 7 (ME176C/X), Tool/Utility for the Asus MeMO Pad 7
Contributors
lambdadroid
Source Code: https://github.com/me176c-dev/me176c-boot
Version Information
Status: Beta
Created 2018-04-20
Last Updated 2018-09-24
Click to expand...
Click to collapse
For more than a week, I have been trying to reverse from lineage 14 to the asus firmware .36 whit TWRP 3.02.-0
. I get this error:
Could not find META-INF/com/google/android/update-binary in the zip file.
What im doing wrong?
RichardCooper said:
For more than a week, I have been trying to reverse from lineage 14 to the asus firmware .36 whit TWRP 3.02.-0
. I get this error:
Could not find META-INF/com/google/android/update-binary in the zip file.
What im doing wrong?
Click to expand...
Click to collapse
This is not related to me176c-boot, and it seems like you are not using one my TWRP builds either. Please open a separate thread here: https://forum.xda-developers.com/memo-pad-7/help
me176c-boot 0.3.0
Tip: Using the ASUS stock charger for offline mode charging is a great way to be able to charge at any time, even when the current ROM is in a non-bootable state. It also charges a bit more efficiently than the LineageOS ROM.
me176c-boot 0.3.0 contains major improvements and new features in all three of its components. Some of the new features will be required for future versions of the LineageOS ROM, however, booting the stock ROM is still supported.
me176c-bootstrap 0.3.0:
Moved some device specific code from the kernel to the bootloader
Technical details: https://github.com/me176c-dev/me176c-acpi#global-nvs-area
android-efi 0.3.0:
Added option to load additional init ramdisks (initrd)
systemd-boot-me176c 241.0:
Updated to systemd-boot v241
Added custom "android" loader type that makes it possible to write nicer boot configurations using android-efi
Example: https://github.com/me176c-dev/android-efi#systemd-boot
Download: esp-0.3.0.zip
Note: Upgrading wipes all custom boot configurations. For example, if you have been using the stock offline charger option, you will need to re-install it after installing this update.
Had zero issues getting it installed on my tablet. I look forward to seeing how linux runs on this as well! thanks
Succesfully flashed the latest esp and re-installed stock charging.
Thx!
Related
Fuhu Nabi General information
1. Introduction
It was only recently that the Nabi2 got it's own forum. This device has been out a couple of years so the information you may be looking for is spread all over XDA. The largest single chunk of information resides in the Nabi 2 Root and Gapps Install by jmz, the problem is that thread is now 265 plus pages and mostly impossible to search. What I find more troubling is that the methods in which we go about root, modding etc evolve over time and newer users are using methods and tools that are now obsolete and can create more issues then they solve. Also while the moderators have done a wonderful job, not every Nabi thread is here in this section of the forum so I wanted to link to those that are pertinent.
While this is a Nabi2 forum I personally find it a better use of this corner of XDA to discuss all Nabi products, and this information post will discuss them all. Nabi JR, Nabi 2 Original, Disney and Nick, Nabi XD, Nabi2S, Nabi Dreamtab(Intel and Nvidia) , Nabi BigTab 20" and 24".
Most of the discussion will be catering to Microsoft Windows users as it is the most common usage scenario. It also will be light on discussion of the Intel version of the Dreamtab as it quite different.
Also look at the wiki. Information is very dated but there is some useful stuff, be careful with what you are flashing as the wiki is more informational then current methods. I would recommend asking before using any of the scripts or programs. http://forum.xda-developers.com/wiki/Fuhu_nabi_2
2.Basics
With the exception of the Nabi Dreamtab by Intel (DMTAB-IN08A), all the Fuhu Nabi products are built on Nvidia Tegra2, Tegra3, or Tegra 4. Therefore most methods of modding, recovery, etc are similar with a few device specific difference. The main utility we use is a custom recovery called TWRP, if you have come from other devices you might have used CWM, Odin, and countless other utilities, TWRP will be accomplishing the tasks on the Nabi devices. All the Nabi's already have a "stock" recovery on the device. It is useful for taking OTA(updates) and factory resetting but it's limitations end there, and this is where the TWRP custom recovery will come in to play.
There are 4 modes of operation for Nabi's
Each mode offers different usage scenarios and you should familiar with what they look like and which one you are in.
-Android
-Recovery -
-Bootloader/Fastboot
-Forced recovery/nvflash/APX
Windows are driver can be a pain but necessary before you can do anything else
No matter which method you choose or need to use the Windows drivers must be installed on your computer before you can do anything, without getting that setup nothing else is going to matter.
Most mods, rooting, and recovering devices and are done by one of 2 methods.
-Tool/Script - This is usually done by a GUI/Command prompt tool where the user clicks a few buttons and the magic happens in the background
-Manually - This is getting the hands dirty method, typing command lines, moving and unzipping files and is unfortunately common as there aren't many of the tools/scripts mentioned above.
3. The 4 Operational Modes
1. Android Usage: ADB and File Transfer.
-The normal operational mode for the device, and why you bought the tablet. ADB is NOT enabled by default, you will need to turn it on to perform any ADB operations. To enable ADB on the device:
-Login to parent mode
-Open Settings and see if "Developer Options" is listed if not
------Go to "About tablet".
------Click on Builder Number 10 or so times.
------Eventually you will see developer options are enabled.
-Open Developer Options and turn them on in top right corner
-Check the box USB debugging
-When using ADB on newer software builds when you execute a command the first time you will need to authorize on the tablet the first time, you can prevent this pop up by checking the box to always trust your computer.
2. Bootloader Usage: Fastboot. Booting to recovery. Booting to nvflash. Installing TWRP or stock recoveries.
Allows selection of other 3 modes, and utilizing fastboot commands.
How to enter bootloader/fastboot mode:
Device powered off:
-Depending on device press and hold the power and vol - keys OR power and vol + key. Some will boot straight to recovery, and others will come to the "bootloader" screen. We want the bootloader.
-To enter fastboot use vol+ and vol- to highlight and select fastboot protocol. (Device will need to be plugged in to computer and fastboot driver installed before the screen will change)
Device powered on:
-Use ADB and execute from the command line: adb reboot-bootloader
3. Recovery Usage: ADB, File Transfer, Installing Mods and Root, Recovering backups, Recovering Device.
There are 2 different versions of recovery. "Stock" and "TWRP". Stock is what comes with your device, and can be identified by the "dead android" picture when it boots up. Stock recovery is rather limited so if you see the "dead android" know you have stock recovery on the device. The 2nd possible recovery is TWRP, and the one used for most things you will be doing. It should say Team Win Recovery Project, or TWRP when it boots up.
How to enter recovery mode:
Device powered off:
-Depending on device press and hold the power and vol - keys OR power and vol + key. Some will boot straight to recovery, and others will come to the "bootloader" screen.
-Use the vol + and - keys to select recovery kernel. (one key will highlight the selection and the other key will "select" what's highlighted)
Device powered on:
-Use ADB and execute from the command line: adb reboot recovery
4. Forced Recovery Usage: Last resort for recovering dead tablet, heavy duty modding.
Rarely used. Can modify tablet, and prevent bricks. Only useful on Nabi2 Original, Disney, and Nick.
How to enter forced recovery mode:
Device powered off:
-Depending on device press and hold the power and vol - keys OR power and vol + key. Some will boot straight to recovery, and others will come to the "bootloader" screen.
-Use the vol + and - keys to select forced recovery. (one key will highlight the selection and the other key will "select" what's highlighted)
-screen will be completely blank, you will also need a windows APX driver to communicate with device.
4. Drivers
The windows drivers are problematic. There can be conflicts with other drivers, or just not found for the Nabi, or 64bit driver signature enforcement. As previously mentioned to utilize almost any operation for modding/rooting etc. you must have the drivers installed. None of the manual methods or auto tools are going to work if you don't get this accomplished.
It most cases you will only need 2 drivers. ADB interface and Fastboot/Bootloader Interface. The 3rd will only be needed on the rare chance you need to use the APX interface. What is important to understand is your computer will only see the interface that is used depending on the "Operational Mode" the tablet is in. For example if you are in Android or Recovery your computer will see ADB interface but NOT the fastboot interface. If you are in the bootloader interface(and have selected fastboot protocol) you will see the fastboot interface and NOT the ADB interface. So to install both drivers, you will have to boot to Android or Recovery and install one driver and then the bootloader to install the other. The order in which you do this will depend on which operational modes are available to you depending on the health of the tablet. (The same would apply if you need to use Forced recovery, you will need to be in that mode to install the 3rd driver APX interface, again this is rare)
Device Manger is the best way to see what is happening. With your tablet plugged in to the computer open device manager and look for either yellow ! or ? or something under the tree for "Android Device". If you are seeing the yellow ! or ? for your device then likely the drivers are not installed.
There are a few drivers and methods that seem to work best for most users. One of the bigger issues is 64bit driver signature enforcement. Windows Vista,7,8, and 10 do not like to install drivers that aren't digitally signed. There are 3 drivers that I am going to recommend. 2 are digitally signed drivers and there other is not.
PDAnet: I really don't like recommending this but it seems to work in most scenarios. Remember your tablet will have to enter both modes to install both drivers and remember that ADB will not show up by default in Android unless you enable it(see the operational mode section above)
http://pdanet.co/a/
NabiLab drivers: These are digitally self signed by me. That will require rootCA to be installed. This could create a security risk if someone was to steal my signing key. If that worries you don't use them or uninstall the drivers and certificate when you are done.
http://forum.xda-developers.com/showpost.php?p=62826514&postcount=2639
Universal naked:
If you aren't technically savvy I would use these as last resort. It will require you to disable "windows driver signature enforcement"(google it because it depends on windows version). Extract the zip package. Enter device manager and find your device, and manually update driver by pointing to the folder you extracted the zip.
http://forum.xda-developers.com/showthread.php?t=2263822
5. Tools and Automated scripts.
There aren't a lot of current tools available. They have mostly aged beyond their usefulness. The reasons are quite a few.
1. As the Nabi's upgrades the Android software from Ice Cream Sandwich to Jellybean to KitKat, the bootloader also changes. This changes how TWRP is able to see the internal storage and usually it can't. An Ice Cream Sandwich bootloader needs to use a TWRP for that version. For example the original Nabi2 has 3 different TWRP versions for the 3 different bootloaders. A lot of the older tools were made with a TWRP that no longer will work with your device. This will show up as TWRP "unable to mount" errors, and therefore the tool/script will fail for that reason.
2. Gapps. Originally many Nabi devices didn't have a Google Play store option. A lot of the tools still work on that premise, but most Nabi's have Google Play now. Google Apps also change with the Android version. So the tools can make mods based on that old information will cause problems.
3. Super user. A lot of older tools with "root" scripts don't have a current super user(root) binary and daemon. Newer Android version need a more up to date Super User install. With this situation you won't cause as many problems but will not good root with the script like you expect.
I will try to keep the list somewhat up to date
4. Mods. Like above, the mods that change your screen and/or add functionality, are heavily dependent on your android version, and will usually make your tablet un bootable if using an incompatible one.
Taking that in to account it's important to realize using old tools will cause you more issues then using no tools at all. I will try to keep the list some what up to date but in general there aren't many still usable tools.
The only tool that is even somewhat current is NabiLabGUI 2015, it can deal with quite a few of the Nabi products, and is at least very good at troubleshooting and has a command line setup that you can use to follow other users command line suggestions.
Get it here. http://nabtabhacks.com/nabilabgui2015/publish.htm
Here is the thread for the OLD version of the program. http://forum.xda-developers.com/showthread.php?t=2391449
Remember none of these are going to work if you haven't set up the drivers
Nabi2 Original/Disney/Nick
Old software not to use: jmzroot package, Ubuntu install from scratch, original NabiLab(non GUI version), and most others.
Really just stick with NabiLab2015 if you need a automated solution.
NabiXD
The XD hasn't changed much so this probably still will work http://forum.xda-developers.com/showthread.php?t=2207499
Nabi JR
For the Tegra2 4GB NABI-NV5A(couple years old) NabiLab2015 can do some functions or this tool http://forum.xda-developers.com/showthread.php?t=2200119
For the Tegra3 16GB NABI-NV5B(also a couple years old) NabiLab2015 can do some functions.
For the newest NabiJR SNBJR-MT5C - Not much, no TWRP even available yet.
Nabi DreamTab Nvidia Edition
Latest installer http://forum.xda-developers.com/showpost.php?p=63151136&postcount=46
Nabi BigTabs
None
Nabi 2S(newer Nabi 2 tablet)
None
If the tools aren't working your are going to need to do it by hand. See next section.
6. Setting up to do it by hand
Remember none of this is going to work if you haven't set up the drivers. Putting it all together now, also recall that you must be in the right "Operational Mode" to use either fastboot or to use ADB.
First of all I should mention that NabiLabGUI2015 has an option to work from the command line and has a lot of this already setup but to start from scratch:
When you setup the drivers earlier you got a driver for ADB and a driver for fastboot. Now to then talk to those interfaces you will need software to do that. Specifically an ADB.exe and fastboot.exe.
-Download and install this package(pay attention to where you install this as you will likely need to put files in there later): http://forum.xda-developers.com/showthread.php?t=2317790
-From your start menu select "Minimal ADB and Fastboot" this should open a command prompt where you can type commands
-If you didn't pay attention or forgot where you installed the files, at the command prompt that opens type "explorer ." The period is important, explorer <space bar> and a period. So type what is between the quotes.
Now you can drop and drag, unzip, etc the files you need in to that folder. You are done with manual setup.
For nvflash setup(Only for Nabi2 Orig, Nick, Disney NOT 2S, this step won't normally ever be required, and is only here for completeness)
-Download the nvflash.zip attached to this post.
-Make a new folder in the same folder as above and call it nvflash
-Extract the contents of the nvflash.zip in to the nvflash folder
-At the command prompt type "cd nvflash" to change in to the folder and use nvflash
THIS IS STILL A WORK IN PROGRESS
7. Getting TWRP on the device
The most common form of using TWRP is to install to the recovery partition of your device. Remember on certain devices(Nabi2 for example) the version of TWRP you use has to match the bootloader on the device, and the bootloader "type" will almost always correlate to the version of Android you are/were using. So if your Android ROM is Kitkat, the bootloader will be KitKat and you should use the KitKat TWRP. There are various tools linked above in the tools and scripts section that can install TWRP automatically depending on device or you can also use "dd" from Android to install it. In this section the manual method of installing will be highlighted.
1) To load TWRP we will be in the fastboot operational mode(see section 3)
Device powered off:
-Depending on device press and hold the power and vol - keys OR power and vol + key. Some will boot straight to recovery, and others will come to the "bootloader" screen. We want the bootloader.
-To enter fastboot use vol+ and vol- to highlight and select fastboot protocol. (Device will need to be plugged in to computer and fastboot driver installed before the screen will change)
Device powered on:
-Use ADB and execute from the command line:
Code:
adb reboot-bootloader
2) USB plugged in and Fastboot/Bootoader Driver loaded(see section 4) verify with windows device manager if needed.
3) Download the TWRP zip file for your device from TWRP list below(see section 8)
4) Extract the file to the location your are running your command prompt(see section 6)
-The file will be called twrp-recovery.img or recovery.img
5) Depending on the name of the file in step 4, load TWRP by typing at the command prompt:
Code:
fastboot flash recovery recovery.img
or
Code:
fastboot flash recovery twrp-recovery.img
On some device the bootloader is "locked", without unlocking the bootloader TWRP cannot be loaded. Unlocking the bootloader will erase ALL personal data on the device. If you see a message like this when trying to load TWRP:
downloading 'recovery.img'...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.003s
You will need to unlock the bootloader with following command
Code:
fastboot oem unlock
OR
Code:
fastboot -i 0x0489 oem unlock
8. TWRP List and Downloads
Latest TWRP Recovery for all Nabi devices, download links, and discussion threads.
*Updated as of 04/19/2018*
Also see my AFH account https://androidfilehost.com/?w=files&flid=41986
Code:
[B][U]Nabi2 Original (NABI-NV7A)[/U][/B]
Ice Cream Sandwich TWRP 2.6.3[URL="http://forum.xda-developers.com/attachment.php?attachmentid=2586828&d=1392743412"] Download[/URL]
Jellybean TWRP 2.8.5[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3211498&d=1426404068"] Download[/URL]
KitKat TWRP 2.8.7[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3473994&d=1442276115"] Download[/URL]
Discussion Thread [URL="http://forum.xda-developers.com/showthread.php?t=2074501"]Link[/URL]
Code:
[U][B]Nabi2 Disney and Nick (NABI-NV7A-D or NABI-NV7A-N)[/B][/U]
Jellybean TWRP 2.8.5[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3211498&d=1426404068"] Download[/URL]
KitKat TWRP 2.8.7[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3473994&d=1442276115"] Download[/URL]
Discussion Thread [URL="http://forum.xda-developers.com/showthread.php?t=2074501"]Link[/URL]
Code:
[U][B]Nabi2S (SNB02-NV7A)[/B][/U]
KitKat TWRP 2.7.1[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3148865&d=1423018617"] Download[/URL]
Code:
[B][U]Nabi JR A (Tegra2 4GB, NV5A)[/U][/B]
TWRP 2.6.3[URL="https://androidfilehost.com/user/?w=settings-dev-files&flid=44896"] Download[/URL]
Discussion Thread [URL="http://forum.xda-developers.com/showthread.php?t=2200119"] Link[/URL]
Code:
[B][U]Nabi JR B (Tegra3 16 NV5B)[/U][/B]
TWRP 2.6.3[URL="https://androidfilehost.com/user/?w=settings-dev-files&flid=44897"] Download[/URL]
Discussion Thread [URL="http://forum.xda-developers.com/showthread.php?t=2391468"] Link[/URL]
Code:
[B][U]Nabi JR New (SNBJR-MT5C)[/U][/B]
None - Work in progess
Code:
[B][U]Nabi XD (NV10A)[/U][/B]
TWRP 2.8.5[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3171414&d=1424242604"] Download[/URL]
Discussion Thread [URL="http://forum.xda-developers.com/showthread.php?t=2207459"] Link[/URL]
Code:
[B][U]Nabi Dreamtab Nvidia NV08B[/U][/B]
TWRP 3.0.0[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3692992&d=1458705735"] Download[/URL]
Discussion Thread [URL="http://forum.xda-developers.com/android/development/recovery-twrp-2-7-1-0-nabi-dreamtab-hd8-t2813917"] Link[/URL]
Code:
[B][U]Nabi Dreamtab Intel IN08A[/U][/B]
Tethered CWM recovery see here: [URL="http://forum.xda-developers.com/showpost.php?p=57825022&postcount=25"]Link[/URL]
Discussion Thread [URL="http://forum.xda-developers.com/android/development/recovery-twrp-2-7-1-0-nabi-dreamtab-hd8-t2813917"] Link[/URL]
EDIT 11/5/2019 Might be a recovery download mirror Download
Discussion Thread Link[/CODE]
Code:
[B][U]Nabi BigTab NV24A[/U][/B]
No TWRP - Working in progress, the TWRP for the NV20A 20" BigTab can bring up ADB
Discussion Thread [URL="https://forum.xda-developers.com/nabi-2/general/nabi-nabi-se-discussion-thread-t3770816"] Link[/URL]
Code:
[B][U]Nabi SE[/U][/B]
TWRP 3.0.2 [URL="https://github.com/huckleberrypie/device_Mattel_NabiSE/releases"] Downlaod[/URL]
Discussion Thread [URL="https://forum.xda-developers.com/nabi-2/general/nabi-nabi-se-discussion-thread-t3770816"] Link[/URL]
9. Recovering Bricked Devices
In this section we will go over recovery from non booting devices. I would classify non booting as one of three situations.
1) Tablet is being used normally and one day it has crashed or when restarted sits at the bootamination(spinning Nabi logo, Dreamworks characters)
If you haven't been doing anything but using the tablet normally then the most likely culprit is that some file is corrupt on the data partition. While there are ways to replace just that file if you suspect which one it is the simple solution is to try and wipe the data partition and start fresh. There are two ways to accomplish this:
a) Use the stock recovery if you haven't installed TWRP or haven't unlocked the bootloader. Boot the stock recovery using "recovery" in Section 3 above. Press both vol+ and vol - and the same time and you should get a menu where you can select to factory reset. This wipes ALL data from the tablet. When complete try to boot the tablet.
b) Use TWRP recovery from section 7 above. TWRP will give you some flexibility in that you can back up the data partition before you wipe it(in case the issue wasn't actually the data partition you can restore the data back), and TWRP will not delete "internal storage" if you do a factory reset.
-Boot TWRP
-<optional> Backup data partition to EXTERNAL sdcard(be safe and back up to external card not internal)
-<optional> While connected to computer backup the remaining files on the "internal sd" with windows explorer(Device should show up as an MTP device on later TWRP versions)
-Select Wipe tab and factory reset
2) You have installed a mod, installed a root application that has made a system modification, installed a zip file, or were just playing around swiping and wiping things in TWRP. Sometimes this will appear the same as above with a bootloop and boot animation that goes on forever.
a) Download the ROM for your device in section 10
b) Boot to TWRP (see above for instructions)
c) Do a backup of just the boot partition in TWRP.
- Click Backup tab
- Just check "boot" and nothing else.
- Swipe to Backup
d) Eject the external SD from the tablet and place in the computer
- Note: You should unmount the card from the mount tab in TWRP before ejecting it. (Uncheck the box next to external SD)
e) Connect the SD card to you computer
f) On the SD card navigate to the folder TWRP/BACKUPS/XXXX. XXX is a serial number unique to your Nabi.
g) Make a new folder and call in whatever you want. So it should now look like TWRP/BACKUPS/XXX/yourfolder
h) Unzip the ROM file you downloaded in to the "yourfolder" you created above. The files should look like ext4.system.win, emmc.boot.win, ext.addon.win, etc. Inside the the "yourfolder" directory.
i) Download the bootloader zip for your device from section 10
j) Copy it to the external SD in a location you will remember. This will be for the bootloader update.
k) Eject the SD card from your computer (safely eject it)
l) Install SD card in Nabi
- After inserted in tablet go to TWRP mount tab and check the box to mount the SD card
m) Go to restore tab, and find the backup under the "yourfolder" you made and unzipped the files to.
n) You should be able to select boot, system, and addon and skip the others.
o) If everything restores then go to TWRP install tab, find the bootloader.zip you downloaded and install it.
p) Reboot
10. ROM List and Downloads
Also see my AFH account https://androidfilehost.com/?w=files&flid=41986
Code:
[B][U]Nabi2 Original (NABI-NV7A)[/U][/B]
KitKat 3.0.13 ROM[URL="https://www.androidfilehost.com/?fid=24052804347843199"] Download[/URL]
ROM Mirror [URL="http://www.nabtabhacks.com/downloads/3013stock.zip"] Download[/URL]
Bootloader [URL="https://www.androidfilehost.com/?fid=24269982087011778"] Download[/URL]
Code:
[U][B]Nabi2 Disney(NABI-NV7A-D)[/B][/U]
KitKat 3.0.4 ROM[URL="https://www.androidfilehost.com/?fid=24052804347843201"] Download[/URL]
ROM Mirror[URL="http://www.nabtabhacks.com/downloads/304D.zip"] Download[/URL]
Bootloader [URL="https://www.androidfilehost.com/?fid=24269982087011793"] Download[/URL]
Code:
[U][B]Nabi2 Nick (NABI-NV7A-N)[/B][/U]
KitKat 3.0.5 ROM[URL="https://www.androidfilehost.com/?fid=24052804347843202"] Download[/URL]
ROM Mirror[URL="http://www.nabtabhacks.com/downloads/305N.zip"] Download[/URL]
Code:
[U][B]Nabi2 Original United Kingdom (NABI-NV7A-UK)[/B][/U]
Version 2.3.2[URL="https://www.androidfilehost.com/?fid=24269982087011751"] Download[/URL]
ROM Mirror[URL="http://www.nabtabhacks.com/downloads/232UKstock.zip"] Download[/URL]
Bootloader [URL="https://www.androidfilehost.com/?fid=24269982087013995"] Download[/URL]
Code:
[U][B]Nabi2S (SNB02-NV7A)[/B][/U]
KitKat 2.0.141107[URL="https://www.androidfilehost.com/?fid=24052804347850076"] Download[/URL]
Mirror[URL="http://www.nabtabhacks.com/downloads/2_0_141107stock.zip"] Download[/URL]
Bootloader [URL="https://www.androidfilehost.com/?fid=24269982087011808"] Download[/URL]
Code:
[B][U]Nabi JR A (Tegra2 4GB, NV5A)[/U][/B]
Latest Stock ROM[URL="https://www.androidfilehost.com/?fid=24052804347850083"] Download[/URL]
Mirror [URL="http://www.nabtabhacks.com/downloads/njr1stBACKUP.rar"] Download[/URL]
Bootloader: None
Code:
[B][U]Nabi JR B (Tegra3 16 NV5B)[/U][/B]
Latest Stock ROM[URL="https://www.androidfilehost.com/?fid=24052804347850077"] Download[/URL]
Mirror [URL="http://www.nabtabhacks.com/downloads/JRB.zip"] Download[/URL]
Bootloader: None
Code:
[B][U]Nabi JR New (SNBJR-MT5C)[/U][/B]
None - Work in progess
Code:
[B][U]Nabi XD (NV10A)[/U][/B]
EDIT 11/5/2019 ROM Mirror[URL="https://androidfilehost.com/?fid=24269982087013990"] Download[/URL]
Discussion Thread [URL="http://forum.xda-developers.com/showthread.php?t=2207459"] Link[/URL]
Bootloader: None
Code:
[B][U]Nabi Dreamtab Nvidia NV08B[/U][/B]
1312 ROM[URL="https://www.androidfilehost.com/?fid=24269982087013911"] Download[/URL]
ROM mirror [URL="http://www.nabtabhacks.com/downloads/1312stock.zip"] Download[/URL]
Bootloader[URL="https://www.androidfilehost.com/?fid=24269982087013988"] Download[/URL]
Code:
[B][U]Nabi Dreamtab Intel IN08A[/U][/B]
EDIT 11/5/2019 from some files I found.
Maybe a ROM backup [URL="https://www.androidfilehost.com/?fid=24533100289589801"] Download [/URL]
[STRIKE]Tethered CWM recovery see here: [URL="http://forum.xda-developers.com/showpost.php?p=57825022&postcount=25"]Link[/URL]
Discussion Thread [URL="http://forum.xda-developers.com/android/development/recovery-twrp-2-7-1-0-nabi-dreamtab-hd8-t2813917"] Link[/URL]
Code:
[B][U]Nabi BigTab NV20A[/U][/B]
TWRP 2.8.1 [URL="https://www.dropbox.com/s/p1gh6oo34sgbwri/recovery.img?dl=0"] Download[/URL]
Discussion Thread [URL="http://forum.xda-developers.com/android/help/24-tab-hd-powered-nabi-rooting-t2932197"] Link[/URL]
Code:
[B][U]Nabi BigTab NV24A[/U][/B]
No TWRP - Working in progress, the TWRP for the NV20A 20" BigTab can bring up ADB
Discussion Thread [URL="http://forum.xda-developers.com/android/help/24-tab-hd-powered-nabi-rooting-t2932197"] Link[/URL]
[/STRIKE]
One last post for misc and other
nabi dream tab
hello I have a nabi dream tab that dead and wont boot i follow thw instruction in the forums and re install the stock rom
and boot loader. everything was successful but the tablet still wont boot up its stuck on powered by android
any advice please
Suck4 said:
hello I have a nabi dream tab that dead and wont boot i follow thw instruction in the forums and re install the stock rom
and boot loader. everything was successful but the tablet still wont boot up its stuck on powered by android
any advice please
Click to expand...
Click to collapse
Which ROM did you reinstall? What version 1.3.7, 1.3.12? Have you tried doing a tablet wipe/factory reset?(obviously you will lose everything on the tablet)
Nabi dream tab
aicjofs said:
Which ROM did you reinstall? What version 1.3.7, 1.3.12? Have you tried doing a tablet wipe/factory reset?(obviously you will lose everything on the tablet)
Click to expand...
Click to collapse
I tried both the 1.3.7 and 1.1.12 with boot loader 137 and still no success..
Before I did all that reading and trying I first tried the factory reset but the tablet still didnt boot so i went on to use the twrp tool and follow the instruction here in the forums but still no luck..
I also did some further research and from what i understand it appears that the firmware is what i need to flash so i open up the tablet and try to use the board id and processor type to find it but no luck.. (not sure if i needed to do that but since the twrp didnt work i tried another method) its the dream tab NVO8B..
t
All very nice, but will there ever be tips for doing this stuff on Linux? We do not run MSWin in our household. Granted, it will probably be a few months before I once again try rooting/flashing the Nabi2S, so there's time for the Linux methods to come out if they ever do.
Suck4 said:
I tried both the 1.3.7 and 1.1.12 with boot loader 137 and still no success..
Before I did all that reading and trying I first tried the factory reset but the tablet still didnt boot so i went on to use the twrp tool and follow the instruction here in the forums but still no luck..
I also did some further research and from what i understand it appears that the firmware is what i need to flash so i open up the tablet and try to use the board id and processor type to find it but no luck.. (not sure if i needed to do that but since the twrp didnt work i tried another method) its the dream tab NVO8B..
t
Click to expand...
Click to collapse
I'd be interested if it helped to format system and data in TWRP before the restore next time.
jelabarre59 said:
All very nice, but will there ever be tips for doing this stuff on Linux? We do not run MSWin in our household. Granted, it will probably be a few months before I once again try rooting/flashing the Nabi2S, so there's time for the Linux methods to come out if they ever do.
Click to expand...
Click to collapse
Most of the time the commandine stuff is still the same when it comes to fastboot or adb. A lot of the scripts are easy to modify for linux.
Android keeps restoring all apps
I've got the NabiLab 2015gui, wiped and restored the Nabi2 to 3.0.13, installed twrp through it. I've flashed to the MinimalNabiWipe.zip, and rebooted and it goes right back to please wait while android updates 117 apps. I also can't get it to accept the changes recommended at trendblog.net/fix-kitkat-sd-card-write-restriction/ (which I had found while reading through 50+ of the most recent pages in the Nabi 2 Root and Gapps Install thread, it throws a generic error that it couldn't save. Any ideas?
damfn said:
I've flashed to the MinimalNabiWipe.zip, and rebooted and it goes right back to please wait while android updates 117 apps.
Click to expand...
Click to collapse
I would check to see if you have .odex files that are orphaned. If minimalnabiwipe.zip deleted the .apk and leaves behind the associated .odex file what you describee will happen.
damfn said:
I also can't get it to accept the changes recommended at trendblog.net/fix-kitkat-sd-card-write-restriction/ (which I had found while reading through 50+ of the most recent pages in the Nabi 2 Root and Gapps Install thread, it throws a generic error that it couldn't save. Any ideas?
Click to expand...
Click to collapse
Make sure /system is mounted read AND write?
aicjofs said:
I would check to see if you have .odex files that are orphaned. If minimalnabiwipe.zip deleted the .apk and leaves behind the associated .odex file what you describee will happen.
Click to expand...
Click to collapse
Can you point me in the direction of the .odex file locations? As I did a look around all the folders I could find in twrp and couldn't find .odex.
aicjofs said:
Make sure /system is mounted read AND write?
Click to expand...
Click to collapse
You are correct, I ended up removing "es file manager" and installing "total commander file manager" as it would do it for me.
hi all
I appreciate the awesome write up to help get this done.
I am having trouble, though. I am going thru nabilabgui. I get as far as rebooting below and then nothing happens when I hit a key. It appears that the nabi also freezes on reboot. Not sure what is going on. I tried going thru the manual method and seem to be confused.
Anyway, I would be happy to provide more details to help with this. Any help is appreciated, thank you.
******** Install Recovery and Root for JB and KK ********
Make sure device is connected and detected. Press any key.
Press any key to continue . . .
# Rebooting device
# If stuck here drivers are not installed
< waiting for device >
sending 'recovery' (8176 KB)...
OKAY [ 2.115s]
writing 'recovery'...
Press any key to continue . . .
OKAY [ 1.571s]
finished. total time: 3.686s
Press any key to continue . . .
# If writing recovery OKAY is stated above
# Press VOL - button on device until bootloader is selected
# Push VOL + to select.
# Press VOL - button on device until recovery kernel is selected
# Push VOL + to select.
# Press enter when you see TWRP has booted
Press any key to continue . . .
Press any key to continue . . .
# Pushing root to your device
# Ignore external SD card error if you have none installed
# This will take a few minutes. Wait.
mount: mounting /external_sdcard on vfat failed: No such file or directory
5580 KB/s (4017098 bytes in 0.703s)
0 KB/s (25 bytes in 1.000s)
# Rebooting recovery to flash gapps and root rom.
# Please wait until backup and install has been completed
# Once it has completed hit enter
Press any key to continue . . .
aeneas3 said:
hi all
I appreciate the awesome write up to help get this done.
I am having trouble, though. I am going thru nabilabgui. I get as far as rebooting below and then nothing happens when I hit a key. It appears that the nabi also freezes on reboot. Not sure what is going on. I tried going thru the manual method and seem to be confused.
Anyway, I would be happy to provide more details to help with this. Any help is appreciated, thank you.
******** Install Recovery and Root for JB and KK ********
Make sure device is connected and detected. Press any key.
Press any key to continue . . .
# Rebooting device
# If stuck here drivers are not installed
< waiting for device >
sending 'recovery' (8176 KB)...
OKAY [ 2.115s]
writing 'recovery'...
Press any key to continue . . .
OKAY [ 1.571s]
finished. total time: 3.686s
Press any key to continue . . .
# If writing recovery OKAY is stated above
# Press VOL - button on device until bootloader is selected
# Push VOL + to select.
# Press VOL - button on device until recovery kernel is selected
# Push VOL + to select.
# Press enter when you see TWRP has booted
Press any key to continue . . .
Press any key to continue . . .
# Pushing root to your device
# Ignore external SD card error if you have none installed
# This will take a few minutes. Wait.
mount: mounting /external_sdcard on vfat failed: No such file or directory
5580 KB/s (4017098 bytes in 0.703s)
0 KB/s (25 bytes in 1.000s)
# Rebooting recovery to flash gapps and root rom.
# Please wait until backup and install has been completed
# Once it has completed hit enter
Press any key to continue . . .
Click to expand...
Click to collapse
You don't mention what device you have? I'm guessing Nabi2 of some sort, which particular model? Judging by the log it seemed to have written recovery, at which point is it hanging? The way I had to write it as windows app and emulating a command window(so if I ever stopped updating the GUI program someone could edit the batch files on the backend to do what they needed) I couldn't find a good way to end the script very gracefully(I'm not very strong at that language), but it looks like it finished normally.
aicjofs said:
You don't mention what device you have? I'm guessing Nabi2 of some sort, which particular model? Judging by the log it seemed to have written recovery, at which point is it hanging? The way I had to write it as windows app and emulating a command window(so if I ever stopped updating the GUI program someone could edit the batch files on the backend to do what they needed) I couldn't find a good way to end the script very gracefully(I'm not very strong at that language), but it looks like it finished normally.
Click to expand...
Click to collapse
sorry, nabi 2. thanks! so the next step would be flashing a rom?
It hangs at the end of the text there.
"# Rebooting recovery to flash gapps and root rom.
# Please wait until backup and install has been completed
# Once it has completed hit enter
Press any key to continue . . .'
Thank you. And the program is awesome, no need for apologies about how it ends!
i try restore to stock my nabi XD
i try flash nabi XD with rom stock, 15stock.zip in twrp and faild and to restore as backup, It is restored only well and stays in the logo.
help
my whatsapp +18097191879:crying::crying::crying::crying:
sergioagilp said:
i try flash nabi XD with rom stock, 15stock.zip in twrp and faild and to restore as backup, It is restored only well and stays in the logo.
help
my whatsapp +18097191879:crying::crying::crying::crying:
Click to expand...
Click to collapse
Are you trying to flash("install") the zip or extract the zip(system.win, etc) and restore? I'm not sure which part is failing for you. Which TWRP version?
Did you also do a factory reset after the flash?
Any one have scatter file I'm in twrp but it cannot mount any thing it says internal disc as zero I need to format it but cannot as Windows does not see it so if I use a scatter file try and flash it so flash tools
Any chance there will support for the Nabi Jr (new) soon? I made mistake of buying 2 from Amazon on t assumption that they were completely "hackable".
LOG IN Issue: It's Nabi 2 Demo Device I guess
Dear XDA friends,
This is Zeeshan from Pakistan. Few days back I purchased a used*Nabi 2 from*the local market here in Pakistan. The salesman gave this password to enter*into*the mommy/daddy mode "zxcv6789" which was working perfectly fine.
Then I thought of creating my own nabi account to enhance my daughter's Nabi experience. I registered through my own email ID,*which have*been working fine . However lately I decided to factory reset the Nabi 2 to improve its speed and performance, here is where I have been stuck from last so many days.
After the hard factory reset the tablet did not ask for setting up my Nabi account but it automatically logged in to the nabi mode and now when I try to login into to the mommy mode it says your password is incorrect, when I click on the forgot password link it says "An email has been sent to you. Please allow a few minutes for* delivery. ([email protected])" which seems to be nabi's own email ID and I am in a doubt that this device could be a store demo unit however when I purchased and before the factory reset it was working like a normal one, no demo nothing.
How can I fix this issue to login to Nabi 2 using my own registered email ID.
Following are the details of my Nabi2 device:
About this nabi
Account: [email protected]
Model No: NABI2NV7A-D
Android Version: 4.0.4
Build Number: IMM76L
Product Version: 1.9.23
Many thanks in advance.
Looking forward to any help.
Dear everyone,
I have an ASUS MeMoPad 10 (ME103K) here which I vowed to fix. The user wanted to revert to Factory Defaults, lost power or something like this, and ended up with a bricked device.
I can only start it with power button + volume up, into Fastboot. Secure Boot is enabled.
I have Android SDK and minimal FastBoot installed. Have the Google USB Drivers on my desktop.
I tried flashing SuperBoot (ADB), but ADB simply lists "Waiting for Device". No devices can be listed. It does show up in Windows Device Manager: ASUS Android Bootloader Interface.
I have the following files available:
- SuperBoot r5
- Kernel: l-8064-r1_V12.16.1.12-201508071139-foss.tar
- UL-K01E-WW-12.16.1.12-user
- recovery-original-me103k
There is apparently no recovery.img for this device. The boot.img is in the UL-K01E-WW-12.16.1.12-user file
Power = ASUS logo then goes black
Power + Volume up = Fastboot
Power + Volume down = /
Power + Volume up+down = /
Is this the place I should be looking? I'm honestly not sure if I can catch up with the details: android.stackexchange.com/questions/124344/trying-to-flash-a-system-img-i-took-with-dd-failing
Any help would be much appreciated!
- Al
EDIT:
fastboot devices now detects #serialnumber
Alright, fastboot now detects my device. I installed PDANet which didn't do anything, and then downloaded another adbfastboot package which hit it.
I'm able to start writing boot.img, but that's what it stays at. It's an 8MB file, so it shouldn't take half an hour, I suppose?
I'm not getting any error message either, though.
EDIT: It seems that regardless of what commands I send, they stall and don't get executed. ADB doesn't seem to find any devices, only Fastboot does.
EDIT 2: Tried the same on my laptop. Different ports. Nothing goes further than for example "Writing 'boot' - that's it.
Bump (won't bump until tomorrow late)
B0mp
kab0mp
boink
Bwamp
Recover Asus Me103k (k01e)
1) Stock recovery:
View attachment k01e_stock_recovery.zip
3) Run it without flash:
Code:
fastboot boot k01e_stock_recovery.img
3) In recovery select to install UL-K01E-WW-12.16.1.12-user.zip (early placed on microsd)
4) Also can check boot ability:
Extract boot.img from update firmware zip UL-K01E-WW-12.16.1.12-user
And run it from fastboot:
Code:
fastboot boot boot.img
If Android loaded normaly after it, but after reboot you see FASTBOOT MODE, than execute this commands:
Code:
fastboot oem reset-dev_info
fastboot reboot
Asus MeMo pad ME103K/K01E bootloader unlock
sheinbo said:
Hi,
after all these years I remembered my asus memo... Such a fine displsay but ... . I discovered an unofficial rom for another old device ( samsung gt 5830) and so I'd like to ask you whether you know any possibility to "upgrade" the MeMo or any other way to pitch / patch it. Your reply here let me think that you are very attached to asus memo, maybe you are still interested.
Click to expand...
Click to collapse
Same here, running the device on Lollipop is awfully slow, KitKat is somewhat better though but those are the only two official ROM's which can be found and installed.
Tried to unlock the bootloader to try different ROM's but bootloader is locked, despite all info here on XDA, nothing seems to work and the bootloader remains locked. Unlock APK's also give no result.
Running out of options here, any suggestions will be appreciated.
There are a number of generic installation guides for custom roms eg https://www.xda-developers.com/how-to-install-custom-rom-android/
However this one is specifically for the LG G6 and tested using the US997 model. It worked for me, but I welcome comments on how to improve it.
Create a folder on the PC for all the downloads and files
Download phone driver from LG website
https://www.lg.com/us/support/help-library/lg-mobile-drivers-and-software-CT10000027-20150179827560
Download ADB/Fastboot https://developer.android.com/studio/releases/platform-tools (You need to unzip once downloaded)
(I had an error "adb server version (31) doesn't match this client (41) killing". I searched my PC and found an older version which I had used for another phone and deleted the folders and reinstalled from the download)
Ensure the phone is backing up. (Google backup is working, you have all your photos music etc downloaded) the next steps will wipe the phone
Remove the PIN/Password/Fingerprints from the phone so it will boot without any security.
Unlock the bootloader
https://developer.lge.com/resource/mobile/RetrieveBootloader.dev
The phone will then reboot and do a complete wipe so you need to wait a while for Android to setup.
Telegraph has the latest news on LG G6 ROMs and Recovery. From here I got the links for SHRP recovery which seems more up to date for LG G6 than TWRP. (https://web.telegram.org/#/[email protected])
https://sourceforge.net/projects/pa-g6/files/Releases/SHRP/20.07.2020/US997/
I named the downloaded file "recovery" (You need the .img file not the ZIP)
There are lots of active ROMS for LG G6 I have Lineage installed on another phone which works really well, but Havoc seems the most popular on the G6.
Download the ROM and Gapps https://opengapps.org/ (I used Nano, remember G6 is 64bit)
You will also need to update the bootloader. This was the latest I found for the US997
https://androidfilehost.com/?fid=1899786940962575226
(I missed the bootloader the first time and Gapps will not flash, I was helped by the LG G6 community on Telegram https://web.telegram.org/#/[email protected])
Now you have downloaded all you need
Then connect the phone to the PC and ensured you have ADB debug on in developer options and boot the phone into fastboot
On the PC open a command prompt in the folder you have all the files:
adb reboot bootloader
To load the recovery to the phone :
Fastboot flash recovery recovery.img
YOU MUST NOW BOOT DIRECTLY TO RECOVERY. Do not reboot to Android as this will automatically reset recovery to the stock version.
Unplug the USB cable and reboot to recovery (hold volume down + power button).. continue holding until phone reboots...
As soon as you see the LG logo on the screen.. let go of the power button then quickly press it again (never letting go of volume down).
Keep holding until you see the Factory Reset screen. Click thru the factory reset screens using the volume buttons to move up/down and power button to select. Choose "Yes" twice (saying you want to reset the phone it should boot into your new recovery. Despite what the screen says it won't actually factory reset/wipe your data... as long as you've installed a custom recovery and have not booted into Android since then.
Most likely you will be asked the password to decrypt the data folder. I tried my phone PIN and other default passwords suggested on the internet. I eventually found that this is a known issue and you need for cancel out of this screen and go and "FORMAT DATA"
Reboot directly to recovery (select reboot recovery in Skyhawk), this time you should not be asked for the decryption password.
I recommend you backup your current setup before making changes. If you hit issues you can use the recovery to restore. My SD card slot is broken (Poor LG design) so I plugged a USB thumb drive into the USB C slot and did a full backup. (No data since I just formatted it).
Wipe the partitions before you flash
Full wipe ("The only option you ever need")
Select Advanced and wipe system partition.
FLASH (You need to put the ZIP files either on the USB drive as I did, or copy to your SD card, or you can use ADB sideloader from the PC to push the files to the phone). The USB drive seems the easiest since you can plug it into your PC to load the files then plug it into the phone to read them.
Flash in the following order
Bootloader
ROM
Gapps
After Installing wipe cache and Davik
Reboot
It will do lots of processing while setting up. Ensure it stays cool (remove case and leave it plugged in with the screen off)
Donate to the developer of your new ROM at the end when it works.
I have been running my LG G6 on Android 10 for a few weeks and thought I would share my observations, I am using Havoc 3.7 installed with Skyhawk, I did not root the phone.
Likes : Very smooth experience, phone feel like it is running much faster. Very stable, I had one surprise reboot in the time I have used it. No issues (so far) with installing or using any apps including banking. Much lower use of storage, I have 6GB free.
Same : Battery life is about the same as before.
Gaps : Cannot encrypt, VOLTE doesn't work (which may become a big issue for T-Mobile and AT&T soon), when being used the phone gets much warmer than it did before and the wifi setting randomly turns off.
Next Steps: I am going to try Lineage which has released some fixes for the WIFI issue and report back.
I'm trying to follow the instructions as per this guide for the tmo version of G6 (H87220g) and I'm running into a roadblock on the recovery flash:
[[email protected] tmp]$ mkdir skyhawk
[[email protected] tmp]$ cd skyhawk && 7z x ../SHRP_v2.3.2_us997-233920072020.zip
[[email protected] skyhawk]$ fastboot flash recovery recovery.img
Sending 'recovery' (36936 KB) OKAY [ 1.252s]
Writing 'recovery' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Click to expand...
Click to collapse
I downloaded the Skyhawk zip from the PA download link, unzipped it and used the recovery.img file found inside the zip as part of the fastboot command. Is this incorrect ?
Yes, you need the recovery.img file to flash via fastboot. Have you successfully unlocked the boot loader? You cannot replace recovery without unlocking.
You also need to ensure you have the appropriate files for your phone I have a US997 but as you have H872 you would need skyhawk for the H872 in the notes above you are still using US997.
bootloader is unlocked as per:
https://forum.xda-developers.com/tmobile-g6/how-to/unlock-bootloader-tmo-t3578099
fastboot flash is failing and I'm not the only one it seems like based on comments here and reddit...
I gonna try out @runningnak3d guide and see if that works...
This guide is for the US997. The H872 has a much more complicated process to install recovery : https://forum.xda-developers.com/tmobile-g6/how-to/root-h872-to-including-11g-t3775518
I tried the following:
1. Unlock my bootloader by enabling developer options, enabling OEM unlock, power off the device, hold VOL+ and VOL- simultaniously while connecting a USB cable, and enabling the unlock.
A factory reset was triggered as described in various tutorials.
2. I set the A50 (SN-A505FN/DS) up without Google or Samsung Details.
3. I check, wether the OES unlock was still intact, which it was.
4. I enabled USB debugging and made sure my PC was allowed to do send adb commands.
5. I typed: adb reboot [fastboot, download] (tried both on macOS, Windows and Linux, drivers were installed on Windows via Kies, Samsung Switch and the download package)
6. In the download menu I typed: [fastboot, .\fastboot.exe] flash system <various images derived here: https://www.gadgetsay.com/best-custom-roms-for-samsung-a50/>
--> failed, because the only output was < waiting for any device >
7. Powered the phone of and entered the download mode as in 1.
8. Flashed TWRP from here https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-galaxy-a50-a50dd.3916199/ and later here https://forum.xda-developers.com/t/recovery-root-unofficial-twrp-3-4-0-0-for-galaxy-a50.4138313/
9. Tried to flash the GSI images => Boot loop.
10. Follwed these instructions: https://github.com/phhusson/treble_experimentations/wiki/Samsung-Galaxy-A50 => Still boot loop.
What am I doing wrong? Various tutorials and videos like this one:
indicate that it shouldn't be too difficult.
Thanks in advance for any new idea!
Additional Info: In TWRP i had to resize the system partition after flashing lineage os because it was no longer ~5GB large but rather the size of the image. Afterwards I was able to install GAPPS.
Okay, once again, the answer is "don't be stupid" or at least "rtfm". I've read online, that the A50 doesn't have an a/b-slot so I always downloaded the a-only packages. These however don't work. The very first lineage os with a "b" in the filename (as shown in the video) worked.
CatorCanulis said:
I tried the following:
1. Unlock my bootloader by enabling developer options, enabling OEM unlock, power off the device, hold VOL+ and VOL- simultaniously while connecting a USB cable, and enabling the unlock.
A factory reset was triggered as described in various tutorials.
2. I set the A50 (SN-A505FN/DS) up without Google or Samsung Details.
3. I check, wether the OES unlock was still intact, which it was.
4. I enabled USB debugging and made sure my PC was allowed to do send adb commands.
5. I typed: adb reboot [fastboot, download] (tried both on macOS, Windows and Linux, drivers were installed on Windows via Kies, Samsung Switch and the download package)
6. In the download menu I typed: [fastboot, .\fastboot.exe] flash system <various images derived here: https://www.gadgetsay.com/best-custom-roms-for-samsung-a50/>
--> failed, because the only output was < waiting for any device >
7. Powered the phone of and entered the download mode as in 1.
8. Flashed TWRP from here https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-galaxy-a50-a50dd.3916199/ and later here https://forum.xda-developers.com/t/recovery-root-unofficial-twrp-3-4-0-0-for-galaxy-a50.4138313/
9. Tried to flash the GSI images => Boot loop.
10. Follwed these instructions: https://github.com/phhusson/treble_experimentations/wiki/Samsung-Galaxy-A50 => Still boot loop.
What am I doing wrong? Various tutorials and videos like this one:
indicate that it shouldn't be too difficult.
Thanks in advance for any new idea!
Additional Info: In TWRP i had to resize the system partition after flashing lineage os because it was no longer ~5GB large but rather the size of the image. Afterwards I was able to install GAPPS.
Click to expand...
Click to collapse
dont use the twrp 3.4
use the 3.5
Cator Canulis said:
Okay, once again, the answer is "don't be stupid" or at least "rtfm". I've read online, that the A50 doesn't have an a/b-slot so I always downloaded the a-only packages. These however don't work. The very first lineage os with a "b" in the filename (as shown in the video) worked.
Click to expand...
Click to collapse
we should use arm64 ab because we have SaR device
Hi All,
With the recent launch of LineageOS 18.1 I decided to take the plunge and get it installed on my fully stock Videotron/Freedom H915. Since I had to smash together info from a half dozen other threads, I figured I'd gather it all together here for folks with a Canadian phone trying to make this work.
Since I knew absolutely nothing coming into this, I'm going to go a little more detailed on this write-up. If you've been flashing ROMs since the old days of Cyanogenmod you can probably skim half of this.
Disclaimer : I'm not responsible for any bricked phones or other negative outcomes. This is what worked for me, but I'm far from being an expert. If you continue past this point you agree to take your time, do your reading, be responsible for your own device/actions and not hold me or the forum accountable for anything that might go wrong. You've been warned.
IMPORTANT NOTE #1
If you've picked up an H915 on ebay and you are intending to use it on a network other than the one it's SIM locked on, make sure you do the whole SIM unlock process on the stock ROM either before you get started at all, or once you've reverted to the vulnerable stock ROM after Step 1 below.
I actually use Telus as my provider and I wasted a bunch of time trying to figure out why I couldn't get signal because only the stock ROM will prompt you for a SIM Unlock code. Lineage will just sit there dumbly and not allow you to enable data.
Once you've unlocked the SIM it will stay unlocked from that point forward, just make sure to unlock it and verify your SIM is working with LTE on the stock ROM before you get started.
IMPORTANT NOTE #2
Use LGUP's "DUMP" feature to take a backup of ALL partitions on your phone before you start. If you're reading this thinking "I just bought this phone off ebay, there's nothing on it I care about", take the backup anyway. You never know when you might need a copy of the modem partitions or other things from your phone's original build. It came in super handy for me in troubleshooting the process. So go do a backup!
Current Issues:
If signal is too weak to connect to a tower (or non-existent), the OS tends to crash with a modem error. Still trying to figure this one out.
I think I can get this working without first jumping to US996 but haven't had a chance to verify that. If I do I'll update the thread.
Download Prerequisites
Links working as of 2021-06-29
LGUP with patch
Link
Working adb/fastboot environment
Instructions
Download
Fastboot Drivers
Link
Universal ADB Driver
Link
Videotron/Freedom H915 Android 7 (Nougat) version E - H91510e_00_VTR_CA_OP_1205.kdz
Link
USA General US996 Android 7 (Nougat) version F - US99610f_00_1205.kdz
Link
APK for Terminal Emulator
Link or Alternate Link
LG V20 Root Package Original (v4?)
Link
Old TWRP for Root Package
Link
Videotron/Freedom H915 Modem Partition Image
Link
Lineage Install Zip for H910 (grab the latest, I'm using lineage-18.1-20210506-nightly-h910-signed.zip which is already out of date)
Link
MindTheGapps
Link
(Optional, for rooting) Magisk
Link
Different Boot Modes
For those not familiar with these phones, there are three different "modes" the phone can boot into. Here's a quick reference on how to boot into each one.
Download Mode
This mode is used for pushing KDZ files or individual partition backups using LGUP
Turn Off Phone
Hold the Up-Volume Button
Insert USB-C Cable with other end already plugged into PC
Bootloader (aka Fastboot) Mode
The H915 doesn't come with this mode by default. If you try it, you'll just get battery charging. We'll be temporarily converting the phone to a US996 in order to use the DirtySanta exploit to replace the bootloader partition with a leaked Engineering aboot.
This mode is used with the fastboot tool to load the TWRP utility into the Recovery partition.
Turn Off Phone
Hold the Down-Volume Button
Insert USB-C Cable with other end already plugged into PC
Recovery Mode
The recovery mode on a stock phone is used to perform a factory reset. We will be using the Factory Reset a couple times with the stock ROMs, then replacing the contents of the recovery partition with the TWRP tool that allows us to format partitions, load partition images, and sideload apps and LineageOS itself.
Turn Off Phone
Hold the Down-Volume Button
Press and hold Power-On (rear fingerprint sensor/button). When LG Logo appears, release power button for 1 second then press and hold again
When "Factory Data Reset" appears, release all buttons
Press Volume Down to highlight "Yes" then press power button to select the option
Repeat for the confirmation
Note about flashing KDZ files using LGUP
You can flash KDZ files onto the phone using LGUP from two places - either with the phone in "Download Mode", or with the phone booted into the OS with the USB Options set to "File Transfer" and USB Debugging turned on.
The difference between these two is when it performs the OS compatibility check.
In Download Mode it's the code of the Download Mode partition that does the check. In the OS, it's the OS that does the check before booting to Download Mode and bypassing Download Mode's check.
Why is this important? Because when converting from one phone to another (Say, an H915 to a US996 like we do below), you initially can't flash the KDZ using LGUP's "Upgrade" function. You can only use "Partition DL" to replace the contents of partitions with the contents of the KDZ. This kind of works, but ends up with a phone that will sometimes identify as a H915 (in Download Mode) but sometimes identify as a US996 (in the OS). To clean it up, once you've done the Partition DL method, you can do it again from the OS and use the Upgrade method to get a really clean install.
It works going back the other way as well when you want to return to stock.
If this doesn't make sense, don't worry. You don't need to fully understand it to follow the instructions below, I just found it to be interesting info that didn't seem to appear in other threads.
Process Overview
Revert the phone to an old/vulnerable stock Nougat ROM for Videotron/Freedom Mobile
Enable Dev Options
Dump contents of US996 KDZ partitions over top of existing partitions
Cleanup by re-flashing US996 KDZ partitions over top of existing partitions
Transfer files to the SDCard and install Terminal Emulator
Unlock the Bootloader using the DirtySanta exploit
Boot to old TWRP and install new TWRP
Boot to new TWRP, install LineageOS, Google Apps, and flash modem partition image
Reboot to LineageOS
Actual Process
1 - Revert the phone to an old/vulnerable stock Nougat ROM for Videotron/Freedom Mobile
We need to be on Nougat for this to work, so if you're on Oreo you have to downgrade to Nougat before we begin. I chose a Nougat ROM for the H915 that's vulnerable to the DirtySanta exploit because I know it works and because I'm hoping in the future to be able to skip converting the phone to a US996 if possible.
Boot phone into Download Mode
Launch LGUP with Patch
Select "Upgrade" radio button
Select bin file : H91510e_00_VTR_CA_OP_1205.kdz
Click Start
When finished phone will reboot
1.5 - Do this if Step 1 Failed... Otherwise continue to Step 2
Depending on what's loaded on your phone when you start, it might complain about doing Step 1. This should allow us to bypass the issue and allow Step 1 to work. You can use this step if you've already converted the phone to another model as long as it's not bricked.
Boot phone into download mode
Launch LGIP with Patch
Select "PartitionDL" radio button
Select bin file : H91510e_00_VTR_CA_OP_1205.kdz
Click Start
Click the "Select All" partitions checkbox and click OK. When done it will reboot.
If it hangs or loops on reboot, boot into "Recovery Mode" (which at this point will Factory Reset the OS)
The phone boots into the OS
Quickly go through setup wizard. Skip as many things as possible.
Go Settings - General - About Phone - Software Info - Make sure it identifies as H91510e
Change the USB Option mode to "File Transfer"
Then repeat Step 1, but from inside the OS instead of in Download Mode
2 - Enable Dev Options and File Transfer Mode
We need these enabled after every time we flash the OS so that our LGUP and adb commands will work. You'll get used to doing these steps a bunch.
Quickly go through setup wizard. Skip as many things as possible.
Unplug USB-C cable
Swipe down from the top and change from USB Charging mode to File Transfer mode
Settings - General - About Phone - Software Info
Tap on Build Number many times until it unlocks Developer Mode
Go back 2 menus and enter the new "Developer Options" menus
Make sure "Enable OEM Unlock" is enabled
Enable "USB Debugging" (will be greyed out if USB-C cable is still attached)
Go back to main screen
Plug USB-C cable back in.
A pop-up will appear asking to Allow USB Debugging. Check the "Always Allow" box and tap OK
3 - Dump contents of US996 KDZ partitions over top of existing partition
The Videotron/Freedom KDZ has no Bootloader/Fastboot mode. If you try to enter bootloader mode you'll just end up charging the battery. So we have to cross-flash the US996 KDZ to get a phone with a bootloader which we can then replace with the engineering version using the DirtySanta exploit.
Boot phone into download mode
Launch LGUP with Patch
Select "PartitionDL" radio button
Select bin file : US99610f_00_1205.kdz
Click Start
Click the "Select All" partitions checkbox and click OK
When the phone boots back into the OS, repeat all of Step 2.
Note: If it asks for a password on startup, follow the "Boot to Recovery" steps and since
we don't have anything loaded in the recovery partition it will wipe/erase the phone
and remove the password.
4 - Cleanup by re-flashing US996 KDZ partitions over top of existing partitions
As mentioned in the "Note about flashing KDZ files using LGUP" section above, after you use the PartitionDL method you get a kind of dirty phone image that doesn't always identify as its new model. To clean up, we repeat the process in Upgrade Mode, taking advantage of the fact that at least the OS now identifies as US996 even if Download Mode doesn't. After this, Download Mode will also identify as US996.
Starting booted into the OS with a USB-C cable attached (File Transfer mode, USB Debugging on):
Launch LGUP with Patch
Select "Upgrade" radio button
Select bin file : US99610f_00_1205.kdz
Click Start
When the phone boots back into the OS, repeat all of Step 2.
5 - Transfer files to the SDCard and install Terminal Emulator
We will need some files on the SDCard in the phone in order to install them, either inside the OS (in the case of Terminal Emulator), or later on from TWRP. The Terminal Emulator will be used for the DirtySanta exploit so we need to get that installed now.
Make sure the USB Connection is set to Data Transfer mode and copy the following files to the SDCard:
APK for Terminal Emulator
twrp-3.5.1_9-0-us996.img
h915freedommobilemodem.img
Enable installing apps from unknown sources by:
Settings - General - Fingerprints and Security - Unknown sources (turn it On)
Install Terminal Emulator:
Tools - File Manager
Choose "Allow" when prompted
Click the up-arrow next to "Internal Storage"
Choose SD Card
Scroll down and tap on jackpal.androidterm-1.0.70-71-minAPI4.apk
Install
6 - Unlock the Bootloader using the DirtySanta exploit
The US996 KDZ has a bootloader but it's locked. In order to unlock it we need to use the DirtySanta exploit to give us permissions to replace the Bootloader/Fastboot with a leaked engineering version.
Starting booted into the OS with a USB-C cable attached (File Transfer mode, USB Debugging on):
Settings - General - About Phone - Software Info
Verify that Software Version lists as US99610f
Copy the twrp-3.0.2-1-us996.img file into the folder containing the LG V20 Root Package
Open a command prompt window and change to the folder containing the LG V20 Root Package and run "Step1.bat"
It will push multiple files to the phone and apply some patches/exploits.
This proces will take 5 minutes and put you out at an "elsa:/ $" prompt
At this "elsa:/ $" prompt in your command prompt window type the following:
run-as con
chmod 0777 /storage/emulated/0/*
On the phone, launch Terminal Emulator and run the following:
id
Verify that the string which comes back contains the string "context-u:r:untrusted_app".
If not, run Step1.bat again, else continue forward
Enter the follosing command into Terminal Emulator (be very careful to type it properly):
applypatch /system/bin/atd /storage/emulated/0/dirtysanta
If that command came back with an error, close and re-open Terminal Emulator and try again
The command should begin to patch another file. This will take 5 minutes and will return you to the "elsa:/ $" prompt in Terminal Emulator when it has finished
Open another command prompt to the same folder and run "Step2.bat"
This step will download backup copies of the boot and aboot partitions from the phone then boot the phone into bootloader/fastboot mode.
You'll know it worked if the first line at the top of the phone screen appears in red
In the command prompt window, run Step3.bat
It will flash boot1.img and the TWRP Recovery image multiple times then restart the phone
The phone will hang, no matter how long it's left. Wait 5 minutes (at least until the logo re-loads once) then do the following:
Unplug the USB-C cable
Remove the battery from the phone to turn it off
Replace the battery
Boot into Fastboot mode and run the following commands in your command prompt:
fastboot flash boot bootbackup.img
Remove the USB-C cable and battery to turn off the phone. Then replace the battery and enter Recovery Mode
The phone will show a big red exclamation mark saying "Your device is corrupt". This is normal. It will go away after a few seconds then boot into recovery. This error screen is the result of the engineering "aboot" image that was flashed to give us an unlocked bootloader and will always happen on boot.
7 - Boot to old TWRP and install new TWRP
The old version of TWRP recovery will load. Don't ask me why we can't just go straight to new TWRP above, it didn't work well when I tried it.
If it asks for a password to decrypt data, click Cancel
Swipe to allow modifications
Install - Select Storage - MicroSD Card - OK
Install Image - Scroll down and tap the "twrp-3.5.1_9-0-us996.img"
Select the Recovery partition and swipe to confirm flash
Back to main menu
Reboot - Recovery
8 - Boot to new TWRP, install LineageOS, Google Apps, and flash modem partition image
The new version of TWRP will load:
Check the "Never show this screen during boot again" box
Swipe to allow modifications
Wipe - Format Data - type "yes" to continue
This is likely to fail the first time. Repeat it to properly format the data partition.
Go back to Main Menu - Wipe - Advanced Wipe - Select "Dalvik / ART Cache", "System", and "Cache"
Swipe to wipe
Back to main menu
Advanced - ADB Sideload
Plug in USB-C cable
Swipe to start sideload
In command prompt window on PC type the following:
adb sideload lineage-18.1-20210506-nightly-h910-signed.zip
When complete tap "back" and "ADB Sideload" and swipe again to apply another file:
adb sideload MindTheGapps-11.0.0-arm64-20210412_124247.zip
If you want to root the phone (completely optional, not necessary for this process), now is the time to do it. Tap "back" and "ADB Sideload" and swipe again to apply another file:
adb sideload Magisk-v23.zip
Go back to main menu - Install - Install Image - tap the h915freedommobilemodem.img file
Select the Modem partition and swipe to confirm flash
Remove USB-C cable
9. Reboot to LineageOS
Go back to main menu - Reboot - System - Swipe to reboot
References where I got the info to make this tutorial
Official Lineage 18.1 for LG V20 Release Thread
LineageOS Wiki for H910
DirtySanta Bootloader Unlock and Root Guide (Original)
H910 Rooting Thread (Cross-flash H915 then DirtySanta to US996)
H915 Root, TWRP using DirtySanta [WorkingSignals]
Noob Friendly Root TWRP using DirtySanta
General info about Modem Hardware, Firmware, Radio Interface Layer
[Reserved]
thank you so much. i need it
Great job for writing a complete how-to guide!
Thank You, You saved my old V20 H915
hi have you been able to find a better modem?
btw i'm not able to decrypt under twrp, can you?
Just want to confirm, it's only guide wich works for me. But I have issues with modem:
1. When I tried to change mode of modem, "prefered network type", phone stayed in the loop of the kernel panic "modem crash"
2. It were difficult to revert changes back. Finally, safe mode (in order to get it, you need to press volume up and volume down in the same time, during LinageOS booting process) helped me - when I disabled airplan mode, I had 2-10 seconds until next kernel panic. And in ~10 attempts, I were able to finally switch modem's mode to GSM/WDCMA/LTE
3. I used this phone 3 days, and once the kernel panic (because of modem) happened again
Any ideas what to do with modem? Also, the picture "Your phone is corrupt" is not fan Any ideas how to change it?
I did my best to follow all the instructions but after step 7's reboot I just get blocks full of static. I can tell it's trying to do fresh install setup though from what's peeking through the blocks.
Riot54 said:
I did my best to follow all the instructions but after step 7's reboot I just get blocks full of static. I can tell it's trying to do fresh install setup though from what's peeking through the blocks.
Click to expand...
Click to collapse
This is normal. Flash a kernel that's patched for dirty santa OR, cover the proximity sensor on boot and keep it covered until boot is complete.
That worked, thanks.
After multiple attempts going back and forth with step 6, I finally did it! I might switch to Lighthouse or Arros but I wouldn't have gotten this far without your guide.