Database Info

[Q] how do i bring back root on my i9023 ics 4.0.4

I have just updated my nexus s to the latest 4.0.4 update..now i want to bring back root access .. as we all know were going to loose root access if we updated. anyway i previously used this method http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ now im wondering if this also applies to 4.0.4 update and what is the best recovery to flash on this update?

The only thing i did was upgrade to 4.04, dont reboot but flash superuser, all clear, root is back.

[Q](solved) how do i bring back root on my i9023 ics 4.0.4
willemt158 said:
The only thing i did was upgrade to 4.04, dont reboot but flash superuser, all clear, root is back.
Click to expand...
Click to collapse
hmn... what i did was
i went to adb
open cmd
flashed recovery3101.img
after that i installed superuser using CWM recovery . if your using the stock recovery it will only show an error msg. didnt wipe anything ... all is ok and well hehehe cheers!

I have issue with CWM and Root. I've follow the guide here.
I manage to successfully do up to step 4 without error. After that, when I reboot the device, it have a message "android installing update". I installed titanium backup and it says no root access. Superuser is available. When I tried to update on Play "Update for Superuser could not be downloaded due to an error (941)"
I tried to go back to recovery, it is the stock recovery instead of CWM. I've updated my 9023 from 4.0.3 (stock non root) to 4.0.4 using CWM. I've installed superuser using CWM as well. But when I reboot the device, it went back to stock recovery. I've tried fastboot CWM, turn off, then turn back on to go recovery, it is using CWM. But when I reboot, and try to go back to recovery, it goes to the stock recovery.
Appreciate some help. Hope my explanation is clear.
Will

First try flashing the latest Superuser than reboot, then open rootexplorer
Rename "/system/etc/install-recovery.sh" to "/system/etc/install-recovery.sh.bak".
All Stock ROMs replace the recovery on each Boot if it isn't the stock one. Renaming this script stops that. After you do this, flash CWM one more time and it'll stick.
Thanks to harbb who helped me with the same isseu

