4.2.2 recovery help - Nexus 7 Q&A, Help & Troubleshooting

Hi! Im a noob with a couple of questions hope anyone can help me...
I was recently at 4.2.1 on my nexus 7 had twrp installed, and accidentally updated to stock 4.2.2 my cstom recovery wash flashed by a stock one and forced me to install another via fastboot, but this time i installed cwm then i decided to go back to twrp coZ i dont personally like cwm,. So here is my problem i used rom toolbox to reboot into recovery and it said that i have a cwm installed but when i rebooted i was on twrp, its confusing did i installed both? And made me decide to use rom manager it said that i have twrp and cwm already installed how can i uninstall cmw...
Hope u could help me.. Anyone?

ROM manager plays a clever trick where it temporarily replaces the recovery, even though it is not flashed into the recovery partition.
If you start the recovery from the bootloader, you'll see TWRP; and if you boot into recovery from ROM manager, you will (eventually) see the CWM recovery (you may see some graphics produced by TWRP first, though).
If you have a way (separate from ROM Manager) to boot from the OS into the recovery, you will get TWRP.

bftb0 said:
ROM manager plays a clever trick where it temporarily replaces the recovery, even though it is not flashed into the recovery partition.
If you start the recovery from the bootloader, you'll see TWRP; and if you boot into recovery from ROM manager, you will (eventually) see the CWM recovery (you may see some graphics produced by TWRP first, though).
If you have a way (separate from ROM Manager) to boot from the OS into the recovery, you will get TWRP.
Click to expand...
Click to collapse
Hi thnx for the help, actualy i was able to boot into twrp already and i belive i flashed it completely, my only concern is did i overwrite the cwm in my rec partition? Or it is still there?
Sent from my Nexus 7 using xda app-developers app

There can be only one bootable image in the recovery partition at a time.
If you boot from the bootloader into recovery, and you see TWRP... then that is what is flashed there.
If you want to see what I am talking about, go into ROM manager and select the menu item that causes a boot into recovery. What you will see (after a little bit) is the CWM U/I.
What is going on is that ROM manager boots whatever recovery is actually flashed in the recovery partition, and then immediately replaces /sbin/recovery with it's own version (CWM) and then kills & restarts that same program.
So - what you *see* is the CWM version of /shin/recovery - running on top of the kernel & ramdisk were provisioned by the whatever recovery was actually flashed to the recovery partition.
If you want to actually flash CWM to the recovery partition, ROM Manager has a menu item for that. I'm not sure what the exact wording is.
If you are confused by this, just read the first two sentences in this post.

Related

[Q] Recovery boot fail after updating to 4.1.2

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...

[Q] Recovering... recovery, after Lollipop official image installation

