***WARNING***Recovery & Kernel in ICS***HARDBRICK-WARNING*** - Galaxy Tab 8.9 General

Dont use wipe, restore,or factory reset in STOCK ICS kernel with your Recovery
Thank you for moderator make this sticky..
You know that this not new for us.. This problem exist in many samsung devices with ICS, i got this brick on my GT-N7000 and my device had a motherboard replacement because of that, and it seem our beloved tab definitely got this problem too..
im no dev..just an ordinary Windows and Unix User,not Using English as my Native
but I will update and summarize the issues in this thread until we got the fix about it..
If you already in ICS you need to read the whole thread from this to figure out what the problem is..
Emmc bugs is exist.. And if you need to know what kind of EMMC you have and the possibilty of brick, use this app from chainfire
This is suspected kernel and recovery build from ICS source with this bug if you try to wipe on this:
-any boot.img from stock ICS
-any recovery.img from stock ICS
-CWM 6.0.1.2 which is build from ICS source..
-update binary which is build from ICS source..
Click to expand...
Click to collapse
Discussion about this:
CWM 6.0.1.2-Risk of Brick start by fred_be9300 please report your issue about CWM here..
Official CM9 thread by kallt_kaffe , discussion about this start from page 107
Click to expand...
Click to collapse
After you read, this is my advice:
Dont use any wipe operation or something similar with that such as:
command "Format" in Edify script if you plan make a flashable zip
Nandroid Restore in CWM (build from ics source)
Using wipe with stock recovery in stock ICS boot.img(kernel)
Wiping in safe CWM in stock ICS boot.img
using wipe and nandroid restore with CWM from ICS source without mmc erase patch
using update-binary from ICS build..(compiled from ICS source without mmc erase patch)
Click to expand...
Click to collapse
Thanks for entropy512 who figure out this and make all samsung users more aware about flashing in ICS
And chainfire who makes the tools..
This is not about what version of cwm are used.. But what kind of kernel that recovery operates..
If the recovery execute the command in honeycomb kernel maybe its more safe then ICS kernel..
This is quote from chainfire itself
Chainfire said:
..... CWM is just a userspace program, nothing special(!) - so if the problem can happen in CWM, it can happen in Android....
Click to expand...
Click to collapse
this is possible solution if you want to flash, wipe or restore in ICS
First method: use recovery.img and boot.img with MMC_CAP_ERASE disable.. For that you must familiar with compiling kernel from the source..
Second method:Flashing recovery.img and boot.img from honeycomb, after installation done reboot to recovery and flash the ROM you desire..Remember, your ROM package must have boot.img and recovery.img too..
Click to expand...
Click to collapse
PLEASE BE CAREFULL UNTIL SOMEONE WITH MORE KNOWLEDGE SOLVE THIS FOR US..REMEMBER ITS JUST A WARNING! WHATEVER YOU DID, YOU OWN THAT RISK!!!
Some people are able to safely wipe and flash using affected kernels forever. Some people can wipe a few times before problems occur, some people have problems on their first wipe.
The number of people that broken kernels affect may only be 5-10% - but so far, there is no way to definitively determine that you are safe without putting your device at risk.
Click to expand...
Click to collapse

nandroid restore....are you serious?