not sure if this is legit... I found a few sites with the same tutorial but different backup apps same file download though... can anyone varify?
filename: Superuser-3.0.7-efghi-signed, from a mediafire download (/?57iroxlzh8bb5qi)
from tutorial: Root Nexus S with Android 4.0.4 ICS IMM76 Firmware, from androidlot.com
(sorry can't post link)
it just said to do a recovery from bootloader, no other tampering needed... was thinking of using it if it worked as I just did the Nexus S 19023 OTA update 2.3.6 - 4.0.4 found on this forum but wanted to root to use voodoo sound... first timer and dont want to mess around with roms or cwm... figure no harm rooting as Nexus S probably won't get anymore official updates

Signature verification failed
well i have tried to install the superuser from recovery (apply update from SDcard) but every time i try to install the zip file it gives me signature verification error .

Mansuur said:
well i have tried to install the superuser from recovery (apply update from SDcard) but every time i try to install the zip file it gives me signature verification error .
Click to expand...
Click to collapse
That means your not in CWM Recovery. You have to follow the guide and use fastboot to flash a custom recover. Thats why we use a custom recovery, to bypass the signiture check

so wats da final result?
in ics 4.04 how to flash cwm and root and install vodoo?

ended up using m.sabra's one click root and flash cwm tool (/showthread.php?t=1544940) worked a charm, downloaded voodoo sound plus so i didnt have to flash new kernel, putting music back on phone now (had to unlock bootloader) to see how it sounds
also used appbackup&restore, copied backup folder from sd to computer, used the root tool, redownloded appbackup&restore, copied folder back from computer to phone, allowed install from non market, reinstalled all apps
now have superuser and cwm and all my apps back

Hope this may help. it's the way a did it on my Nexus S
Download fastboot for Windows or Mac.
Make sure you have the Android SDK installed.
Download ClockworkMod Recovery.
Download the Rooted Su Binary for 4.0.4
Make sure you have the necessary drivers installed for your device
Put your device into Bootloader Mode (turn your device off, then hold Volume Up + Power).
Once in Bootloader Mode, type the following into your Command Window
fastboot oem unlock
You should now see a couple of lines go through on your Window.
Then Type the following:
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
Provided this went correctly (it should), you now want to cycle down to “Recovery” on your device using the Volume buttons and press Power to confirm. This should boot you into ClockworkMod.
Select Recovery again, navigate to “Mounts & Storage” and then to “Mount USB Storage”. Once this has been done, your SD Card should appear on your PC.
Copy the Rooted Su Binary you have downloaded to your SD Card, and then Unmount USB Storage on your device.
Navigate back to the main menu of ClockworkMod and select “Install zip from sdcard”, then “Choose zip from sdcard” and select the package you just copied across, and then confirm the installation. This should install the package and root your device.

Hey guys sorry i was on vacation, thats why it took me so long time to come back, anyways... here is the link of the step by step procedure on rooting your nexus s, this is what i followed, http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s-or-nexus-s-4g-new/
but what i did was ;
1. after updating i lost root
2. open adb tool
3. flash new recovery3101.img ( this is to replace default recovery from the stock ics 4.0.4)
4.then installed superuser from the new recovery that i installed ( CWM)
i wont go through all the details since , the link already explained that there....so cheers and hope this works for you , all the needed files is in the link also.

Mrbalders said:
Hope this may help. it's the way a did it on my Nexus S
Download fastboot for Windows or Mac.
Make sure you have the Android SDK installed.
Download ClockworkMod Recovery.
Download the Rooted Su Binary for 4.0.4
Make sure you have the necessary drivers installed for your device
Put your device into Bootloader Mode (turn your device off, then hold Volume Up + Power).
Once in Bootloader Mode, type the following into your Command Window
fastboot oem unlock
You should now see a couple of lines go through on your Window.
Then Type the following:
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
Provided this went correctly (it should), you now want to cycle down to “Recovery” on your device using the Volume buttons and press Power to confirm. This should boot you into ClockworkMod.
Select Recovery again, navigate to “Mounts & Storage” and then to “Mount USB Storage”. Once this has been done, your SD Card should appear on your PC.
Copy the Rooted Su Binary you have downloaded to your SD Card, and then Unmount USB Storage on your device.
Navigate back to the main menu of ClockworkMod and select “Install zip from sdcard”, then “Choose zip from sdcard” and select the package you just copied across, and then confirm the installation. This should install the package and root your device.
Click to expand...
Click to collapse
wow very detailed cheers man!

Glad to help, and hope you've got your Nexus back to root

deleted

deleted

ht2000 said:
These are two links showing two preview images.
https-://image.ibb.co/bHFrK5/Screenshot_20170821_082926.png
https-://image.ibb.co/dMJve5/20170821_082847.jpg
Notes:
Before you get started, you will need access to Developer options. Got to About phone on Settings and click on your Build number till you get a notification stating that you've gained access to this options.
After that, enable both OEM unlocking and USB debugging to unlock the bootloader and gain permission to transfer downloaded files from your PC to your phone via the charging cable.
If your software firmware is 6.0.1-01003, don't update your system to be safe since that I haven't tested installing TWRP on a updated firmware.
Tutorial:
To get started, you will need to download this .img file which contains a flashable TWRP 3.0.2-0 that is unofficially supported for the Alcatel Pop 4 and import it to your device.
https-://uplo.adfi.l.es.io/x.9h.18
In order to flash the TWRP .img image, you will need to gain access to temporary root and in order to do that, you'll need to install KingRoot. To install it, enable Unknown sources if disabled then visit the site below to download and install it.
https-://kingroot.net/
You should see something like this.
https-://ufile.io/491p5
Download SuperSU's Latest .ZIP file below (Should be V2.82 as of 21/08/17)
s.upersu.com/download
Its normal if your phone reboots during the process. Just make sure that you quickly unlock your phone and return to KingRoot to continue the process after your device has rebooted.
After you have successfully rooted your phone, you will need to install Flashify in order to flash the TWRP image I provided you with. The link to install Flashify is below.
https-://play.google.com/store/apps/details?id=com.cgollner.flashify
Since that the temporary root that came with KingRoot is very unstable with the Pop 4, be very gentle navigating through the phone for the time being or your device may reboot and you will need to reroot with KingRoot again.
Open the Flashify app, grant root permissions, go to Recovery image then click on choose a file. After that find the downloaded TWRP that I provided you with, click and it and select YUM! (Meaning yes) to flash TWRP. After it has flashed TWRP, it should give you the option to reboot into TWRP.
Once your booted into TWRP, swipe right to gain access to read and write privileges and make sure you check the box above so you don't have to do that again.
Click Wipe, Format Data then enter "yes" without the quotations of course then press the blue button on the bottom right of the on screen keyboard to format the device.
After the device is formatted go back instead of rebooting, press the on screen back button then install and find the SuperSU .ZIP you've downloaded then swipe right to flash. After flashed, clear cache then reboot.
After it has rebooted, set up the device as if it was new then after set up you should see that you've got SuperSU in your app list.
To access TWRP in the future, hold power button and up volume button till TWRP boot screen loads up.
I will upload a test video showing me using my rooted Pop 4 soon.
I have edited the links so they wouldn't be detected by xda since i'm not allowed to post any links as of right now since i'm using a new account.
Click to expand...
Click to collapse

MOD ACTION:
Thread closed at the request of the OP.

Infinix Zero 5/Zero 5 pro (X603) TWRP Recovery 3.1.1 With OTA Support

Touch is Working Now. (Finally) with OTA Support only for zero5 indian varient
Join Telegram group for further development : https://telegram.me/infinixzero5
This is Ported TWRP Recovery from a same Mt6757 chipset model. which i used to port it for our Infinix X603.
Thanx @topjhonwu for magisk.
Thanx for @majorkid for making OTA supportable
TWRP for non indian and global version for necessary changes. (Need to test)
Warning:-
I am not responsible for bricked devices.
Your warranty will void now. Do it at your own Risk.
Unlocking Bootloader
- Make sure your Bootloader is Unlocked. If already unlocked jump to how to flash.
Process to unlocking.
1. go to settings/about phone/build number (tap build no for 7 time now developer option available in settings)
2. go to developer option turn on usb debugging and OEM unlocking.
3. then go to pc download and extract and copy adb fastboot driver folder in Drive C. (or install form net.)
4. Go in fastboot folder which is copied to C. press and hold shift key on your key board and click right key on your mouse it will show option open cmd here or open power shell window here.
5. Click it, A cmd or power shell window will open.
type "adb devices" - it show some no of your device just give permission from your phone screen)
type "adb reboot bootloader" your phone reboot in bootloader mode.
type "fastboot oem unlock" follow onscreen instruction on phone, press volume + to confirm. thats it but it will erase all your data.
Reboot phone by pressing power button for 10 sec. setup it as temporarily.
Flashing of TWRP
1. Download the Latest TWRP Recovery Image and extract it (Attached). Use correct version for your device for OTA support.
For India (Indian) For Global (Global)
(Insert a SD card in your phone to take stock boot.img backup it will required for OTA in Future.)
2. Go in adb fastboot folder which is copied to C. copy twrp_recovery.img here then press and hold shift key on your key board and click right key on your mouse it will show option open cmd here or open power shell window here.
3. Click it, A cmd or power shell window will open.
4. Flash it via fastboot cmd (fastboot flash recovery Twrp_recovery.img) don’t use bracket.
It will flash recovery on your phone. Now type fastboot reboot in cmd window and press and hold vol+ button and hit enter.
Phone will reboot in twrp recovery.
Note : After flashing first time it will ask for password due to phone is encrypted.
a. just cancel it and allow to modify system by swiping arrow at down and select 2nd last option at right side then select globe icon on right and chose your language English.
(First take Boot.img backup Via backup option in TWRP in SD Card. (bcz internal storage shows 0 mb here at this movement.) It will use for OTA so save it.
b. then flash magisk manager.zip file attached here. (it will remove dm-verity and force encryption from boot.img) and give root access.
c. then go to Wipe and select format Data it will erase all data on your internal storage. remember it will erase your data in ext4 format so go to wipe advance select data and change file system to f2fs. Ext4 data not supported by kernel so you got loop to recovery so It must to repair data in f2fs.
d. Done Reboot to recovery and you got mounted storage.
Another Method.
- Flash it via SP flash tool. (use version 5.1744 recommended)
How to use SP flash tool :
Install Vcom media tek driver on your pc.
More detail and download available on following link
https://spflashtool.com/
IF ANYONE GOT LOOP IN BETWEEN TO RECOVERY MEANS PROCESS NOT FOLLOWED PROPERLY.NOT BOOTING PHONE JUST FLASH STOCK RECOVERY. YOUR PHONE WILL BOOT THEN DO PROCESS AGAIN.
OTA-
1. When ota available just download it. Don’t start flashing.
2. Location of OTA downloaded file in Root so use any root file explorer.
3. File can be found in :-
a. Root/cache/update.zip
b. Root/data/data/com.google.android.gms/app_download/update.zip
4. Copy file name is update.zip to your sd card or phone memory.
5. Reboot to recovery and flash first stock boot.img which you already taken backup and saved before when flashing twrp.
6. now flash update.zip via TWRP (dont reboot after flashing otherwise you will currept your system)
7. After flashing update.zip, first again take backup of your boot.img for future ota update.
8. After taking backup of boot.img flash magisk.zip and reboot. (If you did not flash magisk then your data again encrypted and u lose all data)
6. Done you are on latest version.
Note:- Always remember to flash magisk.zip at last before reboot.
OTA SUPPORTABLE TWRP Link for zero 5 global varient by @majorkid -
https://androidfilehost.com/?fid=890129502657578792
OTA SUPPORTABLE TWRP Link for zero 5 pro global varient by [MENTION=7078341]majorkid[/
https://androidfilehost.com/?fid=890129502657578807
Update: Last updated on 27/01/2018 (With almost all stock stuff with OTA support)

Thank you for your efforts I don't know why but it didn't work (i searched and downloaded alot and it's the only recovery that gave me a response but the screen was flipped and the touch was disabled, also the stock recovery is working well)

XDAdeveeloopers said:
Thank you for your efforts I don't know why but it didn't work (i searched and downloaded alot and it's the only recovery that gave me a response but the screen was flipped and the touch was disabled, also the stock recovery is working well)
Click to expand...
Click to collapse
flip screen was old but i updated it with working twrp. is it showing vernee mix 2 name on top?
can you send screen shot.
its working perfectly.
just match the zip size which you downloaded (if it is 13.23 mb then it is old)
download current version attached above is 15.31 mb in size.
Screen Shot is also updated
Let me know your success.............................

flipped screen fixed !
Ok, now it's not flipped but the touch is still disabled
again, thank you for your efforts. I've attached the screenshots. it tells me to enter the password but the touch is disabled and i couldn't type anything.

At this stage only cancle button will work. Dont type anything just press cancle button.
It shows next screen.
I chek if issue is there.

Cancle is not working too

XDAdeveeloopers said:
Cancle is not working too
Click to expand...
Click to collapse
just use it as temp. bcz after flash touch not working.
Touch is disabled in kernel for recovery partation by infinix.
for temp use cmd.
fastboot boot recovery.img
will update soon..........

when i connect my mouse via otg or flash it temporarily it works fine except that it shows that the internal storage is 0mb and when i try to install something it tells me that it's unable to mount /data as rw
also can you tell me how to get the password required in the first screen ?

XDAdeveeloopers said:
when i connect my mouse via otg or flash it temporarily it works fine except that it shows that the internal storage is 0mb and when i try to install something it tells me that it's unable to mount /data as rw
also can you tell me how to get the password required in the first screen ?
Click to expand...
Click to collapse
Read OP carefully. You need to format data partition completly first time and need to patch boot img via lazy flasher.
Showing 0mb bcz it is encrypted. You can use memory card.
If you want root then go for magisk root till recovery updated.

OK, now I removed the encryption, installed magisk and the root worked but when I try to install busybox and some other apps it doesn't work. When I try to install supersu zip it doesn't work (extracting ramdisk failure aborting) , isn't there any way to install supersu in order to get apps working correctly?

XDAdeveeloopers said:
OK, now I removed the encryption, installed magisk and the root worked but when I try to install busybox and some other apps it doesn't work. When I try to install supersu zip it doesn't work, isn't there any way to install supersu in order to get apps working correctly?
Click to expand...
Click to collapse
which busybox your trying and what error.
currently supersu have some error with new devices. which version you tried it should be 2.82 or above.

I downloaded SuperSU-v2.82-201705271822.zip
Busybox pro 61
MagiskManager-v5.4.3.apk

XDAdeveeloopers said:
I downloaded SuperSU-v2.82-201705271822.zip
Busybox pro 61
MagiskManager-v5.4.3.apk
Click to expand...
Click to collapse
Use busybox form playstore stericson.

I downloaded both free and pro versions of stericson's busybox and neither of them worked.
Also I downloaded supersu 2.82 and it also didn't work.

Finally the Touch is updated and working now.
I enabled touch in kernel which is disabled for recovery partition.

XDAdeveeloopers said:
I downloaded both free and pro versions of stericson's busybox and neither of them worked.
Also I downloaded supersu 2.82 and it also didn't work.
Click to expand...
Click to collapse
System is encrypted.
Use magiskmanager beta 14.5 or flash lazyflasher via twrp then one time you need to wipe data partition.
Always remember when you flash orignal boot.img you need to flash lazyflasher or magisk otherwise your system will become encrypted again.

Thank you, now touch is working perfectly <3

XDAdeveeloopers said:
I downloaded both free and pro versions of stericson's busybox and neither of them worked.
Also I downloaded supersu 2.82 and it also didn't work.
Click to expand...
Click to collapse
you can use ndk busybox from magisk app there is option download module.
But currently there is problem with module with this phone. the data partition is in F2FS format and its kernel is not handling f2fs properly.
TWO option for use magisk module.
1. wait for kernel update via infinix. or
2. format data partition as Ext4 from twrp.
Super su does not work correctly with f2fs currently.

But when I format data partition it resets my phone

XDAdeveeloopers said:
But when I format data partition it resets my phone
Click to expand...
Click to collapse
yes formatting data will reset it.

[GUIDE] Root Android Pie With Magisk

Frist You Must Unlock BootLoader
Second You Must Have Pc With Android platform tools (They Exist Also For MacOS And Linux)
BOOTLOADER UNLOCK
First thing to do: unlock the bootloader (if you didn't already do this, obviously). Smartphones with Android One are much easier to unlock compared to other Xiaomi phones with MIUI (where you have to ask for authorization and wait for weeks).
CAUTION: when you unlock the bootloader, the phone will reset, erasing all your saved data. Backup your data before unlocking.
1. Go to Settings > System > About phone > and tap many times on "Build number" until you unlock "Developer options".
2. Go back to the previous page, where you can find now "Developer options". Go there and enable the "OEM unlocking" option (and it's better to never disable this).
3. Now you can shutdown your phone, then turn it on while holding the "Volume down" button pressed. Release it when you see the Fastboot screen.
4. Now connect the phone with your PC via USB cable, open an administrative command prompt, move to the directory where the Android platform tools are placed and unlock the bootloader with the following command:
Code:
Code:
fastboot oem unlock
The phone will reboot, erasing all the data.
Now you unlocked your phone's bootloader and can continue to the next section
Download This https://mega.nz/#!3aZ3AICJ!YAHEVP5dQ2bgnV0_oDd3O4MBzdVt1qT_9HfqGWvVzCE
open an administrative command prompt, move to the Android platform tools directory and then write the following command:
Code:
Fastboot boot boot_rooted.img
If everything works the phone should boot normally. Open Magisk Manager and it should ask to install Magisk, if not you must tap on the "Install" button. Then choose "Install" > "Direct Install (Recommended)" to install Magisk on the phone, and reboot when finished.
HOW TO APPLY OTA UPDATES
IMPORTANT: OTA updates will work only if all the partitions on the smartphone are untouched. Magisk Manager can restore the original boot.img following this section of the guide, but if you tampered directly with the system partition (e.g. manually editing build.prop) or other partitions, OTA will refuse to install.
You can try to fix OTA updates without the need to flash the whole original fastboot ROM, by flashing only the tampered partitions (usually only "system") with the corresponding img file found inside the fastboot ROM zip. Check the "Troubleshooting" section of this guide for details.
12. When you know that a new OTA update is available and you want to install it, open Magisk Manager, and tap on "Uninstall" > "Restore Images" but very important: absolutely don't reboot the phone now!
Important note: Magisk Manager will restore the boot.img that was found on the phone while installing Magisk. If the boot.img was already non-vanilla (for example you flashed the boot.img with TWRP before installing Magisk), Magisk Manager will backup that modified version of boot.img, and when restored the OTA will not work, as that's not a vanilla boot.img.
13. Close Magisk Manager and go to "Settings" > "System" > "System update" and install the OTA update. After the update is downloaded, a two-stages update will begin.
14. When both stages of the update process completed, it will ask to restart: DON'T DO IT!. Open Magisk Manager again and tap on "Install" > "Install" > "Install to Inactive Slot (After OTA)" and after that you can tap on "Reboot".
After the reboot you will have the updated Android version with Magisk already working.
I'm 12 Years Old Don't Worry I Test It On My Mi A2 Lite Thanks
I Take Some Things From https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952

NourHazem I said:
Frist You Must Unlock BootLoader
Second You Must Have Pc With Android platform tools (They Exist Also For MacOS And Linux)
BOOTLOADER UNLOCK
First thing to do: unlock the bootloader (if you didn't already do this, obviously). Smartphones with Android One are much easier to unlock compared to other Xiaomi phones with MIUI (where you have to ask for authorization and wait for weeks).
CAUTION: when you unlock the bootloader, the phone will reset, erasing all your saved data. Backup your data before unlocking.
1. Go to Settings > System > About phone > and tap many times on "Build number" until you unlock "Developer options".
2. Go back to the previous page, where you can find now "Developer options". Go there and enable the "OEM unlocking" option (and it's better to never disable this).
3. Now you can shutdown your phone, then turn it on while holding the "Volume down" button pressed. Release it when you see the Fastboot screen.
4. Now connect the phone with your PC via USB cable, open an administrative command prompt, move to the directory where the Android platform tools are placed and unlock the bootloader with the following command:
Code:
The phone will reboot, erasing all the data.
Now you unlocked your phone's bootloader and can continue to the next section
Download This https://mega.nz/#!3aZ3AICJ!YAHEVP5dQ2bgnV0_oDd3O4MBzdVt1qT_9HfqGWvVzCE
open an administrative command prompt, move to the Android platform tools directory and then write the following command:
If everything works the phone should boot normally. Open Magisk Manager and it should ask to install Magisk, if not you must tap on the "Install" button. Then choose "Install" > "Direct Install (Recommended)" to install Magisk on the phone, and reboot when finished.
HOW TO APPLY OTA UPDATES
IMPORTANT: OTA updates will work only if all the partitions on the smartphone are untouched. Magisk Manager can restore the original boot.img following this section of the guide, but if you tampered directly with the system partition (e.g. manually editing build.prop) or other partitions, OTA will refuse to install.
You can try to fix OTA updates without the need to flash the whole original fastboot ROM, by flashing only the tampered partitions (usually only "system") with the corresponding img file found inside the fastboot ROM zip. Check the "Troubleshooting" section of this guide for details.
12. When you know that a new OTA update is available and you want to install it, open Magisk Manager, and tap on "Uninstall" > "Restore Images" but very important: absolutely don't reboot the phone now!
Important note: Magisk Manager will restore the boot.img that was found on the phone while installing Magisk. If the boot.img was already non-vanilla (for example you flashed the boot.img with TWRP before installing Magisk), Magisk Manager will backup that modified version of boot.img, and when restored the OTA will not work, as that's not a vanilla boot.img.
13. Close Magisk Manager and go to "Settings" > "System" > "System update" and install the OTA update. After the update is downloaded, a two-stages update will begin.
14. When both stages of the update process completed, it will ask to restart: DON'T DO IT!. Open Magisk Manager again and tap on "Install" > "Install" > "Install to Inactive Slot (After OTA)" and after that you can tap on "Reboot".
After the reboot you will have the updated Android version with Magisk already working.
I'm 12 Years Old Don't Worry I Test It On My Mi A2 Lite Thanks
I Take Some Things From https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
Click to expand...
Click to collapse
May i use this method on my a2 lite running android pie

ashikalone said:
May i use this method on my a2 lite running android pie
Click to expand...
Click to collapse
Instead of doing a full quote, you should have read it.

Also if you are only 12, you didn't take "some things" from bubuxp's thread, but almost the whole story. I would prefer if mod could close this thread.

harvey said:
Also if you are only 12, you didn't take "some things" from bubuxp's thread, but almost the whole story. I would prefer if mod could close this thread.
Click to expand...
Click to collapse
Starting to think there is no mod in this forum... At least for this device:silly:

Any one try this

Why do we need a separated Pie root guide, when the only difference for Pie is a newer patched boot image which you can make yourself with Magisk and the fitting OTA/Fastboot files?
We really need a mod for our A2 Lite forum, there are too many "useless" posts and threads inside. Feels like MIUI forum and not XDA.

OTA
NourHazem I said:
Frist You Must Unlock BootLoader
Second You Must Have Pc With Android platform tools (They Exist Also For MacOS And Linux)
BOOTLOADER UNLOCK
First thing to do: unlock the bootloader (if you didn't already do this, obviously). Smartphones with Android One are much easier to unlock compared to other Xiaomi phones with MIUI (where you have to ask for authorization and wait for weeks).
CAUTION: when you unlock the bootloader, the phone will reset, erasing all your saved data. Backup your data before unlocking.
1. Go to Settings > System > About phone > and tap many times on "Build number" until you unlock "Developer options".
2. Go back to the previous page, where you can find now "Developer options". Go there and enable the "OEM unlocking" option (and it's better to never disable this).
3. Now you can shutdown your phone, then turn it on while holding the "Volume down" button pressed. Release it when you see the Fastboot screen.
4. Now connect the phone with your PC via USB cable, open an administrative command prompt, move to the directory where the Android platform tools are placed and unlock the bootloader with the following command:
Code:
Code:
fastboot oem unlock
The phone will reboot, erasing all the data.
Now you unlocked your phone's bootloader and can continue to the next section
Download This https://mega.nz/#!3aZ3AICJ!YAHEVP5dQ2bgnV0_oDd3O4MBzdVt1qT_9HfqGWvVzCE
open an administrative command prompt, move to the Android platform tools directory and then write the following command:
Code:
Fastboot boot boot_rooted.img
If everything works the phone should boot normally. Open Magisk Manager and it should ask to install Magisk, if not you must tap on the "Install" button. Then choose "Install" > "Direct Install (Recommended)" to install Magisk on the phone, and reboot when finished.
HOW TO APPLY OTA UPDATES
IMPORTANT: OTA updates will work only if all the partitions on the smartphone are untouched. Magisk Manager can restore the original boot.img following this section of the guide, but if you tampered directly with the system partition (e.g. manually editing build.prop) or other partitions, OTA will refuse to install.
You can try to fix OTA updates without the need to flash the whole original fastboot ROM, by flashing only the tampered partitions (usually only "system") with the corresponding img file found inside the fastboot ROM zip. Check the "Troubleshooting" section of this guide for details.
12. When you know that a new OTA update is available and you want to install it, open Magisk Manager, and tap on "Uninstall" > "Restore Images" but very important: absolutely don't reboot the phone now!
Important note: Magisk Manager will restore the boot.img that was found on the phone while installing Magisk. If the boot.img was already non-vanilla (for example you flashed the boot.img with TWRP before installing Magisk), Magisk Manager will backup that modified version of boot.img, and when restored the OTA will not work, as that's not a vanilla boot.img.
13. Close Magisk Manager and go to "Settings" > "System" > "System update" and install the OTA update. After the update is downloaded, a two-stages update will begin.
14. When both stages of the update process completed, it will ask to restart: DON'T DO IT!. Open Magisk Manager again and tap on "Install" > "Install" > "Install to Inactive Slot (After OTA)" and after that you can tap on "Reboot".
After the reboot you will have the updated Android version with Magisk already working.
I'm 12 Years Old Don't Worry I Test It On My Mi A2 Lite Thanks
I Take Some Things From https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
Click to expand...
Click to collapse
Waiting I do not understand if I'm running my phone and installing a magician please update will not work?
---------- Post added at 06:37 PM ---------- Previous post was at 05:54 PM ----------
alenaki123 said:
Waiting I do not understand if I'm running my phone and installing a magician please update will not work?
Click to expand...
Click to collapse
f i unlock bootloader, root and install magisk ota update i will not work ???

Read the guide

Updates will work if you install it if you got ota go to magisk manager
Click uninstall>restore images>go install ota do not reboot>go magisk manager and click install select>inactive slot (after ota)

Bootloop! Not working
V10.0.2 Working https://www.the***********.com/root-xiaomi-mi-a2-a2-lite-android-pie-magisk/

OP should be ashamed of copying the entire guide and pasting It with a new link and poor formating.

I don't see Magisk Manager after doing boot patched_boot.img. It actually run successfully, the phone restarted after the command.
My Build number is PKQ1.180917.001.V10.0.2.0.PDLMIFJ, I tried both of these patched, V10.0.2.0.PDLMIFJ Patched Boot Image: Link
V10.0.1.0.PDLMIFJ Patched Boot Image: Link

luckyvictor said:
I don't see Magisk Manager after doing boot patched_boot.img. It actually run successfully, the phone restarted after the command.
My Build number is PKQ1.180917.001.V10.0.2.0.PDLMIFJ, I tried both of these patched, V10.0.2.0.PDLMIFJ Patched Boot Image: Link
V10.0.1.0.PDLMIFJ Patched Boot Image: Link
Click to expand...
Click to collapse
You need install manually magisk manager ,you can download apk from official website, after from magisk manager you can install magisk 18.0 ...this is my experience

thanks man, following your guide I was able to root this bad boy. Much more complicated than anything I've ever rooted as I've usually got TWRP installed but for whatever reason it's unable to decrypt my system and even after a fresh wipe I still can't install so this method worked great for me, we'll see how OTA updates go...
EDIT: Seems to be after a reboot I am no longer rooted, do I need to fastboot flash that patched boot image everytime I reboot?

@discomilk
Boot from patched boot.img
Open Magisk Manager -> install -> install direct
Reboot and profit!

Yup, seems I forgot to install Magisk after that patched boot. Everything working now.

[OnePlus6] Phone frozen (bricked?) while installing Kali NetHunter.

Wanted to install NetHunter on my phone to learn. Here is a story of a foolish student decided to make his life difficult:
Device: OnePlus 6
Model: A6000
Android 10
Here are the steps I followed:
Followed these two documentations:
1) https://www.kali.org/docs/nethunter/installing-nethunter/#1-nethunter-support-and-pre-built-images
2) https://www.kali.org/docs/nethunter/
So downloaded the zip image > put android in developer mode with OEM and advanced reboot and debugging enabled > Fastboot menu
Then I followed this guide for step 3-5 from link 1:
https://forum.xda-developers.com/t/...-flash-twrp-root-nandroid-efs-backup.3792643/
(a little bit google reading said TWRP takes care of A/B style devices by itself no special steps needed)
Set up the windows machine with fastboot, adb and device drivers > run the command "fastboot oem unlock" > transferred twrp zip to the device internal storage > then flashed the new recovery mode "fastboot boot twrp.img" > install and selected the twrp zip that I had saved in internal storage before > reboot > system.
So far worked perfectly.
Then I downloaded the Magisk apk from github and installed it by transferring it to internal storage.
Next for step 6 from link 1:
I again download the ForceEncrypt disabler from zip and transfer it to internal storage then flash it using TWRP.
So far no errors.
Now the final step should have been to flash the nethunter zip image and this is where the problems started:
I tried to flash it using TWRP but it gave me an error about there not being enough storage.
Saw a YT video where he extracts the nethunter zip and via the magisk app does a install on the tar file found inside the extracted folder. This also failed.
After a bit google it said it was because I did not have custom ROM and chroot and lineageOS should solve my problem.
I flash the LineageOS zip image using TWPR > successful but says I should switch the slot to complete the zip files installed.
After switching and rebooting, fastboot goes to lineage always and its a bootloop , so no matter what I select its always reaching the same screen and I cant tranfer zip to internal anymore to try a different build.
So now I run the command fastboot boot twrp.img again and go back to slot A.
Now my phone is stuck in bootloader. No matter what option I select out of the 4:
Start
Recovery mode
restart bootloader
power off
(latter two work as expected technically)
I always end up on the same screen.
After connecting the phone it is showing it as connected in "fastboot devices" now but fastbood is not able to flash or boot any image to it: either freezes or unknown error. "adb devices" shows no devices.
Practically begging for help right now.

To fix your phone, you should use this recovery tool.
https://forum.xda-developers.com/t/op6-latest-10-3-8-collection-of-unbrick-tools.3914109/
You can follow a tutorial like this one
Good luck

You haven't chosen the right place to ask for help. delete your post or change it to "Questions and answer". Have a good day.

d
CarlosTime said:
You haven't chosen the right place to ask for help. delete your post or change it to "Questions and answer". Have a good day.
Click to expand...
Click to collapse
Thank you. I am trying the suggested video right now.
Do you also know why I get the storage error while trying to flash nethunter?

take it easy, relax i have a long story with oneplus too
send me msg on telegram so i can help u 98%
uaername : NotReal0
stay safe bro, and dont worry i dont need you money just bc im noob with english so i just know that u damaged ur phone and i know how to fix

saffron_jedi said:
Wanted to install NetHunter on my phone to learn. Here is a story of a foolish student decided to make his life difficult:
Device: OnePlus 6
Model: A6000
Android 10
Here are the steps I followed:
Followed these two documentations:
1) https://www.kali.org/docs/nethunter/installing-nethunter/#1-nethunter-support-and-pre-built-images
2) https://www.kali.org/docs/nethunter/
So downloaded the zip image > put android in developer mode with OEM and advanced reboot and debugging enabled > Fastboot menu
Then I followed this guide for step 3-5 from link 1:
https://forum.xda-developers.com/t/...-flash-twrp-root-nandroid-efs-backup.3792643/
(a little bit google reading said TWRP takes care of A/B style devices by itself no special steps needed)
Set up the windows machine with fastboot, adb and device drivers > run the command "fastboot oem unlock" > transferred twrp zip to the device internal storage > then flashed the new recovery mode "fastboot boot twrp.img" > install and selected the twrp zip that I had saved in internal storage before > reboot > system.
So far worked perfectly.
Then I downloaded the Magisk apk from github and installed it by transferring it to internal storage.
Next for step 6 from link 1:
I again download the ForceEncrypt disabler from zip and transfer it to internal storage then flash it using TWRP.
So far no errors.
Now the final step should have been to flash the nethunter zip image and this is where the problems started:
I tried to flash it using TWRP but it gave me an error about there not being enough storage.
Saw a YT video where he extracts the nethunter zip and via the magisk app does a install on the tar file found inside the extracted folder. This also failed.
After a bit google it said it was because I did not have custom ROM and chroot and lineageOS should solve my problem.
I flash the LineageOS zip image using TWPR > successful but says I should switch the slot to complete the zip files installed.
After switching and rebooting, fastboot goes to lineage always and its a bootloop , so no matter what I select its always reaching the same screen and I cant tranfer zip to internal anymore to try a different build.
So now I run the command fastboot boot twrp.img again and go back to slot A.
Now my phone is stuck in bootloader. No matter what option I select out of the 4:
Start
Recovery mode
restart bootloader
power off
(latter two work as expected technically)
I always end up on the same screen.
After connecting the phone it is showing it as connected in "fastboot devices" now but fastbood is not able to flash or boot any image to it: either freezes or unknown error. "adb devices" shows no devices.
Practically begging for help right now.
Click to expand...
Click to collapse
I had the same issue after trying to install nethunter myself. Unfortunately for me the MSMDownload tool wouldn't work because I couldn't get the phone to stay off, it would just boot back up into bootloader/fastboot mode as soon as I connected to the computer via usb cable.
Here's the solution that will work 100%. Go to this website below and download the stock OOS zip file for your phone, in my case it was the Oneplus 6T fastboot ROM. Unpack the files into your platform-tools folder, click skip all if it asks you if you want to replace any files in that folder, then run the flash-all.bat and it will unbrick your device. Keep in mind that it will unroot your device and remove twrp as well. There's a thread here that explains how to do it manually so that doesn't happen but its a bit of work to get it done that way.
FastbootRoms Activity
sourceforge.net