Database Info

[Q] Is there a ROM not affected by RR / SOD??

I've been searching here for a long time and looking at different custom ROMs but cannot find an answer. (so please be gentle on me if I missed the obvious...)
Is there a custom ROM for the TF101 which is not affected by the RR, SOD, bootloop, and all the other issues introduced in stock ICS?
Will appreciate the advice.

yud said:
I've been searching here for a long time and looking at different custom ROMs but cannot find an answer. (so please be gentle on me if I missed the obvious...)
Is there a custom ROM for the TF101 which is not affected by the RR, SOD, bootloop, and all the other issues introduced in stock ICS?
Will appreciate the advice.
Click to expand...
Click to collapse
I have used android revolution hd since it updated to ICS and not since the first ICS ota version have I seen a random reboot and I have never had a SOD

Get a new kernel
Your solution to SODs and ROR is getting a new kernel, the best one is to my point of view GUEVOR works, the last ones are great with stock rom.

werewolferx said:
Your solution to SODs and ROR is getting a new kernel, the best one is to my point of view GUEVOR works, the last ones are great with stock rom.
Click to expand...
Click to collapse
This is what you need to do. But, I would recommend either the 17c or 16b. I had a lot of SOD with the latest 19.2 kernel.

Thank you all!
I'm currently on stock .21
So confirming that what I need to do is:
Revert to an older, rootable stock ROM
Root
Then either:
Install Guevor kernel (with stock rom?)
or
Install Revoultion HD
Is this correct?

Yes, Guevor 17c is rock stable, so is the TestyMehIcs kernel. Both should do you good
ARHD on it's own (as mike tweaks the kernel) or with Guevor/testymeh is good too.

Thing O Doom said:
Yes, Guevor 17c is rock stable, so is the TestyMehIcs kernel. Both should do you good
ARHD on it's own (as mike tweaks the kernel) or with Guevor/testymeh is good too.
Click to expand...
Click to collapse
Thanks @Thing O Doom.
And is the procedure above correct?

Yes, between steps 2 and 3 though you need to make sure to install CWM recovery (I recommend Rouge XM version, as it reads internal and external SD card) this is what you will use to flash the kernel and a ROM

Thing O Doom said:
Yes, between steps 2 and 3 though you need to make sure to install CWM recovery (I recommend Rouge XM version, as it reads internal and external SD card) this is what you will use to flash the kernel and a ROM
Click to expand...
Click to collapse
Thanks Thing O Doom.
Yes, I forgot to mention CWM...
Will try the stock .24 when it comes out (hopefully this weekend) and if RR continues I will go Revolution HD or guevor.

[KERNEL][ICS] Harmony (OC/UV)

This Kernel is for testing only right now, so be careful at what you're doing please.
The kernel has the following features:
Overclocked up to 1.4 GHZ
Slightly undervolted
Extended File System support -> REISERFS, BTRFS, NTFS (full read / write support)
based on the newest ASUS .24 source
more to come ..
BE CAREFUL ! FIRST TIME FLASHING THIS KERNEL WILL GIVE YOU A BOOTLOOP WHICH YOU SHOULD BE ABLE TO FIX WITH THE METHOD DESCRIBED IN ROACH'S THREAD !
I am trying to find the fault in the updater-script, working hard here.
Please don't be mad at me, this is my first kernel ever built for android.
But everyone's gotta start somewhere, eh ?

Cool, thanks for sharing. Will try.

rayman33 said:
This Kernel is for testing only right now, so be careful at what you're doing please.
The kernel has the following features:
Overclocked up to 1.4 GHZ
Slightly undervolted
Extended File System support -> REISERFS, BTRFS, NTFS (full read / write support)
based on the newest ASUS .24 source
more to come ..
BE CAREFUL ! FIRST TIME FLASHING THIS KERNEL WILL GIVE YOU A BOOTLOOP WHICH YOU SHOULD BE ABLE TO FIX WITH THE METHOD DESCRIBED IN ROACH'S THREAD !
I am trying to find the fault in the updater-script, working hard here.
Please don't be mad at me, this is my first kernel ever built for android.
But everyone's gotta start somewhere, eh ?
Click to expand...
Click to collapse
I had the bootloop issues in the past when I tried to flash some of Blades earlier kernels. I had to remove the busybox parts out of his ramdisk and repack it to get it to flash successfully. None of the other kernels at the time had the busybox stuff and they all flashed OK.

