So I rooted, unlocked bootloader, flash custom recovery, flashed custom kearnel/rom, and somewhere in that process i unmounted or erased or something idk my internal sdcard.... Google and I have been looking for the latter part of the day for a fix or answer till I finally had to break down and open a thread. please can someone point me in the direction or instruct me on how to reformat or repartition my phone to have storage without flashing factory firmware? im also unable to mount my external sdcard aswell. Im running a 6.0 mm rom with missing storage.
Thanks,
DirtyWhiteBoy707
You have an unlocked bootloader and a custom recovery; "starting over" doesn't have to mean going back to full stock. (i.e., losing either the unlocked bootloader or your custom recovery)
One would surmise that because twrp offers the nuclear option of a full wipe (reformat) of the userdata partition, that it has the expectation that the kernel's init will recreate the "internal" sdcard if it doesn't exist on the first boot thereafter. Dunno, maybe your custom kernel doesn't do that; a stock ROM surely would though because a factory reset in stock always destroys the internal sdcard.
One of the freedoms that an unlocked bootloader gives you is the ability to flash whatever you please in Odin (so long as you don't nuke the now customized/unlocked bootloader).
So for instance if you thought the only way to do what you wanted was to "use the stock ROM for a few minutes", just hack together an Odin tar.md5** file containing ONLY the boot.img & system.img file blobs from the stock Odin file. Boot into TWRP, nuke (full wipe/reformat) of /data, & wipe cache. Then boot into Odin and flash your "almost stock" system.img/boot.img tar.md5 Odin file in the AP slot.
That would leave you with an "unrooted, pure stock ROM" - except for the fact that you still have both your custom recovery and an unlocked bootloader. So you could inject stock with root from the TWRP recovery (e.g. with the SuperSU flashable installer) if you wanted to go back to rooted stock, or you could nuke that ROM for a custom one afterwards using TWRP.
[ While you are making .tar.md5 blobs for Odin**, go ahead and make one up so you can reflash *only* your custom recovery anytime you like (just rename the twrp*.img file to "recovery.img" before putting it in the .tar file) - it sounds like you are accident prone. Note that if you did this you could even include the stock recovery.img in your "almost stock" custom Odin tarball; all it would take to restore TWRP would be a trip to Odin with your unlocked bootloader. This would let you perform the honest-to-dog factory reset/wipe if you thought that was critical ]
Myself I would first try a full userdata reformat (using TWRP) and see if your current ROM/kernel recreates the internal sdcard on boot. (OTOH, if your screwing around with the boot partition resulted in interfering with mount operation, maybe *existence* of the directories is not the problem.)
good luck
**instructions for creating Odin tar.md5 archives can be found all over XDA
solved
simply had to install the correct kernel for the partitions to be updated correctly. ended up using a kernel by Lsskernel for note5ports and 6.0.1
DirtyWhiteBoy707 said:
simply had to install the correct kernel for the partitions to be updated correctly. ended up using a kernel by Lsskernel for note5ports and 6.0.1
Click to expand...
Click to collapse
Makes sense.
Sort of a mystery that whatever boot partition (kernel+ramdisk) you started with didn't already do it... unless it was derived from a device that didn't use an "internal" pseudo-SDcard.
Probably even the stock kernel - dirty flashed - would have "fixed it" as well. It might not have booted into the UI, but by the time it wedged or bootlooped (late boot) what you wanted accomplished will have already happened (by "init" processing through the *.rc scripts.)
As often as people try it with the explanation "well, I tried it and it worked", when you mix-n-match ROMs with various boot partitions (particularly the contents of the ramdisk, far less so for the "kernel"), there's no guarantee that you didn't create a side effect in some subsystem (minor or major) as a result of changes written in to /data from that single boot cycle.
Dirty flashing leads to dirty behavior. Hard to predict how major or minor those problems might be though.
Related
Did anyone's TWRP become broken after updating to 4.4.2? Thought I'd ask because everytime I attempted to gain access to Recovery Mode, I would get an error (it said something like "No connecrtion"). I had to manually flash TWRP with Wugs and was able to successfully gain access to Recovery Mode again.
urbanman2004 said:
Did anyone's TWRP become broken after updating to 4.4.2? Thought I'd ask because everytime I attempted to gain access to Recovery Mode, I would get an error (it said something like "No connecrtion"). I had to manually flash TWRP with Wugs and was able to successfully gain access to Recovery Mode again.
Click to expand...
Click to collapse
I've not updated my Nexus 7 to KitKat yet, but I just noticed on my Nexus 5 that TWRP is broken after updating to the 4.4.2 OTA. I don't get the "No connection" error, I just get the little dead android icon with the red exclamation point. Too bad I'm at work and won't be able to re-flash it until I get home.
You're not alone.
urbanman2004 said:
Did anyone's TWRP become broken after updating to 4.4.2? Thought I'd ask because everytime I attempted to gain access to Recovery Mode, I would get an error (it said something like "No connecrtion"). I had to manually flash TWRP with Wugs and was able to successfully gain access to Recovery Mode again.
Click to expand...
Click to collapse
Lacking any and all details about how you upgraded, I would have to say that is to be expected. The OTAs usually directly overwrite the recovery with a new version of the stock recovery.
Moreover, the most recent OTA used that "/system/recovery-from-boot.p" patch file and associated script "/system/etc/install-recovery.sh" mechanism that automatically overwrites the recovery by patching the boot partition image; I think this happens either on every boot (or maybe during a clean shutdown).
So, not having noticed that, I flashed a custom recovery & booted the stock ROM... and next time I rebooted into recovery, I was back at the stock recovery ... WTF?, right?
I renamed those files to stop that from happening. I think some of the recoveries are aware of this and perform similar tricks on your behalf when they "install root" for you, but if you continue to get your recovery overwritten by stock, this is the place to look.
FYI I capture a full nandroid backup of every new stock release, whether or not I plan on using stock. I set them aside (copy them to a PC) so that they are always available.
I do this by:
- TiBu user app & data backup
- make a nandroid backup of my current ROM
- restore a nandroid backup of the prior release of the pure Stock ROM including it's matching stock recovery
- take the OTA and apply it (note everything is COMPLETELY, 100% stock during this operation)
- soft-boot a custom recovery via fastboot ("fastboot boot ...")
- make a nandroid backup of the new pure Stock ROM, including it's matching stock recovery
- flash a custom recovery and either restore a different ROM, or root the stock ROM and move forward with TiBu
This may seem like a lot of work, but it preserves maximum flexibility and safety:
(a) I can roll back to pure stock (any version!) any time I please from my archive of stock nandroid backups.
(b) I never - ever - have problems with OTA installation (including hazardous things like bootloader installs)
(c) I never need to go begging on the internet "please anybody, can you send me file "xxxx" from the stock release "xyz" ? I already have them - all of them.**
hope that helps
** note that TWRP's ".win" files are just tar archives. You don't even need to restore prior ROMs to pluck out individual stock ROM files.
I'm trying to install CM via TWRP.
First I had to unlock the bootloader, so I did, and since then I could not boot to my stock Android (although, correct me if I'm wrong, unlocking the bootloader should NOT delete the OS), it just sent me to recovery.
So I went along, flashed TWRP and got cm 10.2.1 for jfltexx. At first it didn't install well, because my data partition was not formatted correctly. So I formatted it, now TWRP sees it correctly and is able to mount it, enable MTP and everything. When I try to install now, everything seems fine and TWRP's log shows "Updating partition details..." and gives me the "Successful" message, offering to wipe cache/reboot system. (I did wipe cache and dalvik cache before, of course).
If I choose "Reboot System", it just boots back to recovery. The same happens if I power it off and boot normally, even if I pull out the battery and retry that way.
What can I do about it?
Jon-G said:
I'm trying to install CM via TWRP.
First I had to unlock the bootloader, so I did, and since then I could not boot to my stock Android (although, correct me if I'm wrong, unlocking the bootloader should NOT delete the OS), it just sent me to recovery.
So I went along, flashed TWRP and got cm 10.2.1 for jfltexx. At first it didn't install well, because my data partition was not formatted correctly. So I formatted it, now TWRP sees it correctly and is able to mount it, enable MTP and everything. When I try to install now, everything seems fine and TWRP's log shows "Updating partition details..." and gives me the "Successful" message, offering to wipe cache/reboot system. (I did wipe cache and dalvik cache before, of course).
If I choose "Reboot System", it just boots back to recovery. The same happens if I power it off and boot normally, even if I pull out the battery and retry that way.
What can I do about it?
Click to expand...
Click to collapse
First I'd try a newer version of CM. That's an old one. It might not work and play well with a newer version of TWRP. Plus the newer version is a little more polished.
Second, if you must use that CM version, redownload it. You wouldn't be the first person who got a corrupted install file that causes screwball issues like this.
Third, if all else fails use Odin to reset back to stock and start over. Something might have gotten all borked up when you first modified the device that isn't letting the install work. A full restore to stock should correct that.
Skipjacks said:
First I'd try a newer version of CM. That's an old one. It might not work and play well with a newer version of TWRP. Plus the newer version is a little more polished.
Second, if you must use that CM version, redownload it. You wouldn't be the first person who got a corrupted install file that causes screwball issues like this.
Third, if all else fails use Odin to reset back to stock and start over. Something might have gotten all borked up when you first modified the device that isn't letting the install work. A full restore to stock should correct that.
Click to expand...
Click to collapse
Thanks for the reply.
Regarding the versions of CM and TWRP, I deliberately picked these versions due to their high download count (A sign I can trust these builds, being not too buggy). I'll try a newer CM version and another TWRP version if that didn't help.
I will also verify the MD5 for the downloaded file this time.
If I restore to stock via Odin, wouldn't that override the recovery? I've looked on some tutorial on how it's done, and it seems like the stock recovery is flashed, then used to restore the stock. Is there any way to use Odin to flash other ROMs?
EDIT: Nope cm-11-20140210 also failed, and I did verify the MD5 now. My TWRP is the newest available for jgedlte in the download page (2.8.0.1).
I did manage getting into some sort of a boot loop (The initial "Reboot System" brought back the recovery, but after a full power off and a reboot, the screen remains black and the phone vibrates every 4 seconds or so.)
EDIT 2: I tried to flash the stock back, following this tutorial. I downloaded the Open European version, flashed the AP but it failed during the write of system.img.ext4, saying that the image is invalid. I tried again with the PIT file, but it failed too (secure check fail while repartitioning...).
Really in a bind here. I have a VZW Note 3 with JasmineROM 6.1. This morning I was prompted to do a SuperSU update and I went along and now I'm stuck in a boot loop. When I did Jasmine 6.1 last October I stopped seeing any Safestrap boot, so I'm not sure how to get into a mode where I can grab data. Any help here would be greatly appreciated. Right now all I can do is get into stock recovery and download mode.
Reading between the lines it sounds like you:
- have a locked bootloader
- have no custom recovery
If that is the case, you probably have a trip back to stock in your future: you have lost the only root you had. An unlocked bootloader would allow you to flash whatever you wanted in Odin (for instance, re-flashing a Jasmine system.img or a twrp custom recovery), but without that you are restricted in Odin to only flashing Sammy-signed blobs.
You might spend some time to see if Jasmine supports a "safe mode" boot on the off-chance that the bootloop is being caused by a market app.
A "dirty Odin flash" of only the stock system.img probably will not boot correctly or will also boot-loop, so I suppose that means you are in danger of losing all data on your phone as well. But you could try this as a last-ditch desperation move. The worst that could happen is that you will still have to flash back to pure stock... and lose all your data. (The stock recovery "factory reset" wipes everything, including the so-called "internal" SD card).
sorry
bftb0 said:
Reading between the lines it sounds like you:
- have a locked bootloader
- have no custom recovery
If that is the case, you probably have a trip back to stock in your future: you have lost the only root you had. An unlocked bootloader would allow you to flash whatever you wanted in Odin (for instance, re-flashing a Jasmine system.img or a twrp custom recovery), but without that you are restricted in Odin to only flashing Sammy-signed blobs.
You might spend some time to see if Jasmine supports a "safe mode" boot on the off-chance that the bootloop is being caused by a market app.
A "dirty Odin flash" of only the stock system.img probably will not boot correctly or will also boot-loop, so I suppose that means you are in danger of losing all data on your phone as well. But you could try this as a last-ditch desperation move. The worst that could happen is that you will still have to flash back to pure stock... and lose all your data. (The stock recovery "factory reset" wipes everything, including the so-called "internal" SD card).
sorry
Click to expand...
Click to collapse
I wound up having to do a factory restore which restored me to a clean state of JasminROM. After that I performed the new bootloader unlock and installed TWRP. Lost some data, but didn't have a choice. Last fall when I upgraded JasmineROM to 6.1 it got rid of Safestrap which was the only way to get out of this bind. At least now I have TWRP and can use that in the future.
Hi
Trying to flash TWRP but no ADB & Fastboot directory under Windows 10 program files/x86?!? Also should GApps go here? 32bit? What if SD card & internal storage is merged? End result is Lineage OS...
Could anyone link a good guide?
Which adb/fastboot utility did you install? If you install Minimal ADB 1.4.2, on my computer it's present under C:\Program Files (x86)\Minimal ADB and Fastboot. For 1.4.2: https://www.androidfilehost.com/?fid=745425885120698566
If you're trying to flash TWRP (ensure you've got either TWRP 3.0.2 or a more recent version, 3.1.1 for example, and that it's for athene devices), you could follow this guide: https://forum.xda-developers.com/showpost.php?p=67031805&postcount=3 Also, double check you've unlocked your bootloader before attempting any of this: https://forum.xda-developers.com/showpost.php?p=67031801&postcount=2 Bear in mind unlocking your bootloader will wipe your device and void your warranty.
Once you've flashed TWRP, then reboot straight to recovery - this is to ensure TWRP is not overwritten by the stock recovery. Once you've booted to the recovery, then TWRP should stick and you may reboot as normal.
EDIT - instead of flashing TWRP, you may wish to boot to TWRP (and look at step 4 below):
Copy the TWRP image file to your adb folder.
Boot into the bootloader and connect your device to your computer.
Open your adb client and verify your device is communicating by executing 'fastboot devices' without the quotes. You should get a response with your device's serial number.
To boot in TWRP, execute in the adb terminal 'fastboot boot <name of TWRP image>' without the quotes. E.g if your TWRP is twrp-3.1.1-athene_shreps.img, then the command you'd use is 'fastboot boot twrp-3.1.1-athene_shreps.img' (without quotes).
Afterwards, you'll be able to flash LineageOS and GApps. The main instructions for flashing a custom ROM are usually listed in the first post of each custom ROM (here's the link for the official LineageOS: https://forum.xda-developers.com/moto-g4-plus/development/rom-cyanogenmod-14-1-t3522101)
If you have your SD card and internal storage merged, then unless you can save the encryption key from your stock, your SD card will be wiped/inaccessible. SD cards mounted as portable storage appear to operate okay under both custom and stock ROMs. Thus, back up your SD card to your computer. You may wish to re-format your SD card as portable storage (and from what I've read on the Lenovo Motorola forums, that might help your SD card last longer, as it's not being subjected to encryption as it would be with adoptable storage).
1)You'll be flashing the LineageOS and GApps (can use either OpenGApps or BeanGApps) zips using TWRP. You need 7.1 arm Gapps (32 bit).
2)Download LineageOS and GApps to your device. Do not unzip them.
3)Reboot to TWRP recovery. Tap the Backup option on the main menu.
4)Back up your device in TWRP (make a note this is your stock backup). If you want this backup to be OTA friendly for stock updates, then do not 'swipe to allow modifications'. Back up the stock ROM, verify you've got the backup then reboot to TWRP, and then 'swipe to allow modifications'.
5)Go back to the main menu, and tap the 'Wipe'.
6)Under 'Advanced Wipe', select Dalvik/ART cache, system, data and cache. Double check these are the only ones you have ticked.
6a)Swipe to wipe.
7)Go back to the TWRP main menu.
8)Tap Install and locate your LineageOS and GApps zips.
9)Flash LineageOS first and then GApps.
10)Reboot to LineageOS.
If your device screen goes to sleep whilst in TWRP, press on the volume keys to wake up your device.
If you wish to revert back to near stock, you can flash your TWRP backup of your stock ROM (though this will revert any messages to the point when your backup was taken, you may wish to use Titanium Backup or MyPhoneExplorer to backup). If you decide to revert completely to stock, then if you were on the June 2017 stock update, please only flash the June 2017 or later stock firmwares: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
@echo92 if he would decide to flash back to a clean StockRom (by fastboot) in order to start with a complete unmodified System (stock boot, stock kernel & stock recovery) wouldn't it be better not to "flash" but just to "boot" once into TWRP and take a backup of the clean StockRom in order to save the stockrecovery too? So he could simply restore his clean stock if he wants to take a future OTA.
If he "flashes" TRWP permanently onto StockR he would backup Stock with modified recovery and might wonder, why he couldn't install an OTA.
Please correct me, if I'm wrong.
bullfinch110 said:
@echo92 if he would decide to flash back to a clean StockRom (by fastboot) in order to start with a complete unmodified System (stock boot, stock kernel & stock recovery) wouldn't it be better not to "flash" but just to "boot" once into TWRP and take a backup of the clean StockRom in order to save the stockrecovery too? So he could simply restore his clean stock if he wants to take a future OTA.
If he "flashes" TRWP permanently onto StockR he would backup Stock with modified recovery and might wonder, why he couldn't install an OTA.
Please correct me, if I'm wrong.
Click to expand...
Click to collapse
Oh definitely, that's an option, booting into TWRP and backing up the stock ROM. As I understand it, you have to back up your device without allowing TWRP to modify your system partition. If the backup is taken after that, I recently read that enabling that will cause an OTA to fail (since the type of OTA monitors if the system was ever mounted as read/write), even if the backup you took had no other changes.
It honestly depends on how much flashing the opening poster is planning on doing, if it's simply just LineageOS and OpenGApps, then might be worth booting into TWRP. However, to keep updated then you'd have to perform the updates when you've got a PC available (to be able to boot into TWRP), in which case the inconvenience of booting into TWRP with a PC might outweigh the downside of a custom recovery. For custom ROMs, we might have a similar issue ironically, where a user downloads an update for custom ROMs and cannot flash the update because they do not have TWRP on their device (albeit this issue is easier to fix). I concur that simply booting into TWRP may be more suitable for new users and those that do not realise the requirements/downsides of having a custom recovery. I'll add in the option of booting to TWRP in the previous post As the saying goes, with great power comes great responsibility.
Also, if the user flashes other files (e.g. a custom logo.bin to hide the bootloader warning), then the OTA would fail anyway, and custom logos aren't backed up by TWRP. For a logo.bin though, that can be easily replaced by a stock logo.bin (from the appropriate stock ROM) flashable in fastboot or in TWRP.
If the xda pros would establish a new status, like "Recognized Explainer", you were the first who 'd deserve it.
Thx!!!
I have successfully installed Lineage Flo (2013) on a Nexus 7! This practice (fell at every hurdle) & your post should bring the matter to a swift finish.
Many thx.
How To Flash Roms with the Ridiculous Slots... yep. You're a rookie again because these things are going to drive you onto a drunken crazy bender... You'll probably wake up in Mexico married to someone you've never met and tied in with the Chicago Mob in debt for a quarter million. THIS IS WHAT WORKS FOR ME. I do the same thing Every time and have done this wrong so many times I've lost count.
Note number 1...
You have or know how to use adb and fastboot basics... if not... Of not Google the Adb and fastboot set up for your devices and/or PC/Laptop etc... There are a lot of forums and Q&A on setting this up to get fastboot cmds running. You should be familiar regardless and at least have the stock flashall.bat for a Google Stock IMG JUST IN CASE. I am assuming everyone is already at the install for TWRP and is working with 3.2.0-0 only. You cannot flash roms without it. Any other version for 8.1 will NOT work at this time...
Note number 2...
Roms will vary. Some may include the vendor image and you don't need to flash it. Some may include gapps and you don't need to flash those... Some may include everything and have you flash to slot_a and that is all. In other words do what the OP says, they built it. They know what's in it and how it works.
Here's the trick... It doesn't mean you can't do these in any other way but you will NOT get stuck if you follow some simple rules...
Roms only flash while in Slot_A
Gapps only Flash in Slot_B
Kernels only flash in Slot_B
Magisk only flash in Slot_B
IMG Flash to Slot_B
TWRP 3.2.0-0 ONLY
TWRP 3.2.0-0 to either slot
Do NOT EVER Flash anything other then TWRP, Rom Gapps and Vendor until GOING through first boot. Yes you can but it increases your issues.
Always always always double check between every install the status of your Overlays folder. Before every rom install Mount System then Go to File Manager and Delete that folder from Slot B before you boot to Slot A to flash the rom. This can hold Data from Magisk and Mods that get all tore up Everytime... It also happens when you reflash Magisk or dirty flash a rom. I'm going to put together a fresh flash below and I'll get into that a little later.
So from stock Google image...
Clean flash... MAKE SURE YOUR LOCKSCREEN IS OFF... No fingerprint set up... Not a pin set up... No pattern set up. If your more secure than swiping up to open your screen your not getting in to TWRP 3.2.0-0 decrypted.
Either... Reboot recovery (you'll be in slot B) if you already have TWRP installed....
Or....If you're just booting TWRP for the first time...from bootloader you fastboot boot (not flash really the terminology is BOOT) TWRP-3.2.0-0-marlin.img (you'll be in slot B)
Read your bootloader screen or go to TWRP 3.2.0-0 Reboot menu to find out which slot you're in.
FLASHING YOUR FIRST ROM...
note... Most are going to require before flashing your coming from stock. Just do it. At least the initial install... Dirty flash or clean flash after that without going back to stock but you don't have to flash the stock image.
Ready... You're in slot b remember...in order here...
- Wipe Data System Cache
- Flash TWRP 3.2.0-0 the ZIP
This is why you can't have your lockscreen on... If you didn't listen just go back to your bootloader and start over with the flash-all.bat. Sorry but I warned you... You can't get anything to flash at this point because you can't decrypt 3.2.0-0.
- Go to MOUNT then make sure your system box is checked
- Go to ADVANCED and then File Manager and make sure you have no overlay folder. If you do... click on it and hit delete from the options on the bottom portion of TWRP.
- HIT HOME and Go to the actual reboot menu choice (Not the swipe reboot system)
-Click on slot_A and then reboot back into recovery. ...NOTE... I usually don't use the reboot recovery option.(reboot recovery seems wonky and doesnt work for me all the time) I reboot system and just hold volume down until I hit the bootloader and the choose recovery in the bootloader options...
You ARE in Slot A now... Right... You can Double check in the bootloader or TWRP in the reboot menu.
- if you really really really like to wipe you can wipe Data system and cache in Slot_A... I never do from slot_a but to each their own.
- Flash rom and flash TWRP 3.2.0-0. Nothing else.
- Reboot back to recovery again.
You ARE in slot B. Yep automatically... When a rom is flashed it goes to the opposite slot. And reboots you there on the next recovery reboot so DO NOT GO change your slot to B unless an OP actually directs you to do so.
So... We're in slot B
- Flash Gapps and Vendor... nothing else until after you boot up.
Yeah yeah... You want to be rooted... Well boot up first and we'll hopefully be able to walk through that too.
Your booted up. Go to your development options and double check to make sure USB Debugging is enabled... Really whatever, you're really pretty safe if you have Your fastboot drivers and they must be installed because you installed TWRP to get this far so if something goes wrong from here we can still always do the flash-all.bat so your phone shouldn't implode and brick out.
Reboot recovery. Yep you're in slot B... You should now always boot recovery to slot_b unless you mess something up and get stuck in a loop. I've seen it but couldn't duplicate. It was always me flashing out of order.
GAINING ROOT... MAGISK INSTALL
- Choose the zip, flash and reboot.
Nothing further needed, make sure it's compatible with 8.1 and at least 15 to 16 are Oreo compatible. Easy right.
Well even when I'm updating... the wonderful Overlay folder can get jacked. I'm pretty sure I've heard it laugh at me as I stuck in bootloop after bootloop... If you delete the overlay folder anytime BEFORE you update to the next version of Magisk you'll be ok
UPDATING MAGISK...
So if you're on 15.3 and you want to get to 16.0 without getting stuck or having issues on boot.
- Reboot from Rom to recovery... You WILL always be in slot B by default.
- Go to Mount
- Mount System
- Go to Advanced and then File Manager, find your Overlay folder.
- Click on the overlay folder
- Click Delete
- Hit Home
- Flash your updated Magisk 16.0
MAGISK AND KERNEL
To get Magisk and a kernel going can give you to madness. It gets a little tricky. But honestly devs have really really improved the process. If you're rooted already most you can flash reboot into the rom reboot to recovery again and then do this again...
- Reboot from Rom to recovery... You WILL always be in slot B by default.
- Go to Mount
- Mount System
- Go to Advanced and then File Manager, find your Overlay folder.
- Click on the overlay folder
- Click Delete
- Hit Home
- Flash your updated Magisk 16.0
For the most part the current kernels do not blow out your Recovery anymore however some do. In fact the only one I know that will is Noexezshades. Probably spelled that wrong but you'll catch my drift if you read his OP.
SERIOUSLY YOU BETTER ALREADY HAVE BOOTED INTO YOUR ROM FOR THE FIRST TIME.. You'll hate your life if you set this up during your initial install.
INSTALLING KERNEL WITH MAGISK
- Reboot Recovery (hahaha. Ha. You turned your fingerprint scanner on... Reboot and turn it back off)
- Flash Magisk
- Reboot
I know... right now you're saying WTF... I didn't flash the kernel. This is just a fail safe... Points in Any Kernel need Root to install... I haven't had issues but really probably because I always flash Magisk first.
If you already had Magisk installed start here.
Now we're going to Flash the kernel. It's going to unroot you so we'll just immediately install Magisk I recommend always installing Magisk after a kernel because it also Patches the boot otherwise there are times when patching the boot.img is required however I believe most DEVs have surpassed that FOR MOST KERNELS.
- Reboot recovery (Dang. You forgot to turn off your fingerprint sensor again, sorry life's rough turn off your lockscreen again)
- Flash kernel
- Reboot system
- Reboot recovery (you might lose TWRP however every Newer version I'm using--- unless noted by the OP--- is working at present)
- DON'T flash Magisk... No dont flash Magisk. If you were following along you can see you need to go delete the overlay folder before you flash Magisk it will almost always go bad at this point if you don't delete the overlay folder
- Flash Magisk
- Reboot.
Hopefully you learned what's happening now in the background. I try to explain things from a user level and do this as part of my daily work every day. I don't understand things unless someone tells me what's going on along the way and keeps me partially entertained...
Talk amongst yourselves or don't post Anything. The goal is to take the issues out of the day to day so the devs aren't getting the questions.
I'm gonna have to read this post a couple of times to get the hang of it. I'm kind of a newbie.
Great post. Thank you for the write up. Helps to understand twrp when dealing with two partitions
When I understand it correctly, for a ROM installation I need to select slot a. (Standard for me). And slot b for Kernel installation and others.
But why my twrp installation was broken? After installation I can't boot to the system and unable to start the recovery, so I must flash the complete system images from Google.
Gesendet von meinem Pixel XL mit Tapatalk
Just for clarity, the OP mentions TWRP-3.0.2-0 a couple times. It should be 3.2.0-0.
Nice write-up.
Sent from my Pixel XL using Tapatalk
pkelly517 said:
Just for clarity, the OP mentions TWRP-3.0.2-0 a couple times. It should be 3.2.0-0.
Nice write-up.
Click to expand...
Click to collapse
It'd be neat if I could edit my post from the XDA app. My screen and back glass broke... then the earpiece blew out so I was awaiting parts and haven't been online
I need to go away from the option of even flashing TWRP at kernel install. As everyone updates their kernels... I see it starts a looping issue now. Everything else is solid.
overlay folder
I am not grasping what the "overlay folder" refers to. What folder do i need to delete any time i flash magisk? I really appreciate the detail in the steps of this guide.
-Happy Feet- said:
When I understand it correctly, for a ROM installation I need to select slot a. (Standard for me). And slot b for Kernel installation and others.
But why my twrp installation was broken? After installation I can't boot to the system and unable to start the recovery, so I must flash the complete system images from Google.
Gesendet von meinem Pixel XL mit Tapatalk
Click to expand...
Click to collapse
Hey Happy feet.
From the beginning
Reboot recovery from stock.
Wipe data, system, and dalvik
Flash TWRP installer.zip after your wipe
Delete your overlay folder if you were rooted previously.
This is at Advanced/ File Manager/click on overlay and then hit delete.
Hit the HOME button in TWRP
Click on slot A and then reboot recovery
Back in recovery now IN SLOT A
Flash ROM
Now flash TWRP installer.zip again
Reboot recovery... Benzo ROM includes everything so you'd just be rebooting at this point into the Rom so read and reread the OP you downloaded from.
Flash Gapps (if needed for your ROM some have them built in)
After you flash the gapps if needed... then flash vendor (assuming it required from the dev who made the rom (like Benzo ROM has the vendor built in))
You do not have to flash TWRP at this point and can reboot directly into the Rom. If it doesn't boot or you hit a bootloop you did something out of order from the above, or there is something wrong with the Rom itself.
Second part... When I say Flash TWRP I mean the TWRP installer.zip there are 2 different files. The marlin-fastboot image and the Marlin Installer.zip. so if you flashed Twrp-3.2.0-0-marlin.img that is not enough... You have to have the twrp installer.zip downloaded on your internal storage to flash through TWRP and you no longer need to fastboot flash.
ROMs absolutely will erase your TWRP installer.zip and you need to reflash TWRP installer.zip before you reboot after you flash your ROM.
Sorry if I over explained it, not trying to make you feel like you don't know what you're doing, it's just very different than the old school installs.
Mikkey81 said:
Hey Happy feet.
From the beginning
Reboot recovery from stock.
Wipe data, system, and dalvik
Flash TWRP installer.zip after your wipe
Delete your overlay folder if you were rooted previously.
This is at Advanced/ File Manager/click on overlay and then hit delete.
Hit the HOME button in TWRP
Click on slot A and then reboot recovery
Back in recovery now IN SLOT A
Flash ROM
Now flash TWRP installer.zip again
Reboot recovery... Benzo ROM includes everything so you'd just be rebooting at this point into the Rom so read and reread the OP you downloaded from.
Flash Gapps (if needed for your ROM some have them built in)
After you flash the gapps if needed... then flash vendor (assuming it required from the dev who made the rom (like Benzo ROM has the vendor built in))
You do not have to flash TWRP at this point and can reboot directly into the Rom. If it doesn't boot or you hit a bootloop you did something out of order from the above, or there is something wrong with the Rom itself.
Second part... When I say Flash TWRP I mean the TWRP installer.zip there are 2 different files. The marlin-fastboot image and the Marlin Installer.zip. so if you flashed Twrp-3.2.0-0-marlin.img that is not enough... You have to have the twrp installer.zip downloaded on your internal storage to flash through TWRP and you no longer need to fastboot flash.
ROMs absolutely will erase your TWRP installer.zip and you need to reflash TWRP installer.zip before you reboot after you flash your ROM.
Sorry if I over explained it, not trying to make you feel like you don't know what you're doing, it's just very different than the old school installs.
Click to expand...
Click to collapse
Thanks for your help, great explained for an pixel Beginner.
Gesendet von meinem Pixel XL mit Tapatalk
beezza said:
I am not grasping what the "overlay folder" refers to. What folder do i need to delete any time i flash magisk? I really appreciate the detail in the steps of this guide.
Click to expand...
Click to collapse
Go to TWRP.
Open Mount and click to Mount System
Open Advanced and then choose File
If you find a folder in your root named 'overlay' tap on it (select it) and then click on delete.
If it's not there.... great. You've probably never rooted. It'll cause some bootloops once in a while, sometimes it doesn't matter. It's more important to do this at the point of flashing a room because you most likely will not get a fresh install to boot up if you're rooted.
Quick Note: This file carries over Magisk root data and gets messy as you update Magisk or reflash it.
I tried installing latest magisk on android "P" and was on Slot-B and it wouldnt install, error...
changed to slot-A and then it installed..
Magisk v16.3 (1630)
Thanks for info. good stuff i am new to pixel coming for my old friend nexus 6
just fyi I downloaded and flashed twrp-3.2.1-2-marlin before reading this and just happen the passcode thing for me is not a problem. Had to enter it twice the first time using twrp but now just once. works fine.
I don't give nearly enough appreciation where it's due but I gotta hand it to you... By far the best guide ever! Thank you!
Very good details and advice. I'm having far else problems by following these steps. Thanks for all your work.
commenting here to save this for future.
thank you OP!
hoping this thread is still alive. . . is there a recommended factory image to restore to? do i need to flash the factory on both slots? is it best to flash -the factory system.img on a particular slot? In the end which slot to --set_active=?
And how do the SLOTS come into play for doing a TWRP backup and doing a TWRP restore ?