Related
Some of us used the flash-stock-then-flash-CWM method of installing the ICS leak, but were left without a working recovery. The method below allows you to unlock the bootloader and install a custom CWM.
This method may or may not work for you. I take NO CREDIT for making this happen, I'm just writing a quick howto. Thanks to strra for making it convenient.
Typically, attempting to boot into Recovery would generate an error that recovery image was not verified (something along those lines).
Thanks for all the devs who made this possible - you guys are amazing. Donate to them if you can, they deserve it.
I TAKE NO RESPONSIBILITY IF YOU TURN YOUR A500 INTO A PAPERWEIGHT.
If you don't feel comfortable with this possibility, stop here.
Install the A500 drivers from Acer on PC (from Acer's site).
Install and launch Android terminal app on tablet. Run the following command:
Code:
dmesg>/mnt/external_sd/dmesg.txt
Open up dmesg.txt and look for androidboot.serialno. That is your CPUID. In my case, the serial number reported by the OS, on the box, in the MicroSD slot was NOT my cpuid.
Use Vache's site to convert that number into your SBK (four long hex values).
Extract all of the required files (batch.rar and nvflash) from strra's post into c:\nvflash.
Open up a Windows command prompt (cmd.exe) and then `cd c:\nvflash`.
Launch `run.bat`, but don't enter your SBK yet.
Power down the tablet.
Use a paper clip and hold down the Reset button. Do not release it. Hold down power for 3 secs and then release it. After another second, remove the paper clip. Your Windows PC should then detect your device and install the APX driver. You should then have an APX USB device installed. If you do not have an APX USB device listed in your system tray, you cannot proceed.
Go back to the Windows command prompt and enter your SBK. Once you enter it, the process should begin. If you receive a USB write error, your SBK is incorrect.
Once the process begins, the Windows command prompt will read "Press any key when your A500 is in bootloader mode". Do not continue until the tablet is in Download Mode.
Once the tablet reads "download mode" (something along those lines), you are in bootloader mode. You can proceed and it will begin formatting the various partitions and installing the recovery.
Once the process completes, it should say PASS. You can then power off the tablet and power it back on again.
Make sure your tablet boots.
Power the tablet down and attempt to launch CWM via Power+VolDown.
PROTIP
Remount /system rw:
Code:
su
mount -o remount,rw -t ext4 /dev/block/mmcblk0p3 /system
Worked perfectly! Thanks!
yaw
worker for me too... thanks to all for this work!
good write-up
also, another protip:
if you right click the title bar of the command prompt, you can go to edit>paste to copy/paste the SBK... should make things a little easier
@strra:
You don't happen to know the location of the apk's for `Acer Media` and `Weather`, do you?
I'd like to add them to the following list of bloat that can go (another PROTIP) once you remount /system rw.
Under /system/app, rename:
3DPhotoBrowser-apk
AcerNidus-apk
Clearfi-apk
aupeo-apk
Problem with recovery
When it launches download mode, it says entering download mode in acer boot screen and it stays like that. How much time should I wait until it enters download mode? Or is that download mode? When it shows PASS message then under appears a red text saying LNX image not certified or something like that, why? Please help me. Thanks.
Now my tablet boots with a white text on it saying custom bootloader. But i don't have recovery mode.
Luescoff said:
Now my tablet boots with a white text on it saying custom bootloader. But i don't have recovery mode.
Click to expand...
Click to collapse
Install new recovery with fastboot. Boot into Android normally and connect it to PC with Android SDK (you need working adb and fastboot commands).
Check if adb sees your device:
Code:
adb devices
Boot into bootloader:
Code:
adb reboot bootloader
If you haven't been in bootloader mode before you might need to install fastboot drivers (from ACER Drivers for example).
Check if fastboot sees your device:
Code:
fastboot devices
My a500 didn't return its ID so fastboot is showing a device with "?" instead of ID. It is ok.
Install new recovery (here it is in recovery.img file, change it to yours):
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot reboot
When device will be booting just hold Volume Down like always to get into recovery.
You can also test and boot recovery.img directly from PC with fastboot:
Code:
fastboot boot recovery.img
You can test with fastboot boot command as it doesn't overwrite anything in device's flash. It downloads boot image (like recovery.img or boot.img into RAM and runs it from there).
jm77 said:
@strra:
You don't happen to know the location of the apk's for `Acer Media` and `Weather`, do you?
I'd like to add them to the following list of bloat that can go (another PROTIP) once you remount /system rw.
Under /system/app, rename:
3DPhotoBrowser-apk
AcerNidus-apk
Clearfi-apk
aupeo-apk
Click to expand...
Click to collapse
You can also add social Jogger
Link to facebook .
and all the links to there so called book shelf apps like link to games link to media .there are 4 of them They Hog resources even if you NEVER use them.I forget all there names and im on Vachs rom he has removed them all.
@jm77: Maybe could you split the DL link (batch.rar) and add the link to the OP of the orig. thread for downloading the bootloader binary (so when I update it people get the updated version directly)?
jm77 said:
@strra:
You don't happen to know the location of the apk's for `Acer Media` and `Weather`, do you?
.......
Click to expand...
Click to collapse
Acer hid them in flexrom/app this time around!
Thanks for the help.
yaworski said:
Install new recovery with fastboot. Boot into Android normally and connect it to PC with Android SDK (you need working adb and fastboot commands).
Check if adb sees your device:
Code:
adb devices
Boot into bootloader:
Code:
adb reboot bootloader
If you haven't been in bootloader mode before you might need to install fastboot drivers (from ACER Drivers for example).
Check if fastboot sees your device:
Code:
fastboot devices
My a500 didn't return its ID so fastboot is showing a device with "?" instead of ID. It is ok.
Install new recovery (here it is in recovery.img file, change it to yours):
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot reboot
When device will be booting just hold Volume Down like always to get into recovery.
You can also test and boot recovery.img directly from PC with fastboot:
Code:
fastboot boot recovery.img
You can test with fastboot boot command as it doesn't overwrite anything in device's flash. It downloads boot image (like recovery.img or boot.img into RAM and runs it from there).
Click to expand...
Click to collapse
Thank you, yaworski
For a mysterious reason the only way to boot in CWM recovery mode on my a500 is passing by your last command
Code:
fastboot boot recovery.img
The classical "volume-/power" method brings me to the "dead android man" with the exclamation mark... Same thing if I use the "Acer recovery" app.
In others words, the only way to open the recovery is passing by the bootloader and the fastboot commands...
Any idea for the reason of that?
So should the odmdata in the bat file be 0x300d8011 or 0xb00d8011. It has 0x300d8011, but i saw another post where it should match was EUU uses as 0xb00d8011.
Thanks.
castafiore said:
Thank you, yaworski
For a mysterious reason the only way to boot in CWM recovery mode on my a500 is passing by your last command
Code:
fastboot boot recovery.img
The classical "volume-/power" method brings me to the "dead android man" with the exclamation mark... Same thing if I use the "Acer recovery" app.
In others words, the only way to open the recovery is passing by the bootloader and the fastboot commands...
Any idea for the reason of that?
Click to expand...
Click to collapse
it's because you didn't delete recovery-from-boot.p from /system and it's reflashing stock recovery whenever you boot into android
I want to make a backup of my current EBT before I try flashing this new one. When I enter APX mode (reset button + power), I get "Acer Picasso USB Boot-recovery driver" listed in my device manager.
Then I issue the command (i blanked out most of my SBK here).
Code:
nvflash --read 4 myboot.img --sbk 0x8E000006 0x9C000001 0x22000002 0xF0000002 --sync
I've tried different flags like --bct --odmdate --configuration but i always get:
Code:
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
Following that, the device dissappears from my windows device manager.
I've also tried the first command from run.bat with both odmdata values
Code:
nvflash --bct bct.bct --setbct --bl bootloader.bin --configfile flash.cfg --odmdata 0xb00d8011 --sbk 0x8E000006 0x9C000001 0x22000002 0xF0000002 --sync
nvflash --bct bct.bct --setbct --bl bootloader.bin --configfile flash.cfg --odmdata 0x300d8011 --sbk 0x8E000006 0x9C000001 0x22000002 0xF0000002 --sync
Both of these give the error message same message.
Any ideas?
---------- Post added at 01:21 PM ---------- Previous post was at 01:11 PM ----------
Also, just tried the run.bat as is (well.. i removed the "cls" so the screen woudln't blank. Get the same error..
Code:
C:\Users\james\Downloads\bootloader>run
****************************************************************
* This will boot your A500 into bootloader mode, *
* flash patched bootloader V2, and flash Thor Recovery 1.7 *
****************************************************************
****************************************************************
* Before executing, be sure to delete recovery-from-boot.p *
* from /system to ensure recovery will stick *
****************************************************************
****************************************
* Reboot your tablet into APX mode *
****************************************
Generate your SBK with your CPUID from here : http://vache-android.com/v1/index.
php?site=sbk
Enter your SBK:0x8E000006 0x9C000001 0x22000002 0xF0000002
Loading bootloader...
Nvflash started
rcm version 0X4
[COLOR="Red"]Command send failed (usb write failed)
[/COLOR] **********************************************************
* Press any key when your A500 is in bootloader mode *
**********************************************************
Press any key to continue . . .
strra said:
it's because you didn't delete recovery-from-boot.p from /system and it's reflashing stock recovery whenever you boot into android
Click to expand...
Click to collapse
Thank you, strra.
I suspected it, to be honest, since I've noticed this advice when I launched the run.bat
But, my question has been/is still now: how to remove this "recovery-from-boot.p" ?
Can it be done when in APX mode? Do the adb commands work in APX mode?
castafiore said:
Thank you, strra.
I suspected it, to be honest, since I've noticed this advice when I launched the run.bat
But, my question has been/is still now: how to remove this "recovery-from-boot.p" ?
Can it be done when in APX mode? Do the adb commands work in APX mode?
Click to expand...
Click to collapse
While in Android you need to remount your /system partition as writable and just delete the file with rm command . If you didn't replaced your boot.img yet with patched one, just use
Code:
fastboot boot boot.img
command where boot.img is patched kernel, then wait until Android is started (it will run on patched kernel from ram like with recovery).
When you run on patched kernel and you use adb shell then you will have root from the beginning. Then just use
Code:
mount -o remount,rw /system
and you can remove the file.
Thanks for your quick and clear answer, yaworski
Booting on this patched boot.img is the trick.
fastboot boot recovery.img doesnt work for me, and i'm no able to mount rw to delete the recovery-from-boot.p. what can i do now??? i'm stuck in this leak version...
querobolo said:
fastboot boot recovery.img doesnt work for me, and i'm no able to mount rw to delete the recovery-from-boot.p. what can i do now??? i'm stuck in this leak version...
Click to expand...
Click to collapse
Did you flash the patched bootloader in APX mode using nvflash? Because all above instructions work only on unlocked and patched bootloader with "secure" flag off.
This document ALSO provides knowledge about android system work flow
The following Steps will help and resolve issues related with Zenfone 2 Series,
Do remember that most of the steps which are provided here are not automated, So have patience.
This guide will help you Recover Completely bricked mobiles - You are responsible for you own actions
We will try to do
1. adb and fastboot installtion
2. Unlock Bootloader
3. Custom Recovery Installation
4. Root Device
5. Unbrick (Asus Zenfone 2 ze551ml/ze550ml ONLY)
6. Recover lost IMEI's and Device Serial number( Of course the valid one Which is mentioned for your device ) (Asus Zenfone 2 ze551ml/ze550ml ONLY)
7. Recover serial number, mac, bluetooth address (Asus Zenfone 2 ze551ml/ze550ml ONLY)
____________________________________________________________________________________________
*************************** 1. adb and fastboot installtion ********************************
____________________________________________________________________________________________
used for Basic troubleshooting and updating android system
In windows just copy these four files into windows(c:/windows) folder or install it in windows folder
AdbWinApi.dll AdbWinUsbApi.dll adb.exe fastboot.exe
Download Link https://freeandroidroot.com/download-minimal-adb-and-fastboot-all-versions/
For Linux refer distribution guide
HIT THAT THANKS BUTTON IF IT HELPS
____________________________________________________________________________________________
********************************** 2. Unlock Bootloader ************************************
____________________________________________________________________________________________If you are on Android L(5.x) Asus provide boot loader unlock tool you can download it from asus.com
Doing so will make your device warranty void. or you can use custom bootloader unlock
if you are on Android M(6.x) Asus doesn't provide any tool to unlock for Android MM
You should use custom bootloader unlock you can follow the procedure provided by the unlock tool
FAQ
Can we relock device ?
YES
Why we need to unlock bootloader ?
Bootloader is a program which will allow your device to load Android OS
Why Bootloader is locked ?
To protect the devices from unauthorized access to third party. More of Business tactics
How to
Download the file from https://mega.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw!Ux9HlCzA zip file which corresponds to your Device
follow the instructions provided in the zip file
The successful of that unlocking process conclude that your device bootloader is unlocked, but its not ROOTed
HIT THAT THANKS BUTTON IF IT HELPS
____________________________________________________________________________________________
**************************** 3. Custom Recovery Installation *******************************
____________________________________________________________________________________________
There are majorly two custom recoveries used
* CWM - clock work MOD
* TWRP - Most flexible recovery mode ( more than just recovery)
you can download cwm from link (search google)
and TWRP from https://twrp.me/Devices/
once you downloaded the binary file from respected link provided
boot the device into fastboot mode
Follow Steps (only Asus Devices)
--------------------
* Turn off the mobile, Press and hold the volume UP button, Then press and hold the power button until device vibrates release only power button, once you see the ASUS logo release the Volume button
* fastboot devices - (in Computer prompt) wait till your device listed
* fastboot flash recovery filename(cwm.img or twrp.img) - it will take 20-50 Sec to complete
* press vol+ or Vol- until you see recovery mode on the screen and press power button
Once all the steps completed successfully you should be able to see the custom recovery screen
HIT THAT THANKS BUTTON IF IT HELPS
____________________________________________________________________________________________
************************************ 4. Root Device ****************************************
____________________________________________________________________________________________
Everyone who started using android device they all come across the word "ROOT" soon or later.
No wonder, whoever have root access to device can do wonders on android device. Root is nothing but having administrator privilege to make system wide changes, changes applied using root will applied without any question. no more, no less. whatever happens to device(system) you are your own, "SU" is nothing but "super user" and root is a super user which is from UNIX and Linux.
After unlocking android device bootloader, you need to patch su(binary file) command into android system which will allow you to run commands from adb shell prompt as root user.
There is no universal procedure to ROOT device, everything depends on the android device company, so based on manufacturing company you can google and get your device ROOTed
To root your Ze551ml/Ze550ml
Tools Required
---------------
Unlocked Bootloader Asus Zenfone 2(Ze551ml/Ze550ml)
SuperSU-2.78SR1-zf2_6.0.1.zip (Google search SuperSU-2.78SR1-zf2_6.0.1) download the zip file which has zf2 in filename or try https://www.yadi.sk/d/vVk0Qd-Ow7fdK
Custom Recovery (TWRP or CWM)
Steps to Root Device
---------------------
# copy SuperSU-2.78SR1-zf2_6.0.1.zip file into sdcard
# adb reboot recovery
OR
* Turn off the mobile, Press and hold the volume UP button, Then press and hold the power button until device vibrates release only power button, once you see the ASUS logo release the Volume button
* press vol+ or Vol- until you see recovery mode on the screen and press power button
# From TWRP main screen select install
# Browse and select SuperSU-2.78SR1-zf2_6.0.1.zip from sdcard
# select reboot
# adb shell
# su ( allow the permission from superSU app on mobile)
That concludes you are at root prompt (Device Rooted successfully)
HIT THAT THANKS BUTTON IF IT HELPS
____________________________________________________________________________________________
*************************************** 5. UNBRICK *****************************************
(Asus Zenfone 2 ze551ml/ze550ml ONLY)
____________________________________________________________________________________________
Cause
----------------
Custom or Wrongly flashed ROMS
Most of the time unlock bootloader and ROOTing device leads to bricked mobile
Symptoms of bicked Device
------------------------------
1. Black Screen - You can sense vibrations only, from the device when you press power button but nothing on the screen(Unless screen hardware faulty)
2. Vibrations - Device keeps on vibrating at same interval of time (usually every 5-10 mins loop)
Tools required
-------------------
- Xfstk windows application (google search "xfstk-downloader_v1.7.0")
- Intel Soc windows driver (google search "iSocUSB-Driver_v1.2.0")
- xFSTK_ZE551ML-sal358-amtech.vn.zip do (google serach "xFSTK_ZE551ML-sal358-amtech.vn" download the zip file which contains 3 bin files)
- Asus user UL-Z00A-xx-x.xx.xx.xxx-user.zip you can download this zip file from asus website (https://www.asus.com/in/Phone/ZenFone_2_ZE551ML/HelpDesk_Download/)
- partition.tbl (https://mega.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw!0483WIxB)
some files are located at https://mega.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw!0483WIxB
Remember the windows operating system will block some of the drivers from loading on windows 7, 8 or 10 just override that, install the driver first, Intel Soc windows driver after that install Xfstk windows application
How to Steps
--------------
* Open XFSTK Downloader, Click MRD tab A0 / B0 + A0 + CRC Tab, scanning shows Moorfield in device list.
* Click Options--> modify settings check Enable Override and change GP Flag overide value 0x800000807. Click OK.
* Change value of Device detection timeout to 120
* FW DNX should point to droidboot_dnx.img.POS_sign.bin (browse and locate)
* IFWI should point to ifwi.bin (browse and locate)
* OS DnX dont make any change to this field
* OS Image should point to droidboot_dnx.img.POS_sign.bin (browse and locate)
* Click Begin Download (Remember Once you see Scanning ....... device detected:1 which will be changing 0 to 1, couple of times wait till you see download sucessful before that mobile screen goes on and off let it continue for couple of minutes usually (2-5 mins) later you see 4 color strip on mobile screen and it enter into fastboot mode if you see that, your device is unbricked. if you dont see fastboot mode just turn off your mobile and try to enter into fastboot mode using volume up (press and hold) and power button(Press and hold release only power button when device vibrates)
* extract UL-Z00A-xx-x.xx.xx.xx-user.zip into a folder and copy partition.tbl into same folder open command prompt in that folder
* Run these commands one after another on every sucessful completion of command
fastboot oem erase_osip_header
fastboot oem erase_token
fastboot oem start_partitioning
fastboot flash /tmp/partition.tbl partition.tbl
fastboot oem partition /tmp/partition.tbl
fastboot erase system
fastboot erase cache
fastboot erase data
fastboot erase APD
fastboot erase ADF
fastboot oem wipe splashscreen
fastboot oem stop_partitioning
fastboot flash splashscreen splashscreen.img
fastboot flash token bom-token_ann_a0-mofd_v1-ze551ml.bin
fastboot flash dnx dnx_fwr_ann_a0-mofd_v1-ze551ml.bin
fastboot flash ifwi ifwi_ann_a0-mofd_v1-ze551ml.bin (Note This file is located in ifwi.zip)
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
* select Recovery mode using volume up or down key and press power button
* When you see android logo on the screen press and hold power button, press and release volume up key then release power button
* select sideload using voulme key and press power button
* on computer enter adb devices, should show connect device
* Run command adb sideload UL-Z00A-xx-x.xx.xx.xx-user.zip and enter, this command will take minimum 20-30mins to complete
if everything goes well your device is back to life, Congrats
HIT THAT THANKS BUTTON IF IT HELPS
____________________________________________________________________________________________
******************** 6. Recover lost IMEI's and Device Serial number **************************
(Asus Zenfone 2 ze551ml/ze550ml ONLY)
IT's ILLEGAL TO TAMPER IMEI RELATED INFORMATION AND IT IS PUNISHABLE OFFENCE
THIS IS JUST AN OVERVIEW AND
FOR KNOWLEDGE PURPOSE ONLY____________________________________________________________________________________________Its mobile user's NIGHTMARE when they see Wrong IMEI and serial number
Cause
---------------------------
Custom or Wrongly flashed ROMS
Symptoms of Wrong IMEI and Serial Number
-------------------------------------------
Unable to connect to network even though mobile boots properly and works normally
How to Check
---------------
When you run adb devices from your pc its shows device serial number
IMEI can be checked in Settings --> About --> Status --> IMEI information OR
Call Dialer enter *#*#4636#*#* and select Device Information
Tools required
-----------------
Digma_SoFia_IMEI_recovery.rar (Google search "Digma_SoFia_IMEI_recovery file contains contains Digma software and windows driver)
IntelAndroidDrvSetup1.10.0.exe (Google search "IntelAndroidDrvSetup1.10.0") IntelAndroidDrvSetup1.10.0.exe
Rooted Device
links
Digma - https://yadi.sk/d/30q9w4KJjvgHd
IntelAndroidDrvsetup - https://mega.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw!0483WIxB
Steps :
* To identify the com port turn on your device and run command adb shell(from computer command prompt)
* Run su
* your device should be rooted so it will give su prompt(#)
* Run setenforce 0
* Run setprop system.at-proxy.mode 1
* Install IntelAndroidDrvsetup and intel mobil family imc1 driver which is included in Digma software ( This is the hard part to setup as windows driver installation restrictions and identifying com ports on usb interface make sure these software and driver installed properly)
* after successful installation of driver and Phonetool run Phonetool
* settings --> Phonetool check RTS and DTR on select your phone com port listed in port list click ok
* click on update info (Should say success connecting to port)
* Click modes --> security click on show advanced options
* Click unlock
* Click on personalization programming tab
* scroll down and click add button
* add your mobile phone imei number (only first 14 digits) again add one time if you mobile is dual sim phone
* Click Execute (will take upto 60 sec)
* if above all steps completed without any error, just reboot your phone and check your imei number should show your real imei numbers
Note some times you needs to flash imei number after setting setprop system.at-proxy.mode 3 to flash 2 imei number just try until both imei show correctly on you mobile check your imei number by dialing *#*#4636#*#*
HIT THAT THANKS BUTTON IF IT HELPS
____________________________________________________________________________________________
**************** 7. Recover serial number, mac, Bluetooth address **************************
____________________________________________________________________________________________
Refer https://forum.xda-developers.com/showpost.php?p=66877096&postcount=28 Thanks to BORETS24
Thanks, helped a lot.
Unsure of what happened to my phone
Hey, I was trying to root my zenfone 2 ZE551ml by following a youtube video. It asked me to first put superSu.zip inside the SD Card which I did. Next - unlock the bootloader of my phone by downloading an zip which has an unlocker.bat file. Then it asked me to flash TWRP recovery using fastboot which I also did and then to boot into twrp and install the supersu.zip. I did everything but the last step, as when i tried to boot into the recovery to use twrp, the phone restarted, came to the white asus screen, stayed there for a very long time and then went back into the bootloader.
At this point I got frustrated and thought of reinstalling everything. So I downloaded the zip file for the latest firmware, flashed recover, boot and droid boot and then when I restarted the phone to go into the recovery, the white asus screen just keeps on repeating itself. The device keeps on shutting down and then restarting but never goes past the white asus logo screen where it says "powered by android", doesn't even let me get into fastboot.
I am new to all this and any help from anyone is highly appreciated. Thanks
error loading partition.tbl? edit: now im stuck on "cannot load fastboot flash token bom-token_ann_a0-mofd_v1-ze551ml.bin "
after doing these steps
fastboot oem erase_osip_header
fastboot oem erase_token
fastboot oem start_partitioning
fastboot flash /tmp/partition.tbl partition.tbl
fastboot oem partition /tmp/partition.tbl
fastboot erase system
fastboot erase cache
fastboot erase data
fastboot erase APD
fastboot erase ADF
fastboot oem wipe splashscreen
fastboot oem stop_partitioning
fastboot flash splashscreen splashscreen.img
fastboot flash token bom-token_ann_a0-mofd_v1-ze551ml.bin
fastboot flash dnx dnx_fwr_ann_a0-mofd_v1-ze551ml.bin
fastboot flash ifwi ifwi_ann_a0-mofd_v1-ze551ml.bin (Note This file is located in ifwi.zip)
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
when i reboot and select recovery i cant load recovery , it opens bootloader
how to install recovery
Hi, good day.
I am having 0 response when I hit this command. setprop system.at-proxy.mode (number) Do you know why ?
Device is rooted, since I've unlocked the bootloader using the ASUS app.
Fastboot erase config....
After that I stucked at boot logo
Used xfstk then aft but stucked at boot used fastboot commands for flashing system all gonna smooth but stucked at boot...
Used recovery to sideload marshmallow ... succeed. But also stucked at boot ..unlock boot loader flash TWRP flashing custom rom also stucked at boot logo... PLZZ help me guyzzz
And it shows error in TWRP
Unable:to mount Config(invalid argument)
I'm on step, Run setenforce 0, but it returns an error message, "Couldn't set enforcing status to '0': Permission denied". Please advise. Thank you in advance!
Hi,
i tried to update my phone via the integrated updater. It did not start the update and now fails booting into android. it boots every time into twrp.
i tried several possible solutions:
reflash other version
reflash the latest version
flashed fulmics
factory wipe
reflashed twrp
tried to
inshadesofgrey said:
If you get into a recovery boot loop (where the phone keeps booting into the recovery, and not the OS), this will fix it without losing any data. (NO FACTORY RESET NEEDED)
Go to TWRP recovery terminal commands, and enter the following:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
PRESS ENTER
THEN TYPE
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
THEN PRESS ENTER
REBOOT
This should boot up your phone without any changes.
Click to expand...
Click to collapse
but failed
now i am out of knowledge...
has anyone an idea?
Regards!
Christian
did you tried to restore everything to stock with a kdz file? you can find it on google and you can flash it putting the device in download mode and using lgUP / uppercut to do so.. if you need help you can send me a PM
one_ctrl said:
did you tried to restore everything to stock with a kdz file? you can find it on google and you can flash it putting the device in download mode and using lgUP / uppercut to do so.. if you need help you can send me a PM
Click to expand...
Click to collapse
Is there any better solution for this problem?
I solved it once with a full reinstall an this uppercut tool.
On reddit for other phones there is the solution to boot to bootloader and do
Code:
fastboot continue
resuming boot...
FAILED (remote: unknown command)
finished. total time: 0.001s
But this does not work.
It seems my phone boots to twrp because the lineage os updater app set s.th. to automatically boot to twrp. How can we remove this auto-boot to twrp flag?
Sorry for bringing up this again. I did an OTA update on lineageos on my lg g6. The phone booted correctly in twrp, I installed the update but now the phone boots directly to twrp without any way to let it boot the os. How did you resolve this?
Thanks
Only solution back to stock & after install LOS and wait until bug is fixed.
I use a lg g pad x 8.0 and ran into the same issue.
fastboot continue would not work.
the dd commands did not work either
I think the "msm_sdcc.1" is device specific.
In recovery, I used the file manager to look in /dev/block/platform and notice that "msm_sdcc.1" did not exist but there was one folder in there. I went in there and there was another and kept going til I found the "by-name" folder
then I ran the dd command replacing "msm_sdcc.1" with what was on my device.
I did it for "fota" and "misc" and then my device booted
Someone else has had this problem @gnackwatschn, you can find a way to fix the boot loop here https://forum.xda-developers.com/lg-g6/help/twrp-bootloop-lineageos-ota-update-t3746014/post75488796#post75488796
WARNING [brick]
eng3 said:
I use a lg g pad x 8.0 and ran into the same issue.
fastboot continue would not work.
the dd commands did not work either
I think the "msm_sdcc.1" is device specific.
In recovery, I used the file manager to look in /dev/block/platform and notice that "msm_sdcc.1" did not exist but there was one folder in there. I went in there and there was another and kept going til I found the "by-name" folder
then I ran the dd command replacing "msm_sdcc.1" with what was on my device.
I did it for "fota" and "misc" and then my device booted
Click to expand...
Click to collapse
WARNING! I ran into the same problem on the LG G6 with the nightly update dated Nov 1, 2018. Did what you did, but wrote down the command.
After navigating to the TWRP > Advanced > Terminal, first do
Code:
ls /dev/block/platform
Mine had one entrie: soc, which had two entries: 624000.ufshc and 74a4900.sdhci
only 624000.ufshc had a by-name directory containing fota and misc, so my commands ended up being:
Code:
dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/fota
dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/misc
The commands run, saying:
Code:
dd: writing '/dev/block/platform/soc/624000.ufshc/by-name/fota': No space left on device
8193+0 records in
8193+0 records out
4194304 bytes (4.0MB) copied), 2.783000 seconds, 11.5MBs
and similar for misc.
Reboot to system gives a warning, Your device has failed a routine safety check and will not boot.
Now I'm stuck.... guess its time to start another thread.
It's seems like Nvidia released the developers image for the shield 2019 pro. There is no description at links only some dots see images.
Shield Android TV SW Version: 8.1.0 (32.7.301.32)
Android Paches: 5 oct 2019
https://developer.nvidia.com/search/site/Shield 2019
NVIDIA SHIELD ANDROID TV 2019 Pro Developer Only OS Image
https://developer.nvidia.com/nvidia-shield-android-tv-pro-developer-only-os-image
Filename: nv-recovery-image-shield-atv-pro-2019-8.1.0-dev-rooted.zip
NVIDIA SHIELD ANDROID TV 2019 Pro Recovery OS Image
https://developer.nvidia.com/nvidia-shield-android-tv-pro-recovery-os-image
Filename: nv-recovery-image-shield-atv-pro-2019-8.1.0.zip
I have downloaded them let see what happens, i'm not responsible if you brick your device.
Both recovery images are working on the Shield 2019 PRO and I was able to fully flash my shield and got things running again.
Image files contains a flash-all file and all the images to recover you device
fastboot oem unlock
:: Confirm the prompt on the screen
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash dtb mdarcy.dtb.img
fastboot flash vbmeta vbmeta.img
fastboot oem lock
:: Confirm the prompt on the screen
The developer version contains 1 extra file called vbmeta_skipped.img.
NOTE: After unlocking your bootloader you will lose Dolby Vision, after locking you bootloader you will get back Dolby Vision
See also https://forum.xda-developers.com/showpost.php?p=81200005&postcount=380
Below are the steps we used to root our Nvidia Shield 2019 PRO, if you are new to rooting devices you better can wait until their are less steps.
For some reason this post doesn't show correctly in the XDA app.
UPDATE: it's possible to use the official release of Magisk.
PreRequisites:
Download: Experimental TWRP is from https://forum.xda-developers.com/showpost.php?p=80769929&postcount=312
Download: Magisk official release https://github.com/topjohnwu/Magisk/releases/tag/v20.4
Download: Filename: nv-recovery-image-shield-atv-pro-2019-8.1.0-dev-rooted.zip (see above post)
Download: Filename: nv-recovery-image-shield-atv-pro-2019-8.1.0.zip (see above post)
Working ADB/Fastboot.
Coffee and a bit of luck.
Enable Developers options/Enable USB Debugging/Authorize device.
Step 1
Reboot to bootloader to start fresh...(you will need a keyboard)
Use files from filename: nv-recovery-image-shield-atv-pro-2019-8.1.0.zip
Use vbmeta_skipped.img from filename:
nv-recovery-image-shield-atv-pro-2019-8.1.0-dev-rooted.zip
a) fastboot oem unlock and confirm by pressing A
b) fastboot flash staging blob
c) fastboot flash boot boot.img
d) fastboot flash recovery recovery.img
e) fastboot flash system system.img
f) fastboot flash vendor vendor.img
g) fastboot flash dtb mdarcy.dtb.img
h) fastboot flash vbmeta vbmeta_skip.img
I) fastboot -w
j) fastboot reboot bootloader
Step 2
Now we will boot to twrp and install magisk...
a) fastboot boot twrp.img (you will need a mouse for this)
b) select mount and mount everything it lets you (usually data, system_root, vendor, cache)
c) adb remount all
d) adb shell
e) rm /system (removes symlinked folder)
f) mkdir /system
g) mount -o bind /system_root/system /system
h) exit
i) adb push Magisk-v20.4.zip /data/media
j) In twrp press install and navigate to magisk zip and flash it
k) adb reboot bootloader
l) fastboot -w
m) fastboot reboot bootloader
n) fastboot flash dtb mdarcy.dtb.img
o) fastboot flash vbmeta vbmeta_skip.img
p) fastboot reboot
q) let it reboot a couple of times, after Nvidia blinks and then reboots).
Optional
r) If Shield doesn't go passed the Nvidia logo.
s) start shield with A+B pressed to get in fastboot
t) in fastboot menu select reset factory default.
u) fastboot flash dtb mdarcy.dtb.img
v) fastboot flash vbmeta vbmeta_skip.img
w) fastboot reboot
x) let it reboot a couple of time
Step 3
Device eventually loads.. when it does follow these steps
a) Enable usb debugging
b) make sure its authorized and connected
c) adb install -g magisk.apk
d) adb shell
e) su (grant root to shell when it pops up)
f) mount -o rw,remount /
g) Go to apps (trough settings), show all apps, start/open magisk manager
h) When it pops up telling you it needs to install stuff select ok and install it.. device will reboot in 5 seconds...
Step 4
When device tries to boot you should now be stuck at the android boot ani (NOT the nvidia logo).. then follow these steps..
a) adb shell
b) su
c) resetprop ro.boot.verifiedbootstate orange
d) after device boots run: resetprop ro.boot.verifiedbootstate green
Step 5
If you have registerd for the hotfix (32.7.301.43) then you can start the upgrade now. The device will reboot and starts the upgrade, after that you lost root again.
a) adb reboot bootloader
b) fastboot boot twrp.img (you will need a mouse for this)
c) select mount and mount everything it lets you (usually data, system_root, vendor, cache)
d) adb remount all
e) adb shell
f) rm /system (removes symlinked folder)
g) mkdir /system
h) mount -o bind /system_root/system /system
i) exit
j) adb push Magisk-v20.4.zip /data/media
k) In twrp press install and navigate to magisk zip and flash it
l) adb reboot bootloader
m) fastboot flash dtb mdarcy.dtb.img
n) fastboot flash vbmeta vbmeta_skip.img
o) fastboot reboot
p) When device tries to boot you should now be stuck at the android boot ani (NOT the nvidia logo).. then follow these steps..
q) adb shell
r) su
s) resetprop ro.boot.verifiedbootstate orange
t) after device boots run: resetprop ro.boot.verifiedbootstate green
After every reboot
When device tries to boot you should now be stuck at the android boot ani (NOT the nvidia logo).. then follow these steps..
a) adb shell
b) su
c) resetprop ro.boot.verifiedbootstate orange
d) after device boots run: resetprop ro.boot.verifiedbootstate green
Stuck at Nvidia Logo
a) Power off Shield, remove power cable
b) Press & Hold A+B on keyboard or controller.
c) Plugin power cable will holding keys.
d) You will see the fastboot menu.
Restore Stock
Use files from Filename: nv-recovery-image-shield-atv-pro-2019-8.1.0.zip
a) Power off Shield, remove power cable
b) Press & Hold A+B on keyboard or controller.
c) Plugin power cable will holding keys.
d) You will see the fastboot menu.
e) fastboot flash staging blob
f) fastboot flash boot boot.img
g) fastboot flash recovery recovery.img
h) fastboot flash system system.img
i) fastboot flash vendor vendor.img
j) fastboot flash dtb mdarcy.dtb.img
k) fastboot flash vbmeta vbmeta.img
l) fastboot -w
m) fastboot reboot bootloader
n) fastboot oem lock and confirm by pressing A
Like I mentioned before, only use this when you know what your are doing. I'm not responsible for any brick devices.
All the credits are for @elliwigy and @rootfan
reserved
Hello and thank you for sharing this.
I'm looking for the fastboot drivers (the 2017 don't works with the pro 2019), I have contacted Nvidia by chat and he doesn't found too.
Can you please tell me where I can download them ?
And sorry for my poor english I'm french.
EDIT :
Ok I have resolved the problem, I have manually installed the .inf.
Regards.
After every reboot
When device tries to boot you should now be stuck at the android boot ani (NOT the nvidia logo).. then follow these steps..
a) adb shell
b) su
c) resetprop ro.boot.verifiedbootstate orange
d) after device boots run: resetprop ro.boot.verifiedbootstate green
Click to expand...
Click to collapse
I don't understand, does this mean we have to do these steps every time the shield reboot ?
lycaos said:
Hello and thank you for sharing this.
I'm looking for the fastboot drivers (the 2017 don't works with the pro 2019), I have contacted Nvidia by chat and he doesn't found too.
Can you please tell me where I can download them ?
And sorry for my poor english I'm french.
EDIT :
Ok I have resolved the problem, I have manually installed the .inf.
Regards.
Click to expand...
Click to collapse
Hi,lycaoslease tell me how to edit the .inf,thanks a lot!
marokino95 said:
I don't understand, does this mean we have to do these steps every time the shield reboot ?
Click to expand...
Click to collapse
Yes every time you reboot you will have to do this. I have connected a Raspberry to the shield which makes it easier.
song4 said:
Hi,lycaoslease tell me how to edit the .inf,thanks a lot!
Click to expand...
Click to collapse
Hello.
It's not easy for me to explain in english, I have Windows in french. But simply go to "device manager" or something like that, select update fastboot, select choose manually, and select again the option to choose manually the driver. Select the .inf and choose boooader driver (it is really simple but like I've said It's not easy for me to explain in english, just don't select the option to search automatically the driver in folder/sub folders, select the other option).
Ok so, I have a big problem when I boot twrp.img : My mouses are not recognized (I have tried 4 wired mouses and bought one very basic old mouse. All the mouses are detected in normal or fastboot mode but 0 device are detected except the computer (I can send adb commands in twrp mode, it's all I can do).
I have also tried a lot of wired controller...
If someone have a solution to use twrp...
(All that things just for modify the Vendor_045e_Product_028e.kl to change A to B and Y to X to use my switch controller pro connected to the 8bitdo recognized as xbox 360 controller >< because natively the switch have pads issues and button mapper have a big latence and don't works in nvidia gamestream !!).
Have a good week-end guys, french kisses :silly:
lycaos said:
Hello.
It's not easy for me to explain in english, I have Windows in french. But simply go to "device manager" or something like that, select update fastboot, select choose manually, and select again the option to choose manually the driver. Select the .inf and choose boooader driver (it is really simple but like I've said It's not easy for me to explain in english, just don't select the option to search automatically the driver in folder/sub folders, select the other option).
Ok so, I have a big problem when I boot twrp.img : My mouses are not recognized (I have tried 4 wired mouses and bought one very basic old mouse. All the mouses are detected in normal or fastboot mode but 0 device are detected except the computer (I can send adb commands in twrp mode, it's all I can do).
I have also tried a lot of wired controller...
If someone have a solution to use twrp...
(All that things just for modify the Vendor_045e_Product_028e.kl to change A to B and Y to X to use my switch controller pro connected to the 8bitdo recognized as xbox 360 controller >< because natively the switch have pads issues and button mapper have a big latence and don't works in nvidia gamestream !!).
Have a good week-end guys, french kisses :silly:
Click to expand...
Click to collapse
Dear lycaos,Thank you for your kindness to help me.Wish you have a good weekend.
Thanks
hi, I am trying to root my Shield 2019 Pro. However I am stuck at installing Fastboot drivers for Windows 10. I only found the Windows drivers for older Shield models. And they don't work. How can I make these work? Thanks a lot!
Well, some of you know this because you have successfully rooted the Shield Pro 2019.
How do I install Fastboot drivers on Windows 10?
thanks for absolutely no help.
Rey3000 said:
thanks for absolutely no help.
Click to expand...
Click to collapse
That's a interesting reply, I also have a busy job and a family. And the same goes for other people on xda.
I'm using Linux and I don't have a problem with the drivers. But you can use the drivers on the Nvidia site.
https://developer.nvidia.com/gameworksdownload#?search=SHIELD Family Windows USB
If that doesn't work you could maybe try
https://xdaflash.com/download-universal-adb-driver-installer-windows
Rey3000 said:
thanks for absolutely no help.
Click to expand...
Click to collapse
Maybe read all post next time ? Lycaos had the same problem you have and he explained how he resolved it on the first page, i had it too and resolved it by following what he said.
powercommy said:
Below are the steps we used to root our Nvidia Shield 2019 PRO, if you are new to rooting devices you better can wait until their are less steps.
Click to expand...
Click to collapse
While I'm generally familiar with Android, I'm new to rooting devices. Where is the best place to keep tabs on progress? Also, out of curiosity, how long does it usually take "until there are fewer steps"?
Exosq said:
Maybe read all post next time ? Lycaos had the same problem you have and he explained how he resolved it on the first page, i had it too and resolved it by following what he said.
Click to expand...
Click to collapse
Of course I tried. Doesn't work. Windows 10. Tried all USB ports. Hence my plea. - how dare I ask for help??
---------- Post added at 08:12 PM ---------- Previous post was at 08:10 PM ----------
besides ... he didn't mention what drivers he used. I OBVIOUSLY tried the latest ones from Nvidia - 2018. They do NOT work ffs.
Rey3000 said:
Of course I tried. Doesn't work. Windows 10. Tried all USB ports. Hence my plea. - how dare I ask for help??
---------- Post added at 08:12 PM ---------- Previous post was at 08:10 PM ----------
besides ... he didn't mention what drivers he used. I OBVIOUSLY tried the latest ones from Nvidia - 2018. They do NOT work ffs.
Click to expand...
Click to collapse
Maybe you should try a different approach with users of XDA and tone down your attitude a little bit. I have no interest in helping you out this way. Maybe other xda-ers will.
powercommy said:
Maybe you should try a different approach with users of XDA and tone down your attitude a little bit. I have no interest in helping you out this way. Maybe other xda-ers will.
Click to expand...
Click to collapse
In case you haven't noticed ... you DIDN'T help me.
mgmcd said:
While I'm generally familiar with Android, I'm new to rooting devices. Where is the best place to keep tabs on progress? Also, out of curiosity, how long does it usually take "until there are fewer steps"?
Click to expand...
Click to collapse
It really depends on how many users are using their Nvidia 2019 Pro before things gets easier. Their is not much differents between rooting your phone/tablet. As long as you follow the the steps you should be okay. It's very difficult to brick your device.
You could also monitor this thread @elliwigy is a user to watch.
https://forum.xda-developers.com/sh...-twrp-shield-android-tv-t3510456/post81811131
Bricked phone doing factory upgrade to B04. Stuck in EDL mode, but wont connect
Device manager shows QUSB_BULK but no tool will see the phone. Any ideas guys.
I have installed quailcom drivers etc , no difference
You can try this tool:
https://forum.xda-developers.com/axon-7/how-to/salesmultidla2017-tool-to-unblick-dfu-t3854229
Hi , I did try that. The port manager in the app does not show anything. It as if the phone is not connected. Even though it is listed in windows device manager as QUSB_BULK
Wait until batterry fully discharged, try enter edl mode again and flash using edl tool or miflash
the_hoho said:
Wait until batterry fully discharged, try enter edl mode again and flash using edl tool or miflash
Click to expand...
Click to collapse
Hi,
I waited till the battery discharged. Went into EDL mode. They only success I had is with axon7tool.exe
Miflash will not detect the phone. As seen believe I can read and write with axon7tool.exe
Is there any recovery I can put back on the phone that will run? The bootloader is unlocked. Thanks
H:\TRWP AXON 7>axon7tool -r recovery
Connecting to device...
Sending programmer...
Connecting to programmer...
log: Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke getnumdisksectors
log: Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke getnumdisksectors
Reading recovery ...
Success!
Reset in 5 seconds ...
Reset in 4 seconds ...
Reset in 3 seconds ...
Reset in 2 seconds ...
Reset in 1 seconds ...
> H:\TRWP AXON 7>axon7tool -r recovery
Your command with option "-r" (for read) only backuped the existing recovery to your PC.
There was no effect on the phone. It read your phone recovery and downloaded (=backuped) to your PC (probably with name recovery-backup.bin).
Since your booloader is unlocked, you can write official but unsigned TWRP recovery to the phone. This official but unsigned TWRP recovery
will run correctly (since bootloader is unlocked). So you need to 1) download latest official TWRP recovery, then 2) write it to the phone.
1)
On your PC:
Go to https://eu.dl.twrp.me/ailsa_ii/
Download the recovery twrp-3.3.1-0-ailsa_ii.img (14 897 152 bytes, md5 0d57b791c6b7c7d979ea70b0951c519d) with the link:
https://eu.dl.twrp.me/ailsa_ii/twrp-3.3.1-0-ailsa_ii.img.html
Copy the file to the directory containing your axon7tool.exe ("H:\TRWP AXON 7").
Then copy twrp-3.3.1-0-ailsa_ii.img to recovery.bin (command: "copy twrp-3.3.1-0-ailsa_ii.img recovery.bin")
(this means you have a new recovery.bin file which is exactly the same as twrp-3.3.1-0-ailsa_ii.img file).
Explanation: this to prepare to write TWRP recovery to the phone, the axon7tool.exe syntax "-w recovery" requires a file named recovery.bin
which has the content of the recovery you want to put (in your case, latest official TWRP recovery twrp-3.3.1-0-ailsa_ii.img).
On your PC, go to H:\TRWP AXON 7 directory:
H:\TRWP AXON 7>
type "dir" command, you should have files: axon7tool.exe, recovery.bin (identical to twrp-3.3.1-0-ailsa_ii.img), twrp-3.3.1-0-ailsa_ii.img and other files.
2)
Put you phone in EDL mode as you did before.
On your PC, type the following command to write TWRP recovery to the phone:
axon7tool -w recovery
(Explanation: the above command will write (-w) the recovery to the phone using the file named recovery.bin (= twrp_rec_tenfar.img) found in your PC.
You can then boot to recovery, using menu in bootloader at start (use Vol-Up, Vol-Down for selection, Power to Confirm selection).
Other way: if phone is power off: Vol-Up + Power to get into TWRP recovery.
Afterwards, with TWRP you have total control on the phone, custom ROM etc...