[Q] Why can't I install a kernel? - Eee Pad Transformer Q&A, Help & Troubleshooting

I can't install *any* kernel. I've rooted from 8.4.4.11 with the Pure.Root batch file, which works perfectly. I've tried using CWM to install several Clemsyn kernels, STOCK kernel (?!), and even pulled a blob out of one of Clemsyn's packs and turned it into a '.img', which I then nvflashed. NOTHING works.
I get the blue bar across the screen, the quick reboot, then the "Eee Pad" screen forever. It won't power off from the power button (immediately powers back up to "Eee Pad" screen); I have to go into CWM and power down from there. The only recovery options are 1) re-do the 'boot.img' from Pure.Root or 2) start over with the full recover to 8.4.4.5 from Tabletroms, both of which work without incident. I've even done a data wipe (volume down), and tried doing a cold boot (volume down, then volume up at the prompt)
Maybe I'm asking too much, but I'd *really* like a rooted tab with OC kernel, running on stock ROM. Is this simply not possible? (*shrug* works on my Nook Color...)
-B60* unit, perfect working order
-8.4.4.11, "manual" install (never picked up the OTA)
-this -> Pure.Root works perfectly, except CWM (noted below)
-cwm-solarnz-8.4.4.11.img (had to replace 'recovery.img' in Pure.Root; no other method would allow entry into recovery mode)
-wiped cache/cleared Dalvik EVERY TIME

did you try kernel manager from the market?
Sent from my Transformer TF101 using Tapatalk

didn't think it was working with the xformer yet...
--edit--
Ah, gomen, it was Rom Manager I was thinking of... Regardless, it (Kernel Manager) didn't work either.

Stupid question, but in CWM you did the following ?
-Install zip from SDcard
-Select zip
-pick the kernel zip
-go back
-reboot (CWM option)

bud77 said:
Stupid question, but in CWM you did the following ?
-Install zip from SDcard
-Select zip
-pick the kernel zip
-go back
-reboot (CWM option)
Click to expand...
Click to collapse
Yes

Then I would suggest a reinstall via NVFlash, and retry kernel installation
You might have screwed at some point, which makes you stuck now

bud77 said:
Then I would suggest a reinstall via NVFlash, and retry kernel installation
You might have screwed at some point, which makes you stuck now
Click to expand...
Click to collapse
I think you might've misunderstood; I'm not currently "stuck", - I can recover any time I want, I'm just limited to the rooted kernel from Pure.Root. No other kernel will boot (well, except for stock, of course)

Ah, my bad, I kinda misunderstood
I trhink there might be some limitation with pure.(stock.)root
Have you tried a "real" ROM then change kernel ?

bud77 said:
Ah, my bad, I kinda misunderstood
I trhink there might be some limitation with pure.(stock.)root
Click to expand...
Click to collapse
That's my working theory as well...
bud77 said:
Have you tried a "real" ROM then change kernel ?
Click to expand...
Click to collapse
I've been hesitant to, particularly with 3.2 coming soon out now
There's also the question of which one... There's a lot to choose from.
Depending on what 3.2 offers, I may upgrade and wait for a new rootkit before I do anything else.
Thanks for the replies!

Well, I'm a Prime user, so I can only guide you to it (Roach does a great job & support on it)
Closest to the stock ROM, with nice optimization
But the best rom for one person, might not be for another
Best is to try, and find which suits you best ^^

Related

Rooted i9023, some help needed please!

