Phone Details
Motorola Atrix 4G AT&T (bought around June 2011 Time frame)
System Version
4.5.91.MB860.ATT.en.US
Model Number
MB860
Android Version
2.34
Baseband Version
N_01.77.30P
Webtop Version
WT-1.2.0-110
Kernel Version
[email protected] #2
Build Number
4.5.91
I am absolutely new to this Android ROM installs on the phones. Though I decided to install this ROM I absolutely didn’t’ have any idea how to proceed. As a beginner I started doing the following in order.
Download and Keep the CM7 ROM
1. Downloaded Ba2F.zip to my laptop
2. Downloaded and Installed the Motorola USB drivers MotoHelper_2.0.53_Driver_5.2.0.EXE
3. Connect the Atrix and set the USB option on the phone to “USB Mass Storage”
4. Copy both BaTF.zip as well as the Extracted one to Phone internal storage as well as the Ext-SDcard on the phone
Download ROM Manager and Titanium Backup
1. Downloaded both from Android Market (ROM Manager Pro and Titanium Backup Free Version)
2. Both Apps won’t open because I had not ROOTED the phone
Root the Phone
1. I used “Pete's Motorola Root Tools.EXE” file to ROOT the phone
2. Followed step by step as mentioned here http://www.androidauthority.com/how-to-root-motorola-atrix-4g-35233/
Flash ClockworkMod Recovery
1. I used ROM Manager to do this as when you try to do anything in ROM manager it prompts to do this. The version of this is 5.0.2.0 ( I am not sure what is this for why we have to do this)
Unlocking the Bootloader
1. What I learned is, to unlock the bootloader, we have to first flash the phone with the SBF file
a. Installed RSDLite5.3.1.msi
b. Loaded the file 4547-fix-try2.sbf (Downloaded from http://forum.xda-developers.com/showthread.php?t=1136261)
c. Boot the phone with Power+volume UPPER key pressed till "Starting RSD protocol support" comes up
d. Connect to the Laptop and Hit Start button in RSD Lite Program
e. It Did Throw an error saying “FAIL” after showing the following message
i. Failed to boot: error 0x1000'( not word for word). There will also be a list of boot options like Fastboot, RSD, Recovery, etc. And it says Starting Fastboot Protocol
2. Then comes unlocking the phone
a. Though I had the previous error message, it still had the Fastboot Protocol loaded
b. I went to the FASTBOOT folder in command prompt of my laptop executed the following to unlock the phone which worked perfectly as I see the “Unlock” on the left hand corner when phone boots
c. fastboot oem unlock (it gave me the code) then I used the code to unlock
d. fastboot oem unlock #######
e. fastboot reboot
3. Installing the recovery IMG
a. I had downloaded the Recovery IMG file (recovery-atrix5.img) from http://forum.xda-developers.com/showthread.php?t=1204500
b. Booted the phone into Fastboot mode (turn off phone, hold power and volume down key until 'fastboot' appears then use volume up to select so it says 'starting fastboot protocol support').
c. From the CMD promnt and FASTBOOT directory I used fastboot erase recovery
d. Then I executed fastboot flash recovery recovery-atrix5.img (Note: I didn’t rename the file to recovery as suggested by some people)
e. Then gave fastboot reboot to restart.
4. Booting into Recovery mode (This is where I have the problem)
a. The phone is not booting into recovery it’s not going past the Android and yellow Triangle screen
b. I re-flashed the phone same SBF file (this time it was a success showed in the RSD Lite Program), re-installed the same IMG file after renaming to recovery.img
c. Also tried with a different IMG from the same link (recovery-blue-atrix5.img) but no luck
d. Also deleted the file install-recovery.sh from ./etc/ folder (bought the app root manager to delete the file) and then push the recovery.img, no luck
e. Some people said to TAP the bottom right corner while on that screen, did that but nothing is happening
f. Then I saw a note to press both the Volume Keys at the same time, this works but in this mode the cursor (I mean the selection) on the phone doesn’t go to the First TWO (i and iii) shown below, it allows me to select any of the last FOUR (v, vi, vii, viii).
i. Android System Recovery <3e>
ii. <EMPTY LINE >
iii. Android System Recovery utility
iv. <EMPTY LINE >
v. Reboot System now
vi. Apply update from sdcard
vii. Wipe data/factory reset
viii. Wipe cache partition
g. Using the above option I did factory reset but sill no results.
5. Current condition of the phone
a. It boots in unlock mode and I can do all the daily tasks. But I want to install the CM7 ROM that’s my requirement
PLEASE HELP HELP HELP
First of all, I applaud your effort in giving the a very comprehensive description of your issue.
Second, it seems you are having issues with installing a custom recovery because the recovery you're describing is still the stock recovery. I'll look around and see if I can find something that might help.
jhakash said:
4. Booting into Recovery mode (This is where I have the problem)
a. It boots in unlock mode and I can do all the daily tasks. But I want to install the CM7 ROM that’s my requirement
PLEASE HELP HELP HELP
Click to expand...
Click to collapse
---------- Post added at 11:31 AM ---------- Previous post was at 11:28 AM ----------
Have you tried re-installing the CWM from RomManager through RomManager? And then boot into recovery from within the app?
---------- Post added at 11:40 AM ---------- Previous post was at 11:31 AM ----------
EDIT: This might seem trivial, but is "USB Debugging" turned on?
You are the Man, I just flashed the same CWM 5.0.2.0 and i am in the recovery mode. This gave me an error when i did last time hence i didn't try again.
Thanks a bunch
Glad I can help, also, I think it's recommended to use the RomManager recovery for CM7 so good thing it worked.
jhakash said:
You are the Man, I just flashed the same CWM 5.0.2.0 and i am in the recovery mode. This gave me an error when i did last time hence i didn't try again.
Thanks a bunch
Click to expand...
Click to collapse
Oops.. started again, Can i use the recovery-atrix5.img and ROM manager flash it? if yes, then how?
I copy this file (after renaming to recovery.img) to both internal storage and SD card then what option should i choose in ROM Manager?
If you downloaded the CWM zip file for the romracer recovery and as long as RomManager's recovery is working then, yes, you can.
jhakash said:
Oops.. started again, Can i use the recovery-atrix5.img and ROM manager flash it? if yes, then how?
I copy this file (after renaming to recovery.img) to both internal storage and SD card then what option should i choose in ROM Manager?
Click to expand...
Click to collapse
jhakash said:
Oops.. started again, Can i use the recovery-atrix5.img and ROM manager flash it? if yes, then how?
I copy this file (after renaming to recovery.img) to both internal storage and SD card then what option should i choose in ROM Manager?
Click to expand...
Click to collapse
See post#2 from romracer's thread. Read the Miscellaneous part. Probably need to get rid of, or backup, install-recovery.sh.
He has mentioned he already did that. In his OP, under the steps he took look at "Booting into Recovery Mode" - 4.d, he says he removed it.
Maybe he's not doing it in the right order? Do you happen to know which should be done first as far as installing recovery and removing said file?
ghost_og said:
See post#2 from romracer's thread. Read the Miscellaneous part. Probably need to get rid of, or backup, install-recovery.sh.
Click to expand...
Click to collapse
live4nyy said:
He has mentioned he already did that. In his OP, under the steps he took look at "Booting into Recovery Mode" - 4.d, he says he removed it.
Maybe he's not doing it in the right order? Do you happen to know which should be done first as far as installing recovery and removing said file?
Click to expand...
Click to collapse
Woops, I should have read more carefully. It's best to remove the file first and then flash the recovery.img, or else the script will install the stock recovery on boot. That would make stock recovery the current one on the phone at the time of the script getting deleted.
I would double check and make sure /system/etc does not have install-recovery.sh. If it is not there, then proceed to the fastboot steps and reflash the recovery.img again. It should stick this time.
@Ghost, yes i deleted the file multiple times however i didn't find the /system/etc folder on the Internal Storage. however I found the install-recovery.sh file under /etc folder. The thing i observed that whether i flash it with a new CWM or not if i reboot the phone then it was created by itself.
@Live4nyy, Thanks for your suggestion, I could able to install CM7 now and it looks awesome good so far, but looks like i need to install Google Apps separately to access the APP market, am I right?
The only thing that happens to me is, it allowed me to go to Recovery only ONCE after i Flashed it thru ROM Manager, if i exit out of recovery without doing anything then next time tried to go to Recovery, it will struck at the same old Android screen and i had to flash it again. But Many thanks for suggesting to flash it thru ROM Manager.
Now with CM7, under ROM Manager (I guess this comes default with CM7) I see there is no version listed under "Flash Clockworkmod Recovery" and it says i must have to install it in-order to Flash and restore ROMs, do i need to do that? I can go to Recovery mode after reboot without any issues. Please Advise.
------
Jhakash
jhakash said:
@Ghost, yes i deleted the file multiple times however i didn't find the /system/etc folder on the Internal Storage. however I found the install-recovery.sh file under /etc folder. The thing i observed that whether i flash it with a new CWM or not if i reboot the phone then it was created by itself.
Click to expand...
Click to collapse
I just checked out my girlfriend's stock, locked, unrooted Atrix and she actually has install-recovery.sh in both /etc and /system/etc. Her file manager does not alphabetize anything in either folder, so I almost overlooked the second one.
If you're already on CM7, then you probably won't need to worry anymore. They have an entirely different set of start up scripts in that folder. Welcome to the community!
At this point I do not know enough to help you any further with this issue. All I knew about is the file that needs to be removed that @ghost_og has mentioned. But if you can flash it from RomManager and access CWM from there as well then I guess that's a good enough workaround for now.
Does anyone else have any idea why the stock recovery cannot be removed?
jhakash said:
@Live4nyy, Thanks for your suggestion, I could able to install CM7 now and it looks awesome good so far, but looks like i need to install Google Apps separately to access the APP market, am I right?
The only thing that happens to me is, it allowed me to go to Recovery only ONCE after i Flashed it thru ROM Manager, if i exit out of recovery without doing anything then next time tried to go to Recovery, it will struck at the same old Android screen and i had to flash it again. But Many thanks for suggesting to flash it thru ROM Manager.
Now with CM7, under ROM Manager (I guess this comes default with CM7) I see there is no version listed under "Flash Clockworkmod Recovery" and it says i must have to install it in-order to Flash and restore ROMs, do i need to do that? I can go to Recovery mode after reboot without any issues. Please Advise.
------
Jhakash
Click to expand...
Click to collapse
I am good to go now, everything seems to be functioning well after flashing CM7 ROM, no more recovery issues, and the Stock recovery is gone now.
Appreciate for all the info you guys provided, it helped a lot. Have a great day and Merry Christmas.
Regards
Jhakash
Related
Hi.
While trying to upgrade my tablet to a later version of Android, something borked the bootloader. The tablet boots fine to a bare ICS (no gapps, but ROM MANAGER installed, though it does nothing but hang), but trying to boot into recovery mode hangs it (black screen with android robot, OEM info).
I can install apks to the tablet. I have installed ADB on my PC and it sees my tablet.
Where do I go from here ?
I have no clue
- what exact file(s) I need (my tablet is an Ainol novo8 advanced)
- where I need to put them
- what the commands are to do that
- it should be rooted (the superuser app aloows me to grant su privileges to apps)
Any help that can bring my tablet back to life would be very welcome.
Olivier
obarthelemy said:
Hi.
While trying to upgrade my tablet to a later version of Android, something borked the bootloader. The tablet boots fine to a bare ICS (no gapps, but ROM MANAGER installed, though it does nothing but hang), but trying to boot into recovery mode hangs it (black screen with android robot, OEM info).
I can install apks to the tablet. I have installed ADB on my PC and it sees my tablet.
Where do I go from here ?
I have no clue
- what exact file(s) I need (my tablet is an Ainol novo8 advanced)
- where I need to put them
- what the commands are to do that
- it should be rooted (the superuser app aloows me to grant su privileges to apps)
Any help that can bring my tablet back to life would be very welcome.
Olivier
Click to expand...
Click to collapse
If you can still use ADB your tablets bootloader is likely not messed up, it sounds like you booted the tablet into fastboot mode not recovery. To get into recovery you can enter it by holding a key combination the most common combination is holding volume up plus the power button at the same time. If that doesn't work from ADB you should be able to get into recovery by running the command:
Code:
adb reboot recovery
Also ROM manger doesn't always work right with every device so I would recommend just uninstalling ROM Manager for now. If it is booting fine into bare ICS then your tablet should be ok, if your looking for Google Apps for ICS they can be found here http://cmw.22aaf3.com/gapps/gapps-ics-20120317-signed.zip. Let me know if you still have questions .
Sent from my SCH-I535 using xda premium
Thanks a lot for your answer.
I'm sorry I didn't describe the issue well: I can no longer access the recovery mode.
I used to get to it by cold-booting the tablet holding Vol+ and Power. I used that to install ICS, gaps, powertools and 3D tools as described in http://forum.xda-developers.com/showthread.php?p=36059461#post36059461. The first package (recovery CWM) failed to installed because it was unsigned), the others installed, but in the end it seems I only got ICS: I have no gapps.
Now doing Vol+ and Power only gets me to the boot screen (a green android with OEM info, on a black background). Your "adb reboot recovery" does the same. I can only exit that screen by a hard reset.
During a normal boot, that screen flashes by for a couple of thesconds, then another, then the ICS colorful boot animation.
I have no clue how the recovery boot process works. I'm guessing it's reading a file of the internal Flash, and that file or dependencies got corrupted or partly overwritten by one of the packages I installed ? I'm not even sure if CWM recovery replaces the default recovery mode, or if it chains right after it ? I do have a supposedly-working CWM recovery .zip from the authors of the CM10 hack, as well as the "original" files listed here: http://forum.xda-developers.com/showpost.php?p=31089682&postcount=286 (official images from an out-of-the-box, unhacked tablet).
PS: the recovery mode I used to have was very rustic, only taking "update.zip" as an input, so when I did the update I had to go back and forth renaming the first package to "update.zip", applying it, renaming it "update1.zip, then on the the second package, etc, etc... It said Android System Recovery (3e), so maybe 3e was the version.
last but not least, if I could at least get the gapps onto the tablet, even w/o fixing the recovery mode, it would be very useful. I can install apks, or follow instructions to do it via adb ?
obarthelemy said:
Thanks a lot for your answer.
I'm sorry I didn't describe the issue well: I can no longer access the recovery mode.
I used to get to it by cold-booting the tablet holding Vol+ and Power. I used that to install ICS, gaps, powertools and 3D tools as described in http://forum.xda-developers.com/showthread.php?p=36059461#post36059461. The first package (recovery CWM) failed to installed because it was unsigned), the others installed, but in the end it seems I only got ICS: I have no gapps.
Now doing Vol+ and Power only gets me to the boot screen (a green android with OEM info, on a black background). Your "adb reboot recovery" does the same. I can only exit that screen by a hard reset.
During a normal boot, that screen flashes by for a couple of thesconds, then another, then the ICS colorful boot animation.
I have no clue how the recovery boot process works. I'm guessing it's reading a file of the internal Flash, and that file or dependencies got corrupted or partly overwritten by one of the packages I installed ? I'm not even sure if CWM recovery replaces the default recovery mode, or if it chains right after it ? I do have a supposedly-working CWM recovery .zip from the authors of the CM10 hack, as well as the "original" files listed here: http://forum.xda-developers.com/showpost.php?p=31089682&postcount=286 (official images from an out-of-the-box, unhacked tablet).
Click to expand...
Click to collapse
obarthelemy said:
PS: the recovery mode I used to have was very rustic, only taking "update.zip" as an input, so when I did the update I had to go back and forth renaming the first package to "update.zip", applying it, renaming it "update1.zip, then on the the second package, etc, etc... It said Android System Recovery (3e), so maybe 3e was the version.
Click to expand...
Click to collapse
obarthelemy said:
last but not least, if I could at least get the gapps onto the tablet, even w/o fixing the recovery mode, it would be very useful. I can install apks, or follow instructions to do it via adb ?
Click to expand...
Click to collapse
The recovery you are referring to is to the standard Android 3e recovery it is included in every version of Android, and will always be like that unless you install a custom recovery such as CWMR and or TWRP. As a general rule you should never install a custom ROM without having a custom recovery image installed first, essentially all the stock 3e recovery is good for is installing OTA updates and preforming a basic factory reset of your phone. You should try and fix your recovery before going any-further, you can sign the un-signed zip by using this tool. Overall, I would focus on trying to fix the recovery to prevent any further damage to your tablet and so that way you have a simple way to recover from anything that might go wrong when flashing ROMs, mods, and other zip files.
issue with the uImage linked
The uImage linked on the download pages for the CM10 and CM9 version ends in ".*"
I have no clue what the normal extension should be; replacing that *.zip doesn't work. Is the file bad, or am I just too clueless about what to do with it ?
Ok so the question is:
1- which "recovery mode" file should I install on my tablet, especially since the mod author's ones seem flaky
2- how do I do that via ADB since my tablet no longer seems to have a working "recovery mode".
I'm sorry to hassle you with those questions... I've looked around, I can't find info nor files I'm confident about ?
Tried everything for past 3 days, I cannot get Root access.
1) Bootloader unlocked
2) Activated Developer options
3) downloaded Su
4) Flashify or such other options don't work.
5) Also installed Minimum ADB & Fastboot, renamed recovery file, (and I believe also installed the TWRP).
Still can't get to the option of Install Recovery, Take Backup of Stock ROM or Data.
Tried Vol up + Power button, but there is no option to install (despite having SU in a memory card). The only options I get ( on a touch sensitive screen) are to test the phone on some criteria (technical terms I can''t remember) along with an option for Chinese. The options on the screen were Fastboot, download, recovery (and 1 more I can't remember currently)..
I suppose I have to choose Fastboot, and then install TWRP (I renamed the img file as recovery.img before installing it through a cmmand prompt (run as administrator).
Indiguns said:
Besides, I was stuck at the penultimate step, and no answer I saw, or youtube videos I watched helped. I have posted at two other places (at the right places) within this forum as well, and would request alecxs, and such members to be more helpful when they come across such a query, than call names/ spam.
Click to expand...
Click to collapse
i know it may frustrating, maybe next time just post a link to your thread.
as @narshi shukla mentioned, you have to initial boot in recovery from fastboot (btw there is no need to flash, just booting is required at this time)
have you downloaded the right twrp image, check the size of your file? you can alternative download from the mentioned support thread
did you read the note?
"Note many devices will replace your custom recovery automatically during first boot."
this means your stock recovery will maybe flashed back over twrp right after reboot. you have to repeat the steps each time, until you have successful entered into twrp recovery.
once in twrp recovery, you have to select the SuperSU.zip from external sd card. press the "install" button and select file. if file is not visible, go back and press the "mount" button, make sure external sd card is mounted. you can use a USB-OTG-Adapter and mount a USB-Stick as well.
go back to install and select the zip file, swipe to confirm flash. if flashing fails, goto "Advanced" and select "copy log to SD". you can upload the recovery.log file here for further analysis
Indiguns said:
Tried everything for past 3 days, I cannot get Root access.
1) Bootloader unlocked
2) Activated Developer options
3) downloaded Su
4) Flashify or such other options don't work.
5) Also installed Minimum ADB & Fastboot, renamed recovery file, (and I believe also installed the TWRP).
Still can't get to the option of Install Recovery, Take Backup of Stock ROM or Data.
Tried Vol up + Power button, but there is no option to install (despite having SU in a memory card). The only options I get ( on a touch sensitive screen) are to test the phone on some criteria (technical terms I can''t remember) along with an option for Chinese. The options on the screen were Fastboot, download, recovery (and 1 more I can't remember currently)..
I suppose I have to choose Fastboot, and then install TWRP (I renamed the img file as recovery.img before installing it through a cmmand prompt (run as administrator).
Click to expand...
Click to collapse
I had the same problem, to fix it download twrp-k5-3.0.2-r2_shreps.img instead of twrp-k5-3.0.2-r1_shreps.img.
Indiguns said:
Tried everything for past 3 days, I cannot get Root access.
1) Bootloader unlocked
2) Activated Developer options
3) downloaded Su
4) Flashify or such other options don't work.
5) Also installed Minimum ADB & Fastboot, renamed recovery file, (and I believe also installed the TWRP).
Still can't get to the option of Install Recovery, Take Backup of Stock ROM or Data.
Tried Vol up + Power button, but there is no option to install (despite having SU in a memory card). The only options I get ( on a touch sensitive screen) are to test the phone on some criteria (technical terms I can''t remember) along with an option for Chinese. The options on the screen were Fastboot, download, recovery (and 1 more I can't remember currently)..
I suppose I have to choose Fastboot, and then install TWRP (I renamed the img file as recovery.img before installing it through a cmmand prompt (run as administrator).
Click to expand...
Click to collapse
Use Magisk for Rooting. It is the best. Make sure you have installed TWRP. You can use KingoRoot or KingRoot app, if your Android version is 2.2 , 2.3 , 4.0, 4.3, 4.4, 5.0
https://youtu.be/46_ZILSewIo?t=201
This is basically a copy of my Z380M TWRP thread adopted for the ZenPad 10. I decided to start a new one since the OP of justshaun's original recovery/rooting thread has gone stale, even as I had posted several new releases of TWRP over the months. Its instructions are also a little outdated. I've also compiled a version for the new Z301M(F) models and needed a place to post it. This is where I will be posting TWRP updates from now on.
In addition to this thread, referring to the Z380M TWRP thread and the original Z300M thread (links above) may be helpful. These models share the same hardware and software base, so most things that apply to one tablet also apply to the others.
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 or Linux PC
SP Flash Tool version 5.1532 (only this version will bypass security checks)
MediaTek VCOM drivers (available through Windows Update)
ZenPad 10 scatter file for SPFT, attached (choose the one for your tablet)
Recovery image, attached (choose the one for your tablet)
ZenPad Z300M, Z301M or Z301MF tablet upgraded to Android N
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 10.
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 for your device (twrp-3.2.1-0-z30*m.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-z30*m.img
Once inside TWRP, flash twrp-3.2.1-0-z30*m.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". On the Z301M/Z301MF, that option is labeled Factory Reset. 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.
WARNING 2: Make sure you use the correct scatter file for your device (i.e. don't mix up the Z300 and Z301 files). For the initial flash, there is no check for scatter file correctness. If you use the wrong one, SP Flash Tool will alter and lock your GPT to that scatter file layout, possibly bricking your device. It will not be easy to restore it. Flashing with the correct scatter file later on will not work because Flash Tool will not allow you to use a different file than the one you used initially.
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
SP Flash Tool v5.1532
Z300M Scatter file for all storage sizes (right click, Save link as...) -- do not use for other models
Z300M TWRP 3.2.1-0 image -- updated March 15, 2018
Z301M(F) series Scatter file for all storage sizes (right click, Save link as...) -- do not use for Z300M or other devices
Z301M TWRP 3.2.1-0 image -- updated March 13, 2018
Z301MF TWRP 3.2.3-0 image -- updated August 29, 2018
Development and experimental files
Source code
P.S. The thanks button doesn't bite.
Heya, thanks for the new thread..
Stupid question(coming from Samsung flashing)
Ive got Zenpad S3 10 P027, is this TRWP not ideal for this?
Currently, have some su (root) issues. Recovery shows Android icon chest with ! and says "No Command"
When running su in Terminal ADB via PC, says command not recognized.
Looks like I need to reflash recovery. When in TRWP (launched via fastboot boot twrp on PC) I flashed stock recovery but had system mounted read only. Could that be the problem?
Bro, I think you need to do some more homework on root, su, dm-verity, mods, etc. and read the instructions more carefully before applying these hacks. You are making a lot of simple mistakes and ending up shooting yourself in the foot for it. I don't think there's anything wrong with the Z500 TWRP. It can handle installing the stock firmware just fine. The problem is elsewhere. The unlock tool also works fine in TWRP as well in my testing.
The No Command screen is normal. That's been answered many times... you need to hold power+vol. up (or down) to get to the menu. There is no way the stock recovery image can be broken and still boot up.
The su thing, IDK what the problem is, but I'm sure if you install Magisk Manager and make your own patched image from your currently installed firmware, and fastboot-boot with it, you will have su functionality. Just like what it says in the unlock tool instructions.
Lastly and most important, never mount system in read-write mode, as I've repeated several times and exactly as it says in the directions:
7. At the TWRP welcome screen, do not select to modify the system partition and touch Keep System Read-only instead. Doing otherwise will render your tablet unbootable.
8. Mount system in TWRP (in read-only mode)
Click to expand...
Click to collapse
The only time you can mount it in read-write mode is when you are absolutely sure you have disabled dm-verity in your boot image.
I've successfully installed TWRP on Z301M using the instructions from the first post, but then I somehow managed to lose the system. Yes, I should have backed up like the OP suggests.
I thought I should be able to reinstall the original firmware downloaded from Asus (e.g. UL-ASUS_P028_1-WW-3.3.12.0-user.zip) but both the 'adb sideload' method and the TWRP failed to install that firmware zip. My device looks bricked. The only thing I can do is to boot into TWRP (I actually need to select Factory Reset on the bootloader screen to get into TWRP). The folder 'system' is empty.
Can anyone suggest what I am doing wrong when trying to restore the Asus firmware?
When I try to sideload the zip, setting TWRP in the sideload mode, the computer begins uploading but after a few seconds gives the message "Total xfer: 0.01x" and stops, while Android errors with "set boot part fail. can not open misc-sd".
When I install the firmware zip from TWRP it also starts installing fine but shortly gives the same error "set boot part fail. can not open misc-sd".
Thanks
@ahacker, first of all, thank you for the feedback on the Z301M platform. You are literally the first person to have said anything about that version of TWRP.
To see the files on system, you first have to mount the system partition. Did you do that? If not, I suggest mounting it read-only. If there was any corruption on it, then reinstalling the firmware should have fixed it. The "misc-sd" errors are normal. Pretty sure they happen on stock recovery too. The stock firmware does not have dm-verity enabled, so letting TWRP modify system to prevent overwriting recovery should not have caused any problems.
At which point did it stop booting? Also, did you use the scatter file from first post? And can you tell me if the touch screen works fine in TWRP on your tablet?
I'm not sure what the deal is with adb sideload. I don't think I've ever actually tried it....
diplomatic, thanks for replying!
diplomatic said:
[MENTION=4776997]
To see the files on system, you first have to mount the system partition. Did you do that?
Click to expand...
Click to collapse
I do mount the system partition. It appears empty. When I reboot into system TWRP says that the OS is not installed.
I don't remember the details of how I lost the system partition. First time I entered into TWRP it asked for a password, probably to mount some partition. I pressed cancel or something. Then I might have cleaned the caches. But I am sure I haven't wiped system. I might have pressed Factory Reset somewhere, because I don't have any data yet on the new tablet.
I would indeed try to mount the system read only. This is not the first Android system I rooted (maybe fifth), and I was always able to restore the system either from sideload or recovery. But here it seems Asus is making us jump extra hoops to do that.
diplomatic said:
[MENTION=4776997]
Reinstalling the firmware should have fixed it.
Click to expand...
Click to collapse
That seems to be my main problem now. I cannot reinstall the Asus firmware. It may look like I might be installing a wrong version, but I am positive that I have Z301M tablet. This is what I bought and what the boot-loader says. I download Z301M firmware from the Asus website (e.g.). So it must be a correct firmware.
diplomatic said:
[MENTION=4776997]
The "misc-sd" errors are normal. Pretty sure they happen on stock recovery too. The stock firmware does not have dm-verity enabled, so letting TWRP modify system to prevent overwriting recovery should not have caused any problems.
Click to expand...
Click to collapse
Thank you for the information.
diplomatic said:
[MENTION=4776997]
Also, did you use the scatter file from first post? Does the touch screen work fine in TWRP on that tablet?
Click to expand...
Click to collapse
Yes. I found that to be the only scatter file that worked. I tried scatter.txt from the firmware zip, but the Flash Tool refuses tio pick it up. TWRP seems to be working fine with touches working as expected.
diplomatic said:
[MENTION=4776997]
I'm not sure what the deal is with adb sideload. I don't think I've ever actually tried it....
Click to expand...
Click to collapse
This is the unbricking method described here. It probably does the same thing as the "Install Zip" from recovery, because the errors that both methods give are the same.
---------- Post added at 01:19 AM ---------- Previous post was at 12:57 AM ----------
Now system refuses to mount
ahacker said:
I don't remember the details of how I lost the system partition. First time I entered into TWRP it asked for a password, probably to mount some partition. I pressed cancel or something. Then I might have cleaned the caches. But I am sure I haven't wiped system. I might have pressed Factory Reset somewhere, because I don't have any data yet on the new tablet.
Click to expand...
Click to collapse
Er, the password should have been for decrypting your userdata. If you didn't have one set up, there might be something wrong there.... Or possibly just unformatted.
ahacker said:
That seems to be my main problem now. I cannot reinstall the Asus firmware. It may look like I might be installing a wrong version, but I am positive that I have Z301M tablet. This is what I bought and what the boot-loader says. I download Z301M firmware from the Asus website (e.g.). So it must be a correct firmware.
Click to expand...
Click to collapse
Yeah, that has to be the right one. The installation script has to match the model name reported by the recovery. Otherwise it would simply abort.
ahacker said:
Yes. I found that to be the only scatter file that worked. I tried scatter.txt from the firmware zip, but the Flash Tool refuses tio pick it up. TWRP seems to be working fine with touches working as expected.
Click to expand...
Click to collapse
Great! Guess my kernel patch was on the dot and the partition layout has not changed from the Z300.
ahacker said:
This is the unbricking method described here. It probably does the same thing as the "Install Zip" from recovery, because the errors that both methods give are the same.
Click to expand...
Click to collapse
When you installed the zip, did you unmount system completely? BTW, when you mentioned the errors, the installation does keep going for like 5 to 10 minutes afterwards, right?
If you still can't resurrect it, please post or send me the recovery & kernel log that has your installation attempt.
diplomatic said:
When you installed the zip, did you unmount system completely? BTW, when you mentioned the errors, the installation does keep going for like 5 to 10 minutes afterwards, right?
Click to expand...
Click to collapse
I've tried both ways, with and without system mounted, a few times. The installation would fail after something like 5 seconds.
diplomatic said:
If you still can't resurrect it, please post or send me the recovery & kernel log that has your installation attempt.
Click to expand...
Click to collapse
I think I am giving up on this cheap tablet. I cannot even format it in the Flash Tool: it says "To format code area is forbidden on this phone". Asus is forbidding too much for me to ever buy it again. Attached the logs.
Thanks, diplomatic
OK, found the problem. Check your PMs, ahacker.
diplomatic said:
OK, found the problem. Check your PMs, ahacker.
Click to expand...
Click to collapse
I have replied (twice), but the reply does not appear in my Sent Items. I hope it has reached you. If not, I'll paste the reply here, if you don't mind.
i not understand... i have Asus ZenPad 10 LTE Z301MFL.. a root method has been released ???
@diplomatic
Would this be compatible with Z0310M ? can't find anything for this damn model...
Hi, NeBouse,
Are you sure you have the correct information? It looks like just a misspelling of Z301M, aka P028....
I have z301m.
One thing that was a surprise for me is that the TWRP recovery flashed with the method described in the original post does not stick. You have to flash it each time you use it. If you are like me this information is important, because the original recovery plainly wipes your data without asking or warning.
After you have flashed TWRP on the device, to go to the recovery mode you have to chose "Factory Reset" in the bootloader. Then it will complain about wrong OS, which is the sign that flashing TWRP worked; choose 'yes'. The first thing you should do in TWRP is a ful nandroid backup. (Not listening the OP's advice about backing up when Installing TWRP with a wrong scatter file almost cost me the device. Thankfully diplomatic managed to remotely fix my problem, probably spending a lot of his personal time. The scatter file in the original post is a correct one now.)
Creating a nandroid backup in TWRP takes unusually long time, I even once decided that it hanged. Taking long time, like 10-30 minutes, for a full backup is normal.
Asus Z300M , Magisk 16.3 (beta) and FW 5.3.19 WW now works!
z301m, WW-3.3.12.0 firmware
For rooting I've installed in TWRP Magisk v15.3 (diplomatic warned against 16.x, someone else against 15.4) - link.
Installed in TWRP xPosed framework 88.2 - link, and xPosed Installer apk from within Android - link.
So far, so good.
What I've found is that TWRP seems to have problems with external sd cards (lots of fs corruption). I found it safer to unmount by hand by unticking the sd card checkbox in "Mount". Not very conclusive about this though.
Thanks, ahacker. Good feedback. Although to be fair, I didn't say to avoid Magisk 16.x. I said 16.0. I'm pretty sure whatever bug it had is already fixed in the latest version.
Now that you've installed root, TWRP will stick around on the emmc. The stock recovery only gets installed if you have the original unpatched boot image on it. I mean, this is not unique to these devices. That's been standard Android functionality since some 4.x or 5.x version. And this is essentially what's in the warning on the OP.
The backup I'm talking about in the installation method is done with the SP Flash Tool readback function. That will pull the partition tables and your device's "metadata" that's unique to your unit. I don't think nandroid covers that...
Oh, and what is this SD corruption you're talking about? What file system is it formatted in? Have you checked your card for errors in Windows?
Asus releases so many difference Z301M model, so I am curious if this also works on Z301MF model?
Notice Z300MF has the MTK8163BA (or MTK8163A?) CPU model while Z301M uses : 8163B
Anyone tested that already? Thanks.
my zenpad 10 has frp lock. it this a solution to remove the frp lock?
Pls help how i flash original software via fastboot ?????
Hey guys,
I already soft bricked my device (I think) -.- I rooted it with the patched boot image and accidently installed a magisk module which caused a boot loop.
I booted into TWRP and didn't read that for now we can't mount the important partitions, so there went that. I rebooted to stock recovery and erased my complete device (factory reset + userdata) and now it bootloops into the bootloader.
Can't boot stock recovery or ROM.
Is there any chance to recover it with the current tools we have or do I have to wait for a fully working TWRP?
Any tip is appreciated
Is this topic something you can work with?
https://forum.xda-developers.com/7t-pro/development/recovery-oxygen-os-stock-recovery-adb-t3991865
MarkSnijders said:
Is this topic something you can work with?
https://forum.xda-developers.com/7t-pro/development/recovery-oxygen-os-stock-recovery-adb-t3991865
Click to expand...
Click to collapse
Thanks for the hint, but no chance. After flashing the recovery and reboot, the 7t pro always reboots to bootloader :-\
Edit: Could switch the boot slot and was able to enter recovery. Tried the modified one with adb function, but sideloading a rom is not possible adb: sideload connection failed: closed
I think I have to wait for TWRP
dre-z said:
Thanks for the hint, but no chance. After flashing the recovery and reboot, the 7t pro always reboots to bootloader :-\
Edit: Could switch the boot slot and was able to enter recovery. Tried the modified one with adb function, but sideloading a rom is not possible adb: sideload connection failed: closed
I think I have to wait for TWRP
Click to expand...
Click to collapse
Try this:
- Reboot to bootloader (If not possible, hold "Volume Down" & "Powerbutton" to boot into recovery, from there select "Boot Fastboot")
- Open CMD and type "fastboot flash boot boot.img" (I attached the 7tPro AA Boot.img)
##EDIT##: Well, unfortunately I'm not allowed to post extern links, so you have 2. options. Somewhere here in the Opt7tPro threads, some guy posted a link where he uploaded the stock boot image. Should be found here https://forum.xda-developers.com/7t-pro/help/rooting-oneplus-7t-pro-t3983533/page2 (scroll down ). Option 2, you downlaod the 7T OTA from OP website and extract the payload.bin with the programm "payload_dumper-win64". This will extract a more or less working boot image..
Your phone should then be able to boot normally again.
If it does, you will probably find out, that your WiFi, Speakers & Camera won't work.
Don't worry, this is because you maybe need the BA boot.img.
Then there are to options.
1. You wait until OP releases the original files on their website, as they did with the 7t
2. You go to "Settings", "System" & "Factory Reset", to reset your phone. (By now, this is the only way to fix the problem, so you can use the patched boot again)
If you choose option 2, after the "installation" screen, where it asks to enter your language, you must boot your phone into fastboot again.
Then you can flash the patched boot image again and your phone should work as normal
I was on same situation, i planned to root, but not found really 7T PRO rom, 7T ot 7 PRO has totally different ROMs, so i made a big mistake, to flash different rom. Phone stuck in boot loop. After 1.5 day google searching, i found one, that can bring back phone to live. I found a fresh 7T PRO rom, and simply flashed back, it booted, and finally everything's works good. Must to download fresh factory rom: https://androidfilehost.com/?fid=4349826312261606254, unzip it to any folder, start your phone in fastboot mode, plug in usb cable, (other eng plug to PC) and then simply do double click at the unzipped folder to flash all.bat file. You will get some errors, it's totally normal. Within 4-5 minutes your phone will works again. Hope it will work at you.
You, my fellow xda guys, are amazing!!! The solution with the stock boot.img helped me out!
Now I can start using my 7t pro after 3 days ^^
Hello everyone, my phone is samsung note 10 plus, I have twrp installed and rooted with magisk, I'm on Android 9, I somehow lost root, have no idea how, I'm very careful not to allow updates or google to install something there might affect my root.
when I go to magisk I'm getting the image that I've attached, when I click on install magisk, download the zip file and try to install it I get an an error as show in the 2nd image, saying unsupported/unknown image forma. I've also attached the log file. Is there any way for me to fix this without flashing the rom and start from scratch? Can I repair it somehow, maybe with TWRP?
Thank you all in advance
you have boot.img of the device?
i thought you can only install magisk in 2 way by flashing boot.img unto magisk or flashing magisk.zip unto TWRP as recovery partition
#edit how did you install magisk in the beginning? thats how you will install it again
there a chance you will get your device brick if you install magisk wrong way (A/B partition) but since you already install it previously just reinstall it back
Hmmm, where should I have the boot. Img you mean as if I backed it up on my pc? Or I can download it and use it?
Now I'm confused :/
Before i explain i don't take responsibility for any damages caused on your device if you decided to follow my tutorial .
So basically there's 2 way to install Magisk
• Image Patching - Basically this is what most people do they find stock boot.img and recovery.img for there devices
1. Copy the Stock boot.img or recovery.img to your device
2. Download and install the latest Magisk Manager
If you are patching a recovery image, manually check “Recovery Mode” in Advanced Settings!
Press Install → Install → Select and Patch a File, and select your stock boot or recovery image file
Magisk Manager will patch the image, and store it in [Internal Storage]/Download/magisk_patched.img
Now pull the magisk_patched.img with ADB:
adb pull /sdcard/Download/magisk_patched.img
Flash the patched boot.img or recovery.img to your device and reboot.
For most devices, here is the fastboot command:
fastboot flash boot magisk_patched.img or
fastboot flash recovery magisk_patched.img if you are patching a recovery image
Now you are rooted
•Custom Recovery - This is when you do not have Stock boot.img or recovery.img for your device
( High Chance Of Phone Getting Bricks )
1. Download and install the latest Magisk Manager
2. Download Magisk.zip (https://github.com/topjohnwu/Magisk/releases/) choose the Latest Release
3.Now reboot to recovery (TWRP, CWM ... ETC)
if you use stock recovery it should say "apply update via sdcard"
then just choose Magisk.zip
4. Now if you have TWRP just click Install and choose Magisk.zip
5. wait for the process
6. Now you are Rooted (hopefully xD :fingers-crossed
ineedroot69 said:
Before i explain i don't take responsibility for any damages caused on your device if you decided to follow my tutorial .
So basically there's 2 way to install Magisk
• Image Patching - Basically this is what most people do they find stock boot.img and recovery.img for there devices
1. Copy the Stock boot.img or recovery.img to your device
2. Download and install the latest Magisk Manager
If you are patching a recovery image, manually check “Recovery Mode” in Advanced Settings!
Press Install → Install → Select and Patch a File, and select your stock boot or recovery image file
Magisk Manager will patch the image, and store it in [Internal Storage]/Download/magisk_patched.img
Now pull the magisk_patched.img with ADB:
adb pull /sdcard/Download/magisk_patched.img
Flash the patched boot.img or recovery.img to your device and reboot.
For most devices, here is the fastboot command:
fastboot flash boot magisk_patched.img or
fastboot flash recovery magisk_patched.img if you are patching a recovery image
Now you are rooted
•Custom Recovery - This is when you do not have Stock boot.img or recovery.img for your device
( High Chance Of Phone Getting Bricks )
1. Download and install the latest Magisk Manager
2. Download Magisk.zip (https://github.com/topjohnwu/Magisk/releases/) choose the Latest Release
3.Now reboot to recovery (TWRP, CWM ... ETC)
if you use stock recovery it should say "apply update via sdcard"
then just choose Magisk.zip
4. Now if you have TWRP just click Install and choose Magisk.zip
5. wait for the process
6. Now you are Rooted (hopefully xD :fingers-crossed
Click to expand...
Click to collapse
Thank you very much.
OK, I tried method 2 and didn't work. I downloaded my stock firmware and I have the image file, I can try the first one to place the image in the root of the phone, patch the file with magisk and reflesh it with Odin?
Will I lose all my stuff on the phone by doing this? Thank you
i remember using odin back in 2012 for my samsung galaxy y i didn't know people still using that thing
i search your device on google and it said samsung provide the kernel for it ( https://www.xda-developers.com/samsung-galaxy-note-10-kernel-source-code/amp/ ) thats a good start for rooting your device try looking for it
also visit https://forum.xda-developers.com/galaxy-note-10 it is dedicated section for your device model which means all threads and post are for your device model
ineedroot69 said:
i remember using odin back in 2012 for my samsung galaxy y i didn't know people still using that thing
i search your device on google and it said samsung provide the kernel for it ( https://www.xda-developers.com/samsung-galaxy-note-10-kernel-source-code/amp/ ) thats a good start for rooting your device try looking for it
also visit https://forum.xda-developers.com/galaxy-note-10 it is dedicated section for your device model which means all threads and post are for your device model
Click to expand...
Click to collapse
Im already rooted....
Im having issues how to fix the root as i somehow don't have it any more and i don't want to reflash my rom if I'll lose all my stuff on the phone. Im looking how to fix the root.
drazenm said:
Im already rooted....
Im having issues how to fix the root as i somehow don't have it any more and i don't want to reflash my rom if I'll lose all my stuff on the phone. Im looking how to fix the root.
Click to expand...
Click to collapse
He's just saying to re-root it... If you lost root it's more than likely gone and you'll have to do whatever you did to gain root in the beginning. I constantly backup all my apps, data, pictures and everything to my little USB OTG thumb drive and to my laptop. I do this daily because many times a factory reset is what has to happen depending on what's going on. You can grab a Samsung micro sdcard 128 GB for $18-$19 or so online or thumb drives like I have a SanDisk 128gb.. it was $14. Just some thoughts for moving ahead so you don't have to go through this again. Lots of good suggestions here. If I were you I'd hit the "thanks" button on whenever took time to stop and search for answers to your issue. That's what we do here on xda. I could care less about racking up "thanks" count just throwing that out there so that you know..
Good luck on getting her all fixed. The note 10 is a real gem!
Sent from my marlin using XDA Labs
flash713 said:
He's just saying to re-root it... If you lost root it's more than likely gone and you'll have to do whatever you did to gain root in the beginning. I constantly backup all my apps, data, pictures and everything to my little USB OTG thumb drive and to my laptop. I do this daily because many times a factory reset is what has to happen depending on what's going on. You can grab a Samsung micro sdcard 128 GB for $18-$19 or so online or thumb drives like I have a SanDisk 128gb.. it was $14. Just some thoughts for moving ahead so you don't have to go through this again. Lots of good suggestions here. If I were you I'd hit the "thanks" button on whenever took time to stop and search for answers to your issue. That's what we do here on xda. I could care less about racking up "thanks" count just throwing that out there so that you know..
Good luck on getting her all fixed. The note 10 is a real gem!
Sent from my marlin using XDA Labs
Click to expand...
Click to collapse
I can re root it, that's not the problem, i can do it with the patched magisk boot image through Odin, im asking if that's gonna wipe off everything on my phone. Because i can't backup certain things without titanium backup, and titanium requires root access. Thank you for your help and everyone's else's im well aware and grateful for the attempts, suggestions etc.
no it's not gonna wipe anything thats why magisk is called "systemless" . It will essentially modify the system without actually modifying it.
if you flash magisk_patched.zip nothing noticeable will happen except you will have root access
all your installed application will be there
also i notice this some people actually copy magisk_patched.zip thats really bad idea you need to let Magisk generate it.
For example you have 2 phones same model and same build version .
You generate magisk_patched.zip on the phone A
then decided to copy magisk_patched.zip into phone B ofcourse it will still works
but since you just copy it and didnt let magisk generate it . It would not make backup for boot or recovery partition
if you uninstall Magisk on your phone B .There is really high super ultra mega chance of your phone getting bricks. Also it would not revert any changes done on the period while Magisk is installed
ineedroot69 said:
no it's not gonna wipe anything thats why magisk is called "systemless" . It will essentially modify the system without actually modifying it.
if you flash magisk_patched.zip nothing noticeable will happen except you will have root access
all your installed application will be there
also i notice this some people actually copy magisk_patched.zip thats really bad idea you need to let Magisk generate it.
For example you have 2 phones same model and same build version .
You generate magisk_patched.zip on the phone A
then decided to copy magisk_patched.zip into phone B ofcourse it will still works
but since you just copy it and didnt let magisk generate it . It would not make backup for boot or recovery partition
if you uninstall Magisk on your phone B .There is really high super ultra mega chance of your phone getting bricks. Also it would not revert any changes done on the period while Magisk is installed
Click to expand...
Click to collapse
Thanks for the help, please correct me if im wrong.
Im supposed to copy the AP . md5 file to the root directory of my phone, patch it with magisk, get the patched file, copy it on the pc, connect phone to the pc, get it into download mode, flash the patched file with Odin and that should be it?
Or maybe i can do it with twrp?
Any suggestions?
drazenm said:
Any suggestions?
Click to expand...
Click to collapse
1. Install the latest Magisk Manager
2. In Magisk Manager: Install → Install → Select and Patch a File and select the AP tar file.
Magisk Manager will patch the whole firmware file and store the output to [Internal Storage]/Download/magisk_patched.tar
3. Copy the patched file to your PC with adb pull /sdcard/Download/magisk_patched.tar. Do not use MTP as it is reported to corrupt files.
4. Reboot to download mode, and flash magisk_patched.tar as AP in Odin, together with the BL, CP and HOME_CSC files. Never flash only an AP file, as Odin can shrink your /data file-system if you do.
Important: Uncheck "Auto Reboot" in Options!
5. Magisk is now successfully flashed to your device! But there are still several steps before you can properly use the device.
6. We now want to boot into the stock recovery to factory reset our device.
Full data wipe is mandatory! Do not skip this step.
Press Power + Volume Down to exit download mode. As soon as the screen turns off, immediately press the combo key to boot to recovery (e.g. on the S10 it is Power + Bixby + Volume Up). Since we want to boot into stock recovery, continue pressing the volume up button until you see the stock recovery screen.
7. Use volume buttons to navigate through the stock recovery menu, and the power button to select an option. Choose Wipe data/factory reset to wipe the data of the device.
8. This time, we can finally boot to the system with Magisk. Select Reboot system now, and immediately press the combo key to recovery. After seeing the bootloader warning screen, release all buttons so it can boot to the system.
9. The device will automatically reboot for the first time it boots. This is completely normal and done by design.
10. After the device is booted up, do the usual initial setup. The following steps will need an internet connection.
11. Magisk Manager will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
12. Voila! Enjoy Magisk
credit to @Magisk github
you can read the full tutorial here https://github.com/topjohnwu/Magisk/blob/master/docs/install.md
ineedroot69 said:
1. Install the latest Magisk Manager
2. In Magisk Manager: Install → Install → Select and Patch a File and select the AP tar file.
Magisk Manager will patch the whole firmware file and store the output to [Internal Storage]/Download/magisk_patched.tar
3. Copy the patched file to your PC with adb pull /sdcard/Download/magisk_patched.tar. Do not use MTP as it is reported to corrupt files.
4. Reboot to download mode, and flash magisk_patched.tar as AP in Odin, together with the BL, CP and HOME_CSC files. Never flash only an AP file, as Odin can shrink your /data file-system if you do.
Important: Uncheck "Auto Reboot" in Options!
5. Magisk is now successfully flashed to your device! But there are still several steps before you can properly use the device.
6. We now want to boot into the stock recovery to factory reset our device.
Full data wipe is mandatory! Do not skip this step.
Press Power + Volume Down to exit download mode. As soon as the screen turns off, immediately press the combo key to boot to recovery (e.g. on the S10 it is Power + Bixby + Volume Up). Since we want to boot into stock recovery, continue pressing the volume up button until you see the stock recovery screen.
7. Use volume buttons to navigate through the stock recovery menu, and the power button to select an option. Choose Wipe data/factory reset to wipe the data of the device.
8. This time, we can finally boot to the system with Magisk. Select Reboot system now, and immediately press the combo key to recovery. After seeing the bootloader warning screen, release all buttons so it can boot to the system.
9. The device will automatically reboot for the first time it boots. This is completely normal and done by design.
10. After the device is booted up, do the usual initial setup. The following steps will need an internet connection.
11. Magisk Manager will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
12. Voila! Enjoy Magisk
credit to @Magisk github
you can read the full tutorial here https://github.com/topjohnwu/Magisk/blob/master/docs/install.md
Click to expand...
Click to collapse
Thanks so much for your help, but i just want to get root back on my phone as i had it rooted already, i dont want to wipe off everything and lose my stuff. There are things that i can only backup with titanium backup, which i can't use now without root privileges :/ can i repair root somehow?
how did you lose your root anyway?
your Android OS updated?
you can try restoring apps with titanium backup but i don't think it will restore Magisk being installed again and gaining root access
ineedroot69 said:
how did you lose your root anyway?
your Android OS updated?
you can try restoring apps with titanium backup but i don't think it will restore Magisk being installed again and gaining root access
Click to expand...
Click to collapse
I didn't do the update, but something did mess up the root aa you can see on the photos that I've attached at the beginning of the topic. I just want to reroot my phone again but not to loose all my current stuff on it.
if you have boot.img or recovery.img for your device you might not lose your stuff installing back magisk but i think you only have the whole firmware ".tar.md5" flashing thats is like factory reset for your phone
#edit i read about ".tar.md5" they say if you just extract it .It contains all stock .img file for your device such as boot.img, recovery.img , system.img ...etc
since i have too much free time can you upload the firmware ".tar.md5" of your device i will upload .boot.img and recovery.img for you
ineedroot69 said:
if you have boot.img or recovery.img for your device you might not lose your stuff installing back magisk but i think you only have the whole firmware ".tar.md5" flashing thats is like factory reset for your phone
#edit i read about ".tar.md5" they say if you just extract it .It contains all stock .img file for your device such as boot.img, recovery.img , system.img ...etc
since i have too much free time can you upload the firmware ".tar.md5" of your device i will upload .boot.img and recovery.img for you
Click to expand...
Click to collapse
thank you for taking your time to help me out, i appreciate it.
here is the link to the firmware file:
https://androidfilehost.com/?fid=6006931924117937015
inside are these files:
AP_N975FXXU1ASH5_CL16618471_QB25345699_REV01_user_low_ship_meta_OS9.tar.md5
BL_N975FXXU1ASH5_CL16618471_QB25345699_REV01_user_low_ship.tar.md5
CP_N975FXXU1ASH5_CP13587367_CL16618471_QB25409313_REV01_user_low_ship.tar.md5
CSC_OMC_OXM_N975FOXM1ASH5_CL16618471_QB25349308_REV01_user_low_ship.tar.md5
HOME_CSC_OMC_OXM_N975FOXM1ASH5_CL16618471_QB25349308_REV01_user_low_ship.tar.md5
ineedroot69 said:
if you have boot.img or recovery.img for your device you might not lose your stuff installing back magisk but i think you only have the whole firmware ".tar.md5" flashing thats is like factory reset for your phone
#edit i read about ".tar.md5" they say if you just extract it .It contains all stock .img file for your device such as boot.img, recovery.img , system.img ...etc
since i have too much free time can you upload the firmware ".tar.md5" of your device i will upload .boot.img and recovery.img for you
Click to expand...
Click to collapse
Any luck?
drazenm said:
Any luck?
Click to expand...
Click to collapse
sorry for late reply i'm kinda busy but to make it easier on my part (downloading 5GB file would take me 5 hours) can you just upload the following ?
AP_N975FXXU1ASH5_CL16618471_QB25345699_REV01_user_ low_ship_meta_OS9.tar.md5
BL_N975FXXU1ASH5_CL16618471_QB25345699_REV01_user_ low_ship.tar.md5
CP_N975FXXU1ASH5_CP13587367_CL16618471_QB25409313_ REV01_user_low_ship.tar.md5