Help! My phone is about to explode and only a true hero can fix it. Up for the challenge?
So I currently have multirom installed on my phone with a stock, kexec-able kernel. Everything seems to be running smoothly except for the fact that I have no multiboot menu. I have tried a stock kexec kernel and bouffla kernel with this however I have yet to find my hardboot menu.
Any help would be very appreciated!
flash multirom uninstaller
Flash multirom twrp
Flash multirom
Disable force overlay from multirom settings (this step is the cause mostly or all the time with me)
Transmitted via BACON
andybfmv96 said:
Help! My phone is about to explode and only a true hero can fix it. Up for the challenge?
So I currently have multirom installed on my phone with a stock, kexec-able kernel. Everything seems to be running smoothly except for the fact that I have no multiboot menu. I have tried a stock kexec kernel and bouffla kernel with this however I have yet to find my hardboot menu.
Any help would be very appreciated!
Click to expand...
Click to collapse
Alternatively, you can try "Inject boot sector". The boot menu is a part of boot.img, so if it's wiped or if it's completely fresh then MultiRom will not show up.
SirSoviet said:
Alternatively, you can try "Inject boot sector". The boot menu is a part of boot.img, so if it's wiped or if it's completely fresh then MultiRom will not show up.
Click to expand...
Click to collapse
Tried that actually. I've flashed multirom multiple times. I am having trouble with Kali Nethunter installation as well. Something g weird is going on with my phone and I don't know what it is...
MZO said:
flash multirom uninstaller
Flash multirom twrp
Flash multirom
Disable force overlay from multirom settings (this step is the cause mostly or all the time with me)
Transmitted via BACON
Click to expand...
Click to collapse
Just saw this. Trying now with a fresh install..
MZO said:
flash multirom uninstaller
Flash multirom twrp
Flash multirom
Disable force overlay from multirom settings (this step is the cause mostly or all the time with me)
Transmitted via BACON
Click to expand...
Click to collapse
i cant find that force overlay option actually...
Related
Looking for some input on clean ROM on the TF300T,
This is my second time trying to install it and both times it was successful, however as soon as the boot image loads up it stays stuck loading... I did download the file again thinking it may have been corrupted.
It has been sitting there loading for 20 minutes now.
I am using cwm the latest version and I did not install a kernel still running stock
Any ideas on what could cause this?
chibra said:
Looking for some input on clean ROM on the TF300T,
This is my second time trying to install it and both times it was successful, however as soon as the boot image loads up it stays stuck loading... I did download the file again thinking it may have been corrupted.
It has been sitting there loading for 20 minutes now.
I am using cwm the latest version and I did not install a kernel still running stock
Any ideas on what could cause this?
Click to expand...
Click to collapse
CWM has issues on this unit. Many, many complaints. I use twrp. If you decide to use twrp be sure to choose JB and tf300t version.
Clean ROM is freaking amazing! Seriously just do it I love the mods I can make for it too! Can't wait till I get my volume long press seek mod done! Love this device!
Sent from my SGH-T999
"So I put my phone into airplane mode and threw it... worst transformer ever. -.-" -My friend
tobdaryl said:
CWM has issues on this unit. Many, many complaints. I use twrp. If you decide to use twrp be sure to choose JB and tf300t version.
Click to expand...
Click to collapse
I initially when i first rooted intalled Twrp however i was not able to flash anything at all with it, it would give me errors.... that is the only reason i went to cwm.... I was able to make backups and restores with but ROMs flashing would just fail
chibra said:
I initially when i first rooted intalled Twrp however i was not able to flash anything at all with it, it would give me errors.... that is the only reason i went to cwm.... I was able to make backups and restores with but ROMs flashing would just fail
Click to expand...
Click to collapse
OK. It was just a suggestion since the problem you are experiencing is usually cleared by using twrp.
oryhight sullivan
tobdaryl said:
OK. It was just a suggestion since the problem you are experiencing is usually cleared by using twrp.
Click to expand...
Click to collapse
i m going to give twrp another shot...
i installed http://tinyw.in/5foT
JB version for the TF300T
This is the Rom i m trying to install
http://forum.xda-developers.com/showthread.php?t=2049322
Kernel is still stock and i ve left it that way through the aroma installer
Everytime i flash and reboot i get a boot loop
chibra said:
i installed http://tinyw.in/5foT
JB version for the TF300T
This is the Rom i m trying to install
http://forum.xda-developers.com/showthread.php?t=2049322
Kernel is still stock and i ve left it that way through the aroma installer
Everytime i flash and reboot i get a boot loop
Click to expand...
Click to collapse
I'm sorry it is hard to tell since you have chosen an older twrp to install. The current is five versions later and was updated as the kernels were updated to account for changes. The rom you are flashing is based on 10.4.4.25.
chibra said:
i installed http://tinyw.in/5foT
JB version for the TF300T
This is the Rom i m trying to install
http://forum.xda-developers.com/showthread.php?t=2049322
Kernel is still stock and i ve left it that way through the aroma installer
Everytime i flash and reboot i get a boot loop
Click to expand...
Click to collapse
Use TWRP 2.4.1.0
You are using a very old version of TWRP that has bugs with AROMA installer. So that is most likely where your issues are.
What ROM are you ccoming from? What boot loader are you on.
Sounds to me like you need to upgrade your boot loader and possibly do a full wipe - make sure you are on latest TWRP first otherwise you could brick if you use an older recovery!
sbdags said:
What ROM are you ccoming from? What boot loader are you on.
Sounds to me like you need to upgrade your boot loader and possibly do a full wipe - make sure you are on latest TWRP first otherwise you could brick if you use an older recovery!
Click to expand...
Click to collapse
Wise words. Nobody likes to listen to me so im glad someone else suggested it!
elesbb said:
Use TWRP 2.4.1.0
You are using a very old version of TWRP that has bugs with AROMA installer. So that is most likely where your issues are.
Click to expand...
Click to collapse
Updated the TWRP to the version you mentioned still stuck in boot loop.
sbdags said:
What ROM are you ccoming from? What boot loader are you on.
Sounds to me like you need to upgrade your boot loader and possibly do a full wipe - make sure you are on latest TWRP first otherwise you could brick if you use an older recovery!
Click to expand...
Click to collapse
The only ROM i was able to flash that was fully functioning is cm10.1,
i have also flashed PA 2.9 but had some bugs i couldn't stand (screen rotation not working, extended desktop with no pie)
as for boot loader it says 1.00e by "US _Epad-10.4.2.20-20121228" A03
I just updated the TWRP as recommended on the other post (v2.4.1.0)
on every flash i wipe dalvik / Cache / Factory reset.
Before attempting to boot into Clean Rom i also followed the steps on screen saying to wipe cache and dalvik.
I m hoping PA releases a 3.0 for this device and/or i m able to get Clean rom running
chibra said:
The only ROM i was able to flash that was fully functioning is cm10.1,
i have also flashed PA 2.9 but had some bugs i couldn't stand (screen rotation not working, extended desktop with no pie)
as for boot loader it says 1.00e by "US _Epad-10.4.2.20-20121228" A03
I just updated the TWRP as recommended on the other post (v2.4.1.0)
on every flash i wipe dalvik / Cache / Factory reset.
Before attempting to boot into Clean Rom i also followed the steps on screen saying to wipe cache and dalvik.
I m hoping PA releases a 3.0 for this device and/or i m able to get Clean rom running
Click to expand...
Click to collapse
If you are coming from cm10.1 you will definitely need to do a full wipe as it is non stock. It does say this in the first post. You only do a dalvik and cache wipe when upgrading from the same ROM or in CROMI's case from stock.
Do a data wipe in recovery, make sure you have a titanium backup or equivalent if you want to restore apps.
Success!!!
It worked perfectly fine after i install the back up i did before i flashed my 1st costume rom,
I rooted made a back up at stock/rooted... It just would not install from a full wipe,
it install fine once i flashed that specific backup and dirty flashed then wiped dalvik and cache before booting.
Hi, i've a stock + root + xposed google nexus 5 with a TWRP recovery; yesterday i've installed and used successfully MultiRom dualbooting CM11 M8 and a CM11S port for my device. Then i've tried to flash both CM11 M8 and CM11S (port) and i'm still getting some problems with the boot:
-if i turn off the device and then start it again the system boots normally and without problems, but if i try to reboot from within the ROM it doesn't work properly, i only see a black screen and, if i reboot to recovery, i'm unable to restore the backup because the recovery is "unable to mount data".
-The only solution is to shut down again the N5, turn it on, shut down again and then boot directly into recovery mode.
NOTE:
before you ask, i performed a full wipe (the default wipe of TWRP that wipes data, dalvik and cache) and then flashed the ROMs
Any idea of why i'm not able to install custom roms without issues? any help would be appreciated
Spartiata said:
Hi, i've a stock + root + xposed google nexus 5 with a TWRP recovery; yesterday i've installed and used successfully MultiRom dualbooting CM11 M8 and a CM11S port for my device. Then i've tried to flash both CM11 M8 and CM11S (port) and i'm still getting some problems with the boot:
-if i turn off the device and then start it again the system boots normally and without problems, but if i try to reboot from within the ROM it doesn't work properly, i only see a black screen and, if i reboot to recovery, i'm unable to restore the backup because the recovery is "unable to mount data".
-The only solution is to shut down again the N5, turn it on, shut down again and then boot directly into recovery mode.
NOTE:
before you ask, i performed a full wipe (the default wipe of TWRP that wipes data, dalvik and cache) and then flashed the ROMs
Any idea of why i'm not able to install custom roms without issues? any help would be appreciated
Click to expand...
Click to collapse
I doubt it, but could it be because you have Snapshot M8 installed twice? ("CM11S" is not a port, it is Snapshot M8 with CM11S apks placed into the zip). I would try with two different ROMs.
Lethargy said:
I doubt it, but could it be because you have Snapshot M8 installed twice? ("CM11S" is not a port, it is Snapshot M8 with CM11S apks placed into the zip). I would try with two different ROMs.
Click to expand...
Click to collapse
i've full wiped the device before flashing the ROMs, and i've uninstalled all the MultiRoms installation before flashing the new ROM
Spartiata said:
i've full wiped the device before flashing the ROMs, and i've uninstalled all the MultiRoms installation before flashing the new ROM
Click to expand...
Click to collapse
Not sure what to tell you except try another ROM first.
Lethargy said:
Not sure what to tell you except try another ROM first.
Click to expand...
Click to collapse
i'll try with paranoid and let you know
Paranoids works fine, seems like a CM problem .-.
Spartiata said:
Paranoids works fine, seems like a CM problem .-.
Click to expand...
Click to collapse
CyanogenMod will always be CyanogenMod
First time using MultiRom. I currently have CM11S with AK kernel as my primary rom. I have a TWRP backup of CM12 5.0 also. I would like to use MultiRom with them so I can use each whenever I want without having to wipe/restore each time. I read on the MultiRom thread that CM12 has to be the primary rom for it to work. I don't want to mess anything up, any help would be appreciated.
You read right, lollipop ROMs only work with Multirom if they're the primary ROM.
Transmitted via Bacon
timmaaa said:
You read right, lollipop ROMs only work with Multirom if they're the primary ROM.
Transmitted via Bacon
Click to expand...
Click to collapse
Not sure exactly how to do it without messing anything up, do I just make the 5.0 into the secondary rom, and then swap it with the primary? Or is it more complicated than that.
BlakeSm said:
Not sure exactly how to do it without messing anything up, do I just make the 5.0 into the secondary rom, and then swap it with the primary? Or is it more complicated than that.
Click to expand...
Click to collapse
I thought there were pretty comprehensive instructions in the Multirom thread? You can't make 5.0 a secondary ROM, full stop, so that won't work. Just flash 5.0 like you normally would then add CM11S as a secondary.
Transmitted via Bacon
BlakeSm said:
Not sure exactly how to do it without messing anything up, do I just make the 5.0 into the secondary rom, and then swap it with the primary? Or is it more complicated than that.
Click to expand...
Click to collapse
Make a backup of your primary ROM(cm11s) then in multirom recovery add a second rom and restore the backup of your cm11s ROM.
Next, wipe the primary ROM. (Data, system, dalvik & cache) then flash 5.0 with gapps and AK kernel for CM 12
Thanks guys!
It's been a while since I've touched my OPO since I've been using my OPT as my daily. I'm still on YNG1TAS2I3 on my OPO running stock everything. At the moment it is not rooted, with no custom recovery, but the bootloader IS unlocked. I also had xposed installed with some modules but I ran the xposed uninstaller arm.zip version in TWRP and removed the modules.
Is it possible to dirty flash YNG4PAS1N0 which is CM12.1 onto my OPO? I've tried installing TWRP and then fastbooting CM12.1 but it causes a bootloop. I had to re-fastboot flash CM12.0 to get out of it. I've tried it with TWRP 3.0.2.0 and TWRP 2.8.6.0. I also tried sideloading it but again-- bootloop. Reflashing CM12.0 causes CM recovery to rewrite TWRP even though I don't flash the recovery partition. So it took me a LONG time to get TWRP installed again for all these trials.
At this point is my only option to do a complete wipe and then flash? Even trying to run the OTA update for YNG4PAS1N0 causes a bootloop.
I think fastboot wipe the partition then flash it, else upgrade incrementally (I know it'd suck)
Transmitted via BACON
MZO said:
I think fastboot wipe the partition then flash it, else upgrade incrementally (I know it'd suck)
Transmitted via BACON
Click to expand...
Click to collapse
Well the problem is even incrementally updating it is kicking it into bootloop like I said.
crazykidguy said:
Well the problem is even incrementally updating it is kicking it into bootloop like I said.
Click to expand...
Click to collapse
Then
Instead of normal flashing you should fastboot erase <partition> and then flash it.
Transmitted via BACON
Since a lot of people have had trouble flashing Custom ROMs, I decided to create a guide that should work on every device (whether A/B partition or not) except on Samsung devices. For bypassing Decryption Issues, adb sideload the .zip files.
GUIDE
I am assuming you have unlocked your Bootloader, flashed TWRP and have some knowledge on ADB.
[This is known as a clean install or clean flash]
Turn off Lockscreen Security
Reboot to Recovery
Factory Reset
Format Data
Copy the .zip files from your PC to your phone / Plug in your USB OTG
Flash the ROM and then the Recovery Installer (No Magisk/SuperSU after)
Reboot to Recovery
Flash GApps and Magisk/SuperSU
Reboot to System
[This is known as a dirty flash]
To update the custom ROM or fix a error (Bootloop after successful first boot, No Service, etc.)
I am assuming you used my guide to flash the custom ROM
These are basically the same steps but without wiping or formatting data
Turn off Lockscreen Security
Reboot to Recovery
Flash the ROM (has to be the same ROM, updated is recommended, older versions may cause issues) and then the Recovery Installer (No Magisk/SuperSU after)
Reboot to Recovery
Flash GApps and Magisk/SuperSU
Reboot to System
LINKS:
Official GApps Website - GApps Github
Official TWRP Website - TWRP Github
Magisk Forum - Magisk Thread - Magisk Github
Official SuperSU Website - SuperSU Forum - SuperSU Thread - SuperSU Github
I recommend the Nano variant of GApps since I have had no error with it.
Enjoy!
[Disabler-ONLY]
`This is basically the same guide just if you want to flash Zackptg5's "Universal DM-Verity, ForceEncrypt, Disk Quota Disablers" or any other disabler which requires different steps.
[This is known as a clean install or clean flash]
Turn off Lockscreen Security
Reboot to Recovery
Format Data
Copy the .zip files from your PC to your phone / Plug in your USB OTG
Flash the ROM and then the Recovery Installer (No Magisk after)
Reboot to Recovery
Flash the Disabler, Magisk and then GApps
Reboot to System
Profit
Dirty Flash? You can't. Usually when using a Disabler you have to clean install your custom ROM.
To update use the method in the first post but for step number 5 Flash the Disabler, Magisk and then GApps
This is a bit much to do. Just use twinnfamous' twrp and you can flash a custom easily. Plus, I flash havoc over crdroid, then back and forth again. So you can flash over. Just have to wipe data and cache after ROM flash and twrp flash then reboot to recovery.
Basically:
Fastboot boot twrp (twinnfamous' 0.7)
Be on 9.0.7 firmware as most custom ROMs use this base right now I think..
Anyway, then flash twrp (twinnfamous' 0.7 installer zip)
Reboot to recovery
Now flash custom ROM
Flash twrp zip
Reboot to recovery
(You'll now be on the opposite slot as before, which means you are on the slot which your new custom ROM was installed)
Wipe > custom > data and cache wipe
Install opengapps nano and magisk 18.0
Reboot system
You'll boot right into the ROM setup screen with no decryption issues along the way as long as you do exactly as I said.
Have fun flashing!
dpryor88 said:
This is a bit much to do. Just use twinnfamous' twrp and you can flash a custom easily. Plus, I flash havoc over crdroid, then back and forth again. So you can flash over. Just have to wipe data and cache after ROM flash and twrp flash then reboot to recovery.
Basically:
Fastboot boot twrp (twinnfamous' 0.7)
Be on 9.0.7 firmware as most custom ROMs use this base right now I think..
Anyway, then flash twrp (twinnfamous' 0.7 installer zip)
Reboot to recovery
Now flash custom ROM
Flash twrp zip
Reboot to recovery
(You'll now be on the opposite slot as before, which means you are on the slot which your new custom ROM was installed)
Wipe > custom > data and cache wipe
Install opengapps nano and magisk 18.0
Reboot system
You'll boot right into the ROM setup screen with no decryption issues along the way as long as you do exactly as I said.
Have fun flashing!
Click to expand...
Click to collapse
You wasted that post just for this? I assure you that my tutorial guarantees success when using a official or unofficial version of TWRP or custom ROM, I also used the method you posted about but it did not work. Also what do you mean by "9.0.7"?
The GApps version you use doesn't have to be Nano and Magisk doesn't have to be v18.0. I'm sure you just copy-pasted this, my method should always succeed. The TWRP doesn't have to be from @twinnfamous , it can be from any developer. This is not a OnePlus 6T only guide.
This flashing process is difficult in my view. Why are you making the simple custom rom flashing process so difficult for the noobs.
_Masked_ said:
You wasted that post just for this? I assure you that my tutorial guarantees success when using a official or unofficial version of TWRP or custom ROM, I also used the method you posted about but it did not work. Also what do you mean by "9.0.7"?
The GApps version you use doesn't have to be Nano and Magisk doesn't have to be v18.0. I'm sure you just copy-pasted this, my method should always succeed. The TWRP doesn't have to be from @twinnfamous , it can be from any developer. This is not a OnePlus 6T only guide.
Click to expand...
Click to collapse
Why are you angry? Haha.
And you linked this from the op6t forums so I'm commenting on that phone. And that's how it's done on that phone. And it does matter which twrp you use for THAT phone because one doesn't decrypt correctly.
Copy and paste? No... And nano is always best if you read xda basically anywhere. Not that I said you HAVE to use nano anyway.. it was just in my steps. And that works for me with any/every ROM. So don't be so opposed to other suggestions. Your method is really weird and involves way too much use of a computer/fastboot. Kind of defeats the purpose of using twrp, don't you think?
Ashwinrg said:
This flashing process is difficult in my view. Why are you making the simple custom rom flashing process so difficult for the noobs.
Click to expand...
Click to collapse
What is making it difficult is encryption/decryption not working right in twrp yet (just a guess). I was having a hell of a time getting anywhere myself and kept getting my storage all jumbled from encryption until I found this thread which put it together for me with the adb sideload part, that bypasses encryption or at least lets you flash what you want when the folder names get all wonky.
Thanks OP for laying it out so clearly for me, I am an old dinosaur that was hesitating on messing with this a/b nonsense until I got my 6T and got the itch again. My trusty dusty nexus 6 is so much easier but it's also been around and has one system and a solid twrp for it.
Cheers! :good:
raiderep said:
What is making it difficult is encryption/decryption not working right in twrp yet (just a guess). I was having a hell of a time getting anywhere myself and kept getting my storage all jumbled from encryption until I found this thread which put it together for me with the adb sideload part, that bypasses encryption or at least lets you flash what you want when the folder names get all wonky.
Thanks OP for laying it out so clearly for me, I am an old dinosaur that was hesitating on messing with this a/b nonsense until I got my 6T and got the itch again. My trusty dusty nexus 6 is so much easier but it's also been around and has one system and a solid twrp for it.
Cheers! :good:
Click to expand...
Click to collapse
Sorry for the late reply, but yes this is for bypassing TWRP Decryption issues.
_Masked_ said:
Since a lot of people have had trouble flashing Custom ROMs, I decided to create a guide that should work on every device (whether A/B partition or not) except on Samsung devices.
GUIDE
I am assuming you have unlocked your Bootloader, flashed TWRP and have some knowledge on ADB.
[This is known as a clean install or clean flash]
Turn off Lockscreen Security
Reboot to Recovery
Format Data (Wipe)
Flash ROM and then the Recovery Installer (No Magisk after)
Reboot to Recovery
Go to Advanced, ADB Sideload then sideload GApps, the Recovery Installer and Magisk
Reboot to System
Profit
I recommend the Nano variant of GApps since I have had no error with it.
Enjoy
Click to expand...
Click to collapse
this step means need do with pc not by twrp
ayed78 said:
this step means need do with pc not by twrp
Click to expand...
Click to collapse
This is to bypass Decryption issues.
Ashwinrg said:
This flashing process is difficult in my view. Why are you making the simple custom rom flashing process so difficult for the noobs.
Click to expand...
Click to collapse
I mean I could make a tool for flashing a custom ROM but I'm sure that there's a tool for that already.
bump. (ignore)
_Masked_ said:
Turn off Lockscreen Security
Reboot to Recovery
Factory Reset
Format Data
Copy the .zip files from your PC to your phone / Plug in your USB OTG
Flash the ROM and then the Recovery Installer (No Magisk/SuperSU after)
Reboot to Recovery
Flash GApps and Magisk/SuperSU
Reboot to System
Click to expand...
Click to collapse
So when are we required to wipe system in addition to just a factory reset? And when do we need to format data?
Krullendhaar said:
So when are we required to wipe system in addition to just a factory reset? And when do we need to format data?
Click to expand...
Click to collapse
Just follow the steps, in order.
Hi.
What if I want to flash a custom kernel on a clean Rom flash? When should I do it? Together with Magisk and Gapps?
What do you mean by "Recovery Installer"? That's the only thing I don't understand.
Thank you for this guide.
Santi3598 said:
What do you mean by "Recovery Installer"? That's the only thing I don't understand.
Thank you for this guide.
Click to expand...
Click to collapse
Same here, I do not understand why I should flash a recovery img when twrp does seem to stay installed after flashing everything. Maybe the custom rom I use does include twrp ?
Custom rom means bugs, possible privacy leak and overall less polished. Developer that are working on them are fantastic but they are most of the time nowhere near as what offer the stock one.
What you need is to check adb, doesn't need root but you can still remove apps (even system one) and do more tweaks.
If needed, check how to patch boot image with magisk, it works on all phone and get you root.
With that, you're free to debloat your device.
Hey just one little question: is it ok to dirty flash with encrypted data folder ?
Santi3598 said:
What do you mean by "Recovery Installer"? That's the only thing I don't understand.
Click to expand...
Click to collapse
Me neither, is it safe to assume that the step can be left out if TWRP is already there and I use it to flash the ROM?
Santi3598 said:
Thank you for this guide.
Click to expand...
Click to collapse
+1