Ok guys so I have managed to root my i9023 and flash clockwork recovery which was all good, I set about flashing some new roms via rom manager, again, all good.
So now I settle on this cm7 based rom which I love, used anim mod to get some nice transitions, then I used font changer.
All was good, then I decided that the font I was using was a bit ott so I decided to change it again, upon reboot it starts boot looping, bollocks !!!
So I try to get into clockwork recovery, and it seems to have gone back to the stock bootloader, grrrrr
I re flash clockwork, wipe / clear etc... then flash the rom again, but it would not flash, so I went to my backup of stock n flashed that, all good.
I then install rom manager again and flash the rom I liked again, this time no problem, but when it loads up the home button and search button are not working
So i decide on a factory reset, I select wipe everything including sd just to be sure but it comes up "error null"???
So now I wipe the sd manually and then do the reset and it works, ok, I re load everything on from scratch and all is good, but when I installed rom manager it says that clockwork recovery IS NOT installed again
Can anyone here work out from my ramblings WTF is going on???
I dont get why the font changer all of a sudden caused a boot loop, as I had changed font about 15 times with it without issue, also why clockwork recovery will not stick anymore after a reboot, when before it did and I have not changed a thing!
Cheers!!!
Rename install-recovery.sh in system/etc to something else, flash cwm recovery again, this time it'll stick until you install a stock rom again.
Rom manager is causing more problems than it's saving time, hence I don't use it.
Sent from my Nexus S using XDA App
Thanks for the reply, can you go into detail on what exactly I need to do to get clockwork to stick? I still hold noob status!
Thanks!
Also rom manager seems fine, I flashed loads of roms with it with no issue, I also rebooted a few time at least between flashes so I dont get why clockwork suddenly decided to jump ship.
It was the font changer that f&%ked it all up for me, or anim mod (which I wont touch now even tho I miss the wicked transitions).
When using Font Changer, it's better to do a reboot manually instead of selecting Reboot from within the program. That sometimes cause me a boot loop too. But after turning the phone off / on a.k.a. "reboot manually", the phone boots fine.
To elaborate what rentaric said, use Root Explorer and go to /system/etc/, there should be a file named install-recovery.sh. This file is responsible for flashing the stock recovery every time the phone boots. If you rename it to something else e.g. install-recovery.sh.bak then CWM will stick on reboot.
Thanks, but when I get into the /system/etc/ there is not file called install-recovery.sh.
The only .sh in there is init.goldfish.sh
Any ideas???
bump...............
Flash cwm rec and either stock or custom rom.
Stock rom incl the .sh you want.
Sent from my Nexus S using XDA App
I've read on these forums that using Clockwork on the I9023 is a no-go. Serves up incompatible ROMs, etc.
BTW, I'm looking to root my I9023. Can the OP please point me to the method he used.
athani said:
I've read on these forums that using Clockwork on the I9023 is a no-go. Serves up incompatible ROMs, etc.
BTW, I'm looking to root my I9023. Can the OP please point me to the method he used.
Click to expand...
Click to collapse
LINK: http://forum.xda-developers.com/showthread.php?t=1007782
Please read the whole thread, if I had it would have saved me half a night scratching my head...lol
rentaric said:
Flash cwm rec and either stock or custom rom.
Stock rom incl the .sh you want.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Yeah I have a custom rom installed, supercm7, but the install-recovery.sh. that I have been told is causing the problem of clockwork disappearing is not in the /system/etc/ folder, so I am asking if there is anything else that could be causing me to have to re flash clockwork via my pc every time I want to change rom?
I will tell you exactly what happens.
1. I go into rom manager
2. download a rom and choose flash rom from sd card
3. it asked if I want to wipe etc, i select yes
4. phone re boots and I get ! with an android
5. I pull the battery, hold volume up n power and boot / connect to my pc
6. re flash clockwork via SDK
7.the phone then load the new rom on its own
Before it would just flash the rom without me having to install clockwork again.
install-recovery.sh is only there if you're using a stock android rom.
"so I am asking if there is anything else that could be causing me to have to re flash clockwork via my pc every time I want to change rom?"
ROM Manager.
It's not a reliable working tool for ME as I'm changing ROMs/kernels on a regular basis and it might not work reliable the one time you need it.
Thanks for that, I may just sack rom manager then.
Its a shame as I flashed several roms with it without issue.
Oh well, loving this supercm7 so gonna stick with it untill an update comes out.
Many thanks to all who have replied, clicking the thanks buttons now!
I had the same problem but i installed a previus recovery and works fine formeforme
Sent from my Nexus S 4G using XDA Premium App

[Q] TF101G back to stock rom.