rayman33 said:
BE CAREFUL ! FIRST TIME FLASHING THIS KERNEL WILL GIVE YOU A BOOTLOOP WHICH YOU SHOULD BE ABLE TO FIX WITH THE METHOD DESCRIBED IN ROACH'S THREAD !
Click to expand...
Click to collapse
A link or pointer to Roach's thread will be appreciated.

Will wait until the proper flash zip is ready. Just don't want to take chances on this bootloop thing.
Sent from Transformer TF101 (B60) via XDA Premium HD

Glad to see you hit the ground running! Hope to see more soon :-D Good luck!

nice work will try .

Cool to see another kernel, I'll try when the bootloop is fixed.

Don't flash this until it's been fixed. The blob is incorrectly build and there is a high chance of it causing bricks!

Might be best to remove the file if it will cause bricks.

Hey people, just a quick notice :
I achieved unbricking my sbkv2 device using "nvflash" wheelie by rayman84 ! Many thanks for this, dude.
Currently reworking the kernel from scratch.
Friendly blob should be up soon.

[Q] cromi-x and cm11

Hi,
I've been using cromi-x rom for several months (v5.2.3 with kernel thatv7 and fsync off) and it run really fine. I even don't consider to install data2sd or rom2sd as performance already meets my needs due to fsync off.
But i'm a curious man and i'm interested in testing another rom : cm11. But i have few questions about that (i did not find answers in existing threads) :
- does cm11 correct the tf700 i/o issue (with sync off for example) and will i get as good performance than on cromi-x ?
- i have TWRP installed but CM requires CWR. Which one is compatible with both roms (so that i can easily switch back from one rom?to the other) ?
Thanks
Sent from my ASUS Transformer Pad TF700T using xda app-developers app

Ghorin said:
Hi,
I've been using cromi-x rom for several months (v5.2.3 with kernel thatv7 and fsync off) and it run really fine. I even don't consider to install data2sd or rom2sd as performance already meets my needs due to fsync off.
But i'm a curious man and i'm interested in testing another rom : cm11. But i have few questions about that (i did not find answers in existing threads) :
- does cm11 correct the tf700 i/o issue (with sync off for example) and will i get as good performance than on cromi-x ?
Click to expand...
Click to collapse
I doubt it since essentially it is hardware related (cheap memory) and I doubt that the CM team found a better way to mitigate it than sbdags.
- i have TWRP installed but CM requires CWR. Which one is compatible with both roms (so that i can easily switch back from one rom?to the other) ?
Click to expand...
Click to collapse
TWRP 2.6.3.2 also works with CM11. It also seems to work fine with CROMi-X.
sbdgas just modded the rom2sd2 script to run CM11 as rom2sd with _thatv7 on internal. Somebody else tried the same scenario with Hund's kernel - both ran like syrup it seems....
But give it a shot running CM11 on internal with TWRP 2.6.3.2! That's what nandroids are for
And let us know how it went!

berndblb said:
I doubt it since essentially it is hardware related (cheap memory) and I doubt that the CM team found a better way to mitigate it than sbdags.
Click to expand...
Click to collapse
As far as I understand, the solution was to put fsync to off. Maybe CM has also implemented that solution, but I don't find any information about that on CM thread / website.
berndblb said:
TWRP 2.6.3.2 also works with CM11. It also seems to work fine with CROMi-X.
sbdgas just modded the rom2sd2 script to run CM11 as rom2sd with _thatv7 on internal. Somebody else tried the same scenario with Hund's kernel - both ran like syrup it seems....
But give it a shot running CM11 on internal with TWRP 2.6.3.2! That's what nandroids are for
And let us know how it went!
Click to expand...
Click to collapse
Yep you're right, I see that there is a thread explaning that, I will read it and try to apply it. I'll give news about my testing but that will take a few days probably as i'm very busy at the moment at home.

I've read the dual-boot internal+external rom thread and it needs a linux machine which i don't have. Could i do that gparted configuration with a live-linux CD ?
And about performance, does the option "fsync off" exist in CM11 ? If not then i don't expect good performance/no-lag like on CROMI-X and i would be then not interested to test CM.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app

