Related
Is there a way to remove the Cyanogen Recovery Console?
I'm quite new to Android myself but from my experience so far i'm sure you can 'replace' it with any recovery image - i went from cyanogens to the RA-hero-v1.2.3
If you're wanting to go back to stock recovery image you need to find the .img file for it then adb the file to your phone to replace the current recovery image. (just follow the process of installing the recovery image you currently have but using the new file)
Unfortunately i'm not sure where you can download the stock image.
Hope this helps!
i think in the ruu installer you can select what you want to overwrite/install. if so, just select recovery and there you go ;-)
the ruu installer can be found somewhere in development forum or on htc.com
There is one here frpm HTC Hero (Orange UK) also you will find nandroid in the shared folder. LINK
Hey Guys,
i want to remove recovery Build RA-hero-v1.6.2a but i have no idea how to ?
I thought with the RUU installer i could do it but it it doesn't work.
It tell me "no usb connexion".
Any help ?
Thanks !!!
To replace it with what?
with the original from HTC
So you're running the RRU file and its giving what error number?
It's error 170.
I think the recovery image block the process.
I'm running windows 7 64 bit, it may be help !
i think it can remove via fastboot .. simply erase it if you know how to use ADB
Run RUU under Windows XP SP3!
You should have looked at BTDAG's signature,...
Use [Guide] Drivers & RRU Errors Solved if your still having issues.
This is for real, folks. The first working custom recovery for Asus ZenPad 8.0 Z380M and a method to flash it under a locked bootloader. This took quite a bit of work to make, partly due to having to find a way to bypass the locked bootloader. And because of a kernel configuration issue that limited the size of the initial ramdisk, which took some serious effort to weed out. @lss1977 helped to port it to this device. And of course, credits to TeamWin for TWRP.
In addition to this thread, the current Z300M/Z301M TWRP thread and the the old Z300M recovery/rooting thread may be helpful. These models share the same hardware and software base, so most things that apply to one tablet also apply to the other.
DISCLAIMER
As usual, you do anything described in this post at your own risk. No one but you is responsible for any data loss, bricking or damage of your device.
REQUIREMENTS
Windows PC
SP Flash Tool version 5.1532 (only this version will bypass security checks)*
MediaTek VCOM drivers (available through Windows Update)
Z380M scatter file, attached
Recovery image, attached
Z380M preloader file (optional), available inside the stock firmware download
ZenPad Z380M tablet upgraded to Android N
* If you prefer to use a more recent SP Flash Tool, check out the special image file below.
This won't be a guide on how to use SP Flash Tool. There are plenty of good guides out there like this one on how to set up drivers, load scatter files, flash and make backups with SP Flash Tool. If you're not familiar with this software or how to flash MediaTek devices in general, please do your research before attempting this. I will just get straight to the specifics about the ZenPad 8.
FIRST TIME INSTALLATION
For a locked bootloader:
At this point you should have your tablet powered off, the drivers installed, all of your data backed up, and SP Flash Tool v5.1532's Download tab open and loaded with the tablet's scatter file. Open the download agent file DA_PL.bin, replacing the default MTK_AllInOne_DA.bin. (You can use the AllInOne DA if you want, but the procedure involves extra steps as described below.) Load the extracted TWRP recovery image (twrp-3.2.1-0-z380m.img) under the recovery partition line in the partition table. Click the Download button inside SPFT. Now just connect the USB cable to your tablet and your computer's USB port. It should start the download process automatically and disconnect when finished.
Alternative Method:
If you're using MTK_AllInOne_DA.bin, you have to hold the Volume Up key as you insert the cable, which puts the device into an emergency download mode. In addition, you will need to have the stock preloader*.bin file loaded inside SPFT for it to be able to communicate with your tablet. The preloader is available inside the official zip file download. Do not flash the preloader (untick the box) or any partitions other than recovery. You just need to have a valid bin file selected under the Preloader line.
For an unlocked bootloader:
If you have used the Asus unlock tool to unlock your device, you will still not be able to use fastboot flash to install a custom recovery. However, you can do a "hot boot" or a tethered boot of TWRP. This method doesn't require SP Flash Tool. Download the TWRP image, put your tablet in fastboot mode and connect to PC. Then run this command to boot TWRP dynamically:
fastboot boot twrp-3.2.1-0-z380m.img
Once inside TWRP, flash twrp-3.2.1-0-z380m.img to Recovery using Install -> Install Image. Then reboot to recovery. You may be able to use TWRP in the tethered boot mode, but that could result in glitches due to different parameters passed by the bootloader to the kernel. That's why flashing is recommended.
To update from your installed TWRP version to a new one, just transfer the image to your tablet, then boot to TWRP and install it by going to Install -> Install Image and flashing to Recovery.
START RECOVERY
With the tablet powered off, hold the Volume Up and Power keys together until you get to a menu where you can select "recovery". Use Vol. Up to scroll and Vol. Dn to select. If you have a locked bootloader, it will show a Yellow State message because the recovery is not signed by the OEM. Just press volume up to boot it. On the welcome screen of TWRP it will ask you about modifying the system partition, I suggest you go with Keep System Read-only. Doing otherwise will complicate your OTA updates.
WARNING: Never start the stock recovery from the bootloader menu on this device. It is programmed by the bootloader to instantly wipe your data without any warning. Also, be aware that Android installs the stock recovery at every normal boot cycle. So you either have to flash the TWRP every time you want to run it, or disable the automatic recovery installation in the stock firmware. Any kind of mod to the boot image will prevent the automatic recovery installation. If you're not sure which recovery you have installed, you can always do a 'adb reboot recovery' from Android without risk of data loss.
What works: Basically everything... access to major partitions, decrypted userdata partition, decrypted adoptable storage, external SD card, ADB, USB-OTG, touch interface, splash screen, installing stock Asus OTA/web FW updates
What doesn't work: (no known problems yet, but please report any)
Not guaranteed to work: factory reset
DOWNLOAD
(Updated February 3, 2018: updated kernel to firmware 5.3.18; up-to-date TWRP 3.2.1 sources)
SP Flash Tool v5.1532
Z380M Scatter file for all storage sizes (right click, Save link as...)
Recovery image
Signed image for Flash Tool only -- may be flashed with recent SP Flash Tool versions -- DO NOT INSTALL USING ANY OTHER METHOD -- tested with SPFT 5.1736.
Development and experimental files
Source code
P.S. The thanks button doesn't bite.
Nice one now lets get some custom roms done.
Has anyone installed this yet? I see the file has been downloaded a few times. Any feedback is welcome.
If you want the recovery to stick after reboot either rename or remove system/bin/install_recovery.sh.
lss1977 said:
If you want the recovery to stick after reboot either rename or remove system/bin/install_recovery.sh.
Click to expand...
Click to collapse
The way I did it was to edit the init.rc file inside the boot ramdisk and comment out the service block that calls install_recovery.sh. I used the MTK boot image unpack/repack tools. I don't know, it seems like changing anything on the system partition will break OTA updates because of dm-verity. Because that depends on verifying each block of the file system. I have never even mounted the system as R/W in recovery.
how to create scater file from text posted? I copied all text to MT8163_Android_scatter.txt file but when open with splash tools give error "scatter file is invalid"
please atach your working scatter file to other atachments
PxYra said:
how to create scater file from text posted? I copied all text to MT8163_Android_scatter.txt file but when open with splash tools give error "scatter file is invalid"
please atach your working scatter file to other atachments
Click to expand...
Click to collapse
OK, I added the scatter file as a download. It was a pain in the ass to copy & paste. (But it did work.)
Problem fixed downloaded new version of flashtool 5.16 and scatter working
Ok I installed TWRP on Z380M P00A, and wanna say to other
1. Use VCOM drivers only from splash tool official site
2. To install VCOM drivers first need enter chinese recovery tablet, then in windows device manager you see USB device, install manualy drivers (don forget in windows disable driver signature)
3. Use only SP-Flash-Tool-v5.1532.00, newer or older version not properly working with this phone
Ok, thanks for the update, PxYra. Just to let you know, there are signed versions of VCOM drivers floating around so you don't need to mess with signature enforcement. Here's one: https://www.androidfilehost.com/?fid=24591000424943663. They are also updated by Windows so you can just let Windows Update install them.
Thanks for your work.
Flashing procedure works only with "MTK_AllInOne_DA.bin" method for me. But this is OK!
(Updated May 6, 2017: added kernel from firmware 5.3.7, source code cleanup)
Click to expand...
Click to collapse
is it possible to get the older versions? I need Android 6.x, because of xposed-Framework for my Zenpad 8.0 Z380M.
Greets Freisei
Hey freisei...
I never posted a version for Android 6. There was just one based on the 5.3.6 kernel, practically the same as the current one. That's why I didn't keep it. I could try to build one for you if you want, but I can't test it of course. Does this recovery not boot at all on the old firmware?
It's strange that the DA_PL.bin method didn't work for you. What happened when you tried it? I suppose the old preloader doesn't allow it(?).
hello guys, you think lineage os official version for asus z380kl (p024) will work on our z380m ?
---------- Post added at 08:19 PM ---------- Previous post was at 08:05 PM ----------
Can anyone help me? after selecting recovery img, pressing download and inserting usb cable, nothing happens. Thanks in advance
lss1977 said:
If you want the recovery to stick after reboot either rename or remove system/bin/install_recovery.sh.
Click to expand...
Click to collapse
hello friend, can you please upload that file? I deleted it, but now I need it to revert to official recovery, as my zenpad is bricked! It would be of great help! thanks!
Pires_7 said:
hello friend, can you please upload that file? I deleted it, but now I need it to revert to official recovery, as my zenpad is bricked! It would be of great help! thanks!
Click to expand...
Click to collapse
Your ZenPad didn't brick because you deleted install_recovery.sh. It's because you modified the system partition. Making any mods to system is bad advice unless you know exactly what you're doing. Even mounting it in r/w mode can break it. That's because dm-verity has tripped and is blocking access to changed blocks of the file system. So you have 3 options: mod your boot image fstab file to disable dm-verity, restore the original system image block-for-block (either from backup or official firmware converted to an img file), or wipe userdata (lss reported that to work).
Pires_7 said:
hello guys, you think lineage os official version for asus z380kl (p024) will work on our z380m ?
Click to expand...
Click to collapse
Nope, no chance.
diplomatic said:
Your ZenPad didn't brick because you deleted install_recovery.sh. It's because you modified the system partition. Making any mods to system is bad advice unless you know exactly what you're doing. Even mounting it in r/w mode can break it. That's because dm-verity has tripped and is blocking access to changed blocks of the file system. So you have 3 options: mod your boot image fstab file to disable dm-verity, restore the original system image block-for-block (either from backup or official firmware converted to an img file), or wipe userdata (lss reported that to work).
Nope, no chance.
Click to expand...
Click to collapse
Ok. I made some real s*it, I think I deleted every partition except recovery. Can you provide me a twrp backup or some way around my problem?
What do you mean you deleted every partition except recovery? There's like 28 partitions. You would have to work hard to accomplish that.
My first suggestion is to extract a system.img from the Asus stock firmware zip using this. Then flash it with SP Flash Tool. You might also try to install a full firmware zip from TWRP. Although I have no idea if that will work or if it's even safe to try.
diplomatic said:
What do you mean you deleted every partition except recovery? There's like 28 partitions. You would have to work hard to accomplish that.
My first suggestion is to extract a system.img from the Asus stock firmware zip using this. Then flash it with SP Flash Tool. You might also try to install a full firmware zip from TWRP. Although I have no idea if that will work or if it's even safe to try.
Click to expand...
Click to collapse
i was able to extract system.new.dat from stock firmware zip, but it extracts to a system folder. How do I flash this through sp flash tool?
OK, the system folder you don't need. It should have produced a system.img file also. That's the file you need to flash. Just select it for the system partition row in the partition list and then Download. Hopefully that will be enough.
EDIT: I just looked at the script, and realized the system.img.img file gets deleted in the process. So what you need to do is start the extraction, then after it makes system.img.img, when it starts extracting individual files, hit Ctrl+C. Then you'll end up with the img file.
Thank you very much! it works! YOU are the BEST!
please tell me, in your scatter file, address partition_name: frp (0x80a5000) is correct? if i format this partition (frp), google account remove?
Has anyone been able to figure out how to root the Alcatel idealXTRA (5059r)? I have been able to make a modded boot image with Magisk but I can not flash it to my phone because I need a DA file for SP Flash Tool specifically for this phone
I've been able to unlock the bootloader with Android "Tool all in one" which i found on here sometime ago. Actually have gotten a "successful" flash thru adb bootloader but with no effect on the device. I've tried a variety of tools, you'll need MtkDroidTools (Mediatek specific tool) and a host of other things and pherhaps you'll have some luck. I however did not. It appears that this specific device and its hardware are simply beyond my skills in rooting which are extensive so I question the viability of the exercise all together. That being said I still devote multiple hours a month attempting.
SUCCESS!!
The DA file your speaking of is actually located in the SP Tool folders : \SP_Flash_Tool_v5.1904_Win\\MTK_AllInOne_DA.bin
Disclaimer this method is finicky at best but on my device has worked, I take no responsibility for bricked/destroyed devices nor voided warranties. This simply resembles the method I used to successfully root my Alcatel 5059r Device nothing more
Alright I'm going to do a small write up with links for you. I'm assuming you have your bootloader unlocked and Magisk rooting is sufficient bc if its not well your not going to be able to root this device. First we need stock firmware, magisk manager 7.0, and the flashing tool that works with this phones MediaTek CPU.
HTML:
https://alcatelfirmware.com/alcatel-onetouch-ideal-xtra-5059r
Here you'll find both the stock firmware and the SP Flash Tool for this particular hardware.
You'll also need the latest Magisk Manager app on your phone(great idea for after you root if you've saved it on your SD as well as its the first thing you want to install after). You can find that on XDA or Github or a simple google search.
In short you need to patch the stock firmwares boot.img with Magisk Manager in order to gain root.
Once you've downloaded your Firmware, Tool, and .apk of Magisk Manager extract the boot.img from the stock firmware .zip/.rar then move it a storage path somewhere you can find it on your device. THEN DELETE THE BOOT.IMG THAT REMAINS IN THE .ZIP FOLDER
Start magisk manager and you'll probably get a big red X on Magisk 18.1, press it and install > patch boot image, select the stock boot.img we extracted to your pc then moved to your device.
With the Patch_boot.img move it off your devices storage back onto windows. Then add it back into the .zip/.rar Stock Firmware folder. Now we have a complete set of stock firmware flashed with Magisk 18.1 and ready to go!
Now you have a properly rooted boot.img now onto the flash
SP Flash Tool is a finicky tool at best, I always got error codes but was successful. Start off by shutting off your phone and unplugging the USB if your connected.
Extract the patched stock firmware .zip/.rar
Extract SP Flash tool, and run the flashtool.exe
From here you can follow the basic instructions on the website I posted
If you need an Auth file run a search here in XDA and you'll find a nice little .zip with an Auth file in it that works.
Your Scatter file is in the stock firmware, Auth file above.
With your phone still off & disconnected and your 3 drop boxes on the SP Flash Tool full and looking like the guide on the website. Press download. Attach your phone to USB and hit Volume up or down. Here is kind of the tricky part and trust me error codes don't necessarily mean there was any error. I ended up using the windows chimes to tell when the device was picked up, it disconnects pretty quickly but in between connection/disconnect chimes you have enough time to hit download again and you should get a Red Line on the bottom of SP tool saying 100% Completed, although probably with an error code. I did this routine of flashing in between chimes probably 10 times.
Reboot and yes your phone has been wiped, first thing you'll want to do is reinstall magisk manager and with any luck you should have green checks beside both boxes.
Proofs
https://forum.xda-developers.com/picture.php?albumid=15313&pictureid=58444
https://forum.xda-developers.com/picture.php?albumid=15313&pictureid=58445
Rooted with magisk and built twrp
deleted
Well in case anyone wants to work on this I'm uploading TWRP
deleted
deleted
Deleted
deleted
Can't seem to get root to work on gsi
deleted
Here's some good stuff and how I got recovery and LOS 16 on alcatel idealxtra 5059r
https://forum.xda-developers.com/an...16-alcatel-t3933004/post79586479#post79586479
LgPWN'd said:
Here's some good stuff and how I got recovery and LOS 16 on alcatel idealxtra 5059r
https://forum.xda-developers.com/an...16-alcatel-t3933004/post79586479#post79586479
Click to expand...
Click to collapse
EVEN BETTER LOOK AT OUR TELEGRAM GROUP
https://t.me/Android_General_Chat
ROMS
TOOLS
RECOVERIES
ROOT LIVES THERE
come join in the fun
I just bought a Nuu R1 Rugged Phone. It has Oreo 8.1.0 on it.
It is an "unlocked" phone. But I don't know if unlocked refers to the phone carrier or to the boot loader. (I'm thinking phone carrier.)
The last I rooted my tablets was Android 5, which required using a custom script that a dev here wrote that temporarily ran CW via fast boot.
I would like to root my R1. I hear now that Magisk is the way to go. (Instead of SU.)
Most every Guide says that I have to have TWRP installed before installing Magisk. But there's no TWRP for the R1. And I am incapable of compiling my own.
I learned, from Nuu Tech Support, that I can get into the phone's Recovery mode with some hidden button pushes. Here's a screen shot:
My first question is, could I simply install Magisk by selecting "Update from SD card"?
If it's not that easy, then, second: I can also get to a fastboot screen. (Not shown here.) Could I install Magisk from ADB on my computer?
I suppose a third question: Is there a version of TWRP that's compatible with this phone? And if so, how do I find it? It would be nice to have a Nandroid backup.
I am willing to show various screens that come up from various button pushes if that would help a dev here.
More data for TWRP'ing
So, I see that one needs an image of the OEM ROM to compile TWRP. I found two sites on the web that claim to have the ROM. (Before the R1 was officially released.) Sounds sketchy. Will try to get an image from Tech Support.
In the meantime, I found that the bootloader can be unlocked (or allowed to be unlocked) via a setting under Developer Options.
I contacted Nuu Mobile Support and they were kind to send me the MediaTek USB drivers for the R1.
It was a two step process to get the driver installed for ADB. But now I have access to the R1 via ADB.
I read here on the forums that I can boot TWRP via fastboot, and not risk ruining/corrupting the R1's Recovery Partition.
Anyone know of a TWRP model version that's close enough to work on the R1? (I presume a TWRP for another MediaTek device might work?)
I would hate to try KingRoot to get root.
I found a website called unofficialtwrp.com. It has a TWRP for the MediaTek 6739, running Oreo 8.1, with 16/2 GB. That's exactly what the Nuu Mobile R1 has.
So, hopeful that this would allow me to root my R1, I tried it. (Short version: Didn't work.)
I already had ADB installed and could talk to my R1 via ADB.
But once the R1 had booted into fastboot mode via ADB, I got a message from fastbood devices that it was "waiting."
I learned that that message means that I didn't have drivers for fastboot.
I ended up installing a fresh version of Win8.1 and using the Windows' updater to find the needed drivers. I had to have the R1 plugged in to the USB in fastboot mode for this to work. After that, I could talk to the device via the fastboot command.
So I unlocked the boot loader (which wiped my data - not every Guide warns you about that) and I did "fastboot boot recovery.img."
I got the message that the recovery file had transferred. After abotu 15 seconds, the phone rebooted. But no TWRP.
Rats.
I didn't want to try the fastboot flash command in case this unoffiical twrp from an unofficial site bricked my phone. If I understand things correctly, booting in fastboot to the recovery.img should give me a temporary instance of TWRP.
Presumably, after copying Magisk into memory, I would be able to get root that way.
PMikeP said:
I found a website called unofficialtwrp.com. It has a TWRP
Click to expand...
Click to collapse
Whoa you have been busy you must've heard XDA helps those who help themselves.. :highfive:
I just dropped by to say, 1st rule of modding is taking a pristine stock backup..
For MTK devices, there is a tool called SP Flash Tools, a quick search will help you take a full backup using this tool.
Afterward, you can even try using SP Flash Tools to flash a Magisk patched boot image to your device for ROOT!
Hope this helps!
Thanks. I did see SP Flash Tools mentioned and I did take a look at it. While I've rooted before, I'm trying to get my head around a Scatter File.
Everything I've read so far - well, almost everything - says that I need TWRP to get Magisk installed. But if you think it can be done via SP Flash Tools, I'll start playing with it.
Root nuu r1
Did u ever manage to figure out how to do this & get TWRP to install? :fingers-crossed:
No, I haven't had time to play with rooting lately. I still would like to root it tho.
Anyone know how to root the nuu phones?
someone has the boot.img i need the image
I will port TWRP for you in case you have stock recovery.img
jjgvv said:
I will port TWRP for you in case you have stock recovery.img
Click to expand...
Click to collapse
plis
do you have stock rom?
Any guide on unlock/rooting Xiaomi Mi Pad 5 Pro from China? I need root access + english. If there is HD Netflix, it would be great.
Go through the regular Xiaomi unlock process (register device, connect to unlocking tool, wait 7 days, unlock). Unlocking will wipe (factory reset) the device. Choose English when setting up the device after unlocking.
Download Magisk and install.
Download Fastboot enuma ROM from Xiaomi. (Fastboot is easier than recovery)
Extract boot image from ROM zipfile.
Copy boot image file to device and use Magisk to patch the file. Copy file back to PC.
Reboot into fastboot. Fastboot flash patched boot image (possibly best to flash A & B, but if something goes wrong then its a long process to recover).
Reboot. Rooted.
There is another thread with details on getting HD Netflix & Amazon working if it does not by default.
Sorry, I have no knowledge of software.
Magisk download from playstore and install on phone?
Any link to download the fastboot enuma rom?
What is Fastboot flash patched boot image? What is A and B?
While everyone must admittedly start from somewhere, I will need to caution you that blindly following instructions from the internet may end up with you having an un-usable device. Having some idea of what the instructions are doing is a far safer option.
Secondly, rooting is not a magical solution for everything, you indicated you *need* root, yet you also seem unfamiliar with Magisk. So are you sure you really need root? Root will not magically make the system native English UI if that is what you were hoping. You would need to use the Chinese ROM in English, or wait until a Global rom is released or 3rd party roms.
Unlocking Xiaomi / Mi devices is well documented you can follow any of those guides.
Once unlocked:
Download Magisk apk from here: https://github.com/topjohnwu/Magisk copy to the device and install.
Download the ROM for your device. Preferably the same version that is already on the device. Also preferably the "fastboot" type. Fastboot type has the individual files you need inside the zipfile, plus this will be a good backup to have in case something goes wrong as the fastboot ROM can be used to re-install.
You can try xiaomirom.com for the rom files, check that the download comes from the official xiaomi site though. "enuma" is the model name for the Pro 5G version.
Unzip the rom file and copy the boot.img file to the device
Open magisk on the device and choose install, select and patch a file, choose the boot.img file.
Copy the patched file back to a PC, reboot the tablet into fastboot mode and connect to the PC
On the PC make sure you have the right drivers installed and the fastboot program (no idea how to do this on windows).
In a command shell window type fastboot flash boot <name of patched file>
Reboot the tablet. Open Magisk and it should say installed and you should have root access
Heard of bricking and unbricking solutions.
I rrequire root access to system files or app files inaccessible normally.
I am ok with China rom as long as most of its UI is in English with Google Playstore.
"Download the rom for your device"? Any website link to do so? Hmmm... I am so confused. Any YouTube videos to show step by step? The first part to signing into xiaomi account to unlock device is ok. But the rooting part sounds so complicated.
Pardon me for my inexperience.
Check in Magisk manager if Mi Pad 5 Pro uses A/B partition. If so, flashing a patched boot.img to both partition is required.
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
I cant this working with 'https://hackmd.io/@EdwardWu/ArrowOS_elish'
can anyone help please?