Hi guys,
I've been thinkin about selling my TF101g and buy a new model, but my tablet has custom recovery and Rom, and I would like turn it all stock, and i couldn't find any thread to the Tf101g.
Can somebody help me with a thread that works?
lennao said:
Hi guys,
I've been thinkin about selling my TF101g and buy a new model, but my tablet has custom recovery and Rom, and I would like turn it all stock, and i couldn't find any thread to the Tf101g.
Can somebody help me with a thread that works?
Click to expand...
Click to collapse
Hi, I'm new to this forum (first post).
I had the same problem - e.g. I wanted to return to stock. I flashed ' PERI 1-click recovery' and the latest version of Revolver custom ROM for the TF101G but I couldn't get 3G to work (unknown Baseband), and PERI wouldn't let me flash the stock ROM - it gave an error 'assert failed' 'Status 7'.
Thought I'd b*****d it thoroughly and couldn't find a thread telling me how to get back to Stock, but trial and error prevailed.
This is what I did (assume you already have ROOT and a custom recovery installed):
1. Download the latest ASUS stock ROM zip from the ASUS site to the PC. Make sure you select the right one for your model (mine's the WW TF101G version)
http://support.asus.com/Download.aspx?SLanguage=en&m=Eee+Pad+Transformer+TF101G&p=20&s=16
2. For some reason ASUS put the stock ROM zip image inside another zip file, so extract it from the downloaded zip file and copy the extracted stock ROM zip (e.g. WW_epad-user-9.2.2.6.zip) to TF101G Internal Storage (not an external SD)
3. The custom recovery you have installed my allow you to flash the stock ROM, in which case just do steps 7 and then 10 onwards. Mine (PERI) gave me an Assert Failed error, in which case ....
4. Download ClockWork Recovery for the Transformer. I used Clockwork_Recovery_5.8.1.8_by_JvS_Corp_V3 from this site and it worked just fine. I don't know which other versions work and which don't:
http://forum.xda-developers.com/showthread.php?t=1577929
5. Copy the downloaded Clockwork_Recovery_5.8.1.8_by_JvS_Corp_V3.zip to TF101G Internal Storage (not external SD)
6. Now boot the TF101G into recovery mode (Power + Volume Down until prompt appears, then Volume Up for recovery)
7. Wipe all caches (including the user data cache)
8. Flash Clockwork_Recovery_5.8.1.8_by_JvS_Corp_V3.zip - you'll see lots of scrolling @@@@@@@s, don't worry that's normal
9. Once the Install is complete, Boot into recovery mode again - you should now be in Clockwork Recovery V5.8.1.8
10. Flash the stock ROM (e.g. WW_epad-user-9.2.2.6.zip). Wait until the install is complete.
11. Reboot normally. You will see a blue status bar which will take a while to complete and then it will reboot itself, you may see a message 'Android is Updating' which will also take a while to complete.
After doing this, you should now have the stock ROM, stock recovery, no ROOT and you will be asked to set up the Tablet for the first time, i.e. back to stock.
P.S. If you don't wipe the User Data cache, you can flash to stock without using your apps / settings / data.
Hope this helps.
i dont understand. If youre going to sell the tf101 why not load it up with custom overclockable kernel, new JB rom, and a custom touch recovery? those are added features compared to a lame stock version of the transformer.
serafis said:
Hi, I'm new to this forum (first post).
I had the same problem - e.g. I wanted to return to stock. I flashed ' PERI 1-click recovery' and the latest version of Revolver custom ROM for the TF101G but I couldn't get 3G to work (unknown Baseband), and PERI wouldn't let me flash the stock ROM - it gave an error 'assert failed' 'Status 7'.
Thought I'd b*****d it thoroughly and couldn't find a thread telling me how to get back to Stock, but trial and error prevailed.
This is what I did (assume you already have ROOT and a custom recovery installed):
1. Download the latest ASUS stock ROM zip from the ASUS site to the PC. Make sure you select the right one for your model (mine's the WW TF101G version)
http://support.asus.com/Download.aspx?SLanguage=en&m=Eee+Pad+Transformer+TF101G&p=20&s=16
2. For some reason ASUS put the stock ROM zip image inside another zip file, so extract it from the downloaded zip file and copy the extracted stock ROM zip (e.g. WW_epad-user-9.2.2.6.zip) to TF101G Internal Storage (not an external SD)
3. The custom recovery you have installed my allow you to flash the stock ROM, in which case just do steps 7 and then 10 onwards. Mine (PERI) gave me an Assert Failed error, in which case ....
4. Download ClockWork Recovery for the Transformer. I used Clockwork_Recovery_5.8.1.8_by_JvS_Corp_V3 from this site and it worked just fine. I don't know which other versions work and which don't:
http://forum.xda-developers.com/showthread.php?t=1577929
5. Copy the downloaded Clockwork_Recovery_5.8.1.8_by_JvS_Corp_V3.zip to TF101G Internal Storage (not external SD)
6. Now boot the TF101G into recovery mode (Power + Volume Down until prompt appears, then Volume Up for recovery)
7. Wipe all caches (including the user data cache)
8. Flash Clockwork_Recovery_5.8.1.8_by_JvS_Corp_V3.zip - you'll see lots of scrolling @@@@@@@s, don't worry that's normal
9. Once the Install is complete, Boot into recovery mode again - you should now be in Clockwork Recovery V5.8.1.8
10. Flash the stock ROM (e.g. WW_epad-user-9.2.2.6.zip). Wait until the install is complete.
11. Reboot normally. You will see a blue status bar which will take a while to complete and then it will reboot itself, you may see a message 'Android is Updating' which will also take a while to complete.
After doing this, you should now have the stock ROM, stock recovery, no ROOT and you will be asked to set up the Tablet for the first time, i.e. back to stock.
P.S. If you don't wipe the User Data cache, you can flash to stock without using your apps / settings / data.
Hope this helps.
Click to expand...
Click to collapse
thx man, i'll try this at home tonight!!
haxin said:
i dont understand. If youre going to sell the tf101 why not load it up with custom overclockable kernel, new JB rom, and a custom touch recovery? those are added features compared to a lame stock version of the transformer.
Click to expand...
Click to collapse
because it doesn't exist a JB ROM with 3G working, and usually, when i'll sell something, i prefer selling with the stock image, it's more guarantee that will work properly, like when leaving the store, so they can root and change roms themselves.
lennao said:
thx man, i'll try this at home tonight!!
Click to expand...
Click to collapse
In my post, where I said "P.S. If you don't wipe the User Data cache, you can flash to stock without using your apps / settings / data", I meant "...without losing your apps / settings / data". That way you can carry on using it until you sell it, and then just do a factory reset once you have a buyer.
Good luck.
serafis said:
In my post, where I said "P.S. If you don't wipe the User Data cache, you can flash to stock without using your apps / settings / data", I meant "...without losing your apps / settings / data".
Good luck.
Click to expand...
Click to collapse
hey,
i would like to thank you, your tutorial works fine! and was pretty easy too, nothing complicated.
thx again!
lennao said:
hey,
i would like to thank you, your tutorial works fine! and was pretty easy too, nothing complicated.
thx again!
Click to expand...
Click to collapse
Excellent, glad it worked out.

[Q] Semi-bricked tf300t

I'll preface this by saying the following:
I know there are a lot of brick guides out there, and most are relatively easy to get out of. I've worked myself into a bit of a pickle, though.
It started when I noticed that there was an update available through the CM updater. I figured, what the hell, I'm running a nightly and this is likely to be a stable release, so I went ahead and downloaded it. I got home and checked the get.cm page, and sure enough, a new, stable build had recently been released. Being the diligent soul that I am, I made sure to do a full backup before I installed the .zip. Everything worked out just fine, the backup went swell, the update finished without problems, and then I rebooted my device.
All I see is the Asus splash screen. It just stays there. So I think, no big deal, it just didn't work out like I wanted, I'll go format my data (which I didn't do the first time around, in hopes that everything would carry over) and install again. The same thing happens. I haven't started panicking yet, since I still have 3 backups (1 older Jellybean, and one much older ICS). None of them work. I wipe everything that I can think might help. Data, system, cache, dalvik, you name it. Nothing was working, and I was starting to freak out. Then I decided to try to get some action through fastboot, hoping that I could push a .zip that wasn't the CM10 update that had started everything. In my search for a push command, I thought it would be a good idea to try a wipe from fastboot. This wiped everything. Not only the system, boot, etc. partitions, but also my personal partition that had all of my data. This in itself isn't a big problem, but it also left the partitions unformatted. Now I have a device that is devoid of data and can't do anything but get into CWM and fastboot.
What the hell can I do? Am I doomed? Is there no way to get out of the hole I've dug myself into?
tl;dr failed update, things got really real, really fast.
Specs before the initial update
ROM: CM10 nightly, Jellybean 4.1.x
CWM: 5.5.0.4
Kernel Version (?): 9.4.3.30-20120604 (I'm not sure with this, it says something about "android carhu-user" before it)
same thing just happened to me. Im going to download another version of CM and try that. It might just be that.
DerangedLoofah said:
same thing just happened to me. Im going to download another version of CM and try that. It might just be that.
Click to expand...
Click to collapse
That's the thing, though, I have no idea how I'm supposed to get it to my device now...
http://forum.xda-developers.com/showthread.php?t=1989076
Have you tried this? I was just thinking about it because I can't reflash my recovery and thought this may be the way to start over.
OK I downloaded the us jb update and extracted to my external SD card and flashed it in recovery after wipes. Everything is good now.
Edit: flash recovery in fast boot.
Sent from my SCH-I535 using Tapatalk 2
Glad you got it!
nitsuj79 said:
Glad you got it!
Click to expand...
Click to collapse
DerangedLoofah managed to get it, but I still haven't had any luck.
DerangedLoofah said:
OK I downloaded the us jb update and extracted to my external SD card and flashed it in recovery after wipes. Everything is good now.
Edit: flash recovery in fast boot.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
How did you flash it in fastboot? I can't figure out how to get to something that's on the external SD card. What were the exact commands you used?
1. Download any software from this topic http://forum.xda-developers.com/show....php?t=1697227
2. Unpack it one so you have a zip without UpdateLauncher
3. Rename the zip to EP201_768_SDUPDATE.zip
4. Put on a sdcard into the root (the sdcard should be clean, no other files)
5. Boot you tablet to RCK (Volume down + power, then volume up)
6. Let the magic begin!!! Take some minutes.
Attention! JB user pleas choose a JB ROM, don't flash ICS ROM on JB bootloader.
You tried this method with no love? I was able to flash stock pretty easily doing this.
nitsuj79 said:
1. Download any software from this topic http://forum.xda-developers.com/show....php?t=1697227
2. Unpack it one so you have a zip without UpdateLauncher
3. Rename the zip to EP201_768_SDUPDATE.zip
4. Put on a sdcard into the root (the sdcard should be clean, no other files)
5. Boot you tablet to RCK (Volume down + power, then volume up)
6. Let the magic begin!!! Take some minutes.
Attention! JB user pleas choose a JB ROM, don't flash ICS ROM on JB bootloader.
You tried this method with no love? I was able to flash stock pretty easily doing this.
Click to expand...
Click to collapse
Does that work with CWM? I don't have the stock bootloader on it.
This works only if you didn't flash custom recovery, it is the best method for locked devices. But you can still flash any stock ROM from CWM (but I suggest to use TWRP, you can install it from external sd). And you can push the ROM to internal memory via adb. I think you can install stock ROM via fastboot too, I am not sure, but the command fastboot update should help.
I managed to get it working again. If you can get to fastboot, push a bootloader that supports an external SD cards (like TWRP) and then from that install one of the official ASUS firmwares. From there, you have to root again, but it's better than having a device that won't boot at all.

[Q] Install ClockworkMod persistently

Hi,
I downloaded and flashed my S2 with this firmware:
http://forum.xda-developers.com/showthread.php?t=1996714
Works very well. But I would like to have a better ClockworkMod Recovery. So I downloaded CWM Touch 5.8.1.5 (and also the "regular" CWM 4.0.1.5 as an alternative). I started the phone into recovery mode and used "apply zip". It says "replacing stock recovery", and the CWM Touch shows up with all functions working like a charm.
But next time I reboot the phone into recovery, the old recovery mode is present again. Same happens with the other CWM (4.0.1.5). It's like the installation is not done persistently on the partition but just temporarily into RAM ...
If I use the ROM Manager app to install one of the two CWMs, the app accepts the zip file, reboots the phone - but like before, the old recovery is still there. And it doesn't make a difference whether I select "wipe cache/data" and/or "wipe dalvik" prior to installation or not.
Is there a way of persistently installing this (or maybe a different) CWM?! Does it depend on the specific kernel that is in place with the firmware? Does said firmware and its kernel prevent installing a different CWM?
Regards,
Mac
Found a CWM6 here
http://forum.xda-developers.com/showthread.php?t=1877270
Works alright and can be installed permanently.
Mac
The cwm of kernel doesn't allow another cwm to be installed!
Unless you're on stock kernel,I think this won't be possible!
But there should be a way out!!
Sent from my MT11i using Tapatalk 2
Ghostfreak NB said:
The cwm of kernel doesn't allow another cwm to be installed!
Click to expand...
Click to collapse
Well, obviously it does. Said CWM 6 can be installed via Odin. I did not try CWM installation. This indeed may not work.
Mac

took out the tf101 after about a year or so

hey guys, ill get straight to the point:
i decided to take out my old tf101(non-3g) after after a year or more, dont remember. it works relatively well, but im sure theres a lot that can be updated rom-wise. right now it has this:
Kernel version
2.6.39.4-JELLYBEAN-g18e8917-dirty [email protected] #89 SMP PREEMPT Wed Aug 22 17:40:05 CEST 2012
Build number
full_tf101-userdebug 4.1.1 MASTER eng. RaymanFX.20120821.232608 test-keys
I include this because I'm not exactly sure what version i have.. i think its the 6.0.0 from raymanfx
Anyway, from what I could from a quick glance of these forums, there's a ton of new features for this tablet! or at least one i really like, multi-window.
So can I get some suggestions from you guys on whats the best way to get my tablet up to date? I'm looking for a stable rom also. Is the best way to get to this point to return my tablet to stock and start over from there?
Any useful suggestions are welcomed. Thanks
First thing you should do is make sure you have TWRP recovery installed
Make sure if you have CWM recovery installed that you change over to TWRP before flashing the ROM or you have a good chance of a boot loop
Easiest method, install Goo Manager from here
https://play.google.com/store/apps/details?id=com.s0up.goomanager
Open app > Hit the top right 3 dots menu button > choose "Install Open RecoveryScript"
Follow instructions to get TWRP running, boot into TWRP to check it has worked by holding Power & Volume Down from a powered off state until you see the white text at the top of the screen
Then release all buttons and tap volume up to enter recovery
If that works fine, then download a new ROM and Gapps and copy to a Micro SD Card
This is the latest and most stable version that has Multi Window support
http://forum.xda-developers.com/showthread.php?t=2392087
Copy the ROM & Gapps to Micro SD and stick it in the TF
Boot into TWRP
Press the WIPE option and wipe everything apart from External which is where your new ROM is
Go back to the main screen by hitting the home button at the top right
Press the install button
Choose External memory to find your new ROM and Gapps
Install ROM
Install Gapps
Wipe Cache & Dalvik Cache
Press reboot to Reboot into your new 4.3.1 Jellybean ROM with Multi Window
----
If you have problems getting TWRP using Goo Manager, use EasyFlasher
http://forum.xda-developers.com/showthread.php?t=1688012
roadrunnerx7 said:
Anyway, from what I could from a quick glance of these forums, there's a ton of new features for this tablet! or at least one i really like, multi-window.
Click to expand...
Click to collapse
Because you want Multi-Window, go with the previously mentioned KatKiss 4.3.1 or, if you can wait a few days, go for 4.4.2 v023. Tim's changelog indicates the next version is going to fix it.
4.4.2 really flies, BTW!
*Detection* said:
.
Click to expand...
Click to collapse
Thank you very much for the thorough explanation. When I get a chance I'll get started on updating things. Thanks!!
DoughMucker said:
Because you want Multi-Window, go with the previously mentioned KatKiss 4.3.1 or, if you can wait a few days, go for 4.4.2 v023. Tim's changelog indicates the next version is going to fix it.
4.4.2 really flies, BTW!
Click to expand...
Click to collapse
Thanks for the suggestion. Why is 4.4.2 v023 better though?
roadrunnerx7 said:
Thanks for the suggestion. Why is 4.4.2 v023 better though?
Click to expand...
Click to collapse
Android 4.4 (Kit Kat) runs much better on lower powered/memory devices than previous versions. The possible downside of KatKiss 4.4.2 compared with KatKiss 4.3.1 is that it is relatively new and may have some issues with some apps (i haven't seen any though).
So I followed all the steps and updated my tablet. Installed the 4.4.2 version. It's awesome!!! I never imagined this tablet would still have so much value in it.
Thanks again guy for helping me out!
Great!
Yea the latest 4.4.2 #23 is a superb ROM, best one so far imo & multiwindow is in this one too
I just bought my wife a used TF300T running stock 4.2.1 and, after rooting and using lagfix, it doesn't seem any faster than my TF101 running KatKiss 4.4.2. Maybe I should have bought another TF101 and saved a few bucks.
DoughMucker said:
I just bought my wife a used TF300T running stock 4.2.1 and, after rooting and using lagfix, it doesn't seem any faster than my TF101 running KatKiss 4.4.2. Maybe I should have bought another TF101 and saved a few bucks.
Click to expand...
Click to collapse
Run a few benchmarks like 3DMark and Antutu on each of them
*Detection* said:
Run a few benchmarks like 3DMark and Antutu on each of them
Click to expand...
Click to collapse
I ran Antutu on each...
TF101 (@1400MHz) got 10113. TF300T got 13444. But they feel pretty much the same for the basic stuff my wife and I do with the tablets.
I'm having problems with Netflix.. A lot of times it hang.. Not loading, but the picture. The video will seemingly stop playing and get stuck, but the sound continues and the playback timer continues also. Only the video gets stuck. The only thing that will temp fix it is to close the app and open again, but even then there's a 50/50 chance it will screw up again. And if I move to a specific spot in the video, so that it has to sort of reload it, it will likely get stuck again.
You guys have any problems like this with Netflix? Solutions?
I'm still on v23.. I see there's a v23c now but not sure if that's a newer version?
Instructions for issues are in post 2 of the main ROM thread
http://forum.xda-developers.com/showpost.php?p=49007034&postcount=2
--
Netflix
To get the latest Netflix versions to work you can use this XPosed module:
http://forum.xda-developers.com/showthread.php?t=2101525
You can also use an older version of Netflix ( 2.0..)
roadrunnerx7 said:
I'm still on v23.. I see there's a v23c now but not sure if that's a newer version?
Click to expand...
Click to collapse
23c just adds support for some international keyboards - they're otherwise the same.
*Detection* said:
Instructions for issues are in post 2 of the main ROM thread
http://forum.xda-developers.com/showpost.php?p=49007034&postcount=2
--
Netflix
To get the latest Netflix versions to work you can use this XPosed module:
http://forum.xda-developers.com/showthread.php?t=2101525
You can also use an older version of Netflix ( 2.0..)
Click to expand...
Click to collapse
I did the netflix fix before already. Thats why im not sure what to do to fix it. Havent tried getting an older version. Do you know where i can get an older version of netflix? Also if i do use the older, can i uninstall the Xposed module?
Thanks
*Detection* said:
First thing you should do is make sure you have TWRP recovery installed
Make sure if you have CWM recovery installed that you change over to TWRP before flashing the ROM or you have a good chance of a boot loop
Easiest method, install Goo Manager from here
https://play.google.com/store/apps/details?id=com.s0up.goomanager
Open app > Hit the top right 3 dots menu button > choose "Install Open RecoveryScript"
Follow instructions to get TWRP running, boot into TWRP to check it has worked by holding Power & Volume Down from a powered off state until you see the white text at the top of the screen
Then release all buttons and tap volume up to enter recovery
If that works fine, then download a new ROM and Gapps and copy to a Micro SD Card
This is the latest and most stable version that has Multi Window support
http://forum.xda-developers.com/showthread.php?t=2392087
Copy the ROM & Gapps to Micro SD and stick it in the TF
Boot into TWRP
Press the WIPE option and wipe everything apart from External which is where your new ROM is
Go back to the main screen by hitting the home button at the top right
Press the install button
Choose External memory to find your new ROM and Gapps
Install ROM
Install Gapps
Wipe Cache & Dalvik Cache
Press reboot to Reboot into your new 4.3.1 Jellybean ROM with Multi Window
----
If you have problems getting TWRP using Goo Manager, use EasyFlasher
http://forum.xda-developers.com/showthread.php?t=1688012
Click to expand...
Click to collapse
Hi
Sorry to revive an old thread
I am in the same boat. I have a B40 tablet.
I followed the steps up till install ROM.
When I install, it is stuck at "updating partition detail".
I have tried to flash newest twrp without success ( cannot even get into recovery)
I have tried easyflasher to unbrick, flash twrp 2.2.1, flash twrp 2.3.2.3 using GOOmanager, but still stuck at "updating partition detail" when flash katkiss 4.4.2v23c.
I have tried different micro-sd cards and different downloads.
What may have gone wrong?
Thanks
strikeraj said:
Hi
Sorry to revive an old thread
I am in the same boat. I have a B40 tablet.
I followed the steps up till install ROM.
When I install, it is stuck at "updating partition detail".
I have tried to flash newest twrp without success ( cannot even get into recovery)
I have tried easyflasher to unbrick, flash twrp 2.2.1, flash twrp 2.3.2.3 using GOOmanager, but still stuck at "updating partition detail" when flash katkiss 4.4.2v23c.
I have tried different micro-sd cards and different downloads.
What may have gone wrong?
Thanks
Click to expand...
Click to collapse
Does it not flash the ROM first, then stop at "Updating Partition Details" ?
Are you sure it hasn't successfully flashed the ROM?
iirc Updating Partition Details is the last thing it says after flashing
*Detection* said:
Does it not flash the ROM first, then stop at "Updating Partition Details" ?
Are you sure it hasn't successfully flashed the ROM?
iirc Updating Partition Details is the last thing it says after flashing
Click to expand...
Click to collapse
Sadly not.
When I swipe to flash, that is the first and only line that pops up immediately.
If I let it sit at that line for the night, in the morning I see TWRP going back to home screen. But the log still only has that one line.
strikeraj said:
Sadly not.
When I swipe to flash, that is the first and only line that pops up immediately.
If I let it sit at that line for the night, in the morning I see TWRP going back to home screen. But the log still only has that one line.
Click to expand...
Click to collapse
Ok, try NVFLASH'ing the Stock ROM
NVFLASH will delete and re-create all the partitions on the device and then flash you back to 100% factory stock
Once you are up and running with stock, use Easyflasher to flash TWRP recovery again, then try flashing KatKiss ROM again from TWRP
Download > Extract > Plug TF into PC USB > Power off TF and Put TF into APX Mode (Vol Up & Power) > Run download.bat as Administrator
Download
https://mega.co.nz/#!tINBhLob!InI_F2Y6D8rSVZ5sDeCQx2T41c9gp_7Z_7kCqFNDVIs
*Detection* said:
Ok, try NVFLASH'ing the Stock ROM
NVFLASH will delete and re-create all the partitions on the device and then flash you back to 100% factory stock
Once you are up and running with stock, use Easyflasher to flash TWRP recovery again, then try flashing KatKiss ROM again from TWRP
Download > Extract > Plug TF into PC USB > Power off TF and Put TF into APX Mode (Vol Up & Power) > Run download.bat as Administrator
Download
https://mega.co.nz/#!tINBhLob!InI_F2Y6D8rSVZ5sDeCQx2T41c9gp_7Z_7kCqFNDVIs
Click to expand...
Click to collapse
Thanks for your reply.
Just a couple questions
1. I have used easyflasher to flash stock before flashing twrp and katkiss. Is that the same as using NVFLASH? Or should I not wipe everything before flashing katkiss so that the partition is not touched? If so, what should I wipe before flashing?
2. I thought katkiss requires twrp >=2.3.2.3 . Easyflasher flashes a version lower than that. Am I correct to use goomanager under stock rom to update twrp to 2.3.2.3 before flashing katkiss?
3. If I want to try flashing katkiss from internal memory, where should I put the zip file and what should I not wipe before flashing?
Thanks
strikeraj said:
Thanks for your reply.
Just a couple questions
1. I have used easyflasher to flash stock before flashing twrp and katkiss. Is that the same as using NVFLASH? Or should I not wipe everything before flashing katkiss so that the partition is not touched? If so, what should I wipe before flashing?
2. I thought katkiss requires twrp >=2.3.2.3 . Easyflasher flashes a version lower than that. Am I correct to use goomanager under stock rom to update twrp to 2.3.2.3 before flashing katkiss?
3. If I want to try flashing katkiss from internal memory, where should I put the zip file and what should I not wipe before flashing?
Thanks
Click to expand...
Click to collapse
1.) Use NVFLASH to flash stock - Wipe everything in TWRP once you're ready for KatKiss
2.) TWRP that comes with Easyflasher will work, you can upgrade later
3.)Flash KatKiss from MicroSD so you can wipe everything on Internal

Categories

Resources