Related
I was forwarded tot this subforum, maybe someone could help me here?
I tried to root the tablet, and thought I had all the steps required to do so. I just rooted my OPO without problems and wanted to do the same with the Asus. As I've said, I thought I had all the steps but saw I missed some things and followed a mix of different tutorials on xda-developers.com. I had downloaded the ASUS v5.0.11 update and the 5.0.11 root. I could get into bootloader with Vol-Up + Power, it opened the android with helmet-bootloader without problems. I used the fastboot commands: - fastboot erase cache - fastboot erase system - fastboot flash update "updatename".zip
there it failed to flash the zip
Then I saw I had to use the fastboot 4.7.3 and not the 5.0.11 one. So I tried to flash that one I found somewhere. Then I installed recovery 4.7.3 and then I got a bricked asus
I have no idea in what order I did things, and I'm sure I did a lot more than I've described. But now I can't get into bootloader with Vol-Up + Power, and when I try to access the bootloader with adb reboot bootloader, I don't see the android with helmet anymore, but just the usb-icon with a red gauge. When I try to start the tablet, it hangs on the bootscreen 'Asus, in search of incredible'.
I want to get into bootloader again so I can play with fastboot-commands again, or if someone knows what to do by the things I've just tried to describe.
I would cry if only I could get into the OS again.
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.
Team Win Recovery Project 3.0.2
https://postimage.org/
Code:
*** Disclamer
* Your warranty is now void.
*
* We are 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 us for messing up your device, we will laugh at you.
WARNING: The stock boot image has dm-verity, which prevents you from booting if you swipe to enable system modifications!
SOLUTION: Flash a root such as SuperSU or phh-superuser. You can also flash no-verity-opt-encrypt.zip.
- Prerequisites :
• YOUR BOOTLOADER MUST BE UNLOCKED
-Check this post for details on how to unlock your stylo 2 plus bootloader
http://forum.xda-developers.com/showpost.php?p=68919557&postcount=15
-If you have problems with the device drivers installed , you will need to install lg bridge app by lg that contains the device driver
http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=PWZO7A26B9UW
• Enable OEM Unlocking and ADB in developer options!
- Download :
https://www.mediafire.com/download/ofyf0vdc8t4349c
[Please do not repost this information or mirror the downloads. Feel free to post a link to this thread anywhere you like.]
- How to install twrp :
Notice:
this install guide was originally written for the stylo 2 plus I'm not sure it will work on the stylo 2..
• BOOT INTO FASTBOOT MODE:
With your phone off, connect your usb cable to your phone while holding VOLUME DOWN to boot into fastboot mode or just type [adb reboot bootloader] in the adb terminal
• ONCE YOU ARE IN FASTBOOT MODE:
Open a command prompt and type "fastboot flash recovery <path_to_recovery.img>” without the quotation marks.
Example: fastboot flash recovery C:/Users/John/Desktop/recovery.img
[don't forget to extract the downloaded recovery zip to get the recovery.img]
• WHEN THE FLASH COMPLETES: (Takes about 2 seconds)
On your phone, unplug the usb cable and power it off by taking out the battery and putting it back in.
• BOOT INTO RECOVERY MODE FOR THE FIRST TIME
HOLD VOLUME DOWN + POWER until you see the LG logo and then temporarily release the POWER button, immediately pressing and holding it back down until you see the white prompt screen. You will NEVER release the volume down button in this process!
Use the hard keys to select "YES" and then "YES" again to boot into
TWRP recovery!
After the TWRP splash screen you will see the option to type in the password to decrypt the filesystem. Due to the password prompt and the touchscreen driver, you will not have any touchscreen functionality until your phone locks for inactivity. After it locks (ON ITS OWN) and the screen dims, you can unlock it normally and TWRP is fully functional.
Warning: use the [volume down + power] buttons combo only to boot into twrp for the first time after flash ! don't use it after that as it will wipe your device every time you try to use the buttons combo again to boot into twrp after the first time .
u have 2 methods to boot into twrp after the first boot:
1- u can use this app [root is required] :
https://play.google.com/store/apps/details?id=com.stephansmolek.reboot&hl=en
2- or u can use adb command type [ adb reboot recovery ] in adb terminal to boot into twrp
DISABLE FORCED ENCRYPTION & ROOT IT!
1. In TWRP, go to Wipe > Format Data. Enter the keyword ‘yes‘, in the provided space and enter. This will wipe the automatically encrypted filesystem, and decrypt it.
2. Once the wiping is done, reboot back into recovery. Go to Reboot > Recovery.
3. When the recovery boots again, connect your phone to the PC and Enable MTP under the Mount section.
4. Transfer the downloaded ‘no-verity-opt-encrypt-2.1.zip’ and ‘SR1-SuperSU-v2.78-SR1-20160915123031.zip to your internal storage or EXTSD
5. Disconnect the device now.
6. Tap on Install. Now, navigate your phone’s storage and select ‘no-verity-opt-encrypt-2.1.zip’. Finally swipe the ‘Swipe to confirm Flash’ button on the bottom of the screen.
7. The flashing process will merely take a few seconds. And when it’s done, follow the same method to flash the root package – SR1-SuperSU-v2.78-SR1-20160915123031.zip
Click to expand...
Click to collapse
Wait 1 or 2 minutes after the zip files are done flashing then reboot system and PROFIT! Your phone may take 3-5 minutes to boot the first time and it might boot-loop once or twice at the Metro PCS splash screen but don’t worry this is expected.
All required files [supersu+dm-verify disable] can be found in this thread :
http://forum.xda-developers.com/lg-g5/development/recovery-team-win-recovery-project-lg-g5-t3363047
Like my work?
consider donating. TY
Nice :good:
Now...who's gonna be first to try this on a LS775 (not Stylo Plus xx550)?
Andromeda_Station said:
Nice :good:
Now...who's gonna be first to try this on a LS775 (not Stylo Plus xx550)?
Click to expand...
Click to collapse
Thx xD it should be safe to test if u are not doing anything wrong , are u able to enter fastboot mode ?
messi2050 said:
Thx xD it should be safe to test if u are not doing anything wrong , are u able to enter fastboot mode ?
Click to expand...
Click to collapse
Not yet...I need to make a proper back up before I do any messing around with this thing. I've got four phones here but the Stylo 2 is the only one I can't afford to brick right now
I thought the Stylo 2 Plus stuff had already been tried and didn't work on this?
Andromeda_Station said:
Not yet...I need to make a proper back up before I do any messing around with this thing. I've got four phones here but the Stylo 2 is the only one I can't afford to brick right now
I thought the Stylo 2 Plus stuff had already been tried and didn't work on this?
Click to expand...
Click to collapse
This is not a stylo 2 plus recovery that's twrp port for the stylo 2 ls775 model....
messi2050 said:
This is not a stylo 2 plus recovery that's twrp port for the stylo 2 ls775 model....
Click to expand...
Click to collapse
Ah, I see that now...just downloaded it.
No luck so far though...have USB debugging and 'enable OEM unlock' checked, 'adb reboot bootloader' and 'reboot to bootloader' from recovery both just boot as normal and power off/volume down+plug in USB just gives the battery charging screen.
Edit: Just went back and read some old threads over again...looks like no one has been able to get to fastboot post ZV3
Is anyone actively trying to get this to work? This is my last hope for this phone. If I cant get it rooted I'm switching phones.
Would this method work for LG VS835 (Stylo 2 V)
Araltd said:
Would this method work for LG VS835 (Stylo 2 V)
Click to expand...
Click to collapse
No
I have the VM version of the stylo 2. I got temp root at one point and tried to get full root via the terminal method but it didn't work and I have king root installed in the system but no root, Ive been trying this method but when I push the adb reboot boot loader command it reboots into the boot loader but I can't get any command to work after that. I launched the adb devices command and no device is listed, the only time the device is listed is when the phone is booted to the stock ROM. I'm currently downloading the lg bridge app in hopes it fixes this issue. I'm willing to do this because I have 3 VM variants of this phone all running zv3. Also my google apps are broke after attempting to achieve permanent root....I feel a Lil bummed about that lol
I spent a fair amount of time yesterday and today trying everything I could imagine to get to fastboot...nothing. Tried everything I could find for other LG models in case one worked...nope. Read every thread on every forum I could find that was posted to within the last 60 days. Pulled out the stylus and tried it all again (lol)...all the while being mocked by the cursed "Boost Zone" app icon.
Now I'm just trying to decide if I should pull my hair out, or punch myself in the nuts.
---------- Post added at 05:35 PM ---------- Previous post was at 05:32 PM ----------
bakerd62 said:
I'm willing to do this because I have 3 VM variants of this phone all running zv3. Also my google apps are broke after attempting to achieve permanent root....I feel a Lil bummed about that lol
Click to expand...
Click to collapse
AFAIK @DirtyPISTOLA is the only one who's pulled this off...everyone else got ZV4'd
You've probably already read these, but if not:
http://forum.xda-developers.com/android/help/lg-stylo-2-ls775-root-t3387009
http://forum.xda-developers.com/android/development/boost-varient-permanent-root-t3435543
I don't even know what I did?
So I tried this. First when I tried to Unlock the bootloader but no matter what I tried it wouldn't work. It would always return with the error saying the command is unrecognized (I tried the old and new command to unlock the bootloader). So then I figured I might as well try and flash the recovery anyways. I tried flashing TWRP and it worked. It comes up with a screen that asking if I want to keep my system partition unmodified. Whether I choose to or not it has a bunch of error messages when I try to factory reset. I'm completely confused. I have TWRP but it seems I can't do anything with it. My phone isn't bricked either. I can still boot into android just fine.
Slayer1822 Jr said:
So I tried this. First when I tried to Unlock the bootloader but no matter what I tried it wouldn't work. It would always return with the error saying the command is unrecognized (I tried the old and new command to unlock the bootloader). So then I figured I might as well try and flash the recovery anyways. I tried flashing TWRP and it worked. It comes up with a screen that asking if I want to keep my system partition unmodified. Whether I choose to or not it has a bunch of error messages when I try to factory reset. I'm completely confused. I have TWRP but it seems I can't do anything with it. My phone isn't bricked either. I can still boot into android just fine.
Click to expand...
Click to collapse
Huh...flashed it with fastboot? If so, what mode was your phone in when you did it?
Andromeda_Station said:
Huh...flashed it with fastboot? If so, what mode was your phone in when you did it?
Click to expand...
Click to collapse
It was in fastboot mode
Slayer1822 Jr said:
It was in fastboot mode
Click to expand...
Click to collapse
Ah...right, I see from the other thread you're on ZV3. I can't get to fastboot
Slayer1822 Jr said:
It was in fastboot mode
Click to expand...
Click to collapse
what's the output of [adb reboot recovery] ?
messi2050 said:
what's the output of [adb reboot recovery] ?
Click to expand...
Click to collapse
It reboots the phone into TWRP with the same message as the first time I booted to it (can see that in my post above)
I'm on zv6 how can I help
Sent from my LGLS775 using Tapatalk
So I figured out after many days of trying to flash a recovery through fastboot and didn't work, I found a way. This may work for zv4, zv5, and zv6 for I'm on zv3. Anywho I'll get started on what I did.
1) get some type of root (temp or perm)
2) download flashify from play store or Google
3) allow root access
4) open up flashify and choose recovery image
5) press choose image
6) locate where you downloaded your recovery
7) press on your image it will pop up a box click yup 8) it will flash, after the flash choose reboot now
9) for any reason you don't want to reboot right then but you want to later, go to flashify and click the 3 dots in the top right corner and press reboot recovery.
How do I get even temp root? I'm on zv6 if it matters.
Sent from my LGLS775 using Tapatalk
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!
Hey community,
I have been running Poco F1 with twrp and PixelExperience for the last 2 years. Considering the past record of the OS and my experience with the OS, I decided recently to upgrade to the newer PE12 for Poco F1 (maintained by Lakshay Garg). It went smooth initially and after the last OTA update, the phone started behaving weirdly.
Long story short,
This morning the phone went into an automatic restart and is now stuck in a boot loop. It boots and reaches the "G" logo and reboots. However, the weird part is,
Code:
fastboot flash
and
Code:
fastboot boot
are not available, throwing errors. The device is visible in
Code:
adb devices
and
Code:
fastboot devices
. This problem occurs when the phone is not plugged in. Once plugged in, the phone runs fine and everything just works. TWRP is not accessible, as if it is not there anymore and the only recovery that I can reach is the pixel recovery which has no option to flash any custom recovery (newbie, so not sure if something like this should exists or not).
I've tried various threads here and wasn't able to find any solution. Let me know what commands/outputs you guys might need from the device to help me in this.
Thanks in advance. Hope this gets fixed soon.
tysonX5653 said:
Hey community,
I have been running Poco F1 with twrp and PixelExperience for the last 2 years. Considering the past record of the OS and my experience with the OS, I decided recently to upgrade to the newer PE12 for Poco F1 (maintained by Lakshay Garg). It went smooth initially and after the last OTA update, the phone started behaving weirdly.
Long story short,
This morning the phone went into an automatic restart and is now stuck in a boot loop. It boots and reaches the "G" logo and reboots. However, the weird part is,
Code:
fastboot flash
and
Code:
fastboot boot
are not available, throwing errors. The device is visible in
Code:
adb devices
and
Code:
fastboot devices
. This problem occurs when the phone is not plugged in. Once plugged in, the phone runs fine and everything just works. TWRP is not accessible, as if it is not there anymore and the only recovery that I can reach is the pixel recovery which has no option to flash any custom recovery (newbie, so not sure if something like this should exists or not).
I've tried various threads here and wasn't able to find any solution. Let me know what commands/outputs you guys might need from the device to help me in this.
Thanks in advance. Hope this gets fixed soon.
Click to expand...
Click to collapse
Seems to be a battery problem. How old is it? You may need to replace it.
However make sure you followed the clean install method before you come on a conclusion. Also try to not use any Magisk modules.
Best Clean Install method:
Backup all your data. All your data into Internal Storage will be lost during this process.
Download latest Official TWRP Recovery, Pixel Experience build.
Create one Folder and move all the files you downloaded there.
Reboot to Fastboot Mode
Connect your device to PC and Boot into to TWRP via ADB or Minimal ADB and Fastboot:
Code:
fastboot boot <recovery_filename>.img
Example:
Code:
fastboot boot C:\Users\Retrial\Desktop\twrp-3.6.1_9-0-beryllium.img
Select Wipe > Advanced Wipe -> Select Dalvik / ART Cache, System, Data, Internal Storage, Vendor, Cache and then Swipe to Wipe.
Go back and select Wipe > Format Data > type yes
While you are in TWRP, transfer the Folder with the files you downloaded above.
Flash Pixel Experience ROM.
Flashing the ROM will replace TWRP with PE Recovery so OTA updates can be installed without problems since TWRP currently doesn't support decryption on A12 encypted ROMs - If you need in future to change ROM just fastboot boot to twrp via adb and flash img of twrp to recovery partition.
Done! Reboot to system.
Thanks, turns out that it was a battery problem after all. After battery replacement everything is working just fine. I also installed Awaken OS as Pixel Experience was removing the TWRP recovery each time I flashed it. Now as for my fastboot, initially it was not working; it was showing this error whenever I tried to flash TWRP recovery or any stock recovery:
Sending 'boot.img' (38640 KB) FAILED (Write to device failed (Cannot send after transport endpoint shutdown)) fastboot: error: Command failed
After this, the fastboot mode was diconnected and my phone was showing this Error:
Press any Key to Shut Down
It was resolved by running this bat file (as admin) :
https://bit.ly/31T2LcB
After running this file, there was no error and I was able to flash the twrp Recovery smoothly. So thanks for all the help really appreciate it.
tysonX5653 said:
Thanks, turns out that it was a battery problem after all. After battery replacement everything is working just fine. I also installed Awaken OS as Pixel Experience was removing the TWRP recovery each time I flashed it. Now as for my fastboot, initially it was not working; it was showing this error whenever I tried to flash TWRP recovery or any stock recovery:
Sending 'boot.img' (38640 KB) FAILED (Write to device failed (Cannot send after transport endpoint shutdown)) fastboot: error: Command failed
After this, the fastboot mode was diconnected and my phone was showing this Error:
Press any Key to Shut Down
It was resolved by running this bat file (as admin) :
https://bit.ly/31T2LcB
After running this file, there was no error and I was able to flash the twrp Recovery smoothly. So thanks for all the help really appreciate it.
Click to expand...
Click to collapse
Did you face the problem again?
I am using PE11 since last 2 years but suddenly i started facing the same problem. When plugged in, works fine. When I unplug it, works until screen is on and when I use power button to lock or unlock, phone goes into bootloop. I opend it in twrp where it can work as long as battery lasts, that's why I am not sure if it's a battery problem or something else