Per https://topjohnwu.github.io/Magisk/install.html#magisk-in-recovery installing Magisk as recovery due to No RAMDISK on my Moto E6.
"If your device does not have ramdisk in boot images, Magisk has no choice but to be installed in the recovery partition.
Click to expand...
Click to collapse
The phone was successfully unlocked per Motorola Unlock Your Bootloader.
Magisk_Manager generated magisk_Patched Img. Recovery_Image was extracted on PC with WinRAR from Get Droid Tips, Moto E6 Stock Collection, current download matches my Moto E6 build#, PPB29.73-81. My model is XT2005-5. To avoid corruption, I used ADB, not MTP to transfer files. ADB pushed WinRAR Extracted recovery image, and ADB pulled magisk_Patched image.
However, the Execution of ADB Fastboot flash recovery was "Image not signed or corrupt" per the following log:
Code:
C:\adb>fastboot flash recovery C:\adb\magisk_patched_k54ii.img
target reported max download size of 535822336 bytes
sending 'recovery' (16341 KB)...
OKAY [ 0.533s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.285s]
finished. total time: 0.820s
Why am I getting a corrupt image? Does anyone recommend a better Stock Recovery-Image source, perhaps where I can confirm the hashtag of the download and image extraction? TWRP does not seem to be an option for MotoE6/ No-RAMdisk devices.
I don't recommend images from Get Droid Tips, Moto E6 Stock Collection while they have the build numbers for the downloads, they did not show that there are various model numbers for the Moto E6. My guess is this is the likely cause of the "corrupt" image message from my flash recovery attempt.
I will use a stock image from https://mirrors.lolinet.com/firmware/moto/surfna/official/
kem827 said:
Per https://topjohnwu.github.io/Magisk/install.html#magisk-in-recovery installing Magisk as recovery due to No RAMDISK on my Moto E6.
The phone was successfully unlocked per Motorola Unlock Your Bootloader.
Magisk_Manager generated magisk_Patched Img. Recovery_Image was extracted on PC with WinRAR from Get Droid Tips, Moto E6 Stock Collection, current download matches my Moto E6 build#, PPB29.73-81. My model is XT2005-5. To avoid corruption, I used ADB, not MTP to transfer files. ADB pushed WinRAR Extracted recovery image, and ADB pulled magisk_Patched image.
However, the Execution of ADB Fastboot flash recovery was "Image not signed or corrupt" per the following log:
Code:
C:\adb>fastboot flash recovery C:\adb\magisk_patched_k54ii.img
target reported max download size of 535822336 bytes
sending 'recovery' (16341 KB)...
OKAY [ 0.533s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.285s]
finished. total time: 0.820s
Why am I getting a corrupt image? Does anyone recommend a better Stock Recovery-Image source, perhaps where I can confirm the hashtag of the download and image extraction? TWRP does not seem to be an option for MotoE6/ No-RAMdisk devices.
Click to expand...
Click to collapse
I don't know why this occurs, but it's "normal". What the installer guide doesn't tell you is:
- when you flash the patched recovery, you can't then use fastboot to get to recovery mode (well, you can...but it doesn't work). Instead, you MUST use the fastboot navigation keys (vol up/down and power) to go to recovery. When you do that, you'll boot the whole system into a rooted state (you won't see a recovery menu of any kind).
- at least on my phone, when you do this you are rooted for exactly one session. Next time you boot, the recovery image you flashed will be replaced with the "factory" original one. There is a work-around for this, but that's the behavior.
- if you are trying to install EdXposed, I don't believe you can do so just with the recovery-image method. You have to install the whole of Magisk (many MB) and I haven't figured out how to do this yet. (many, many false starts...)
dav0dav0 said:
I don't know why this occurs, but it's "normal". What the installer guide doesn't tell you is:
- when you flash the patched recovery, you can't then use fastboot to get to recovery mode (well, you can...but it doesn't work). Instead, you MUST use the fastboot navigation keys (vol up/down and power) to go to recovery. When you do that, you'll boot the whole system into a rooted state (you won't see a recovery menu of any kind).
- at least on my phone, when you do this you are rooted for exactly one session. Next time you boot, the recovery image you flashed will be replaced with the "factory" original one. There is a work-around for this, but that's the behavior.
- if you are trying to install EdXposed, I don't believe you can do so just with the recovery-image method. You have to install the whole of Magisk (many MB) and I haven't figured out how to do this yet. (many, many false starts...)
Click to expand...
Click to collapse
Ok, Thanks. Looks like my attempt to flash ( from Get Droid Tips, Moto E6 Stock Collection, ) was not the correct Moto E6 model. Phone boots still to the factory, and not rooted, but has a "bad key" error.. Boot to Recovery just responds "no command"
I did find now download the correct image from https://mirrors.lolinet.com/firmware/moto/surfna/official/ (matched by the Correct Moto E6 XT2005 model and build) but now ADB does not want to push or pull files. Unsure how to proceed.
I got my "stock ROM" by using Moto's "Rescue and Smart Assistant" tool -- it interrogates the phone, and lets you download the correct ZIP file automatically. Obviously, you do'nt want to actually install the ZIP -- you just want it downloaded. It puts the ZIP into a location it discloses, so you can find it. ;-)
Was ADB pushing/pulling files before? That's really weird if it did...but in any case, when the phone is booted to the normal system you can just copy the files over to the phone via the standard USB file sharing connection. If that's not working, you may need to reainstall the USB drivers on your PC. Don't forget to enable USB file sharing on the phone!
dav0dav0 said:
I got my "stock ROM" by using Moto's "Rescue and Smart Assistant" tool -- it interrogates the phone, and lets you download the correct ZIP file automatically. Obviously, you do'nt want to actually install the ZIP -- you just want it downloaded. It puts the ZIP into a location it discloses, so you can find it. ;-)
Was ADB pushing/pulling files before? That's really weird if it did...but in any case, when the phone is booted to the normal system you can just copy the files over to the phone via the standard USB file sharing connection. If that's not working, you may need to reainstall the USB drivers on your PC. Don't forget to enable USB file sharing on the phone!
Click to expand...
Click to collapse
ADB was pushing and pulling. I found the XDA posting that might help solve this official-tool-windows-adb-fastboot-and-drivers-15-seconds-ADB-installer-v1-4-3.2588979/. I'll update my drivers per the video found here, and try again.
While deleting some old Samsung Drivers was probably necessary, the error remained. Searched and found that the directory "/SD Card" is incorrect, even though topjohnwu.github failed to explain that "SD Card" is not the same folder as seen in the windows USB Link. It is the Internal SD Card which the ADB uses, which I find on windows at "Internal Shared Storage/Download". Once I moved the file on my phone to that folder , I was able to Pull the file using the command "ADB Pull \Sdcard\download.."
Reflashed my patched majesk recovery image. But, I can not boot recovery. Fastboot gives me a "no command" message. Screen always displays "bad key" on any boot. Holding power and tapping upkey does nothing in attempt to Boot to Recovery.
kem827 said:
Reflashed my patched majesk recovery image. But, I can not boot recovery. Fastboot gives me a "no command" message. Screen always displays "bad key" on any boot. Holding power and tapping upkey does nothing in attempt to Boot to Recovery.
Click to expand...
Click to collapse
I believe that the "bad key" message will occur whenever you have an unlocked bootloader. There is a way to hide it (search within XDA forums, you'll find several posts), but I leave it as is so I get a positive indicator of where I really am.
You say "Fastboot gives me a 'no command' message": I think what you mean is "when I go from Fastboot to Recovery mode, a get a 'no command' message." -- because the only time I've ever seen that message is under the Android-robot icon, which indicates "you're in stock recovery mode." When you are there, you should be able to get to the command menu by clicking power-on and volume-up simultaneously. If you don't, do a power cycle and try again.
You'll know you've booted the root mode when you don't see the "bad key" message, but instead see something like "Unsigned or corrupt image" when you go into recovery mode (and you won't see the normal Android icon or "no command" message).
In my experience with this phone, if you are in bootloader and use your PC to get you to recovery mode (fastboot reboot recovery from the command line), it may not work. The only way to reliably get into real recovery mode is to do a power cycle on the phone, go into fastboot, and then use the phone's buttons to get to recovery.
Also note that if all that you have done is the Magisk modify-recovery-image strategy, you get one (and only one) attempt to run as rooted. Any time you go thru a power-on reset of the phone, your modded-recovery image will be erased and replaced with the factory one.
In my various runs, I've determined that once you've achieved root access you can soft-reboot the phone and remain in root. Anything you install there will survive soft-reboots. But if you do a hard reboot, next time you go into root you may have to reinstall EdXposed and supporting libraries, and reactivate stuff for everything to work.
Sadly, the Xposed module I was doing all this for doesn't seem to work under EdXposed, even though it's supposed to. So it was a days-long wild goose chase.
dav0dav0 said:
I believe that the "bad key" message will occur whenever you have an unlocked bootloader. There is a way to hide it (search within XDA forums, you'll find several posts), but I leave it as is so I get a positive indicator of where I really am.
You say "Fastboot gives me a 'no command' message": I think what you mean is "when I go from Fastboot to Recovery mode, a get a 'no command' message." -- because the only time I've ever seen that message is under the Android-robot icon, which indicates "you're in stock recovery mode." When you are there, you should be able to get to the command menu by clicking power-on and volume-up simultaneously. If you don't, do a power cycle and try again.
You'll know you've booted the root mode when you don't see the "bad key" message, but instead see something like "Unsigned or corrupt image" when you go into recovery mode (and you won't see the normal Android icon or "no command" message).
In my experience with this phone, if you are in bootloader and use your PC to get you to recovery mode (fastboot reboot recovery from the command line), it may not work. The only way to reliably get into real recovery mode is to do a power cycle on the phone, go into fastboot, and then use the phone's buttons to get to recovery.
Also note that if all that you have done is the Magisk modify-recovery-image strategy, you get one (and only one) attempt to run as rooted. Any time you go thru a power-on reset of the phone, your modded-recovery image will be erased and replaced with the factory one.
In my various runs, I've determined that once you've achieved root access you can soft-reboot the phone and remain in root. Anything you install there will survive soft-reboots. But if you do a hard reboot, next time you go into root you may have to reinstall EdXposed and supporting libraries, and reactivate stuff for everything to work.
Sadly, the Xposed module I was doing all this for doesn't seem to work under EdXposed, even though it's supposed to. So it was a days-long wild goose chase.
Click to expand...
Click to collapse
Thanks for you help. I finally got a correct flash and boot to a rooted recovery. Looks like Top Johns' Magisk Instruction Page needs some corrections: Like explaining that "SDCard" shows as [internal storage] on the PC and that the external Storage is the [SD Card] directory. He fails to tell to rename the magisk_patched file to "recovery. img" before flashing it. (An obvious error but easy to overlook when you are following an unfamiliar command syntax) . The "bad key" message and "corrupt signature" message explanation is useful info too. He fails to let you know how to even check for a successful root
kem827 said:
Thanks for you help. I finally got a correct flash and boot to a rooted recovery. Looks like Top Johns' Magisk Instruction Page needs some corrections: Like explaining that "SDCard" shows as [internal storage] on the PC and that the external Storage is the [SD Card] directory. He fails to tell to rename the magisk_patched file to "recovery. img" before flashing it. (An obvious error but easy to overlook when you are following an unfamiliar command syntax) . The "bad key" message and "corrupt signature" message explanation is useful info too. He fails to let you know how to even check for a successful root
Click to expand...
Click to collapse
And to add to the fun...Magisk Manager has/had a bug where it will tell you that your phone *doesn't* have a RAMdisk but it actually does....sometimes. So you might try to do the boot.img patch instead of the recovery.img one--that would give you a permanent root, rather than a transitory one. I didn't bother to check that out, as the whole reason I was rooting was to use an Xposed module that doesn't seem to work.
Let me know if you try that strategy out and it works...
kem827 said:
Thanks for you help. I finally got a correct flash and boot to a rooted recovery. Looks like Top Johns' Magisk Instruction Page needs some corrections: Like explaining that "SDCard" shows as [internal storage] on the PC and that the external Storage is the [SD Card] directory. He fails to tell to rename the magisk_patched file to "recovery. img" before flashing it. (An obvious error but easy to overlook when you are following an unfamiliar command syntax) . The "bad key" message and "corrupt signature" message explanation is useful info too. He fails to let you know how to even check for a successful root
Click to expand...
Click to collapse
The instructions assume that you are somewhat familiar with Android, adb and fastboot. There's plenty of info and guides on that around the web, so it would be redundant for John to add that too (and the instructions would become way too long).
There are also many devices specific things that he's never gonna be able to cover. The fractured nature of Android is just too much for that...
If you have suggestions though, you can always open a PR on GitHub with your proposed changes and clarifications.
dav0dav0 said:
Magisk Manager has/had a bug where it will tell you that your phone *doesn't* have a RAMdisk but it actually does....sometimes
Click to expand...
Click to collapse
That's not a bug with Magisk, but yet another issue with Android's fractured ecosystem. John actually covers that in his documentation. Check this page, and in particular the last paragraph:
https://topjohnwu.github.io/Magisk/boot.html
Related
Hi everyone i´m new to this forum. I own a Asus ME176CX and updated to official lollipop 5 from asus.com. The device is rooted and it was a little bit slow so i decided to uninstall via root uninstall some of the Bloat Apps.
The Result is ... I messed it up. I deinstalled too many apps, and it seems that i uninstall some system apps too. When my device is booting it wont stop booting and i´m only able to turn the device off.
I can get into fastboot but my recovery mode says only failed when i try to start it. I´m really new to Android and asking for some advise here. I tried a lot of this workarounds here but nothing worked for me
#pleasehelpthenoob
Thanks in Advance
Waido1981 said:
Hi everyone i´m new to this forum. I own a Asus ME176CX and updated to official lollipop 5 from asus.com. The device is rooted and it was a little bit slow so i decided to uninstall via root uninstall some of the Bloat Apps.
The Result is ... I messed it up. I deinstalled too many apps, and it seems that i uninstall some system apps too. When my device is booting it wont stop booting and i´m only able to turn the device off.
I can get into fastboot but my recovery mode says only failed when i try to start it. I´m really new to Android and asking for some advise here. I tried a lot of this workarounds here but nothing worked for me
#pleasehelpthenoobA
Thanks in Advance
Click to expand...
Click to collapse
If you want lollipop, take it to warranty. If you don't mind getting stuck on kitkat (after lollipop update you can run windows or linux on this tablet, and maybe use custom rom if anyone will make it using my idea), just say and I will write you steps how to get kitkat back.
Waido1981 said:
Hi everyone i´m new to this forum. I own a Asus ME176CX and updated to official lollipop 5 from asus.com. The device is rooted and it was a little bit slow so i decided to uninstall via root uninstall some of the Bloat Apps.
The Result is ... I messed it up. I deinstalled too many apps, and it seems that i uninstall some system apps too. When my device is booting it wont stop booting and i´m only able to turn the device off.
I can get into fastboot but my recovery mode says only failed when i try to start it. I´m really new to Android and asking for some advise here. I tried a lot of this workarounds here but nothing worked for me
#pleasehelpthenoob
Thanks in Advance
Click to expand...
Click to collapse
Did you manage to work it out as I'm in the same boat at the moment - I can get to fastboot and can power on and off but stuck at boot! recovery efforts just show dead android and "Error"!
Anyone?
Cheers
noggin-the-nog said:
Did you manage to work it out as I'm in the same boat at the moment - I can get to fastboot and can power on and off but stuck at boot! recovery efforts just show dead android and "Error"!
Anyone?
Cheers
Click to expand...
Click to collapse
yeah my girlfriend has the same tablet. I took a backup with girlfriends device with fbrl and get it on my device. Just had to change settings and accounts and everything works well again.
Hi Everyone, I'm new here too.
I have the same problem in this topic.
I can use fastboot mode Only, I can't use adb mode, and the bootloader is locked.
when i was trying to install original firmware with this command:
fastboot update update.zip
I get this messege:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
I need solution for this.
I haven't problem to installing any operating system, like Windows, Ubuntu, Tizen, Android x86, or other.
Please, I really need help, more than five months i am looking for a way out from this problem but it's all failed, because the boot loader was locked.
Any help would be very appreciated.
Thank you in advance.
Hi
Doesn't anybody have any ideas to help me ?
Maybe I must unlock bootloader to solve my problem.
But how I can do that ?
Waido1981 said:
Hi everyone i´m new to this forum. I own a Asus ME176CX and updated to official lollipop 5 from asus.com. The device is rooted and it was a little bit slow so i decided to uninstall via root uninstall some of the Bloat Apps.
The Result is ... I messed it up. I deinstalled too many apps, and it seems that i uninstall some system apps too. When my device is booting it wont stop booting and i´m only able to turn the device off.
I can get into fastboot but my recovery mode says only failed when i try to start it. I´m really new to Android and asking for some advise here. I tried a lot of this workarounds here but nothing worked for me
#pleasehelpthenoob
Thanks in Advance
Click to expand...
Click to collapse
For people with access to bootloader:
1- Download .17 and extract it on desktop
2- go to META-INF\com\google\android\updater-script and open it with notepad ++, and delete first 2 lines
3- compress it and rename it to update.zip and place it in adb folder (for me its c:\\adb)
4- shutdown the tablet and press (power and vol-) to go to bootloader.
5- write on adb "adb push update.zip /sdcard/" wait until it finishes (dont leave bootloader)
6- Download Temp Recovery: www.androidfilehost.com/?fid=24052804347782876
7- On windows, open temp recovery program, and say "ACCEPT", and press 2 then press T4 and it should boot to the temp recovery on the tablet.
8- then install the update.zip, and then format cache and dalvik, then reboot and it should be fixed.
//////////////////////////////////////////////////////
//////////////////////////////////////////////////////
For people without access to bootloader:
1- Download .17 and extract it on desktop
2- go to META-INF\com\google\android\updater-script and open it with notepad ++, and delete first 2 lines
3- compress it and rename it to update.zip and place it in adb folder (for me its c:\\adb)
4- copy droidboot.img from .17 and put in in adb folder
5- go to fastboot and write "fastboot boot droidboot.img" it should boot to bootlaoder *do it at least 10 times because sometimes, the tablet boots to software and not bootloader*
6- if you are in bootloader then, Download Temp Recovery: www.androidfilehost.com/?fid=24052804347782876
7- After downloading, On windows, open temp recovery program, and say "ACCEPT", and press 2 then press T4 and it should boot to the temp recovery on the tablet.
8- then install the update.zip, and then format cache and dalvik, then reboot and it should be fixed.
//////////////////////////////
Good Luck! :laugh:
//////////////////////////////
Ruben Craveiro said:
For people without access to bootloader:
1- Download .17 and extract it on desktop
......
7- After downloading, On windows, open temp recovery program, and say "ACCEPT", and press 2 then press T4 and it should boot to the temp recovery on the tablet.
Click to expand...
Click to collapse
Hi Ruben,
What do you mean from step 1 ? Where can I find the (.17) to i can download it ?
When I perform step 7, it gave me error.
Overall, I had sent my problem to Asus support and their interaction was bad enough to hates them.
My problem has now ten months I have not found a solution, and the company asking me to send the device to America and I'm outside America.
I promise you I will avoid buying Asus devices from today onwards.
Thank you for trying to help us.
Venting said:
Hi Ruben,
What do you mean from step 1 ? Where can I find the (.17) to i can download it ?
When I perform step 7, it gave me error.
Overall, I had sent my problem to Asus support and their interaction was bad enough to hates them.
My problem has now ten months I have not found a solution, and the company asking me to send the device to America and I'm outside America.
I promise you I will avoid buying Asus devices from today onwards.
Thank you for trying to help us.
Click to expand...
Click to collapse
Did you manage to boot into the temp TWRP recovery or is that not working either?
lambdadroid said:
Did you manage to boot into the temp TWRP recovery or is that not working either?
Click to expand...
Click to collapse
Hello lambdadroid,
No, It's not work.
Venting said:
Hello lambdadroid,
No, It's not work.
Click to expand...
Click to collapse
You said you have access to fastboot though? Then you should also be able to boot into the temp recovery (e.g. TWRP)
lambdadroid said:
You said you have access to fastboot though? Then you should also be able to boot into the temp recovery (e.g. TWRP)
Click to expand...
Click to collapse
OK ..
I don't flashed the TWRP Recovery, and I can't get into fastboot / droidboot mode.
But when I press on this buttons (Volume up + Volume down + and Power) while booting, the device stopped on the ASUS logo screen, and in this status my PC connected with my Tablet device, and I can use fastboot commands, no thing other.
I can't use the ADB commands.
Also, When I tried flashing the firmware with ASUS Flash Tool, or CMD shell, I got the same message: FAILED (remote failure).
When I was trying to install the original firmware through CMD Shell with this command: "fastboot flash update update.zip"
I got this message:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
When I tried with IntelAndroid-FBRL-07-24-2015 to flash TWRP or CWM Recovery, I got the error messages such as:
FAILED (data transfer failure (Unknown error))
FAILED (command write failed (No such device or address))
FAILED (command write failed (Unknown error))
I can't write anything to the device, That's everything.
I think i must unlock the bootloader to solve my problem.
But how do I do that ?
Venting said:
OK ..
I don't flashed the TWRP Recovery, and I can't get into fastboot / droidboot mode.
But when I press on this buttons (Volume up + Volume down + and Power) while booting, the device stopped on the ASUS logo screen, and in this status my PC connected with my Tablet device, and I can use fastboot commands, no thing other.
I can't use the ADB commands.
Also, When I tried flashing the firmware with ASUS Flash Tool, or CMD shell, I got the same message: FAILED (remote failure).
When I was trying to install the original firmware through CMD Shell with this command: "fastboot flash update update.zip"
I got this message:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
When I tried with IntelAndroid-FBRL-07-24-2015 to flash TWRP or CWM Recovery, I got the error messages such as:
FAILED (data transfer failure (Unknown error))
FAILED (command write failed (No such device or address))
FAILED (command write failed (Unknown error))
I can't write anything to the device, That's everything.
I think i must unlock the bootloader to solve my problem.
But how do I do that ?
Click to expand...
Click to collapse
What you're saying doesn't make much sense. How did you actually mess up your tablet?
Please also tell me the following:
- What happens if you power on the tablet normally?
- What happens if you power on the tablet using Vol+ and the power button?
- What happens if you power on the tablet using Vol- and the power button?
Unlocking the bootloader is not possible on this device and it wouldn't help you anyway if you can't get into fastboot (the droidboot screen). As far as I know the fastboot screen you can enter with Vol+ and Vol- and the power button is pretty much useless, you need the droidboot screen to recover your tablet.
lambdadroid said:
What you're saying doesn't make much sense. How did you actually mess up your tablet?
Please also tell me the following:
- What happens if you power on the tablet normally?
- What happens if you power on the tablet using Vol+ and the power button?
- What happens if you power on the tablet using Vol- and the power button?
Unlocking the bootloader is not possible on this device and it wouldn't help you anyway if you can't get into fastboot (the droidboot screen). As far as I know the fastboot screen you can enter with Vol+ and Vol- and the power button is pretty much useless, you need the droidboot screen to recover your tablet.
Click to expand...
Click to collapse
If I press on the power button normally
Or I press on Volume up button, and Power button
Or I press on Volume down button, and Power button
The result is the same, It's a red line is showing on screen bottom, then the device stops working.
You can see this Picture here
Venting said:
If I press on the power button normally
Or I press on Volume up button, and Power button
Or I press on Volume down button, and Power button
The result is the same, It's a red line is showing on screen bottom, then the device stops working.
You can see this Picture here
Click to expand...
Click to collapse
How did you actually mess up your tablet?
I don't think you'll have many options to repair your tablet at this point. You could have luck if you have a powered OTG hub, by booting something like Linux and flashing the necessary stuff back to the internal storage, although depending on how much you messed up, that may not make things better. The other option is sending it in to ASUS.
Venting said:
Hi Ruben,
What do you mean from step 1 ? Where can I find the (.17) to i can download it ?
When I perform step 7, it gave me error.
Overall, I had sent my problem to Asus support and their interaction was bad enough to hates them.
My problem has now ten months I have not found a solution, and the company asking me to send the device to America and I'm outside America.
I promise you I will avoid buying Asus devices from today onwards.
Thank you for trying to help us.
Click to expand...
Click to collapse
what i mean with .17 is the software (first lollipop release)
you can get it here: http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/UL-K013-WW-12.10.1.17_KK-user.zip
and to run the temp recovery make sure you have access to bootloader and have all drivers installed, if your computers says something about adb drivers for bootloader add these drivers so that it works: http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/ADB_driver.zip if you still cant acces is because you did not installed properly all the needed drivers. I wish u luck.
---------- Post added at 08:49 PM ---------- Previous post was at 08:44 PM ----------
[/COLOR]
Venting said:
If I press on the power button normally
Or I press on Volume up button, and Power button
Or I press on Volume down button, and Power button
The result is the same, It's a red line is showing on screen bottom, then the device stops working.
You can see this Picture here
Click to expand...
Click to collapse
if you cant access bootloader or fastboot the only way to get it back, is to have a otg powered hub, and run uefi, and then boot linux and then reinstall the android partitions. (im very newbie at this so i cant tell u much about it)
---------- Post added at 09:00 PM ---------- Previous post was at 08:49 PM ----------
Venting said:
OK ..
I don't flashed the TWRP Recovery, and I can't get into fastboot / droidboot mode.
But when I press on this buttons (Volume up + Volume down + and Power) while booting, the device stopped on the ASUS logo screen, and in this status my PC connected with my Tablet device, and I can use fastboot commands, no thing other.
I can't use the ADB commands.
Also, When I tried flashing the firmware with ASUS Flash Tool, or CMD shell, I got the same message: FAILED (remote failure).
When I was trying to install the original firmware through CMD Shell with this command: "fastboot flash update update.zip"
I got this message:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
When I tried with IntelAndroid-FBRL-07-24-2015 to flash TWRP or CWM Recovery, I got the error messages such as:
FAILED (data transfer failure (Unknown error))
FAILED (command write failed (No such device or address))
FAILED (command write failed (Unknown error))
I can't write anything to the device, That's everything.
I think i must unlock the bootloader to solve my problem.
But how do I do that ?
Click to expand...
Click to collapse
well you have made some stuff wrong, BUT i think you can get it back, first of all its not supposed for you to actually install twrp or cwm, and you need this file: (droidboot.img) https://drive.google.com/file/d/0B3h_JptTNZeeRjdXdE1rWlNLYnM/view?usp=sharing
and place it in c:\\adb and then do fastboot boot droidboot.img and then it should boot to the bootloader if it doesnt, then do it again and again until it does.. (you need to do it several times to make it work, at least thats how i got out of bootloop), then in the bootloader you have access to adb commands so temp recovery should be working, if it still doesnt then it means it needs the adb drivers for the bootloader, after u loaded twrp recovery load .17 update(place the update in microsd, or adb push update.zip /sdcard/) and it should work
lambdadroid, Ruben Craveiro
Thank you guys so much for trying help me.
I tried everything except OTG powered hub.
I will try with OTG powered hub, and I hope solves my problem.
Thank you for everything.
Ruben Craveiro said:
For people with access to bootloader:
1- Download .17 and extract it on desktop
2- go to META-INF\com\google\android\updater-script and open it with notepad ++, and delete first 2 lines
3- compress it and rename it to update.zip and place it in adb folder (for me its c:\\adb)
4- shutdown the tablet and press (power and vol-) to go to bootloader.
5- write on adb "adb push update.zip /sdcard/" wait until it finishes (dont leave bootloader)
6- Download Temp Recovery:
7- On windows, open temp recovery program, and say "ACCEPT", and press 2 then press T4 and it should boot to the temp recovery on the tablet.
8- then install the update.zip, and then format cache and dalvik, then reboot and it should be fixed.
//////////////////////////////////////////////////////
//////////////////////////////////////////////////////
For people without access to bootloader:
1- Download .17 and extract it on desktop
2- go to META-INF\com\google\android\updater-script and open it with notepad ++, and delete first 2 lines
3- compress it and rename it to update.zip and place it in adb folder (for me its c:\\adb)
4- copy droidboot.img from .17 and put in in adb folder
5- go to fastboot and write "fastboot boot droidboot.img" it should boot to bootlaoder *do it at least 10 times because sometimes, the tablet boots to software and not bootloader*
6- if you are in bootloader then, Download Temp Recovery
7- After downloading, On windows, open temp recovery program, and say "ACCEPT", and press 2 then press T4 and it should boot to the temp recovery on the tablet.
8- then install the update.zip, and then format cache and dalvik, then reboot and it should be fixed.
//////////////////////////////
Good Luck! :laugh:
//////////////////////////////
Click to expand...
Click to collapse
Hello
I tried these two methods to recover my unrooted Memo tab. The push method doesn't do anything and the second method says "wating for device"
A little background info on how I got here. The tablet got stuck on the loading screen after the last OTA update. I tried to do the factory reset from the tablet but I get the following messsage, "E: Can't open /dev/block/by-name/misc"
I have also tried to load the zip file using sideload and get the following message.
E:failed to verify whole-file signature
E:signature verification failed
Not sure what else to try...any help is appreciated.
wifebeeter said:
Hello
I tried these two methods to recover my unrooted Memo tab. The push method doesn't do anything and the second method says "wating for device"
A little background info on how I got here. The tablet got stuck on the loading screen after the last OTA update. I tried to do the factory reset from the tablet but I get the following messsage, "E: Can't open /dev/block/by-name/misc"
I have also tried to load the zip file using sideload and get the following message.
E:failed to verify whole-file signature
E:signature verification failed
Not sure what else to try...any help is appreciated.
Click to expand...
Click to collapse
make sure your device is conected to pc and that it has all the drivers needed (adb drivers)...boot into bootloader and load temp recovery and flash latest version
---------- Post added at 10:10 PM ---------- Previous post was at 10:00 PM ----------
Venting said:
lambdadroid, Ruben Craveiro
Thank you guys so much for trying help me.
I tried everything except OTG powered hub.
I will try with OTG powered hub, and I hope solves my problem.
Thank you for everything.
Click to expand...
Click to collapse
you can access dnx mode(fastboot starting #1#2#3), so you can go into bootloader, heres how: get the file efilinux.efi and droidboot.img and put them in adb folder (you can get the droidboot.img on update.zip and if u look on .33 version theres a zip inside of it that its called ESP, you can find efilinux.efi from there) after doing that go into DnX mode on the tablet, and do these fastboot commands: "fastboot flash osloader efilinux.efi" and do "fastboot boot droidboot.img" and this will certainly make you boot to droidboot/bootloader and from there you can load temp recovery and flash the software, and no need for otg hub
Ruben Craveiro said:
make sure your device is conected to pc and that it has all the drivers needed (adb drivers)...boot into bootloader and load temp recovery and flash latest version
HI
I tried temporary recovery and I get the following messege.
error: closed
<waiting for device>
Click to expand...
Click to collapse
Okay so I got my oneplus 3t today and I updated it to Nougat via the ota file all good so far. I then decided that I wanted to install a custom rom so I downloaded twrp supersu etc everything needed to root and install the rom. Here's where it went wrong in knowingly I downloaded the wrong twrp flashed it and it would just hang at the flash screen for twrp. Anyway after hours of trying to install a recovery I managed to get a stock one to semi work, now it turns out I don't know how I did it but my phone won't even boot it just turns on and goes straight to fastboot mode. I managed to get a stock recovery semi working but it won't let me install the stock rom from internal storage and I've tried updating through adb and it will hang at a random percentage for a good 20 mins and then just fail. Really need some help here it would be great, thanks
Hi,
If you can get into fastboot mode then the best recourse is through there. Hope you properly OEM unlocked your device.
First of all, you MUST have the latest adb/fastboot binaries and FOR SURE have the correct drivers.
Follow the links on this XDA article to download the latest adb and fastboot binaries: https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads
This is the link for the Windows binary: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Extract all the contents of the zip file in a folder on your PC.
Then, also make sure to have THE CORRECT twrp, 3.0.2.0 or 3.0.3.0. This is the link but currently it is down: https://twrp.me/devices/oneplus3t.html
Download THE IMAGE, NOT FLASHABLE ZIP and put it in the same folder as the android platform tools above.
Finally, download the latest complete 3T firmware from OnePlus from this link: http://downloads.oneplus.net/devices/oneplus-3t/
I STRONGLY recommend not to use an update zip, even a full ROM update zip as that one might not include certain firmware images.
Put THE ZIP on the same folder as the others, DO NOT EXTRACT ANYTHING.
On your PC, open a command prompt in the folder where you extracted the android platform tools and run the following: fastboot boot twrp-3.0.3-0-oneplus3t.img (assuming you downloaded the 3.0.3 version of twrp).
Your phone will TEMPORARILY accept the twrp recovery as a boot image and boot from there. NOTHING IS BEING PERMANENTLY WRITTEN AT THIS TIME.
After that, enter TWRP's Wipe menu and wipe system, data and cache.
Finally, use TWRP's Advanced menu and enter adb sideload mode. Once there slide that slider to the right to enable adb mode and return to your PC and enter the following command in the command prompt:
adb sideload OnePlus3TOxygen_28_OTA_029_all_1612131737_17e7161d2b234949.zip (assuming you downloaded the 3.5.4 binary from OnePlus).
TWRP should properly flash the OnePlus ROM and hopefully, return you to proper function. You can then update back to Nougat.
Hope that helped!
Yeah that sorted it thanks a lot
Use the emergency tool for OP3T and start from scratch:
https://forums.oneplus.net/threads/unbrick-guide-oneplus-3t.481214/
@KeyperOS
I'm trying to follow this guide, but did you miss something out here?
On your PC, open a command prompt in the folder where you extracted the android platform tools and run the following: fastboot boot twrp-3.0.3-0-oneplus3t.img (assuming you downloaded the 3.0.3 version of twrp).
Your phone will TEMPORARILY accept the twrp recovery as a boot image and boot from there. NOTHING IS BEING PERMANENTLY WRITTEN AT THIS TIME.
Click to expand...
Click to collapse
Once I do "fastboot boot twrp" and get a success, then what?
Do I need to somehow reboot the phone into TWRP - because that didn't happen on its own.
If so, how do I do this?
Thanks,
jackmacbunton said:
Yeah that sorted it thanks a lot
Click to expand...
Click to collapse
Glad that sorted it out
PugRallye said:
@KeyperOSI'm trying to follow this guide, but did you miss something out here?
Once I do "fastboot boot twrp" and get a success, then what? Do I need to somehow reboot the phone into TWRP - because that didn't happen on its own. If so, how do I do this? Thanks,
Click to expand...
Click to collapse
My instructions while detailed are not step-by-step. I expect the person reading them to have their PC configured correctly and at least a vague idea of what they're doing.
So, assuming you put the correct TWRP image (my command uses the name of the image for TWRP 3.0.3.0, you MUST alter it to reflect the actual image's filename if it's not that) on the same folder as the fastboot binary then yeah, the command
fastboot boot twrp-3.0.3-0-oneplus3t.img
should have made your phone reboot and enter into the TWRP image that you had on your PC.
If it didn't then you did sth else wrong before that.
Either you didn't OEM unlock your phone when you still could or you didn't use the android platform tools that I linked or you don't have the correct ADB drivers installed on your PC.
Start from there.
Hope that helped!
Thanks for your help @KeyperOS - I know where I went wrong...
To save some time, when I tried to reboot into TWRP, I typed "fastboot boot " then I dragged and dropped the TWRP img file onto that line in the cmd window (rather than typing the filename manually) - when you do that, it appears to include the full path to the img - it was that that was causing the problem.
When I typed the TWRP filename manually, it worked.
The only thing that caught me out was after I'd installed the ROM (via adb sideload) I tried to reboot the device from TWRP recovery - this seemed to just hang. In the end I just powered off the phone using the power key, then powered it back up as per usual.
Checked that the phone booted to the first of the setup screens, then powered off/booted into fastboot mode, relocked the bootloader and it seems to be OK.
I'm now back on 3.5.4 again, which was what I was trying to do...
4.0.0/1 had felt a bit laggy, and I'd sensed some issues with wifi and BT, I can now run 3.5.4 and see how it compares - was I just imagining it?
Thanks again for the guide and your help - I really appreciated it
@PugRallye
Windows' command prompt has an autocomplete feature. If you want it to add the name of a file, type a couple letters and then present TAB, it's gonna complete the filename itself and if it's the wrong file you can keep tapping tab to cycle through all the options.
Really glad it worked out Btw [emoji4]
In my experience, 3.5.4 was great but 4.0 is a step up in both battery life, which IME is amazing and features, with it I almost didn't need root and certainly don't need xposed which was a first.
Where I can find official ROM for asus me375cl based on android 5.1.1?
Finaly, i find zip with official ROM on 4pda:
4pda-ru/forum/index.php?showtopic=799982
(put '.' (dot) instead '-' in url)
A special thank to alexoid79 for instruction.
little_pindos said:
Finaly, i find zip with official ROM on 4pda:
4pda-ru/forum/index.php?showtopic=799982
(put '.' (dot) instead '-' in url)
A special thank to alexoid79 for instruction.
Click to expand...
Click to collapse
Thank you so much for posting where you found this, this is exactly what I needed!!! You saved my tablet, it is much appreciated! :good:
Flashing Factory Image
The following instructions worked for me when trying to reflash the factory firmware for the ATT Asus MemoPad 7 LTE (ME375CL). I did originally try using the Asus Flash Tool and the raw firmware file (link below) but the tool said it could not unzip the package for some reason or another. So the steps below show how I did it using ADB with fastboot.
I ASSUME NO LIABILITY SHOULD THIS GO WRONG FOR YOU! However, it probably shouldn't matter if you are bricked, I doubt it will make it any worse Either way, I will not replace your tablet or be responsible for troubleshooting it should you mess it up more...
This scenario is based on the tablet stuck on the Asus boot screen and not going any further. I was trying some in depth rooting attempts and bricked it badly. I was then trying to install a custom recovery and that is why I could not reset it and bricked it.
PRE-REQS:
1. ADB installed - Download: https://drive.google.com/open?id=0B0fKccJIuWsna04wMjY1eG9YREU
2. Asus Drivers installed
3. Firmware - Download: https://drive.google.com/open?id=0B0fKccJIuWsnWGhwYzA0Vkluc2s (file is 1 Gb + in size, may take a bit)
SETUP:
If you already have a working ADB setup, do not download the one above. If you are using the one above, I extracted the folder into my C: drive, so the path for ADB would be C:\adb (to keep it simple and less typing).
MAKE SURE THE ASUS DRIVERS ARE INSTALLED! If you have plugged the tablet in to a pc before, they should already be there. Otherwise search, download and install the appropriate drivers.
INSTRUCTIONS:
Extract the firmware zip file to somewhere easily accessible like your desktop. In there, you should see the boot.img, recovery.img and system.img files, copy/paste those files to your ADB folder (for easier typing later on). There are also additional files like these but start with "unsigned_", do NOT use those!
1. Ensure you probably have at least 30% battery charge, I would still recommend more though.
2. Put the tablet in Fastboot mode by ensuring the tablet is completely powered down and then press/hold the VOLUME UP and POWER keys at the same time. When the Asus screen appears, let go of the POWER button but continue to hold the VOLUME UP button. Let go of the VOLUME UP button when the fastboot screen appears.
3. Plug the tablet in to the computer and then open a CMD prompt as administrator.
4. The following uses the ADB downloaded and placed in the folder as listed above, you may need to adjust the location path as needed if you already have ADB installed or located in a different path.
Type in the following without the quotes: "cd c:\adb" (this will change the path to the ADB files for the CMD prompt)
Type in the following without the quotes: "fastboot devices" (you should then see a device listed)
Type in the following without the quotes: "fastboot flash recovery recovery.img" (flashes the factory recovery image)
Type in the following without the quotes: "fastboot flash system system.img" (flashes the factory system image, may take a while to flash)
Type in the following without the quotes: "fastboot flash boot boot.img" (flashes the factory boot image)
5. Once those 3 images have been flashed, you should have seen a message that says "OKAY" after each one. You should be fine as long as you do not have any red error messages on your tablet.
Type in the following without the quotes: "fastboot reboot" (reboots device normally)
6. If all goes well, it should now boot to the Asus screen and then go to the ATT screen. If so, it will stay on the ATT screen for a while, just wait it out. Mine took about 12-15 minutes and then it opened to the new setup screen to set the tablet up as if its new!
This is how I was able to recover my bricked tablet, hopefully it can help someone else that may run into this.
John, thank you for the write-up. Just bought my ME375CL with 4.4.4.4.
When I try to flash the recovery partition, I get the following error:
C:\Users\Myself\Desktop\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (11312 KB)...
OKAY [ 1.047s]
writing 'recovery'...
(bootloader) Official image.
FAILED (remote: flash_cmds error!
)
finished. total time: 2.344s
Click to expand...
Click to collapse
and on the tablet's screen:
FASTBOOT CMD WAITING...
RECEIVE DATA...
E:recovery flash failed!
FLASH FAILED!
RESULT: FAIL(flash_cmds error! )
Click to expand...
Click to collapse
I haven't tried the other commands for system.img or boot.img as I don't want to do anything out of order from the write-up. Ever run into this?
The firmware in the download is 5.1.1, not 4.4.4. That is probably the issue. If you are running good on that, I would try rooting it instead. If you are just wanting to upgrade, you will need to have an active AT&T SIM in the tablet to upgrade over the air. I am not sure if there is a flashable upgrade or not somewhere.
Oh ok John. I misread the title of the thread. I thought it was for updating from 4 to 5.
Quick question then: Is it possible, using the adb / fastboot tools, to backup the current 4.4.4.4 before I allow the tablet to update to Lollipop? After reading around, I understand that Lollipop can't be rooted but I have no real concern for it. But just in case I need the tablet to do something else in the future, I'd like to be able to return it to kit kat to be able to root.
Once you upgrade to lollipop, there is no downgrading for this tablet. There really is not much development for this device. I have kind of been working on a lollipop root when I can. Between my limited time and knowledge of android, I can't promise anything.
Overcoming red messages?
Dear John,
Thank you very much for your help. My device runs KitKat 4.4, I can't upgrade over the air, as I damaged my sim slot struggling to remove a stuck nano sim, which I had inserted before I realized that it required a micro sim. (I'd wrongly assumed that by now the world uses only nano).
I followed the steps above, which you wrote so clearly for lay men, thank you a lot.
The flash for recovery.img and system.img worked fine (no red error messages on device).
The flash for boot.img had a red error message.
Might you have an idea or workaround on how I can address this?
If it refuses, is it possible to factory reset?
Thank you very much again for any words of advice and kind regards.
Gor- said:
Dear John,
Thank you very much for your help. My device runs KitKat 4.4, I can't upgrade over the air, as I damaged my sim slot struggling to remove a stuck nano sim, which I had inserted before I realized that it required a micro sim. (I'd wrongly assumed that by now the world uses only nano).
I followed the steps above, which you wrote so clearly for lay men, thank you a lot.
The flash for recovery.img and system.img worked fine (no red error messages on device).
The flash for boot.img had a red error message.
Might you have an idea or workaround on how I can address this?
If it refuses, is it possible to factory reset?
Thank you very much again for any words of advice and kind regards.
Click to expand...
Click to collapse
Sounds odd that it did 2 out of 3 flashes. After you flashed those and rebooted, are you still on KitKat or did it actually update to Lollipop (5.1)? I ask because I assume the system image that flashed would be the operating system.
I still want to stress that this post is for recovering a bricked tablet that will not boot at all. I would not suggest using this as a flashing upgrade as I do not know if it will truly work. If you are still on KK (even after flashing) you could try installing the Asus Flash Tool and use the raw firmware that you downloaded and try it that way. It did not work for me so that is why I used fastboot. It might work for you.
Here is a link for the Asus Flash Tool:
https://drive.google.com/open?id=0B0fKccJIuWsndXJUa1FEbXVzTjA
johnkirchner said:
Sounds odd that it did 2 out of 3 flashes. After you flashed those and rebooted, are you still on KitKat or did it actually update to Lollipop (5.1)? I ask because I assume the system image that flashed would be the operating system.
I still want to stress that this post is for recovering a bricked tablet that will not boot at all. I would not suggest using this as a flashing upgrade as I do not know if it will truly work. If you are still on KK (even after flashing) you could try installing the Asus Flash Tool and use the raw firmware that you downloaded and try it that way. It did not work for me so that is why I used fastboot. It might work for you.
Here is a link for the Asus Flash Tool: ]
Click to expand...
Click to collapse
As a follow up on your question above, Tab restart stalled at a screen (after the Asus logo), presenting some options to do recovery, reboot, factory reset, etc. (factory reset did not help), and red error messages at bottom.
To the GOOD news for anyone interested. I used the Asus Flash Tool and the firmware zip for 5.1.1 (many thanks for the advice).
Note: Tool did not install correctly on Win10 pc, citing error in installing some devcon.exe or similar file (guess that may be a firewall/antivirus issue).
Flash tool took some 15 or so mins unzipping firmware, after which I saw some action on the tab. Another 15 mins, and it rebooted to the At&t logo, stayed here for another 15 mins and unraveled a whole new device on Android 5.1
Glad to hear it worked for you and that I guess you can use this to flash upgrade from kitkat!
There is working way to root our device on lollipop! It is for the other Asus model, but it works for our
http://4pda.ru/forum/index.php?s=&showtopic=640814&view=findpost&p=53047686
I will check this out!
The root works, installed without any issues and verified with a root checker!
Here is a direct download from my Drive folder: https://drive.google.com/open?id=0B0fKccJIuWsnN21ZbnZpc2F6b1E
1. Download the file above.
2. Extract the zip contents.
3. Plug your ME375CL tablet in to pc via usb cable.
4. Make sure you have enabled Developer Mode and allowed USB Debugging first!
5. Open the folder you extracted and double click the "Root-One-Click.cmd" file.
6. It should reboot to fastboot mode and flash the needed files and then reboot again.
You should now have root access. Verify this by installing a root checker app from the play store. Keep in mind, it may say root not installed on the first run. Sometimes it will take a moment for superuser to initially run or prompt for access.
Side note: the root uninstall did not seem to work, got an error...but oh well, the point is to have root!
Thanks go to @little_pindos for finding this file...you are a rockstar!
Anyone get xposed on LP?
ATT Boot Up Sound
Tired of the ATT boot sound? If you used the rooting method above, then you can get rid of the annoying ATT startup sound by doing the following:
1. Install a Root Browser app (I recommend Rom Toolbox Pro, it has a built in file manager)
2. Navigate to the following path:
root/system/media
3. Find the file named "powerup.wav"
4. Simply rename the file by adding .bak to the end (ex - powerup.wav.bak)
5. Make sure it took the name change (some file managers have issues with that)
6. Reboot and see if it got rid of the sound!
You can also use your own startup sounds as long as they are in a .wav format, I believe. Make sure that the name of the file is powerup.wav.
You can also change your boot animation with "boot animation" app.
Best tweak IMO is adding "ro.config.low_ram=true" to build prop, or installing the low ram device xposed module if we can get it to work (both do the same thing). You gain about 100mb more free RAM on average.
TimmyP said:
You can also change your boot animation with "boot animation" app.
Best tweak IMO is adding "ro.config.low_ram=true" to build prop, or installing the low ram device xposed module if we can get it to work (both do the same thing). You gain about 100mb more free RAM on average.
Click to expand...
Click to collapse
I'll have to try that!
AT&T no longer has updates in system for this tablet
Gor- said:
Dear John,
Thank you very much for your help. My device runs KitKat 4.4, I can't upgrade over the air, as I damaged my sim slot struggling to remove a stuck nano sim, which I had inserted before I realized that it required a micro sim. (I'd wrongly assumed that by now the world uses only nano).
I followed the steps above, which you wrote so clearly for lay men, thank you a lot.
The flash for recovery.img and system.img worked fine (no red error messages on device).
The flash for boot.img had a red error message.
Might you have an idea or workaround on how I can address this?
If it refuses, is it possible to factory reset?
Thank you very much again for any words of advice and kind regards.
Click to expand...
Click to collapse
AT&T removed the last update for this tablet months ago and no longer supports it. ASUS states AT&T has all the updates. Total cluster.
Hello. Newbie here trying to install TWRP onto my G7+ (xt1965-T, moto not Revlry). I've been following the twrp.me instructions, among others. I've got the bootloader unlocked, adb & fastboot devices both return what they should, I've copied the twrp-3.5.0_9-0-lake IMG & ZIP files to my platform-tools folder and am running powershell from there. I copied the zip file to the internal memory of the phone as well as the ASC file with basic copy/paste commands in windows.
I temporarily boot the TWRP image and try to install the zip file, only to have it fail signature verification. I tried it without sig verification but still failed on some error. I've searched, but I haven't been able to find anything to get me past this.
Confusion comes with conflicting instructions. I see here that there is a method that differs from the instructions linked above, AFIAK.
There is a note on the bottom of the 1st instructions stating " If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest firmware for your device and reflash the boot image." I did ignorantly initially type the command fastboot flash recovery TWRPxxx.img. Would this have anything to do with my issues?
Are there multiple ways to achieve installation of TWRP & something like LineageOS and I'm just getting confused between instructions for each?
Thanks
I just tried to install the zip file without signature verification, and it failed to unpack the image
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/twrp-installer-3.5.0_9-0-lake.zip'
I've downloaded this a couple of times with the same result.
timsch75 said:
I just tried to install the zip file without signature verification, and it failed to unpack the image
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/twrp-installer-3.5.0_9-0-lake.zip'
I've downloaded this a couple of times with the same result.
Click to expand...
Click to collapse
Did you go in to TWRP Advanced and try to sideload TWRP ?
timsch75 said:
Hello. Newbie here trying to install TWRP onto my G7+ (xt1965-T, moto not Revlry). I've been following the twrp.me instructions, among others. I've got the bootloader unlocked, adb & fastboot devices both return what they should, I've copied the twrp-3.5.0_9-0-lake IMG & ZIP files to my platform-tools folder and am running powershell from there. I copied the zip file to the internal memory of the phone as well as the ASC file with basic copy/paste commands in windows.
I temporarily boot the TWRP image and try to install the zip file, only to have it fail signature verification. I tried it without sig verification but still failed on some error. I've searched, but I haven't been able to find anything to get me past this.
Confusion comes with conflicting instructions. I see here that there is a method that differs from the instructions linked above, AFIAK.
There is a note on the bottom of the 1st instructions stating " If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest firmware for your device and reflash the boot image." I did ignorantly initially type the command fastboot flash recovery TWRPxxx.img. Would this have anything to do with my issues?
Are there multiple ways to achieve installation of TWRP & something like LineageOS and I'm just getting confused between instructions for each?
Thanks
Click to expand...
Click to collapse
I fought this same model G7+ (XT1965-T) for several days, trying to install LineageOS for microG. Here are the instructions I used here ....I used the same recovery image (twrp-3.5.0_9-0-lake .img) as you. Download the copy-partitions-20200903_1329.zip from here. To sideload copy-partitions zip in TWRP go to Advanced tab, ADB sideload tab, then I sideloaded lineage-17.1-20210202-microG-lake.zip here.
chuck8812 said:
I fought this same model G7+ (XT1965-T) for several days, trying to install LineageOS for microG. Here are the instructions I used here ....I used the same recovery image (twrp-3.5.0_9-0-lake .img) as you. Download the copy-partitions-20200903_1329.zip from here. To sideload copy-partitions zip in TWRP go to Advanced tab, ADB sideload tab, then I sideloaded lineage-17.1-20210202-microG-lake.zip here.
Click to expand...
Click to collapse
I've regressed. I had previously been ably to temporarily boot into TWRP with the fastboot boot x.img command, at least in windows, but for some reason now it hangs up and will not show the TWRP screen. I had this same issue in Linux, but it worked in Windows, but now it fails the same in both. I run the command above and it shows the typical splash screen that it would if booting the stock android system, but goes no further. Previously, it would flash this , but then go to the TWRP screen. I can't get any feedback from adding the verbose flag to the fastboot command. Any way to track down this problem?
effin 'ell I hate regressions, 'specially the ones that come out of nowhere.
p.s. I don't know what happened with the previous blank post. I was trying to reply in Windows, but it wouldn't let me enter text. I rebooted into Linux for this post, and I see that something got posted previously. I'd delete it if I could.... gremlins
Before you start, make sure to put all of the files that you need in the same folder as your adb.exe and fastboot.exe because it will make things easier when you have to fastboot files to your phone. Make sure to follow the directions from the original developers of the tools below. Also, in the windows file explorer, right click on the "Name" tab, in the pop up click "More," select "Path," and also select "Folder Path," then click "Okay." This will make it easier to find the file path name if you need it when you are flashing a specific file to your phone using ADB.
Once you navigate to your android fastboot/adb folder, at the top of your file explorer, click in the address bar, this will highlight the text blue in the address bar, delete the text in the address bar, type CMD and then press enter. The adb/fastboot command window will pop up and be ready for you to use. You may as well leave that command window, the MSM tool, credits: Lucifer6: https://forum.xda-developers.com/t/msm-tool-guac-for-all.3934691/ and the Tool all in One, credits: mauronofrio: https://forum.xda-developers.com/t/...boot-roms-for-oneplus-7-pro-7-pro-5g.3931424/ , https://toolaio.tk/ open in case one of these tools decides to bite you in the brain so hard your phone melts into booting itself properly.
You'll be needing this Twrp.img from this post if you're on android 11 like I am, credits: Nebrassy:
https://forum.xda-developers.com/t/recovery-11-unofficial-teamwin-recovery-project.4289455/
And Magisk, credit: topjohnwu, which can be downloaded from Step 1 in this article https://www.xda-developers.com/how-to-install-magisk/
Credit: Sumukh for the article (code word the instructions in this article are for a different breed of TWRP then the one needed for rooting android 11 OnePlus 7 Pro, so please after booting into TWRP go to "Advanced," then in the list click "Flash Current TWRP," then reboot straight back to TWRP, flash Magisk, then reboot straight back to TWRP, then flash Magisk again, and then reboot the system ((if possible at this time)) or you'll have boot loops for breakfast), credits: topjohnwu for Magisk
And the android 11 stock rom of your oneplus 7 pro which can be found here, credit OPTeam: https://forum.xda-developers.com/t/...a-oxygen-os-repo-of-oxygen-os-builds.3930585/
I wasn't able to use MSM Tool by Lucifer6 because my phone didn't want to be recognized by my computer and I am not sure the files exist for android 11 to work with the MSM Tool, but if they do exist or there is a way to use the android 11 zip with the MSM Tool, please someone post it with detailed instructions so that everyone can find it.
I couldn't get the Tool All in One to work because I don't know, however, there are important files in mauronofrio's zip file in this post: https://forum.xda-developers.com/t/...boot-roms-for-oneplus-7-pro-7-pro-5g.3931424/ Grab the zip file from the link next to "All Roms on AFH." This can help get your phone back from the nightmare of the qualcomm crashdump scenario. If you are on android 11, do not flash the images in this zip folder because the zips in this post are for android 10 and I don't think you can downgrade. There are more directions about this in number 3 of this post.
If at any point you are able to boot your phone into the system, DO NOT put a password, fingerprints, facelock, swipe pattern, nudey collage on your phone to lock it up until AFTER you are sure you are completely done using TWRP, because Nebrassy's TWRP, as far as I know, is not supposed to be able to decrypt the phone once it has a nudey papier-mâché password on it. So, once you put a password on your phone, you may not be able to use TWRP again unless you like pain.
And yes, I did try, in the past week to clean install my rom, made sure to not create a password, flash TWRP and magisk, make a password for the phone, realized I needed to do something else in TWRP, deleted my papier-mâché password and the fingerprints to go along with and then try to get back into TWRP. It's really a hit or miss. You may get back in, you may end up flashing something only for it to get stuck in a TWRP booting boot loop like I did.
It's risky. Take off your password to your phone, then TWRP it up, say your goodbyes to TWRP and then finish setting up your phone with a password. Also, you may have to try plugging the OEM charging cable into different USB ports on your computer at specifically any time.
There are three different recipes that I tried to get my phone to work again after crash dumping. Any one of these could help. For me, it took doing all three, trial and error and error and error for my phone to get booted and rooted after the crash dump so you can try doing the easiest looking ones first, which are number 1 and number 2, see if that works, and then move on to the harder one.
Read all three recipes first before you try anything because some things from number two you can use in one or three. You're in for a real one right now so relax and get comfy. Take your time and make sure you follow the directions in the original posts by the developers because it will waste less of your time if you make sure you extract everything and other scientific ratchet. And you'll make less of a mess of your phone than it already is.
It's bricked, not dead. Hopefully. Hopefully, it's not dead. And I'm not much for hope nor am I much for being blamed if your phone slips into an endless hell pit, it contacts a plane's black box and directs said plane to land onto your roof, or some other maniacal nonsense backwater dribble okay let's get started.
1.) Easy: I used a combination of movements buttons including power off and volume down, only volume up and volume down which did other things, and power off and volume up. At first, none of these movements buttons would take me to fastboot mode. It would just keep rebooting to qualcomm crashdump mode no matter what.
Flustered, red, breathing hard because I don't walk enough, I tried these movements buttons again and again and again and again and not always in the order I wrote them down. I kept trying until I saw some Chinese writing.
Choose the first option even if you can't read the text. Guess where the "Okay" (bottom right) is and click it. The text--the first option--is highlighted in blue, which I should have said in the first place. Hopefully after twitching that phone for a good 30-45 minutes or more depending on how long you like crying, it will finally boot into fastboot mode. Plug the phone to the windows, fastboot boot the twrp.img from Nebrassy in the CMD window. If you are still trying to root, grab a usb or an external hard drive that has the rom zip and the latest magisk.apk that you need for your phone (directions below). If you are not trying to root, grab a usb or an external hard drive that has the rom zip and just flash the rom and that's it (directions below).
Plug the USB storage into your phone. On twrp go to "Mount," click the checkbox next to "USB Storage," click "Select Storage," then in the pop up click the circle next to your USB or external hard drive or whatever you're using. Go to "Install," select the zip of the rom on your USB Storage, click "Install."
You can then flash twrp afterwards by going back in the past and selecting to have TWRP flashed automatically after a rom installation; it's in the options. Or by going to "Advanced," then click "Flash Current TWRP" (mind you this is for the Oneplus 7 Pro using the TWRP 3.5.2_11-Nebrassy image in October of 2021, so if you're reading this and have a different phone or you're from the future, please, don't laugh at me if the current way of flashing TWRP is outdated by the time you read this).
Then you must flash magisk, reboot to TWRP recovery, and then flash magisk again or else the phone won't boot. After flashing magisk that second time, you may reboot the system. Once you get past those sussy terms and voluntary agreements, magisk will look like an android 1 icon. Click it.
The phone will ask you for your hand in marriage by asking if you are truly ready to jump off the deep end by allowing magisk to install unknown apps. Click I do, and magisk will install. Then, magisk will ask you to install the other half of itself, and again, make that app yo baby momma by saying yes, yes, yes. And now you have a new phone with none of your old life to spy on you and tell you how good you weren't in the past or whatever.
3.) Not so easy, but manageable. Caution, read slowly: Another thing I did try was to flash all of the images in the stock rom zip. You can download the correct rom for your phone in this post, credit OPTeam: https://forum.xda-developers.com/t/...a-oxygen-os-repo-of-oxygen-os-builds.3930585/ ,search the googles, or use the OEM website. Then, use the payload dumper method from here: credits to djsubterrain
https://forum.xda-developers.com/t/...ot-image-and-apply-root-to-the-phone.4263811/
After I djsubterrained my payload, all of this sounding unnecessarily dirty, I put it in this other thing that I tried (directions below): credits to mauronofrio
https://forum.xda-developers.com/t/...boot-roms-for-oneplus-7-pro-7-pro-5g.3931424/
I downloaded the zip file from the above post in the link next to "All roms on AFH." Extract it. Once I did the dump on my payload, I took all of the extracted images from the "payload_output" folder, put them in a new folder inside of mauronofrio's extracted zip folder, named that new folder "images," and just renamed the original "images" folder that was in the zip file to something else.
In mauronofrio's extracted zip folder, I copied the file named "flash-all-partitions-fastboot.bat" from the "Others_flashall" folder and pasted it into my new "images" folder. I double clicked on the "flash-all-partitions-fastboot.bat" file. An alluring window opened and I typed "Y" for yasss and then clicked "Enter."
And then that flashed most of the images to the phone. Not all of the images flashed. Some of them said "failed," but the important ones like the system.img and boot.img, among others, flashed successfully. I have no idea if using that specific ".bat" file was the right one for my situation because I wasn't sure if I was wearing comfy enough pants to be seen by the oracle.
After that, I did the the whole fastboot boot to TWRP and flashed the zip rom over again using my USB storage because it was easier for me to do that than to figure out how to adb sideload when the adb sideload button in TWRP wasn't working and while I was crash dumping for qualcomm, my phone refused to be recognized by the Tool All In One and the MSM Tool. Then I flashed TWRP, then I flashed magisk, rebooted to recovery, flashed magisk again, and then I tried to reboot to the system. But my phone booted back to twrp, a lot, a lot of times before the end of this story.
2.) Also easy: I think from TRWP (or you can use the power and volume buttons mantra from number one) I clicked on reboot the bootloader from fastboot mode. I used the up and down volume buttons to select "Bootloader" or "Start" (do both until the "Boot Reason" screen shows up for you).
For whatever reason I clicked "Boot Reason" and the reason was something made up like fs_mgr_mount_all. I clicked "Next" at the bottom of the screen and it asked me to wipe everything like music and photos which I already thought were long gone. But I have a backup of my music and my photos so no big deal.
I clicked on "wipe all data," and my phone finally booted back up into the OS. I went through the completely voluntary terms and conditions and voluntarily, completely voluntarily, and no one else is here with me, agreed to the voluntary terms and conditions. And then I clicked on the android 1 icon for magisk and...
At some point in time I formatted the system using TWRP after flashing the zips and the stuffs and now even though my phone says encrypted, the first time I booted back to twrp after finishing setting up my phone and putting a password on it, TWRP said that it decrypted USER 0 after putting my password into TWRP. I have no idea how it happened.
Nebrassy's TWRP is not supposed to be able to do that for android 11 as far as I know. About 30 mins later I booted back to TWRP just to see what would happen, and sure enough it took my password and decrypted my phone. Even though I am on android 11, rooted with a TWRP that is not supposed to be able to decrypt USER 0. I don't know how. Maybe I'll try to upload a log file so that can be figured out, or maybe by now it has already been figured out. Don't know.
So, that was fun, I hope you were able to get out of the crashdump by any of the means used here or not here. If you were able to get out of the qualcomm crashdump some other way or have advice on how any of the recipes could have been cooked better please post it in a forum or in this thread or sector B.92-80 of space so that no one ever comes close to using the very last tears their body has to offer.
I'm sorry if I forgot to give credit to anyone but at this point you'll have to flash me into recovery to get it. Or just say "I belong in here too," and post a link to your something helpful.