Hello everyone!
I used to have TWRP 2.8 and a custom rom installed on my Nexus 4. After the official Lollipop image came out, I installed it and everything works fine, except the fact that there seems to be no recovery at all. When I try to enter recovery and the phone reboots, I get the green-robot-error image. While installing the Lollipop image, I read the messages and it said that boot.sig and recovery.sig were not found. I tried installing TWRP over again, but nothing changed. Everything else works fine on the phone, fastboot, Lollipop, I even rooted with no problems. How do I properly reinstall TWRP on my device, without getting the green robot of death icon?
I have same problem, the OS reinstall default recovery every reboot, if you install TWRP via fastboot mode and directly reboot into TWRP recovery mode is there and it works, but after reboot to systen it's gone.
How have rooted Lollipop? SuperSU I install from TWRP and tells me that binary super are missing.
Here is the solution, but I dont have su
http://forum.xda-developers.com/nexus-4/help/guide-ultimate-nexus-4-root-guide-t2018179
common issue at this point. It appears recovery isnt sticking for some reason.
kokotron said:
Hello everyone!
I used to have TWRP 2.8 and a custom rom installed on my Nexus 4. After the official Lollipop image came out, I installed it and everything works fine, except the fact that there seems to be no recovery at all. When I try to enter recovery and the phone reboots, I get the green-robot-error image. While installing the Lollipop image, I read the messages and it said that boot.sig and recovery.sig were not found. I tried installing TWRP over again, but nothing changed. Everything else works fine on the phone, fastboot, Lollipop, I even rooted with no problems. How do I properly reinstall TWRP on my device, without getting the green robot of death icon?
Click to expand...
Click to collapse
I advise you to read more in future to keep yourself away from such troubles.
Installing a Factory Image sends your device back to completely stock, this includes all the partitions, i.e System, Data, Cache, Recovery. Just think of it resembling the newly bought device. The Red icon means you now have the stock recovery installed. You now need to Install the custom recovery (TWRP) again.
Download TWRP Recovery Image: Click here
Power Off Nexus 4
Boot into Bootloader/Fastboot mode. Press VolDown + Power buttons altogether to reboot into bootloader mode.
Connect the device to the PC via USB data cable
Open a new CMD window
"cd" the command line window to the location of the downloaded image and enter the following command thereafter:
Code:
fastboot flash recovery openrecovery-twrp-2.8.1.0-mako.img
And you'll be able to boot into recovery mode.
sidVici0us said:
I have same problem, the OS reinstall default recovery every reboot, if you install TWRP via fastboot mode and directly reboot into TWRP recovery mode is there and it works, but after reboot to systen it's gone.
How have rooted Lollipop? SuperSU I install from TWRP and tells me that binary super are missing.
Click to expand...
Click to collapse
For rooting, I used the file and the guide in the following thread, it doesn't require recovery, just fastboot mode.
http://forum.xda-developers.com/nexus-4/orig-development/n4-cf-auto-root-t2025274
kokotron said:
For rooting, I used the file and the guide in the following thread, it doesn't require recovery, just fastboot mode.
http://forum.xda-developers.com/nexus-4/orig-development/n4-cf-auto-root-t2025274
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-4/help/guide-ultimate-nexus-4-root-guide-t2018179
A solution for auto swpan defualt recovery, the file is there only rename it
DJBhardwaj said:
I advise you to read more in future to keep yourself away from such troubles.
Installing a Factory Image sends your device back to completely stock, this includes all the partitions, i.e System, Data, Cache, Recovery. Just think of it resembling the newly bought device. The Red icon means you now have the stock recovery installed. You now need to Install the custom recovery (TWRP) again.
Download TWRP Recovery Image: Click here
Power Off Nexus 4
Boot into Bootloader/Fastboot mode. Press VolDown + Power buttons altogether to reboot into bootloader mode.
Connect the device to the PC via USB data cable
Open a new CMD window
"cd" the command line window to the location of the downloaded image and enter the following command thereafter:
Code:
fastboot flash recovery openrecovery-twrp-2.8.1.0-mako.img
And you'll be able to boot into recovery mode.
Click to expand...
Click to collapse
As I mentioned in my post, I did try to reinstall TWRP. I did it exactly the way you are describing. Still no recovery. The robot icon I'm describing is a common image when something's wrong on an android device and has nothing to do with stock recovery. Thanks a lot for taking the time to post all these info, though!
sidVici0us said:
I have same problem, the OS reinstall default recovery every reboot, if you install TWRP via fastboot mode and directly reboot into TWRP recovery mode is there and it works, but after reboot to systen it's gone.
How have rooted Lollipop? SuperSU I install from TWRP and tells me that binary super are missing.
Here is the solution, but I dont have su
http://forum.xda-developers.com/nexus-4/help/guide-ultimate-nexus-4-root-guide-t2018179
Click to expand...
Click to collapse
Just Install a Custom Kernel with modified ramdisk. Install Hellscore kernel and then install SuperSU. You will be able to experience Root.
I think unleashed kernel has also been updated with the same, but I can only confirm it with Hellscore.
It's the new bootloader. Flash an older bootloader version, reboot the bootloader, then flash TWRP again and it will stick.
kokotron said:
As I mentioned in my post, I did try to reinstall TWRP. I did it exactly the way you are describing. Still no recovery. The robot icon I'm describing is a common image when something's wrong on an android device and has nothing to do with stock recovery. Thanks a lot for taking the time to post all these info, though!
Click to expand...
Click to collapse
It is weird. I am pretty much sure you're either missing something or using a corrupted img file. Confirm that the file has been downloaded completely by verifying the md5 checksum and I am sure it will mismatch
hp420 said:
It's the new bootloader. Flash an older bootloader version, reboot the bootloader, then flash TWRP again and it will stick.
Click to expand...
Click to collapse
In that case, could it mean that TWRP could probably release an update based on the new bootloader that would solve the issue?
kokotron said:
In that case, could it mean that TWRP could probably release an update based on the new bootloader that would solve the issue?
Click to expand...
Click to collapse
It is not the bootloader, I already achieved that TWRP left there and not deleted, these are the steps to Reproduce.
Download the latest TWRP 2.8.1
restart in bootloader mode
fastboot flash recovery twrp-recover.zip
After the fast boot menu select to boot into recovery and went to boot the TWRP.
Go to Mount ands mount system partition
The go to TWRP file manager and rename the file /system/etc/install-recovery.sh /system/etc/install-recovery.bak
And ready the recovery.
To root I used http://forum.xda-developers.com/nexus-4/orig-development/n4-cf-auto-root-t2025274
Work fine in L.
sidVici0us said:
It is not the bootloader, I already achieved that TWRP left there and not deleted, these are the steps to Reproduce.
Download the latest TWRP 2.8.1
restart in bootloader mode
fastboot flash recovery twrp-recover.zip
After the fast boot menu select to boot into recovery and went to boot the TWRP.
Go to Mount ands mount system partition
The go to TWRP file manager and rename the file /system/etc/install-recovery.sh /system/etc/install-recovery.bak
And ready the recovery.
To root I used http://forum.xda-developers.com/nexus-4/orig-development/n4-cf-auto-root-t2025274
Work fine in L.
Click to expand...
Click to collapse
It is the bootloader. I had the exact same thing happen to me. The only thing I did was flash the last bootloader released before lollipop (30d, i think?) and reflashed twrp, and it stuck. I tried several times reflashing before I rolled back to the legacy bootloader and every time I rebooted the stock recovery was reinstalled. Now you tell me, if the only thing I changed was the bootloader, then reflashed twrp and it worked, how is it not the new bootloader?
sidVici0us said:
It is not the bootloader, I already achieved that TWRP left there and not deleted, these are the steps to Reproduce.
Download the latest TWRP 2.8.1
restart in bootloader mode
fastboot flash recovery twrp-recover.zip
After the fast boot menu select to boot into recovery and went to boot the TWRP.
Go to Mount ands mount system partition
The go to TWRP file manager and rename the file /system/etc/install-recovery.sh /system/etc/install-recovery.bak
And ready the recovery.
To root I used http://forum.xda-developers.com/nexus-4/orig-development/n4-cf-auto-root-t2025274
Work fine in L.
Click to expand...
Click to collapse
Ok thank you, this seems to have worked. When I booted back into Android though root didn't work any more. I re-rooted using your link (which was what I used the first time as well), and I guess I'll know how it goes the next time I reboot the phone.
hp420 said:
It is the bootloader. I had the exact same thing happen to me. The only thing I did was flash the last bootloader released before lollipop (30d, i think?) and reflashed twrp, and it stuck. I tried several times reflashing before I rolled back to the legacy bootloader and every time I rebooted the stock recovery was reinstalled. Now you tell me, if the only thing I changed was the bootloader, then reflashed twrp and it worked, how is it not the new bootloader?
Click to expand...
Click to collapse
Not the boot loader because I have the new bootloader that came with L and TWRP working perfectly, so both can coexist.
The problem comes from within the rom as I said, the file is in /system/etc/install-recovery.sh is responsible to clear the custom recovery and return to default android recovery. The solution is to remove (or rename) that file, what I saw is that the TWRP and SuperSU (both try to) can not rename it, and the solution was to rename it manually from the file manager included in the TWRP (mounting /system as explained before).
The same problem to can not overwrite files (should be modified in any command in library ) prevents install from a flashable zip SuperSU, so the solution http://forum.xda-developers.com/nexu...- root-t2025274 initiating its own operating system booting own image solves the problem that can not be overwritten (or modified) files from the TWRP (at least until a specified version for L see the light).
Probably whoever the new bootloader prevents TWRP modify files in /system, but bootloader not erases the custom recovery. Surely people of TWRP is working to fix this issue (or sleeping sometimes you have to sleep) but the problem can be solved by keeping the new booloader.
Conclucion, I have stock L Last bootloader, root and TWRP everything working perfectly and hellsCore Kernel
sidVici0us said:
Download the latest TWRP 2.8.1
restart in bootloader mode
fastboot flash recovery twrp-recover.zip
After the fast boot menu select to boot into recovery and went to boot the TWRP.
Go to Mount ands mount system partition
The go to TWRP file manager and rename the file /system/etc/install-recovery.sh /system/etc/install-recovery.bak
And ready the recovery.
To root I used http://forum.xda-developers.com/nexus-4/orig-development/n4-cf-auto-root-t2025274
Work fine in L.
Click to expand...
Click to collapse
I did exactly what you just wrote and It worked partially. My TWRP now sticks but I am not able to install supersu. I did install supersu and it was successful but the issue is that when i use root checker it still shows my phone is not rooted and also when i open supersu app it says "supersu binaries are not installed....". Any suggestion?
you installed via the SuperSU binaries from flashable zip in TWRP or use the method http://forum.xda-developers.com/nexus-4/orig-development/n4-cf-auto-root-t2025274 ?
With the CF-auto-root you should have no problems, I did so and I read that many people do so, use this method to root.
On the other hand, I was thinking that having a recovery that can not flash zip is not something useful
---------- Post added at 03:16 PM ---------- Previous post was at 02:52 PM ----------
samvid1992 said:
I did exactly what you just wrote and It worked partially. My TWRP now sticks but I am not able to install supersu. I did install supersu and it was successful but the issue is that when i use root checker it still shows my phone is not rooted and also when i open supersu app it says "supersu binaries are not installed....". Any suggestion?
Click to expand...
Click to collapse
You can not use the superSU flasheable zip, the recovery is not working to modify /system partition, use the other method.
samvid1992 said:
I did exactly what you just wrote and It worked partially. My TWRP now sticks but I am not able to install supersu. I did install supersu and it was successful but the issue is that when i use root checker it still shows my phone is not rooted and also when i open supersu app it says "supersu binaries are not installed....". Any suggestion?
Click to expand...
Click to collapse
CF autoroot works perfectly!! http://www.xda-developers.com/android/chainfire-releases-cf-auto-roots-for-nexus-line/

