Hi guys,
I wanted to post that in the relevant topic on the dev forum but as I don't have 10 messages I can't.
Anyway it's just to let you know that I've flashed cocore 5.6.2 on a 9070p. As to now everything but USB mass storage write access on the internal SD works. Mass storage is ok on external SD (r/w) though.
Antutu scores 6883 and the phone feels much more responsive than before.
The upgrade path I followed was:
1/ install german XXLPD rom from sammobile using Odin
2/ root it using Shaaan's method http://forum.xda-developers.com/showthread.php?t=2087424
3/ install deodexed rom from Agadoo http://forum.xda-developers.com/showthread.php?t=2239129
4/ install Cocore 5.6.2 using the dd method http://forum.xda-developers.com/showthread.php?t=2140597
not booting
hi. Can u give us a exact steps how to flash 9070 non P version cocore kernel 5.6.2,
because i just got my phone not booting.
Fortunately i revived it by flashing original kernel with odin.
Running for a couple of days now, phone feels more stable & responsive than stock JB Kernel
I flashed cocore 5.6.2.w/CWM recovery to 9070P using Universal Kernel Flasher by frapeti and it works OK.
maybe sth went wrong - just try again
when trying to flash kernel with universal kernel flash, i get error incompatile device. Is it still safe to flash it ?
wikmanipoiss said:
when trying to flash kernel with universal kernel flash, i get error incompatile device. Is it still safe to flash it ?
Click to expand...
Click to collapse
upgrade to the latest version of UKF - the older ones didn't recognize i9070P as compatible device
if the latest one is version 1.10 then i have it. But still error incompatile device
well, idk what's the problem - maybe it relies on some tricky build.prop entry to tell if it's compatible or not
try flashing via temp recovery or via terminal emulator then.
just flashed it through cwm. Got it working
I've now been using the phone on a daily basis for five days since my original post. Lots of SMS, some data over Wifi (web+email) and a few calls, it seems pretty stable I had no reboot or high CPU usage and the phone is still very responsive.
So, fwiw I definitely recommend this setup.
Hey guys. I'm still a newbie in android, but which cocore should I download? Twrp or CWM? and can I istall in via universal?
Related
Hi everyone.
I'm thinking of installing the FITDroid v3.2 ROM on my FIT (Have 2.3.4 Stock Rom with Root) but I have a question:
In the topic it says the I shoud flash it on the DEODEXED XXKPL ROM FIRMWARE (for better performance), my question is if I can install it since my phone has the XXKPG FIRMWARE.
I read the topic and one user recommended to another to update to XXKPL using Kies but I tried and it said that my phone can't update using Kies.
TugaSonic said:
Hi everyone.
I'm thinking of installing the FITDroid v3.2 ROM on my FIT (Have 2.3.4 Stock Rom with Root) but I have a question:
In the topic it says the I shoud flash it on the DEODEXED XXKPL ROM FIRMWARE (for better performance), my question is if I can install it since my phone has the XXKPG FIRMWARE.
I read the topic and one user recommended to another to update to XXKPL using Kies but I tried and it said that my phone can't update using Kies.
Click to expand...
Click to collapse
I think you have to flash original ROM (Froyo 2.1 perhaps??) AND unroot it to update with KIES.
THEN install Fitdroid v3.2
The Matter is the modified appearance to KIES.
Trie it this way: click
TugaSonic said:
Hi everyone.
I'm thinking of installing the FITDroid v3.2 ROM on my FIT (Have 2.3.4 Stock Rom with Root) but I have a question:
In the topic it says the I shoud flash it on the DEODEXED XXKPL ROM FIRMWARE (for better performance), my question is if I can install it since my phone has the XXKPG FIRMWARE.
I read the topic and one user recommended to another to update to XXKPL using Kies but I tried and it said that my phone can't update using Kies.
Click to expand...
Click to collapse
u can install it on any firmware without any prob..... Go on try it...... dont worry....
vishwanathptl said:
u can install it on any firmware without any prob..... Go on try it...... dont worry....
Click to expand...
Click to collapse
Thank's already installed the firmware.
But have another question, on the instructions to install FITDroid it says to use CWM Recovery (which I had before), but the firmware changed the recovery to another (I think it's the original) so my question is if I can install without CWM Recovery and how do I install CWM (the tutorials I found always replace the firmware).
TugaSonic said:
Thank's already installed the firmware.
But have another question, on the instructions to install FITDroid it says to use CWM Recovery (which I had before), but the firmware changed the recovery to another (I think it's the original) so my question is if I can install without CWM Recovery and how do I install CWM (the tutorials I found always replace the firmware).
Click to expand...
Click to collapse
No you cannot install custom ROM such as Fitdroid using the orginal recovery
First install the CWM using odin(You can Do this only if you have 2.3.x it will not work on froyo!)
and then flash the ROM
OK. Already installed CWM and FITDroid.
Just have one question about FITDroid, can I use SetCPU instead of No-Frills CPU Controller to change the frequencies (since SetCPU allows to create profiles)?
TugaSonic said:
OK. Already installed CWM and FITDroid.
Just have one question about FITDroid, can I use SetCPU instead of No-Frills CPU Controller to change the frequencies (since SetCPU allows to create profiles)?
Click to expand...
Click to collapse
Yes you can use SetCPU also
But No frills allows to change I/O scheduler also which is not available in SetCPU
OK, one last thing I just have a problems with FITDroid, whice is sometimes the wireless doen't work properly.
It says that it's connected to my router but when I try to use a brownser, market, etc. it says that there isn't a connection and the only way I found to fix that is to reboot (Which fixes the problem temporarily since after a few hours the same happens). Does anyone know how to fix it or is it a bug on the ROM?
same problem for wifi ..its quite buggy i had experienced too much bug in fitdroid..took me days on flash and reflash , reboot
TugaSonic said:
OK, one last thing I just have a problems with FITDroid, whice is sometimes the wireless doen't work properly.
It says that it's connected to my router but when I try to use a brownser, market, etc. it says that there isn't a connection and the only way I found to fix that is to reboot (Which fixes the problem temporarily since after a few hours the same happens). Does anyone know how to fix it or is it a bug on the ROM?
Click to expand...
Click to collapse
which version of fitdroid do u use... cause they latest updated version doesnt hav any problems with it...
wilfredcool007 said:
which version of fitdroid do u use... cause they latest updated version doesnt hav any problems with it...
Click to expand...
Click to collapse
I'm using the latest v3.2.
Hello!
I just got a pretty good deal on a stock Froyo Infuse 4G, so I bought it.
A little help please! I would love to have the stock ATT rom with the ability to overclock the processor. This is was I have done so far.. plrease don't be so hard on me since this is my first non-HTC device lol.
So the first thing I did was install a "leaked" Gingerbread ATT stock rom using a program called Odin. Then, I root it using that Superoneclick software... I actually clicked a million times instead trying to get it working because I had GingerBread instead of Froyo ... but somehow managed to do it, it is properly rooted and well tested. So! now with my rooted device, I downloaded Rom Manager from the market, flashed it succesfully (at least that's what the screen said)... and when trying to boot into CWM Recovery I got the following errors:
verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
installation aborted.
I tried to flash it via RomManager several times, also did it via SD-Card renaming it to Update.zip and flashing it with the stock recovery.. same error. I searched for more information, someone in the forum said the reason could be an incompatible Kernel, so I flashed the Community V8 Kernel... and my device didn't boot past the Samsung screen... but somehow if I tried manaully to get into CWM recovery, it worked! (just the recovery). Flashed a custom rom that I didn't like... then suddenly I lost the CWM Recovery and cannot then bricked it and was unable to flash it again..
I managed to restore the phone to ATT factory condition using a guide here on Xda (this time the phone kept the leaked GB rom)... then rooted it again and haven't done anything else. Mu question is:
How can I keep this stock rom with the ability to overclock the processor? (flashing different kernels just makes it freeze on boot at Samsung logo).
Thanks for your help!::
here a good start by me:
http://forum.xda-developers.com/showthread.php?t=1437548
Thanks, it is a useful link but I still don't find the answer to my question (or maybe I just don't undertand it).
I am beyond frustration... could anyone please tell me what to do to step by step to flash an overclockable Kernel keeping my GingerBread stock ATT rom? like if you were explaining it to a retarded person?
many thanks...
domenicostorino said:
Thanks, it is a useful link but I still don't find the answer to my question (or maybe I just don't undertand it).
I am beyond frustration... could anyone please tell me what to do to step by step to flash an overclockable Kernel keeping my GingerBread stock ATT rom? like if you were explaining it to a retarded person?
many thanks...
Click to expand...
Click to collapse
1. You need to restore you phone back to stock using gtg's unbrick or heimdall 1 click. (See my post)
2. ATT's GB latest is not rootable thru SOC. You can use odin to flash an insecure kernel (http://forum.xda-developers.com/showthread.php?t=1212485) but you will also need to update superuser binaries and busybox as well. Running the insecure kernel for OC, you will lose the video recorder and video player.
It doesn't sound like you can understand enough yet to do this.
3. If you want a stock att and rooted, go to the dev section:
check out zeus stock 5.2, vagabond or victory. These are GB stock base roms with root already done. There is also dman's deodexed, rooted gb uclb3 already with oc kernel...no video
qkster said:
1. You need to restore you phone back to stock using gtg's unbrick or heimdall 1 click. (See my post)
2. ATT's GB latest is not rootable thru SOC. You can use odin to flash an insecure kernel (http://forum.xda-developers.com/showthread.php?t=1212485) but you will also need to update superuser binaries and busybox as well. Running the insecure kernel for OC, you will lose the video recorder and video player.
It doesn't sound like you can understand enough yet to do this.
3. If you want a stock att and rooted, go to the dev section:
check out zeus stock 5.2, vagabond or victory. These are GB stock base roms with root already done. There is also dman's deodexed, rooted gb uclb3 already with oc kernel...no video
Click to expand...
Click to collapse
Thanks for the info!
The first step has been done, restored the phone using Heimdall one click after bricking it, the phone was restored with a UCKJ4 2.36 GingerBread stock ATT rom (Kernel 2.6.35.7-I997uckj4-cl694350) and I am also rooted using SuperOneClick.
I don't fully understand step two, will try it once I get some more knowledge.
Question about the third step... does HDMI work in any of those custom stock roms? I use HDMI a lot.
domenicostorino said:
Thanks for the info!
The first step has been done, restored the phone using Heimdall one click after bricking it, the phone was restored with a UCKJ4 2.36 GingerBread stock ATT rom (Kernel 2.6.35.7-I997uckj4-cl694350) and I am also rooted using SuperOneClick.
I don't fully understand step two, will try it once I get some more knowledge.
Question about the third step... does HDMI work in any of those custom stock roms? I use HDMI a lot.
Click to expand...
Click to collapse
My Vagabond ROM runs the stock kernel if you follow directions.
HDMI will work. Battery is excellent. Feel free to check it out
qkster said:
My Vagabond ROM runs the stock kernel if you follow directions.
HDMI will work. Battery is excellent. Feel free to check it out
Click to expand...
Click to collapse
Thanks, but is it overclockable?
domenicostorino said:
Thanks, but is it overclockable?
Click to expand...
Click to collapse
you cant have your cake and eat it too.
stock kernel = HDMI. no oc
oc = no HDMI, and currently, no video on some rom
New to xda, so I'll just let you in everything in the last 2 hours. I flashed Bugless Beast (2002-06-09), wiping cache and dalvik cache and it ran fine. Then I installed the Matr1x bfs v22.5 from bootloader and rebooted once more. After that, it stayed on the Google screen until I removed the battery. So far the only possible solution that I've looked into is this thread called [HOW TO] Return to Stock Using Odin (VZW and GSM) -- you can google the link to see what I'm talking about. I can't seem to get the process to succeed. The attempts always end up as successful: 0 failed: 0 I tried using both the VZW from the first link given and the GSM: CF_ODIN_YAKJU_IMM76D_full for the PDA button on Odin. Nothing comes up on Odin when I mount the phone to the PC so I'm not sure if I'm even connecting, although I was able to connect the phone to the PC early today to transfer files. Could I be using incorrect files to start Odin? Am I connecting to Odin? Are there any other possibilities besides using Odin to return this phone to normal?
I was running early versions of Bugless Beast and Matr1x before flashing the new versions. Please, I need to get this phone fixed before this weekend. Thanks, in advance.
itsTnTg said:
New to xda, so I'll just let you in everything in the last 2 hours. I flashed Bugless Beast (2002-06-09), wiping cache and dalvik cache and it ran fine. Then I installed the Matr1x bfs v22.5 from bootloader and rebooted once more. After that, it stayed on the Google screen until I removed the battery. So far the only possible solution that I've looked into is this thread called [HOW TO] Return to Stock Using Odin (VZW and GSM) -- you can google the link to see what I'm talking about. I can't seem to get the process to succeed. The attempts always end up as successful: 0 failed: 0 I tried using both the VZW from the first link given and the GSM: CF_ODIN_YAKJU_IMM76D_full for the PDA button on Odin. Nothing comes up on Odin when I mount the phone to the PC so I'm not sure if I'm even connecting, although I was able to connect the phone to the PC early today to transfer files. Could I be using incorrect files to start Odin? Am I connecting to Odin? Are there any other possibilities besides using Odin to return this phone to normal?
I was running early versions of Bugless Beast and Matr1x before flashing the new versions. Please, I need to get this phone fixed before this weekend. Thanks, in advance.
Click to expand...
Click to collapse
you flash jelly bean kernel on ICS rom !(v.22.5 and higher are Jelly Bean, v.22.0 and lower are ICS)
you can boot on recovery ?
like leap said you flashed a JB kernel on a ICS ROM. Just download Matr1x v20 and flash it from the CWM recovery, it should boot right away. If not just go in CWM wipe factory reset and reflash Bugless Beast, or any other ROM, and the proper kernel (Matrix v20 for ICS, 20.5 for JB). Don't mess with Odin if you don't have experience or flash a wrong ROM stock into your Nexus, unless you want a nice paperweight.
Thanks
leap_ahead said:
you flash jelly bean kernel on ICS rom !(v.22.5 and higher are Jelly Bean, v.22.0 and lower are ICS)
you can boot on recovery ?
Click to expand...
Click to collapse
Wow, thanks! I run v. 22.0 and it works fine now.. I feel embarrassed of how simple it is to fix it.
Thanks
DeuXGod said:
like leap said you flashed a JB kernel on a ICS ROM. Just download Matr1x v20 and flash it from the CWM recovery, it should boot right away. If not just go in CWM wipe factory reset and reflash Bugless Beast, or any other ROM, and the proper kernel (Matrix v20 for ICS, 20.5 for JB). Don't mess with Odin if you don't have experience or flash a wrong ROM stock into your Nexus, unless you want a nice paperweight.
Click to expand...
Click to collapse
Thanks for the instructions! You saved me like a whole day of trying to fix this phone.
Hi All,
I am looking for a complete guide (or links to various parts) to install the new CM10.1 nightlies that started on 5/19/2013.
I've been looking through XDA and I see a lot of information that's dated for the 4.2.1 and earlier, but nothing that confirms these steps work for these new nightlies.
1. Unlock BL using ASUS v8? (I am on 4.2.1)
2. Root it (how, what procedure should I follow and which files)?
3. Which BL should I install? I've been using CWM on my GS3, but a lot of these guides use TWRP. which versions
4. This guide looks dated, please confirm
http://forum.xda-developers.com/showthread.php?t=2055430
5. Any recommendations for a better ROM? Or is the CM10.1 the best for this tablet?
6. Since I have the WIFI version of this, I am assuming I dont need to worries about the baseband updates that were recently required for the CM10.1 updates? If I am wrong, please advise.
Thanks for you help in advance!
snoopspecial said:
Hi All,
I am looking for a complete guide (on links to various parts) to install the new CM10.1 nightlies that started on 5/19/2013.
I've been looking through XDA and I see a lot of information thats dated for the 4.2.1 and earlier, but nothing that confirms these steps work for these new nightlies.
1. Unlock BL using ASUS v8? (I am on 4.2.1)
2. Root it (how, what procedure should I follow and which files)?
3. Which BL should I install? I've been using CWM on my GS3, but a lot of these guides use TWRP. which versions
4. This guide looks dated, please confirm
http://forum.xda-developers.com/showthread.php?t=2055430
5. Any recommendations for a better ROM? Or is the CM10.1 the best for this tablet?
6. Since I have the WIFI version of this, I am assuming I dont need to worries about the baseband updates that were recently required for the CM10.1 updates? If I am wrong, please advise.
Thanks for you help in advance!
Click to expand...
Click to collapse
Most of your questions have already been answered multiple times. Ill do my best to summarize the answers ......
1) V8 unlocks most although there are some who arent able to unlock after having things come back from Asus from repair.
2) Unless you are stuck on a locked bootloader, skip rooting if you are planning on installing a custom rom..... why waste your time rooting something you wont be using? If you fall into this category, your option are limited but there is a way to root without TWRP or CWM.
3) Personally I have found that the 4.1 bootloader version 10.4.2.20 seems to play nicest with my tf300t. This of course means im stuck using Roms made specifically for 4.1 bootloaders. Im using twrp 2.4.4.0. Instructions on downgrading firmware are all over, but im pretty sure you must have an unlocked bootloader for this as well. Its a simple fastboot command to push the older system blob file to the device. Relatively easy.
4) Cant comment as I dont use CM
5) Im using CleanRom Inheritance and found that it not only benches higher, but runs much much faster than anything else I have tried on my tablet. I started with the latest 4.2.1 ROM and Bootloader. After trying everything out and everything lagging on my tablet, I decided to downgrade firmware. ROMS are nothing but personal preference, but, I find personally that Cromi ( for 4.1 ) along with Unter's kernel,makes my device smooth as butter. YMMV
6) Again, I cant comment as I dont use CM. Maybe someone else can chime in on this ? There are PLENTY of rom options available. Just try things out and see what you like best. Just remember to read the roms OP very carefully to make sure you have the proper bootloader installed for it. You can brick your device if you mismatch the rom and bootloaders.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
pyraxiate said:
Most of your questions have already been answered multiple times. Ill do my best to summarize the answers ......
1) V8 unlocks most although there are some who arent able to unlock after having things come back from Asus from repair.
2) Unless you are stuck on a locked bootloader, skip rooting if you are planning on installing a custom rom..... why waste your time rooting something you wont be using? If you fall into this category, your option are limited but there is a way to root without TWRP or CWM.
3) Personally I have found that the 4.1 bootloader version 10.4.2.20 seems to play nicest with my tf300t. This of course means im stuck using Roms made specifically for 4.1 bootloaders. Im using twrp 2.4.4.0. Instructions on downgrading firmware are all over, but im pretty sure you must have an unlocked bootloader for this as well. Its a simple fastboot command to push the older system blob file to the device. Relatively easy.
4) Cant comment as I dont use CM
5) Im using CleanRom Inheritance and found that it not only benches higher, but runs much much faster than anything else I have tried on my tablet. I started with the latest 4.2.1 ROM and Bootloader. After trying everything out and everything lagging on my tablet, I decided to downgrade firmware. ROMS are nothing but personal preference, but, I find personally that Cromi ( for 4.1 ) along with Unter's kernel,makes my device smooth as butter. YMMV
6) Again, I cant comment as I dont use CM. Maybe someone else can chime in on this ? There are PLENTY of rom options available. Just try things out and see what you like best. Just remember to read the roms OP very carefully to make sure you have the proper bootloader installed for it. You can brick your device if you mismatch the rom and bootloaders.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
First of all, thanks for the quick reply and detail!
1. I have a new one - so hopefully I should be ok. But I'll use v8
2. Great point, duh! The ROMs are already rooted!
3. I'd like to stick with the 4.2.2 bootloaders since my other devices are all running the same stuff. I haven't used TWRP before - any preference to that versus CWM?
4. no worries
5. I'll definitely keep in mind along with your bootloader suggestion should I downgrade. I've felt the lag with the ASUS Stock 4.2.1 ROM and all it's bloatware - I'm expect an immediate change right there with a clean rom.
6. yeah that is the primary reason I am asking about which bootloader to use with CM10.1's new nightlies.
snoopspecial said:
First of all, thanks for the quick reply and detail!
1. I have a new one - so hopefully I should be ok. But I'll use v8
2. Great point, duh! The ROMs are already rooted!
3. I'd like to stick with the 4.2.2 bootloaders since my other devices are all running the same stuff. I haven't used TWRP before - any preference to that versus CWM?
4. no worries
5. I'll definitely keep in mind along with your bootloader suggestion should I downgrade. I've felt the lag with the ASUS Stock 4.2.1 ROM and all it's bloatware - I'm expect an immediate change right there with a clean rom.
6. yeah that is the primary reason I am asking about which bootloader to use with CM10.1's new nightlies.
Click to expand...
Click to collapse
To be honest, the lag is still there accross all the 4.2 roms I tried, even debloated. Its not as bad but its still there. My alternate device has a beastly exynos in it so im used to a perfect smooth experience. I notice even a little bit of jitter and it drives me crazy ( hence why I downgraded to 4.1 ) .
As far as what bootloader to use for which CM rom, each will tell you which to use specifically. I saw there is a cm10.1 for 4.2 and for 4.1. Just make sure to match things.
I used to be a CWM user all the way, but twrp does trump it in features and usability, especially for the transformer series. I beleive there is only one single twrp that works properly on the new bootloader for stock based roms ( no cwm will work on it at all). It ends in .42 so make sure you flash the correct one. If not, your partitions wont be writable.
One MAJOR warning.........
Do NOT use the wipe / factory reset on ANY bootloader. You will brick your tablet!!! Permanently!!!!
You can ONLY use the wipes inside of twrp / CWM.
Sent from my SGH-T889 using xda app-developers app
dude, you are so awesome!
definitely smart to have installed TWRP - CWM through ROM Manager tried to suggest installing a TF201 recovery. From the web site it's vague but suggest a TF101 image as well.
I followed your suggestion and downloaded the 42 TWRP recovery from after having done all the SDK Tools installation and testing connectivity with FASTBOOT (from the installed SDK package, not random ones from the internet).
http://www.teamw.in/project/twrp2/97
I'm up in TWRP and running a backup of the ASUS original installation, will copy to External SD card.
previously i've formatted the internal card and then installed the ROM and GAPPS. Should I not do this?
thanks again! I'm keeping notes and will update when done.
pyraxiate said:
Most of your questions have already been answered multiple times. Ill do my best to summarize the answers ......
1) V8 unlocks most although there are some who arent able to unlock after having things come back from Asus from repair.
2) Unless you are stuck on a locked bootloader, skip rooting if you are planning on installing a custom rom..... why waste your time rooting something you wont be using? If you fall into this category, your option are limited but there is a way to root without TWRP or CWM.
3) Personally I have found that the 4.1 bootloader version 10.4.2.20 seems to play nicest with my tf300t. This of course means im stuck using Roms made specifically for 4.1 bootloaders. Im using twrp 2.4.4.0. Instructions on downgrading firmware are all over, but im pretty sure you must have an unlocked bootloader for this as well. Its a simple fastboot command to push the older system blob file to the device. Relatively easy.
4) Cant comment as I dont use CM
5) Im using CleanRom Inheritance and found that it not only benches higher, but runs much much faster than anything else I have tried on my tablet. I started with the latest 4.2.1 ROM and Bootloader. After trying everything out and everything lagging on my tablet, I decided to downgrade firmware. ROMS are nothing but personal preference, but, I find personally that Cromi ( for 4.1 ) along with Unter's kernel,makes my device smooth as butter. YMMV
6) Again, I cant comment as I dont use CM. Maybe someone else can chime in on this ? There are PLENTY of rom options available. Just try things out and see what you like best. Just remember to read the roms OP very carefully to make sure you have the proper bootloader installed for it. You can brick your device if you mismatch the rom and bootloaders.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
snoopspecial said:
dude, you are so awesome!
definitely smart to have installed TWRP - CWM through ROM Manager tried to suggest installing a TF201 recovery. From the web site it's vague but suggest a TF101 image as well.
I followed your suggestion and downloaded the 42 TWRP recovery from after having done all the SDK Tools installation and testing connectivity with FASTBOOT (from the installed SDK package, not random ones from the internet).
http://www.teamw.in/project/twrp2/97
I'm up in TWRP and running a backup of the ASUS original installation, will copy to External SD card.
previously i've formatted the internal card and then installed the ROM and GAPPS. Should I not do this?
thanks again! I'm keeping notes and will update when done.
Click to expand...
Click to collapse
okay - lots of options in TWRP - going the simple safe route and just following the norm:
http://teamw.in/whattowipe
snoopspecial said:
dude, you are so awesome!
definitely smart to have installed TWRP - CWM through ROM Manager tried to suggest installing a TF201 recovery. From the web site it's vague but suggest a TF101 image as well.
I followed your suggestion and downloaded the 42 TWRP recovery from after having done all the SDK Tools installation and testing connectivity with FASTBOOT (from the installed SDK package, not random ones from the internet).
http://www.teamw.in/project/twrp2/97
I'm up in TWRP and running a backup of the ASUS original installation, will copy to External SD card.
previously i've formatted the internal card and then installed the ROM and GAPPS. Should I not do this?
thanks again! I'm keeping notes and will update when done.
Click to expand...
Click to collapse
Im assuming you are flashing CM10 then? The only important thing is fully read the OP and match your bootloader to whatever one they tell you. Its generally not a suggestion, but an actual requirement.
Mines a 32gb so I keep all of my backups and rom flashes right on the internal storage. I feel its safer in case of SD corruption or an accidental wipe. It doesnt hurt to have it in 2 places though ( backup your original rom to SD card but keep everything on the internal as well ). I always flash from internal ( roms and nandroids alike ). Ive never had an issue.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
so this is what i've done so far and am stuck now it seems. probably a mismatch between the CM ROM and the BOOTLOADER.
1. Installed TWRP 2.5.0.0 - version ending with 42.
2. From the Wipe -> Advanced in TWRP, I selected SYSTEM, CACHE, DALVIK CACHE, and DATA (skipped the last two options).
3. I have the ROMs/GAPPS on my external SD card (and backup now too)
4. I installed today's nightly CM 10.1 for TF300T and the 20130301-signed (per 4.2.2 CM builds).
5. Reboot (via TWRP, Power Off)
I hit the power button to turn on and it gets stuck at the ASUS screen. Cannot boot into ROM either via the Android icon in the Bootloader menu.
snoopspecial said:
so this is what i've done so far and am stuck now it seems. probably a mismatch between the CM ROM and the BOOTLOADER.
1. Installed TWRP 2.5.0.0 - version ending with 42.
2. From the Wipe -> Advanced in TWRP, I selected SYSTEM, CACHE, DALVIK CACHE, and DATA (skipped the last two options).
3. I have the ROMs/GAPPS on my external SD card (and backup now too)
4. I installed today's nightly CM 10.1 for TF300T and the 20130301-signed (per 4.2.2 CM builds).
5. Reboot (via TWRP, Power Off)
I hit the power button to turn on and it gets stuck at the ASUS screen. Cannot boot into ROM either via the Android icon in the Bootloader menu.
Click to expand...
Click to collapse
going to give Cromi 4.2.1 a try too while I am in this bootloader:
http://forum.xda-developers.com/showthread.php?t=2204166
I have the matching ASUS bootloader and TWRP combination this the ROM needs.
As for the CM10.1 - looks like for TF300T they are still using the older JB requirements... but still researching.
snoopspecial said:
going to give Cromi 4.2.1 a try too while I am in this bootloader:
http://forum.xda-developers.com/showthread.php?t=2204166
I have the matching ASUS bootloader and TWRP combination this the ROM needs.
As for the CM10.1 - looks like for TF300T they are still using the older JB requirements... but still researching.
Click to expand...
Click to collapse
interesting - this ROM is packed with configuration options - you can really tailor your install.. very interesting - should work since it is a stock-based rom. we'll see. installing now.
snoopspecial said:
interesting - this ROM is packed with configuration options - you can really tailor your install.. very interesting - should work since it is a stock-based rom. we'll see. installing now.
Click to expand...
Click to collapse
yeah so that worked fine. the CM10.1 version must require some different combination.
taking your suggestions now and downgrading to the 4.1 bootloader. will also install the CleanInheritance rom.
by the way, thanks again for your help and suggestions!
So just for other people out there... if you want to run the TF300T downloads from get.cm (the nightlies as of now).
I've confirmed the following requirements:
1. 10.4.2.20 - TWRP 2.5.0.0 - JB
2. CM 10.1 5/25/2013 Nighty (This is a 4.2.2 ROM - requiring the JB, not 4.2 bootloader - i imagine at some point this will be updated)
3. GAPPS 20130301-signed
ah so nice!
Hello everyone
I've got p5110 with new 4.2.2 rom (xeo). I have installed also root and cwm. That wasn't problem. But the main problem was looking for kernel cos i want to overclock cpu on gpu on stock rom So i found this one http://forum.xda-developers.com/showthread.php?t=2302663 but there are few questions...
Which files I install? I know that zip file in cwm but there is the second one called proprietary-vendor-samsung.zip for JB >= 4.2 (stock 4.2.2, CM 10.2) . I dont understand which file i should install first... :/ I want single boot on stock rom.
Thanks for all !
Qosmio46 said:
Which files I install? I know that zip file in cwm but there is the second one called proprietary-vendor-samsung.zip for JB >= 4.2 (stock 4.2.2, CM 10.2) . I dont understand which file i should install first... :/ I want single boot on stock rom.
Click to expand...
Click to collapse
Just read the OP carefully, it has the instructions, and they are very simple:
1. Boot into the recovery.
2. Flash the kernel (blackhawk-next-kernel-x.y.z-p51xx.zip) -- replace "x.y.z" with the version you need.
3. Immediately after that (do NOT reboot!) flash the proprietary Samsung binaries (proprietary-vendor-samsung.zip).
4. Reboot.
You don't need to worry about all the dual-boot stuff.
I think I understand now there is a main file with kernel and with this zip comes some binary files in catalogue (that's what i saw) i need to install this in cwm after this install this second zip with no re booting. In this second zip are files which are managed these from first zip with kernel? Thats way i need to install these both one by one. Seems legit thank you very much i hope that will work
Qosmio46 said:
i hope that will work
Click to expand...
Click to collapse
It will, don't worry. I have been using this kernel for quite a while on my P3113, went through many version upgrades. The best kernel for this tablet, hands down!
Confirmed! Best Kernel
Today morning, i have installed this kernel as you said first kernel then these files It is great and working perfectly Thanks for help !