Ghorin said:
I've read the dual-boot internal+external rom thread and it needs a linux machine which i don't have. Could i do that gparted configuration with a live-linux CD ?
Click to expand...
Click to collapse
Sure! I recommend the one from sysresccd.org (should be in every household), but you can also use the GParted live CD or any other that includes gparted.
Ghorin said:
And about performance, does the option "fsync off" exist in CM11 ? If not then i don't expect good performance/no-lag like on CROMI-X and i would be then not interested to test CM.
Click to expand...
Click to collapse
As long as the kernel supports "fsync off", it will also work in CM.

_that said:
Sure! I recommend the one from sysresccd.org (should be in every household), but you can also use the GParted live CD or any other that includes gparted.
As long as the kernel supports "fsync off", it will also work in CM.
Click to expand...
Click to collapse
Thanks for your answer, i'll try it when i have time (late at night when child and wife are sleeping )

Not all kernels that support f sync off support cm11, the only cm11 kernel besides the stock cyanogen mod one is bryce09's and that still has bugs. CM 11 with the build.prop tweaks, clean master, lagfix, and crossbreeder give performance better then CROMI-X with no overclock.
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app

[Q] Link to bodivas repack kernel for 6810

Hi, does anyone have a link to the bodivas repack kernel for the 6810? The link is missing from UTIA's second post in the thread for his kernel. I want to give his kernel a whirl. Thanks, Matt

