Related
Hi,
I am not 100% sure that this is the correct place to post I couldn't find a section for TF201.
I have bricked mt TF201 while trying to flash CM 9. I unlocked the bootloader successfully using the ASUS tool (now have the device unlocked at boot logo) I am unable to get past the boot logo and cannot boot into recovery using vol down + Power.
I can boot into ADB using Vol Up +Power at this stage screen goes off and my PC makes the device inserted noise.
So obviously I want to try an fix my tablet before giving up. I have NVFlash but it just says waiting for ADB device, I have install the universal naked drivers but nothing device manager recognizes an ADB device but with a yellow exclamation mark.
another thing is I need blob.bin do I take this from my current device ( I haven't got it backed up) or will I need to find an ASUS stock rom?
I couldn't not see that ASUS stock rom listed on the ASUS site in the UK.
Any help will be much appreciated
Thanks
TF201 forum (Transformer Prime)
http://forum.xda-developers.com/forumdisplay.php?f=1411
Moved to TF201 (Prime) Section
Code:
#include
/*
* 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.
*/
THIS RECOVERY WILL TRIP YOUR KNOX COUNTER ..AND UR WARRANTY WILL BE VOID
THIS RECOVERY IS ONLY FOR THE GALAXY A7 [SM-A700FD] [QCOM] RUNNING LOLLIPOP
THIS RECOVERY HAS BEEN TESTED AND EVERYTHING SEEMS TO BE WORKING FINE .. CHECK THE BUGS SECTIONS
Why twrp ? Why not a pre-rooted firmware which will not void warranty?
Ans : TWRP has many more functionality than stock recovery ! Rooting means to playing around with your device.If some thing goes wrong it you have to flash the whole firmware again instead,backup your ROM through CWM and if something goes wrong restore your backup AS SIMPLE AS THAT !
All you have to do is follow my instructions :
STEP 1 :
-Download and setup ADB drivers for your device
can be found here Drivers !
STEP 2 :
-Download the recovery from --->
TWRP
-Download odin 3 Link
-Turn of your device and go to odin mode [ Vol down + power + home button (all at the same time) ] release it when you see Galaxy A7logo
-Press vol up to confirm
STEP 3 :
-Now that you are in odin mode connect your device via usb cable !
-Now open Odin3 3.09 that you have downloaded.
-If there is a pop-up like Installing ADB drivers let it get finished it is usually updates !!!!
-Make sure the COM : xx (xx is usb port number it can be any number so dont worry about it,just verify COM is lit up)
-Select the recovery (Link in STEP 2) ! Now select AP and browse to where you have .tar file and select it
MAKE SURE U UNTICK THE AUTO-REBOOT BUTTON
-Click Start
ONCE IT SAYS PASS ... BOOT INTO RECOVERY USING VOL UP + HOME + POWER BUTTON
HOW TO ROOT THE DEVICE :
-Download SuperSu (obviously the latest one) from here ------> Click here !
-Copy that to internal sd card or external sd
-Power off your device and press vol up + power + home button (all at once)
-Select install zip from sdcard --->choose zip from sdcard ---> scroll down and flash UPDATE-SuperSU-v2.xx.zip
Done ! And you are ready to go
BUGS
You tell me!
YOU TELL ME
NOTE : IF ANY OPTION DOESNT WORK FOR U ... TURN OFF UR PHONE AND THEN BOOT INTO RECOVERY
SOURCES
DEVICE TREE
KERNEL(PREBUILT ... THANX TO SAMSUNG ... AVAILABLE IN THE DEVICE TREE)
CREDITS
TWRP TEAM
@govind.madhu93 for testing
CHANGELOG :-
BUILD 2
Fixed Recovery reboot loop
BUILD 1
Initial Build
Thanks a lot!!
Can i try this method for A700FQ if i can flash twrp i can root my A7
I had installed a kitkat twrp on my a700fd that was developed for a700h and it worked.
Sent from my SM-A700FD using XDA Free mobile app
help
system force close after flashing recovery. only status bar is visible
PS: everything working fine now. cleared cache and restarted it. thanks a lot. backup restore also working
Hey are you also thinking to develop any custom rom for galaxy a7 ?
if you start i am ready to help.
govind.madhu93 said:
I had installed a kitkat twrp on my a700fd that was developed for a700h and it worked.
Sent from my SM-A700FD using XDA Free mobile app
Click to expand...
Click to collapse
It work with A700H kitkat my friend?
is this working on russian lollipop version of A700FD?
palimatix said:
is this working on russian lollipop version of A700FD?
Click to expand...
Click to collapse
yes
Hello
How about the SM-A700F would it work on that device too?
Great job. Now we just need an AOSP ROM.
I noticed that backups made with this TWRP have wrong date in their names (half a year earlier).
New build is up !!
Changelog
Fix Recovery reboot loop
Download - http://dl.rutvikrajagopal.com/a7lte/twrp
Will we see any development for the A700F [Exynos] ?
Hello! I've installed the second version of TWRP - all works, but backup folder name has invalid date - today it made backup with folder name 2015-03-25..
jazzzzy said:
Hello! I've installed the second version of TWRP - all works, but backup folder name has invalid date - today it made backup with folder name 2015-03-25..
Click to expand...
Click to collapse
I'll look into the issue soon
RVR said:
Code:
#include
/*
* 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.
*/
THIS RECOVERY WILL TRIP YOUR KNOX COUNTER ..AND UR WARRANTY WILL BE VOID
THIS RECOVERY IS ONLY FOR THE GALAXY A7 [SM-A700FD] [QCOM] RUNNING LOLLIPOP
THIS RECOVERY HAS BEEN TESTED AND EVERYTHING SEEMS TO BE WORKING FINE .. CHECK THE BUGS SECTIONS
Why twrp ? Why not a pre-rooted firmware which will not void warranty?
Ans : TWRP has many more functionality than stock recovery ! Rooting means to playing around with your device.If some thing goes wrong it you have to flash the whole firmware again instead,backup your ROM through CWM and if something goes wrong restore your backup AS SIMPLE AS THAT !
All you have to do is follow my instructions :
STEP 1 :
-Download and setup ADB drivers for your device
can be found here Drivers !
STEP 2 :
-Download the recovery from --->
TWRP
-Download odin 3 Link
-Turn of your device and go to odin mode [ Vol down + power + home button (all at the same time) ] release it when you see Galaxy A7logo
-Press vol up to confirm
STEP 3 :
-Now that you are in odin mode connect your device via usb cable !
-Now open Odin3 3.09 that you have downloaded.
-If there is a pop-up like Installing ADB drivers let it get finished it is usually updates !!!!
-Make sure the COM : xx (xx is usb port number it can be any number so dont worry about it,just verify COM is lit up)
-Select the recovery (Link in STEP 2) ! Now select AP and browse to where you have .tar file and select it
MAKE SURE U UNTICK THE AUTO-REBOOT BUTTON
-Click Start
ONCE IT SAYS PASS ... BOOT INTO RECOVERY USING VOL UP + HOME + POWER BUTTON
HOW TO ROOT THE DEVICE :
-Download SuperSu (obviously the latest one) from here ------> Click here !
-Copy that to internal sd card or external sd
-Power off your device and press vol up + power + home button (all at once)
-Select install zip from sdcard --->choose zip from sdcard ---> scroll down and flash UPDATE-SuperSU-v2.xx.zip
Done ! And you are ready to go
BUGS
You tell me!
YOU TELL ME
NOTE : IF ANY OPTION DOESNT WORK FOR U ... TURN OFF UR PHONE AND THEN BOOT INTO RECOVERY
SOURCES
DEVICE TREE
KERNEL(PREBUILT ... THANX TO SAMSUNG ... AVAILABLE IN THE DEVICE TREE)
CREDITS
TWRP TEAM
@govind.madhu93 for testing
Click to expand...
Click to collapse
hello, you can create a recovery for Galaxy A7 (SM-A700F Lollipop)? I looked everywhere but there:laugh::laugh:
nino64 said:
hello, you can create a recovery for Galaxy A7 (SM-A700F Lollipop)? I looked everywhere but there:laugh::laugh:
Click to expand...
Click to collapse
I would like that too if possible, our Sm-A700f dosnt get much love :crying:
After installed the build 2 I am still having reboot loop.
Hello people! The truth did not know where to put this but if it's wrong because there is no problem and relocated!
I have a x900 LeTV I bought several months ago! Two weeks ago you installed a beta version of android 6.0.1. and I was working fine few days and one night, suddenly he went out and caught no more! Hard has a brick because no load, does not light, does not enter or fasboot recovey mode, any PC with any version of Windows recognizes it and have been for days following guidelines to resuscitate through QPST.2.7.429.msi without but although follow the steps one by one PC with Windows 7 simply does not recognize me! I am in despair and can not think of anything else! Some genius of the community could help me? There is a guide for x800 that is very similar to x900, yet still do not achieve much !!!
Same
Same issue, did u manage to fix it?
Hello dear all,
after a long time of rush*around different solutions I finally figure it out how to hard brick Indian le max x900
(note hard brick means ur phone is completely dead no charging,no restart, *no fastboot etc....becoz of may be wrong rom flashing)
1. Install qualcom driver and latest qpst 2.7*(link:*https://androiddatahost.com/np4wq)(qualcomm driver present in qfil file for x800 link in step4)
2. Installed qpst*will be present at c:/program files(x86)/qualcomm/qpst/bin....inside it find qfil flashing*application...open it
3. connect ur dead indian le max to computer and see if qualcomm usb driver can detect it(u may notice qfil flashing appln will also show some com no connected)....if u r unsuccessful just press both volume key/or power key and both vol key at a time for around 1 min when phone is connected to pc.*(in any case u failed no big issue try to install it manually by searching in google, well I have used win10 and it simply worked for me)
4. Download the qfil file for x800 and extract it somewhere, it also have qualcomm driver inside it so once extracted install that driver too (link:*https://mega.nz/#!G0ozxZwb!vowHBNjQGC1AtVOx2ThrWpYt6yHEnAACFvq90XDF4n0)....actually i tried qfil for x900,x1, line brush tutorials etc but none of those worked for me and x800 aks le 1 pro have the same processor so it can make x900 alive....sahara error all the time...*( a big thx to*UNBRICK X800 X900*Started by*mxmax)
5. if all done correctly u can see ur dead indian lemax*phone connected to qualcomm mode with some com no, that u can notice in qfil flashing appln.
6.in the flashing appln select Flat Build,
* * * * * * * * * * * * * * * * * * * * *in browse select ur extracted qfil x800 folder (path\qfil x800\x1_na_dvt1_fastboot\prog_emmc_firehose_8994_lite.mbn,
* * * * * * * * * * * * * * * * * * * * *in load xml select rawprogram_unsparse (present inside folder x1_na_dvt1_fastboot)....after that patch0 that automatically comes,
* * * * * * * * * * * * * * * * * * * * than finally click on download....u can see process started and once completed exit it.
7. So now ur phone have qfil of x800 flashed, try to boot it by pressing power button for 1 min.....u can see blue led blinked and ur phone start to boot (if not means ur phone's battery is very less simply connect it with charger by pressing power button u can see phone starts to show orange led flashing after some time....ie it start charging)
8. once it start in step 7 the phone show chinese letv logo...but it doesn't boot becoz it is for x800 not x900....phone simply tries to boot again and again...so once the phone start to reboot by itself simply press power button and vol down key at a time....u can see small penguin that means ur phone is in fastboot mode.
9. its time now to install twrp 3.0 to ur x900 connected to pc in fastboot mode(link:*https://www.androidfilehost.com/?fid=24533103863139522)...simply install twrp from link extract it open the twrp installer appln ....and install it by pressing backspace key that u find during instrution)....great thing about twrp recovery is it can charge ur phone too while connected to power source.
10.So after step 9 ur phone should be in twrp 3.0 recovery mode....u can see internal storage of it shows in pc of around 10 gb not 52 gb.....so inside twrp\wipe\format data...type yes, and advanced wipe select all and wipe......once done u have 52 gb avail in internal storage that u can see in ur pc too.
11. put indian version any rom inside ur internal storage and flash it...once done ur phone will successfully rebooted links for roms are below...simply download any as per ur choice
* * * * *https://drive.google.com/file/d/0B6m-wM0vYiL8U0U4cUhUM2NlMGc/view*(this is stock 12s rom)
* * * **https://www.androidfilehost.com/?fid=24533103863139959* (this is also stable 12s rom made bu cuoco with extra settings and dolby presinstalled)
* * * **http://evolutionletvx900.blogspot.in/* *(this will give u link for 12s and 13s rom which have nova and google launcher preinstalled)
* * flash any rom and if any any file after flashed make big vibrate ur phone with blue led on...don't panic...simply press power button for long time it will reboot ur phone
A big thx to memerbers of leeco.re for proving international support for leeco becoz it had gone from India, and I request u to make support for Indian x900 also since we cant able to install eui 5.8 based roms....tried to install several roms by deleting lines for check in update-script...even though it installed make it brick/dea again...so plz help for android 6*
Hi, I'm a x900 user
I have the same issue than some of you guys, my phone is detected in Qualcomm mode in QFIL, I have to charge the phone like an hour or two, I can tell its chargin because It has the blue led on, when it has no charge the led is blinking red and after sometime it becomes blue.
Put the phone in Qualcomm mode, download finish succesfully, pressed Vol Up + Power, my phone starts but with blue led and black screen, although its detected as a hard drive (LeTV), it'srecognized as an adb device (serial number ----- recovery). I ran the command "x1_na_fastboot" in command prompt inside folder CEXCNFN590......zip., I got rebooting in fast mode device, but it stops in "awaiting devices".
Thats were I'm stuck. Got any ideas?
2 Rahulraj2012
Thanks bro it is work exactly as you say !!! X900 Unbriked for now ;-)
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!
Hi!
I tried to update my Mi Pad 4 Wifi to latest twrp 3.5.2.9 but I ended with a half-brick...
I cannot access TWRP anymore (no way to access it with power+volume up). Power menu (I am using arrowos) or adb reboot recovery, they just show me a brief twrp loader image than goes black and I need to power cycle.
Worse even, I can launch fastboot, fastboot devices responds but I cannot boot/flash, or whatever from fastboot.
I suspect I had somehow hosed some boot/persistent or other device partition.
I tried to reboot to EDL but it's not responding ...
System is working but I fell I am in an unsafe position....
Any clue on how to restore fastboot twrp funcionality or I lost my Mi Pad?
not sure if your issue but I needed to goto to fastbook devices, fastboot flash default boot.img. I couldn't get TWRP to work natively as boot - I needed to use Fastboot boot boot.img to temporarily boot into TWRP. This was over a year ago however so definitely not 3.5.2.9
p.s. somehow I managed to get 3.3.1 working - this is what is on my MiPad currently
p.p.s. if your fastboot comes onscreen but jumping straight to black screen with "press any key to shutdown" as soon as you plug in the USB then try this. I needed to
[Guide] Fix "press any key to shutdown" when unlock bootloader or run fastboot cmd
[Guide] Fix "press any key to shutdown" when unlock bootloader or run fastboot cmd For some Windows 10 users (like me), it seems impossible to unlock the bootloader of their Xiaomi devices. Because every time they run MiFlashUnlock and connect...
forum.xda-developers.com
I've also now just installed this. I flashed from TWRP and it worked
[RECOVERY][UNOFFICIAL] Pitch Black Recovery Project [v3.x.x][2021/03/30]
/* *Disclaimer * * Your warranty is now void. * * We're 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...
forum.xda-developers.com
Last message - promise. Seems that it worked for me initially because I used 3.3.1.
Long-standing and known issues with later versions and suggested fix here >
PSA - The Latest TWRP Release (3.5.0_9-0) is Bugged
Already opened an issue on GitHub but looks like the dev got a long backlog. If anyone has a fix I'd really appreciate it. I experienced the following when updating TWRP to 3.5.0_90: - long loading time: takes ~20s to finish initialization -...
forum.xda-developers.com