[ROM][JB 4.2.2] [ KatKiss-4.2.2 #226 ] [Stable]

[timduru]

Ok, I managed to get to recovery and i'm restoring previous ROM. Now what should I do to avoid bootloop when flashing this ROM?

If you make a full wipe / factory reset before installing it will work fine.
Make sure you don't restore any system settings.
You might also want to switch directly to KatKiss 4.3.1
or 4.4.2 if you don't need what is not working yet in 4.4.2

 

[chefp]

boot loop

This TF101 is stuck on the initial "Eee Pad Asus" splash screen. I'm not sure if this was caused by KK but it's the first time this has happened on this TF101. Prior to that it had been on for over a week without charging. The dock battery was drained completely and the internal was at 23%. I plugged into the dock to charge and powered off the tablet to reduce battery drain.

I'm not sure what to call it other than a boot loop. It just cycles to that power-up screen over & over, never actually starting the image boot. Doing a cold boot into Android (power + vol-down, wait) does the same thing.

The good news is that I can get it into TWRP recovery with the power + vol-down then vol-up buttons. I've tried wiping dalvik, cache, system, re-flash KatKiss image... no go. Also tried from the TWRP terminal "echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0".

Is there a bootblock image that needs to be reflashed?

 

[ricardocardoso]

If you make a full wipe / factory reset before installing it will work fine.
Make sure you don't restore any system settings.
You might also want to switch directly to KatKiss 4.3.1
or 4.4.2 if you don't need what is not working yet in 4.4.2

I did a full wipe before flashing...

Sent from my Transformer TF101 using XDA Premium HD app

 

[jazzruby]

This TF101 is stuck on the initial "Eee Pad Asus" splash screen.
The good news is that I can get it into TWRP recovery with the power + vol-down then vol-up buttons. I've tried wiping dalvik, cache, system, re-flash KatKiss image... no go. Also tried from the TWRP terminal "echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0".

I'm not sure if this pertains in your case but let's at least verify the above 'echo' command was executed and placed 'boot' as the first item.

cat /dev/block/mmcblk0p3
boot
recovery
...

-JR-

 

[ricardocardoso]

If you make a full wipe / factory reset before installing it will work fine.
Make sure you don't restore any system settings.
You might also want to switch directly to KatKiss 4.3.1
or 4.4.2 if you don't need what is not working yet in 4.4.2

Flahed 4.3.1 and all went well

 

[chefp]

I'm not sure if this pertains in your case but let's at least verify the above 'echo' command was executed and placed 'boot' as the first item.

cat /dev/block/mmcblk0p3
boot
recovery
...

-JR-

Interesting... that command blanks the output window using Terminal Command in TWRP. There's no visible output from the cat. Could this be a TWRP bug? Without being able to boot, how else can I write to mmcblk0p3?

 

[Kingzak34]

Interesting... that command blanks the output window using Terminal Command in TWRP. There's no visible output from the cat. Could this be a TWRP bug? Without being able to boot, how else can I write to mmcblk0p3?

Use easy flasher and restart from the begining

Envoyé depuis mon Transformer TF101 avec Tapatalk 4

 

[chefp]

Use easy flasher and restart from the begining

Hoping to avoid a complete wipe if at all possible. From what I can tell, something's corrupted with the bootloader partition or mmcblk0p3 (is that the bootloader itself or what tells the tablet which partition to boot?). Would nvflash.exe --bl bootloader.bin be enough to fix the bootloader?

 

[jazzruby]

Hoping to avoid a complete wipe if at all possible. From what I can tell, something's corrupted with the bootloader partition or mmcblk0p3 (is that the bootloader itself or what tells the tablet which partition to boot?). Would nvflash.exe --bl bootloader.bin be enough to fix the bootloader?

Well... you have a few options:
First, if you can ADB to the device, then drop into a shell and run the 'echo boot' command from there and verify with the 'cat' command that 'boot' is first.

Second, it would indeed be nice if NVFlash was that easy on our device (tf101) but it's not; we need --for a better lack of term-- a proxy, and that would be 'Wheelie' it was started by 'rayman' and you can read/get started HERE (Linux) and HERE (Windows)

Third, if you can make a full NANDroid backup, then you can always do a Selective/Advanced restore, e.g. /system or /data or both after a 'wipe/rebuild' of your device.

Fourth, backup your 'User' apps with TitaniumBackup and anything on 'Internal memory', e.g. Docs, Pics, etc...(you can use TWRP terminal and copy to external SDcard), in case you choose the third option and it fails.

HTH,

-JR-

 

[chefp]

Well... you have a few options:
First, if you can ADB to the device, then drop into a shell and run the 'echo boot' command from there and verify with the 'cat' command that 'boot' is first.

Second, it would indeed be nice if NVFlash was that easy on our device (tf101) but it's not; we need --for a better lack of term-- a proxy, and that would be 'Wheelie' it was started by 'rayman' and you can read/get started HERE (Linux) and HERE (Windows)

Third, if you can make a full NANDroid backup, then you can always do a Selective/Advanced restore, e.g. /system or /data or both after a 'wipe/rebuild' of your device.

Fourth, backup your 'User' apps with TitaniumBackup and anything on 'Internal memory', e.g. Docs, Pics, etc...(you can use TWRP terminal and copy to external SDcard), in case you choose the third option and it fails.

HTH,

-JR-

Thanks for the tips. It's starting to look like I'll have to go the wheelie route and wipe the tablet. When I do echo boot from an adb shell (while the tablet is in TWRP), mmcblk0p3 reads "boot" at the beginning. However whenever it reboots, it doesn't stick and of course doesn't boot. Sure hoping this isn't a defective flash sector.

Has anyone else's tablet gotten a corrupt bootloader from normal operation? Seems like this would have to be a low-level kernel type of bug to do something like that.

 

[jazzruby]

Thanks for the tips. It's starting to look like I'll have to go the wheelie route and wipe the tablet. When I do echo boot from an adb shell (while the tablet is in TWRP), mmcblk0p3 reads "boot" at the beginning. However whenever it reboots, it doesn't stick and of course doesn't boot. Sure hoping this isn't a defective flash sector.

Has anyone else's tablet gotten a corrupt bootloader from normal operation? Seems like this would have to be a low-level kernel type of bug to do something like that.

When you say "reads 'boot' at the beginning", you do mean on it's own line, correct?

boot-recovery
NO GOOD (stuck) needs the dd command

boot
recovery
....
GOOD

As a last ditch effort; why not try and flash Roach's recovery HERE it contains a hack that uses a slightly different command (you could also try in terminal)
dd if=/dev/zero of=/dev/block/mmcblk0p3
or
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=1 count=13

-JR-

 

[*Detection*]

Has anyone managed to connect to a Wireless N only network with this ROM ?

The TF can see mine, but won't connect, doesn't even seem to try, it just jumps back to the list of networks again

Any ideas how to get it to connect ?

 

[polishfly]

Hey guys, I know this is old and outdated, but.....

Sometime between now and a few months ago I suspect my tablet updated an APP and is now useless. It keeps playing the nice Kat Kiss 4 dot doodle that comes up when the OS is powering up. I tried to wipe cache and devik and it just gets stuck at "Starting applications" and does not go any further. I tried installing the same Kat Kiss ROM on top and it does the same thing.

 

[jazzruby]

Hey guys, I know this is old and outdated, but.....

Sometime between now and a few months ago I suspect my tablet updated an APP and is now useless. It keeps playing the nice Kat Kiss 4 dot doodle that comes up when the OS is powering up. I tried to wipe cache and devik and it just gets stuck at "Starting applications" and does not go any further. I tried installing the same Kat Kiss ROM on top and it does the same thing.

First off, you should really update to a more recent version i.e. KatKiss JB | KatKiss KK etc...

If not, then try (re)installing the ROM but make sure to WIPE SYSTEM FIRST.

HTH,

-JR-

 

[polishfly]

First off, you should really update to a more recent version i.e. KatKiss JB | KatKiss KK etc...

If not, then try (re)installing the ROM but make sure to WIPE SYSTEM FIRST.

HTH,

-JR-

I hate wiping the system cause I dont want to lose my settings and layout.

If i do go to a new ROM what do yo recommend? Is KK stable and fast? My TF101 was screaming on the 4.2.2 and i dont want to lose that performance.

 

[jazzruby]

I hate wiping the system cause I dont want to lose my settings and layout.

If i do go to a new ROM what do yo recommend? Is KK stable and fast? My TF101 was screaming on the 4.2.2 and i dont want to lose that performance.

1. Most of your settings are stored on the /data partition and would require a Factory reset/Wipe data to clear("lose"). On /system you may be concerned with root(su) mods e.g. hosts file, startup scripts etc...

2. All of @timduru (KatKiss) builds are fast and stable you'll just have to read up on the threads to see what's best for you.

-JR-

 

[Piehti]

I hate wiping the sys[...] stable and fast? My TF101 [...] ant to lose that performance.

Most stable and working with all features (even multiwindow): KitKass 4.3.1 is what you want. Also - as far as I know - it's faster as 4.2.2.
Most uptodate but ART and Multiwindow not working and no big time advantages to 4.3.1 then KatKiss 4.4.2 would be your pick.

As said before: All of Tims rom are quit stable and as far as I tested also the fastest and most responsive.
You can't go wrong with 4.3.1. You might consider backing up your layouts and settings before. Before and after flashing.
NAND Backups would be my suggestion. Have a look at my tutorials.

Cheers.

 

[polishfly]

If I wipe system, do I lose all of my apps and have to re-install them?

 

[Piehti]

If I wipe system, do I lose all of my apps and have to re-install them?

Yes you do - if you do it right. But you could backup them. Just get Titanium Backup.
This might help: Brief backup guide

Gesendet von meinem Transformer TF101 mit Tapatalk

 

[Kingzak34]

Format system do not erase user data

Tapatalké avec mon Nexus 4 MIUI !