This is a step by step guide for those who want root privileges on their watches. First of all, thanks to @rbox for the modified recovery image, and thanks to @Chainfire for the rooting files. Great developers.
I´ve used the latest superSU beta (systemless rooting), only deleting from the script the superuser.apk.
I´m not responsible for any damage. Do it knowing what you´re doing and at your own risk.
1- You must be in android wear 6.0.1 version. Download and unpack the rooting_files.rar (3 parts, xda format restrictions) and press shift button while right mouse click on a blank space on the folder. In the menu, select open command window here.
2- Reboot your watch in fastboot mode (power off the watch and power on sliding your finger from left top corner to right down corner) (or use adb command "adb reboot bootloader"). Connect it in the charging craddle to pc. If yout bootloader is locked, run "fastboot oem unlock" (It will factory reset your watch). If not, continue.
3- [optional] Flash through adb the twrp287 base image with the command "fastboot flash recovery twrp287.img"
4- Flash the modified twrp with "fastboot flash recovery twrp300modif.img"
5- Select recovery mode from fastboot menu and enter in twrp.
6- Push the wearSU267.zip into the internal memory with command "adb push wearSU267.zip /sdcard"
7- In TWRP select Install option and flash the wearSU267.zip. You may see some errors, ignore them.
8- Reboot your watch
You should have root now! Try it with a su command in terminal or any app.
I´ve included the original TWRP 3.0.0 image if anyone want to flash it after all.
Due to the new /system partition format, we cannot mount it in writable mode, so we cannot make changes inside at the moment, maybe someone can find a solution...
EXTRA: If you want change DPI, run this command: "adb shell wm density 180" (180 or whatever you want). The original value is 240 dpi.
Reserved
Nice tutorial! Currently flashing, I'll see if it works in a few minutes
Update: NICE! Worked like a charm!
Seeing as Busybox is used by almost all android wear apps would you not add it to the files? Also why are you flashing an old recovery and then the proper working one? Just flash the working one
Funciona de lujo, grax!
Xmaster24 said:
Seeing as Busybox is used by almost all android wear apps would you not add it to the files? Also why are you flashing an old recovery and then the proper working one? Just flash the working one
Click to expand...
Click to collapse
In the TWRP page it says the 3.0.0 image is an update, and must be flashed over an old version:
"TWRP Install (Requires TWRP 2.8.4 or higher already installed)"
https://twrp.me/devices/lggwatch.html
Anyway, it does not have effect, it is a precaution.
I´ve installed busybox after all through apk, but it´s not necessary for get root commands working
prototovsky said:
In the TWRP page it says the 3.0.0 image is an update, and must be flashed over an old version:
"TWRP Install (Requires TWRP 2.8.4 or higher already installed)"
https://twrp.me/devices/lggwatch.html
Click to expand...
Click to collapse
Em that's if your updating via recovery through fastboot your completely overwriting the recovery partition if you know how flashing works therefore the old version just disappears after flashing new version
Xmaster24 said:
Em that's if your updating via recovery through fastboot your completely overwriting the recovery partition if you know how flashing works therefore the old version just disappears after flashing new version
Click to expand...
Click to collapse
Then I´ll mark it as optional.
Knowledge is always collaborative
prototovsky said:
Then I�?�´ll mark it as optional.
Knowledge is always collaborative
Click to expand...
Click to collapse
Here's a link to my root method: Only 4 Steps you can take what you like from it http://forum.xda-developers.com/apps/supersu/android-wear-6-0-1-root-squashfs-t3319097/
Also thanks for info on dpi hate having 240 dpi even though it's the watches true dpi lol
Ok, so my watch is rooted now. Thanks! Now what?
jwinstonsf said:
Ok, so my watch is rooted now. Thanks! Now what?
Click to expand...
Click to collapse
Well I use kernel audiotor 4 wear, advanced settings(playstore) commandr, es file explorer (installed onto watch via adb) and minium wear
Xmaster24 said:
Well I use kernel audiotor 4 wear, advanced settings(playstore) commandr, es file explorer (installed onto watch via adb) and minium wear
Click to expand...
Click to collapse
my watch starts now only in twrp - the whole time - what can i do???
finrod2007 said:
my watch starts now only in twrp - the whole time - what can i do???
Click to expand...
Click to collapse
Try a factory reset in TWRP, if this does not work, reflash the rom
prototovsky said:
Try a factory reset in TWRP, if this does not work, reflash the rom
Click to expand...
Click to collapse
unable to mount ....system, data ....
finrod2007 said:
unable to mount ....system, data ....
Click to expand...
Click to collapse
Then reflash all (stock) through adb using this: http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863
prototovsky said:
Then reflash all (stock) through adb using this: http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863
Click to expand...
Click to collapse
thx, i think this will work out, i dont know what it is with twrp flashing supersu...
finrod2007 said:
thx, i think this will work out, i dont know what it is with twrp flashing supersu...
Click to expand...
Click to collapse
after point 5 of the tool - i stuck on bootlogo...made point 6 to restore the watch from stock but now it starts, starting the apps and do the same again and again, its going worser than better^^
finrod2007 said:
after point 5 of the tool - i stuck on bootlogo...made point 6 to restore the watch from stock but now it starts, starting the apps and do the same again and again, its going worser than better^^
Click to expand...
Click to collapse
Just use my method only 4 Steps and have debugged it completely so there should be no problems http://forum.xda-developers.com/g-watch/development/guide-how-to-root-lg-g-watch-6-0-1-t3320512
Xmaster24 said:
Just use my method only 4 Steps and have debugged it completely so there should be no problems http://forum.xda-developers.com/g-watch/development/guide-how-to-root-lg-g-watch-6-0-1-t3320512
Click to expand...
Click to collapse
yes of course I had known it before i had not done it, because everything was good, because then after point 6 i have android 5.1.1 on my watch, not android 6 any more, and its equal what i do nothing is changing when i start the watch, android is starting is finishing, watch starting again, doing this as again and again. i have done step 4 again, it does not change anything...
---------- Post added at 04:08 PM ---------- Previous post was at 04:07 PM ----------
finrod2007 said:
yes of course I had known it before i had not done it, because everything was good, because then after point 6 i have android 5.1.1 on my watch, not android 6 any more, and its equal what i do nothing is changing when i start the watch, android is starting is finishing, watch starting again, doing this as again and again. i have done step 4 again, it does not change anything...
Click to expand...
Click to collapse
but i will do your method now, maybe need a fresh stock rom which i can flash with a .bat file or something like that. are there any links???
finrod2007 said:
yes of course I had known it before i had not done it, because everything was good, because then after point 6 i have android 5.1.1 on my watch, not android 6 any more, and its equal what i do nothing is changing when i start the watch, android is starting is finishing, watch starting again, doing this as again and again. i have done step 4 again, it does not change anything...
---------- Post added at 04:08 PM ---------- Previous post was at 04:07 PM ----------
but i will do your method now, maybe need a fresh stock rom which i can flash with a .bat file or something like that. are there any links???
Click to expand...
Click to collapse
Will send you stock system.img, and you can use invisiblek's kernel or stock boot.img cause they are both working fine just format the others (/data and /cache)
Related
Hi,
i had B00 with root and chinese recovery
after updating to b121 i goot bootloop
than i changed recovery back to stock
tried to delete cache and system etc. nothing worked
B100 Upgrade via dload/update.app not working cause version mismatch i think
what can i do now. I don't need 349 euro trash.
please help me
Same problem here
Try updating with the full B121 ROM. I have uploaded it here https://mega.nz/#!dgZwAQpb!XcZSZJOWvG1DIDoJRr_EYSehtqTU1ciPE53bNhII8JQ
Follow the instructions in the included documents.
flibblesan said:
Try updating with the full B121 ROM. I have uploaded it here https://mega.nz/#!dgZwAQpb!XcZSZJOWvG1DIDoJRr_EYSehtqTU1ciPE53bNhII8JQ
Follow the instructions in the included documents.
Click to expand...
Click to collapse
Thanks mate, I'll give it a try.
pappapishu said:
Thanks mate, I'll give it a try.
Click to expand...
Click to collapse
any chance?
Fixed it with honor 6 multi-tool, huwaeiupdateextractor and fw b100.
Now i'm installing the b121 right away.
@evilmumi: hope you fixed it as well.
---------- Post added at 04:26 PM ---------- Previous post was at 04:24 PM ----------
evilmumi said:
any chance?
Click to expand...
Click to collapse
sorry, i didn't see your previous post.
yes, i figured out:
- downlaod the fw b100 version
- download honor 6 multi-tool (yes, even if it's made for the 6, it worked for 7 as well) and follow the "unbrick" procedure
if you have any question please ask
flibblesan said:
Try updating with the full B121 ROM. I have uploaded it here ...
Follow the instructions in the included documents.
Click to expand...
Click to collapse
thanks
you are my hero.
back in business
i hope i can use titanium backup to restore my old data w/o root
i am in trouble! i have erased all (cache dalvick data and system) by twrp! Now obviously the phone is on bootloop...i need desperately a system rom to flash
flibblesan said:
Try updating with the full B121 ROM. I have uploaded it here https://mega.nz/#!dgZwAQpb!XcZSZJOWvG1DIDoJRr_EYSehtqTU1ciPE53bNhII8JQ
Follow the instructions in the included documents.
Click to expand...
Click to collapse
Alphasampei said:
i am in trouble! i have erased all (cache dalvick data and system) by twrp! Now obviously the phone is on bootloop...i need desperately a system rom to flash
Click to expand...
Click to collapse
just read the thread
short:
0.)download from mega
1.) copy update.app on micro sd card /dload
2.)boot with volume up down and power than you can work!
evilmumi said:
just read the thread
short:
0.)download from mega
1.) copy update.app on micro sd card /dload
2.)boot with volume up down and power than you can work!
Click to expand...
Click to collapse
nope! still boot in twrp, i have no system inside the phone
sometimes we have this problem in our german forum too! More on rooted devices!
reflashing the full B100 or B121 rom help
we do it like your user described it here:http://forum.xda-developers.com/showpost.php?p=63070827&postcount=9
BTW: Where we can find the "updateextractor"? All versions of it that i have found, doesn’t work for H7 Roms!:crying:
Back to System boot
evilmumi said:
Hi,
i had B00 with root and chinese recovery
after updating to b121 i goot bootloop
than i changed recovery back to stock
tried to delete cache and system etc. nothing worked
B100 Upgrade via dload/update.app not working cause version mismatch i think
what can i do now. I don't need 349 euro trash.
please help me
Click to expand...
Click to collapse
When the phone is in RecoveryMode try a long press vol-up/vol-down/special-key and power all together for a few seconds until the phone reboots ... after that, the phone will start in SystemMode ... for me it worked.
stalfst said:
When the phone is in RecoveryMode try a long press vol-up/vol-down/special-key and power all together for a few seconds until the phone reboots ... after that, the phone will start in SystemMode ... for me it worked.
Click to expand...
Click to collapse
I realized that when I plugged the charger to phone and then powered it, it went off the TWRP boot loop. I fdon't know if any others have same issue.
When I updated my phone I had same kind of problem so I flashed stock recovery and then made the force upgrade following the rom's intructions.
Now eveything works again.
Alphasampei said:
nope! still boot in twrp, i have no system inside the phone
Click to expand...
Click to collapse
Twrp has a bootloop bug.. I also got this after rooting. What you need to do is to get it out of the bootloop by getting the phone in fastboot/download mode. I have no clue on how I finally got it to boot in fastboot mode, but I tried and tried until it finally booted in fastboot. Then I flashed stock recovery and everything was good after that. Lesson learned was that twrp and especially Chinese twrp is buggy as hell!
kjettern said:
Twrp has a bootloop bug.. I also got this after rooting. What you need to do is to get it out of the bootloop by getting the phone in fastboot/download mode. I have no clue on how I finally got it to boot in fastboot mode, but I tried and tried until it finally booted in fastboot. Then I flashed stock recovery and everything was good after that. Lesson learned was that twrp and especially Chinese twrp is buggy as hell!
Click to expand...
Click to collapse
I had no problems at all, no bootloops or any other weird stuff. Perhaps because I wiped cache + dalvik after supersu installation?
have the same problem, what should i do?
sugarray21 said:
have the same problem, what should i do?
Click to expand...
Click to collapse
Read instruction HERE
Fix Bootloops
Breaking out of bootloops depends on your device state and what kind of problem you are having. In this section, we are going to focus on the popular case where you can’t access neither the system nor the recovery partitions.
• Step 1: Turn off the phone.
• Step 2: Press Volume UP + Power Button For 10 seconds while connecting the USB cable from your device to your computer. That must make you boot into the bootloader mode.
(Update: A user has reported that holding the power button is optional on some models. Thanks to @sminki for pointing that out).
• Step 3: Head to your computer and download and install the following tool:
http://forum.xda-developers.com/show....php?t=2433454
• Step 4: Download the latest complete update file (B121) from:
http://www.modaco.com/forums/topic/3...s-121115-b140/
Then, extract it and get its UPDATE.app file.
• Step 5: Use the Huawei Update Extractor to extract the (BOOT.img), (SYSTEM.img), (RECOVERY.img), (CACHE.img), (CUST.img), and (USERDATA.img) from the UPDATE.app file that you have extracted from Step 4.
• Step 6: Open your command prompt, and navigate to the right directory where you have extracted the image files. Use the “cd” and “..” commands to do so.
• Step 7: Type the following commands and execute them one by one >
Code:
fastboot flash boot BOOT.img
fastboot flash system SYSTEM.img
fastboot flash recovery RECOVERY.img
fastboot flash cache CACHE.img
fastboot flash cust CUST.img
• Step 8: You can also erase the user data if you like by typing and executing the following >
Code:
fastboot flash userdata USERDATA.img
• Step 9: Reboot your device using the following command >
Code:
fastboot reboot
• Step 10: You must be able to boot successfully into the system.
(Noten this model, the "fastboot erase [Partition]" command has been reported by two users that it is not working. Thus, flash the image files directly and if it did not work, then check with the Huawei support center to fix your device. Thanks to @sminki for reporting this).
http://forum.xda-developers.com/honor-7/general/guide-beginners-how-to-root-update-fix-t3255452
TWRP Terminal Emulator command method.
I followed the steps here, http://androidforums.com/threads/twrp-bootloop-fix-after-update-ota.922585/ Thanks to the Author... hash_brown.1855790
Which is actually for LG, but slightly altering for Honor7 it works!!
for Honor 7 the commands to be run from TWRP Terminal command emulator will be
dd if=/dev/zero of=/dev/block/platform/hi_mci.0/by-name/fota
Click to expand...
Click to collapse
Hit GO/enter(return)...wait, takes a few seconds
Now input this
dd if=/dev/zero of=/dev/block/platform/hi_mci.0/by-name/misc
Click to expand...
Click to collapse
Hit enter (return)...wait again.
When its complete, reboot.
:good:
Alphasampei said:
nope! still boot in twrp, i have no system inside the phone
Click to expand...
Click to collapse
I had the same problem with twrp i can walking through how to unbrick your phone happy to help
It's finally here! TWRP recovery for the Fire TV 1. Most likely, I will not be updating this thread with new releases, as the prerooted ROMs will always contain the latest version. This thread is just here so people on Fire OS 3 can install TWRP and people on rooted but locked bootloader Fire TV 1's can get recovery initially installed.
As usual, this WILL void your warranty and I am NOT responsible for anything you do with this. Installing it properly won't brick your Fire TV, but doing stupid things with it might.
Installing this requires root. If you are not rooted, figure that out first.
Installation for Unlocked Bootloader
Make sure you are on a FULLY unlocked bootloader. From within FireOS and after running su run this:
Code:
cat /proc/cmdline
And MAKE SURE unlocked_kernel=true is present! If it is not, you are NOT fully unlocked and you must Fully Unlock first!
Make sure you are on at least 51.1.4.0 ROM and the latest CWM installed.
Copy the bueller-twrp_3.0.0-6.img file to /sdcard
From within adb shell, use su to become root, and run this command (are you sure you did step 1?)
Code:
dd if=/data/media/0/bueller-twrp_3.0.0-6.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
From outside adb shell, reboot to recovery
Code:
adb reboot recovery
TWRP should load, you can install a FireOS5 prerooted ROM now.
Installation for Locked Bootloader
This requires that you are on at least version 5.0.5 and rooted.
Copy the bueller_recovery_vX.zip file to /sdcard
From within adb shell, use su to become root, and run this command (replace vX with the actual version you downloaded)
Code:
sh /data/media/0/bueller_recovery_vX.zip
Reboot
Notes
This includes bootmenu. For everyone that loved the old bootmenu with Comic Sans, I'm sorry to disappoint you, but the Comic Sans is gone. When the FireTV boots, it will present you with the bootmenu where you can leave it alone and it will boot normally or you can select recovery and it will boot in to recovery. You do need a USB keyboard to interact with the bootmenu. To force it to boot in to Recovery, you can create a file /cache/bootmenu_recovery.
DHCP for Ethernet is enabled, and if there is enough demand I may add in wifi at some point. The IP address should show up in the top left corner.
USB storage and USB keyboard/mice should all work. Hotplugging works, so you should be able to plug and unplug devices as needed.
You can use a USB keyboard, mouse, or the mouse emulator to interact with it. To use a keyboard, you can use the arrow keys to move the cursor and the enter key to select buttons. Sliders don't require sliding, so you can just hit enter/click on them. To use the mouse emulator, use adb shell and then run the program mouse and follow the instructions.
ROMs
Recovery must be included in all ROMs. If you want to develop a ROM, please contact me about including recovery in it.
Installing zips
You can push zips to /sdcard, put it on a USB storage, or use adb sideload. Do note you need adb version 1.0.32 to use adb sideload.
Stuck in a loop?
If you cannot boot normally and keep going back to the bootmenu, wipe Cache from Wipe -> Advanced Wipe.
Source Code
You can find the source code here:
https://github.com/androidrbox/firetv-2ndinit
https://github.com/androidrbox/android_bootable_recovery
WARNINGS
It is extremely important you never reboot after a failure. This will most likely lead to a brick. If recovery is hung, you can use adb shell to run
Code:
killall recovery
to restart it
It is also extremely important to never reboot after wiping /system.
Finally, thanks to everyone who has donated to me.
Changelog and Downloads:
July 7, 2016 - v2 (md5sum: 8f65187cb0cbc190a7d64f512ae3ede2)
This is the updated version with TWRP 3.0.0-7.
July 4, 2016 - TWRP Image 3.0.0-7 (md5sum: cda1a1c1cdd3e25a1caa86f5a5de1eee)
May 20, 2016 - v1 (md5sum: 9208d81fd07cff9952de5be33c62f730)
This is for use by people who have FireOS5 and are rooted.
This includes 2ndinit version a7a48c and TWRP version 3.0.0-6.
May 20, 2016 - TWRP Image (md5sum: 5dc83370046e5b50755ddb55fe8424ad)
This is for use by people who have FireOS3 and CWM and is TWRP version 3.0.0-6.
thanks so much rbox! just tested it and i can confirm that my firetv 1 with fireos3 and fully unlocked bootloader just installed twrp successfully - woot!
i still have the old boot menu though with comic sans..?
mrchrister said:
thanks so much rbox! just tested it and i can confirm that my firetv 1 with fireos3 and fully unlocked bootloader just installed twrp successfully - woot!
i still have the old boot menu though with comic sans..?
Click to expand...
Click to collapse
For unlocked bootloaders, this step JUST installs recovery. You need to install the prerooted rom to get the new bootmenu.
got you, downloading now
Sent from my iPhone using Tapatalk
I successfully dd'ed the recovery image onto my ftv with unlocked bootloader but attempting to boot it causes the TWRP logo to show for a few seconds, then the screen goes black and the cycle repeats. Any idea how to fix this?
ssgelm said:
I successfully dd'ed the recovery image onto my ftv with unlocked bootloader but attempting to boot it causes the TWRP logo to show for a few seconds, then the screen goes black and the cycle repeats. Any idea how to fix this?
Click to expand...
Click to collapse
If you unplug the power and replug it, it should boot normally, then you can see if the recovery log got saved, /cache/recovery/last_log and pastebin it.
The log at /cache/recovery/last_log is from CWM from the last time I flashed a new rom.
ssgelm said:
The log at /cache/recovery/last_log is from CWM from the last time I flashed a new rom.
Click to expand...
Click to collapse
Can't really explain why it would be doing that. Can you connect via adb?
I am not on ethernet right now. When I get a chance I'll do that and see if I can connect. Thanks so much for your work on this!
ssgelm said:
I successfully dd'ed the recovery image onto my ftv with unlocked bootloader but attempting to boot it causes the TWRP logo to show for a few seconds, then the screen goes black and the cycle repeats. Any idea how to fix this?
Click to expand...
Click to collapse
I'm also getting this, what can I do?
here's last_log
gehx said:
I'm also getting this, what can I do?
Click to expand...
Click to collapse
Can you connect via adb?
rbox said:
Can you connect via adb?
Click to expand...
Click to collapse
yep, that's how I pulled last_log
gehx said:
yep, that's how I pulled last_log
Click to expand...
Click to collapse
I meant while recovery is running.
rbox said:
I meant while recovery is running.
Click to expand...
Click to collapse
recovery never fully loads, i just get the twrp splash screen over and over and over again...it's in a loop
gehx said:
recovery never fully loads, i just get the twrp splash screen over and over and over again...it's in a loop
Click to expand...
Click to collapse
Yes. But have you tried using adb...
rbox said:
Yes. But have you tried using adb...
Click to expand...
Click to collapse
I'm not sure what IP to use?
gehx said:
I'm not sure what IP to use?
Click to expand...
Click to collapse
The same one the firetv would be using when it's booted... via ethernet of course.
rbox said:
The same one the firetv would be using when it's booted... via ethernet of course.
Click to expand...
Click to collapse
the connection times out:
adb connect 192.168.1.6
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
unable to connect to 192.168.1.6:5555: Operation timed out
Click to expand...
Click to collapse
gehx said:
the connection times out:
Click to expand...
Click to collapse
Can you pull the log again? It should say the ip in it actually.
rbox said:
Can you pull the log again? It should say the ip in it actually.
Click to expand...
Click to collapse
new last_log
it shows 192.168.1.8; I'm unable to adb connect to that IP too
Hi guys,
for those on system/bootstack by tron1, this is what i did to flash B02 with root and fastboot working.
Thnx to @wineds , @tron1
In detail this is what i did ( because i couldn't update the .zip from sd nor update through adb sideload after i installed stock recovery 711 - @wineds could flash the .zip over SD though - thats up to you to choose)
1. I redownloaded fota B02 (to be sure ) from : http://dl1.ztems.com/zxmdmp/downloa...ages/HK/ZTE/ZTE A2017G/401379/fota_B02_B04.up
2. I didn't change .up to .zip. Put it in ADB folder (you know how...)
3. reinstalled Bootstack B01 tron1 via TWRP ( i reuploaded it here because some users had zip problems : https://www.androidfilehost.com/?fid=457095661767157153 )
4. reinstalled System B01 tron1 via TWRP ( i reuploaded and checked it again because some users had zip problems : https://www.androidfilehost.com/?fid=529152257862722738 )
5. installed stock recovery from factory img 7.11 , I uploaded it here https://www.androidfilehost.com/?fid=745425885120725539
6. in TWRP reboot to recovery----> you will reboot in stock recovery
7. update from ADB sideload ( adb sideload yourupdateB02file.up)
8. let it update...will take +-5 min in my case, in my case it was hanging a while on 47% (i thought it froze and tapped on power once, it continued...perhaps you don't have to and wait )
9. reboot system----> you'll have B02
10. use adb again, use ADB REBOOT EDL (https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379), use command ' axon7tool -w recovery' just to reflash TWRP 3.0.2.2 (if needed : https://www.androidfilehost.com/?fid=529152257862720446) . It will reboot system ok. Reenter TWRP 3.022 again and stay there.
11 to get fastboot again, use same thread as above under B ( leave TWRP running), in ADB you'll see you're in recovery mode, that's ok.
12. refollow steps 6 to 14. Reboot to fastboot will be ok again !
13 now in ADB type : fastboot flash recovery 'yourlatestrecovery 3.1'.img (if needed : https://www.androidfilehost.com/?fid=529152257862720448)
14. fastboot reboot
14. your system will reboot without the anoying " blah blah blah unlocked"
15 reenter TWRP 3.1 again and flash SU2.79 again
16 done
17 pls comment/feedback if you succeeded as well
@raystef66
Your links in steps 1 and 10 are invalid due to copy/paste ellipsis (...).
dnlilas said:
@raystef66
Your links in steps 1 and 10 are invalid due to copy/paste ellipsis (...).
Click to expand...
Click to collapse
Some of them were...weird, i never had this problem reffering to other threads..
Did update links. Check them out to verify pls.
Thnx !
I tried your method, everything is fine until I sideload b02 because I get a message when the current system is being verified "E3005: EMMC:/dev/block/bootdevice/by-name/boot: (here are some numbers) has unexpected content" Error in sideload Status 8
And I cannot update to B02, even though currently I am on b01 by tron1 .
S0wL said:
I tried your method, everything is fine until I sideload b02 because I get a message when the current system is being verified "E3005: EMMC:/dev/block/bootdevice/by-name/boot: (here are some numbers) has unexpected content" Error in sideload Status 8
And I cannot update to B02, even though currently I am on b01 by tron1 .
Click to expand...
Click to collapse
Have you tried in stock recovery to update with sd instead of sideload with adb? You also could try changing . UP to . ZIP
raystef66 said:
Have you tried in stock recovery to update with sd instead of sideload with adb? You also could try changing . UP to . ZIP
Click to expand...
Click to collapse
I tried with stock recovery with sideload and with sd as well. with .up and .zip too and I get the same error .
@raystef66 thanks for ur guide
I need to update to b02 but I don't have courage to lose root
Anyone please report after success
Sent from my ZTE A2017G using XDA-Developers Legacy app
tuiyaan said:
@raystef66 thanks for ur guide
I need to update to b02 but I don't have courage to lose root
Anyone please report after success
Sent from my ZTE A2017G using XDA-Developers Legacy app
Click to expand...
Click to collapse
this method has been tried originally by @wineds - he only updated via SD, that's all and changed .up into .zip
In fact you have nothing to fear because when f.e. you're in stock recovery and things won't update as expected, you always can go back in ADB and flash recovery again with axon7tool (EDL) etc...there's always a way out. And have root back....
When your update succeeds after all, you WILL obtain root again as i discribed. Just follow the steps carefully.
I managed to do this in 1 take
S0wL said:
I tried your method, everything is fine until I sideload b02 because I get a message when the current system is being verified "E3005: EMMC:/dev/block/bootdevice/by-name/boot: (here are some numbers) has unexpected content" Error in sideload Status 8
And I cannot update to B02, even though currently I am on b01 by tron1 .
Click to expand...
Click to collapse
Yes rename FOTA as a .zip file and try update from SD card in stock recovery. The fIle needs to be on your external SD. However the error seems to indicate one of your partitions has been modified.
Isn't it easier to
-update to B02
-axon7tool -w recovery
-disconnect before the Success, rebooting countdown ends
-boot TWRP??
Someone made a flashable fastboot zip. haven't tested yet but I guess it will get us fastboot easier
Choose an username... said:
Isn't it easier to
-update to B02
-axon7tool -w recovery
-disconnect before the Success, rebooting countdown ends
-boot TWRP??
Someone made a flashable fastboot zip. haven't tested yet but I guess it will get us fastboot easier
Click to expand...
Click to collapse
Nope, did that too and was a no go. That would have been one of the options to do (i made a thread for this too) but in this case fastboot didn't want to boot with that method strange enough. But you could try and see for your self.
For me this method worked great and i stay 100% stock despite other flashable b02's which are customized.
raystef66 said:
Nope, did that too and was a no go. That would have been one of the options to do (i made a thread for this too) but in this case fastboot didn't want to boot with that method strange enough. But you could try and see for your self.
For me this method worked great and i stay 100% stock despite other flashable b02's which are customized.
Click to expand...
Click to collapse
Yeah, fastboot doesn't want to boot because it isn't there... I mean get to EDL then flash TWRP from there with axon7tool.
I used this method on my guide and it's been working flawlessly
Choose an username... said:
Yeah, fastboot doesn't want to boot because it isn't there... I mean get to EDL then flash TWRP from there with axon7tool.
I used this method on my guide and it's been working flawlessly
Click to expand...
Click to collapse
To get fastboot back you have to downgrade aboot to b01 version :
https://forum.xda-developers.com/showpost.php?p=71847111&postcount=39
wineds said:
To get fastboot back you have to downgrade aboot to b01 version :
https://forum.xda-developers.com/showpost.php?p=71847111&postcount=39
Click to expand...
Click to collapse
Yeah, and you can flash that once you get TWRP
I'm going to update that guide, but the XDA app doesn't let me edit, and I'm far away from a computer. I'll write the process and see if I can try to get fastboot with that zip storming did. For now the process i have in mind is:
Get axon7tool, adb reboot edl, install Zadig qusb_bulk drivers, reload edl with 3 buttons, axon7tool -w recovery (after a backup ofc), disconnect before the tool restarts the phone (you get stock recovery), flash that zip.
Choose an username... said:
Yeah, and you can flash that once you get TWRP
I'm going to update that guide, but the XDA app doesn't let me edit, and I'm far away from a computer. I'll write the process and see if I can try to get fastboot with that zip storming did. For now the process i have in mind is:
Get axon7tool, adb reboot edl, install Zadig qusb_bulk drivers, reload edl with 3 buttons, axon7tool -w recovery (after a backup ofc), disconnect before the tool restarts the phone (you get stock recovery), flash that zip.
Click to expand...
Click to collapse
Or use my method
Works too you know :laugh:
Never mind how you do it every method is ok.
I kept it to the basics every one should know by now. In fact performing the steps to get fastboot again lasts no more then a minute. Just copy paste...
Btw, don't brick your phone again! :cyclops: as i remember you came from the other side of the moon...
raystef66 said:
Or use my method
Works too you know :laugh:
Never mind how you do it every method is ok.
I kept it to the basics every one should know by now. In fact performing the steps to get fastboot again lasts no more then a minute. Just copy paste...
Btw, don't brick your phone again! :cyclops: as i remember you came from the other side of the moon...
Click to expand...
Click to collapse
Lol I wiped system and data and was holding the power button... Can't believe I was that silly.
My guide actually turned out pretty huge too. So whatever man
Choose an username... said:
Lol I wiped system and data and was holding the power button... Can't believe I was that silly.
My guide actually turned out pretty huge too. So whatever man
Click to expand...
Click to collapse
Cheers mate and...happy flashing! :good:
Hi, when I try to flash stocksystem by tron1, TWRP tell me that the zip is incorrect and he can't flash it. I tried to download it again and again but still doesn't work.
fabro91 said:
Hi, when I try to flash stocksystem by tron1, TWRP tell me that the zip is incorrect and he can't flash it. I tried to download it again and again but still doesn't work.
Click to expand...
Click to collapse
Dont think the zip is incorrect. Flashed it without any errors. Others too. You're on latest 3.1.0.0 and SU2.79? Is zip in root of sd/internal?
No on external sd
---------- Post added at 05:33 PM ---------- Previous post was at 05:32 PM ----------
Didn't work with sideload anymore
*** OUTDATED, WORK HAS NOW PROGRESSED TO POISON ROM, https://forum.xda-developers.com/an...mputers/amlogic/t95z-plus-poison-rom-t3751720 ***
Features
Removed Bloatware apps such as Twitter, Team Viewer etc.
Removed Dummy Play Store App
Removed Outdated versions of apps and replaced them with latest versions as of time of writing, like Playstore, Firefox, Kodi etc.
Used a Custom Launcher (Created by Ricky Divjakovski) to give device a fresh look.
Enter Key now works on External Keyboards
Known Bugs:
Play Store shortcut on Launcher does not work, Can open Playstore through Setting/Apps. ***Fixed***
Enter key on External Keyboard doesn't work. ***Fixed***
Navigation Bar does not come back if minimised without a reboot.
When you go to Settings/About/Status sometimes has an error and doesn't open, opens on second attempt though.
Any other bugs feel free to report.
***IMPORTANT ***
You need to be on Stock 7.1.2 Firmware before flashing the Custom Rom. So I recommend you make a backup of your existing Firmware if for any reason you want to go back to your Existing Firmware and setup. To make a backup, you need to get Custom Recovery (TWRP) installed, you need to install the right version of TWRP depending on your existing firmware. Download your existing Firmware Custom Recovery files from below.
TWRP FILES
If on Firmware 6.0.1 from here
If on Firmware 7.1.1 from here
If on Firmware 7.1.2 from here
INSTALLING CUSTOM RECOVERY
METHOD 1:
Download Ricky's Amlogic Flash Tool from AmlogicFlashTool.zip and follow the instructions from his thread over at https://forum.xda-developers.com/an...c/amlogic-devices-amlogic-flash-tool-t3745640.
METHOD 2:
1. Download ADB from here and install it on your pc, then open a command prompt (Windows 10 hold Shift and press Right Mouse button, will take you to Power Shell) in the directory of the custom recovery
2. Enable USB debugging, go to settings>about and click build number about 10 times, then go back to the main settings menu and you will see developer options, enter it and check allow USB debugging.
3. Connect to your device via IP address. go to settings>about>status and get your IP address. it should be something like 192.168.25.19
4. In CMD type the following commands, replace YOURIPADDRESS with the address we got from step 3
Code:
adb connect YOURIPADDRESS
adb push custom-recovery.img /sdcard/
adb shell su -c dd if=/sdcard/custom-recovery.img of=/dev/block/recovery
adb reboot recovery
TWRP BACKUP
Now go ahead and make a backup of your existing setup before proceeding any further. I recommend putting the backup onto a usb drive.
Step:
1. Go to Backup
2.If desired name your backup on name setting up top left hand corner, not necessary but can do if you like.
3. Select Storage: USB or SDCard depending on which one you are going to use. Click OK.
3. Swipe to Backup
4. Let it do it's thing, When finished remove usb/sd card and reboot to system.
5. Recommend putting a copy of your backup from your usb or sd card to your PC as well.
FLASHING 7.1.2 STOCK FIRMWARE
You need to download the Stock 7.1.2 firmware from here
Use the provided USB Burning tool to flash the firmware if you have a USB Male to Male cable. Video of how to here
Now 7.1.2 Stock is installed, you now have to flash the Custom Recovery (TWRP) for 7.1.2, follow the instructions earlier to install Custom Recovery with the 7.1.2 file.
CUSTOM ROM
NOTE: Remember to make sure you have a backup of your old existing firmware before flashing this custom rom
Instructions:
1. Download the 3/32GB T95Z Custom Rom 7.1.2.zip from here
and put it on a usb stick.
2. Reboot into recovery
3. Wipe Cache, System and Data
4. Go back to the main menu and select install, then choose the 3/32GB T95Z Custom Rom 7.1.2.zip and swipe to install!
Reboot and enjoy!
Please give 5 to 10 minutes on first reboot after flash.
Contributors
Ricky Divjakovski, whiteak
ROM OS Version: 7.x Nougat
Credits:
Magendanz (TWRP)
Snoop05 (Adb)
Version Information
Status: Testing
Great job! A whole range of ROMS for Amlogic devices is about to unveil once i release the rom skeletop package!
Hi on my device when i reboot to recovery after put TWRP by adb it's stuck on T95z plus logo... Any idea ?
after unplug the power cable and plug it again the box start, but i can't start in recovery by the adb... can u give me some help ?
Thanks by advance.
---------- Post added at 11:36 AM ---------- Previous post was at 11:31 AM ----------
I do that and i don't see any error..
C:\Users\papla\Downloads\platform-tools-latest-windows\platform-tools>adb connect 192.168.1.100
connected to 192.168.1.100:5555
C:\Users\papla\Downloads\platform-tools-latest-windows\platform-tools>adb push custom-recovery.img /sdcard/
custom-recovery.img: 1 file pushed. 6.6 MB/s (13793280 bytes in 1.986s)
C:\Users\papla\Downloads\platform-tools-latest-windows\platform-tools>adb shell su -c dd if=/sdcard/custom-recovery.img of=/dev/block/recovery
26940+0 records in
26940+0 records out
13793280 bytes transferred in 2.774 secs (4972343 bytes/sec)
C:\Users\papla\Downloads\platform-tools-latest-windows\platform-tools>adb reboot recovery
C:\Users\papla\Downloads\platform-tools-latest-windows\platform-tools>
Is your box 2/16gb or 3/32gb, you may be flashing the wrong TWRP.
whiteak said:
Is your box 2/16gb or 3/32gb, you may be flashing the wrong TWRP.
Click to expand...
Click to collapse
32Gb box and i take the twrp from your thread.
papla83 said:
32Gb box and i take the twrp from your thread.
Click to expand...
Click to collapse
Try this TWRP here
It's a earlier version, but I ported this one myself. It's the one I used until I found a newer version.
whiteak said:
Try this TWRP here
It's a earlier version, but I ported this one myself. It's the one I used until I found a newer version.
Click to expand...
Click to collapse
Same result, hang on t95Zplus logo and doesn't move....
papla83 said:
Same result, hang on t95Zplus logo and doesn't move....
Click to expand...
Click to collapse
And you definitely have a 3/32gb box, I don't know what could be the problem. I had the exact same problem, but it was because I was using the 2/16 version on my 3/32 box. You don't have any usb sticks plugged into the box either? if you do try pulling them out when flashing.
whiteak said:
And you definitely have a 3/32gb box, I don't know what could be the problem. I had the exact same problem, but it was because I was using the 2/16 version on my 3/32 box. You don't have any usb sticks plugged into the box either? if you do try pulling them out when flashing.
Click to expand...
Click to collapse
yes i have, i will try whitout sd card and usb stick and make a feedback
---------- Post added at 02:02 PM ---------- Previous post was at 01:56 PM ----------
same result
can i brick my box if i flash it with the 16Gb model ? because maybe i can try with no risk ( the recovery doesn't start anyway )
Worst case is it should only do the same thing, I was pushing the 16gb model on my box a fair few times and all it did hang at the T95Z Plus logo.
whiteak said:
Worst case is it should only do the same thing, I was pushing the 16gb model on my box a fair few times and all it did hang at the T95Z Plus logo.
Click to expand...
Click to collapse
When i try to send twrp 16gb version to my box i have an error message failed to send file ( i use the amlogic adb tool by Ricky Divjakovski )...
papla83 said:
yes i have, i will try whitout sd card and usb stick and make a feedback
---------- Post added at 02:02 PM ---------- Previous post was at 01:56 PM ----------
same result
can i brick my box if i flash it with the 16Gb model ? because maybe i can try with no risk ( the recovery doesn't start anyway )
Click to expand...
Click to collapse
By personal experience your best bet is to re flash the original rom with the usb flashing tool.
Once it is done you can try flashing different TWRP until you find one that work. Installing TWRP from the store just does not work on those device.
Installing SU also soft brick your device and normal recovery do not work.
Also to flash using to USB burning tool make sure you use the OTG USB port on your device (usually port no, 1).
whiteak said:
Known Bugs:
Play Store shortcut on Launcher does not work, Can open Playstore through Setting/Apps.
Navigation Bar does not come back if minimised without a reboot.
When you go to Settings/About/Status sometimes has an error and doesn't open, opens on second attempt though.
Any other bugs feel free to report.
Click to expand...
Click to collapse
I got play store to work on my original rom from the launcher after disabling it in the app settings, and replacing system/app/GoogleStore folder by the one from SuperCeleron 3/32g custom rom ans installing it from the apk. Might be worth a look to get it working on your rom.
Funny thing is that I tried to install SuperCeleron Rom on my machine but it brick it every time.
Also on initial setup after you have an option to give root acces or not and also to enables init.d support, I just can't remember where it was in the Droid settings on the launcher or the most advance settings in the apps folder. I will have to go thru all the settings to find them.
I tried your ROM but it disabled my Play Store in the launcher and in the apps and did not let me reinstall it for some reason. I had to go thru TotalCommander to be able to launch it. Since I did not want to fool around to restore it. I just flashed back my Rom.
I can live with the way my device perform right now has the most important part for me was Kodi.
Stuck at logo as well
I got everything to go just fine: ADB went smooth, TWRP running just fine, successful flash from microSD card, wiped cache, rebooted and waited 15 minutes and I'm just stuck at the logo
I even pulled AC and ejected the card and then plugged it in let it sit for 20 minutes and nothing but the logo still.
I'm 101% sure I'm have a 3G+32Gb T95z Plus (AP6225 WLAN)
LeMaestro said:
I got play store to work on my original rom from the launcher after disabling it in the app settings, and replacing system/app/GoogleStore folder by the one from SuperCeleron 3/32g custom rom ans installing it from the apk. Might be worth a look to get it working on your rom.
Funny thing is that I tried to install SuperCeleron Rom on my machine but it brick it every time.
Also on initial setup after you have an option to give root acces or not and also to enables init.d support, I just can't remember where it was in the Droid settings on the launcher or the most advance settings in the apps folder. I will have to go thru all the settings to find them.
I tried your ROM but it disabled my Play Store in the launcher and in the apps and did not let me reinstall it for some reason. I had to go thru TotalCommander to be able to launch it. Since I did not want to fool around to restore it. I just flashed back my Rom.
I can live with the way my device perform right now has the most important part for me was Kodi.
Click to expand...
Click to collapse
I want just have the best experience with this box, the box ,at this time and with this rom works, but i feel the works doesn't finish and i think we have a huge possibility with a finalised and optimised rom.
---------- Post added at 10:02 PM ---------- Previous post was at 10:01 PM ----------
Semper 5 said:
I got everything to go just fine: ADB went smooth, TWRP running just fine, successful flash from microSD card, wiped cache, rebooted and waited 15 minutes and I'm just stuck at the logo
I even pulled AC and ejected the card and then plugged it in let it sit for 20 minutes and nothing but the logo still.
I'm 101% sure I'm have a 3G+32Gb T95z Plus (AP6225 WLAN)
Click to expand...
Click to collapse
Hi. sorry for the dumb question but do you wipe to the factory data too or only wipe cache ?
papla83 said:
Hi. sorry for the dumb question but do you wipe to the factory data too or only wipe cache ?
Click to expand...
Click to collapse
I tried just the cache at first, but I tried both. and now, since I updated 7.1.1 > 7.1.2 I can't get TWRP to boot. I think the 7.1.2 doesn't like the TWRP I was using.
PS, the link for TWRP in this thread is nonexistent.
It would be AMAZING if we could get this custom ROM in an IMG file to use in the Amlogic burner application.
Semper 5 said:
I tried just the cache at first, but I tried both. and now, since I updated 7.1.1 > 7.1.2 I can't get TWRP to boot. I think the 7.1.2 doesn't like the TWRP I was using.
PS, the link for TWRP in this thread is nonexistent.
It would be AMAZING if we could get this custom ROM in an IMG file to use in the Amlogic burner application.
Click to expand...
Click to collapse
Take a look here maybe you will find what you need.
https://forum.xda-developers.com/an...95z-plus-one-thread-files-recoveries-t3737040
I used the custom recovery for the 3/32Gb variant and it worked perfect, now I have a working TWRP.
papla83 said:
I want just have the best experience with this box, the box ,at this time and with this rom works, but i feel the works doesn't finish and i think we have a huge possibility with a finalised and optimised rom.
Click to expand...
Click to collapse
Me to I would like to have a few thing added or fixed in the launcher, but those guys just started to work on this a few days ago, so let give them time to make it better. I screw up my box enough in the last week so let be patient.
Semper 5 said:
I tried just the cache at first, but I tried both. and now, since I updated 7.1.1 > 7.1.2 I can't get TWRP to boot. I think the 7.1.2 doesn't like the TWRP I was using.
PS, the link for TWRP in this thread is nonexistent.
It would be AMAZING if we could get this custom ROM in an IMG file to use in the Amlogic burner application.
Click to expand...
Click to collapse
TWRP link updated, not sure why it unlinked but anyway should be good to download again.
LeMaestro said:
Take a look here maybe you will find what you need.
https://forum.xda-developers.com/an...95z-plus-one-thread-files-recoveries-t3737040
I used the custom recovery for the 3/32Gb variant and it worked perfect, now I have a working TWRP.
Me to I would like to have a few thing added or fixed in the launcher, but those guys just started to work on this a few days ago, so let give them time to make it better. I screw up my box enough in the last week so let be patient.
Click to expand...
Click to collapse
That link in the other thread links to my mega folder, can I ask which custom recovery you used the 3.1.1-0 or the 3.0.2, both should work, but just curious. Also so you did manage to flash my custom zip successfully and it did boot up? Not sure why people are having problems.
I wanted to make sure everyone read this part first so that you know it's critical to backup because it happened to me figuring things out. If for any reason you are stuck in a boot loop, just reload twrp recovery and restore boot.img that you backed up for an easy quick fix.
Install drivers and adb on your PC.
Open command prompt or search 'cmd'.
Navigate to the directory with adb.exe
Download and store TWRP 2.2.2 (preferred) in the same directory where adb is located. Recommend renaming recovery file to recovery.img
Enable usb debugging on device by going to settings > about > and click on MIUI version repeatedly until developer settings are enabled. Go back and select additional settings to enable usb debugging.
Run the command: adb devices - to verify if able to connect to device (the serial number of your device will populate if so.
Run the command: adb reboot bootloader and phone device should say "Fastboot" in blue font
Run the command: fastboot boot recovery.img
Recovery will show in Chinese, click on the bottom right button to select English
May require to enter your default password you use to unlock your phone normally.
Click backup and be sure to backup system, boot, and recovery most of all so it's easy to recover your device moving forward.
Download and save SuperSU (I have been unsuccessful in getting Magisk to work at this time) onto storage device from PC to MI 8 that should appear with your Internal storage
Click on "Mount" in TWRP and unselect read-only
Click "Install" and flash SuperSU then reboot (my device rebooted one time and fully boot up the 2nd time so you're not alarmed)
Links:
SuperSU: https://download.chainfire.eu/1122/SuperSU/SR3-SuperSU-v2.82-SR3-20170813133244.zip?retrieve_file=1
TWRP: https://forum.xda-developers.com/mi-8/development/recovery-twrp-3-2-2-0703-t38126005
Appreciate any feedback, ideas, thoughts, or suggestions where all can collaborate and expand where we help each other further. Look forward to the future development of the MI 8 folks! Please note, I wanted to share the method that seemed to work best for me, but please be aware each and every single MI 8 device is not always exactly the same and the end result may vary and I'm not held accountable or responsible should you choose to follow the directions listed above. However, I wanted to share this information to help avoid any frustration going forward and save you time.
p.s. - If someone could help me figure out how to get twrp recovery to hold and not end up being replaced by mi recovery I would be most grateful as this has been an issue for me (I tried flashing, booting, and installing the img through twrp with no success). Thank you.
Hello thanks for your guide but i think we first need to unlock bl And for the twrp recovery to stick and not to be replaced by xiaomi recovery we need to flash something called "dm-verity " it basically removes that check, which replaces any other recovery by xiaomi recovery
Have a nice day and thanks for your work
I thought so as well, unfortunately I just haven't had much luck with dm verity which led to a soft brick on my device. I'll have to look over the code as it may vary in comparison to other xiaomi devices.
Sent from my MI 8 using Tapatalk
Fastboot flash recovery Command should do it ..
mekaziah said:
I wanted to make sure everyone read this part first so that you know it's critical to backup because it happened to me figuring things out. If for any reason you are stuck in a boot loop, just reload twrp recovery and restore boot.img that you backed up for an easy quick fix.
Install drivers and adb on your PC.
Open command prompt or search 'cmd'.
Navigate to the directory with adb.exe
Download and store TWRP 2.2.2 (preferred) in the same directory where adb is located. Recommend renaming recovery file to recovery.img
Enable usb debugging on device by going to settings > about > and click on MIUI version repeatedly until developer settings are enabled. Go back and select additional settings to enable usb debugging.
Run the command: adb devices - to verify if able to connect to device (the serial number of your device will populate if so.
Run the command: adb reboot bootloader and phone device should say "Fastboot" in blue font
Run the command: fastboot boot recovery.img
Recovery will show in Chinese, click on the bottom right button to select English
May require to enter your default password you use to unlock your phone normally.
Click backup and be sure to backup system, boot, and recovery most of all so it's easy to recover your device moving forward.
Download and save SuperSU (I have been unsuccessful in getting Magisk to work at this time) onto storage device from PC to MI 8 that should appear with your Internal storage
Click on "Mount" in TWRP and unselect read-only
Click "Install" and flash SuperSU then reboot (my device rebooted one time and fully boot up the 2nd time so you're not alarmed)
Links:
SuperSU: https://download.chainfire.eu/1122/SuperSU/SR3-SuperSU-v2.82-SR3-20170813133244.zip?retrieve_file=1
TWRP: https://forum.xda-developers.com/mi-8/development/recovery-twrp-3-2-2-0703-t38126005
Appreciate any feedback, ideas, thoughts, or suggestions where all can collaborate and expand where we help each other further. Look forward to the future development of the MI 8 folks! Please note, I wanted to share the method that seemed to work best for me, but please be aware each and every single MI 8 device is not always exactly the same and the end result may vary and I'm not held accountable or responsible should you choose to follow the directions listed above. However, I wanted to share this information to help avoid any frustration going forward and save you time.
p.s. - If someone could help me figure out how to get twrp recovery to hold and not end up being replaced by mi recovery I would be most grateful as this has been an issue for me (I tried flashing, booting, and installing the img through twrp with no success). Thank you.
Click to expand...
Click to collapse
Skickat från min MI 8 via Tapatalk
what issues do you get with magisk? I was able to flash it without any issues.
superior8888 said:
Fastboot flash recovery Command should do it ..
Skickat från min MI 8 via Tapatalk
Click to expand...
Click to collapse
Yes it does. Don't know why anyone would run SuperSU though.
mekaziah said:
I thought so as well, unfortunately I just haven't had much luck with dm verity which led to a soft brick on my device. I'll have to look over the code as it may vary in comparison to other xiaomi devices.
Click to expand...
Click to collapse
MAKE SURE U HAVE UNLOCKED BOOTLOADER
here is wat i do
first i boot into twrp
(make sure u have rom.zip magisk/superuser.zip an twrp.img) on internal storage
then i wipe
dalvik cache
cache
data (NOT FORMAT)
system
then i flash
rom.zip
twrp.img
then i reboot recovery
fkash magisk.zip
then reboot system
now i have new rom an still have twrp on
-fluffy- said:
here is wat i do
first i boot into twrp
(make sure u have rom.zip magisk/superuser.zip an twrp.img) on internal storage
then i wipe
dalvik cache
cache
data (NOT FORMAT)
system
then i flash
rom.zip
twrp.img
then i reboot recovery
fkash magisk.zip
then reboot system
now i have new rom an still have twrp on
Click to expand...
Click to collapse
Would you mind stating the version of Magisk?
Strange Guide no Attention for Unlok Bl.
barrielui said:
Would you mind stating the version of Magisk?
Click to expand...
Click to collapse
16.4
magisk has been working fine for me for a while
samwise110712 said:
what issues do you get with magisk? I was able to flash it without any issues.
Click to expand...
Click to collapse
What's your ROM version? I flash twrp then magisk, bootloop...
-fluffy- said:
MAKE SURE U HAVE UNLOCKED BOOTLOADER
here is wat i do
first i boot into twrp
(make sure u have rom.zip magisk/superuser.zip an twrp.img) on internal storage
then i wipe
dalvik cache
cache
data (NOT FORMAT)
system
then i flash
rom.zip
twrp.img
then i reboot recovery
fkash magisk.zip
then reboot system
now i have new rom an still have twrp on
Click to expand...
Click to collapse
Hello how did you flash the TWRP through the TWRP ???
What version of MiUi you have ???
omek07 said:
Hello how did you flash the TWRP through the TWRP ???
What version of MiUi you have ???
Click to expand...
Click to collapse
simple put twrp.img on ur storage
then flash img from twrp
-fluffy- said:
simple put twrp.img on ur storage
then flash img from twrp
Click to expand...
Click to collapse
Yes but its asking after in which partition.
What partition you chose ?
---------- Post added at 08:26 AM ---------- Previous post was at 07:41 AM ----------
-fluffy- said:
simple put twrp.img on ur storage
then flash img from twrp
Click to expand...
Click to collapse
Could you please tell me what rom you have ???
Thank you
omek07 said:
Yes but its asking after in which partition.
What partition you chose ?
---------- Post added at 08:26 AM ---------- Previous post was at 07:41 AM ----------
Could you please tell me what rom you have ???
Thank you
Click to expand...
Click to collapse
u choose recovery
im using miui eu
magisk is running without any issue.
i am on the newest xiaomi eu beta rom and flashed magisk 16.7 without any issue right now
(after waiting horrible 15 days for unlocking the bootloader)
Ok so both of you have the xiaomi eu. I have global stable 9.5.11. so maybe that's the problem
---------- Post added at 06:30 AM ---------- Previous post was at 06:29 AM ----------
So both of you have xiaomi eu rom. I have global stable 9.5.11. maybe that's the problem.
omek07 said:
Ok so both of you have the xiaomi eu. I have global stable 9.5.11. so maybe that's the problem
---------- Post added at 06:30 AM ---------- Previous post was at 06:29 AM ----------
So both of you have xiaomi eu rom. I have global stable 9.5.11. maybe that's the problem.
Click to expand...
Click to collapse
I have the lastest global version, I cannot get the root access...
Someone tell me flash the Chinese verision then flash xiaomi.eu and magisk.
felixrao said:
I have the lastest global version, I cannot get the root access...
Someone tell me flash the Chinese verision then flash xiaomi.eu and magisk.
Click to expand...
Click to collapse
My friend i changed to the Xiaomi eu and everything worked. You dont have to flash the Chinese Version first you can go from Global to Xiaomi.eu. Just dont forget to do FORMAT data and not only Wipe Data.