Related
Hi all,
found out how to root this device!
Here the steps:
Make sure you have fastboot installed on your computer: https://wiki.cyanogenmod.org/w/Fastboot
download supersu zip from here
https://download.chainfire.eu/696/supersu/
save it to your external sdcard
enable developer options (settings - about - click mutliple times on the build number).
enable OEM unlock in the developer options settings on the device.
reboot Wileyfox Swift into fastboot mode: with the device powered down, hold the Volume Up and connect USB
to unlock the boot loader, WARNING!!! This wipes your user data!!!
on your computer type
Code:
fastboot oem unlock
fastboot -i 0x2970 oem unlock-go
fastboot oem unlock-go
download latest recovery image from here
http://download.cyanogenmod.org/?device=crackling
to boot the custom recovery, on your computer type
Code:
fastboot boot <name_of_recovery>.img
OR
install recovery
Code:
fastboot flash recovery <name_of_recovery>.img
and reboot into recovery manually (remove and reinstall battery, hold volume down and power buttons.
install supersu update zip from recovery menu (choose zip from extenal SD)
reboot and enjoy root access
Thanks
I went a step forward and installed the CM nightly.
mermigas said:
Thanks
I went a step forward and installed the CM nightly.
Click to expand...
Click to collapse
Does the camera work? I tried one of the first nightlies but the camera crashed, so this was no option for me.
olli_o said:
Does the camera work? I tried one of the first nightlies but the camera crashed, so this was no option for me.
Click to expand...
Click to collapse
No problem with camera for me.
All works fine and smooth
No bugs nored
olli_o said:
4) reboot directly into recovery. Normal system boot reinstalls stock recovery.
5) install supersu update zip from recovery menu
Click to expand...
Click to collapse
When in recovery I press apply update and sd card, before i've even selected supersu, which returns:
Install failed
Installation aborted
Installation aborted
any ideas?
monethys said:
When in recovery I press apply update and sd card, before i've even selected supersu, which returns:
Install failed
Installation aborted
Installation aborted
any ideas?
Click to expand...
Click to collapse
This is stange. I modified the instructions a little, does it also happen if you follow these steps?
OTA?
Will I be able to update my phone (ota?) after the root?
I'm fine with having to reroot
rebane2001 said:
Will I be able to update my phone (ota?) after the root?
I'm fine with having to reroot
Click to expand...
Click to collapse
Incremental auto-update won't work rooted. But you can manually update. See here
Followed instructions and now have a rooted wileyfox swift thank you
olli_o said:
Hi all,
found out how to root this device!
Here the steps:
download supersu zip from here
save it to your external sdcard
enable developer options (settings - about - click mutliple times on the build number).
enable OEM unlock in the developer options settings on the device.
reboot Wileyfox Swift into fastboot mode: with the device powered down, hold the Volume Up and connect USB
to unlock the boot loader, WARNING!!! This wipes your user data!!!
on your computer type
Code:
fastboot oem unlock
fastboot -i 0x2970 oem unlock-go
fastboot oem unlock-go
download latest recovery image from here
to boot the custom recovery, on your computer type
Code:
fastboot boot <name_of_recovery>.img
install supersu update zip from recovery menu (choose zip from extenal SD)
reboot and enjoy root access
Click to expand...
Click to collapse
In case anyone has a similar issue:
I could unlock. I could install the recovery. But SuperSU was coming up with signature errors and wouldn't install. I discovered that this was because the recovery was being overwritten (I flashed it to the device because "fastboot boot..." was not working).
I could not get the device to flash the recovery then reboot to recovery without it going into normal boot first and rewriting the recovery so that I would not be able to install SU.
The solution I found for this was to take the back of the phone off.
Flash the recovery: fastboot flash recovery "recovery file name".img
Then just pull the battery.
Hold the volume down when you put the battery back in and launch the device still holding volume down.
Remember to release the power button once you see fox logo or you'll reboot again.
Now I installed SuperSU without a hitch and all is good.
Hope that helps anyone who is stuck.
Links removed from quote so as not to trigger spam bot.
Help
olli_o said:
Hi all,
found out how to root this device!
[*]download latest recovery image from here
/download.cyanogenmod.org/?device=crackling[/
[/LIST]
Click to expand...
Click to collapse
All the list from here is a nightly build. Can you give the stable mod? I'm noob so can follow it. it is very hard for me to make it work I'm still working to install the fast boot for mac. I found this:
bash <(curl -s htps:/raw.githubusercontent.com/corbindavenport/nexus-tools/master/install.sh)
It seems to work when i check this command:
adb devices
BUT NOT SURE if this is safe.
Please provide link for recovery or rom which i can follow using your guide. There are many in the link above but which one is stable and i can use that all the of the system functioning.
Thank you in advance.
I hope this will help someone figure things out w/ what i did... LOL
Thanks ALL. Basically the post above helped to root my phone but its been hard for me and as mentioned in my previous post, I'm noob. So here is what i did after the fastboot issue and continue on even though i didn't know if the install is safe since my OS X was able to detect the device/phone as mentioned above.
1. On fastboot, i just use "fastboot devices" to verify my phone is connected. This command did not work "fastboot -i 0x2970 devices"
2. Then use, "fastboot oem unlock-go" and i waited about 20sec as the terminal returned that message and then it was confirmed unlocked. These commands did not work "fastboot oem unlock, fastboot -i 0x2970 oem unlock-go" my terminal just froze and did nothing.
3. Then i use this to check if it is unlocked "fastboot oem device-info"
4. Using the link on downloading the recovery, i just click all of upper part with the picture and found the .img file see below:
Swift
Wileyfox - crackling
Download Latest Nightly (this is .zip file)
Download Latest Nightly Recovery (this is the .img file which i used)
Device Wiki 2016-01-07
5. update: i did erase recovery "fastboot erase recovery"
i use two commands and both works "fastboot flash recovery cm-12.1-20160107-NIGHTLY-crackling-recovery.img"
(here is the terminal msg: target reported max download size of 268435456 bytes
sending 'recovery' (23110 KB)...
OKAY [ 0.727s]
writing 'recovery'...
OKAY [ 0.387s]
finished. total time: 1.114s)
and this "fastboot boot cm-12.1-20160107-NIGHTLY-crackling-recovery.img"
(here is the terminal msg:downloading 'boot.img'...
OKAY [ 0.727s]
booting...
OKAY [ 0.186s]
finished. total time: 0.913s)
(I LEARNED THE HARD WAY THE .img file must be IN THE SAME DIRECTORY of the fastboot - but PLEASE ASK THE EXPERTS and don't copy if i did something wrong)
6. Next should be the auto reboot that suppose to happen but it didn't. So i took " k_web9000" advice and just pull the battery off (i didn't have any choice its not doing anything... heheh).
6. To boot in Recovery - i followed this :With the device powered down, hold the Volume Down and Power buttons.
7. Next should install the SuperSU.zip file (Please make sure to use chrome since my Safari auto unzip the file and wasted so much of my time troubleshooting... i mean hours retracing my steps ...funny) Just update it and locate the sdcard and look for the .zip file
8. Then it just rebooted after the install and on the boot screen i saw 4 files that where updated.
9. Finally, i checked for the root by downloading root checker and it was verified rooted.
Now you have been noobified
A SYSTEM UPDATE POP-UP 12.1 YOG7DAS2FI Incremental about 48MB BUT DIDNT TOUCH IT, What do i need do? Can i update?
PLEASE LET ME KNOW HOW TO UPDATE TO THE LATEST ONE WITHOUT LOSING MY ROOT.
OR HOW TO INSTALL CYANOGENMOD easy way please . i can see CYANOGEN OS 12.1-YOG4PAS33J on my device
PLEASE HELP. THANKS
You cannot update whilst you are rooted.
If you want to have the latest then CM Nightly is your best option.
How to
https://wiki.cyanogenmod.org/w/Install_CM_for_crackling
How?
mermigas said:
You cannot update whilst you are rooted.
If you want to have the latest then CM Nightly is your best option.
How to
]https://wiki.cyanogenmod.org/w/Install_CM_for_crackling]
Click to expand...
Click to collapse
Thanks for the info and link!! Awesome!
" 4. In ClockworkMod Recovery, use the physical volume buttons to move up and down. On most devices, the power button is used to confirm a menu selection, but for some devices a physical home key acts as a selector. Some devices have touch enabled ClockworkMod Recovery, in which case you may be able to swipe to, or touch, menu selections.
5. Optional (Recommended): Select backup and restore to create a backup."
In the link you gave, how did they get the clockworkmod recovery? I downloaded & installed it in the google store but it say can not use due to the device not listed. All icons are grayed and i also tried TWRP same issue.
The link also pointed to the nightly build, is there a stable release, doesn't need much update, i can use daily and without the hiccups.
Lastly, if there is no clockworkmod, how do you get it backup as recommended in the link you gave and as quoted above.
Many thanks in advance.
There is only official CM recovery and back up is not possible. Use Titaniumfor back up. You can also use twrp recovery posted in general section. Nightlies are more than stable.
Something is not right...
mermigas said:
You cannot update whilst you are rooted.
If you want to have the latest then CM Nightly is your best option.
How to
https://wiki.cyanogenmod.org/w/Install_CM_for_crackling
Click to expand...
Click to collapse
i was afraid of updating coz my data might be deleted but it seems the OTA update didn't delete my data. My version now is 13.0-20160127-NIGHTLY-crackling but the downside is the google play is not present anymore. i will try install the gapp again.
i don't know if i did it right, some say you need TWRP but it works just fine w/o TWRP in updating via OTA. I also try to install TWRP but i can't get it to work, so i can backup my phone. Last option is what you suggested the titanium backup.
Please let me know if i did right and the gapp if this always going to be installed again. i will be using the same gapp file and report what happen. thanks
Report:
i tried to install gapp file but i didn't use the previous gappfile since the it needs for 6.0 android and i used arm64 but gave error:70 which is the space issue via emulated option. So i go to cyangenmod recovery>apply update> from sdcard1 and "install failed - installation aborted". I can't even see the files on my sdcard. How do you now fix this?
Also can i have the right TWRP file and instruction for Wileyfox Swift PLEASE? thanks
Something went wrong! Please help
I can't to get the gapp to installed.
I wipe everything using the cm recovery and i also was able to install TWRP recovery and it does always hangs when installing the gapp -arm64-aroma (i can choose what to install). I also reinstall 12.1 and 13 but failed again when installing any gapp even in nano version (please note that i wipe everything). in my last attempt i wipe: dalvik, system, cache, data, internal storage & android secure but nothing works to install the gapp. Btw, when i wipe from the 1st time i always get this error "e: unable to find partition size for '/recovery"
PLEASE HELP
I had a few problems doing this from Ubuntu 15.10.
1. ADB did not see the device although it worked fine on my Nexus 4 showing that adb/fastboot were configured correctly. I had to go to /home/.android and create the document 'adb_usb.ini' (right click, new document) which contains the text '0x2970'.
Once this was done I had to run the following commands
adb kill-server
adb start-server
This allowed ADB to see the device but it said that it was offline.
2. I had to create the file /etc/udev/rules.d/51-android.rules (type into terminal 'sudo nano /etc/udev/rules.d/51-android.rules') and paste in the following line, save it (ctrl+x, y, enter).
SUBSYSTEM=="usb", ATTR{idVendor}=="2970", ATTR{idProduct}=="2282", MODE="0666"
sudo service udev restart
After this ADB and fastboot recognized the device and allowed me to follow the directions posted above or on the cyanogenmod wiki.
Hope that is of some use to someone!!!
Also the Cyanogen Recovery was both unpleasant to use and caused problems trying to install GApps, I had to switch to using the unofficial TWRP recovery which worked first time and is a much better interface.
Hey do we need to unlock a bootloader before installing the custom recovery on this device? Thanks.
So i unlock and install twrp on my xiaomi redmi note 5 pro, twrp works fine on my device nothing wrong with it, but the next day when i try to open it instead of opening twrp but it's directing me to mi recovery (stock recovery), and i tried to re install twrp again on my device i thought the issues gone, well it works for few times, but later when i came back to twrp it directing me to mi recovery again, I don't know what to do, is there any solution for this? Or i should boot manually on my pc everytime i want to open twrp? Any answers will be appreciated.
Sorry for my grammar and coma replacement
Me too
kamisama06 said:
So i unlock and install twrp on my xiaomi redmi note 5 pro, twrp works fine on my device nothing wrong with it, but the next day when i try to open it instead of opening twrp but it's directing me to mi recovery (stock recovery), and i tried to re install twrp again on my device i thought the issues gone, well it works for few times, but later when i came back to twrp it directing me to mi recovery again, I don't know what to do, is there any solution for this? Or i should boot manually on my pc everytime i want to open twrp? Any answers will be appreciated.
Sorry for my grammar and coma replacement
Click to expand...
Click to collapse
Had the same issue. When you flash recovery, boot back into recovery and than flash lazyflasher.zip. The recovery won't be replaced with stock recovery. I even mentioned about it when I faced same issue. Check my old post.
https://forum.xda-developers.com/showpost.php?p=76939231&postcount=125
That's because of anti-rollback feature.
In July MiUi was released with anti roll back feature, which prohibits to go back to previous versions of MiUi.
However your problem can be solved with these steps.
1) Download "twrp.img" in RN5P and PC both.
2) Boot into fastboot mode and connect it to the PC.
3) Browse the folder where you have "twrp.img" in PC, and flash it,(I hope you know, how to do that.).
4) Boot into twrp by command "fastboot boot twrp.img" (in Linux use "sudo" before above command incase of permission deficiency)
5) Now your phone will boot into Twrp recovery. Here click on install.
6) In lower right corner you'll see "Install image" button. Click on that. Now browse to the folder you have stored "Twrp.img" in your phone. Install it, select "Recovery" when asked.
That's it. It will be installed permanently untill you reflash any MiUi ROM further after.
magzetic said:
In July MiUi was released with anti roll back feature, which prohibits to go back to previous versions of MiUi.
However your problem can be solved with these steps.
1) Download "twrp.img" in RN5P and PC both.
2) Boot into fastboot mode and connect it to the PC.
3) Browse the folder where you have "twrp.img" in PC, and flash it,(I hope you know, how to do that.).
4) Boot into twrp by command "fastboot boot twrp.img" (in Linux use "sudo" before above command incase of permission deficiency)
5) Now your phone will boot into Twrp recovery. Here click on install.
6) In lower right corner you'll see "Install image" button. Click on that. Now browse to the folder you have stored "Twrp.img" in your phone. Install it, select "Recovery" when asked.
That's it. It will be installed permanently untill you reflash any MiUi ROM further after.
Click to expand...
Click to collapse
6) In lower right corner you'll see "Install image" button. Click on that. Now browse to the folder you have stored "Twrp.img" in your phone. Install it, select "Recovery" when asked.
It's asking which partition should it be flashed boot or recovery?
deathbearer said:
6) In lower right corner you'll see "Install image" button. Click on that. Now browse to the folder you have stored "Twrp.img" in your phone. Install it, select "Recovery" when asked.
It's asking which partition should it be flashed boot or recovery?
Click to expand...
Click to collapse
Recovery bro
magzetic said:
In July MiUi was released with anti roll back feature, which prohibits to go back to previous versions of MiUi.
However your problem can be solved with these steps.
1) Download "twrp.img" in RN5P and PC both.
2) Boot into fastboot mode and connect it to the PC.
3) Browse the folder where you have "twrp.img" in PC, and flash it,(I hope you know, how to do that.).
4) Boot into twrp by command "fastboot boot twrp.img" (in Linux use "sudo" before above command incase of permission deficiency)
5) Now your phone will boot into Twrp recovery. Here click on install.
6) In lower right corner you'll see "Install image" button. Click on that. Now browse to the folder you have stored "Twrp.img" in your phone. Install it, select "Recovery" when asked.
That's it. It will be installed permanently untill you reflash any MiUi ROM further after.
Click to expand...
Click to collapse
After doing this I can't access my recovery via Vol up + power. But still can boot it via adb command
magzetic said:
In July MiUi was released with anti roll back feature, which prohibits to go back to previous versions of MiUi.
However your problem can be solved with these steps.
1) Download "twrp.img" in RN5P and PC both.
2) Boot into fastboot mode and connect it to the PC.
3) Browse the folder where you have "twrp.img" in PC, and flash it,(I hope you know, how to do that.).
4) Boot into twrp by command "fastboot boot twrp.img" (in Linux use "sudo" before above command incase of permission deficiency)
5) Now your phone will boot into Twrp recovery. Here click on install.
6) In lower right corner you'll see "Install image" button. Click on that. Now browse to the folder you have stored "Twrp.img" in your phone. Install it, select "Recovery" when asked.
That's it. It will be installed permanently untill you reflash any MiUi ROM further after.
Click to expand...
Click to collapse
I cam confirm that doing step 6 will prevent stock recovery (MIUI) from replacing TWRP.
Another way will be to flash lazyflasher if I'm not wrong but I never have to do it.
Can this work when official ROM is intalled?
is this normal after flashin the twrp ?
No,you didn't make the correct actions and twrp got replaced by stock.Do it again and be sure to make all actions.(Including dumb file etc)
After installing recovery, flash magisk,that's all
copy the twrp .img file in to phone's sd card
boot recovery via fastboot from pc
using cmd
fastboot boot filename.img
after the boot from pc it enters twrp ,then also flash the twrp .img from sd card
thats all
Guys after a little research I figured out that thing at the photo is redmi's 4 series control panel and when I choose the recovery option, it normally enters in TWRP. So after all , I'm good . [emoji868][emoji1690]
Στάλθηκε από το Redmi Note 6 Pro μου χρησιμοποιώντας Tapatalk
guys, i cant see the recovery partition in the list of "select which partition to flash to" when trying to flash twrp. All that's there are: boot, dtbo, vendor image, system image, boot logo, vbmeta partitions only
Followed the instructions here for Rooting and fastbooting to TWRP. Could not locate the Download folder where I put Magisk, so rebooted and put it in a few other folders. Rebooted back to TWRP image and still cannot the Magisk zip or extracted files anywhere. Switched to the B partition and looked around there with no luck. Then went to reboot in TWRP. Now I have a spinning white screen with the "scrolling G" ...15 minutes and counting.
How do I get it out of this stuck boot.
Why can I not find the Download or Android folders in TWRP File Manager where I put Magisk?
Thanks
Downloads from your phone should be in /sdcard/downloads.
If you are stuck with a non-booting system, you need to flash the factory image, you can try to flash it and remove the '-w' from flash-all.bat to keep your data.
Edit: btw to root stock, simply boot twrp image and flash magisk.zip, then reboot system. You can then boot twrp and flash twrp.zip if desired.
boostedduece said:
Downloads from your phone should be in /sdcard/downloads.
If you are stuck with a non-booting system, you need to flash the factory image, you can try to flash it and remove the '-w' from flash-all.bat to keep your data.
Edit: btw to root stock, simply boot twrp image and flash magisk.zip, then reboot system. You can then boot twrp and flash twrp.zip if desired.
Click to expand...
Click to collapse
From what I recall, in the /sdcard/ I had 2 folders /0/ and /00b/? Both had "scrambled" folder names within, nothing that was Download or the like.
So, it's been at least an hour and I still have the scrolling boot screen. In hindsight I recall I went to B before restarting. Can't see device from ADB. Tried the previous Nexus methods of holding power and up/down keys...still white screen G with scroll. Edit: I tried again holding Power and it will now shut off. Holding volume down and power I can get to the boot menu and see Fast Mode. It won't boot on it's own, but I can get to the boot menu. So I'll try connecting again in the morning. Edit #2: after trying recovery and power button a few times the phone booted.
So it looks like I am back to finding Magisk in the Download folder-which I copied from my computer to the Download folder on the 3xl. I installed ES File Explorer and see the zips are in storage/emulated/0/Download but I do not see Download after I reboot with the TWRP image.
There is one /sdcard folder, the other 2 in /storage/emulated/.. have different attributes, but I recommend dealing with /sdcard.
Sounds like it did not decrypt the partition in twrp, that's why the names were garbled.
Holding both volume buttons and power for a while should hard shutdown the device.
You should be able to get to bootloader from power + volume down, flash-all.bat should work from here, you are definitely not bricked though.
Still unable to locate Download Folder
So, I can get the phone to boot and reboot.
From a command prompt:
adb devices (device is available)
adb reboot bootloader
fastboot boot twrp-3.2.2-3-crosshatch.img
Boots to TWRP asking for password, I hit cancel.
It then asks if I want write protection. Initially, I went this route, but tried again allowing full access.
I can see /sdcard/ and 2 folders /0/ and /0bb/, /0bb/ is empty.
when I go into /0/ the folder names are scrambled. Some have sub-folders that are also scrambled.
Why are the names scrambled? Where is my Download folder with my .zip and unzip files?
vette8t7 said:
So, I can get the phone to boot and reboot.
From a command prompt:
adb devices (device is available)
adb reboot bootloader
fastboot boot twrp-3.2.2-3-crosshatch.img
Boots to TWRP asking for password, I hit cancel.
It then asks if I want write protection. Initially, I went this route, but tried again allowing full access.
I can see /sdcard/ and 2 folders /0/ and /0bb/, /0bb/ is empty.
when I go into /0/ the folder names are scrambled. Some have sub-folders that are also scrambled.
Why are the names scrambled? Where is my Download folder with my .zip and unzip files?
Click to expand...
Click to collapse
You have to enter your password that unlocks your phone when you first boot into TWRP so that it can decrypt your phone. Don't hit cancel
vette8t7 said:
So, I can get the phone to boot and reboot.
From a command prompt:
adb devices (device is available)
adb reboot bootloader
fastboot boot twrp-3.2.2-3-crosshatch.img
Boots to TWRP asking for password, I hit cancel.
It then asks if I want write protection. Initially, I went this route, but tried again allowing full access.
I can see /sdcard/ and 2 folders /0/ and /0bb/, /0bb/ is empty.
when I go into /0/ the folder names are scrambled. Some have sub-folders that are also scrambled.
Why are the names scrambled? Where is my Download folder with my .zip and unzip files?
Click to expand...
Click to collapse
TWRP is failing to decrypt your phone. This used to be a big issue, but has been solved for some time. What version of TWRP are you using?
@vette8t7 if you haven't figured this out yet, as others have said, twrp is not decrypting your device. If you haven't you'll need to boot into your system and enable a pin security. Without that twrp doesn't have any info to decrypt your device.
Sent from my [device_name] using XDA-Developers Legacy app
hatdrc said:
You have to enter your password that unlocks your phone when you first boot into TWRP so that it can decrypt your phone. Don't hit cancel
Click to expand...
Click to collapse
Oh man, THAT makes sense. I thought it was wanting me to create one and I didn't want to have to track ANOTHER password.
Okay, I'm in, see Downloads and .zip files!!:good:
hatdrc said:
You have to enter your password that unlocks your phone when you first boot into TWRP so that it can decrypt your phone. Don't hit cancel
Click to expand...
Click to collapse
vette8t7 said:
Oh man, THAT makes sense. I thought it was wanting me to create one and I didn't want to have to track ANOTHER password.
Okay, I'm in, see Downloads and .zip files!!:good:
Click to expand...
Click to collapse
Geez, back in the day I unlocked and rooted my Galaxy Nexus without issue and did most of the same on a Note 4. Didn't really have a need to do either on my Nexus 6p-which I have gone back to using while I straighten out the 3XL. I'd leave the 3XL alone except I need to unlock and root to run the commands to prevent the service check for hotspot on my Verizon GUDP. The 6p has gotten sluggish as of late, thus the 3XL upgrade.
So...I found my Magisk-v18.0.zip (the non-beta) in TWRP after entering the passcode. Hit install. It went through to restart adn white screen scrolling G and now I keep landing on an Android Recovery page:
google/crosshatch/crosshatch
9/PQ1A.181205.006/5108886
user/release-keys
Use volume up/down and power.
Can't load Android System. Your data may be corrupt. If you continue to get this message, you may need to perform a factory reset and erase all user data stored on this device.
Try again
Factory data reset.
So after trying the "Try again" and it try to load and then reboots and tries to load and I come to the same screen above.
I finally tried selecting "Factory data reset" only to come to the same menu.
I was able to run fastboot from the cmd and run twrp-3.2.3-3-crosshatch.img again.
In /sdcard/ I have an empty /obb/ and an empty /TWRP/ folder.
Performed an adb push of magisk.zip and twrp.zip to /0bb/directory and this time performed magisk followed by twrp install and now I get the Google setup window..I don't see Magisk installed.
vette8t7 said:
Geez, back in the day I unlocked and rooted my Galaxy Nexus without issue and did most of the same on a Note 4. Didn't really have a need to do either on my Nexus 6p-which I have gone back to using while I straighten out the 3XL. I'd leave the 3XL alone except I need to unlock and root to run the commands to prevent the service check for hotspot on my Verizon GUDP. The 6p has gotten sluggish as of late, thus the 3XL upgrade.
So...I found my Magisk-v18.0.zip (the non-beta) in TWRP after entering the passcode. Hit install. It went through to restart adn white screen scrolling G and now I keep landing on an Android Recovery page:
google/crosshatch/crosshatch
9/PQ1A.181205.006/5108886
user/release-keys
Use volume up/down and power.
Can't load Android System. Your data may be corrupt. If you continue to get this message, you may need to perform a factory reset and erase all user data stored on this device.
Try again
Factory data reset.
So after trying the "Try again" and it try to load and then reboots and tries to load and I come to the same screen above.
I finally tried selecting "Factory data reset" only to come to the same menu.
Any ideas what I did now and how I get out of it?
Click to expand...
Click to collapse
I'd start fresh by flashing the factory image by running the flash-all batch file. BUT, edit it first to remove the -w you'll see a number of times down. If you don't your device will be wiped. Then boot twrp with fastboot boot, don't flash it. Then install magisk within twrp. If you want to keep twrp permanently then install the twrp zip file. I generally install twrp, then boot back into recovery and then install magisk.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
I'd start fresh by flashing the factory image by running the flash-all batch file. BUT, edit it first to remove the -w you'll see a number of times down. If you don't your device will be wiped. Then boot twrp with fastboot boot, don't flash it. Then install magisk within twrp. If you want to keep twrp permanently then install the twrp zip file. I generally install twrp, then boot back into recovery and then install magisk.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I've gotten to the point where TWRP is installed. If I install TWRP.zip I can get the phone to boot to an image that doesn't appear to have Magisk installed. So I installed the Magisk Manager. It indicates Magisk isn't installed. So I reboot into TWRP select Magisk v18 and install, then reboot system. The phone will go to the Google white screen spin for a bit and then reboot to TWRP. If I install the twrp.zip I can get back into the phone and see Magisk still isn't installed. Ihave tried combinations of installing TWRP.zip then Magisk.zip and vice versa, but I never seem to get Magisk installed.
I've seen mention of the flash-all batch, but I don't seem to have it in anything I have downloaded from these two guides:
https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
I see it in #4 here: https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-xl-android-9-0-pie-unlock-t3857195
so I'll try what you suggest.
vette8t7 said:
I've gotten to the point where TWRP is installed. If I install TWRP.zip I can get the phone to boot to an image that doesn't appear to have Magisk installed. So I installed the Magisk Manager. It indicates Magisk isn't installed. So I reboot into TWRP select Magisk v18 and install, then reboot system. The phone will go to the Google white screen spin for a bit and then reboot to TWRP. If I install the twrp.zip I can get back into the phone and see Magisk still isn't installed. Ihave tried combinations of installing TWRP.zip then Magisk.zip and vice versa, but I never seem to get Magisk installed.
I've seen mention of the flash-all batch, but I don't seem to have it in anything I have downloaded from these two guides:
https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
I see it in #4 here, so I'll try what you suggest.
Click to expand...
Click to collapse
I assume you've found the factory image and extracted the zip file. In there is the flash-all.bat. Edit that, notepad++ is a good editor. Save the file after you've edit it and run that. Make sure you save it or you'll run the unedited version. Then start the process of booting twrp and installing magisk.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
I assume you've found the factory image and extracted the zip file. In there is the flash-all.bat. Edit that, notepad++ is a good editor. Save the file after you've edit it and run that. Make sure you save it or you'll run the unedited version. Then start the process of booting twrp and installing magisk.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yes, found the factory image and extracted the zip. Is started to take the -w out and yes, Notepad++), but decided to leave it in to start fresh. I put the phone in Fastboot. Ran the flash-all, it worked for a while and then indicated there waasn't a recovery.img and a few other things and then "ended" with any key to exit. So I restarted to find everything was still there. So I rebooted to TWRP and installed the Magisk.zip, only to result in the same boot and restart into TWRP. So, convinced the factory image didn't wipe I performed that step again. Boot phone to Fastboot. Opened a command prompt in the image directory. flash-all. It ran for a while complained about the few .img files, but seemed to do more than it did the first time. This time I reloaded the boot loader and fastboot boot twrp.img only to go in and find I still had file in the Download folder (I was expecting to push them from a wipe). So of course when I install magisk.zip and restart it goes to the white google spinning rescreen and eventually restarts back into TWRP.
Your instructions lineup with #4 and 7 or 8 here: https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-xl-android-9-0-pie-unlock-t3857195
For some reason I can't seem to wipe for 1 and ever get Magisk to install 2. Of course my phone has the December OTA update if that has added any new variables here?
I reran this flash-all again to a log file (attached).
vette8t7 said:
Yes, found the factory image and extracted the zip. Is started to take the -w out and yes, Notepad++), but decided to leave it in to start fresh. I put the phone in Fastboot. Ran the flash-all, it worked for a while and then indicated there waasn't a recovery.img and a few other things and then "ended" with any key to exit. So I restarted to find everything was still there. So I rebooted to TWRP and installed the Magisk.zip, only to result in the same boot and restart into TWRP. So, convinced the factory image didn't wipe I performed that step again. Boot phone to Fastboot. Opened a command prompt in the image directory. flash-all. It ran for a while complained about the few .img files, but seemed to do more than it did the first time. This time I reloaded the boot loader and fastboot boot twrp.img only to go in and find I still had file in the Download folder (I was expecting to push them from a wipe). So of course when I install magisk.zip and restart it goes to the white google spinning rescreen and eventually restarts back into TWRP.
Your instructions lineup with #4 and 7 or 8 here: https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-xl-android-9-0-pie-unlock-t3857195
For some reason I can't seem to wipe for 1 and ever get Magisk to install 2. Of course my phone has the December OTA update if that has added any new variables here?
I reran this flash-all again to a log file (attached).
Click to expand...
Click to collapse
- first, make sure you have the latest SDK Platform-tools r28.0.1 (see guide 'Prerequisites c.' for link).
- extract the December factory image in the Platform-tools folder.
- Open a command prompt in the Platform-tools folder.
- type flash-all at the prompt.
- when it finishes, do #8 for root.
Homeboy76 said:
- first, make sure you have the latest SDK Platform-tools r28.0.1 (see guide 'Prerequisites c.' for link).
- extract the December factory image in the Platform-tools folder.
- Open a command prompt in the Platform-tools folder.
- type flash-all at the prompt.
- when it finishes, do #8 for root.
Click to expand...
Click to collapse
I have the r28.0.1
I was researching the Image and I had downloaded and used the A1.docomo, which, as jd1639 pointed out in another thread is for japanese phones. I've just finished downloading the non-docomo for December and see where I get.
Oh, now I see what I am doing wrong. The image .zip needs to be extracted into the platform folder. I noticed you said run the command from "platform-tools" folder.
vette8t7 said:
I have the r28.0.1
I was researching the Image and I had downloaded and used the A1.docomo, which, as jd1639 pointed out in another thread is for japanese phones. I've just finished downloading the non-docomo for December and see where I get.
Click to expand...
Click to collapse
If you have r28.0.1 where is the Platform-tools folder?
---------- Post added at 05:54 AM ---------- Previous post was at 05:50 AM ----------
vette8t7 said:
I have the r28.0.1
I was researching the Image and I had downloaded and used the A1.docomo, which, as jd1639 pointed out in another thread is for japanese phones. I've just finished downloading the non-docomo for December and see where I get.
Oh, now I see what I am doing wrong. The image .zip needs to be extracted into the platform folder. I noticed you said run the command from "platform-tools" folder.
Click to expand...
Click to collapse
Yes, the Factory image zip needs to be extracted to the Platform-tools folder.
Homeboy76 said:
If you have r28.0.1 where is the Platform-tools folder?
C:\adb\platform-tools_r28.0.1-windows\platform-tools
Within that is adb, fastboot, twrp-pixel-installer-crosshatch-3.2.3-3.img (renamed twrp.img), december factory image (extracted) as well as the Magisk-v18.0.zip and twrp.zip (for copying or pushing)
---------- Post added at 05:54 AM ---------- Previous post was at 05:50 AM ----------
Yes, the Factory image zip needs to be extracted to the Platform-tools folder.
Click to expand...
Click to collapse
So once the factory image is done, I go through setup (skipping through most for later) to get the usb debugging enabled and copy Magisk.zip and twrp.zip.
adb reboot bootloader
fastboot boot twrp.img
put in passcode
Swiped to allow for modifications
First time I just installed the magisk.zip only to have it reboot twice into the loop of my #10 post again.
The second time I repeated the whole factory image process up to fastbooting twrp.img and this time installed twrp.zip, reboot recovery, install Magisk-v18.0.zip. Reboot system. It boots and No Magisk in the app tray! Err...well now it is there and it shows Magisk installed!
Holy Moly what a PITA!! On a positive note, I kind of refreshed some of this stuff I hadn't done in years :good:
I got stuck a couple of months back when my wife's nexus 6p died (not battery-which I later swapped into mine), something with the processor board. I got a Verizon 3XL with the locked bootloaderL...so if anything ever develops there, I can root that phone for the GUDP hotspot as well.
I followed the steps here: https://forum.xda-developers.com/pixel-3-xl/how-to/how-to-native-tethering-rooted-pixel-3-t3858662
So far, so good. Great Success! Thanks for your help!
homeboy76 said:
If you have r28.0.1 where is the Platform-tools folder?
Click to expand...
Click to collapse
vette8t7 said:
C\adb\platform-tools_r28.0.1-windows\platform-tools
Within that is adb, fastboot, twrp-pixel-installer-crosshatch-3.2.3-3.img (renamed twrp.img), december factory image (extracted) as well as the Magisk-v18.0.zip and twrp.zip (for copying or pushing)
Click to expand...
Click to collapse
"twrp-pixel-installer-crosshatch-3.2.3-3.img (renamed twrp.img)"
I think you mean 'twrp-3.2.3-3-crosshatch.img (renamed twrp.img)
vette8t7 said:
...The second time I repeated the whole factory image process up to fastbooting twrp.img and this time installed twrp.zip, reboot recovery, install Magisk-v18.0.zip. Reboot system. It boots and No Magisk in the app tray! Err...well now it is there and it shows Magisk installed!...
Click to expand...
Click to collapse
@vette8t7
Yes
While waiting for a working TWRP for all those needful of the possibility to access their file system from recovery, e.g. for removing an offensive magisk extension preventing boot I repackaged the Stock OOS recovery from the 10.0.1BA package but with ADB enabled.
Prerequisites:
Oneplus 7T Pro
unlocked bootloader
access to fastboot on the phone
adb and fastboot
Installation:
Reboot the phone to fastboot, then flash the recovery from fastboot with the command
Code:
fastboot flash recovery
(when taking the file as downloaded the filename is "OP7TP_StockRecovery_ADB_nosec.img")
Uninstall:
Same as installation, but flash the original stock recovery instead.
Usage:
Boot up recovery, enter encryption key if file system is encrypted. Then connect the phone to PC and you are ready to go with adb. E.g. by using
Code:
adb shell
to open a shell and access the file system. Magisk modules are located in /data/adb/modules, deleting the corresponding directory there will remove the module in question.
Downloads:
10.0.3BA Recovery
Modified 10.0.3BA recovery from GDrive
Original 10.0.3BA stock recovery from Gdrive
10.0.4BA Recovery
Modified 10.0.4BA recovery from GDrive
Original 10.0.4BA stock recovery from Gdrive
10.0.7BA Recovery
Modified 10.0.7BA recovery from GDrive
Original 10.0.7BA stock recovery from Gdrive
Open Beta 1 Recovery
Modified OB1 recovery from GDrive
Open Beta 2 Recovery
Modified OB2 recovery from GDrive
Notes of caution:
ADB security is disabled as I could not get the recovery to allow for authorizing a connected computer. As a consequence any computer connected is automatically authorized in ADB, although with encrypted filesystem at least no data is accessible without the key.
with direct ADB access to your file system you can easily wreck you phone requiring a factory reset or even reinstallation of the OS from fastboot - please be careful on what you are doing
Credits: Thanks to osm0sis for Android kitchen and all great developers for the Oneplus devices, specifically mauronofrio for his TWRP efforts.
I just need it, thank you very much.
But this rec has a bug
After swiping in and entering REC, the interface does not need to enter a password, and the adb shell opens /data is empty.
Only the boot_a and boot_b that have not been modified by magisk are brushed in and the password is entered again after booting and re-entering rec, and the data can be modified.
但是这个rec有个BUG
刷入并进入REC后 界面不需要输入密码,并且adb shell打开/data是空的
只有刷入没有被magisk修改过的boot_a和boot_b并且开机后重新进入rec才有输入密码的界面,并且data可以修改
991547436 said:
But this rec has a bug
After swiping in and entering REC, the interface does not need to enter a password, and the adb shell opens /data is empty.
Only the boot_a and boot_b that have not been modified by magisk are brushed in and the password is entered again after booting and re-entering rec, and the data can be modified.
但是这个rec有个BUG
刷入并进入REC后 界面不需要输入密码,并且adb shell打开/data是空的
只有刷入没有被magisk修改过的boot_a和boot_b并且开机后重新进入rec才有输入密码的界面,并且data可以修改
Click to expand...
Click to collapse
English only pls?
OnePlus 7T Pro
s3axel said:
While waiting for a working TWRP for all those needful of the possibility to access their file system from recovery, e.g. for removing an offensive magisk extension preventing boot I repackaged the Stock OOS recovery from the 10.0.1BA package but with ADB enabled.
Prerequisites:
Oneplus 7T Pro
unlocked bootloader
access to fastboot on the phone
adb and fastboot
Installation:
Reboot the phone to fastboot, then flash the recovery from fastboot with the command
Code:
fastboot flash recovery <recovery_filename.img>
(when taking the file as downloaded the filename is "OP7TP_StockRecovery_ADB_nosec.img")
Uninstall:
Same as installation, but flash the original stock recovery instead.
Usage:
Boot up recovery, enter encryption key if file system is encrypted. Then connect the phone to PC and you are ready to go with adb. E.g. by using
Code:
adb shell
to open a shell and access the file system. Magisk modules are located in /data/adb/modules, deleting the corresponding directory there will remove the module in question.
Downloads: (all based on 10.0.3BA image from Oneplus)
Modified recovery from GDrive
Original stock recovery from Gdrive
Notes of caution:
ADB security is disabled as I could not get the recovery to allow for authorizing a connected computer. As a consequence any computer connected is automatically authorized in ADB, although with encrypted filesystem at least no data is accessible without the key.
with direct ADB access to your file system you can easily wreck you phone requiring a factory reset or even reinstallation of the OS from fastboot - please be careful on what you are doing
Credits: Thanks to osm0sis for Android kitchen and all great developers for the Oneplus devices, specifically mauronofrio for his TWRP efforts.
Click to expand...
Click to collapse
HolyChickenGuy said:
English only pls?
OnePlus 7T Pro
Click to expand...
Click to collapse
English is a translation. I don't know if the translation is correct.
991547436 said:
But this rec has a bug
After swiping in and entering REC, the interface does not need to enter a password, and the adb shell opens /data is empty.QUOTE]
I noticed the same behaviour when trying "fastboot boot", the recovery needs to be flashed to work.
Second I own an EU device with BA firmware/OS on it, maybe global devices with AA firmware are different...
Click to expand...
Click to collapse
Theres no flashable zip rom for twrp? Thanks
Enviado desde mi MI MAX 3 mediante Tapatalk
jorgeepelos said:
Theres no flashable zip rom for twrp? Thanks
Enviado desde mi MI MAX 3 mediante Tapatalk
Click to expand...
Click to collapse
TWRP doesn't even work for this device, and with devices launched Android 10 you can no longer flash system via TWRP.
Sent from my OnePlus7TPro using XDA Labs
Lossyx said:
TWRP doesn't even work for this device, and with devices launched Android 10 you can no longer flash system via TWRP.
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
Ok thanks!!!
Enviado desde mi MI MAX 3 mediante Tapatalk
Thank you very much for this recovery.
Just needed it after trying to install Viper4Android and only going to fastboot screen.
Cheers
Same as the user above, had problems with Viper. Used this and removed the modules, and now it boots. Thanks!
This has caused my device to bootloop to recovery. Flashing stock recovery doesn't fix this problem.
Doing fastboot boot boot.img starts my rom, but every time I reboot (via fastboot, adb or normally from rom) it goes back to recovery. I am running 10.0.3.HD01BA and don't have any ideas how to recover from this.
Any help would be appreciated, I am truly a novice in this scene.
Az4z3l11 said:
This has caused my device to bootloop to recovery. Flashing stock recovery doesn't fix this problem.
Doing fastboot boot boot.img starts my rom, but every time I reboot (via fastboot, adb or normally from rom) it goes back to recovery. I am running 10.0.3.HD01BA and don't have any ideas how to recover from this.
Any help would be appreciated, I am truly a novice in this scene.
Click to expand...
Click to collapse
Did you install any modules?
OnePlus 7T Pro
Az4z3l11 said:
This has caused my device to bootloop to recovery. Flashing stock recovery doesn't fix this problem.
Doing fastboot boot boot.img starts my rom, but every time I reboot (via fastboot, adb or normally from rom) it goes back to recovery. I am running 10.0.3.HD01BA and don't have any ideas how to recover from this.
Any help would be appreciated, I am truly a novice in this scene.
Click to expand...
Click to collapse
Just a thought: could it be that you flashed this recovery with "Fastboot flash boot <filename.img> ? This would explain that when booting not the original boot image but recovery comes up.
From your message I take that you have the original boot image at hand, you could try flashing it with "fastboot flash boot boot.img"
The recovery image in this thread is flashed with "fastboot flash recovery <filename.img>...
Hth, cheers,
Axel
Gesendet von meinem HD1913 mit Tapatalk
HolyChickenGuy said:
Did you install any modules?
OnePlus 7T Pro
Click to expand...
Click to collapse
Only one that came with my Swift Installer.
s3axel said:
Just a thought: could it be that you flashed this recovery with "Fastboot flash boot <filename.img> ? This would explain that when booting not the original boot image but recovery comes up.
From your message I take that you have the original boot image at hand, you could try flashing it with "fastboot flash boot boot.img"
The recovery image in this thread is flashed with "fastboot flash recovery <filename.img>...
Hth, cheers,
Axel
Gesendet von meinem HD1913 mit Tapatalk
Click to expand...
Click to collapse
Negative, I have the command prompt window still open, and was extra careful to flash the recovery with recovery, not boot.
The image I have is a patched boot image from another xda thread. I am scared that flashing that would brick my device.
EDIT: Is there a way to extract my original boot.img and then try to flash it?
EDIT2: Extracted my boot.img from /data folder in stock_boot_xxxxxxxxxxx.img.gz. I will try to flash it once I have backed everything up.
EDIT 3: Tried flashing original boot.img and re-rooting phone with magisk, and no luck. The solution was too obvious though. I didn't realize that my phone had encryption on and the password was my lockscreen PIN code. After decrypting the recovery the phone boots normally and the adb recovery works perfectly.
Thanks for the support, it seems that tinkering with your phone is way harder than I remember it from back in the days; hopefully TWRP will fix this, once it supports Android 10.
Thank you very much for the recovery!
Is there a recovery like this for the regular 7t?
Just curious, do you have a guide on how to this yourself?
Sent from my OnePlus7TPro using XDA Labs
Lossyx said:
Just curious, do you have a guide on how to this yourself?
Click to expand...
Click to collapse
It's actually pretty easy and this would most probably also work for the 7T...
Prerequisites:
Android Image Kitchen (credit to osm0sis for providing this tool)
the original recovery image file (henceforth called "recovery.img"). You can extract this yourself from an update zip file by unpacking "payload.bin" and then use a tool like payload_dumper (credit to vm03 for providing this) to extract the recovery.img file
Now do the following:
unpack image with Image Kitchen --> this will create a "ramdisk" and a "Split_img" directory with the unpacked content within
navigate into the "ramdisk" folder and use a text editor (on windows preferably Notepad++) to edit the file "prop.default"
look for entry "ro.adb.secure" and change entry value from "1" to "0". Note this entry can occur multiple times (I noticed twice), change each --> this will prevent adb from asking for authorization (the recovery does not provide such a dialogue)
look for entry "ro.debuggable" and change this from "0" to "1" --> this actually enables adb
look for entry "ro.secure" and change this from "1" to "0" --> may be unnecessary but I wanted to avoid brick in case a modified recovery would result in such a behaviour
save textfile
repack the image with Android Image Kitchen and voila:
you have a new modified recovery image you can flash
HolyChickenGuy said:
English only pls?
OnePlus 7T Pro
Click to expand...
Click to collapse
991547436 said:
English is a translation. I don't know if the translation is correct.
Click to expand...
Click to collapse
Moderator Announcement:
The way you did is very fine and exemplary!
*********
您的做法非常好，堪称典范！
XDA Forum Rules (excerpt):
...
4. Use the English language.
We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature). You could try :- https://translate.google.com/ or https://www.babelfish.com/ or use one of your choice.
...
Click to expand...
Click to collapse
991547436 said:
But this rec has a bug
After swiping in and entering REC, the interface does not need to enter a password, and the adb shell opens /data is empty.
Only the boot_a and boot_b that have not been modified by magisk are brushed in and the password is entered again after booting and re-entering rec, and the data can be modified.
Click to expand...
Click to collapse
I was in a bootloop, because of the GCam aux Magisk module. For me it was the same at first attempt. I installed with
Code:
fastboot flash recovery OP7TP_StockRecovery_ADB_nosec.img
After that I rebooted to recovery. I also did not get a password prompt. I connected with
Code:
adb shell
but /data was empty. Because I wanted to see if my system still works without Magisk, I booted with the unmodified boot.img by using
Code:
fastboot boot boot.img
System came up without Magisk and was usable. After that I rebooted and it got stuck at fastboot screen again. I tried one more time to select recovery from fastboot screen and it asked me for password. Since I don't have encryption I just tried to connect again with
Code:
adb shell
This time /data was properly mounted and I was able to delete the Magisk module. After that I rebooted to system with
Code:
adb reboot
and now I have my fully functional system back. I don't know why it didn't work in the first attempt but this is awesome.
@s3axel you made my day! Thank you very much!!! Your work is appreciated!
Code:
*** Disclaimer ***
All flashing is done at your own risk!
While nothing from this thread should break your device,
don't come back here blaming anyone if it does!
Introduction
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and
customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to
mash. The GUI is also fully XML driven and completely theme-able. You can change just about
every aspect of the look and
Click to expand...
Click to collapse
Prerequisites:
Code:
. Unlocked Bootloader
Installation instructions:
Recovery Install Method:
Simply download the TWRP-3.7.0_12-0 from twrp website and boot it using fastboot mode, steps are mentioned below
Fastboot Boot Method:
You will need the platform-tools from the Android SDK on your computer. Download only the platform-tools according to your device to get adb and fastboot binaries.
On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging. From your computer, open a command prompt and type
Code:
adb reboot bootloader
You should now be in fastboot mode.
Download the twrp boot image from the link given below, and copy twrp.img file into the same folder as your adb and fastboot binaries and type:
Code:
fastboot boot twrp.img
You will be booted to TWRP, from there go to advanced and then click on "Flash Current TWRP"
REMEMBER: if the device waspreviously rooted, then root has been overwritten, you need to flash the magisk zip again to retain root
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Device Changelog
Version:3.7.0_12-0:
Initial Official Release
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Downloads
Official TWRP Website
My Telegram TWRP Support Group:
https://t.me/pocof4_recoveriesCredits:
- TWRP Team
Sources
TWRP: https://github.com/TeamWin/android_bootable_recovery
Device Tree: https://github.com/TeamWin/android_device_xiaomi_munch
Kernel Tree: https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/munch-s-oss
Status: Stable
TWRP: 3.7.0_12
reserved 1
reserved 2
Build will be live on twrp.me soon
Wow nice!
Build is live
Decrypting working? Will working on future Android 13 with decrypting? I know that dev received Android 13 already
Yes decrypting working fine, even on Android 13
When I updated yesterday, I immediately flashed it without losing data. For today's update, why doesn't it turn on, you have to turn on the new data format, is there the same or a solution
Can I just boot it with fastboot and flash Magisk flashable file in order to root the phone?
I have seen videos on youtube showing exactly that, just wanted to make sure it's doable.
Just want to root the phone, do not intend to flash any rom (yet).
dreamdrake said:
Can I just boot it with fastboot and flash Magisk flashable file in order to root the phone?
I have seen videos on youtube showing exactly that, just wanted to make sure it's doable.
Just want to root the phone, do not intend to flash any rom (yet).
Click to expand...
Click to collapse
If you already have your magisk_patched.img, you can choose which method you want:
1. with Fastboot + TWRP (temporary)
fastboot boot [drag and drop recovery.img]
flash your magisk_patched.img in boot partition + check "Flash to both slots"
reboot to system
2. only Fastboot
fastboot flash boot_a [drag and drop magisk_patched.img]
fastboot flash boot_b [drag and drop magisk_patched.img]
fastboot reboot
What if I would "fastboot boot TWRP.img" and then flash Magisk flashable version checking "flash to both slots"?
dreamdrake said:
What if I would "fastboot boot TWRP.img" and then flash Magisk flashable version checking "flash to both slots"?
Click to expand...
Click to collapse
When you check "Flash to both slots" TWRP will flash the makisk_patched.img to boot_a and boot_b.
I'm not sure, but if you don't check the box, TWRP will maybe flash to inactive slot and you are NOT rooted.
Edit: You can check which slot is active with adb shell getprop ro.boot.slot_suffix
Is it possible to make a backup of the installed rom with relative restore using this official twrp? If yes, which files to select
ok... i can't access to internal storage via pc. I formated data (type yes), rebooted to recovery again and my pc sees internal storage but there is no info about size and i can't copy files to it. It shows message something like "this device is disconnected". I tried to reinstall adb drivers, tried to restart my pc and it's not working. I used adb sideload to falsh ROM and after i booted to ROM, rebooted to recovery I can access internal storage via TWRP.
Runs super laggy with kernel compiled with gcc which is very strange and annoying.
Can't access storage with PC... Disabled and enabled MTP multiple times...
I had to flash ROM via OTG...