orlandoxpolice said:
nandroid restore....are you serious?
Click to expand...
Click to collapse
Yep. And some zip file update-binary executables too (the edify format() function in the 'updater-script's).
Specifically those update-binary commands that were statically linked with the ICS version of the ext4 library.
Both of these operations (edify format() and nandroid partition restore) make use of the make_ext4fs() function. That function apparently changed in ICS to add a call to the eMMC erase functionality in the vigilant pursuit of security. However, that functionality is what tickles the eMMC fw bug with the 'bad' kernels (i.e. those that don't have the erase functionality disabled).
Oh what a tangled web we weave ...

Correct me if I'm wrong, but if i understand the problem and various threads correctly, the easiest and safest way to keep flashing ics based custom roms without fear of the emmc bug would be to always flash a #honeycomb kernel# in recovery each time #before# flashing any ics rom, right?
So if we have a flashable zip of galaxy tab 8.9 honeycomb kernel or even a pre-ics cm9 kernel, and keep it in our sdcard to be available to flash everytime, then we could, go into recovery, flash the bugless kernel, reboot in to recovery again, then safely flash an ics rom(even wipe data) , since it'll run according to the bugless k ernel (this is how we got the ics roms on our tabs in the first place, right)!
I'm no developer, so I don't know how to make one, but is there an existing flashable zip of the stock honeycomb kernel or a honeycomb based cm9 kernel in the existing threads(maybe motely's should be fine?) Or can a developer craft one for us?
This should work, right? Or an I mistake somewhere?
Sent from my Galaxy Nexus using xda premium

Jnn1 said:
This should work, right?
Click to expand...
Click to collapse
Unfortunately, no.
The problem isn't what you are flashing onto the device or what you are flashing over the top of. It's what you are flashing WITH. This is done with the recovery image (usually Stock or CWM).
The recovery image has its own kernel which is distinct from 'the kernel' used by the regular system. The recovery image is an entirely self-contained mini-system that is able to manipulate the contents of the device. Other than being able to read and write and format the rest of the device it shares no operational functionality with the rest of the system (well, other than the bootloader, of course ).
So if you had HC installed and wanted to flash JB you could still get bricked if your recovery image was using a 'bad' kernel.
This is why there have been recommendations to use CWM 5.x.y.z or 6.0.0.8 or lower. Someone says that 6.0.1.0 seems to work but KK and a few others have strongly recommended the lower versions.
HTH.

orlandoxpolice said:
nandroid restore....are you serious?
Click to expand...
Click to collapse
Nandroid restore is ONLY unsafe in a recovery that (itself) is built with a buggy ICS kernel. Version 6.0.0.8 and before are safe, because based on earlier GB kernel.
Also, update-binary (a copy of which exists in EVERY flashable zip) is ONLY unsafe IF built against buggy ICS kernel module... and if the updater-script in the same zip does a format()
I don't know if we've already seen dangerous update-binary in the wild... Mostly people don't recompile that, but endlessly reuse older ones. Still, you might want to check that next time you want to flash a zip. Or keep a safe update-binary available to inject into any zip you want to flash...
Disclaimer: this is my interpretation based on careful reading of many posts

This thread needs to be stickied!
I was on 6.0.1.2 but now went back to 6.0.1.0 but it looks like I'll be heading for 6.0.0.8

pseudoheld said:
This thread needs to be stickied!
I was on 6.0.1.2 but now went back to 6.0.1.0 but it looks like I'll be heading for 6.0.0.8
Click to expand...
Click to collapse
6.0.1.2 is the only one I compiled that uses the ICS kernel and I've removed the links to it some days ago. I don't remember compiling a 6.0.1.0 version but I could be wrong.

kallt_kaffe said:
6.0.1.2 is the only one I compiled that uses the ICS kernel and I've removed the links to it some days ago. I don't remember compiling a 6.0.1.0 version but I could be wrong.
Click to expand...
Click to collapse
Haha yeah you did it was in the cm9 thread as a test version. I had it running quite some time without any problems but decided to be on the safe side with 6.0.0.8

It think there was a 6.0.0.8 and a 6.0.0.8_alternate (version in file name) Then someone said one of these was saying 6.0.1.0 in the UI. AFAIR.

fred_be9300 said:
It think there was a 6.0.0.8 and a 6.0.0.8_alternate (version in file name) Then someone said one of these was saying 6.0.1.0 in the UI. AFAIR.
Click to expand...
Click to collapse
Right. The 6.0.0.8 in CM9 thread is 6.0.1.0 according to CWM recovery menu header.

tracid said:
Right. The 6.0.0.8 in CM9 thread is 6.0.1.0 according to CWM recovery menu header.
Click to expand...
Click to collapse
Oh well, then they are safe. I just didn't notice the version number had changed. Only the 6.0.1.2 version has the dangerous kernel.

So again...
1. I have the same eMMC chip revision number known to be brickable as per Chainfire's app.
2. I have been using CWM 5.5.0.4 only and never anything else.
3. I have flashed CM9 and AOSP Jelly Bean without bricking my device using CWM 5.5.0.4
Is it safe to assume that flashing the latest CM9 through CWM 5.5.0.4 will not result in a lifeless brick of a P7300?
Again, I am only asking for an assumption, not a definitive answer. Will hold nobody responsible.

de3pkeeper said:
Is it safe to assume that flashing the latest CM9 through CWM 5.5.0.4 will not result in a lifeless brick of a P7300?
Click to expand...
Click to collapse
should be safe!
it seems like only in conjunction with the newer cwm the brick can happen.

boscorama said:
Unfortunately, no.
The problem isn't what you are flashing onto the device or what you are flashing over the top of. It's what you are flashing WITH. This is done with the recovery image (usually Stock or CWM).
The recovery image has its own kernel which is distinct from 'the kernel' used by the regular system. The recovery image is an entirely self-contained mini-system that is able to manipulate the contents of the device. Other than being able to read and write and format the rest of the device it shares no operational functionality with the rest of the system (well, other than the bootloader, of course ).
So if you had HC installed and wanted to flash JB you could still get bricked if your recovery image was using a 'bad' kernel.
This is why there have been recommendations to use CWM 5.x.y.z or 6.0.0.8 or lower. Someone says that 6.0.1.0 seems to work but KK and a few others have strongly recommended the lower versions.
HTH.
Click to expand...
Click to collapse
Ah ... I see ... the recovery has it's own kernel that is a separate beast from the Rom kernel ... thanks for taking the time to kindly explain! And I'll make sure to stay on cwm 6.0.0.8 or lower!
Sent from my GT-P7310 using xda premium

Jnn1 said:
Correct me if I'm wrong, but if i understand the problem and various threads correctly, the easiest and safest way to keep flashing ics based custom roms without fear of the emmc bug would be to always flash a #honeycomb kernel# in recovery each time #before# flashing any ics rom, right?
So if we have a flashable zip of galaxy tab 8.9 honeycomb kernel or even a pre-ics cm9 kernel, and keep it in our sdcard to be available to flash everytime, then we could, go into recovery, flash the bugless kernel, reboot in to recovery again, then safely flash an ics rom(even wipe data) , since it'll run according to the bugless k ernel (this is how we got the ics roms on our tabs in the first place, right)!
I'm no developer, so I don't know how to make one, but is there an existing flashable zip of the stock honeycomb kernel or a honeycomb based cm9 kernel in the existing threads(maybe motely's should be fine?) Or can a developer craft one for us?
This should work, right? Or an I mistake somewhere?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yes you can..
We dont know from what kernel the bugs appear maybe from boot.img or from recovery.img..
So the safest way is flash the safe boot.img with safe recovery.img in one flashable.zip and then reboot to recovery again and flash the ROM you desire..
It works and tested by me..

There are 2 types of CWM 6.0.0.8 to choose at KK's CM9 thread. One is original and the other is alternate. So which one should we install. I am comfuse. I am currently on CM10 review. Is KK's CM10 kernel safe to use? Thanks

nexus_g said:
There are 2 types of CWM 6.0.0.8 to choose at KK's CM9 thread. One is original and the other is alternate. So which one should we install. I am comfuse. I am currently on CM10 review. Is KK's CM10 kernel safe to use? Thanks
Click to expand...
Click to collapse
The alternate version is for those folks that experience display issues with the regular one. You can use either one.
I don't know what kernel is in the CM10 preview. But as long as you use a 'safe' recovery for your wipes and resets you should be just fine.

boscorama said:
The alternate version is for those folks that experience display issues with the regular one. You can use either one.
I don't know what kernel is in the CM10 preview. But as long as you use a 'safe' recovery for your wipes and resets you should be just fine.
Click to expand...
Click to collapse
No, mine bricked not in recovery. But on first booting of new rom (unofficial cm9) with 3.1.0 kernel.

notz76 said:
No, mine bricked not in recovery. But on first booting of new rom (unofficial cm9) with 3.1.0 kernel.
Click to expand...
Click to collapse
The important thing here is what you used to install CM9.

Related

[Q] Is it possible to replace the stock recovery?

I have a stupid question, since Chainfire can modify the kernal with 2e recovery, is it possible to use ClockWorkMod recovery to replace the stock recovery directly?
Koush said:
I will probably not create a permanent recovery method, because of the way Samsung handles boot and recovery partitions: they are both contained in the same kernel. So, by creating a recovery image, I would have to replace the boot kernel, and then other devs would not be able to do future kernel tweaks unless they included Clockwork in their kernel.
Furthermore, if someone is using a custom kernel, and I want to upgrade Clockwork, it would overwrite any custom changes they had in their kernel (overclocking, or whatever else). Fakeflash is perfectly acceptable and preferred for the Samsung Galaxy S.
I will of course provide new fakeflash zips for the Galaxy S as I fix bugs and add features.
Click to expand...
Click to collapse
That should suffice as to why there isnt a permanent recovery yet.
There is a way because Modaco has released a Rom with Clockworkrecovery as the default recovery.. ;D But i don`t no how it works ;D
That is possible, yes.
I can't remember the exact name, but I saw a German Guy on Twitter who replaced the stock recovery with ClockWorkMod on our Galaxy S.
Was it Aery...?
Daneshm90 said:
That should suffice as to why there isnt a permanent recovery yet.
Click to expand...
Click to collapse
It sounds reasonable, but still wanna after the official version released
Borky_16 said:
There is a way because Modaco has released a Rom with Clockworkrecovery as the default recovery.. ;D But i don`t no how it works ;D
Click to expand...
Click to collapse
Any link available? Thx.

Call me blind, but where is AOKP M6?!

I've seen a lot of posts of people saying they are using AOKP M6 (last ICS build from the team) on their Notes and it's awesome. Also, saw a couple of YouTube videos, I remember.
Okay... what the hell? I cannot find AOKP M6 for the Note here, on XDA. Only ROMs based on AOKP build 40 (before Milestone 6), with themes / tweaks included & stuff...
Maybe I'm blind, maybe I'm stupid... I want someone to give me a link to a thread where I can find AOKP M6 for the Note! Please
Formhault said:
I've seen a lot of posts of people saying they are using AOKP M6 (last ICS build from the team) on their Notes and it's awesome. Also, saw a couple of YouTube videos, I remember.
Okay... what the hell? I cannot find AOKP M6 for the Note here, on XDA. Only ROMs based on AOKP build 40 (before Milestone 6), with themes / tweaks included & stuff...
Maybe I'm blind, maybe I'm stupid... I want someone to give me a link to a thread where I can find AOKP M6 for the Note! Please
Click to expand...
Click to collapse
http://goo.im/devs/aokp/n7000
there u go..
sahilarora2003 said:
http://goo.im/devs/aokp/n7000
there u go..
Click to expand...
Click to collapse
It's funny, cause I went on the AOKP website and didn't see the Galaxy Note listed :/
What kernel does that ROM use?
Also, how am I supposed to flash it? I'm on RocketROM v7, which has LQ3 kernel. Can I flash Abyss 4.2 then wipe then flash AOKP?
Formhault said:
It's funny, cause I went on the AOKP website and didn't see the Galaxy Note listed :/
What kernel does that ROM use?
Also, how am I supposed to flash it? I'm on RocketROM v7, which has LQ3 kernel. Can I flash Abyss 4.2 then wipe then flash AOKP?
Click to expand...
Click to collapse
First Reboot into recovery.
Flash JBRoid Cleaner.
Flash Abyss 4.2
Reboot Recovery. U'll have Redpill Recovery.
Wipe Cache/Dalvik/Data.
Flash Milestone 6.
Reboot System.
I always use these steps..and worked flawlessly....
sahilarora2003 said:
First Reboot into recovery.
Flash JBRoid Cleaner.
Flash Abyss 4.2
Reboot Recovery. U'll have Redpill Recovery.
Wipe Cache/Dalvik/Data.
Flash Milestone 6.
Reboot System.
I always use these steps..and worked flawlessly....
Click to expand...
Click to collapse
Alright. You're the... I dunno... 5th person who confirms this method to me? I guess I'll make a TiBu backup and do as you said. I really want AOKP. Thanks
Let's just hope I don't get superbricked
Also, any suggestions on what kernel I should flash afterwards? Or should I stick to the one used in AOKP?
Formhault said:
Alright. You're the... I dunno... 5th person who confirms this method to me? I guess I'll make a TiBu backup and do as you said. I really want AOKP. Thanks
Let's just hope I don't get superbricked
Also, any suggestions on what kernel I should flash afterwards? Or should I stick to the one used in AOKP?
Click to expand...
Click to collapse
As many of the members facing reboot issues , I strongly recommend To flash CM9. Im using it with no problems whatsoever.
Don't worry...It is the safest method as Abyss 4.2 uses GB kernel which is safe to flash AOKP....
sahilarora2003 said:
As many of the members facing reboot issues , I strongly recommend To flash CM9. Im using it with no problems whatsoever.
Click to expand...
Click to collapse
I've been using AOKP on the SGS2 and the Nexus, and I grew to love it. Now I want to at least give it a shot on my Note. I like RocketROM, too, but... there are a few things about TouchWiz which turn me off.
If CM9 had ROM Control like AOKP, I'd go for it .
-----
How about Gapps? I believe I need to flash a specific package for 1280x800 resolution? Or... it's not really required, so I can flash any Gapps from the AOKP website...?
sahilarora2003 said:
Don't worry...It is the safest method as Abyss 4.2 uses GB kernel which is safe to flash AOKP....
Click to expand...
Click to collapse
So... only the KERNEL matters when wiping? Then I don't understand why people recommend flashing a whole GB ROM before wiping, even via Odin. It would take much more time than flashing just Abyss...
Formhault said:
I've been using AOKP on the SGS2 and the Nexus, and I grew to love it. Now I want to at least give it a shot on my Note. I like RocketROM, too, but... there are a few things about TouchWiz which turn me off.
If CM9 had ROM Control like AOKP, I'd go for it .
-----
How about Gapps? I believe I need to flash a specific package for 1280x800 resolution? Or... it's not really required, so I can flash any Gapps from the AOKP website...?
So... only the KERNEL matters when wiping? Then I don't understand why people RECCOMEND flashing a whole GB ROM before wiping.
Click to expand...
Click to collapse
My Bad.. U also have to flash Gapps after flashing Rom.. Here is the link... :- http://goo.im/gapps/gapps-ics-20120429-signed.zip
Flashing a GB rom is recommended because it is safe to flash over it as it is proved be safe of bricking your device...
sahilarora2003 said:
Flashing a GB rom is recommended because it is safe to flash over it as it is proved be safe of bricking your device...
Click to expand...
Click to collapse
So... wiping even after flashing the cleaning script + Abyss can be dangerous? :/
sahilarora2003 said:
My Bad.. U also have to flash Gapps after flashing Rom.. Here is the link... :- http://goo.im/gapps/gapps-ics-20120429-signed.zip
Click to expand...
Click to collapse
Hmm... that seems to be the same package I used on the Nexus. So it's not resolution-dependant.
-----
Was hoping XDA would automatically merge these two posts... Oh well...
Formhault said:
So... wiping even after flashing the cleaning script + Abyss can be dangerous? :/
Click to expand...
Click to collapse
No need to Wipe after JBRoid cleaning script as it is already included in the script... But as u asked it is not dangerous..
sahilarora2003 said:
No need to Wipe after JBRoid cleaning script as it is already included in the script... But as u asked it is not dangerous..
Click to expand...
Click to collapse
Yeah, that's what I was asking - whether it's dangerous or not, not if I need to wipe in between...
I'm safe. Hurray! Thanks . I needed 5+ confirmations in order to have the guts to try flashing again, haha.
Okay, so Titanium Backup was finally done backing up and verifying the backup.
-I rebooted into Recovery (a version that wasn't touch-driven - it was flashed automatically with RocketROM, I believe).
-I flashed the cleaning script.
-I flashed Abyss 4.2 kernel.
-I rebooted the recovery. It wasn't RedPill, but a touch-driven version of CWM. I guess the package I had wasn't the one with RedPill Custom Icon or whatever it's called .
-I wiped everything.
-I flashed AOKP and Gapps.
-I rebooted.
IT BOOTED UP ! YAY !
You can't imagine my heart beat rate, lol.
Formhault said:
Yeah, that's what I was asking - whether it's dangerous or not, not if I need to wipe in between...
I'm safe. Hurray! Thanks . I needed 5+ confirmations in order to have the guts to try flashing again, haha.
Okay, so Titanium Backup was finally done backing up and verifying the backup.
-I rebooted into Recovery (a version that wasn't touch-driven - it was flashed automatically with RocketROM, I believe).
-I flashed the cleaning script.
-I flashed Abyss 4.2 kernel.
-I rebooted the recovery. It wasn't RedPill, but a touch-driven version of CWM. I guess the package I had wasn't the one with RedPill Custom Icon or whatever it's called .
-I wiped everything.
-I flashed AOKP and Gapps.
-I rebooted.
IT BOOTED UP ! YAY !
You can't imagine my heart beat rate, lol.
Click to expand...
Click to collapse
Congrats. Welcome to the world of AOKP.. Cheers !!!
lol
shouldnt the flashing of the cleaning script be done from a GB kernel instead of an ICS kernel since it is used before the abyss kernel is installled ?
rraaka said:
shouldnt the flashing of the cleaning script be done from a GB kernel instead of an ICS kernel since it is used before the abyss kernel is installled ?
Click to expand...
Click to collapse
Nah...Cleaning script is to clean the effects that ur previous kernel had on your device...After flashing the script use abyss to have Red Pill Recovery..I use it all the tym before flashing any ROM....No Problems Yet....
thanks sahil, i was just wondering coz the script does some amount of wiping that too on an ics kernel !?
rraaka said:
thanks sahil, i was just wondering coz the script does some amount of wiping that too on an ics kernel !?
Click to expand...
Click to collapse
Ur Welcome!!! Don't do factory reset with ICS kernel as it can be dangerous..
sahilarora2003 said:
Nah...Cleaning script is to clean the effects that ur previous kernel had on your device...After flashing the script use abyss to have Red Pill Recovery..I use it all the tym before flashing any ROM....No Problems Yet....
Click to expand...
Click to collapse
I never got RedPill recovery after flashing Abyss! Wtf?
Sent from my GT-N7000
sahilarora2003 said:
Ur Welcome!!! Don't do factory reset with ICS kernel as it can be dangerous..
Click to expand...
Click to collapse
Not true entirely.
If you factory reset from a *safe* kernel, it cannot* brick your device if the erase_emmc_command is removed. If you're doing it from Official/Stock Samsung ICS Kernel, then yeah you'll brick your device.
You're right that a Clean Install is best.
Though you need to flash Abyss first.
Now its safe, use JBroid to delete the low-level stuff you've accumulated.
You need to Flash Abyss again, otherwise flash a *safe* custom kernel.
Then flash the ROM of your choosing, which will also flash a new kernel (cm9 based).
You can then flash the kernel of your choosing (eg/ ANiDROID, thor etc etc).
I know it gets redundant, but having a nice clean install the first time fixes 80% of bugs.
I'm learning that the HARD way
Kangal said:
Not true entirely.
If you factory reset from a *safe* kernel, it cannot* brick your device if the erase_emmc_command is removed. If you're doing it from Official/Stock Samsung ICS Kernel, then yeah you'll brick your device.
You're right that a Clean Install is best.
Though you need to flash Abyss first.
Now its safe, use JBroid to delete the low-level stuff you've accumulated.
You need to Flash Abyss again, otherwise flash a *safe* custom kernel.
Then flash the ROM of your choosing, which will also flash a new kernel (cm9 based).
You can then flash the kernel of your choosing (eg/ ANiDROID, thor etc etc).
I know it gets redundant, but having a nice clean install the first time fixes 80% of bugs.
I'm learning that the HARD way
Click to expand...
Click to collapse
None of the ICS kernels can 100% gurantee you that it is safe. (My personal Experience).

Odin stuck on Nand write

Hello,
I have the Samsung N7000, but it is stuck on Odin too.
My phone is not bricked or something like it, but I want Clockworkmod recovery 6.0.4.5 on it so I can flash Cyanogenmod 11 KitKat on it.
It is stuck on NAND WRITE too. I already have Clockworkmod recovery 6.0.2.8 on it, so I need to upgrade it.
Any suggestions??
Best regards, Joey
Moved to a new thread in Note Q&A
JoeyLohstroh said:
Hello,
I have the Samsung N7000, but it is stuck on Odin too.
My phone is not bricked or something like it, but I want Clockworkmod recovery 6.0.4.5 on it so I can flash Cyanogenmod 11 KitKat on it.
It is stuck on NAND WRITE too. I already have Clockworkmod recovery 6.0.2.8 on it, so I need to upgrade it.
Any suggestions??
Best regards, Joey
Click to expand...
Click to collapse
You have not mentioned the file you were trying to flash.. No mind readers here...
Anyways, flash raw kernel from the current recovery and reboot recovery.
nokiamodeln91 said:
You have not mentioned the file you were trying to flash.. No mind readers here...
Anyways, flash raw kernel from the current recovery and reboot recovery.
Click to expand...
Click to collapse
Sorry, I tried flashing Clockworkmod 6.0.4.5 tar.md5 file.
It ran till it said NAND WRITE START and than FAIL. The collor above turned red and instead of PASS it said FAIL!
So raw kernel should fix this?
Do you have a link maybe? I'll search for it on Google but I want to make sure I have the good file.
Edit*
I found what you told me, but it says that raw kernel is for Android 4.4?
http://forum.xda-developers.com/showthread.php?t=2397000
I have 4.1.2 so I'm not sure if this will brick my device or something like that.
My device is all working fine and it is not bricked or bootloop YET, and since it has that NAND WRITE fail I'm not sure if it will reinstall my stock rom.. if it may brick.
I will still say what I wrote above.. Flash raw r4..reboot recovery and flash kk rom.
nokiamodeln91 said:
I will still say what I wrote above.. Flash raw r4..reboot recovery and flash kk rom.
Click to expand...
Click to collapse
Allright, but I don't need to upgrade my cwm then? Because on several websites are telling me that I need at least Philz touch CWM 6.0.4.3 on it..
JoeyLohstroh said:
Allright, but I don't need to upgrade my cwm then? Because on several websites are telling me that I need at least Philz touch CWM 6.0.4.3 on it..
Click to expand...
Click to collapse
1. To flash a kitkat rom you will need a recent Cwm recovery.
2. Philz tw kernel are not updated to latest cwms.
3. If you try to flash philz_touch_xxx.zip, it won't work as you already saw.
So if you want to root the phone, use philz tw kernel that is associated with a rom build number like XXLTA.. Then you will get Cwm but not recent enough flash kk. That's why you flash raw r4.reboot into recovery takes to to recent Cwm. From there you can flash kk..
Just note that r4 is for 4.3 and will not boot a 4.1.2 so you will need to flash kk after r4.
nokiamodeln91 said:
1. To flash a kitkat rom you will need a recent Cwm recovery.
2. Philz tw kernel are not updated to latest cwms.
3. If you try to flash philz_touch_xxx.zip, it won't work as you already saw.
So if you want to root the phone, use philz tw kernel that is associated with a rom build number like XXLTA.. Then you will get Cwm but not recent enough flash kk. That's why you flash raw r4.reboot into recovery takes to to recent Cwm. From there you can flash kk..
Just note that r4 is for 4.3 and will not boot a 4.1.2 so you will need to flash kk after r4.
Click to expand...
Click to collapse
Aah like that. But I think that I need Raw kernel R5 than? Because KitKat is Android 4.4
And when I flash raw kernel, than I should be able of flashing newest Cwm?
JoeyLohstroh said:
Aah like that. But I think that I need Raw kernel R5 than? Because KitKat is Android 4.4
And when I flash raw kernel, than I should be able of flashing newest Cwm?
Click to expand...
Click to collapse
Hi,
Is not possible to flash recovery without kernel, on recent samsung phones recovery and kernel are tied. (Maybe you can change recovery editing the kernel image but that is out of subject and maybe your skills).
Follow the steps @nokiamodeln91 suggest you, there is no other way. Raw Kernel has a KK compatible recovery.
llawarta said:
Hi,
Is not possible to flash recovery without kernel, on recent samsung phones recovery and kernel are tied. (Maybe you can change recovery editing the kernel image but that is out of subject and maybe your skills).
Follow the steps @nokiamodeln91 suggest you, there is no other way. Raw Kernel has a KK compatible recovery.
Click to expand...
Click to collapse
Okay. But if KitKat doesn't work that well, do I need to downgrade my Kernel and Cwm recovery than?
And do you have a link to the stock kernel?
Then you go into recovery, wipe data, and flash anew rom using odin or use recovery to flash a custom rom.
nokiamodeln91 said:
Then you go into recovery, wipe data, and flash anew rom using odin or use recovery to flash a custom rom.
Click to expand...
Click to collapse
But do you know/have a link to the stock kernel?
Just in case..
JoeyLohstroh said:
But do you know/have a link to the stock kernel?
Just in case..
Click to expand...
Click to collapse
No, and what will you do with the stock kernel?
nokiamodeln91 said:
No, and what will you do with the stock kernel?
Click to expand...
Click to collapse
If cwm doesn't want to instal KitKat, because of some reason, or I decide to not install it, than I want to reboot 4.1.2 but because of the Raw Kernel that won't be possible.
JoeyLohstroh said:
If cwm doesn't want to instal KitKat, because of some reason, or I decide to not install it, than I want to reboot 4.1.2 but because of the Raw Kernel that won't be possible.
Click to expand...
Click to collapse
LOL that does not make any sense.. You will need to restore the backup or install a new rom. There is no need to separately install a stock kernel.. May be you need to read more how all this works.
nokiamodeln91 said:
LOL that does not make any sense.. You will need to restore the backup or install a new rom. There is no need to separately install a stock kernel.. May be you need to read more how all this works.
Click to expand...
Click to collapse
Well, I didn't know that you sometimes need another kernel before you can install cwm.
I have been installing custom roms en recoverys many times on LG's so that isn't the problem.
But the NAND WRITE and FAIL problem must be a kernel issue than?

[Q] Failed to install latest PhilZ

Hi there. Last night I tried to install the latest Philz recovery, but something somewhere goes wrong. I am with AryaMod v5, 4.1.2 Rooted, baseband XXLT3 and build XXLTC. As I can see it has [email protected] World Kernel as well.
So last night I downloaded Philz 6.45.6 and flash it through recovery, but then the phone didin'r start. it jush light the Samsung N700 sign, then it went black. I did Backup so I had to Restore it. So far so good /I have my phone back/. But when my Note did restore, it couldn't find android_secure, so I don't have all the app stored in my SD Card...big deal.
Now I downloaded Rom manager and I see Current Recovery: ClockWorkMod 6.0.4.8/Latest Recovery: CWM 6.0.4.3
So my question now is can I install latest Philz because I want to flash Arya V7 and there it says Latest PhilZ or I can flash now by folowwing yhe steps from 3 to the end? Do I need to flash latest recovery every time it is released?
PharrellVP said:
Hi there. Last night I tried to install the latest Philz recovery, but something somewhere goes wrong. I am with AryaMod v5, 4.1.2 Rooted, baseband XXLT3 and build XXLTC. As I can see it has [email protected] World Kernel as well.
So last night I downloaded Philz 6.45.6 and flash it through recovery, but then the phone didin'r start. it jush light the Samsung N700 sign, then it went black. I did Backup so I had to Restore it. So far so good /I have my phone back/. But when my Note did restore, it couldn't find android_secure, so I don't have all the app stored in my SD Card...big deal.
Now I downloaded Rom manager and I see Current Recovery: ClockWorkMod 6.0.4.8/Latest Recovery: CWM 6.0.4.3
So my question now is can I install latest Philz because I want to flash Arya V7 and there it says Latest PhilZ or I can flash now by folowwing yhe steps from 3 to the end? Do I need to flash latest recovery every time it is released?
Click to expand...
Click to collapse
do clean re-install aryamod v5 first because there is right kernel. Then you can restore your backup or install aryamod v7 (i have done like that)
Did I changed the Kernel? Because I was with Philz Kernel before installing the AryaMod V5. Then I saw i have [email protected] World Make II kernel as it is now shown in About the phone. And how can I do clean re-install?
PharrellVP said:
Hi there. Last night I tried to install the latest Philz recovery, but something somewhere goes wrong. I am with AryaMod v5, 4.1.2 Rooted, baseband XXLT3 and build XXLTC. As I can see it has [email protected] World Kernel as well.
So last night I downloaded Philz 6.45.6 and flash it through recovery, but then the phone didin'r start. it jush light the Samsung N700 sign, then it went black. I did Backup so I had to Restore it. So far so good /I have my phone back/. But when my Note did restore, it couldn't find android_secure, so I don't have all the app stored in my SD Card...big deal.
Now I downloaded Rom manager and I see Current Recovery: ClockWorkMod 6.0.4.8/Latest Recovery: CWM 6.0.4.3
So my question now is can I install latest Philz because I want to flash Arya V7 and there it says Latest PhilZ or I can flash now by folowwing yhe steps from 3 to the end? Do I need to flash latest recovery every time it is released?
Click to expand...
Click to collapse
Hello. Using PhilZ-cwm6-XXLTA-ATL-5.15.0-signed.zip. Would suffice. Philz latest doesn't include kernel anymore, only the recovery and from my personal experience, philz latest is more compatible with KK roms than TW roms.
Jackwu696 said:
Hello. Using PhilZ-cwm6-XXLTA-ATL-5.15.0-signed.zip. Would suffice. Philz latest doesn't include kernel anymore, only the recovery and from my personal experience, philz latest is more compatible with KK roms than TW roms.
Click to expand...
Click to collapse
What are you talking about?
nokiamodeln91 said:
What are you talking about?
Click to expand...
Click to collapse
I said, u don't need to use any latest philz and use the above mentioned philz will suffice to flash any TW based roms because I use it the whole time n no problem at all. I have downloaded all philz latest n they can't be flashed unless it's for KK kernel. So do u understand or is there Anything u might want to add?
Sent from my GT-N7000 using XDA Free mobile app
Jackwu696 said:
Anything u might want to add?
Click to expand...
Click to collapse
Maybe he wanted to add:
Your statement "Philz latest doesn't include kernel anymore, only the recovery and from my personal experience, philz latest is more compatible with KK roms than TW roms." is completely wrong.
ThaiDai said:
Maybe he wanted to add:
Your statement "Philz latest doesn't include kernel anymore, only the recovery and from my personal experience, philz latest is more compatible with KK roms than TW roms." is completely wrong.
Click to expand...
Click to collapse
Hello @ThaiDai
I said what I said because after downloading latest philz it can't be used to flash over TW kernels. But when in KK roms, it can be flashed. I have checked it before. Also somewhere in philz thread, I read that his recovery no longer includes kernels anymore. So please enlighten me where I'm wrong coz I'm open to correctionsn I'll really appreciate the knowledge to better help our fellow members. Just don't ask "what am I talking about?" And also I said "according to my personal experience" too.
Thanks for elaborating
Jackwu696 said:
Hello @ThaiDai
I said what I said because after downloading latest philz it can't be used to flash over TW kernels. But when in KK roms, it can be flashed. I have checked it before. Also somewhere in philz thread, I read that his recovery no longer includes kernels anymore. So please enlighten me where I'm wrong coz I'm open to correctionsn I'll really appreciate the knowledge to better help our fellow members. Just don't ask "what am I talking about?" And also I said "according to my personal experience" too.
Thanks for elaborating
Click to expand...
Click to collapse
Kernel for note and s2 has recovery built into them. Not the case with later phones like s3 s4... where recovery can be independent of the kernel. So you can have any kernel you want and any recovery you want.
Thus your statement that Philz kernel for N7000 doesn't include kernel is weird as it wont be of any use for normal users and " philz latest is more compatible with KK roms than TW roms" is again confusing as Phil made just 1 KK kernel with new recovery but that had issues with radio and all so..
"I said what I said because after downloading latest philz it can't be used to flash over TW kernels"
And this is? You can flash TW kernel using cwm/twrp as well.
Just don't ask "what am I talking about?"
I read your statement several times still couldn't understand, thats why ......
Hello @nokiamodeln91 . Glad to have you clarify this. Let me start from beginning then. I have dowloaded philz_touch_6.19.3-n7000, philz_touch_6.26.6-n7000 recoveries. When I want to flash a KK rom such as C-Rom over a TW rom such as this rom, aryamod's and such, I rebooted into recovery, flashed either of them n I got "installation error, installation aborted" (with the android avatar lying down dead). But when I move from KK to another KK such as C-rom to SKOP, these 2 files can be flashed without problem to change CWM recovery to philz. Seeing as the one who asked the question that led me to answer like that, I just suggested to him to use PhilZ-cwm6-XXLTA-ATL-5.15.0-signed instead if he want to flash a TW based rom (in his case, aryamod) and don't use the latest philz.. Sorry if any of my word confused you. Cheers. I have respect to you n other members who always help other needy members.
Sent from my GT-N7000 using XDA Free mobile app
Can't philz touch v5 to flash kitkat rom?
Sent from my SM-G7102 using Tapatalk
---------- Post added at 12:42 AM ---------- Previous post was at 12:37 AM ----------
Hi all master,,I have Note N7000.why I can't flash latest version Philz touch v6 on my device?what's wrong?need help...
Sent from my SM-G7102 using Tapatalk
There is some issue with the package.. You flash an older TW version. Then from that recovery flash raw r4.. Then from its recovery flash KK.
*Necropost* Sorry, But I have a question regarding this.
@nokiamodeln91 If I flash an older TW version then r4, do I need to wipe dalvik/cache before flashing r4 or can I go Older TW kernel > Reboot recovery > r4 kernel > reboot recovery > wipe system/data/cache/dalvik > flash KK ROM ?
aurator said:
*Necropost* Sorry, But I have a question regarding this.
@nokiamodeln91 If I flash an older TW version then r4, do I need to wipe dalvik/cache before flashing r4 or can I go Older TW kernel > Reboot recovery > r4 kernel > reboot recovery > wipe system/data/cache/dalvik > flash KK ROM ?
Click to expand...
Click to collapse
Yes your perception is correct.
Sent from my GT-N7000 using XDA Free mobile app

[Q] CM11 + CWM on GT-N7000

Hi Guys. short (and maybe dumb) question but i have to be sure before messing up the phone of my friend.
I would like to flash CM11 nightlies with clockworkmod on a Samsung Galaxy Note GT-N7000.
I have read several tutorials for flashing the GT-N7000 and i'm not sure which is the best way to do it.
It is neccesary to update or change the (current stock) kernel? Or is it possible to just copy the recovery and ROM to the SD card, boot into download mode, install from there?
Sorry i only have experience with flashing my HTC One X.
Thanks in advance,
Greetings
I am in the same possition. A friend of mine wants to help him install a custom rom to his n7000.
He has the stock samsung rom and the phone is LAGGY!!
I only have experience with flashing cm11 to my own galaxy s3 with philz touch recovery.
I am reading for 4 hours now and i am lost...
Should i only use TWRP?
but twrp has a version only for cm 10...(i havent found by searching any cm11 twrp version for n7000)
Should i use cm 10 then and all is ok??
Thanks a lot
I am reading things about installing kernel for recovery (philz touch)
After installing that, its just wipe data / cache and install Rom from Zip.
Im still bit confused about the rooting process -> Trough Zip or trough Odin.
I hope some1 can help me.
First you need root. Then you can flash a custom rom.
To root your device tgere a several ways possible. All written here in sticky threads.
Easy way via Philz Kernel. You will get custom recovery and root in in step. What Rom is currentky installed? Last five digits are enough.
User_99 said:
First you need root. Then you can flash a custom rom.
To root your device tgere a several ways possible. All written here in sticky threads.
Easy way via Philz Kernel. You will get custom recovery and root in in step. What Rom is currentky installed? Last five digits are enough.
Click to expand...
Click to collapse
Stock rom is currently installed. I uploaded a picture with the specs within an attachment
Search for XXLTA Kernel in PhilZ thread and flash this one. All written in PhilZ thread. After that take your new Rom an follow the instructions in the thread again. For CM 11 you need also Raw4 kernel first. Only after that flash the custom rom. But that's all written 100000 times here....
User_99 said:
Search for XXLTA Kernel in PhilZ thread and flash this one. All written in PhilZ thread. After that take your new Rom an follow the instructions in the thread again. For CM 11 you need also Raw4 kernel first. Only after that flash the custom rom. But that's all written 100000 times here....
Click to expand...
Click to collapse
Thank you for your reply.
I now have:
- PhilZ-cwm6-XXLTA-ATL-5.15.0
- raw_kernel_r4_j43
- cm-11-20141207-NIGHTLY-n7000
am i good to go?
hosseltietjes1990 said:
Thank you for your reply.
I now have:
- PhilZ-cwm6-XXLTA-ATL-5.15.0
- raw_kernel_r4_j43
- cm-11-20141207-NIGHTLY-n7000
am i good to go?
Click to expand...
Click to collapse
you also need gapps
eveles said:
you also need gapps (and maybe for later use one custom kernel )
Click to expand...
Click to collapse
Yes i know, to install play store and other applications. But for the flashing part, that is enough right? The kernel, ROM and Philz Recovery?
hosseltietjes1990 said:
Yes i know, to install play store and other applications. But for the flashing part, that is enough right? The kernel, ROM and Philz Recovery?
Click to expand...
Click to collapse
yes that is enough but gapps are usually installed right after the ROM so having it together with the other files is a good idea.
- transfer ROM, Kernels to internal or external SD.
- flash Philz JB kernel compatible with your device [ follow the instruction in Philz kernel thread on how to flash with no yellow triangle ] and reboot then verify that root is working (just try and give a file explorer root access or install an app like root checker from playstore)
- Once root is verified reboot to recovery (you should now be in philz touch recovery) I recommend you take a nandroid backup but the choice is yours
- Wait for the backup to complete or if you are skipping backup then
a) wipe data factory reset
b) wipe cache
c) format system by going into mounts and storage
d) wipe dalvik cache
- flash raw kernel and reboot recovery.
- Now in TWRP recovery (you can again choose to do steps a to d which is totally optional) find and flash the ROM you want
- flash gapps
- reboot
That should do it
and now just in case you don't like what you flashed you can always go back to your ROM if you took a nandroid backup as suggested in the installation steps
hope it helps
Restore instructions :
I don't know if CWM recovery takes he same path to backup as Philz recovery but if it does it pretty simple
- just reboot to recovery and do the steps a to d from the above installation steps and restore backup
But in case you are not able to find backup file in CWM then do this
- reboot to recovery
- flash Philz kernel (same one you flashed during installation )
-go to advanced and select "reboot recovery"
- now you should be in Philz recovery again
- do steps from a to d again and restore
Simple
REVENGE SOLVES EVERYTHING
tysonraylee said:
yes that is enough but gapps are usually installed right after the ROM so having it together with the other files is a good idea.
- transfer ROM, Kernels to internal or external SD.
- flash Philz JB kernel compatible with your device [ follow the instruction in Philz kernel thread on how to flash with no yellow triangle ] and reboot then verify that root is working (just try and give a file explorer root access or install an app like root checker from playstore)
- Once root is verified reboot to recovery (you should now be in philz touch recovery) I recommend you take a nandroid backup but the choice is yours
- Wait for the backup to complete or if you are skipping backup then
a) wipe data factory reset
b) wipe cache
c) format system by going into mounts and storage
d) wipe dalvik cache
- flash raw kernel and reboot recovery.
- Now in TWRP recovery (you can again choose to do steps a to d which is totally optional) find and flash the ROM you want
- flash gapps
- reboot
That should do it
and now just in case you don't like what you flashed you can always go back to your ROM if you took a nandroid backup as suggested in the installation steps
hope it helps
REVENGE SOLVES EVERYTHING
Click to expand...
Click to collapse
Very clear! Thank you very much. Sorry for being a noob with this but it i think you cant be too sure when you are flashing kernels. Got my Nexus S bricked once while i was flashing a custom kernel.
And i dont have any experience with flashing samsung phone. Only HTC.
Thanks again and have a good day!
hosseltietjes1990 said:
Very clear! Thank you very much. Sorry for being a noob with this but it i think you cant be too sure when you are flashing kernels. Got my Nexus S bricked once while i was flashing a custom kernel.
And i dont have any experience with flashing samsung phone. Only HTC.
Thanks again and have a good day!
Click to expand...
Click to collapse
I was in the same boat 2 years ago so i understand the situation I am glad i could help and if you are coming from nexus I am pretty sure you won't have any issues at all. Just one or two flashes and you will know everything
and who knows I might need your help one day as I am thinking of buying the N6 myself
oh and btw let me tell you that recovery and kernel are in the same partition for N7000 so you can't have "this kernel and that recovery" here as you would in other devices. Thus if you need a certain recovery then you have to flash a certain kernel and if you need a certain kernel then it will install the recovery that comes with it overwriting the previous one. Also even if you flash just recovery somehow, the device will restore the one with the kernel upon reboot
So yeah
REVENGE SOLVES EVERYTHING
tysonraylee said:
I was in the same boat 2 years ago so i understand the situation I am glad i could help and if you are coming from nexus I am pretty sure you won't have any issues at all. Just one or two flashes and you will know everything
and who knows I might need your help one day as I am thinking of buying the N6 myself
REVENGE SOLVES EVERYTHING
Click to expand...
Click to collapse
I just recently flashed my HTC one X And the One X of a friend of mine. No need there to flash the kernel on that phone, only recovery trough adb and flash rom. So i really dont wanna mess with kernels
I you would like to ask something, feel free to ask! Thanks for the support
hosseltietjes1990 said:
Thank you for your reply.
I now have:
- PhilZ-cwm6-XXLTA-ATL-5.15.0
- raw_kernel_r4_j43
- cm-11-20141207-NIGHTLY-n7000
am i good to go?
Click to expand...
Click to collapse
In the guide below
http://forum.xda-developers.com/showthread.php?p=53346482
it clearly says ''-Download Raw Kernel r5 and copy it to either your internal or external memory''
You have downloaded raw_kernel_r4_j43
Why is that?
Am i missing something?
My friend's n7000 runs on 4.1.2 as well and my goal is to install cm11 as well.
Saying that, which is the appropriate raw_kernel???
The kernel code name should match the currently installed TW rom (4.1.2) or should it match the CM11 rom you intend to flash (4.4.4)????
to answer my own question : In XxPixX's quide of course it says r5 so 4.4.4 )
Anyway the kernel that you have downloaded is neither r5 nor r1 (i beleive that r1 is for 4.1)
Thanks, i hope someone with more experiense would clarify that!!
eveles said:
In the guide below
http://forum.xda-developers.com/showthread.php?p=53346482
it clearly says ''-Download Raw Kernel r5 and copy it to either your internal or external memory''
You have downloaded raw_kernel_r4_j43
Why is that?
Am i missing something?
My friend's n7000 runs on 4.1.2 as well and my goal is to install cm11 as well.
Saying that, which is the appropriate raw_kernel???
thanks!!!!!!
Click to expand...
Click to collapse
yes you have to download raw kernel because CM 11 or Android Kitkat requires SE Linux compatible recovery and raw kernel is the one that has this compatibility.
If you skip raw kernel then installation will fail giving you "status 7 installation aborted" error.
Downloading the latest Raw kernel for KitKat should do it just read in the kernel thread and download the latest one for kk.
the kernel code name should match the ROM (4.1.2) the one you currently have. Download the philz JB kernel for your JB ROM(follow the steps given in philz kernel thread)
There is no requirement as such for 4.4.4 ROM
REVENGE SOLVES EVERYTHING
tysonraylee said:
yes you have to download raw kernel because CM 11 or Android Kitkat requires SE Linux compatible recovery and raw kernel is the one that has this compatibility.
If you skip raw kernel then installation will fail giving you "status 7 installation aborted" error.
Downloading the latest Raw kernel for KitKat should do it just read in the kernel thread and download the latest one for kk.
REVENGE SOLVES EVERYTHING
Click to expand...
Click to collapse
Raw Kernel 5 (download link: http://ge.tt/5fBuPYn1/v/1?c ) is the good one right. Think that should do the trick. I see some people just flashing the philz touch cmw, and then the Rom, without the kernel. Several video's on youtube confirming that. So It's quite confusing 20 people explaining how to install CM11 and root on Samsung Note GT-N7000
hosseltietjes1990 said:
Raw Kernel 5 (download link: http://ge.tt/5fBuPYn1/v/1?c ) is the good one right. Think that should do the trick. I see some people just flashing the philz touch cmw, and then the Rom, without the kernel. Several video's on youtube confirming that. So It's quite confusing 20 people explaining how to install CM11 and root on Samsung Note GT-N7000
Click to expand...
Click to collapse
The download link you have provided links to r6 not r5
r6 says that is only for omniron 4.4
We were talking about cm11.
eveles said:
The download link you have provided links to r6 not r5
Click to expand...
Click to collapse
Oh i'm sorry haha. R6 should work right?
edit: sorry i did not read properly. r5 it is then
hosseltietjes1990 said:
Oh i'm sorry haha. R6 should work right?
Click to expand...
Click to collapse
No.
r5 should work.
Dude you are more confused than i am!!
hosseltietjes1990 said:
Raw Kernel 5 (download link: http://ge.tt/5fBuPYn1/v/1?c ) is the good one right. Think that should do the trick. I see some people just flashing the philz touch cmw, and then the Rom, without the kernel. Several video's on youtube confirming that. So It's quite confusing 20 people explaining how to install CM11 and root on Samsung Note GT-N7000
Click to expand...
Click to collapse
yes that should do it, download the k44 one
I haven't seen any videos about that but it is possible to do so but that's just using the recovery temporarily to flash a certain ROM but in the end that recovery is replaced by the ROMs kernel recovery its the same thing we are doing by using raw kernel here in these installation steps but its true that it gets a little confusing
I have updated my previous reply. Please refresh the page to see the explanation
eveles said:
The download link you have provided links to r6 not r5
Click to expand...
Click to collapse
R6 is the latest version. Please download the R6-k44.zip
REVENGE SOLVES EVERYTHING

Categories

Resources