Hey Everyone,
So I have an Asus ZenPad C 7.0 Z170C and I was working on rooting the device. Long story short, I messed up and now I have a brick... or paper weight. I can at least use a paper weight for something....
Here is what my devices does currently:
When I try to boot the device, it gets stuck at the 2ND Asus screen and never actually boots up. I can get my device into fastboot (the GREEN background).
I can also get the device into RECOVERY mode by pressing (POWER + VOLUME DOWN) when booting the device.
However, I can only get the device to the screen with the DEAD ANDROID and "No Command" text screen. If I try getting the BOOTLOADER list to pop up, from the DEAD ANDROID screen, by pressing POWER + VOLUME UP, I get an error. The error is different depending on whether I have my EXTERNAL SD card in my device.
The error messages say the following:
EXTERNAL SD Card LEFT IN Device:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://forum.xda-developers.com/picture.php?albumid=13045&pictureid=52347
"
E: failed to mount /cache (invalid argument)
E: can't mount /cache/recovery/last_locale
"
----------------------------------------------------------------------
EXTERNAL SD Card Taken OUT of the Device:
http://forum.xda-developers.com/picture.php?albumid=13045&pictureid=52348
"
E: failed to mount /sdcard (No such file or directory
E: Can't mount /sdcard/P01Z_SDUPDATE.zip
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/lastlocale
"
Ive been searching and searching endlessly online all day and couldnt find anything that works. The closest I got was with the following:
Asus Flash Tool: Seems to work fine at first but then hangs. The "Unzip Image" step finishes and then it says "Rune Flash Image Script..." and does nothing. I let it run for over 1 hour and nothing changed.
Please let me know if there is anything else I can try. I do NOT care if my data is lost.
Thank you in advance!!
If you can get in the bootloader (POWER + VOLUME UP) and the device can be seen in the list on fastboot devices, then it should be easy to restore.
yes, I can do both.. whats your recommendation to restore?
InvisiBot said:
If you can get in the bootloader (POWER + VOLUME UP) and the device can be seen in the list on fastboot devices, then it should be easy to restore.
Click to expand...
Click to collapse
Message "can't mount /sdcard" it means low quality SD card, take another and use the fat32.
Take the online ASUS update UL-P01Z-WW-12.26.4.45-user.zip and put the zip file on SD card.
After fastboot (POWER + VOLUME UP) do a hard reset:
Code:
fastboot format cache
fastboot format userdata
After that boot to recovery (POWER + VOLUME DOWN) and choose apply update from sd card.
It is not necessary to use the SD card. You can select in the menu apply update from ADB and specify the path to the file on your computer through ADB:
Code:
adb sideload "C:\adb\[B]UL-P01Z-WW-12.26.4.45-user.zip[/B]"
If the recovery menu does not appear, press any button once.
If you have a problem with recovery partition, do a hard reset (fastboot format ...), and then flash attached files (it is important to observe the sequence):
Code:
fastboot flash vrl "C:\adb\extracted_UL-P01Z-WW-12.26.4.45-user\vrl.bin"
fastboot flash recovery "C:\adb\extracted_UL-P01Z-WW-12.26.4.45-user\recovery.bin"
If errors appear on the command line, you may need to unlock the bootloader:
Code:
fastboot oem unlock
fastboot oem unlock confirm
or:
Code:
fastboot oem asus-go
fastboot oem asus-go confirm
The files vrl.bin and recovery.bin were obtained using the following instructions: https://forum.xda-developers.com/an...uimage-bin-t3191929/post72093244#post72093244
5.0.1
Excellent. Sounds simple enough... I will try this out when I get some time. Thanks you for your help!
Much Appreciated!
InvisiBot said:
Message "can't mount /sdcard" it means low quality SD card, take another and use the fat32.
Take the online ASUS update UL-P01Z-WW-12.26.4.45-user.zip and put the zip file on SD card.
After fastboot (POWER + VOLUME UP) do a hard reset:
Code:
fastboot format cache
fastboot format userdata
After that boot to recovery (POWER + VOLUME DOWN) and choose apply update from sd card.
It is not necessary to use the SD card. You can select in the menu apply update from ADB and specify the path to the file on your computer through ADB:
Code:
adb sideload "C:\adb\[B]UL-P01Z-WW-12.26.4.45-user.zip[/B]"
If the recovery menu does not appear, press any button once.
If you have a problem with recovery partition, do a hard reset (fastboot format), and then flash attached files (it is important to observe the sequence):
Code:
fastboot flash vrl "C:\adb\extracted_UL-P01Z-WW-12.26.4.45-user\vrl.bin"
fastboot flash recovery "C:\adb\extracted_UL-P01Z-WW-12.26.4.45-user\recovery.bin"
Click to expand...
Click to collapse
Deleted
So I FINALLY got around to trying your steps and.... IT WORKED!!
Can't thank you enough. I decided to "Apply Update using ADB" instead of the SD card and your step by step guide was perfect.
Thanks Again!!!!
InvisiBot said:
Message "can't mount /sdcard" it means low quality SD card, take another and use the fat32.
Take the online ASUS update UL-P01Z-WW-12.26.4.45-user.zip and put the zip file on SD card.
After fastboot (POWER + VOLUME UP) do a hard reset:
Code:
fastboot format cache
fastboot format userdata
After that boot to recovery (POWER + VOLUME DOWN) and choose apply update from sd card.
It is not necessary to use the SD card. You can select in the menu apply update from ADB and specify the path to the file on your computer through ADB:
Code:
adb sideload "C:\adb\[B]UL-P01Z-WW-12.26.4.45-user.zip[/B]"
If the recovery menu does not appear, press any button once.
If you have a problem with recovery partition, do a hard reset (fastboot format), and then flash attached files (it is important to observe the sequence):
Code:
fastboot flash vrl "C:\adb\extracted_UL-P01Z-WW-12.26.4.45-user\vrl.bin"
fastboot flash recovery "C:\adb\extracted_UL-P01Z-WW-12.26.4.45-user\recovery.bin"
Click to expand...
Click to collapse
..
deleted
i did al those steps with thw zenpad 7, because the thing stays in the logo, but im able to set it in recovery mode and fastboot; but when i flashed the latest firmware (from december) it asks for a newer one because the firmware on it is dated 10 april but that is not rolled out on the asus website; any adeas? gr bennie
C:\adb>fastboot flash recovery recovery.bin
(bootloader) recovery partition type: raw
target reported max download size of 1019215872 bytes
sending 'recovery' (8044 KB)...
(bootloader) Ready to receive: 0x007db000 size of da
OKAY [ 0.243s]
writing 'recovery'...
(bootloader) Flashing partition: recovery
FAILED (remote: Fail to flash partition: recovery)
finished. total time: 0.266s
why show error when i flash recovery ,...
i face problem in recovery
try in fastboot
fastboot format cache
fastboot format userdata
fastboot flash recovery (here the extract from above)
check recovery then!
I flash the zip with no errors but after reboot it says "ERROR FW image Verify Fail, Init: Tlv set update list fail" in the recovery menu
What is it mean what should i do?
InvisiBot said:
Message "can't mount /sdcard" it means low quality SD card, take another and use the fat32.
Take the online ASUS update UL-P01Z-WW-12.26.4.45-user.zip and put the zip file on SD card.
After fastboot (POWER + VOLUME UP) do a hard reset:
Code:
fastboot format cache
fastboot format userdata
After that boot to recovery (POWER + VOLUME DOWN) and choose apply update from sd card.
It is not necessary to use the SD card. You can select in the menu apply update from ADB and specify the path to the file on your computer through ADB:
Code:
adb sideload "C:\adb\[B]UL-P01Z-WW-12.26.4.45-user.zip[/B]"
If the recovery menu does not appear, press any button once.
If you have a problem with recovery partition, do a hard reset (fastboot format ...), and then flash attached files (it is important to observe the sequence):
Code:
fastboot flash vrl "C:\adb\extracted_UL-P01Z-WW-12.26.4.45-user\vrl.bin"
fastboot flash recovery "C:\adb\extracted_UL-P01Z-WW-12.26.4.45-user\recovery.bin"
If errors appear on the command line, you may need to unlock the bootloader:
Code:
fastboot oem unlock
fastboot oem unlock confirm
or:
Code:
fastboot oem asus-go
fastboot oem asus-go confirm
The files vrl.bin and recovery.bin were obtained using the following instructions: https://forum.xda-developers.com/an...uimage-bin-t3191929/post72093244#post72093244
Click to expand...
Click to collapse
can you extract recovery.bin and vrl.bin
from UL-P01V-WW-12.26.5.49-user from this firmware
my asus zenpad cant turn model number p01v
when i turn on it come no command stuck on there
what i will do
need system.img
InvisiBot said:
Message "can't mount /sdcard" it means low quality SD card, take another and use the fat32.
Take the online ASUS update UL-P01Z-WW-12.26.4.45-user.zip and put the zip file on SD card.
After fastboot (POWER + VOLUME UP) do a hard reset:
Code:
fastboot format cache
fastboot format userdata
After that boot to recovery (POWER + VOLUME DOWN) and choose apply update from sd card.
It is not necessary to use the SD card. You can select in the menu apply update from ADB and specify the path to the file on your computer through ADB:
Code:
adb sideload "C:\adb\[B]UL-P01Z-WW-12.26.4.45-user.zip[/B]"
If the recovery menu does not appear, press any button once.
If you have a problem with recovery partition, do a hard reset (fastboot format ...), and then flash attached files (it is important to observe the sequence):
Code:
fastboot flash vrl "C:\adb\extracted_UL-P01Z-WW-12.26.4.45-user\vrl.bin"
fastboot flash recovery "C:\adb\extracted_UL-P01Z-WW-12.26.4.45-user\recovery.bin"
If errors appear on the command line, you may need to unlock the bootloader:
Code:
fastboot oem unlock
fastboot oem unlock confirm
or:
Code:
fastboot oem asus-go
fastboot oem asus-go confirm
The files vrl.bin and recovery.bin were obtained using the following instructions: https://forum.xda-developers.com/an...uimage-bin-t3191929/post72093244#post72093244
Click to expand...
Click to collapse
Can you post the system.img file for the Zenpad C 7..0 and maybe the other factory images too? I accidentally overwrote it and have no way to recover it since I forgot to back up the ROM.
Related
When I saw that CWM 6 was available for our Flyer, I jumped to install it without waiting to see results of other users (stupid move, I know). Using DoomLord's touch recovery, I installed and rebooted. Seeing as I had nothing new to flash, I didn't boot back into recovery. Today, I decided I wanted to try out IOIDroid's newest work, and rebooted into recovery to prep for install.
CWM 6 was gorgeous! Only one problem: any action taken made all options text disappear! (nothing but the CWM logo would show until the power button was pushed again) I was able to reboot manually, installed ROM Manager, and CWM 5 through ROM Manager. Reboot to recovery, and nothing but a beautiful white screen/HTC logo... Manually rebooted again, and tried to re flash DoomLord's touch recovery through ROM Manager, reboot, same result. Tried using GooIM to flash the same recovery, and nada...
Luckily the ONEXXL still boots, but I'm stuck with no recovery, now... I'm thinking if I uninstall ROM Manager, delete the CWM folder from my SD, reinstall ROM Manager/CWM, that might fix it? I kinda feel like I'll get the same splash screen, though...
Any other ideas? Never completely lost recovery before...
My tab's Flyer than yours (unless this is posted in a Flyer thread... Then it's just as Flyer...)
http://android-gz.com
Use fastboot.
yes fastbot flash the recovery img
fastboot flash recovery "name of file.img"
That's the reply I was dreading... Lol. I've always had problems with fastboot / adb on my laptop... Think it's got something to do with Windows 7. CMD prompt opens and immediately closes when I try to open either... I'll try it again, though...
I chose the red pill... Now I'm in the mAtrix and I know Kung Fu...
http://android-gz.com
are you sellecting the fastboot.exe itself?
you need to open the command prompt on its own and navigate to the directory that holds the commands
mcord11758 said:
are you sellecting the fastboot.exe itself?
you need to open the command prompt on its own and navigate to the directory that holds the commands
Click to expand...
Click to collapse
Sho 'nuff... I'm a dolt! I haven't tangled with either since my old OG EVO... I soft bricked that, and gave up until I had the time to properly learn, and still haven't gotten the chance to learn. I'll try it the right way now...
I chose the red pill... Now I'm in the mAtrix and I know Kung Fu...
http://android-gz.com
IP IHI II IL said:
Sho 'nuff... I'm a dolt! I haven't tangled with either since my old OG EVO... I soft bricked that, and gave up until I had the time to properly learn, and still haven't gotten the chance to learn. I'll try it the right way now...
I chose the red pill... Now I'm in the mAtrix and I know Kung Fu...
http://android-gz.com
Click to expand...
Click to collapse
Download the start-here.txt attached to this post and place it in the same directory as your fastboot.exe. Change "start-here.txt" to "start-here.bat" and double click it. Follow the commands in the attached image to flash your recovery.img. Make sure the recovery.img is in the fastboot folder.
If the text options disappear when you're in recovery press volume-up and volume-down at the same time to toggle between "Back menu button disabled." and "Back menu button enabled."
pravus_nephilim said:
Download the start-here.txt attached to this post and place it in the same directory as your fastboot.exe. Change "start-here.txt" to "start-here.bat" and double click it. Follow the commands in the attached image to flash your recovery.img. Make sure the recovery.img is in the fastboot folder.
If the text options disappear when you're in recovery press volume-up and volume-down at the same time to toggle between "Back menu button disabled." and "Back menu button enabled."
Click to expand...
Click to collapse
Woah, dude! You ROCK! With 4 kids, and helping my fiancée with her daycare it's not easy to find the time to tinker, and you just saved my heinie! Thanks a TON!
I chose the red pill... Now I'm in the mAtrix and I know Kung Fu...
http://android-gz.com
pravus_nephilim said:
Download the start-here.txt attached to this post and place it in the same directory as your fastboot.exe. Change "start-here.txt" to "start-here.bat" and double click it. Follow the commands in the attached image to flash your recovery.img. Make sure the recovery.img is in the fastboot folder.
If the text options disappear when you're in recovery press volume-up and volume-down at the same time to toggle between "Back menu button disabled." and "Back menu button enabled."
Click to expand...
Click to collapse
Alright, my machine's a dolt now... I try to change the file, and it just renames it start-here.bat.txt... I managed to get into fastboot the right way, finally, and I've tried flashing the recovery to no avail. I've renamed it a few times, but my damn machine just adds the text to the file name instead of changing the file type...
(I just realized I needed to extract the img from the zip, did that and still won't flash...)
I know I must look like an idiot at this point, and sorry if I'm wasting your time with n00bishness, but like I said before, it's been a LONG time since I've been able to practice, so this is basically all new to me...
Sorry guys, and thanks for the help so far!!
Here are my failed attempts:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\PHILTHY>C:\android\fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
C:\Users\PHILTHY>devices
'devices' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\PHILTHY>C:\android\fastboot flash Flyer-HC-CWM5-Recovery-DooMLoRD-v02-T
ouchEdition.zip
unknown partition 'Flyer-HC-CWM5-Recovery-DooMLoRD-v02-TouchEdition.zip'
error: cannot determine image filename for 'Flyer-HC-CWM5-Recovery-DooMLoRD-v02-
TouchEdition.zip'
C:\Users\PHILTHY>c:\android\fastboot devices
HT15XJN00873 fastboot
C:\Users\PHILTHY>c:\android\fastboot recovery.img
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
C:\Users\PHILTHY>c:\android\fastboot update update.zip
error: failed to load 'update.zip'
C:\Users\PHILTHY>c:\android\fastboot flashall
error: neither -p product specified nor ANDROID_PRODUCT_OUT set
C:\Users\PHILTHY>c:\android\fastboot flash recovery.img
unknown partition 'recovery.img'
error: cannot determine image filename for 'recovery.img'
C:\Users\PHILTHY>c:\android\fastboot flash c:\android\recovery.zip
unknown partition 'c:\android\recovery.zip'
error: cannot determine image filename for 'c:\android\recovery.zip'
C:\Users\PHILTHY>c:\android\fastboot flash recovery.img
unknown partition 'recovery.img'
error: cannot determine image filename for 'recovery.img'
C:\Users\PHILTHY>c:\android
'c:\android' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\PHILTHY>c:\android\fastboot flash recovery recovery.img
error: cannot load 'recovery.img'
C:\Users\PHILTHY>
EDIT: ok, so I re-downloaded/installed the SDK and tools. I put the recovery.img in the folder "C:\android\platform-tools" and ran:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\PHILTHY>C:\android\platform-tools\fastboot flash recovery recovery.img
error: cannot load 'recovery.img'
C:\Users\PHILTHY>
WTH am I doing wrong?! I know it's user error...
EDIT 2: MORE failed attempts... starting to get frustrated...
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\PHILTHY>C:\android\platform-tools\fastboot flash recovery recovery.img
error: cannot load 'recovery.img'
C:\Users\PHILTHY>C:\android\platform-tools\adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\Users\PHILTHY>C:\android\platform-tools\fastboot devices
HT15XJN00873 fastboot
C:\Users\PHILTHY>C:\android\platform-tools\fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
C:\Users\PHILTHY>C:\android\platform-tools\fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.512s]
finished. total time: 0.514s
C:\Users\PHILTHY>C:\android\platform-tools\fastboot flash C:\android\platform-to
ols\recovery.img
unknown partition 'C:\android\platform-tools\recovery.img'
error: cannot determine image filename for 'C:\android\platform-tools\recovery.i
mg'
C:\Users\PHILTHY>C:\android\platform-tools\fastboot flash recovery.img
unknown partition 'recovery.img'
error: cannot determine image filename for 'recovery.img'
C:\Users\PHILTHY>C:\android\platform-tools\fastboot flash recovery recovery.img
error: cannot load 'recovery.img'
C:\Users\PHILTHY>C:\android\platform-tools\fastboot flash Flyer-HC-CWM5-Recovery
-DooMLoRD-v02-TouchEdition.zip
unknown partition 'Flyer-HC-CWM5-Recovery-DooMLoRD-v02-TouchEdition.zip'
error: cannot determine image filename for 'Flyer-HC-CWM5-Recovery-DooMLoRD-v02-
TouchEdition.zip'
C:\Users\PHILTHY>C:\android\platform-tools\fastboot flash C:\android\platform-to
ols\fastboot\recovery.img
unknown partition 'C:\android\platform-tools\fastboot\recovery.img'
error: cannot determine image filename for 'C:\android\platform-tools\fastboot\r
ecovery.img'
C:\Users\PHILTHY>C:\android\platform-tools\fastboot flash C:\android\platform-to
ols\fastboot\recovery.img
unknown partition 'C:\android\platform-tools\fastboot\recovery.img'
error: cannot determine image filename for 'C:\android\platform-tools\fastboot\r
ecovery.img'
C:\Users\PHILTHY>C:\android\platform-tools\fastboot flash recovery recovery.img
error: cannot load 'recovery.img'
C:\Users\PHILTHY>C:\android\platform-tools\fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
C:\Users\PHILTHY>C:\android\platform-tools\fastboot flash recovery recovery.img
error: cannot load 'recovery.img'
C:\Users\PHILTHY>C:\android\platform-tools\fastboot flash recovery recovery.img
error: cannot load 'recovery.img'
C:\Users\PHILTHY>C:\android\platform-tools\fastboot flash recovery.img
unknown partition 'recovery.img'
error: cannot determine image filename for 'recovery.img'
C:\Users\PHILTHY>
I have the recovery.img in "C:\android\platform-tools". I also created a folder named "fastboot" and put it in there, and tried to run it to no avail...grrrrr
IP IHI II IL said:
Alright, my machine's a dolt now... I try to change the file, and it just renames it start-here.bat.txt... I managed to get into fastboot the right way, finally, and I've tried flashing the recovery to no avail. I've renamed it a few times, but my damn machine just adds the text to the file name instead of changing the file type...
(I just realized I needed to extract the img from the zip, did that and still won't flash...)
I know I must look like an idiot at this point, and sorry if I'm wasting your time with n00bishness, but like I said before, it's been a LONG time since I've been able to practice, so this is basically all new to me...
Sorry guys, and thanks for the help so far!!
Click to expand...
Click to collapse
Your explorer settings are preventing you from changing the file type. If you are on Windows 7 change it in;
Start > Control Panel > Folder Options > View then uncheck "Hide extensions for known file types"
If you place that start-here.bat in the same folder as your fastboot.exe it will take you to the right directory in the terminal. It was only to try simplify things!
If you have the SDK extracted to the root of your drive and the terminal is saying "C:\Users\PHILTHY>" you're going to have to change directory by typing
Code:
cd C:\android-sdk\platform-tools
Then when you're in the proper folder in the terminal type out the following commands while in fastboot
Code:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot
Extract the recovery.img from the .zip. You don't need to make a folder called fastboot. Just have the recovery.img in the platform-tools folder along with the fastboot.exe.
pravus_nephilim said:
Your explorer settings are preventing you from changing the file type. If you are on Windows 7 change it in;
Start > Control Panel > Folder Options > View then uncheck "Hide extensions for known file types"
If you place that start-here.bat in the same folder as your fastboot.exe it will take you to the right directory in the terminal. It was only to try simplify things!
If you have the SDK extracted to the root of your drive and the terminal is saying "C:\Users\PHILTHY>" you're going to have to change directory by typing
Code:
cd C:\android-sdk\platform-tools
Then when you're in the proper folder in the terminal type out the following commands while in fastboot
Code:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot
Extract the recovery.img from the .zip. You don't need to make a folder called fastboot. Just have the recovery.img in the platform-tools folder along with the fastboot.exe.
Click to expand...
Click to collapse
I'll can't believe I forgot to enter the cd command... All that frustration over 2 lil letters... I promise I used to know this stuff well... Guess I've been outta the game for too long... That did it! Thanks for all your help guys, and SUPER thanks to pravus for goin the extra mile to help a dolt!
I chose the red pill... Now I'm in the mAtrix and I know Kung Fu...
http://android-gz.com
I had an even worse case on my flyer.
Tried to get the touch recovery, then install a HC based rom. It won't work at all. Everytime I got flash closed on recovery.
pravus_nephilim said:
Download the start-here.txt attached to this post and place it in the same directory as your fastboot.exe. Change "start-here.txt" to "start-here.bat" and double click it. Follow the commands in the attached image to flash your recovery.img. Make sure the recovery.img is in the fastboot folder.
If the text options disappear when you're in recovery press volume-up and volume-down at the same time to toggle between "Back menu button disabled." and "Back menu button enabled."
Click to expand...
Click to collapse
vinteri said:
I had an even worse case on my flyer.
Tried to get the touch recovery, then install a HC based rom. It won't work at all. Everytime I got flash closed on recovery.
Click to expand...
Click to collapse
Do you have a Gingerbread or Honeycomb hboot and are you HTCDev unlocked or S-OFF?
I have s-off. Before I flashed the touch recovery, I had ICS OneXXl rom installed.
hBoot should be HC.
pravus_nephilim said:
Do you have a Gingerbread or Honeycomb hboot and are you HTCDev unlocked or S-OFF?
Click to expand...
Click to collapse
vinteri said:
I have s-off. Before I flashed the touch recovery, I had ICS OneXXl rom installed.
hBoot should be HC.
Click to expand...
Click to collapse
Okay, so you're S-OFF with the Honeycomb hboot and trying to flash another HC ROM in recovery. How did you flash the touch recovery? I don't fully understand what you mean when you said "Everytime I got flash closed on recovery".
Everytime I tried to go to recovery, it showed up for less one second, then turned to black screen. Bad thing is I wiped the previous installed Rom. Without recovery, I can't restore from backup.
Sent from my PG86100 using Tapatalk 2
vinteri said:
Everytime I tried to go to recovery, it showed up for less one second, then turned to black screen. Bad thing is I wiped the previous installed Rom. Without recovery, I can't restore from backup.
Sent from my PG86100 using Tapatalk 2
Click to expand...
Click to collapse
Surely you can reboot into the bootloader, go to fastboot and try reflash the a recovery.img? Check the md5 of your downloaded recovery.img in case something is off.
I got my hands on a ls660 finally. It is possible to use send_command.exe to flash and backup the phone. I already tested this myself.
There is no need to zero your laf partition to enter fastboot to flash twrp!
1. copy the twrp bumped image on the sd card
2. cd into the folder that you have the send_command.exe stored.
3. with your ls660 turned off hold volume up and plug in the usb data cable
4. after the phone is in download mode send this command to the apropriate diag port:
Code:
Send_Command.exe \\.\COM14
The phone will show
Code:
Author : blog.lvu.kr
SPECIAL COMMAND : ENTER, LEAVE
6. This command backs up your recovery image and names it OGrecovery:
Code:
dd if=/dev/block/mmcblk0p17 of=/storage/external_SD/OGrecovery.img
7. This command flashes your phone with the twrp image:
Code:
dd if=/storage/external_SD/recovery_bumped.img of=/dev/block/mmcblk0p17
8. Send the following command in all caps:
Code:
LEAVE
When you reboot to recovery you should load twrp recovery.
A friend just gave me a Lenovo A560 which won't boot at all. I can enter recovery mode, tried reseting with no use but it seems to have problems with mounting block devices.
Code:
E:failed to mount block devices /dev/block/mmcblk1p1
E:remount block devices /dev/block/mmcblk1
E:failed to mount /sdcard (No such file or directory)
E:failed to mount block devices /dev/block/mmcblk1
E:remount block devices /dev/block/mmcblk1
E:failed to mount /sdcard (No such file or directory)
E:volume for path [/cache]
Any help would be apreciated, I am willing to try any experiments to sort it out.
solution
andymatr1x said:
A friend just gave me a Lenovo A560 which won't boot at all. I can enter recovery mode, tried reseting with no use but it seems to have problems with mounting block devices.
Code:
E:failed to mount block devices /dev/block/mmcblk1p1
E:remount block devices /dev/block/mmcblk1
E:failed to mount /sdcard (No such file or directory)
E:failed to mount block devices /dev/block/mmcblk1
E:remount block devices /dev/block/mmcblk1
E:failed to mount /sdcard (No such file or directory)
E:volume for path [/cache]
Any help would be apreciated, I am willing to try any experiments to sort it out.
Click to expand...
Click to collapse
Hi. I just managed to fixed problem wont boot yesterday on my A560. Unfortunately when I running recovery mode and trying to flash other ROM, it shows exactly what you write above. However below is what I did to make my phone pass Lenovo logo:
1. Download official rom in needrom website.
2. Extract the file.
3. Put the extracted file(system.img,recovery.img,cache.img,boot.img,userdata.img) inside folder you installed ADB. For me is C:\android
4. Remove battery from your phone for 5 seconds, put is inside back, hold both volume buttons along with plugging USB cable. Your phone will only show Lenovo logo(fastboot mode)
5. Run cmd.exe, type cd C:\android and press enter.
6. Copy below code:
fastboot erase system
fastboot erase recovery
fastboot erase cache
fastboot erase boot
fastboot erase userdata
paste it then press enter.
6.After it finished, copy:
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash vendor userdata.img
and press enter.
7. Copy:
fastboot reboot
and press enter.
8. This should reboot your phone back and enter the new flash official ROM.
Forgive for my bad English and please let me know if these works for you
Thank you very much for dedicating your time to help me. I really apreciate your help. I succeded earlier in installing the custom rom from the website you provided above and it works well. Cheers
Hi!
I'm trying to root my Huawei MediaPad T1-701w but am in need of help... I've tried out nearly every 'one click root' app or PC program out there, but every single one fails. Huawei has hardened the kernel/android version and patched all known exploits to date (October 2016). The issue is that the variant of the MediaTab I have is pretty uncommon (T1-701w) so there is not a lot to find about it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
However, I did find that the iovyroot might be able to root it, see https://forum.xda-developers.com/general/xda-assist/huawei-t1-701u-write-protection-t3418836 , but the current pre-compiled version of iovyroot is not compatible with my tablet (it needs new offsets).
I also tried downgrading, but I don't quite understand how to do so. I found one older ROM for my Mediatab variant which might contain more exploits according to 4PDA.ru, but how do I downgrade? The 'dload' method does not work. Also before downgrading, I want to dump my current ROM, which requires root, right?
Can anyone help me out here please?
Thank you!
If you have the most recent stock ROM of your device (oct. 2016), extract the file "boot.img" out of (UPDATE.APP) and put it here, and i'll send you back the rooted one, then follow the steps in the following thread to make it works:
https://forum.xda-developers.com/huawei-mediapad/general/root-root-mediapad-t1-10-t1-a21l-t3601136
=====
Here's the link for the stock ROM:
http://consumer.huawei.com/nl-en/support/downloads/detail/index.htm?id=80385
mann1 said:
If you have the most recent stock ROM of your device (oct. 2016), extract the file "boot.img" out of (UPDATE.APP) and put it here, and i'll send you back the rooted one, then follow the steps in the following thread to make it works:
https://forum.xda-developers.com/huawei-mediapad/general/root-root-mediapad-t1-10-t1-a21l-t3601136
=====
Here's the link for the stock ROM:
http://consumer.huawei.com/nl-en/support/downloads/detail/index.htm?id=80385
Click to expand...
Click to collapse
Many thanks for your reply! Please find the boot.img from the UPDATE.app of my ROM with header file (?) here: http://data.freek.ws/public/huawei_t1-701w/V100R001C232B009CUSTC232D001/
(It was too large to attach to this post, sorry).
Is PhilZ Touch 6 Recovery compatible with my tablet?
Many many thanks!! Kind regards.
Well, download the following zip file here
Both rooted and stock imgs are included.
I do not know if PhilZ recovery will work with your device or not, i don't have the same model.
Give it a try, you don't need full functions anyway , just the "install zip" one, BUT keep the stock "recovery.img" before you do, so you can go back to it in case philz didn't work.
Also you can try the CWM recovery fromhere, both ways are risky, but nothing serious i guess, you can go back to the stock recovery at any moment.
Tell me the results pls
GOOD LUCK
mann1 said:
Well, download the following zip file here
Both rooted and stock imgs are included.
I do not know if PhilZ recovery will work with your device or not, i don't have the same model.
Give it a try, you don't need full functions anyway , just the "install zip" one, BUT keep the stock "recovery.img" before you do, so you can go back to it in case philz didn't work.
Also you can try the CWM recovery fromhere, both ways are risky, but nothing serious i guess, you can go back to the stock recovery at any moment.
Tell me the results pls
GOOD LUCK
Click to expand...
Click to collapse
Many many thanks for your quick reply and effort
I manage dto flash the rooted boot.img without any problems, great !
Howevever, in your tutorial you write that I need to flash SuperSU in order to activate the rooting. But how can I flash it if I don't have custom recovery? PhilZ recovery sadly does not work, I tried
Stock recovery does not allow me to flash super su.
Many thanks
Kind regards.
You're very welcome
Try the following:
use command prompet and type:
adb root
if it works w/o any errors type:
adb shell
a new cm window will pop up with your device shell
[email protected]:/ $
type:
su
if the root works, the shell is gonna be:
[email protected]:/ #
If it works, download the superSu.apk file NOT the zip, restart the device,
then put SuperSU options "Default access: Grant" and check "Enable su during boot" then restart
mann1 said:
You're very welcome
Try the following:
use command prompet and type:
adb root
if it works w/o any errors type:
adb shell
a new cm window will pop up with your device shell
[email protected]:/ $
type:
su
if the root works, the shell is gonna be:
[email protected]:/ #
If it works, download the superSu.apk file NOT the zip, restart the device,
then put SuperSU options "Default access: Grant" and check "Enable su during boot" then restart
Click to expand...
Click to collapse
Once again thanks for your reply.
Hmm, the root doesnt seem to be working:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
U5MDU17327001608 device
C:\Program Files (x86)\Minimal ADB and Fastboot>adb root
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
[email protected]:/ $ su
/system/bin/sh: su: not found
But I did flash your rooted_boot.img.. What should I do?
Nope, it works very well, if it doesn't you would see an error after you type "adb root"
Just try to install superSU.apk directly like we do with any apk, then restart.
OR
If it didn't work, try this:
=========
adb devices
adb root
adb shell "mount -o remount,rw /system"
adb push su /system/bin/su
adb push superuser.apk /system/app
adb reboot
=========
put the superSu in the same folder with adb
mann1 said:
Nope, it works very well, if it doesn't you would see an error after you type "adb root"
Just try to install superSU.apk directly like we do with any apk, then restart.
OR
If it didn't work, try this:
=========
adb devices
adb root
adb shell "mount -o remount,rw /system"
adb push su /system/bin/su
adb push superuser.apk /system/app
adb reboot
=========
put the superSu in the same folder with adb
Click to expand...
Click to collapse
Thanks again for the help!
My tablet is a tough one I think. It says 'mount: Operation not permited'.
Any ideas?
Yep, your tablet comes with Spreadtrum SC7731G, and it's not easy to find a custom recovery for these chipsets.
But i'm sure the device is already rooted now, we just need a working custom recovery to flash the superSU, so pls keep the rooted boot.
===
I've googled some custom recoveries that are compatible with SC7731, so give them a try:
https://drive.google.com/file/d/0B8vhq1nCgRGdR3VmbE1RSWNRSjA/view
this is number 9 recovery img in this thread:
https://forum.xda-developers.com/showthread.php?t=2527663
=====
and here's another one:
http://www.mediafire.com/file/1j4uj3c4vk5rtcw/recovery.img
=====
BE CAREFUL,these ones are not tested on your device, so test them very carefully, one of them may work but with cranky touch function, try to use it just to flash the SuperSu ZIP file NOT apk.
mann1 said:
Yep, your tablet comes with Spreadtrum SC7731G, and it's not easy to find a custom recovery for these chipsets.
But i'm sure the device is already rooted now, we just need a working custom recovery to flash the superSU, so pls keep the rooted boot.
===
I've googled some custom recoveries that are compatible with SC7731, so give them a try:
https://drive.google.com/file/d/0B8vhq1nCgRGdR3VmbE1RSWNRSjA/view
this is number 9 recovery img in this thread:
https://forum.xda-developers.com/showthread.php?t=2527663
=====
and here's another one:
http://www.mediafire.com/file/1j4uj3c4vk5rtcw/recovery.img
=====
BE CAREFUL,these ones are not tested on your device, so test them very carefully, one of them may work but with cranky touch function, try to use it just to flash the SuperSu ZIP file NOT apk.
Click to expand...
Click to collapse
Thanks for your reply
Hmm, are you sure it's rooted? Because it keeps complaining about 'no permission' or is that caused due to incompatibility with my device?
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 2.171s]
booting...
FAILED (remote: no permission)
finished. total time: 2.173s
Freekers1337 said:
Thanks for your reply
Hmm, are you sure it's rooted? Because it keeps complaining about 'no permission' or is that caused due to incompatibility with my device?
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 2.171s]
booting...
FAILED (remote: no permission)
finished. total time: 2.173s
Click to expand...
Click to collapse
I guess it's compatibility issue.
1- flash the rooted boot
fastboot flash boot rooted_boot.img
===
2- flash one of the custom recoveries (don't boot them)
fastboot flash recovery recovery.img (use the right file name)
then restart
===
your device will start normally w/o any problem, there's no problem with the rooted boot.
then turn off the tablet and get into the recovery mode by (Vol. down + power buttons)
do not use the "adb reboot-bootloader" cm.
===
now the the recovery might work, and if it didn't, you will face the bootloader screen mode, type:
fastboot reboot
to restart your device, and flash the 2nd recovery img.
So sorry i don't have your device to try that myself.
mann1 said:
I guess it's compatibility issue.
1- flash the rooted boot
fastboot flash boot rooted_boot.img
===
2- flash one of the custom recoveries (don't boot them)
fastboot flash recovery recovery.img (use the right file name)
then restart
===
your device will start normally w/o any problem, there's no problem with the rooted boot.
then turn off the tablet and get into the recovery mode by (Vol. down + power buttons)
do not use the "adb reboot-bootloader" cm.
===
now the the recovery might work, and if it didn't, you will face the bootloader screen mode, type:
fastboot reboot
to restart your device, and flash the 2nd recovery img.
So sorry i don't have your device to try that myself.
Click to expand...
Click to collapse
Thanks for sticking with me
I tried both custom recoveries you sent me, but both fail with error: 'FAILED (remote: image is not a boot image)'.
I also tried creating my own recovery using these two tutorials: https://www.youtube.com/watch?v=w1Ap2YwmGVk & https://www.youtube.com/watch?v=hwMFBuCY-5k but I get the same error (image is not a boot image).
Grrrr, do you still have any ideas ?
Kind regards!
YVW, it's ok, no problem at all.
Pls do not use the command
fastboot boot recovery *.img to try the custom recovery, flash it directly with
fastboot flash recovery filename.img
usually custom recoveries even if they work fine give the same error when u try them with the "boot" command
mann1 said:
YVW, it's ok, no problem at all.
Pls do not use the command
fastboot boot recovery *.img to try the custom recovery, flash it directly with
fastboot flash recovery filename.img
usually custom recoveries even if they work fine give the same error when u try them with the "boot" command
Click to expand...
Click to collapse
I did flash it directly using: fastboot flash recovery xxxxx.img . That's when I got the 'image is not a boot image image' error
Well, we will try easy step, flash the rooted boot img then restart the device, then go to google play, and use the online install function to get superSU.apk, do not download it, just install it directly from the site
mann1 said:
Well, we will try easy step, flash the rooted boot img then restart the device, then go to google play, and use the online install function to get superSU.apk, do not download it, just install it directly from the site
Click to expand...
Click to collapse
I'm sorry, I can't find the online install function. I went to Google Play and installed SuperSU but as soon as it opens it says Device not rooter. After that it says no SU binary found and automatically closes..
Freekers1337 said:
I'm sorry, I can't find the online install function. I went to Google Play and installed SuperSU but as soon as it opens it says Device not rooter. After that it says no SU binary found and automatically closes..
Click to expand...
Click to collapse
It's ok, don't give up
Right now i run out of ideas, but give me some time to get my unrooted stock ROM back, to start the race toward rooting w/o custom recovery.
mann1 said:
It's ok, don't give up
Right now i run out of ideas, but give me some time to get my unrooted stock ROM back, to start the race toward rooting w/o custom recovery.
Click to expand...
Click to collapse
OK I'll wait for your reply.
Freekers1337 said:
OK I'll wait for your reply.
Click to expand...
Click to collapse
Hi
After long journey, i could say I've got an effective way to root your device and mine too w/o custom recovery, it works fine for me, hope it will be the same for you.
First you need to download the following files:
1- New rooted_boot img from here
2- Compressed folder mann1.zip from here
3- SuperSu.apk file from here
====
Now lets start,
1- Unzip the rooted img then flash it, (be careful it's not tested):
use the flash command NOT boot
Code:
fastboot flash boot rooted_boot.img
===
2- Unzip the file "mann1.zip" to get folder "mann1" then copy it directly into your device internal storage NOT the SD card. Put the the whole folder not the files inside.
===
3- Put SupeSU.apk into your SD card
===
If the rooted boot worked fine, restart your device in the normal mode (NOT the recovery or bootloader), and type the following commands one by one:
Code:
adb devices
adb root
adb shell
[I][COLOR="Red"]Now you supposed to see your root like that[/COLOR][/I]
[COLOR="Blue"][email protected]:/ #[/COLOR]
[COLOR="Red"]complete the commands in the shell:[/COLOR]
mount -o rw,remount /system
cat sdcard/mann1/busybox > /system/bin/busybox
cat /sdcard/mann1/su > /system/xbin/su
cat /sdcard/mann1/su > /system/xbin/daemonsu
cat /sdcard/mann1/su > /system/xbin/sugote
cat /system/bin/sh > /system/xbin/sugote-mksh
chown 0.1000 /system/bin/busybox
chmod 0755 /system/bin/busybox
chown 0.0 /system/xbin/su
chmod 0755 /system/xbin/su
chown 0.0 /system/xbin/sugote
chmod 0755 /system/xbin/sugote
chown 0.0 /system/xbin/sugote-mksh
chmod 0755 /system/xbin/sugote-mksh
chown 0.0 /system/xbin/daemonsu
chmod 0755 /system/xbin/daemonsu
daemonsu -d
pm install /sdcard/mann1/superuser.apk
am start -a android.intent.action.MAIN -n
eu.chainfire.supersu/.MainActivity >/dev/null
reboot
If everything run smoothly after rebooting you will find the SuperSu icon installed.
Do NOT run it now
Before that go to your SD card and install SuperSU.apk, from the device not via pc, then restart.
Now your device should be completely rooted , if SUperSu asked to updated via google, reinstall it OR let it updates by google play site.
hello all
i have a gigaset GS 270 plus, and everything i try to do on it fails
i backed up the data on my sd card using the recovery , but on restoring on an identical phone (trait for trait) it says "the backup file is out of date please rebackup your data
on the source phone i tried the same process and it went on smoothly but i cant risk formating, rooting , enabling adb, restoring and removing pasword because of the above problem.
i have 13 backup files of up to 25 gigabytes which i am unable to recover or decrypt on a pc even following the commands given on linux from this thread
https://forum.xda-developers.com/showthread.php?t=2408788&page=2
the phone connects in fastboot mode but not in adb mode
Fortunately it is a mediatek device and i have tried to back up the rom using this tutorial
https://android.stackexchange.com/q...nd-full-rom-without-root-for-mediatek-devices
but all to no avail
i tried a readback of my rom using help from @Alecxs using WwR MTK v2.51 from Ilya Aleksandrovich
but upon creating the scatter file it gives an error
https://ibb.co/Sd3HTfM
please i need anyhelp whatsoever to recover the files from the phone either by a readback or by unlocking the phone or any other method which i have not thought of
Thank you in advance!!!
search for stock ROM, use that preloader.bin
https://forum.xda-developers.com/showthread.php?t=3775129
https://forum.xda-developers.com/showthread.php?t=3899918
yet another instructions for exactly the same like the link you shared
how to create scatter file
https://forum.xda-developers.com/ap...v1-universal-systemless-t3432382/post77795016
aIecxs said:
search for stock ROM, use that preloader.bin
Click to expand...
Click to collapse
yeah, i thought of that too
i already tried searching but i was unable to find any rom except click baits
aIecxs said:
https://forum.xda-developers.com/showthread.php?t=3775129
https://forum.xda-developers.com/showthread.php?t=3899918
Click to expand...
Click to collapse
thank you let me try
Maybe that device has secure boot preventing SP Flash Tool from readback, try another download agent
we can help you porting TWRP but we can't help on readback, you are the only one who has physical access. if you follow the tutorial and it fails, maybe the tutorial is not working for this device
if you are using windows 10, try another PC with Windows 7 or try SP Flash Tool for Linux
edit: there are other methods for creating scatter file. post the output of fastboot getvar all
belvo02 said:
aIecxs said:
No, except you do a readback of metadata from SP Flash Tool. Note when login credentials are involved in encryption, you won't be able to decrypt even on rooted device
port TWRP recovery from Cubot X18 Plus and flash on locked bootloader, that's (besides official solutions) your best option to remove screen lock
Click to expand...
Click to collapse
do you have any suggestions for me?
i want to try dr fone but i dont think it supports gigaset smatphones
i need a method to remove the screen lock without loosing the data ,:sad:
i even got the same phone , i was planning to root it , restore the backup and then use twrp to remove the lock
but it says "the backup file is out of date please rebackup your data"
any method to recover this files s welcome, if i could get even just the pictures and videos, can any thing help me?
im going to try to connect it to sp flashtools and try what you said earlier
thank you for replying
Click to expand...
Click to collapse
you have two devices of same model? great, let's root the spare phone!
take away the source phone for now (the important one)
Do on the target phone only:
WARNING: factory reset - all data lost!
1) unlock the bootloader
- enable developer options by tapping build number seven (7x) times (in settings - about phone)
- enable OEM unlocking in developer options
- install platform-tools and connect device to PC in fastboot mode (Volume Down + Power)
- install usb drivers and check usb connection (from platform-tools directory in cmd.exe)
- unlock bootloader and confirm with Volume Up (factory reset)
Code:
fastboot devices
fastboot flashing unlock
fastboot reboot
2) temporary root device
- enable developer options
- enable usb-debugging
- connect to PC and install usb drivers
- check adb devices (from platform-tools directory in cmd.exe)
- on the phone display permanently authorize the incoming RSA key
- download mtk-su to PC
- adb push binary to /data/local/tmp
- chmod executing permissions
- run the binary until you see # prompt (multiple times)
Code:
adb push mtk-su /data/local/tmp
adb shell
cd /data/local/tmp
chmod 0755 mtk-su
./mtk-su
3) backup boot.img / recovery.img
- get list of partitions
- dump partitions into files (in # shell)
- copy files to Internal storage
- copy files to PC (via MTP)
Code:
ls -d $(find /dev/block -name by-name)/*
cat /dev/block/platform/mtk-msdc.0/11120000.msdc0/by-name/boot > boot.img
cat /dev/block/platform/mtk-msdc.0/11120000.msdc0/by-name/recovery > recovery.img
cp -v *.img /sdcard
4) root device with Magisk Manager
- install Magisk Manager
- open the app
- advanced settings - preserve force encryption
- keep avb/dm-verity
- tap install (2x) times
- select and patch a file - boot.img
- copy magisk_patched.img to PC
- reboot into fastboot
- flash the patched boot
Code:
fastboot flash boot magisk_patched.img
fastboot reboot
5) create your own TWRP recovery
... to be continued
(send me recovery.img will try to make TWRP and you can test)
edit: please do not full quote this post (i want update later). i will receive instant notification for answer button as well
aIecxs said:
you have two devices of same model? great, let's root the spare phone!
take away the source phone for now (the important one)
Do on the target phone only:
WARNING: factory reset - all data lost!
1) unlock the bootloader
- enable developer options by tapping build number seven (7x) times (in settings - about phone)
- enable OEM unlocking in developer options
- install platform-tools and connect device to PC in fastboot mode (Volume Down + Power)
- install usb drivers and check usb connection (from platform-tools directory in cmd.exe)
- unlock bootloader and confirm with Volume Up (factory reset)
Code:
fastboot devices
fastboot flashing unlock
fastboot reboot
2) temporary root device
- enable developer options
- enable usb-debugging
- connect to PC and install usb drivers
- check adb devices (from platform-tools directory in cmd.exe)
- on the phone display permanently authorize the incoming RSA key
- download mtk-su to PC
- adb push binary to /data/local/tmp
- chmod executing permissions
- run the binary until you see # promt (multiple times)
Code:
adb push mtk-su /data/local/tmp
adb shell
cd /data/local/tmp
chmod 0755 mtk-su
./mtk-su
3) backup boot.img / recovery.img
- get list of partitions
- dump partitions into files (in # shell)
- copy files to Internal storage
- copy files to PC (via MTP)
Code:
ls -d $(find /dev/block -name by-name)/*
cat /dev/block/platform/mtk-msdc.0/11120000.msdc0/by-name/boot > boot.img
cat /dev/block/platform/mtk-msdc.0/11120000.msdc0/by-name/recovery > recovery.img
cp -v *.img /sdcard
4) root device with Magisk Manager
- install Magisk Manager
- open the app
- advanced settings - preserve force encryption
- keep avb/dm-verity
- tap install (2x) times
- select and patch a file - boot.img
- copy magisk_patched.img to PC
- reboot into fastboot
- flash the patched boot
Code:
fastboot flash boot magisk_patched.img
fastboot reboot
5) create your own TWRP recovery
... to be continued
(send me recovery.img will try to make TWRP and you can test)
Click to expand...
Click to collapse
thanks im on it!
Thanks a lot @aIecxs for the posting, tried with a Gigaset GS270 but the mtk-su is not working:
1|Gigaset_GS270:/data/local/tmp $ ./mtk-su -v
Failed critical init step 1
Any workaround to get this device rooted?
Best regards