Successfully installed twrp, now I am just curious: must any rom we flash be loki'd to work? not really an issue but wanna know my limits... we arent gonna be ablec o just flash canadian roms then, right? (until they are loki'd)
t2abousa said:
Successfully installed twrp, now I am just curious: must any rom we flash be loki'd to work? not really an issue but wanna know my limits... we arent gonna be ablec o just flash canadian roms then, right? (until they are loki'd)
Click to expand...
Click to collapse
This is going to become a huge problem if people don't start reading about what it is they are doing to their phones...
http://forum.xda-developers.com/showthread.php?t=2292157
"I've installed a Loki-patched recovery. Can I just install regular custom ROMs now?
Any ROMs that include a replacement boot.img must be modified to include a Loki-patched boot.lok file instead. Otherwise, your phone will fail to boot until you restore a Samsung-signed boot.img or a custom boot.lok image via your custom recovery, or flash a stock image via Odin.
"
scott14719 said:
This is going to become a huge problem if people don't start reading about what it is they are doing to their phones...
http://forum.xda-developers.com/showthread.php?t=2292157
"I've installed a Loki-patched recovery. Can I just install regular custom ROMs now?
Any ROMs that include a replacement boot.img must be modified to include a Loki-patched boot.lok file instead. Otherwise, your phone will fail to boot until you restore a Samsung-signed boot.img or a custom boot.lok image via your custom recovery, or flash a stock image via Odin.
"
Click to expand...
Click to collapse
As always a good answer from the king.
Related
I want to root my N7 directly from Linux, but I don't want to replace recovery with CWM. I like CWM on my phone, but I understand it won't allow OTA stock upgrades which I expect will be important for a while on the N7.
I've already unlocked the bootloader, but I haven't seen any instructions for rooting from Linux without replacing the standard recovery with CWM.
Can't you just flash CWM, root, and then reflash stock recovery?
sray1 said:
... but I understand it won't allow OTA stock upgrades which I expect will be important for a while on the N7.
Click to expand...
Click to collapse
There won't be any OTA that is not quickly (if not before it is released) will be available is a flashable download on XDA and other forums.
You are not going to miss anything.
You can as already posted, reflash the stock recovery, but again, whats the point.
rohan32 said:
Can't you just flash CWM, root, and then reflash stock recovery?
Click to expand...
Click to collapse
Where would I find the stock recovery?
Hi, I am not too sure if I posted this in the right place or not but please let me know if it is posted in the wrong place. I am actually relatively new towards rooting of an android device so i need to clear my doubts.
I used Wugfresh toolkit to root my Nexus 10. The toolkit also have an option to install TWRP. But the version of TWRP is not the most updated one. So, can I just download the latest one and flash it or i need to remove the current one before I can update the version.
Also, I am interested in flashing a custom ROM. But my question is if a new stock firmware is out, how am i going to update to the latest stock firmware when I am in a custom ROM.
Please let me know if you don't understand my question. I will try my best to explain further and also thank you in advance.
iOrdinary said:
Hi, I am not too sure if I posted this in the right place or not but please let me know if it is posted in the wrong place. I am actually relatively new towards rooting of an android device so i need to clear my doubts.
I used Wugfresh toolkit to root my Nexus 10. The toolkit also have an option to install TWRP. But the version of TWRP is not the most updated one. So, can I just download the latest one and flash it or i need to remove the current one before I can update the version.
Also, I am interested in flashing a custom ROM. But my question is if a new stock firmware is out, how am i going to update to the latest stock firmware when I am in a custom ROM.
Please let me know if you don't understand my question. I will try my best to explain further and also thank you in advance.
Click to expand...
Click to collapse
TWRP typically recommends installing and updating their recovery via Goo's app thing, but if you know where to look (openrecovery on goo + manta), you can get the .img and then flash it with fastboot. I usually do fastboot erase recovery and then fastboot flash boot TWRP-IMAGE.img. But if you don't feel too comfortable with fastboot, then Goo's program should take care of it I think.
If you want to try the latest stock when you're using a custom ROM, you'll need to flash the latest factory image from Google to go back stock, and then update it (unless the factory image is updated to the latest, which doesn't usually happen till days later). Just want to make sure you backup anything important.
espionage724 said:
TWRP typically recommends installing and updating their recovery via Goo's app thing, but if you know where to look (openrecovery on goo + manta), you can get the .img and then flash it with fastboot. I usually do fastboot erase recovery and then fastboot flash boot TWRP-IMAGE.img. But if you don't feel too comfortable with fastboot, then Goo's program should take care of it I think.
If you want to try the latest stock when you're using a custom ROM, you'll need to flash the latest factory image from Google to go back stock, and then update it (unless the factory image is updated to the latest, which doesn't usually happen till days later). Just want to make sure you backup anything important.
Click to expand...
Click to collapse
So, for TWRP, it means that I can restore the stock recovery before I flash the TWRP img right? Because I am using the Wugfresh toolkit to run all these fashboot commands and they only have the options to either flash a custom recovery or to restore the stock recovery.
As for the custom ROMs, every time I flash a ROM, all my stuff in my Nexus 10 will be gone right? For example my game progress etc. Because if I were to backup, I will make a nandroid backup which means every single thing in my nexus. So, correct me if I am wrong. Every time I flash a ROM, my nexus will be back to a clean state right?
Thank you in advance for your answers. ^^
I wondered if we can install zip files using flashify onto rooted Stock G2 KitKat but it asks which custom recovery I am using. Since we don't have a working custom recovery for KitKat yet. . .
Is it perhaps possible to 1. backup stock recovery using flashify, 2. turn the backup into a recovery.zip, 3. flash a new custom recovery using Goo, 4. boot into custom recovery, 5. flash desired zip, 6. flash backed up recovery.zip, 7. reboot back into stock OS?
EDIT - I may have over thought this, maybe a file manager with root access would be easier.
No. No. No. And no. There is no recovery on kit Kat did you cannot flash anything... yet
Sent from my LG-D800 using Tapatalk
arie001 said:
I wondered if we can install zip files using flashify onto rooted Stock G2 KitKat but it asks which custom recovery I am using. Since we don't have a working custom recovery for KitKat yet. . .
Is it perhaps possible to 1. backup stock recovery using flashify, 2. turn the backup into a recovery.zip, 3. flash a new custom recovery using Goo, 4. boot into custom recovery, 5. flash desired zip, 6. flash backed up recovery.zip, 7. reboot back into stock OS?
Click to expand...
Click to collapse
according to one of the many threads of creating a recovery or rooting g2 4.4.2 I read that flashify does not work(not sure don't remember, something related to this) also another thing to note is the new bootloader checks the recovery and unless it's 100% stock it will just boot you into fastboot mode(where you can soehow reflash the stock one again so it can boot normally) something around those lines so as to your second question I think not but as I'm not a dev I maybe wrong
tdevaughn said:
No. No. No. And no. There is no recovery on kit Kat did you cannot flash anything... yet
Sent from my LG-D800 using Tapatalk
Click to expand...
Click to collapse
XxZombiePikachu said:
according to one of the many threads of creating a recovery or rooting g2 4.4.2 I read that flashify does not work(not sure don't remember, something related to this) also another thing to note is the new bootloader checks the recovery and unless it's 100% stock it will just boot you into fastboot mode(where you can soehow reflash the stock one again so it can boot normally) something around those lines so as to your second question I think not but as I'm not a dev I maybe wrong
Click to expand...
Click to collapse
Thanks for the quick responses
Sigh. . Yeah I thought of that as soon as I posted that the boot loader is the problem making a boot into custom recovery impossible on the KitKat boot loader.
For what it's worth I tried flashing a .zip with flashify and let it think I had CWM installed. I did NOT flash a custom recovery though and when rebooted it just reboots as normal with nothing flashed.
I just installed TWRP (2.6.x) from GooManager (per the all-in-one thread here: http://forum.xda-developers.com/showthread.php?t=2314494), and I'm about to flash the GPE ROM by Danvdh. I understand that this ROM is NOT loki'd, and that normally I'd need to flash loki-doki, but I suspect that this TWRP is an "auto-loki" version, where it will automatically patch any new kernels that are installed. How would I know that this is the case?
godefroi said:
I just installed TWRP (2.6.x) from GooManager (per the all-in-one thread here: http://forum.xda-developers.com/showthread.php?t=2314494), and I'm about to flash the GPE ROM by Danvdh. I understand that this ROM is NOT loki'd, and that normally I'd need to flash loki-doki, but I suspect that this TWRP is an "auto-loki" version, where it will automatically patch any new kernels that are installed. How would I know that this is the case?
Click to expand...
Click to collapse
if it boots and just sits there at the boot screen, chances are the recovery is not auto loki'ed, I flash the loki patch everytime a flash a rom to be on the safe side. Good luck
godefroi said:
I just installed TWRP (2.6.x) from GooManager
Click to expand...
Click to collapse
I think the only "auto-loki" is a CWM one called Philz recovery so chances are you'll need the loki-doki zip.
Its like 1MB anyways, might as weljust download it and keep it on your phone. It doesn't matter what rom or recovery your using its the same zip file and most recoverys let you flash more than one zip at a time anyways.
correct on all above
twrp is loki'd, so you can flash it. but does not auto loki non-loki'd roms etc
so flash loki after your mentioned rom
like AX, if in doubt i flash loki-doki anyway
:good:
Hi all! I am sorry if this has been asked before but I couldn't find a definitive answer in here.
I bought OnePlus 8 Pro from the official website in April and I feel it's time to flash a custom kernel. I've been modding my phones since 2011 using Xperia Neo back then.
1. If I unlock my bootloader will I still be able to receive official updates?
2. How exactly do you flash a custom kernel? At the moment I have no intentions on rooting the phone.
3. Is the procedure for flashing a custom ROM the same as the kernel?
4. Does unlocking my bootloader delete everything from the phone?
A lot has changed since Android 8 and 9 so I feel like a complete noob.
Thank you for the help in advance!
1. Yes as long as your boot partition is stock/aka not rooted or using custom kernel, you can take regular otas.
2. If rooted you can use ex kernel manager... If not you'd boot to bootloader and use fastboot commands to modify the boot image.. Note after this you wouldn't be able to take otas until you flash back stock boot img.
3. Yes very similar, you'd flash different partitions in bootloader using fastboot commands.
4. Yes, same as relocking.
You should be able to install OTA regardless of what kernel you're using.
I recommend Franco Kernel Manager for flashing kernels.
There should be instructions on how to install ROMs with fastboot. You use fastboot and fastbootd (new fastboot for system) depending on what partition you flash.
Lossyx said:
You should be able to install OTA regardless of what kernel you're using.
I recommend Franco Kernel Manager for flashing kernels.
There should be instructions on how to install ROMs with fastboot. You use fastboot and fastbootd (new fastboot for system) depending on what partition you flash.
Click to expand...
Click to collapse
I reckon I need to root to use Franco kernel manager and I shoul be able to flash any kernel just using fastboot?
Regarding the OTA, I read that you need to be on stock kernel to be able to install it so I guess I will wait for the December update and then go through the whole process of bootloader unlock etc.
kokope28 said:
I reckon I need to root to use Franco kernel manager and I shoul be able to flash any kernel just using fastboot?
Regarding the OTA, I read that you need to be on stock kernel to be able to install it so I guess I will wait for the December update and then go through the whole process of bootloader unlock etc.
Click to expand...
Click to collapse
Yes you need root in order to flash a kernel zip using kernel manager. Flashing a kernel through fastboot requires just the boot image, which i don't think any kernel provides standalone.
And no, you don't need to be have stock kernel to flash an OTA. I have no idea why someone would write that.
Lossyx said:
Yes you need root in order to flash a kernel zip using kernel manager. Flashing a kernel through fastboot requires just the boot image, which i don't think any kernel provides standalone.
And no, you don't need to be have stock kernel to flash an OTA. I have no idea why someone would write that.
Click to expand...
Click to collapse
I haven't tried a lot of kernels but in my experience coming from other phones like pixels.... When boot.img gets modified it will fail ota updates...I tried it with this phone with a rooted boot.img and it failed so I assumed a kernel modified boot.img would be the same. Much apologies if I'm incorrect... But that's my reasoning for writing my post.
Updating isn't an issue.
My guide for doing just that amongst other things.
(ROOT) Android 11 / Latest stock and patched img's / payload dumper / magisk_patched guides
Hi all, Have seen a lot of requests for patched boot images on these threads so thought i'd share a guide on how to get it yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it...
forum.xda-developers.com
Personal I use ex kernel manager. Hasn't failed me yet.
Auth apps have worked for me, as does gpay so you should be ok.
Titanium / swift might do it but the OS won't be the same so the apps could notice that.
Just set them back up, the more you do it the easier it is.
Probably best to deactivate first so it's easier to enrol on your new OS