Ignore this request. I flashed UITA's kernel but my hardware and his ROMs/kernels do not get along :'(
Reverting back to my backup...
Matt

mattbuffey said:
Ignore this request. I flashed UITA's kernel but my hardware and his ROMs/kernels do not get along :'(
Reverting back to my backup...
Matt
Click to expand...
Click to collapse
I'll upload it later today. Forgot all about it sorry.
Firstly, did you flash the SkyHigh kernel after first boot of any ROM? Don't flash directly after ROM flash. Otherwise boot loop. Only after ROM full boot.
Secondly, make sure that you have no tweaks or tweaking apps etc installed.
For the ROM, you need to follow the installation instructions EXACTLY, using correct recovery version and full wipe install.
Other than that, unfortunately, your hardware may not like some of the kernel tweaking or UV etc.
BTW, I'm working on a SkyHigh kernel update. Maybe try that in future "IF" I ever get to release stage.....
Sent from my GT-I9500 using XDA Premium 4 mobile app

It's weird, I had the same problem with your ROM on ICS. I was hoping JB would be different, but I got exactly the same stability problem. As you say, it must be something to do with the tweaks that upsets my tab. I can report that CIFS works fine with your kernel though!

[Q] changing kernels?

I've looked into many threads, but have still not been able to find a definitive answer: when changing kernels (going for example from ElementalX to Franco or Purify) should I do a dirty re-flash of the rom and then flash the new kernel or will just a flash of the new kernel be enough?
I know it's been asked before, but I can't seem to find a clear answer.
Thanks
Alex

alexm231 said:
I've looked into many threads, but have still not been able to find a definitive answer: when changing kernels (going for example from ElementalX to Franco or Purify) should I do a dirty re-flash of the rom and then flash the new kernel or will just a flash of the new kernel be enough?
I know it's been asked before, but I can't seem to find a clear answer.
Thanks
Alex
Click to expand...
Click to collapse
1st option

Primokorn said:
1st option
Click to expand...
Click to collapse
Thanks for the reply.
So (just to make sure I have it correct) right now I am running Purity + Purify. If I want to switch to a Purity + Franco setup, I need to dirty flash Purity rom (in which case it brings the kernel back to the standard Purity kernel) and then Franco kernel after that, right?
Do I need to wipe cache or anything else?
Thanks again for all the help
Alex

alexm231 said:
Thanks for the reply.
So (just to make sure I have it correct) right now I am running Purity + Purify. If I want to switch to a Purity + Franco setup, I need to dirty flash Purity rom (in which case it brings the kernel back to the standard Purity kernel) and then Franco kernel after that, right?
Do I need to wipe cache or anything else?
Thanks again for all the help
Alex
Click to expand...
Click to collapse
You're right. To prevent any issue it's better to follow this rule regardless of the custom kernel. We need to dirty flash our current rom due to modifications done by the kernel on the ramdisk.
You never need to wipe before flashing a kernel.

Primokorn said:
You're right. To prevent any issue it's better to follow this rule regardless of the custom kernel. We need to dirty flash our current rom due to modifications done by the kernel on the ramdisk.
You never need to wipe before flashing a kernel.
Click to expand...
Click to collapse
Great. Thanks so much for the detailed answer, it clears up my confusion!
Now off to try Franco's kernel
Alex

Primokorn said:
You're right. To prevent any issue it's better to follow this rule regardless of the custom kernel. We need to dirty flash our current rom due to modifications done by the kernel on the ramdisk.
You never need to wipe before flashing a kernel.
Click to expand...
Click to collapse
I actually have an additional question: do we need the same process even if we're talking about the newer version of the same kernel? Like going from an older version of Franco's to the newest
Alex

No only when you change kernel you need to do it.
Sent from my Nexus 5 using Tapatalk

kufikugel said:
No only when you change kernel you need to do it.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thank you, I promise I will (try) not (to) ask any more silly questions
Alex

alexm231 said:
Thank you, I promise I will (try) not (to) ask any more silly questions
Alex
Click to expand...
Click to collapse
Its better to ask "Silly" questions and understand what you're doing than it is to brick your phone then ask for help.
We'll answer your questions, dont worry. Just ensure you read all the sticky threads in Q&A and General.

rootSU said:
Its better to ask "Silly" questions and understand what you're doing than it is to brick your phone then ask for help.
We'll answer your questions, dont worry. Just ensure you read all the sticky threads in Q&A and General.
Click to expand...
Click to collapse
Yes, I consider your guideline (on your signature) very good advice indeed.
Thanks again to all
Alex

Just wanted to add to this...
If I'm on the stock ROM. I decide to flash elementalx. Then, want to switch to Franco or something, would I need to flash the stock img? Or can i just flash the stock kernel?
Sent from my Nexus 5 using Tapatalk

justinisloco said:
Just wanted to add to this...
If I'm on the stock ROM. I decide to flash elementalx. Then, want to switch to Franco or something, would I need to flash the stock img? Or can i just flash the stock kernel?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Wondering the same thing. If I am currently on stock rom with franco kernel, in order to switch over to elemental do I have to flash the stock rom zip from the thread here on XDA and then install the elemental kernel?

matts290 said:
Wondering the same thing. If I am currently on stock rom with franco kernel, in order to switch over to elemental do I have to flash the stock rom zip from the thread here on XDA and then install the elemental kernel?
Click to expand...
Click to collapse
I know I had to do that when I flashed elemental. Otherwise some apps won't open. But now I want to find out was the the full correct way? Or was it the lazy way
Sent from my Nexus 5 using Tapatalk

justinisloco said:
Just wanted to add to this...
If I'm on the stock ROM. I decide to flash elementalx. Then, want to switch to Franco or something, would I need to flash the stock img? Or can i just flash the stock kernel?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
matts290 said:
Wondering the same thing. If I am currently on stock rom with franco kernel, in order to switch over to elemental do I have to flash the stock rom zip from the thread here on XDA and then install the elemental kernel?
Click to expand...
Click to collapse
Flash the stock boot.img and system.img and then flash the kernel you want to change to..
I have also tried just flashing the stock boot.img and then the custom kernel.. Sometimes it works, sometimes it doesn't. So I would reccomend flashing both! (boot and system)

also check to see if the original kernel left any init.d files, some kernels do. you would want to delete them, as those could, probably would, not play well with your next kernel.

simms22 said:
also check to see if the original kernel left any init.d files, some kernels do. you would want to delete them, as those could, probably would, not play well with your next kernel.
Click to expand...
Click to collapse
another noob question,
does your advice still applies if someone flashed both stock system.img and stock boot.img?
if it is where that file will be located?
thanks.

akmsr said:
another noob question,
does your advice still applies if someone flashed both stock system.img and stock boot.img?
if it is where that file will be located?
thanks.
Click to expand...
Click to collapse
yes. they arent located in either of those locations, so my advice applies, and is the only reason why i posted this. they are located in /etc/init.d/. you either dont have that location (best option), have it but an empty folder, or have an init.d folder with files in it. if there are files there, delete them.

Flashing a system.img will overwrite init.d scripts. /etc is a symbolic link to /system/etc so when you replace /system/etc with whatever is in a ROM.zip or a system.img, these changes apply to /etc too.
If you look in any ROM.zip or kernel.zip, they all flash their scripts to /system/etc/init.d
Sent from my Nexus 5 using Tapatalk