Related
hi all. i just purchased a Ployer Momo8 tablet and it came with Android 4.0 and ICS. i really like the tablet, especially for the extremely low price of $150. my question is, does anyone know of any custom ROMS for this tablet, because it needs serious optimization. especially considering that i have an rooted EVO running a Team Nocturnal ROM fully loaded, so my EVO runs circles around this tablet. i've searched google for custom ROMS for this tablet, but come up with nothing, especially for the 4.0.
Thanks all.
I have this tablet, really nice tablet. A lot of us have downgraded back to 2.3.4 everything seems to work on gingerbread.
I haven't seen any roms, I did put together a recovery for 2.3.4 version. Momo9 seems to have a lot going for it, that's an 7" version of this tablet.
Anyway good luck
Vampirefo
vampirefo said:
I have this tablet, really nice tablet. A lot of us have downgraded back to 2.3.4 everything seems to work on gingerbread.
I haven't seen any roms, I did put together a recovery for 2.3.4 version. Momo9 seems to have a lot going for it, that's an 7" version of this tablet.
Anyway good luck
Vampirefo
Click to expand...
Click to collapse
how do i downgrade to 2.3? does anyone have the stuff necessary to perform the downgrade with some instruction? i've never downgraded before, only upgraded. i'm sick and tired of the force closes on 4.0.
Here is a custom rom, I made a few changes to it so it can be installed on momo8 via my recovery.
http://bit.ly/ykpLXn
Before you install make sure you back up your data and system via my recovery.
once they are backed up place this zip in the zip folder on your sdcard.
if you created directories you should find on your sdcard a folder called momo8, inside that folder are three more folders. backup, updates, zip
this goes in zip folder.
you need to go to advanced options select wipe system, then you can install zip you would need to press home to go back to main screen from there choice install zip follow onscreen instructions. as with backing up wait a bit after zip is installed before pressing home to go to main screen.
If you want to wipe your data, you can do that as well, you would need to wipe data first before wiping system or come back after you installed zip then wipe data.
the custom rom came from this thread.
http://www.slatedroi...-new-firmwares/
---------- Post added at 07:00 PM ---------- Previous post was at 06:56 PM ----------
You can get recovery from here
http://www.youtube.com/watch?v=bz_i9Wk9eR8
or from here
http://www.slatedroid.com/topic/28879-momo8-business-edition/page__gopid__330892#entry330892
downgrade software here
http://bit.ly/xPzDgu
video here, it's for upgrade same instruction but above image is 2.3.4 instead of 4.0
http://www.youtube.com/watch?v=l-cB1Ya11Z4
issues with tablet
First off, I just bought this thing and it is PAINFULLY slow. After doing some research, I have decided I want to downgrade it to 2.3.4 however, I believe that a lot of folks posting tutorials do not use english as their first language. That said, I downloaded this phoenixprousb, which is definately not in english, and it requires an img and a key. I managed to find a fresh IMG, but no one seems to mention anything about a key.
Does anyone know anything about what they mean by .key and is there an easier better way to do this? The only tutorial I can find requires a .key which they dont include.
nachinc said:
First off, I just bought this thing and it is PAINFULLY slow. After doing some research, I have decided I want to downgrade it to 2.3.4 however, I believe that a lot of folks posting tutorials do not use english as their first language. That said, I downloaded this phoenixprousb, which is definately not in english, and it requires an img and a key. I managed to find a fresh IMG, but no one seems to mention anything about a key.
Does anyone know anything about what they mean by .key and is there an easier better way to do this? The only tutorial I can find requires a .key which they dont include.
Click to expand...
Click to collapse
A key? You are about to brick your tablet that is for momo9c which will brick your tablet.
vampirefo said:
A key? You are about to brick your tablet that is for momo9c which will brick your tablet.
Click to expand...
Click to collapse
Then what is this http://www.slatedroid.com/topic/26606-how-to-guide-flashing-updated-firmwarerom-to-ployer-momo9c/
Which is supposed to be the same process for all ployer tablet referenced here
http://www.pandawillforum.com/showt...mware-for-Ployer-MOMO8-business-edition/page2
?
Again, Does anyone have a solution? Anyone?
nachinc said:
Then what is this http://www.slatedroid.com/topic/26606-how-to-guide-flashing-updated-firmwarerom-to-ployer-momo9c/
Which is supposed to be the same process for all ployer tablet referenced here
http://www.pandawillforum.com/showt...mware-for-Ployer-MOMO8-business-edition/page2
?
Again, Does anyone have a solution? Anyone?
Click to expand...
Click to collapse
It's your tablet, brick it if you want, I wont bother trying to stop you anymore.
I just dont understand why there are two seperate processes when they are supposed to be the same procedure. I have livesuite open and its asking me to press PVP for 10s..
PVP?!
God I hate these tabs
SO i managed to flash the tab over to the 2.3.4 clean version listed here but now market doesnt work. Any solutions?
nachinc said:
I just dont understand why there are two seperate processes when they are supposed to be the same procedure. I have livesuite open and its asking me to press PVP for 10s..
PVP?!
God I hate these tabs
SO i managed to flash the tab over to the 2.3.4 clean version listed here but now market doesnt work. Any solutions?
Click to expand...
Click to collapse
Try flashing a clean original 2.3.4. from Ployer site. Use google translator to find download section and type MOMO8A to find the right firmware. It works perfectly on my tab.
Hi guys, i haven't found any MOMO8 theards, so I have to ask here.
I have flashed firmware for LY-F1,but now I can't flash MOMO8 firmware back.
I have tried LiveSuit,all the Phoenix tools but no luck.
Please help me!
Hey Everyone
I've done quite a bit of reading and nothing seems to quite fit the issue I am having so I thought I'd post and seek help.
Some background info...I've unlocked the bootloader and also generated the NVFlash files when I first bought the tablet. It was running the stock ICS Rom. I had CWM Recovery and it was rooted.
I wanted to try a new ROM called BlueAndroid as I read it was really good. I followed all of the instructions and flashed from the sdcard. It appeared successful but when I went to restart the system, it kept boot looping at the ASUS Screen. Then I thought I'd just go back to what I had before by restoring it from CWM Recovery but to my surprise, it didn't work and now it isn't even looping, just stuck on the ASUS Screen.
I tried to fastboot CWM and TeamWin Recovery. Although they were both successful writes to the tablet, they won't load. I can only get to the fastboot screen where it shows the 'wipe data' and 'USB icon'. There used to be an Android Robot icon too but it is gone now.
I even tried to NVFlash. It worked but I'm still stuck on Asus Screen.
Lastly, when I select wipe data, it erases and the Team WIN logo appears for a split second and then it goes back to Asus Screen.
I keep reading something about the possibility of incorrect partitions but I have no idea what that means.
Any help would be greatly appreciated.
Thanks
A
P.S. In the meantime, is there any way to shut the tablet off? I've tried holding the power button down but it just reboots.
Solved: Used blobunpack to get bootloader files from the stock ICS ROM (blobunpack the blob file from the ROM). Then used NVFlash to download those files to tablet. Hope this helps others with same problem. I can elaborate more tomorrow...it is really late and very sleepy but relieved!
xxboarderxx said:
Hey Everyone
I've done quite a bit of reading and nothing seems to quite fit the issue I am having so I thought I'd post and seek help.
Some background info...I've unlocked the bootloader and also generated the NVFlash files when I first bought the tablet. It was running the stock ICS Rom. I had CWM Recovery and it was rooted.
I wanted to try a new ROM called BlueAndroid as I read it was really good. I followed all of the instructions and flashed from the sdcard. It appeared successful but when I went to restart the system, it kept boot looping at the ASUS Screen. Then I thought I'd just go back to what I had before by restoring it from CWM Recovery but to my surprise, it didn't work and now it isn't even looping, just stuck on the ASUS Screen.
I tried to fastboot CWM and TeamWin Recovery. Although they were both successful writes to the tablet, they won't load. I can only get to the fastboot screen where it shows the 'wipe data' and 'USB icon'. There used to be an Android Robot icon too but it is gone now.
I even tried to NVFlash. It worked but I'm still stuck on Asus Screen.
Lastly, when I select wipe data, it erases and the Team WIN logo appears for a split second and then it goes back to Asus Screen.
I keep reading something about the possibility of incorrect partitions but I have no idea what that means.
Any help would be greatly appreciated.
Thanks
A
P.S. In the meantime, is there any way to shut the tablet off? I've tried holding the power button down but it just reboots.
Solved: Used blobunpack to get bootloader files from the stock ICS ROM (blobunpack the blob file from the ROM). Then used NVFlash to download those files to tablet. Hope this helps others with same problem. I can elaborate more tomorrow...it is really late and very sleepy but relieved!
Click to expand...
Click to collapse
I had the same problem. I think it is bricked. I called ASUS, told them it was unlocked, they told me to ship it to them and they would fix it. I boxed it up, and shipped it off. Could not turn it off. Hope the box did not catch on fire.
OP, where were you a week ago when I "bricked" my tablet?
I had the -exact- same issue, btw, although with different circumstances. I can verify with 100% confidence that using NVFlash successfully restores the ICS bootloader. How I understand our situation is that when you tried to flash a ROM or anything based on JB over an ICS-device, it confuses things and causes issues. So you basically have to restore the ICS bootloader to get any progress.
But you hit the nail on the head describing my problem, although I would have ended up typing a dissertation to get across the same information you did. So touche on that
I used the same steps, as well. I blob unpacked my ICS stock firmware (.29 version from ASUS website). I used the boot.blob from my NVFlash files, along with the files I unpacked from the stock blob and flashed them over NVflash.
After a week of a useless tablet, I'm up and running.
I'm going to write a guide about my experience for anyone else and I would welcome your input sir.
I think you could mean a kind of recovery loop: There is a file called "command" on the cache partition which causes the recovery image to boot. But if the recovery is broken then it will not empty cache. The recovery will boot but does not update screen (showing just boot splash). On the next time it will boot again ...
Please be just carefully: "wipe data" in the fastboot menu will create the "command" file.
ScottBroker said:
I had the same problem. I think it is bricked. I called ASUS, told them it was unlocked, they told me to ship it to them and they would fix it. I boxed it up, and shipped it off. Could not turn it off. Hope the box did not catch on fire.
Click to expand...
Click to collapse
Sorry...if I could have made this attempt last week, I may have been able to help you then. :sly:
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
opethfan89 said:
OP, where were you a week ago when I "bricked" my tablet?
I had the -exact- same issue, btw, although with different circumstances. I can verify with 100% confidence that using NVFlash successfully restores the ICS bootloader. How I understand our situation is that when you tried to flash a ROM or anything based on JB over an ICS-device, it confuses things and causes issues. So you basically have to restore the ICS bootloader to get any progress.
But you hit the nail on the head describing my problem, although I would have ended up typing a dissertation to get across the same information you did. So touche on that
I used the same steps, as well. I blob unpacked my ICS stock firmware (.29 version from ASUS website). I used the boot.blob from my NVFlash files, along with the files I unpacked from the stock blob and flashed them over NVflash.
After a week of a useless tablet, I'm up and running.
I'm going to write a guide about my experience for anyone else and I would welcome your input sir.
Click to expand...
Click to collapse
Well, I'm sure you learned a lot during your experience of trying to get it working again - I know I did so that's a +1. I wasn't worried that my tablet was bricked because I was told that if I had the NVFLASH files, I could recover from anything save dropping it and breaking it that way. I was also able to connect to the PC using fastboot and adb so that was another positive.
If you write a guide, that would be great as while I was trying to piecemeal information together to get my tablet running again, there seemed to be dozens of people out there with a similar problem and being unable to get it working again and having to send it off to Asus. Would probably be a great contribution.
The one thing I learned though this ordeal is that the stock bootloader needs to be the same as the custom ROM before installing. I wish ROM guides would tell you this REALLY important fact...
Cheers
A
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
xxboarderxx said:
Well, I'm sure you learned a lot during your experience of trying to get it working again - I know I did so that's a +1. I wasn't worried that my tablet was bricked because I was told that if I had the NVFLASH files, I could recover from anything save dropping it and breaking it that way. I was also able to connect to the PC using fastboot and adb so that was another positive.
If you write a guide, that would be great as while I was trying to piecemeal information together to get my tablet running again, there seemed to be dozens of people out there with a similar problem and being unable to get it working again and having to send it off to Asus. Would probably be a great contribution.
The one thing I learned though this ordeal is that the stock bootloader needs to be the same as the custom ROM before installing. I wish ROM guides would tell you this REALLY important fact...
Cheers
A
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
Click to expand...
Click to collapse
Really? I didn't know that....that might explain why none of the ROM's I'm flashing will work.....
At this point, I'm just going to upgrade to the stock JB firmware and flash the new JB roms. I've got my NVFlash ICS files (which saved my frickin life) so I have no hesitations about doing anything, and I really understand the NVFlash process well having bricked myself so hard.
My guide is mostly done. I spent more time writing it than I did focusing on schoolwork so I will finish it up hopefully this weekend. It's rather long and quite details so I hope it will help everyone.
I was smiling as I read the first post, but this is going to come in real handy if I nuke my bootloader. Thanks. I wish I had gotten to this first, heh, I could have told you don't flash a Jellybean ROM over an ICS bootloader, it won't boot.
Good information to have though. Thank you!
opethfan89 said:
Really? I didn't know that....that might explain why none of the ROM's I'm flashing will work.....
At this point, I'm just going to upgrade to the stock JB firmware and flash the new JB roms. I've got my NVFlash ICS files (which saved my frickin life) so I have no hesitations about doing anything, and I really understand the NVFlash process well having bricked myself so hard.
My guide is mostly done. I spent more time writing it than I did focusing on schoolwork so I will finish it up hopefully this weekend. It's rather long and quite details so I hope it will help everyone.
Click to expand...
Click to collapse
:good:
Just giving some advice to those who may jump in late, DO NOT use the "wipe data" method from holding volume down. This method relies on Asus' stock recovery image. And it somehow screws everything up when you do it on a non Asus' recovery.. Not sure why but dont ever use that
elesbb said:
Just giving some advice to those who may jump in late, DO NOT use the "wipe data" method from holding volume down. This method relies on Asus' stock recovery image. And it somehow screws everything up when you do it on a non Asus' recovery.. Not sure why but dont ever use that
Click to expand...
Click to collapse
You can do it if you have a custom recovery already flashed like TWRP or CWM. But I agree with you - after you start having a basic understanding of Android customization, there's no reason why you would want to use 'wipe data' from the volume down+power.
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
elesbb said:
Just giving some advice to those who may jump in late, DO NOT use the "wipe data" method from holding volume down. This method relies on Asus' stock recovery image. And it somehow screws everything up when you do it on a non Asus' recovery.. Not sure why but dont ever use that
Click to expand...
Click to collapse
That finally explains why it wouldn't work, thank you for elaborating on that!!
Is there a guide on how to get the stock recovery back, or does it automatically get flashed when you flash stock?
opethfan89 said:
That finally explains why it wouldn't work, thank you for elaborating on that!!
Is there a guide on how to get the stock recovery back, or does it automatically get flashed when you flash stock?
Click to expand...
Click to collapse
Automatically gets flashed when you flash stock.
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
If you are in recovery loop you cannot go into the fastboot menu. The only way to get the stock recovery back is to use nvflash.
Okay! (bit of a noob here but I really want help T_T)
I'm on 4.2.1 by the way - build number should be latest available.
So I finally decided to get root on my tablet. I followed the instructions by a youtube user, and succeeded. I downloaded SuperUser and a root checker to make sure everything went right, and proceeded to download PacMan 4.2 Milestone, as well as CyanogenMod 10
I did a factory reset from the settings menu of the tablet, and tried to set up PacMan. It worked alright until the loading screen, where the ghost would bounce indefinitely. When it was clear I wasn't going to get in, I restarted, and factory reset again from the TWRP menu, this time making sure to erase Dalvik, cache, and system (I think that's all?).
I then tried to install CM10, which didn't work either. I found out later it was because CM 10 didn't work with the 4.2 bootloader.
So I factory reset again, erased dalvik, system, and cache, and proceeded to reboot into the recovery I made on external. I don't know if it's normal, but when it reached the step 'restoring data,' it was basically stuck. I let it continue overnight, and found that recovery overall took 1933 seconds (is this a sign of something bad?)
And now I'm back to booting! It's taking a really long time though - at least ~45 minutes on the ASUS screen with the little circle going around.
I guess my question is, (1) what do I do, (2) what is the situation I'm in/how did I get here, (3) how do I avoid it (if possible) in the future?
by the way, I forgot to mention that I can still access the twrp menu. I don't know if that helps though?
Hope this helps!
hobomobile said:
Okay! (bit of a noob here but I really want help T_T)
I'm on 4.2.1 by the way - build number should be latest available.
So I finally decided to get root on my tablet. I followed the instructions by a youtube user, and succeeded. I downloaded SuperUser and a root checker to make sure everything went right, and proceeded to download PacMan 4.2 Milestone, as well as CyanogenMod 10
I did a factory reset from the settings menu of the tablet, and tried to set up PacMan. It worked alright until the loading screen, where the ghost would bounce indefinitely. When it was clear I wasn't going to get in, I restarted, and factory reset again from the TWRP menu, this time making sure to erase Dalvik, cache, and system (I think that's all?).
I then tried to install CM10, which didn't work either. I found out later it was because CM 10 didn't work with the 4.2 bootloader.
So I factory reset again, erased dalvik, system, and cache, and proceeded to reboot into the recovery I made on external. I don't know if it's normal, but when it reached the step 'restoring data,' it was basically stuck. I let it continue overnight, and found that recovery overall took 1933 seconds (is this a sign of something bad?)
And now I'm back to booting! It's taking a really long time though - at least ~45 minutes on the ASUS screen with the little circle going around.
I guess my question is, (1) what do I do, (2) what is the situation I'm in/how did I get here, (3) how do I avoid it (if possible) in the future?
Click to expand...
Click to collapse
hobomobile said:
by the way, I forgot to mention that I can still access the twrp menu. I don't know if that helps though?
Click to expand...
Click to collapse
1. Assuming you know how to do this, try flashing the ASUS stock rom and kernel using TWRP. Before asking more questions, use the search tool in XDA developers first since it is most likely someone may of been in a similar situation to yours.
2. It is probably that the person who you followed on youtube might of been be using a different build of stock. That's just my hypothesis-others may differ to mine. Since you have TWRP, you will be able to recover from this situation. (Pun not intended)
3. You should always research about what you're doing with your android device before you do anything about it, especially if the guide is not moderated by the wonderful people from XDA-Developers, and even more so if you are a noob-even if you consider yourself a novice (like me)
To save you some time:
http://forum.xda-developers.com/showthread.php?t=1697227 The mother of guides, read this first.
http://forum.xda-developers.com/showthread.php?p=42407269 [TOOL]Minimal ADB and Fastboot
http://forum.xda-developers.com/showthread.php?t=2257421 Ask any question here-Noob friendly help thread.
Will update this post with more information if need be. Don't be afraid to ask if you're absolutely confused.
Hope this helped.
Live long and prosper.
If I have helped you in any way, shape or form, hit the thanks button. If I have given you a link to someone on XDA that helped you, give them thanks first.
Thanks a lot! I'll do my best trying to find the info - sorry if I have to bother you again though!
Okay, so I have minimal ADB (I actually used that to get root in the first place), and I downloaded the latest kernel and firmware - I'm pretty sure they're the right versions too (10.6.1.27).
Do I just open TWRP, factory reset, clear dalvik and cache, and install both of the above from an SD card? I did some looking around, but I still don't get what a kernel does, or if it's necessary in this situation.
I'm looking at this right now, by the way (http://forum.xda-developers.com/showthread.php?t=2187982), method three.
Okay, so I downloaded this: ASUS Transformer Pad TF300T Firmware: V10.6.1.27.1 Only for US SKU (Android 4.2) - 2013.07.29 update, unzipped the file, went back into twrp, and wiped system, data, and dalvik. When I tried to install it though, it says 'failed.'
What now?
Potential Solution?
Quote:
hobomobile said:
Okay, so I downloaded this: ASUS Transformer Pad TF300T Firmware: V10.6.1.27.1 Only for US SKU (Android 4.2) - 2013.07.29 update, unzipped the file, went back into twrp, and wiped system, data, and dalvik. When I tried to install it though, it says 'failed.'
What now?
Click to expand...
Click to collapse
hobomobile said:
Okay, so I have minimal ADB (I actually used that to get root in the first place), and I downloaded the latest kernel and firmware - I'm pretty sure they're the right versions too (10.6.1.27).
Do I just open TWRP, factory reset, clear dalvik and cache, and install both of the above from an SD card? I did some looking around, but I still don't get what a kernel does, or if it's necessary in this situation.
I'm looking at this right now, by the way (http://forum.xda-developers.com/showthread.php?t=2187982), method three.
Click to expand...
Click to collapse
Define Kernel:
Google:
Define Kernel:
ker·nel
/ˈkərnl/
Noun
A softer, usually edible part of a nut, seed, or fruit stone contained within its hard shell.
The seed and hard husk of a cereal, esp. wheat.
Synonyms
core - nucleus - pith - grain - heart - seed - essence
So that was useless. :silly:
XDA:
Define Kernel-and ROM, and everything:
http://forum.xda-developers.com/wiki/index.php?title=ROM-VS-Kernel "ROM vs Kernel"
If I was you, I would just flash a custom ROM. From here: http://forum.xda-developers.com/showthread.php?t=1697227
There are plenty of ROMs linked there. Even if you want to use one based on the Stock ROM, you can find the links there.
Flash it in TWRP the same way you flashed the "ASUS Transformer Pad TF300T Firmware: V10.6.1.27.1 Only for US SKU".
Personally, I prefer custom roms because they provide a lot of customisation options.
Is that what your looking for, or do you really want to use the stock ROM?
Remember to at least have a look at the ROMs before dismissing them.
The kernel needs to be the same type as the ROM. e.g, A stock (based) rom will need a stock (based) kernel. AKOP/ASOP ROMS need ASOP/AKOP Kernels. You get the point. See the link mentioned for more information.
Check the compatibility of the ROM with your bootloader before you flash it to not get into situations like this again. (From when you said that CM10 failed to work with your boot loader.
Hope this helped.
BTW, this did not bother me one bit. Your Welcome!
Live long and prosper.
If I have helped you in any way, shape or form, hit the thanks button. If I have given you a link to someone on XDA that helped you, give them thanks first.
If you are running "10.6.1.27" that might be the issue some roms don't boot if you can access fast boot try downgrading to 10.6.1.15.3
Sent from my HTC Desire C using xda app-developers app
1337 H4X0R said:
XDA:
Define Kernel-and ROM, and everything:
http://forum.xda-developers.com/wiki/index.php?title=ROM-VS-Kernel "ROM vs Kernel"
The kernel needs to be the same type as the ROM. e.g, A stock (based) rom will need a stock (based) kernel. AKOP/ASOP ROMS need ASOP/AKOP Kernels. You get the point. See the link mentioned for more information.
Check the compatibility of the ROM with your bootloader before you flash it to not get into situations like this again. (From when you said that CM10 failed to work with your boot loader.
Click to expand...
Click to collapse
Just to add a *tiny* little tidbit right here: every rom has a kernel. It wouldn't boot without one. Yes, a dev can remove the kernel and force you to find one to flash, but that's utterly pointless. I'm just saying that you really don't have to bother yourself with that as yet.
While it's great to educate yourself, don't get overwhelmed. You have PLENTY time to learn more.
I ran into similar issues. You need to make sure your ROM/kernal matches your bootloader and matches your recovery. If not all three match, you run into this issue.
Sent from my EVO using XDA Premium 4 mobile app
so far no good :/
I gave up on this for a couple days, figuring I'd come back to it later when I wasn't as distressed.
so right now, my goal is to get back to stock, and get everything working again before downgrading to 10.6.1.15.3, and then install a custom ROM
Not sure why, but right now, I can't even install the stock kernel flashed onto the device - twrp still tells me 'failed.'
I'm sure that I got the right stock kernel/rom for my build number, so what is going on?
Hello again,
I would like to install the least buggy Jelly Bean ROM onto my ASUS Transformer Pad TF300T. I have never rooted my Tablet before and I am on the latest OTA update by ASUS
Android Version 4.2.1
Build JOP40D.WW_epad-10.6.1.27.5-20130902
I very much would appreciate some hand holding on this whole process. I have signed up to the CyanogenMod website but as yet not had any replies.
I don't really know what ROM to go for as its a minefield, but I would like the most stable Jelly Bean version. Not too keen on moving over to Kit Kat yet.
I have never done this before and I have quite a bit of trepidation about the whole process but as it is, my official ASUS Jelly Bean operating system is laggy and the battery drain is exceptionally noticeable. The tablet can drain empty on Stand By within a couple of days. I have tried all the tricks to extend battery life, including charging Tablet and battery spereately, Cold Boots and Fresh installs but nothing helps.
Cheers
the lemming said:
I don't really know what ROM to go for as its a minefield, but I would like the most stable Jelly Bean version. Not too keen on moving over to Kit Kat yet.
Click to expand...
Click to collapse
If you ask 5 people about this you will get at least 10 opinions...
I choose not to vote on that part of your question.
I have never done this before and I have quite a bit of trepidation about the whole process
Click to expand...
Click to collapse
The most important point is to select the right recovery version for your bootloader/ROM. As you are going to install a 4.2 ROM, I suggest TWRP 2.5.0.0-42. Not the latest, but proven and stable. Make sure to pick the -42 version matching your bootloader. The next point is: don't use the wipe data option on the bootloader screen, but use the wipe options in recovery instead.
If you follow these two points, you avoid most of the issues that get reported over and over again.
Sent from my TF300T using Tapatalk
f69m said:
The most important point is to select the right recovery version for your bootloader/ROM. As you are going to install a 4.2 ROM, I suggest TWRP 2.5.0.0-42. Not the latest, but proven and stable. Make sure to pick the -42 version matching your bootloader. The next point is: don't use the wipe data option on the bootloader screen, but use the wipe options in recovery instead.
If you follow these two points, you avoid most of the issues that get reported over and over again.
Sent from my TF300T using Tapatalk
Click to expand...
Click to collapse
Hello
Thank you for replying. I am very green at all this and I don't want to mess things up. You mention getting a matching boot loader. How do I check what bootloader I posses and where do I find the correct stuff?
I now next to nothing about this process other than bricking my Samsung Ace phone a year ago and I have not dabbled in this since then. I am willing to get my hands dirty but I want to know how to get out of trouble should I do something stupid, which will most definitely happen.
Are you able to post a link to a tutorial that will help me out?
Cheers
the lemming said:
Thank you for replying. I am very green at all this and I don't want to mess things up. You mention getting a matching boot loader. How do I check what bootloader I posses and where do I find the correct stuff?
Click to expand...
Click to collapse
You can see the version of your bootloader at the top left of the bootloader screen. It should match the last Asus stock ROM version you installed: 10.6.1.27.5 in your case. This is the latest bootloader available and should work fine with all up-to-date 4.2 ROMs. Read the first post carefully, it should mention, which bootloader versions are supported. No nee to update.
Note that flashing custom ROMs will not touch your existing bootloader.
I now next to nothing about this process other than bricking my Samsung Ace phone a year ago and I have not dabbled in this since then. I am willing to get my hands dirty but I want to know how to get out of trouble should I do something stupid, which will most definitely happen.
Click to expand...
Click to collapse
Have a look at nvflash flatline for your bootloader 4.2. It allows you to extract some files from your device. If you keep those safe, you are almost brick-safe, as you can then use nvflash to recover your tablet from most known issues.
http://forum.xda-developers.com/showthread.php?t=2545610
Are you able to post a link tersion o a tutorial that will help me out?
Click to expand...
Click to collapse
I am not aware of a guide specifically for flashing custom ROMs, but most ROMs should have good instructions in the first post. Anyhow, you can browse the stickies in the General forum. They have a lot of good information.
Sent from my TF300T using Tapatalk
So, I did a stupid thing this morning. I spent the last, probably, five hours backing up all of my apps and data from my TF300, and once that was all done, I wiped the data on my tablet. "What makes that stupid?" What makes that stupid is, it was a miracle that I ever actually managed to root this thing in the first place, and now, I don't know a) if it's still rooted (I doubt it), and b) if I'm even mentally capable of rooting it again (I doubt it).
So, here's my situation, and if someone could just dumb down the steps for me and point me in the right direction, that's all I need. I got my tablet, I don't know, probably early 2012. I can tell you that the tablet is on ICS 4.0.3, and the build number is 9.4.3.29-20120511. It's also unlocked, I don't know if that needed to be mentioned. Now, things are better since I wiped the data on this mother, but ICS, on this tablet in particular, is slow as balls, and I'm done with it, I want KitKat. But I am so far beyond lost after what I did that if I try to work my own way out of it, I'm going to brick this thing.
I wiped the data because I was trying to do something involving the Fastboot menu or something like that. Whenever I selected the USB icon and hit up on the volume strip, the tablet just locks cold. I figured whatever caused that, would probably go away with a data wipe. It didn't. So now my data's gone, my apps are gone, my tablet's not rooted anymore, I have no idea how to get to KitKat, I can't sleep at night, it burns when I pee... let's focus on the tablet stuff for now, I'm signed up to some forums for the other stuff.
I know most of the people that read this topic will be inclined to say, "You're an idiot, read this, this, and this, and take care of it yourself." I know I'm Androidiot, and I'm humbly asking for help. Again, I'm just petrified of following the wrong topic and ruining the whole thing, so if someone could tell me how I'd go about upgrading my tablet from stock ICS to KitKat, I'd appreciate the hell out of it.
Just a little bump, not too big... no love for Tim?
Normally, you need to install the latest stock ROM from ASUS in order to recover a functional device & by the way upgrade your bootloader.
Things done, you can proceed to install recovery and kitkat.
Better explanations here : http://forum.xda-developers.com/showpost.php?p=53738192&postcount=2
zlazaar said:
Normally, you need to install the latest stock ROM from ASUS in order to recover a functional device & by the way upgrade your bootloader.
Things done, you can proceed to install recovery and kitkat.
Better explanations here : http://forum.xda-developers.com/showpost.php?p=53738192&postcount=2
Click to expand...
Click to collapse
Thank you, Zlazaar!
Well, it seems that after my device was wiped, it still didn't remove CWM as a bootloader or whatever, I don't know what I'm saying. When I hold down the power and volume down buttons, I could wait like ten seconds for fastboot, or I could tap vol up to enter the "RCK" menu. I don't know what that means. But I go into it, and I'm at the CWM menu, I think it was 5.5.0.4. You probably know better than me if I need to do anything further than that with CWM, but I should be good on that, right?
I'm almost going to go to the sites that you mentioned to download files and get more information on how to use it all. I appreciate your help, because without it, I'm sitting on an unrooted stock ROM with only most of my apps, because oh yeah, like 70 apps forgot to transfer with that backup I did... so, whoopee.
Thank you again, buddy!
The goal is kitkat, right ?
So, in order to get it you need 2 important things :
1- The latest bootloader, yours can't handle kitkat.
2- a custom recovery supporting kitkat, i.e i'm using TWRP 2.7.1.0 (link in my signature), your CWM is outdated.
The only way i know to update the bootloader is to flash Stock ROM via fastboot as described in tutorial.
I got some really stupid questions... apparently it's been entirely too long since I've messed with any of this.
What's a bootloader? I know mine's unlocked, but I didn't know there were versions of it. Is it the blob file I got from Asus?
And I have my tablet hooked up to my PC, it's on the fastboot menu wait for input from USB. When I go to the command prompt, I've tried to push TWRP to the device, but when I start a command with "adb push," it just tells me that it doesn't know what to do with that command. Same thing happened with fastboot, but then I realize I didn't have fastboot installed, so I tried to install it and it complained about a missing dll file on my computer, and I think I'm about ready to give up. lol
Here is the driver : Universal Naked Driver
After install, you can use fastboot and complet other steps.
Tim 13 said:
I got some really stupid questions... apparently it's been entirely too long since I've messed with any of this.
What's a bootloader? I know mine's unlocked, but I didn't know there were versions of it. Is it the blob file I got from Asus?
And I have my tablet hooked up to my PC, it's on the fastboot menu wait for input from USB. When I go to the command prompt, I've tried to push TWRP to the device, but when I start a command with "adb push," it just tells me that it doesn't know what to do with that command. Same thing happened with fastboot, but then I realize I didn't have fastboot installed, so I tried to install it and it complained about a missing dll file on my computer, and I think I'm about ready to give up. lol
Click to expand...
Click to collapse
Ok Tim so the GOAL IS: 4.4 KITKAT CORRECT?
This is the process overview. This is a review.
Step 1 Upgrade the bootloader. Why? Inorder to flash a 4.4 rom you need a Jelly Bean 4.2 bootloader. How? Do as zlazarr suggests by flashing the lastest stock version V10.6.1.27.5 on your tf300t. Flashing the latest stock rom will update your bootloader. And here's another helpful guide.
http://www.theandroidsoul.com/how-to-restore-asus-transformer-tf300t-back-to-stock/ Remember that the SKU has to match!
Step 2 Follow this guide.
http://www.transformerforums.com/fo...nstall-roms-tf300-jelly-bean-kitkat-roms.html
It guides you on how to unlock your bootloader which you already have and it shows you how to install twrp. After installing twrp MAKE A BACKUP!
NOTE: If using the command method on the link fails repetitively use the app rashr to install the twrp version in the link
Step 3 Upgrade twrp to vr 2.7.0.0 or higher. Refer to step 2 link on the post about 4.4 kitkat.
Step 4 Install a 4.4 kk rom. I recomend the lastest snapshot of Cyanogen Mod 11. The download is on their wiki.
And then your done! Don't give up! The hardest part I find is using the command prompt! Look for work arounds. AND SEARCH FOR METHODS!
Goodluck
b..c said:
Ok Tim so the GOAL IS: 4.4 KITKAT CORRECT?
This is the process overview. This is a review.
Step 1 Upgrade the bootloader. Why? Inorder to flash a 4.4 rom you need a Jelly Bean 4.2 bootloader. How? Do as zlazarr suggests by flashing the lastest stock version V10.6.1.27.5 on your tf300t. Flashing the latest stock rom will update your bootloader. And here's another helpful guide.
http://www.theandroidsoul.com/how-to-restore-asus-transformer-tf300t-back-to-stock/ Remember that the SKU has to match!
Step 2 Follow this guide.
http://www.transformerforums.com/fo...nstall-roms-tf300-jelly-bean-kitkat-roms.html
It guides you on how to unlock your bootloader which you already have and it shows you how to install twrp. After installing twrp MAKE A BACKUP!
NOTE: If using the command method on the link fails repetitively use the app rashr to install the twrp version in the link
Step 3 Upgrade twrp to vr 2.7.0.0 or higher. Refer to step 2 link on the post about 4.4 kitkat.
Step 4 Install a 4.4 kk rom. I recomend the lastest snapshot of Cyanogen Mod 11. The download is on their wiki.
And then your done! Don't give up! The hardest part I find is using the command prompt! Look for work arounds. AND SEARCH FOR METHODS!
Goodluck
Click to expand...
Click to collapse
Okay, so I've started work on this finally, but I think I might be having some trouble. I flashed the latest stock ROM onto my baby and restarted the tab like the article said, but now it's taking a very long time to load. I don't know if it's supposed to be taking this long, considering I'm pretty sure it wiped the data on it (flashing a ROM wipes data, doesn't it?), so I'd assume that removing the weight of those apps would make startup lightning quick.
I have the ASUS logo and the spinny circle. And it's just spinning and spinning and spinning and spinning. Is this a problem?
I'm going to let it spin spin spin spin spin for like five more minutes, and then I might go cry for a while.
EDIT: I cried too soon, it loaded for a long time then came to a menu that says "Android is upgrading..." and it's optimizing the apps, or apptimizing, that were apparently NOT wiped when I flashed a new ROM. lol, so I'm back on track. So far, so good. Thank you for the detailed guide, I appreciate it!
Further edit: And I'm also done rooting and flashing to KK 4.4. Thank you for dumbass-proofing the process for me, it is incredibly highly appreciated. I didn't kill my tablet!
Tim 13 said:
Okay, so I've started work on this finally, but I think I might be having some trouble. I flashed the latest stock ROM onto my baby and restarted the tab like the article said, but now it's taking a very long time to load. I don't know if it's supposed to be taking this long, considering I'm pretty sure it wiped the data on it (flashing a ROM wipes data, doesn't it?), so I'd assume that removing the weight of those apps would make startup lightning quick.
I have the ASUS logo and the spinny circle. And it's just spinning and spinning and spinning and spinning. Is this a problem?
I'm going to let it spin spin spin spin spin for like five more minutes, and then I might go cry for a while.
EDIT: I cried too soon, it loaded for a long time then came to a menu that says "Android is upgrading..." and it's optimizing the apps, or apptimizing, that were apparently NOT wiped when I flashed a new ROM. lol, so I'm back on track. So far, so good. Thank you for the detailed guide, I appreciate it!
Further edit: And I'm also done rooting and flashing to KK 4.4. Thank you for dumbass-proofing the process for me, it is incredibly highly appreciated. I didn't kill my tablet!
Click to expand...
Click to collapse
Hi Tim13,
I'm glad to hear that everything went well and my guide helped you!:good: And to answer your question flashing doesn't wipe your data. You have to manually wipe it. And lol:laugh::good: that you didn't kill your tab. I hope you find your tab faster and useful again!
It's just as slow and useless as it was. But honestly, the flashing process was fun, and I learned from it. Plus, TWRP and Cyanogen mod are awesome, and now I know that. lol
Great to see you up and running @Tim 13 :good:
Can you add SOLVED to the thread title
Thx Josh
No, I'm not gonna do that.
I'm just kidding. You're all right, darling. :good:
Edit: Actually, not being a douche, I can't figure out how to edit the thread title. I went to edit the first post and I can't change the title of the post... I'm gonna look around for how to do it a bit more but after that I'm gonna go to bed.
DOUBLE EDIT: Got it, as you can see. Thanks to all that helped out!