"Android is upgrading" after installing latest CWM -- erases recovery afterwords

"Android is upgrading" after installing latest CWM -- erases recovery afterwords
Installed latest CWM for Nexus 10 (6.0.4.7) on Android 5.1.1 Stock ( I did take the OTA available today, thinking this might be the problem )
Once I install it I can power down the tablet & access CWM, once. After accessing CWM when I go back into Android it'll give me the "Android is upgrading" and will optimize apps ##/###. Once this is finished I power off the tablet and try to access the CWM again, but I get "No command" like stock recovery is installed.
After I was able to replicate this a couple times I decided to do a factory reset so I could try again. But still getting the same results.
EDIT: Seems like even without accessing CWM after installing I get the Android is Starting: Optimizing ##/### - Going to try TWRP instead as peachpuff says.
How about you try twrp? https://dl.twrp.me/manta/
Thanks peachpuff.
I tried CWM and TWRP now, both after being installed will prompt the "Android is starting: Optimizing apps" regardless of being accessed. And after this is complete the recovery is wiped back to stock.
Odd, other than reflashing the stock images and then flashing another recovery not sure what i can suggest.
Stock Android got a script to flash their recovery back.
You should flash some custom rom or even marshmalllow.
Just boot into the bootloader
Code:
fastboot flash recovery PathToTheRecovery.img
Then boot into the recovery(twrp is better than cwn imo) then flash whatever you want...
also the files at
Code:
/sdcard/Android/*
Code:
/data/.layout_version
may interfere
Khaon said:
Stock Android got a script to flash their recovery back.
You should flash some custom rom or even marshmalllow.
Just boot into the bootloader
Code:
fastboot flash recovery PathToTheRecovery.img
Then boot into the recovery(twrp is better than cwn imo) then flash whatever you want...
also the files at
Code:
/sdcard/Android/*
Code:
/data/.layout_version
may interfere
Click to expand...
Click to collapse
Strangely enough even though I cant access recovery it still jumped into twrp when I did a factory reset. But that sounds like an idea. Thanks.

Lack of recovery

Hey guys, I'm a longtime XDA browser but hardly ever post. I have the MXPE rooted with the newest TWRP build and has been running great since I got it. last night flashed the Deodexed 6.0 build from AICPs 5.1.1. I had some issues with the SD card being mounted as internal storage and erasing something so I tried to flash back to stock as my nandroids weren't seen as usable.
Long story short when I flashed back to stock, the recovery would never take. I've flashed the stock recovery and twrp to no avail. For some reason it wont actually stick. Everything else is back to stock but that. When I used the win toolkit and tried to flash twrp again it said something about the folder locations so I'm wondering if I messed something in the partitions.
Question is, have you guys ran into this issue or have any insight on where to go from here? I've looked around but I couldn't find a post that the same as this issue. As a side note, I can get into the bootloader just fine.
I appreciate any info that someone can provide.
Flash twrp. Reboot back to recovery from recovery. Reboot system.
Hopefully it's that easy. Stock os flashes stock recovery on boot. Rebooting recovery from recovery prevents that from happening.
From TWRP:
"Note many devices will replace your custom recovery automatically during first boot.... Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."
mxpe 6.0
Thanks for the info ffejy462. What happens when I try to flash TWRP and it doesnt stick? I know for a fact that I can boot into it temporarily with fastboot boot and the recovery file. Should I just flash it from there?
THEFILLTER said:
Thanks for the info ffejy462. What happens when I try to flash TWRP and it doesnt stick? I know for a fact that I can boot into it temporarily with fastboot boot and the recovery file. Should I just flash it from there?
Click to expand...
Click to collapse
I'm sorry I didn't see this sooner. Flash recovery with fastboot. Boot into recovery. From reboot menu in recovery, select reboot recovery. Twrp will patch so recovery isn't lost again.
mxpe 6.0
That did it. thanks alot ffejy462!

How do i install teamwin ?

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.

Categories

Resources