Related
Hi there. Thought I'd finally get around to rooting my Glacier, making progress but hit a roadblock.
ROM Manager app is stuck on "Error while downloading from server.", so I flashed clockwork recovery 3.0.2.4 with fastboot shell, ROM Manager still thinks recovery isn't installed and gives me the same download error when I try to manual override.
In recovery, attempting to start a backup gives me the error in the title, that is, "Error while backing up boot image!" and halts.
I could probably continue on to flashing cyanogenmod 7 and gapps, but I'm not comfortable doing that without a backup handy.
Android ver. 2.21, eng SPL (85.2007), 3.0.2.4 ClockworkMod recovery.
Can anyone help?
If it were me, I would download a fresh copy of CWM from here and flash it via fastboot. I bet then you'll be able to successfully make a Nandroid. If not, try formatting your SD card.
Downloaded that and re-flashed to no avail. Backed up SD card, formatted it, and for some reason it started working then.
Ah well, at least I have a backup. Thanks!
Had an odd error with the md5 checksums changing, too.. pushed them with adb, used md5sum, they were correct. Rebooted into recovery and they had changed again. Had to push and verify from recovery in order to install.
It ended up working though, so no complaints.
The easiest workaround I found to this problem was to boot into recovery mode using Quick Boot and follow these steps in the cwm boot screen: apply update from sdcard, install /sdcard/update.zip, reboot into recovery, backup and restore, and BACKUP. Worked for me and I didn't have to reformat my sd card, deleting everything on it.
Hi,
I would like to remind you that, CWM v3.x above are no longer support amend scripting which is used in Froyo ROM. Instead it used edify scripting which is used in Gingerbread ROM.
When you are on Froyo and try to use the latest CWM, it will not work, and you will encounter a problem just like you said.
My self, i use the CWM v.2.5.x, on my fascinate, and it can make backup successfully, although i never try the restore function yet.
OK, so I just got my Nexus S4G two days ago, and I'm ready to root. My phone out of the box has 2.3.4 on it.
I follow this tutorial: http://www.droidfiles.us/nexus-s-4g/root-nexus-s-4g/ the link to which was provided by a good XDA'er. I get the bootloader unlocked and install CWR (recovery-clockwork-3.0.2.4-crespo.img) and that goes fine.
That's when things stop going fine.
First, I try to create a Nandroid backup, and that process seemingly completes fine until i note that the process says it couldn't mount /data. I don't worry about it.
So, I go to Mounts and Storage to prepare to push SuperUser.zip and I tell CWR to "Mount USB Storage" and I wait as directed, but the USB storage never mounts. I try mounting USB Storage and mounting /sdcard, neither of which work, so I can't push SuperUser.zip.
Figuring I did something wrong, I decide to restore from Nandroid, only to have CWR tell me that the MD5 checksum is incorrect and now I have no clean, base Nandroid to restore to.
Then I do some digging, and discover that there's a new CWR for the NS4G at Koush's site and I download the file (recovery-clockwork-3.1.0.0-crespo4g.img) from there, push it to my phone using fastboot's recovery command and start it up.
It doesn't work.
Clicking any of the options (like mounting partitions, or restarting/powering down the phone) causes the screen to go blank and just display the CWR logo in the middle of the screen. The only solution to get out of those loops is to pull battery and restart.
So, now, I'm wondering what to do.
I go back into fastboot, relock the bootloader and I now wait for a reliable root method to root a 2.3.4 NS4G on a Mac.
My questions are:
Where can I get a stock ROM to completely start over from scratch and even remove the recovery I've installed <-- found a base ROM here: http://forum.xda-developers.com/showthread.php?t=1078213
Is there a fully reliable way to root the NS4G on a Mac, and if so how? (I've looked at this thread: http://forum.xda-developers.com/showthread.php?t=878446 and it looks problematic as well).
Look in the dev section, stickies at top, the one talking about ns4g cdma. You have the su zip already. Put the cwm 3024 img file in the same directory as fastboot. You won't use adb. Boot into bootloader and do the fastboot command to unlock. Phone is wiped. Boot into phone normally and log in with gmail. On the phone, mount the device as usb so you can just copy the su zip to the root of the sd card.unmount phone on the Mac side then the phone side. Boot phone into bootloader. Do the command to fastboot the cwm into the phone again. Once finished, choose recovery on bootloader. It will boot into cwm. Choose install zip from card. Choose pick zip. Install su. Reboot into normal phone. Download busybox and a file manager you like that can handle root. With file manager, go to /system/etc and look for the sh file mentioned in the guide and add .old to the end of the file. If su pops up asking for permissions then you know everything is working. Boot into bootloader again. Install cwm again then choose recovery again. Once in cwm do wipe of caches and factory reset and dalvik. Go back and do backup with nandroid. Boot into normal phone. Sign into google again. Update profile and prl them you should be set. Pretty much that's what I did and it worked the first time around.
Follow the Mac guide in the link
herbthehammer said:
Look in the dev section, stickies at top, the one talking about ns4g cdma. You have the su zip already. Put the cwm 3024 img file in the same directory as fastboot. You won't use adb. Boot into bootloader and do the fastboot command to unlock. Phone is wiped. Boot into phone normally and log in with gmail. On the phone, mount the device as usb so you can just copy the su zip to the root of the sd card.unmount phone on the Mac side then the phone side. Boot phone into bootloader. Do the command to fastboot the cwm into the phone again. Once finished, choose recovery on bootloader. It will boot into cwm. Choose install zip from card. Choose pick zip. Install su. Reboot into normal phone. Download busybox and a file manager you like that can handle root. With file manager, go to /system/etc and look for the sh file mentioned in the guide and add .old to the end of the file. If su pops up asking for permissions then you know everything is working. Boot into bootloader again. Install cwm again then choose recovery again. Once in cwm do wipe of caches and factory reset and dalvik. Go back and do backup with nandroid. Boot into normal phone. Sign into google again. Update profile and prl them you should be set. Pretty much that's what I did and it worked the first time around.
Follow the Mac guide in the link
Click to expand...
Click to collapse
I'm going to give your method a try. Thank you for your rapid response...
I see the subtle change you suggested: simply rebooting after unlocking and pushing recovery, and moving SU to the device via USB. Wish I'd thought of that.
(I'm still concerned about the Nandroid issue I reported. But I'll have to avoid any new ROMs for the time being, until I can get an answer for my Nandroid problem...)
My first nandroid choked. After root and final recovery install, I cleared all the caches it was *****ing about the first time, went in normally to make sure everything was okay, then went back and nandroid and no errors the second time. I probably will just stay with rooted stock but I would not flash other stuff until the dust settles and many of the bugs are worked out of the roms and kernels before jumping in.
TonyArmstrong said:
I'm going to give your method a try. Thank you for your rapid response...
I see the subtle change you suggested: simply rebooting after unlocking and pushing recovery, and moving SU to the device via USB. Wish I'd thought of that.
(I'm still concerned about the Nandroid issue I reported. But I'll have to avoid any new ROMs for the time being, until I can get an answer for my Nandroid problem...)
Click to expand...
Click to collapse
If cwm mount won't work then boot into the phone normally and copy over the file like usual is the only other quick and easy way to do it that I could think of at the moment the snafu happened. Yeah the way I did it might not have been the most efficient way but it got me past the hurdle that cwm made quickly. In the end, the result is the same so no big deal.
I don't know if cwm backs up wimax keys so I did it manually. There's a post on how to do it, I don't know if it's in this section. It might be dev?
I wanted to flash PSX Pure Speed Experiment 4.4 rom but I got the " Failed. E:Error executing updated binary in zip '/sdcard/psx_mako_kk_v1..." message mentioned in the OP. I tried the solution posted there, which was to download a patched multirom version of TWRP recovery using the flashify app from the play store. This all seemed to work out fine, and I booted into recovery to flash the rom. Now, this could just be due to my ignorance because the version of TWRP I flashed is 2.6.3.2 (I originally had 2.3.0.1 I believe), but when I wiped my phone, then went to install, there wasnt anything listed in the root of my sd card folder. I tried rebooting TWRP and when I tried again it listed a folder named TWRP there but nothing else. Subsequent reboots yielded nothing. At this point I dont even want to flash the 4.4 rom, I just want to reflash my old CM10.1 rom and be done with it. Any help is greatly appreciated
sropedia said:
I wanted to flash PSX Pure Speed Experiment 4.4 rom but I got the " Failed. E:Error executing updated binary in zip '/sdcard/psx_mako_kk_v1..." message mentioned in the OP. I tried the solution posted there, which was to download a patched multirom version of TWRP recovery using the flashify app from the play store. This all seemed to work out fine, and I booted into recovery to flash the rom. Now, this could just be due to my ignorance because the version of TWRP I flashed is 2.6.3.2 (I originally had 2.3.0.1 I believe), but when I wiped my phone, then went to install, there wasnt anything listed in the root of my sd card folder. I tried rebooting TWRP and when I tried again it listed a folder named TWRP there but nothing else. Subsequent reboots yielded nothing. At this point I dont even want to flash the 4.4 rom, I just want to reflash my old CM10.1 rom and be done with it. Any help is greatly appreciated
Click to expand...
Click to collapse
Reboot the phone and then connect it to your PC and check to see if the PSX ROM file is there. If not, redownload the file and save it in the root of the SDcard. As for the TWRP folder that has nothing in it, delete it. Then try to boot into recovery and flash the PSX ROM, also just making sure that the checkbox for "System" in mount section is unchecked. BTW, is your a multiROM patch for TWRP?
taodan said:
Reboot the phone and then connect it to your PC and check to see if the PSX ROM file is there. If not, redownload the file and save it in the root of the SDcard. As for the TWRP folder that has nothing in it, delete it. Then try to boot into recovery and flash the PSX ROM, also just making sure that the checkbox for "System" in mount section is unchecked. BTW, is your a multiROM patch for TWRP?
Click to expand...
Click to collapse
Thanks for the reply, but when I try to mount my phone, my computer acknowledges that I've connected a device with a sound, but it doesnt show up as a storage device. when I go into devices and printers I can find my phone but it only shows up as an ADB device
And yes to answer your question it is a multiROM patch for TWRP
sropedia said:
Thanks for the reply, but when I try to mount my phone, my computer acknowledges that I've connected a device with a sound, but it doesnt show up as a storage device. when I go into devices and printers I can find my phone but it only shows up as an ADB device
Click to expand...
Click to collapse
Do you have "USB debugging" checkbox, in Developer Options, checked? Also, try reboot your PC and reconect your phone to see whether it shows up as a storage device.
sropedia said:
I wanted to flash PSX Pure Speed Experiment 4.4 rom but I got the " Failed. E:Error executing updated binary in zip '/sdcard/psx_mako_kk_v1..." message mentioned in the OP. I tried the solution posted there, which was to download a patched multirom version of TWRP recovery using the flashify app from the play store. This all seemed to work out fine, and I booted into recovery to flash the rom. Now, this could just be due to my ignorance because the version of TWRP I flashed is 2.6.3.2 (I originally had 2.3.0.1 I believe), but when I wiped my phone, then went to install, there wasnt anything listed in the root of my sd card folder. I tried rebooting TWRP and when I tried again it listed a folder named TWRP there but nothing else. Subsequent reboots yielded nothing. At this point I dont even want to flash the 4.4 rom, I just want to reflash my old CM10.1 rom and be done with it. Any help is greatly appreciated
Click to expand...
Click to collapse
ok when you wiped your rom did you just do a factory reset or a internal sd wipe as well. Also you should try and use 2.6.3.3. Also you have to remember where it is you save your stuff or place everything in 1 specific folder. May I suggest you start over with downloading rom and putting it in a folder created by you like !Flash... using "!" will ensure its the first folder you see.
Also your error also can be fixed by simply rebooting your recovery as its been what I used to fix that error
playya said:
ok when you wiped your rom did you just do a factory reset or a internal sd wipe as well. Also you should try and use 2.6.3.3. Also you have to remember where it is you save your stuff or place everything in 1 specific folder. May I suggest you start over with downloading rom and putting it in a folder created by you like !Flash... using "!" will ensure its the first folder you see.
Also your error also can be fixed by simply rebooting your recovery as its been what I used to fix that error
Click to expand...
Click to collapse
I did a full wipe like I usually do. I would use a different version of TWRP if I knew how to change it from within TWRP. I have a follder titled ROOT that I keep all my ROMs and whatnot in, but the problem is that literally none of the folders in my internal storage are showing up from within TWRP. I can't check to see if USB debugging is enabled because theres no operating system on my phone; like I said, I did a full wipe. The fact that no folders show up also means that it doesnt recognize the backup I had. My computer still won't recognize my phone as a storage device after mounting in TWRP. Maybe I'm doing something in the wrong order? Restarting my computer didn't help.I really need to get my phone working on ANY ROM, and I appreciate all the help so far
I'm new to the Moto Droid world coming from Samsung, and trying to learn about it. I've googled and read a lot about all of the topics below, and I'm looking to learn more. Here are some observations/issues that I'd appreciate any insight on - It would also be helpful to know if these are known, open/unresolved issues:
My device is rooted and unlocked, running sys. ver. 183.46.10.xt907.Verizon.en.US, build KDA20.62.10.1. (I think that's stock Verizon). I have CWM ver. 6.0.4.8 installed. When I try a nandroid backup to my external sd card (/storage/sdcard1), boot-image, recovery image, and system complete normally. When it tries to backup data, I get the error "Can't mount /data!". When I look at my external SD card, I see 4 non-empty files (boot.img, recovery.img, system.ext4.tar.a, system.ext4.tar.b) and 1 empty file (system.ext4.tar). Is there anything I can do to get CWM to backup data also? Do I need to resort to backing up with ADB to get everything?
When I reboot from CWM, I get "rom may flash stock recovery on boot - can't be undone" with "no" or "yes - disable recovery flash" as my choices. I think either choice keeps my CWM recovery. I then get "root access possibly lost - fix? with "no" or "yes fix root (/system/xbin/su)". If I select "yes fix root (/system/xbin/su)", it keeps root, and if I select "no", it loses root. Shall I consider these as minor annoyances that I shall forever live with?
I've tried to flash TWRP, and the only version that I've been able to boot up is the latest one, version 2.8.1.0. The problem is that the font is too big, or our screen size is too small for that version. Is there a version of TWRP that works on our device? I tried ver 2.5, and it doesn't boot.
To flash, I boot the phone into AP Fastboot and use mfastboot on my Windows PC.. Flashing seems to work, but I always get the "<bootloader> variable not supported" message at the start. Is this anything to worry about or indicating some other problem?
Thanks in advance for any and all responses.
beeewell said:
I'm new to the Moto Droid world
coming from Samsung, and trying to learn about it. I've googled and read a lot about all of the topics below, and I'm looking to learn more. Here are some observations/issues that I'd appreciate any insight on - It would also be helpful to know if these are known, open/unresolved issues:
My device is rooted and unlocked, running sys. ver. 183.46.10.xt907.Verizon.en.US, build KDA20.62.10.1. (I think that's stock Verizon). I have CWM ver. 6.0.4.8 installed. When I try a nandroid backup to my external sd card (/storage/sdcard1), boot-image, recovery image, and system complete normally. When it tries to backup data, I get the error "Can't mount /data!". When I look at my external SD card, I see 4 non-empty files (boot.img, recovery.img, system.ext4.tar.a, system.ext4.tar.b) and 1 empty file (system.ext4.tar). Is there anything I can do to get CWM to backup data also? Do I need to resort to backing up with ADB to get everything?
When I reboot from CWM, I get "rom may flash stock recovery on boot - can't be undone" with "no" or "yes - disable recovery flash" as my choices. I think either choice keeps my CWM recovery. I then get "root access possibly lost - fix? with "no" or "yes fix root (/system/xbin/su)". If I select "yes fix root (/system/xbin/su)", it keeps root, and if I select "no", it loses root. Shall I consider these as minor annoyances that I shall forever live with?
I've tried to flash TWRP, and the only version that I've been able to boot up is the latest one, version 2.8.1.0. The problem is that the font is too big, or our screen size is too small for that version. Is there a version of TWRP that works on our device? I tried ver 2.5, and it doesn't boot.
To flash, I boot the phone into AP Fastboot and use mfastboot on my Windows PC.. Flashing seems to work, but I always get the "<bootloader> variable not supported" message at the start. Is this anything to worry about or indicating some other problem?
Thanks in advance for any and all responses.
Click to expand...
Click to collapse
You're using the wrong TWRP. Use TWRP281KK.img > http://d-h.st/511
All the info you need is here > http://forum.xda-developers.com/dro...oot-unlock-t2869432/post55282645#post55282645
Thank You !!
ATTACK said:
You're using the wrong TWRP. Use TWRP281KK.img > http://d-h.st/511
All the info you need is here > http://forum.xda-developers.com/dro...oot-unlock-t2869432/post55282645#post55282645
Click to expand...
Click to collapse
Thank you so much for your reply, and for pointing me to the correct TWRP for my device. It worked like a charm !! :good:
Hi, I am in the process of preparing for upgrading from 7.0 to 7.1.1
I know I need to replace the Custom Kernel with the Stock Kernel. And I have to replace TWRP with Stock Recovery.
Can anybody tell me, which file inside the FTF is the stock recovery? I already found the kernel. Need help to find the stock recovery, thank you!
tempurastyle said:
Need help to find the stock recovery, thank you!
Click to expand...
Click to collapse
We don't have one which is why we have to use TWRP.
So my only way is to flash via Flashtool without wipe?
tempurastyle said:
So my only way is to flash via Flashtool without wipe?
Click to expand...
Click to collapse
Do that then mod your own kernel. [How To] make your own XPERIA DRM-fix kernel.
And flash a TWRP.img to the recovery partition.
fotakernel.sin reside's where we flash twrp on stock. you do not need to flash it to upgrade, contrary you can exclude it in flashtool and keep twrp between updates.
realtuxen said:
fotakernel.sin reside's where we flash twrp on stock. you do not need to flash it to upgrade, contrary you can exclude it in flashtool and keep twrp between updates.
Click to expand...
Click to collapse
this is real knowledge, thanks! so just to be sure, this is what i will do in flashtool:
1) wipe: nothing selected
2) exclude: fotakernel.sin selected
can anybody confirm this is correct?
then after this, i will flash a custom kernel via fastboot and magisk via twrp.
one question regarding magisk: will it be deleted during the flashtool update?
So I ran into a problem...
The Upgrade to 7.1.1 via flashtool was smooth. Then, i flashed twrp via fastboot as usual. When I tried to enter twrp, i get a password prompt to decrypt the phone. So i don't know which password i need to type in. I tried the unlock PIN, doesnt work. Any suggestions?
tempurastyle said:
Any suggestions?
Click to expand...
Click to collapse
To get round that you need to run the following commands...
Code:
fastboot format userdata
fastboot format cache
...so you'll need to backup all your data first.
XperienceD said:
To get round that you need to run the following commands...
Code:
fastboot format userdata
fastboot format cache
...so you'll need to backup all your data first.
Click to expand...
Click to collapse
Ok, so I decided to keep my data and don't install twrp. Now I got another issue, is it possible to install Magisk without TWRP? I already got my kernel using my ta backup according to the instructions a few posts above, which really works great.
tempurastyle said:
Ok, so I decided to keep my data and don't install twrp. Now I got another issue, is it possible to install Magisk without TWRP? I already got my kernel using my ta backup according to the instructions a few posts above, which really works great.
Click to expand...
Click to collapse
I thought you excluded fotakernel so you did not have to flash twrp again. Oh well anyway you can use twrp to flash zips just fine although /data is encrypted, most flash zips do not write to /data anyway some like supersu use /cache (which is not encrypted contrary to the info above) to get around encryption at next boot. And like magisk also patch the boot.img live on your phone, some write to /system which is not encrypted either, I never seen a flash zip that did write to /data. Only backup/browsing/etc on /data is affected.
So when presented with the password screen in twrp just press cancel and make sure the zip you want to flash is located on the external sd card (do not encrypt this in phone settings, your card will be unreadable from pcs to) then choose flash zip and choose the external sdcard to pick the zip from and flash magisk or whatever. You need to run your kernel through ta poc or rootkernel first and disable dm verity and sony ric. (you write you did this so just install twrp and flash away) Do not wipe cache before rebooting just in case magisk uses this in a similar way to supersu (I have no idea)
Also if you do the above fastboot format commands suggested in post#8 without disabling 'forceencrypt' for /data (fstab in the kernel image or with a tool) the phone will encrypt itself again as soon as you turn it on.
If forceencrypt is disabled the same can be achieved (clearing encryption) with a factory reset btw.
So if you did not bump into the password in twrp before you likely did a factory reset with a kernel with encryption disabled. Then, maybe after updating you rebooted stock and the phone encrypted itself again, then now you can not access /data in twrp. Thats also because we have no version of it that supports encryption on the X-compact though. Again do not worry, I have not meet a zip I could not flash, supersu, magisk, etc because they do not access /data anyway.
realtuxen said:
I thought you excluded fotakernel so you did not have to flash twrp again. Oh well anyway you can use twrp to flash zips just fine although /data is encrypted, most flash zips do not write to /data anyway some like supersu use /cache (which is not encrypted contrary to the info above) to get around encryption at next boot. And like magisk also patch the boot.img live on your phone, some write to /system which is not encrypted either, I never seen a flash zip that did write to /data. Only backup/browsing/etc on /data is affected.
So when presented with the password screen in twrp just press cancel and make sure the zip you want to flash is located on the external sd card (do not encrypt this in phone settings, your card will be unreadable from pcs to) then choose flash zip and choose the external sdcard to pick the zip from and flash magisk or whatever. You need to run your kernel through ta poc or rootkernel first and disable dm verity and sony ric. (you write you did this so just install twrp and flash away) Do not wipe cache before rebooting just in case magisk uses this in a similar way to supersu (I have no idea)
Click to expand...
Click to collapse
Yes, after the first upgrade attempt, i let twrp untouched. then when entering twrp, i didnt have a password, so i skipped it. i couldn't find the sd card in the file browser, and after i hit reboot in twrp the phone restarted and got stuck in boot.
So I flashed again, this time deleting twrp. the initial boot up went fine. Then i flashed twrp again and once again, without having a password, i just skipped the password prompt. still couldnt find the sd card, and i rebooted out of twrp. and the phone got stuck again.
after 2-3 trials, i figured out that everytime i rebooted out of twrp, the phone gets stuck during boot. even after turning it off and on, so a reflash was needed.
now i have given up using twrp, so i have an unrooted phone with an unlocked bootloader. which does not allow me to use android pay. i think to solve my problem is:
1) i need to know which twrp version really works, i have tried
this version
and this version
both cause a boot failure for me
2) i need to find the sd card location in the twrp file browser (all the folders show empty for me)
if nothing works, i guess i need to wipe my phone, but that's what i would like to avoid. thanks for your help guys!
tempurastyle said:
Yes, after the first upgrade attempt, i let twrp untouched. then when entering twrp, i didnt have a password, so i skipped it. i couldn't find the sd card in the file browser, and after i hit reboot in twrp the phone restarted and got stuck in boot.
So I flashed again, this time deleting twrp. the initial boot up went fine. Then i flashed twrp again and once again, without having a password, i just skipped the password prompt. still couldnt find the sd card, and i rebooted out of twrp. and the phone got stuck again.
after 2-3 trials, i figured out that everytime i rebooted out of twrp, the phone gets stuck during boot. even after turning it off and on, so a reflash was needed.
now i have given up using twrp, so i have an unrooted phone with an unlocked bootloader. which does not allow me to use android pay. i think to solve my problem is:
1) i need to know which twrp version really works, i have tried
this version
and this version
both cause a boot failure for me
2) i need to find the sd card location in the twrp file browser (all the folders show empty for me)
if nothing works, i guess i need to wipe my phone, but that's what i would like to avoid. thanks for your help guys!
Click to expand...
Click to collapse
The 2. issue with the sdcard is easy. After pressing 'install' button in twrp at the bottom left press the "select storage' button, a small window will pop up then select the 'micro sdcard' and press 'ok", you should see your files now.
The 1. ssue is really odd! I use the second twrp you posted, for some wierd reason the first one does not boot for me (twrp does not start). But I talked with another guy for him it was the other way around. It was really strange. I think most can use both though without problems
There is one more twrp 3.1 from bambamx, but I really do not get this, twrp boots from its own partition with its own kernel. They should be separated unless twrp does something to system ofcause which it very well shouldn't unless you ask it to, deleting a important file or flashing something. I have never heard of this sorry. One thing is certain our device sure could use a stable nougat encryption compatible twrp!
I will let you know if I find something, you can try the last available version, I have no idea if it will exhibit the same strange behaviour. But maybe its worth a shot although it seems something else is at play.
A couple of stupid questions sorry; You disabled dm verity and sony ric in ta poc right, and it does not happen if you boot your phone normal a couple of times.
Edit: sorry Mr. Sandman had not left so I did not read properly here from the morning. I will edit my post to actually answer as best as I can lol.
Just to let you know:
1. You do not need to install TWRP to use it! You can just do
Code:
fastboot boot <TWRP image>
to run TWRP on the phone (instead of
Code:
fastboot flash boot <TWRP image>
). The only drawback of this method is that you will always need a computer to enter TWRP. Btw. with this method you can also try out a custom kernel image before flashing it.
2. You do not need write access to /data partition to install Magisk. It was explained in another thread that Magisk can use /cache temporary when access to /data is not available. It will write to /data on first boot instead.
3. While using TWRP you can use adb to transfer files onto the phone, so you don't need to have them ready on the internal storage.
realtuxen said:
The 2. issue with the sdcard is easy. After pressing 'install' button in twrp at the bottom left press the "select storage' button, a small window will pop up then select the 'micro sdcard' and press 'ok", you should see your files now.
Click to expand...
Click to collapse
I did, but the SD card can't be selected, and the size shows as 0kb. I did a workaround though: i formatted a spare sd card and copied magisk on it. it was instantly recognized and selectable.
ypnos42 said:
Just to let you know:
1. You do not need to install TWRP to use it! You can just do
Code:
fastboot boot <TWRP image>
to run TWRP on the phone (instead of
Code:
fastboot flash boot <TWRP image>
). The only drawback of this method is that you will always need a computer to enter TWRP. Btw. with this method you can also try out a custom kernel image before flashing it.
3. While using TWRP you can use adb to transfer files onto the phone, so you don't need to have them ready on the internal storage.
Click to expand...
Click to collapse
GREAT advice! I launched TWRP from ADB and successfully flashed Magisk using ADB sideload. Thanks, my phone is rooted again!