If you flash a modded kernel, how do you go back if you don't like it or something goes wrong? If it's a bad Kernel flash will you have the option to boot to recovery (TWRP) still?
vulcan4d said:
If you flash a modded kernel, how do you go back if you don't like it or something goes wrong? If it's a bad Kernel flash will you have the option to boot to recovery (TWRP) still?
Click to expand...
Click to collapse
You can reflash the zip (in TWRP) of the rom you running then it should revert to the kernel that come with the rom. The custom kernel should got nothing to do with TWRP. If you got bootloop or something just use hardware combo (Power + Vol up) to enter TWRP and reflash the rom zip as mentioned.
vulcan4d said:
If you flash a modded kernel, how do you go back if you don't like it or something goes wrong? If it's a bad Kernel flash will you have the option to boot to recovery (TWRP) still?
Click to expand...
Click to collapse
I usually backup my kernel (boot) in twrp before modding. That makes it easy. Otherwise you can flash a new kernel boot.img using fastboot or twrp. Just have to get the boot.img.
Related
Before the problem, I had a 4.1.1 rooted unlocked N7 with original ROM. I decided to apply the OTA update (03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip) from TWRP recovery using the option to manually install zip updates.
The tablet rebooted, and I used Voodoo OTA RootKeeper to regain root access. Everything worked fine, I had no error messages at any moment during the procedure and the 4.1.2 update was applied successfully, as I could verify in the info section and by testing the landscape mode.
But, when I try to reboot in recovery using the option in ROM Manager, all I get is the little robot on his back image without any message. The only way to get out of this screen is to press the power button for a few seconds until it reboots into Android. Everything is fine except the recovery mode.
I tried to reflash the recovery image using Wug's Toolkit to no avail. I tried CWM, TWRP and stock recoveries but none worked. I always get the same screen with the robot on his back when I try to boot into recovery. Booting normally is always fine, only recovery seems to be affected. If I use Wug's toolkit to boot a temporary TWRP recovery image, it works but I want to be able to boot as before, with ROM Manager.
Any ideas? Is there a solution other the wipe it all and restart from scratch?
[edit] I can start into Fastboot but if I try to go to recovery from there, the same thing happens...
I fixed it by flashing the older 3.34 bootloader. So something is wrong with the new 3.41 bootloader.
There is nothing wrong with the process.
Its the users interpretation of how it works.
After updating, the file that flashes the stock recovery on boot is put back.
So he flashed in custom recovery.
Booted at which point the custom recovery is replaced with stock
Then wonders why he can't access custom recovery anymore.
Just reflash custom recovery
Sent from my HTC One X using xda app-developers app
bagofcrap24 said:
There is nothing wrong with the process.
Its the users interpretation of how it works.
After updating, the file that flashes the stock recovery on boot is put back.
So he flashed in custom recovery.
Booted at which point the custom recovery is replaced with stock
Then wonders why he can't access custom recovery anymore.
Just reflash custom recovery
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Not true. I flashed the update through cwm and everything went fine. When you reboot the system, cwm asks if you want to flash recovery and keep root. I denied to flash the stock recovery and I kept the root. After that you can't get into recovery at all (stock or cwm or whatever). but if I downgrade my bootloader to 3.34 everything is ok. I also installed new bootloader through cwm manually again and after that I can't boot into recovery.
Btw... How to flash bootloader.raw with fast boot???
Sent from my Nexus 7 using Tapatalk 2
sikagoon7 said:
I think you are a bit misinformed. When you flash the OTA the recovery-from-boot.p is installed by default. It resets the recovery to stock every time you reboot. CWM does nothing to remedy this. The only way to fix it is to remove or rename the file to disable its function. After and ONLY after this will you be able to flash recoveries by choice and boot into them.
And while it is your choice to use whatever recovery you desire I personnaly think using stock recovery and adb sideload is the safest when it comes to signed stock OTA.zips. After that you can root and flash your recovery of choice as if you have a brand new device.
When it comes to the bootloader. Stock system, boot, and recovery verify which bootloader you are using. JRO03D looks for 3.34 and JZO54K looks for 3.41. I don't know the implications of switching them but I don't think I will test that. I've already had a bad experience with dismantling a bootloader. The bootloader is an IMG file. Download the JRO03D factory image from Google's website and extract it. Inside will be a file named bootloader-grouper-3.34.img. THAT is the stock JRO03D bootloader and that is what you need to flash using: fastboot flash bootloader bootloader-grouper-3.34.img.
Click to expand...
Click to collapse
Yes I know that and did that from the beginning (renamed the file) but the point is that you can't boot into recovery (stock or whatever). It tries to boot into recovery I think but it reboots again and loads the OS. I'm using 3.34 booatloader with 4.12 and haven't got any probs yet.
Finally Got it Working
I tried one last thing yesterday. I got into ROM Manager and used the option to flash CWM Recovery. Then I rebooted in CWM (using the ROM Manager option). All was fine and when I chose the option to reboot, CWM asked me if I would like to make the custom recovery permanent because it would otherwise be rewritten at boot (this is what caused my problems, I believe). I choose to do so and it worked normally after that.
I then downloaded the TWRP recovery (http://www.teamw.in/project/twrp2/103) and installed it with Wug's Toolkit using the option to flash a permanent Recovery from a file. I didn't modify the "recovery-from-boot.p" file because I thought that CWM already did that. Tested booting into recovery again and all is finally OK with TWRP.
One of the benefits of the 4.1.2 update is that I can now boot into recovery from the Fastboot menu.
I'm in the same boat, ended up flashing the factory image for jz054k (which included the new bootloader) to try and fix.. now I'm without root and without a recovery..
I'm unlocked, but flashing alternative recoveries just doesn't work right now.. can't boot them up.
Did the original author ever get this resolved?
-m
diomark said:
I'm in the same boat, ended up flashing the factory image for jz054k (which included the new bootloader) to try and fix.. now I'm without root and without a recovery..
I'm unlocked, but flashing alternative recoveries just doesn't work right now.. can't boot them up.
Did the original author ever get this resolved?
-m
Click to expand...
Click to collapse
There are mixed reports on bootloader 3.41 and booting recovery. I have not been able to properly boot recovery from 3.41 under any circumstances. If you have this issue as well, flash the 3.34 bootloader from JRO03D. Doing this has allowed me to use recovery again.
I was running 4.1.2 with old bootloader 3.34 and had a SOD while my Nexus was charging last night.
In Faux123's kernel thread, he told me:
You should use the new boot loader and stick with CWM for now until TWRP get their stuff compatible with 4.1.2. Boot loader initialize the power regulators to some know state for the machine to boot until the kernel takes over.. and the new kernel is expecting it to be initialize certain ways... This was the biggest difference between 4.1.1 and 4.1.2... so I HIGHLY recommend using the matching bootloader...
Click to expand...
Click to collapse
Steps I had to take to get 4.1.2 (rooted, stock rom, custom kernel):
flash stock 4.1.1 boot.img and recovery.img
flash 4.1.1 bootloader 3.34
flash recovery TRWP recovery
flash SuperSU (regain root)
flash CWM lastest recovery 6.0.1.5 (beta) based on Faux123 advice above
flash 4.1.2 bootloader 3.41
No problems so far. This whole process has taken days...
I'm finally where I want to be.
Oops, wrong thread...
Hi all
this summer i've rooted the g2 d802 with autorec i've installed the twrp 2.7 and installed cm12, when 12.1 come out i've just wiped all and flashed the new rom, now everything go fine, but i'd like to try the newer version ^^
i've read some stuff but i'm a newbie, so i'm pretty confused, correct me if i'm wrong
with autorec i've downgraded the bootloader to JB version so i cant install the CM13
i should:
1)update to the latest twrp BUMPED
2)than go to recovery and flash the lastes bootstack
3)reboot to recovery
4)flash the CM13
can i update the 2.7 twrp to the latest one if the older isnt bumped? and how can i update it? i just have to flash it from the older twrp or should i use flashify or something like that?
let me know if the procedure is correct thanks for the help
You need to update the bootloader & I recommend the latest TWRP. Then you're good to go. Going from Lollipop -> Marshmellow isn't as smooth as an incremental Lollipop -> Lollipop update.
Do create a TWRP image backup & titanium application backup beforehand.
I've tried Marshmellow, but AICP Lollipop has much better performance, more features, far more stable & comparable battery life when using servicely. It's still a work in progress.
niubboxp said:
Hi all
this summer i've rooted the g2 d802 with autorec i've installed the twrp 2.7 and installed cm12, when 12.1 come out i've just wiped all and flashed the new rom, now everything go fine, but i'd like to try the newer version ^^
i've read some stuff but i'm a newbie, so i'm pretty confused, correct me if i'm wrong
with autorec i've downgraded the bootloader to JB version so i cant install the CM13
i should:
1)update to the latest twrp BUMPED
2)than go to recovery and flash the lastes bootstack
3)reboot to recovery
4)flash the CM13
can i update the 2.7 twrp to the latest one if the older isnt bumped? and how can i update it? i just have to flash it from the older twrp or should i use flashify or something like that?
let me know if the procedure is correct thanks for the help
Click to expand...
Click to collapse
blastagator twrp 2.8.7.3 reboot into recovery from recovery......then hybridbootstacks again reboot into recovery from recovery the nfals rom and gapps.
http://forum.xda-developers.com/lg-g2/development/boot-g2-hybrid-bootstacks-t3183219
@Turbine1991
is better update bootstack then recovery? or viceversa?
how can i backup my 2.7 twrp? (or if something going wrong with lastes bumped twrp and new bootstack can i flash back 12.1?)
@raptorddd
i read somewere i need at least twrp 2.8.4 for install new twrp recovery from the older recovery, is wrong? can i instal the 2.8.7.3 bumped from the normal 2.7?
niubboxp said:
@Turbine1991
is better update bootstack then recovery? or viceversa?
how can i backup my 2.7 twrp? (or if something going wrong with lastes bumped twrp and new bootstack can i flash back 12.1?)
@raptorddd
i read somewere i need at least twrp 2.8.4 for install new twrp recovery from the older recovery, is wrong? can i instal the 2.8.7.3 bumped from the normal 2.7?
Click to expand...
Click to collapse
First flash recovery once flashed it wont get deleted unless you change recovery or go back to stock. so blastagator latest recovery.. install blastagator then reboot into recovey from recovery. then flash bootstacks,again reboot to recovery from recovery and flash rom gapss. am not sure i dont think it matters wich recovery you use . as long a you have a custom recovery twrp or cwm you flash newst. and itll stay there unless you restore to stock then you loose recovery.
Sorry but i didnt understood, i already have the 2.7, when i go into recovery can i flash the blastagator or i have to flash something else before?
niubboxp said:
Sorry but i didnt understood, i already have the 2.7, when i go into recovery can i flash the blastagator or i have to flash something else before?
Click to expand...
Click to collapse
just flash balstagators twrp and you done. see on top part of screen theres the twrp version number. reboot into recovery so you will be on blastagators recovery.. and you done.. for bootstacks do the same reboot into recovery once you flashed boostacks once you in twrp and copy rom then flash
I can flash the blasstgator inside the older twrp or i need flashify or adb? Did u tryed?
niubboxp said:
I can flash the blasstgator inside the older twrp or i need flashify or adb? Did u tryed?
Click to expand...
Click to collapse
you can flash new twrp inside twrp. to take effect just dont reboot to system choose recovery and check that it says 2.8.7.3 i do it like that. but you say something about using older twrp that you cant install new, that i dont know. mine i used auto rec and gave me 2 earlier versions so i just flashed blastagator.. nothing can happen if you flash twrp inside twrp you just updating.. but reboo into recovery and make sure it says 2.8.7.3 on top and youre done.
raptorddd said:
you can flash new twrp inside twrp. to take effect just dont reboot to system choose recovery and check that it says 2.8.7.3 i do it like that. but you say something about using older twrp that you cant install new, that i dont know. mine i used auto rec and gave me 2 earlier versions so i just flashed blastagator.. nothing can happen if you flash twrp inside twrp you just updating.. but reboo into recovery and make sure it says 2.8.7.3 on top and youre done.
Click to expand...
Click to collapse
Thanks
i've flashed the new twrp and is all ok, i've also flashed the D802 5.0.2 Bootstack with KitKat (Bump) bootloader
but i've read somewhere with kk bootloader the key for enter in recovery is power+vol down than vol- +vol up, but i still enter in recovery with the old combo, how can i verify my bootstack version? when i flashed it everything gone fine
niubboxp said:
i've flashed the new twrp and is all ok, i've also flashed the D802 5.0.2 Bootstack with KitKat (Bump) bootloader
but i've read somewhere with kk bootloader the key for enter in recovery is power+vol down than vol- +vol up, but i still enter in recovery with the old combo, how can i verify my bootstack version? when i flashed it everything gone fine
Click to expand...
Click to collapse
i dont know, but as long as it said succesful in blue letters then you have it..
Well Marshmallow would boot if it did.
I have a i9000 and i would like to install twrp so i can install a 7.0 rom but i dont know how to install twrp can someone tell me how?
I would also like to know this as well. I've tried CWM through odn but it's a zip so wont flash. I've tried it in stock recovery but obviously get the signature fail msg.
TWRP comes with the kernel and hence the ROM.
It gets automatically installed if you're on older BML/MTD device..
In which case you should have rebooted after acceptign wipe..
Ahh right, so I flash a new kernel to it and that comes with the recovery built in.
Do I flash the kernel from odin or stock recovery. Got the stuff to unbrick the phone if that happens, just wanted to know the right way before flashing stock rom back and starting again.
MrGRiMv2 said:
Ahh right, so I flash a new kernel to it and that comes with the recovery built in.
Do I flash the kernel from odin or stock recovery. Got the stuff to unbrick the phone if that happens, just wanted to know the right way before flashing stock rom back and starting again.
Click to expand...
Click to collapse
The kernel is flashed by the ROM zip... I dont remember if it automatically reboots to recovery or not..
However it does create a file in cache that makes it boot to recovery.. Since the /system is not yet installed.
You should flash the ROM after it boots to new recovery.. then install the zip file again..
All this is described in https://github.com/xc-racer99/android_device_samsung_aries-common/blob/aosp-7.1/updater.sh
I got there in the end.
I flashed CF-Root-XX_OXA_JW4-v4.4-CWM3RFS.tar with odin, then installed cm-10.2.0-galaxysmtd.zip which also updated my older CWM. It had a spam, so I wiped/factory/dalvik etc from the updated CWM and then reinstalled cm-10.2.0-galaxysmtd.zip - now running the rom just fine.
Will be trying out some more over next few days now I have a nandroid of CM10.
Thanks for pointing me in the right direction.
I want to update my Moto G4 plus but to do so I will have to flash the stock recovery.So to do so can I flash the stock recovery image file within TWRP without using a PC
Jasnil said:
I want to update my Moto G4 plus but to do so I will have to flash the stock recovery.So to do so can I flash the stock recovery image file within TWRP without using a PC
Click to expand...
Click to collapse
Yes you can,
> TWRP > Install > (install img button at bottom) > select recovery img > flash as recovery.
____Mdd said:
Yes you can,
> TWRP > Install > (install img button at bottom) > select recovery img > flash as recovery.
Click to expand...
Click to collapse
Thank You.
Jasnil said:
Thank You.
Click to expand...
Click to collapse
isn't the recovery twrp though? if he flashes the image it will be twrp image no?
peladoro said:
isn't the recovery twrp though? if he flashes the image it will be twrp image no?
Click to expand...
Click to collapse
Though TWRP is the custom recovery, what is described above is flashing the stock recovery image in TWRP, which will overwrite TWRP recovery with the stock recovery. Upon rebooting to recovery, your recovery should now be the stock (Android) recovery. Both stock and TWRP recovery images can be flashed in TWRP without issue.
Of course, ideally you'll want to flash the recovery of the same patch level as your existing system. Furthermore, simply flashing the stock recovery over TWRP may not be enough to restore your device to stock and permit OTA updates - you'd need an unmodified system/kernel/stock logo as well.
echo92 said:
Though TWRP is the custom recovery, what is described above is flashing the stock recovery image in TWRP, which will overwrite TWRP recovery with the stock recovery. Upon rebooting to recovery, your recovery should now be the stock (Android) recovery. Both stock and TWRP recovery images can be flashed in TWRP without issue.
Of course, ideally you'll want to flash the recovery of the same patch level as your existing system. Furthermore, simply flashing the stock recovery over TWRP may not be enough to restore your device to stock and permit OTA updates - you'd need an unmodified system/kernel/stock logo as well.
Click to expand...
Click to collapse
I have an unmodified system/kernel/stock logo and I have even installed the stock recovery but I got an error while doing the OTA update.What is the problem??
Jasnil said:
I have an unmodified system/kernel/stock logo and I have even installed the stock recovery but I got an error while doing the OTA update.What is the problem??
Click to expand...
Click to collapse
What's the error and which stock firmware are you attempting to update/have on your device?
Are you certain your stock system is not modified? Even allowing TWRP to make modifications (allowing read write on the system) can cause an OTA update to fail. You may have to reflash the newest stock firmware in that case.
Hi guys,
At the moment we don't have many custom ROMs for 6T but we have quite a few custom kernels to play with.
Let's say we are on latest OSS, regards with Magisk and having TWRP. And with custom Kernel.
Correct way to go back to stock kernel and flash different custom kernel would be:
Boot to TWRP.
Flash Stock boot.img
Reboot to TWRP again
Flash TWRP zip
Reflash Magisk
Reboot to System.
Done.
Am I correct? Or do we have to reflash full OTA?
wangdak said:
Hi guys,
At the moment we don't have many custom ROMs for 6T but we have quite a few custom kernels to play with.
Let's say we are on latest OSS, regards with Magisk and having TWRP. And with custom Kernel.
Correct way to go back to stock kernel and flash different custom kernel would be:
Boot to TWRP.
Flash Stock boot.img
Reboot to TWRP again
Flash TWRP zip
Reflash Magisk
Reboot to System.
Done.
Am I correct? Or do we have to reflash full OTA?
Click to expand...
Click to collapse
Boot to TWRP.
Flash Stock boot.img
Flash twrp zip
Reboot to TWRP again
Reflash Magisk
Reboot to System.
Done.
indian84 said:
Boot to TWRP.
Flash Stock boot.img
Flash twrp zip
Reboot to TWRP again
Reflash Magisk
Reboot to System.
Done.
Click to expand...
Click to collapse
Is it okay to flash img files in TWRP? I was told that it is meant just for zip files. Fastboot for img files.
devilrulz4ever said:
Is it okay to flash img files in TWRP? I was told that it is meant just for zip files. Fastboot for img files.
Click to expand...
Click to collapse
As long as you flash correct image to correct slot, it should not be an issue..
devilrulz4ever said:
Is it okay to flash img files in TWRP? I was told that it is meant just for zip files. Fastboot for img files.
Click to expand...
Click to collapse
Since years
my preference is to use EXKM and flash through there. my process
need:
stock boot for whatever your running, in my case .11 boot.img
whatever kernel you want to flash
1. in exkm, flash the stock boot.img, don't reboot
2. then flash your kernel of choice, don't reboot
3. in magisk manager, flash magisk, and use direct patch, then reboot
once it reboots, your g2g