Database Develop

Possible to flash kernel directly from CWM?

Hi there folks,
I want to flash kernels on the go (Semaphore "regular" and Big Mem version) and using the least applications possible (i.e. without SGS Kernel Flasher, if possible).
So I'm looking for a way to flash them via the CWM .zip installation.
I know (think) that with the proper installation script inside the .zip, it should work OK. In fact, I've found this solution that achieves this, but it doesn't work in our phone (I've tried and the old kernels stays around), so probably I'm looking for something similar to that.
Would you let me know what you think?
PS: I've also found this one too, but obviously the kernel in my case is .tar so it won't directly work with CWM...
Thanks

Just out of curiosity, what's wrong with Kernel Flasher?

Dan_Aykroyd said:
Hi there folks,
I want to flash kernels on the go (Semaphore "regular" and Big Mem version) and using the least applications possible (i.e. without SGS Kernel Flasher, if possible).
So I'm looking for a way to flash them via the CWM .zip installation.
I know (think) that with the proper installation script inside the .zip, it should work OK. In fact, I've found this solution that achieves this, but it doesn't work in our phone (I've tried and the old kernels stays around), so probably I'm looking for something similar to that.
Would you let me know what you think?
PS: I've also found this one too, but obviously the kernel in my case is .tar so it won't directly work with CWM...
Thanks
Click to expand...
Click to collapse
I would love to help if you have posted this in the right thread.. this is the development thread!

myrddral said:
Just out of curiosity, what's wrong with Kernel Flasher?
Click to expand...
Click to collapse
Nothing, it works great, but I want to minimize the number of installed apps, so it'd be even greater to be able to flash it via CWM
fahad123 said:
I would love to help if you have posted this in the right thread.. this is the development thread!
Click to expand...
Click to collapse
Yeah, I thought this belonged here since CWM, flashing kernels and kernel flashing apps would be considered as development tools.
If I was wrong, please forgive and may a mod move it away
Thanks!!!

It is a question, there is a dedicated Question and Answer thread. HMMM WHERE SHOULD I PUT IT?

This might help you?
http://forum.xda-developers.com/showthread.php?t=1308448

Thanks!
Jarmezrocks said:
This might help you?
http://forum.xda-developers.com/showthread.php?t=1308448
Click to expand...
Click to collapse
Thanks James, that was awesome!
Sadly they don't have the Semaphore 1.9.1 kernels (regular and big memory) which are what I use.
Now that I think about... I'll download what they have and try replacing the zImage. Will let you know how it goes!

Great!
It worked!
I had to modify the installation script a little and replace the zImages with the corresponding ones and it flashed OK!
Thanks Jamez, you rock!

There are two kind of kernel!
You can flash kernel with odin, like (speedmodkernel o other).
You can flash in Cwm mode! Usually are in zip file and flash it in recovery mode! It must be specify, if you can use odin or cmw!
Pay attention to cm7/miui kernel!
They use a particular filesystem and they aren't compliant to stok rom!

CM9 or ICS Alpha 3?

What is the difference with these 2 and which one should i choose. I got the alpha 3 right now
Sent from my GT-P1000 using XDA App

Hm... I'll chosse Cyanogenmod 9, I dont know because my tab is p1010 (no ics or cm9), but i think that Cyanogenmod is better.

Hey, did any of you try CM9? I tried 3 times and every time fail. Even after patched zImage came out. I can enter to recovery, do wipe factory, wipe cache but device doesn't boot. Stuck on inital GalaxyTab/SAmsung logo. Cant ask in correct thread as this is my first post.
I uploaded 1000L.zip, then with Heimdall uploaded zImage. Tried with 1000L.zip with replaced zImage in it but this zip can;t be installed (wrong file or sth).

Hi
i would download CM9 because GPS works

Do you know - what version of Google Voice Recognition is used in Alpha 3?
In CM9 you only have standard voice input without "open microphone" feature.

I've installed CM9, and it works, but it's an alpha and not for daily use. The developers are working hard, but there are no easily installable packages yet, or instructions how to get it installed or working. I started with Overcome 4.1, and got the current build. As it is, it's for the P1000L, so you have to get the P1000 kernel as well, and you have to replace the one in the ZIP with that one. You shouldn't just create a new ZIP, because it needs to be signed, and a new one won't be. Then you can update with recovery.
A lot of stuff works, but a number aren't, and as the phone is one of those not working (yet), people who want to just use the Tab probably shouldn't try this. If you like to get developing, or want to help out, know what you're doing and don't mind having a not fully functioning Tab, you can look up the the thread in the development section, get stuck in.

I installed CM9 yesterday and am LOVING it! I followed all directions from Humberos and others that are diligently working on bugs and have almost all functions working (calls/2g/3g/wifi/etc).
Camera doesn't work in normal functions, but will capture an image in panorama mode. This is coming along nicely!

CM9 and Alpha 3 has their good and bad, not to forget, both are still in testing stage and not meant for daily use at the moment.
For now it seems that cm9 has the upper hand in being more stable.

you could also try icedBoca... like the others, different things work
atm i'm on CM9 and most of the stuff works, but i can't connect to "hidden" wifi networks and internal sd / external sd mounting is a little bit mixed up

CM9 of course, I have the galaxy tab P1000N, and i have problems with alpha3 to much bugs and never fix them. Try to use CM9 with Humberos kernel, the room are much better and stable, free lag and never shut down. if u dont like try to use Boca rc1 final version

CM9
CM9 is better. I've tried both on my GSM P1000 and the CM9 is more refined and the repo is being constantly updated if you want to build it yourself.

Yep, CM9 is better but the Alpha 3 is good with few defaults...
I can't wait to flash the two...
What about HW acceleration with CM9 ? The build can play 720p but we don't know if we can play with big games like GTA...

CM9 is whole lot better, it has bluetooth, GPS and many more things working compared to Alpha 3. Today they have even declared USB Hosting is also working.
However, I would wait a little, till they incorporate all the small bugfixes in the ROM/Kernel.

brodzky said:
Hey, did any of you try CM9? I tried 3 times and every time fail. Even after patched zImage came out. I can enter to recovery, do wipe factory, wipe cache but device doesn't boot. Stuck on inital GalaxyTab/SAmsung logo. Cant ask in correct thread as this is my first post.
I uploaded 1000L.zip, then with Heimdall uploaded zImage. Tried with 1000L.zip with replaced zImage in it but this zip can;t be installed (wrong file or sth).
Click to expand...
Click to collapse
Have you wiped dalvik cache?
BTW I recommend you to use the flashable kernel (Download Page then go to "CwM flashable - Kernel", press P1000 or the appropriate model and download)
In fact a flashable zip should be SignApp'd. Have you do this after you modified a flashable zip. Ask the best friend in the new era how!

One question.. are the roms like, interchangable? Can I switch to each ROMs as per needed?
Also, can I downgrade back to a 2.3 version of Android afterwards?

delusioned said:
One question.. are the roms like, interchangable? Can I switch to each ROMs as per needed?
Also, can I downgrade back to a 2.3 version of Android afterwards?
Click to expand...
Click to collapse
With CWM/Recoverymode ,no. The problem is the ext4 formating. It is only possible if you flash the firmware 2.3 complete new with odin.

[Q] Anyone else with this problem?

after flashing CM10 my soft keys (the ones at the bottom) just won't work . They work pefectly inside CWM..
In another ROM, CM7 modded by boype, they work pretty good (still not as good as in CWM).
Is there anyone with the same problem??
If you don't have this problem, can you please let me know what ROM+Kernel you're using? then I can verify if this is a software or hardware issue. :good:

Darkwatch321 said:
after flashing CM10 my soft keys (the ones at the bottom) just won't work . They work pefectly inside CWM..
In another ROM, CM7 modded by boype, they work pretty good (still not as good as in CWM).
Is there anyone with the same problem??
If you don't have this problem, can you please let me know what ROM+Kernel you're using? then I can verify if this is a software or hardware issue. :good:
Click to expand...
Click to collapse
Try once again flashing CM10, don't forget to make full wipe (3 wipes)
No one has this problem

sekhar13515 said:
Try once again flashing CM10, don't forget to make full wipe (3 wipes)
No one has this problem
Click to expand...
Click to collapse
I get an error saying: Sd ext not recognized or something during Dalvik-wipe. Although my sd-card is working :/ I reflashed cm7 boypes and it's working. Then, I reflashed CM10 and it's not working. So, I downloaded the LG tool to get back to stock rom and guess what, it's not working... So, reflash of cm7 from boypes and they're working again..
Is this a kernel issue in combination with my firmware version or something?? (V20n currently)
Thx

Darkwatch321 said:
I get an error saying: Sd ext not recognized or something during Dalvik-wipe. Although my sd-card is working :/ I reflashed cm7 boypes and it's working. Then, I reflashed CM10 and it's not working. So, I downloaded the LG tool to get back to stock rom and guess what, it's not working... So, reflash of cm7 from boypes and they're working again..
Is this a kernel issue in combination with my firmware version or something?? (V20n currently)
Thx
Click to expand...
Click to collapse
Check md5 hashes of GAPPS and CM10 zip.
When you say not working. No lights? No response? More spesifics please.
Sent from my LG-P970

xonar_ said:
Check md5 hashes of GAPPS and CM10 zip.
When you say not working. No lights? No response? More spesifics please.
Sent from my LG-P970
Click to expand...
Click to collapse
Sorry for the inconvenience.
So, i flashed CM10 and the lights were on for about 5 seconds, I could not touch them (so no response it is), and then they went off. The only option is to reflash cm7, because i can't use the softkeys.
Can som1 give me some simple steps for:
- Returning to stock
- flashing the correct firmware using Smartflash (i'm from the Netherlands, i guess thats V20n ; Open Europe?)
- Make sure that the Clear Dalvik-cache option is fully working, (sd-ext error)
- Make CM10 work :/
So, just want to know what steps you guys did in order to make all things work correctly

HOWTO: flash custom GB and JB roms for 9070P (NFC)

HOW TO PREPARE i9070 CUSTOM ROMS TO WORK ON 9070P​
disclaimer as usual - everything on your own responsibility still, seems to be quite safe, the worst ever happened is no gsm signal if using not appropriate /lib/tee folder files. no soft/hardbricks reported (yet )
technical details - scroll a bit down
----
part 1: /system/lib/tee folder to replace
Jelly Bean Stock ROMS and ones based on Samsung Stock ROMs (Harshjelly, PureVanilla, LightJB..)​the most important information: in order to get i9070P Jelly Bean modded stock ROMs working, you have to:
1. download this file: http://d-h.st/vUw
2. save the file on your sd card (preferably external sd, not the internal memory)
3. flash your desired rom, do all neccessary wipes and so on, but DON'T REBOOT YET!
4. you have to install the zip downloaded in step 1 (don't confuse the order of steps 3 and 4, otherwise your rom won't work for 9070P, ie. you won't have any radio modules working - gsm, wifi, bt)
5. reboot and enjoy
tested by users on various modded stock roms (read all the pages); the one above works on stock-based ROMs only,
----
CyanogenMod ROMs
for CM10, CM10.1 and CM10.2 file here: http://d-h.st/E9e
proceed exactly as steps described above
thx Mr.xD97 - files for /system/lib/tee extracted from his rom here http://forum.xda-developers.com/showthread.php?t=2278169
according to hannez_r
Tee folder from JB 4.1.2 TW works on CM11.
Click to expand...
Click to collapse
- thx for the info
-------------------------​
part 2: the build.prop incompatibility:​this happens if you attempt to flash custom roms straight from your 9070P stock ROM. once you successfully flash any i9070 ROM, you won't be bothered with the issue (until you reflash your stock ROM with odin again)
in case flashing of your target rom ends immediately with an error ("assert failed: getprop....") then you have to do something with your build.prop. The explanation for that happening is: there are build.prop entries stating that the phone is "9070P" and the updater-script prevents your target ROM from being flashed to an uncompatible device (not an "9070")
possible solutions:​either: 1. grab some build.prop editors prior to flashing anything and change all occurences of "9070P" to "9070" and "janicep" to "janice". like this one: https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor or just edit your build.prop manually.
or: 2. unzip the target ROM .zip file, go to \META-INF\com\google\android and erase the lines starting with "getprop" (do NOT use windows notepad - it breaks the file, use notepad++ instead), save the edited updater-script and push it to the sd card. you're ready to flash the ROM
3. [automatically, to be tested] - waiting for your reports. ; use the build.prop.to.9070.zip to spoof your build.prop to i9070 model; it's a CWM flashable that should change the contents of your build.prop automatically. all credits for the script go to the author of this post: http://forum.xda-developers.com/showpost.php?p=19093919&postcount=20 - remember, not tested yet, in case you still get an assert:getprop error after flashing this .zip, try rebooting recovery and install the ROM .zip then method 3 most probably not working, so don't test unless you have lots of spare time to play with your phone
--------
source and inspiration:
I found that in galaxy ace 2 i8160/L/P forum - you have to replace /system/lib/tee folder (or 3 files inside) in order to flash custom roms made for i9070: there it is: http://forum.xda-developers.com/showthread.php?t=2159250

BUMP.
situation changed a lot. i9070P owners - try solution above
---
no more time today
btw. forgot to tell - take Gingerbread version of suppressed, no one knows what happens when you try with JellyBean version!

Woooow thank you
Gesendet von meinem GT-I9070P mit Tapatalk 2

If I understand properly, I should be able to download JetMod ROM. Replace the three files in the ZIP “tee” directory, “cops_ta.ssw, custom_ta.ssw, smcl_ta_8500bx_secure.ssw”, with the same named files currently in my phone, go to TWRP, Wipe System, Wipe Cache, Wipe Dalvik Cache, Factory reset, then install JetMOD zip?
Does this seem correct?

purplepizza said:
If I understand properly, I should be able to download JetMod ROM. Replace the three files in the ZIP “tee” directory, “cops_ta.ssw, custom_ta.ssw, smcl_ta_8500bx_secure.ssw”, with the same named files currently in my phone, go to TWRP, Wipe System, Wipe Cache, Wipe Dalvik Cache, Factory reset, then install JetMOD zip?
Does this seem correct?
Click to expand...
Click to collapse
yes, exactly. that way works for suppressed amoled/megatheme and for custom roms for ace 2 (ofc for ace 2 they use their /tee files respectively). so no reason it shouldn't work for jetmod.
---------
BTW curious to ask if anybody dared to flash any custom JB rom over recovery to 9070P? guinea pigs needed

You are awesome! Jetmod works great! Thank you!

thanks!!
Oh thank you very very much! I have one question... Now it is not possible try to flash a Jelly Bean rom for 9070 ok.. But in future owners of 9070P will get Jelly Bean probably this method will work also for Jelly bean custom roms for 9070?

FollonSaxBass said:
Oh thank you very very much! I have one question... Now it is not possible try to flash a Jelly Bean rom for 9070 ok.. But in future owners of 9070P will get Jelly Bean probably this method will work also for Jelly bean custom roms for 9070?
Click to expand...
Click to collapse
most probably - yes.
------
btw. I tried to run NFC on suppressed, but no go - deodexed NFC.apk, NFCTestmode.apk and Tag.apk, pushed to /system/app and set permissions, but still no way to run NFC. in case You people have any ideas, let me know fortunately not a dealbreaker to me.

adamuadamu said:
most probably - yes.
------
btw. I tried to run NFC on suppressed, but no go - deodexed NFC.apk, NFCTestmode.apk and Tag.apk, pushed to /system/app and set permissions, but still no way to run NFC. in case You people have any ideas, let me know fortunately not a dealbreaker to me.
Click to expand...
Click to collapse
If you have a native i9070p ROM... search the system folder for any file that contains nfc in the name, and copy it from the native i9070p ROM to suppressed. P.S. use windows search function

Another question: after flashing a custom rom for 9070 on 9070P is flashed also the kernel for 9070... Can we use kernel of the rom or we should change te kernel with CoCore-P? Thank you for the reply

FollonSaxBass said:
Another question: after flashing a custom rom for 9070 on 9070P is flashed also the kernel for 9070... Can we use kernel of the rom or we should change te kernel with CoCore-P? Thank you for the reply
Click to expand...
Click to collapse
as long as the kernel you currently use works OK - no need to worry; but check your CPU usage as some users reported excessive CPU usage all the time for older cocore kernels. I can confirm that cocore 4.1(for non-NFC version) and cocore-P don't have that issue
--
still no luck with NFC - the files I used are the only ones that can have anything in common with nfc. it gets even worse upon reboot as the NFC service app pops up FC window every three seconds and doesn't stop until I deleted it and rebooted again :|

adamuadamu said:
as long as the kernel you currently use works OK - no need to worry; but check your CPU usage as some users reported excessive CPU usage all the time for older cocore kernels. I can confirm that cocore 4.1(for non-NFC version) and cocore-P don't have that issue
--
still no luck with NFC - the files I used are the only ones that can have anything in common with nfc. it gets even worse upon reboot as the NFC service app pops up FC window every three seconds and doesn't stop until I deleted it and rebooted again :|
Click to expand...
Click to collapse
Are you sure you included all the libs ?
You also need to include all the NFC system apps as well
My life has more downs than ups, but I try to keep it a balance.

CallMeVentus said:
Are you sure you included all the libs ?
Click to expand...
Click to collapse
thanks for the suggestion. forgot to compare the differences in libs between 9070 and 9070P roms. will look into it

I have never flashed a new ROM. I want to try JetMod. It seems more I search, more restoring options are presented. (TWRP Restore or TB) Can someone recommend the safest and easiest method for restoring user apps and settings (SMS, MMS, & Contacts) on the new ROM? I have a TB and TWRP back up.

purplepizza said:
I have never flashed a new ROM. I want to try JetMod. It seems more I search, more restoring options are presented. (TWRP Restore or TB) Can someone recommend the safest and easiest method for restoring user apps and settings (SMS, MMS, & Contacts) on the new ROM? I have a TB and TWRP back up.
Click to expand...
Click to collapse
For Contacts I use the in-built backup feature....and SMS and MMS I usually use MyBackup Root for stock Messaging , otherwise when I'm using GO SMS Pro I use its in-built backup feature
My life has more downs than ups, but I try to keep it a balance.

Karsten95 said:
You are awesome! Jetmod works great! Thank you!
Click to expand...
Click to collapse
I must admit I tried Jetmod without success. Does not boot. Just startup screen being displayed.
I tried with default kernel and with cocore-P 1.0 kernel. Nothing worked. Might be something wrong with the installation (using TWRP in cocore-P 1.0). Installing system files seems to take just a fraction of second. And I suspect nothing was actually copied. I also tried replacing Aroma updater with the "regular one". Still the same...
Suppressed 2.2+2.5 worked. But it is not really my taste Should have tried 3.0 instead. But I would really like to try Jetmod. Any hints about the recovery?
Does CWM recovery for i9070 (non-P) http://forum.xda-developers.com/showthread.php?t=1987313 work for P devices? Anyone tried?

LaizyJumper said:
I must admit I tried Jetmod without success. Does not boot. Just startup screen being displayed.
I tried with default kernel and with cocore-P 1.0 kernel. Nothing worked. Might be something wrong with the installation (using TWRP in cocore-P 1.0). Installing system files seems to take just a fraction of second. And I suspect nothing was actually copied. I also tried replacing Aroma updater with the "regular one". Still the same...
Suppressed 2.2+2.5 worked. But it is not really my taste Should have tried 3.0 instead. But I would really like to try Jetmod. Any hints about the recovery?
Does CWM recovery for i9070 (non-P) http://forum.xda-developers.com/showthread.php?t=1987313 work for P devices? Anyone tried?
Click to expand...
Click to collapse
well, probably someone that's using jetmod on 9070P will tell you how to do it. but to be sure: did you start with 3.0, run the android wizard->rebooted to recovery->installed->3.1->rebooted to system->rebooted to recovery->installed 3.2 ? AFAIR when I was using i9070(non-P) I had to proceed these steps as flashing 3.0 + upgrades without reboots in the meantime caused bootloop or similar
as far as CWM is concerned - 1. it's temporary 2. it's meant for JB roms 3. never tried it on 9070P due to the fact TWRP always worked for me

Thank you very much adamuadamu... It worked very well for me... I installed jetmod 3.0 and i've done all the update to 3.2.2 without any problem
So none tried to do the same thing with Jelly Bean roms right?

FollonSaxBass said:
Thank you very much adamuadamu... It worked very well for me... I installed jetmod 3.0 and i've done all the update to 3.2.2 without any problem
So none tried to do the same thing with Jelly Bean roms right?
Click to expand...
Click to collapse
I'm pretty sure JB ROMs will have the same issues that GB non-P ROMs had....and we don't have the JB /system/tee files and kernel to deal with it
My life has more downs than ups, but I try to keep it a balance.

CallMeVentus said:
I'm pretty sure JB ROMs will have the same issues that GB non-P ROMs had....and we don't have the JB /system/tee files and kernel to deal with it
My life has more downs than ups, but I try to keep it a balance.
Click to expand...
Click to collapse
I think the lib/tee files are the main concern at the moment to get JB ported.
I have downloaded official kernel sources for i9070. And it includes config for 9070P as well. I managed to build the 4.1.2 kernel image for 9070P. But I don't really want to test it myself. I am not confident that it won't brick my device
So far, most of brave ones who have tried 9070 JB image on P-device have got a brick. If anyone could explain the reason, would be nice.
Does anyone know, if the reason is wrong kernel? Or is there something else in the JB installer that causes that. Some hboot partition or something?
Modem partition?

Tab reboots before BML/MTD can even get started. Then no recovery

Ok guys,
I am not new to Android but this is really really starting to give me the sh!ts. I have no f#*%ing idea how many times I have gone and restocked this POS tab.
I follow the guide to a T for Overcome etc etc. I know all that.
I can flash CM10 through recovery from there and it completes oddly enough. However it does not boot at all. I have done this maybe 10 times. No boot. Just constant re-install of the kernel and Cyangen Bootanimation. I also have no recovery as soon as that happens and then I have to start ALL OVER AGAIN!!!!
Ok so I decide to try CM 9.1.0 stable. Surely this will allow something. Guess what? It doesn't even install. YES I have removed the lines from the updater script. I mean how stupid. If you don't even have a system for a getprop to querey of course it is going to fail.
Remove the lines, gets to BML/MTP and starts to process for maybe about 10-15 seconds and then reboots and becomes a brick
What in gods name am I missing here that isn't in the million and 1 guides I have already read and the conflicting opinions of people say 'flash CM10 straight after Overccome kernel' and 'No no no you need to be onn CM9 first' and I have even read 'No you need to flash CM7 first then from there you can flash CM10'
Like WTF?
Cant there just be a 100% true guide. For starters Overcome ROM guide only gets you to there, nothing more. There is no steps in between. There are only guides that assume that you have done the steps to get to Overcome ROM.
I am about to scour the internet now and see if I can find CM7 cause I am sick to death of restocking and starting from scratch on this stupid POS. I mean FFS I thought that this would be straight forward like when I updated my i9000 Galaxy S to ICS, but noooooooo nothing I have done gets the results of what people claim in the guides.

These are my steps
Odin
PIT = gt-p1000_mr.pit
PDA = GB_Stock_Safe_v5.tar
Modem = modem.bin (JK3 as per the guide)
reboot download - it does boot otherwise
Odin
PDA = CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS.tar
reboots into Gingerbread
reboot download again
Odin
PDA = Overcome_Kernel_v4.0.0.tar
Sexy voice does her sh!t (I thought that this was where we did BML to MTD but it's not its rfs to ext4 - thought I'd add that for anyone that has in the past like me had experience with doing this stuff before and needs a refresher).
Reboot into recovery and from here is anybodys guess?
I need the EXACT EXPLICIT DETAILS FROM THIS POINT!
Everything I try from here completely messes the P1000 and I have to start again.
CM10 - Flashes but doesn't boot - recovery updates but flashing anything else obviously kills it and I start again
Overcome ROM wipe - Flashes but exists the script before completing
CM9.1.0 - Flashes, gets to BML/MTD and quits - note Recovery is completely screwed after this point
CM7 - Yes I am about to try this. Please tell me why this is wrong and explain and I will listen. Please also advise all the other people out there with guides that are wrong to update them and include the important details that they have overlooked for people like myself.
Thanks

Overcome kernel converts rfs to ext4 but still in BML.
When you flash cm9 or cm10, flash it 3 times.
That is by selecting the zip. Flash it, it reboots to recovery (a new recovery, no longer overcome).
Flash zip again. Now it converts to MTD. It then reboots to recovery. (Many people think it is bootlooping. )
At this point flash zip again. Now it does the longer install.
Screen says a lot of thing about /system and stuff.
Let it finish and reboot to cm.
The weakness of most guides is that they never say 3 times.
The noobs thinks it is a bootloop without reading what the recovery is doing.
Sent from my GT-N7100 using xda app-developers app

priyana said:
Overcome kernel converts rfs to ext4 but still in BML.
When you flash cm9 or cm10, flash it 3 times.
That is by selecting the zip. Flash it, it reboots to recovery (a new recovery, no longer overcome).
Flash zip again. Now it converts to MTD. It then reboots to recovery. (Many people think it is bootlooping. )
At this point flash zip again. Now it does the longer install.
Screen says a lot of thing about /system and stuff.
Let it finish and reboot to cm.
The weakness of most guides is that they never say 3 times.
The noobs thinks it is a bootloop without reading what the recovery is doing.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
You may have missed the point where Recovery becomes unreachable the minute I flash CM9 the first time. After that I can no longer get recovery and device becomes a brick.
Jarmezrocks said:
CM9.1.0 - Flashes, gets to BML/MTD and quits - note Recovery is completely screwed after this point
Click to expand...
Click to collapse
If you can provide a link to a known 100% certain to work version of CM9 or any CM I would be greatly appreciated! I believe there is much confusion (and to be honest I got lost with so many different opinions about changes made to CM in their thread) as to what version is best to flash. I personally tried the latest CM of version 9.1.0 and the stable (to which there were two and I tried one but not the other?) and did not have any luck with either.
Look forward to hearing from you
Thanks for your reply mate :good:

Not sure why your cm9 gone bad.
Make sure you download the p1 variant and check the md5 sum of the file.
It has always been on with me.
Restock. Overcome kernel. Then flash cm 3 times.
Unless there is a hardware issue?
Sent from my GT-N7100 using xda app-developers app

priyana said:
Not sure why your cm9 gone bad.
Make sure you download the p1 variant and check the md5 sum of the file.
It has always been on with me.
Restock. Overcome kernel. Then flash cm 3 times.
Unless there is a hardware issue?
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Thats the thing though, I believe that CM 9 has changed several times since the beginning. Both the latest and stable didn't work. There is another stable version but really got put off the whole ordeal because I was reading so many posts of people confused as to which version they should be flashing and which one they made the stable version in the end.
Something else also thrown in was that some guys where flashing Overcome and not allowing conversion to ext4 and then upgrading to CM10?
Should flashing Overcome kernel over the top of standard Gingerbread allow the device to boot and run stock GB with ext4? How would this be different to running stock and using OCLF4 on stock kernel with CWM Recovery? Say CF root Recovery?
Sorry for all the questions but the device isn't mine and I am now looking for the simplest solution to making it run normal and stable. Seems like normal GB is so unstable its not funny! Is it normal to get random reboots on stock Gingerbread?

It is not normal for GB to reboot by itself. There must be something not right.
About overcome kernel on top of normal GB with ext4, yes that is possible to run it that way.
About allowing overcome kernel to convert to ext4, or not to allow that, it doesn't matter.
CM kernel will repartition the internal storage and everything will dissappear once a new partition scheme is in.
My suggestion is usually for people to not wait for overcome kernel to convert since it is not needed.
Sent from my GT-N7100 using xda app-developers app

Hey I got some good news!:good:
And....I will need you @priyana to update your OP for the Overcome ROM thread too, this will apply to all Australian P1000 Tabs I guess...well at least the Optus ones anyway.
Essentially the GB_Stock_Safe_v5.tar and gt-p1000_mr.pit are NOT safe like we are lead to believe....well not for the tablet I have just repaired. It is now running CM10 no problems!
I have created a new firmware package that incorporates a new PIT and various combos of files from the old GB_Stock_Safe_v5.tar and the standard firmware package.
What I found was flashing the completely stock firmware the device would not boot or function what so ever, which is really strange as most people would expect that standard firmware would at least be stable enough to use. Not even with the stock PIT or the gt-p1000_mr.pit.
You can down load the files here >>> GB_Stock_AUST_Jarmezrocks+P1.pit
This will have a firmware package and pit file combination that is suited to Australian P1000 TABS
Containing
GB_Stock_AUST_Jarmezrocks.tar
P1_add_hidden.pit
These are the ONLY files that will allow the Tab to boot, run and function normally. Before the thing was just so unstable you could barely do anything with it.
So from here Australian user who are having issues/problems with the Overcome ROM guide and getting continual reboots or bootloops should flash this package.
I will start a new thread in the dev section where it will be seen by others who are wanting to salvage their device.

That is good to hear.
BTW, the new overcome thread is sos_sifou's, not mine ?
Regarding the stock ROM, I remember that Stimpz0r, one of the great devs here, used to own a P1000 from optus and have no issue with overcome GB stock safe v5.
Makes me wonder if there are different variant of optus P1000.
Sent from my GT-P1000 using XDA Free mobile app

priyana said:
That is good to hear.
BTW, the new overcome thread is sos_sifou's, not mine ?
Regarding the stock ROM, I remember that Stimpz0r, one of the great devs here, used to own a P1000 from optus and have no issue with overcome GB stock safe v5.
Makes me wonder if there are different variant of optus P1000.
Sent from my GT-P1000 using XDA Free mobile app
Click to expand...
Click to collapse
Sorry yeah you are right, you're just the heavy promoter of it (with good reason too eh?)
I will PM him and see if he can include it in the OP?
All I know is that without a doubt there was no way that package was saving this Tab, and that the one I posted most certainly did....so it would suggest to me that there is a difference between some models...I mean why else would they create a different firmware with a different .pit file? It makes no sense to do it without reason when really it is much easier to maintain the status-quo...don't you think?
Thanks for your valuable input too by the way. I really appreciate it :good:

can you re-upload ? i cannot download it