Database Info

Upgrading from 4.1 to 4.2

I have looked everywhere for help on this subject.
I have rooted my tf300t with unlocked boot loader 4.1, but what are the steps to upgrade to 4.2? I want the latest roms but im stuck with the old 4.1
Do I need to update my TWRP first? I have an old version
If there is a link to show me how please post if not let me know please...im desperate and im going away to Dubai for the xmas period

Found the solution. Please close this thread

olster said:
Found the solution. Please close this thread
Click to expand...
Click to collapse
Could you provide solution please?

Tunameltsalad said:
Could you provide solution please?
Click to expand...
Click to collapse
One way is to use fastboot to flash the latest 4.2 stock ROM. The bootloader is also upgraded in the process. Then you flash the 4.2 TWRP and whatever ROM you want from there.

cmendonc2 said:
One way is to use fastboot to flash the latest 4.2 stock ROM. The bootloader is also upgraded in the process. Then you flash the 4.2 TWRP and whatever ROM you want from there.
Click to expand...
Click to collapse
I've used fastboot before, but a little more info - where can we find the 4.2 stock ROM? I followed a few links off this forum that took me to ASUS support page that stated you must select your OS (which there was no option).
Is there a thread dedicated to this?
I'm sitting on CleanROM (my Aunts), and over time, I guess this thing runs like a pig (so does my mom's stock 4.2 tablet). I am looking to make these two devices actually useful again.

majorpay said:
I've used fastboot before, but a little more info - where can we find the 4.2 stock ROM? I followed a few links off this forum that took me to ASUS support page that stated you must select your OS (which there was no option).
Is there a thread dedicated to this?
I'm sitting on CleanROM (my Aunts), and over time, I guess this thing runs like a pig (so does my mom's stock 4.2 tablet). I am looking to make these two devices actually useful again.
Click to expand...
Click to collapse
I went through this link and I was able to select the OS and then firmware version to download.:
http://www.asus.com/us/supportonly/ASUS%20Transformer%20Pad%20TF300T/HelpDesk_Download/

cmendonc2 said:
I went through this link and I was able to select the OS and then firmware version to download.:
http://www.asus.com/us/supportonly/ASUS%20Transformer%20Pad%20TF300T/HelpDesk_Download/
Click to expand...
Click to collapse
OK, so with this 4.1 modded tablet, if I take the latest version of 4.2, grab the blob, and do the following:
Code:
fastboot -i 0x0B05 flash system blob
fastboot -i 0x0B05 reboot
Is that going to work, or am I going to end up with a brick?
I know that there has been some warnings on upgrading to 4.1 with 4.2 files, so I want to double check before I make a bookend out of this thing.
EDIT: Pulled the trigger - worked out fine. Now I will install a recovery and we'll be good to go!

[Q] Flashing Stock from CMB

I am currently running the CMB r2c1
I am attempting to move to the stock rom (deodexed and rooted http://forum.xda-developers.com/showthread.php?t=2608129), but I am having issues getting the stock rom from asus to flash using twrp.
tried the WW and the US version along with the SD version. I've tried the full zip and unzipping as well. All fail.
Anyone have any suggestions on how to flash the stock rom? I

xnosajx said:
I am currently running the CMB r2c1
I am attempting to move to the stock rom (deodexed and rooted http://forum.xda-developers.com/showthread.php?t=2608129), but I am having issues getting the stock rom from asus to flash using twrp.
tried the WW and the US version along with the SD version. I've tried the full zip and unzipping as well. All fail.
Anyone have any suggestions on how to flash the stock rom? I
Click to expand...
Click to collapse
Asus seems to sign the stock firmware zips this time around and CWM, and now it seems also TWRP can't flash it anymore. Which TWRP version did you try it with?
Why do you want to flash stock? To get to the 4.3 bootloader?
Right now the only solution seems to be to flash the stock revovery in fastboot, apply the update to 4.3, flash custom recovery again and install rom.
I look for the link to the stock recovery and post it in an edit.
Edit: http://droidbasement.com/db-blog/?p=3210
Sent from my DROID4 using Tapatalk

berndblb said:
Asus seems to sign the stock firmware zips this time around and CWM, and now it seems also TWRP can't flash it anymore. Which TWRP version did you try it with?
Why do you want to flash stock? To get to the 4.3 bootloader?
Right now the only solution seems to be to flash the stock revovery in fastboot, apply the update to 4.3, flash custom recovery again and install rom.
I look for the link to the stock recovery and post it in an edit.
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
Thanks for the help.
I do want to get to the 4.3 bootloader so that I can get to a different Rom. I will try the steps you have listed and let you know.

xnosajx said:
Thanks for the help.
I do want to get to the 4.3 bootloader so that I can get to a different Rom. I will try the steps you have listed and let you know.
Click to expand...
Click to collapse
Just for future reference - because this is going to come up again and again - you did follow proper procedure:
Unzipped the downloaded firmware once and then tried to flash the resulting zip in TWRP?
And please: Which TWRP version?
Hint: There's a "Thanks" button at the bottom of each post for a reason

berndblb said:
Just for future reference - because this is going to come up again and again - you did follow proper procedure:
Unzipped the downloaded firmware once and then tried to flash the resulting zip in TWRP?
And please: Which TWRP version?
Hint: There's a "Thanks" button at the bottom of each post for a reason
Click to expand...
Click to collapse
I tried both zips: once without unzipping and once with. I am unsure of the twrp version I was using, because I flashed CWM right after I posted the original question. Going through my bookmarks that I created when I first went to CMB rom, it looks like it was 2.6.
I am still attempting to get the stock recovery flashed with no success. I tried the fastboot method, and it seems to work except that when I reboot, it still comes up with CWM. It also stops blinking on the RCK icon when it installs (kinda hangs). I tried fastboot devices and it shows me the following:
???????????? fastboot
I may have to come back and try again in the morning. I am falling asleep while typing.

xnosajx said:
I tried both zips: once without unzipping and once with. I am unsure of the twrp version I was using, because I flashed CWM right after I posted the original question. Going through my bookmarks that I created when I first went to CMB rom, it looks like it was 2.6.
I am still attempting to get the stock recovery flashed with no success. I tried the fastboot method, and it seems to work except that when I reboot, it still comes up with CWM. It also stops blinking on the RCK icon when it installs (kinda hangs). I tried fastboot devices and it shows me the following:
???????????? fastboot
I may have to come back and try again in the morning. I am falling asleep while typing.
Click to expand...
Click to collapse
Yep - good idea to quit if you are tired!
The return you get on 'fastboot devices' means your fastboot drivers are not working/incorrect.
If you issue the command
Code:
fastboot devices
the return has to be a long string of numbers and letters. Anything else, especially ???????, and no fastboot command will have any effect.
Depending on the PC you are using, find the correct drivers, which may be the Google Universal Naked drivers, install them and troubleshoot until you get a working fastboot connection.
Everything after that should be a breeze.....

Looks to me like you have tried to flash a TF701 ROM onto the TF700.
Try CROMi-X 5.3 instead.

berndblb said:
Yep - good idea to quit if you are tired!
The return you get on 'fastboot devices' means your fastboot drivers are not working/incorrect.
If you issue the command
Code:
fastboot devices
the return has to be a long string of numbers and letters. Anything else, especially ???????, and no fastboot command will have any effect.
Depending on the PC you are using, find the correct drivers, which may be the Google Universal Naked drivers, install them and troubleshoot until you get a working fastboot connection.
Everything after that should be a breeze.....
Click to expand...
Click to collapse
I should have been more specific. Before I attempt the install of the recovery, I get this when I do fast boot devices:
Code:
C:\>fastboot devices
###d2bbce61c### fastboot
The #'s are actual numbers.
After I try to install the recovery image here is the output:
Code:
C:\>fastboot flash recovey recovery.img
sending 'recovery' (8192 KB)...
OKAY [ 3.588s]
writing 'recovery'...
OKAY [ 3.182s]
finished. total time: 6.770s
C:\>fastboot devices
???????????? fastboot
c:\>
And the green flashing (around the icons) stops and hangs.
I have to hold down power to reboot after that.

sbdags said:
Looks to me like you have tried to flash a TF701 ROM onto the TF700.
Try CROMi-X 5.3 instead.
Click to expand...
Click to collapse
I'm an idiot...thanks. I'll try the CROMi-X 5.3

[Q] Help with ROM needed (maybe trivial ...)

Oh my ... I have now spent sure 6 or 7 hours trying to figure this out. If anybody could help me, please ?
This is not my first attempt at root, and I have been succesful with my HTC Wildfire S and installed various Custom ROMs on that, all fine.
Now I have a Desire S, that I managed to unlock (UNLOCKED), which is still S-ON, and, from all I can tell, rooted (superuser app does not complain about anything), I had installed 4EXT on the HTC Sense Stock rom that came with the phone, and that installed fine and no complaints.
HBOOT is 2.02.0002, which many people say requires downgrading, but then in other places it is said, this is not strictly necessary.
Now the following:
The ONLY recovery I have been able to install is recovery-clockwork-5.0.2.0-saga.img (using adb flash recovery ... under ubuntu 12.04).
That seems to go well, and the CM recovery comes up fine and I can do backups and so on. If I try to flash 4EXT_Recovery_Touch_v1.0.0.5_RC5 or RC9 and go into recovery, the phone remains stuck in the white boot screen (Telekom branding, it seems). Oh well ... so no 4EXT and back to CM. No problem, just strange.
Now, with S-ON it SHOULD be possible to install custom ROMs, like flinnycm101_saga_22.zip. so i pushed this onto /sdcard, and also extracted the boot.img from this zip. In recovery I can install the .zip seemingly fine, no errors, and then, since this is S-ON, I
sudo adb flashboot flash boot flinnycm101_saga_22.img
(i renamed it from boot.img to that to keep track, should not be a problem, right?). and that goes over well, too. I do not know how many times I have already erased cache, dalvik, factory, battery. all to no avail. when i reboot the phone remains stuck in the white boot screen. at least i would have expected to get the CM spash screen (like that rotating wheel or something like that), but that may not be a problem.
I have tried a few other roms (devilkin 11.0 and carbon) with this method. same, same ...
I really don't know ... sheesh ... any ideas ? And if it boils down to downgrading: can I do that on ubuntu ? All the guides I have found so far required Windows.
Sorry ... clearly I am not a developer. If somebody could nudge me into the right direction ? I am quite happy to do my homework, but not really sure anymore where else to look. This SHOULD work, from all I found in the internet.
And ... I hope this is not the wrong forum. If so, really sorry ...
1000 thanks
Ingo

ipk1 said:
Oh my ... I have now spent sure 6 or 7 hours trying to figure this out. If anybody could help me, please ?
This is not my first attempt at root, and I have been succesful with my HTC Wildfire S and installed various Custom ROMs on that, all fine.
Now I have a Desire S, that I managed to unlock (UNLOCKED), which is still S-ON, and, from all I can tell, rooted (superuser app does not complain about anything), I had installed 4EXT on the HTC Sense Stock rom that came with the phone, and that installed fine and no complaints.
HBOOT is 2.02.0002, which many people say requires downgrading, but then in other places it is said, this is not strictly necessary.
Now the following:
The ONLY recovery I have been able to install is recovery-clockwork-5.0.2.0-saga.img (using adb flash recovery ... under ubuntu 12.04).
That seems to go well, and the CM recovery comes up fine and I can do backups and so on. If I try to flash 4EXT_Recovery_Touch_v1.0.0.5_RC5 or RC9 and go into recovery, the phone remains stuck in the white boot screen (Telekom branding, it seems). Oh well ... so no 4EXT and back to CM. No problem, just strange.
Now, with S-ON it SHOULD be possible to install custom ROMs, like flinnycm101_saga_22.zip. so i pushed this onto /sdcard, and also extracted the boot.img from this zip. In recovery I can install the .zip seemingly fine, no errors, and then, since this is S-ON, I
sudo adb flashboot flash boot flinnycm101_saga_22.img
(i renamed it from boot.img to that to keep track, should not be a problem, right?). and that goes over well, too. I do not know how many times I have already erased cache, dalvik, factory, battery. all to no avail. when i reboot the phone remains stuck in the white boot screen. at least i would have expected to get the CM spash screen (like that rotating wheel or something like that), but that may not be a problem.
I have tried a few other roms (devilkin 11.0 and carbon) with this method. same, same ...
I really don't know ... sheesh ... any ideas ? And if it boils down to downgrading: can I do that on ubuntu ? All the guides I have found so far required Windows.
Sorry ... clearly I am not a developer. If somebody could nudge me into the right direction ? I am quite happy to do my homework, but not really sure anymore where else to look. This SHOULD work, from all I found in the internet.
And ... I hope this is not the wrong forum. If so, really sorry ...
1000 thanks
Ingo
Click to expand...
Click to collapse
From what I see you done it as needed.
First for recovery try find 4ext touch 1.0.0.6 RC1 and try to flash via fastboot ( fastboot flash recovery recovery.img).If you don't get in try TWRP 2.7.0.0 by devil-kin you got it in this forum.
About white screen you should check your display.There's sony and hitachi.If you have sony then you are good and something else is problem but hitachi is problem bc you need MDDI capable kernel or use only CM 7 or older roms.
Read this about that problem http://forum.xda-developers.com/showthread.php?t=1943524
GL.

Hello!
I find it strange that you're experiencing so many issues while for everybody else things are just fine. I'm not trying to accuse you of anything, it just makes me think that your problems are likely to be on your end...
You don't need to do anything with your hboot, it's fine
Are you sure that flashing www.4ext.net/ddl/saga/recovery.zip using
Code:
fastboot flash recovery recovery.img
doesn't work?
sudo adb flashboot flash boot flinnycm101_saga_22.img
Click to expand...
Click to collapse
This is wrong - should be:
Code:
flashboot flash boot flinnycm101_saga_22.img
But first try:
Code:
flashboot boot flinnycm101_saga_22.img
That will just boot the image from RAM without flashing it to /boot. I recommend trying this out first with this ROM - http://forum.xda-developers.com/showthread.php?t=2240592 - because that ROM is known good. If that works then we know the procedure you use is OK and you can then try to flash a ROM you actually like.
Note that AOSP roms may be problematic, because they only work with sony panels. We can check whether you have a sony or a hitachi panel once you have a ROM booting properly. (Unless there is a fastboot command that can tell you this that I'm not aware of.)
And ... I hope this is not the wrong forum. If so, really sorry ...
Click to expand...
Click to collapse
It is - questions should be posted in the Questions subforum :silly:

SKENER said:
From what I see you done it as needed.
First for recovery try find 4ext touch 1.0.0.6 RC1 and try to flash via fastboot ( fastboot flash recovery recovery.img).If you don't get in try TWRP 2.7.0.0 by devil-kin you got it in this forum.
About white screen you should check your display.There's sony and hitachi.If you have sony then you are good and something else is problem but hitachi is problem bc you need MDDI capable kernel or use only CM 7 or older roms.
Read this about that problem http://forum.xda-developers.com/showthread.php?t=1943524
GL.
Click to expand...
Click to collapse
all right. thanks. i found that recovery and did
sudo fastboot flash recovery 4EXT_Recovery_Touch_v1.0.0.6_RC1.img
when i go into recovery then, again nothing ... phone is stuck in the white screen. sorry. with white screen i meant the splash screen, which is white on my phone, but has the telecom logo. so i think the screen is allright.
so i pulled the battery and back to cwm (flashed the cms recovery and voila).

Aquous said:
Hello!
I find it strange that you're experiencing so many issues while for everybody else things are just fine. I'm not trying to accuse you of anything, it just makes me think that your problems are likely to be on your end...
Click to expand...
Click to collapse
absolutely. that's why i came here. the phone was fine under htc sense, so its not the phone. it got to be me.
Aquous said:
You don't need to do anything with your hboot, it's fine
Click to expand...
Click to collapse
Good.
Aquous said:
Are you sure that flashing www.4ext.net/ddl/saga/recovery.zip using
Code:
fastboot flash recovery recovery.img
doesn't work?
This is wrong - should be:
Code:
flashboot flash boot flinnycm101_saga_22.img
Click to expand...
Click to collapse
oh. typo. sorry.
Aquous said:
But first try:
Code:
flashboot boot flinnycm101_saga_22.img
Click to expand...
Click to collapse
This boots into recovery. But not exactly. It boots to the white Telekom screen, and then it reboots and goes into recovery. Since I found that strange I extracted the boot image once more from the flinny...zip and tried again. confirmed.
Aquous said:
That will just boot the image from RAM without flashing it to /boot. I recommend trying this out first with this ROM - http://forum.xda-developers.com/showthread.php?t=2240592 - because that ROM is known good. If that works then we know the procedure you use is OK and you can then try to flash a ROM you actually like.
Click to expand...
Click to collapse
Downloading. This is "SVHD v2.1.0 by mygamers (MultiDevice)", right ? The thing is huge. That's gonna take a bit and I have to go to work. Get back to you later ...
Aquous said:
Note that AOSP roms may be problematic, because they only work with sony panels. We can check whether you have a sony or a hitachi panel once you have a ROM booting properly. (Unless there is a fastboot command that can tell you this that I'm not aware of.)
It is - questions should be posted in the Questions subforum :silly:
Click to expand...
Click to collapse
I extracted the boot.img
Can somebody move this ?

SKENER said:
From what I see you done it as needed.
First for recovery try find 4ext touch 1.0.0.6 RC1 and try to flash via fastboot ( fastboot flash recovery recovery.img).If you don't get in try TWRP 2.7.0.0 by devil-kin you got it in this forum.
GL.
Click to expand...
Click to collapse
4ext touch 1.0.0.6 RC1, same problem. stuck at the white telekom screen.
twrp-2.7.0.0-saga-recovery.img, same problem.
but openrecovery-twrp-2.6.3.0-saga.img did work
Ingo

Aquous said:
I recommend trying this out first with this ROM - http://forum.xda-developers.com/showthread.php?t=2240592 - because that ROM is known good.
Click to expand...
Click to collapse
tdDDAAA !!!
So I installed the SVHD .zip with TWRP 2.6 (see above) and that did go nowhere yet.
But I then extracted the saga boot image from that zip kernel/saga/boot.img, renamed that to avoid confusions, and then
<code>
fastboot boot "SVHD v2.1.0 by mygamers (saga).img"
</code>
And my Telekom splash screen blinks up, then the HTC sense (quietly brilliant), and some 3 minutes later ... it worked.
Flashing
<code>
fastboot flash boot "SVHD v2.1.0 by mygamers (saga).img"
</code>
MY guess is it was the reformatting to ext4 ... is that something I should have done all along ? Or any other idea ?

Now you have a working phone, you can check which panel type you have, I suspect that has been your problem all along.
Edit: check this thread:
http://forum.xda-developers.com/showthread.php?t=1943524

teadrinker said:
Now you have a working phone, you can check which panel type you have, I suspect that has been your problem all along.
Edit: check this thread:
http://forum.xda-developers.com/showthread.php?t=1943524
Click to expand...
Click to collapse
Yeah,check panel now.Some phones has that problem.If you have hitachi then I'm sorry.From what I know no1 make MDDI kernel anymore.

teadrinker said:
Now you have a working phone, you can check which panel type you have, I suspect that has been your problem all along.
Edit: check this thread:
http://forum.xda-developers.com/showthread.php?t=1943524
Click to expand...
Click to collapse
Must be, since I tried to install blindnnumbs cm now, and same problem, again ... Good ... so back to SVHD and check that thread. Thanks.
Ingo

One more thing:
On the link you provided the instructions are given as follows, and i am not 100% clear on everything:
1) Wipe all data
2) Flash your custom ROM
3) Get your MDDI compatible kernel and flash it
--> IF (and only IF) you've this error when flashing kernel in recovery: assert failed:write_raw_image("/tmp/boot.img","boot"):
--> 3a) extract boot.img from custom rom ZIP and put it in the adb directory on your PC
--> 3b) reboot in fastboot mode
--> 3c) execute from PC: fastboot flash boot.img
--> 3d) reboot in recovery and retry to flash your new kernel
--> 3e) Now, flashing kernel is completed and you can continue to Step 4)
4) Get new boot.img: in recovery, attach USB cable and run from PC terminal --> adb pull /tmp/newboot.img (it will trasfer generated boot.img to your PC) <--
5) On your PC rename newboot.img file to boot.img
6) Reboot in fastboot mode
7) Install new boot.img (from PC terminal execute --> fastboot flash boot.img <--)
So I
- in twrp i installed cm-10.1-20130709-UNOFFICIAL-saga.zip (blindnnumb cm-10.1, penultimate version. the very last version does not unzip, no matter how many times i download it)
- then flashed fastboot flash boot cm-10.1-20130709-UNOFFICIAL-saga.img
- then flashed fastboot flash boot saga_mddi_291212.img (from your link)
- i pulled newboot.img and then flashed newboot.img
and i am stuck again ... but maybe i did not totally understand the instruction from above ? i.e. 2). do i need to install the zip and the img ?
also in line 7) the command seems to be wrong. right ?
ingo

If you already have a boot.img for the mddi kernel, all you have to do is:
1) flash rom zip file in recovery
2) flash mddi kernel zip in recovery
3) flash mddi kernel boot.img in fastboot
The special instructions for s-on are only needed if you have the kernel zip without the boot.img

teadrinker said:
If you already have a boot.img for the mddi kernel, all you have to do is:
1) flash rom zip file in recovery
2) flash mddi kernel zip in recovery
3) flash mddi kernel boot.img in fastboot
The special instructions for s-on are only needed if you have the kernel zip without the boot.img
Click to expand...
Click to collapse
Oh my ... that did not go either. Now I flashed
cm-10-20121116-EXPERIMENTAL-saga-NK111.zip
saga_kernel_82n_4.0_4.1.zip (which does not seem to produce a newboot.img, and does not have a boot.img either)
that, at least, brings up the spinning clockworkmod wheel ... but then that's that, too ...
oh well ... i guess SENSE it is gonna be then ...
ingo

Didn't you read the warning at the top of the hitachi panel thread? It said:
WARNING!
ALL THE LATEST 4.1.x AND 4.2.x ROMS DO NOT SUPPORT HITACHI SCREEN PANELS, EVEN AFTER APPLYING THE CORRECT MDDI KERNEL!
THIS APPLIES TO ROMS THAT ARE BASED ON AOSP, AOKP, CyanogenMod, ParanoidAndroid, PAC-Man, etc., AND ROMS THAT ARE BASED ON MIUI
THE LAST CUSTOM ROM THAT DOES SUPPORT MDDI PANELS IS CyanogenMod 10.1 Build 13 by Flinny, SO THE DATE WHEN BUILD 13 WAS RELEASED IS YOUR GUIDE TO CHOOSE THE CORRECT ROM THAT WILL BOOT UP AFTER FLASHING THE MDDI KERNEL
Click to expand...
Click to collapse

Aquous said:
Didn't you read the warning at the top of the hitachi panel thread? It said:
Click to expand...
Click to collapse
Read it ... and I think I did not understand it right ... I guess I got too tired over it. I thought I had one that should match those criteria. Tomorrow is another day ...
Ingo

(Solved) Soft-bricked, but unable to flash anything but CWM.

Hello, I seem to have soft bricked my tf700.
​I flashed a newish pacman nightly in CWM (after wiping data/cache/dalvik cache), which completed with no errors, then I flashed the corresponding GAPPS. But my device became stuck in the pacman boot intro.
​So I tried flashing slimkat which led to my device not getting past the first bootup screen (where you can enter recovery if pressing the corresponding buttons).
​After this screw-up I stupidly hit the wipe data button on the bootloader. I then tried doing the method of using fastboot to erase system, cache, and all that so I could flash system blob of the newest asus US SKU (that is correct for a US bought tf700 right?). Either this or wiping the data caused me to have a different bootloader as pictured below as I no longer have the android button and it does not ask me to press volume up to access recovery (the only way to access recovery is by hitting the wipe data button in bootloader).
​I can still fastboot flash CWM, but trying to flash TWRP does not work as it finishes but going into recovery causes the tablet to just restart. Trying to flash asus stock as above would always give me an error like the one pictured below. Similar errors occur if trying to flash any rom inside CWM via an external sd card.
​I do not have access to adb as i believe i dont have usb debugging enabled since the pacman rom or any other rom did not ever start. It just gives me the device not found error even after manually installing the drivers on two different computers.
Cant seem to get these pics to load, but copying the url and pasting it works.
http://imgur.com/AaU0GMt
http://imgur.com/vDTVa4B

You probably flashed the wrong Rom. Try flashing the >right< stock Rom and go from there. Double check everything you flash.

tylerleo said:
You probably flashed the wrong Rom. Try flashing the >right< stock Rom and go from there. Double check everything you flash.
Click to expand...
Click to collapse
Whats the "right" rom here? Talking about the original asus stock rom? I have now tried the the pacman nightly, pacman release, slim kat release, clean rom release, an ICS asus stock rom, and two different versions of the jellybean asus stock rom. These were either done in CWM via internal sd card, external sd card, or done through fastboost flash system blob and flash zip.

gio3505 said:
Whats the "right" rom here? Talking about the original asus stock rom? I have now tried the the pacman nightly, pacman release, slim kat release, clean rom release, an ICS asus stock rom, and two different versions of the jellybean asus stock rom. These were either done in CWM via internal sd card, external sd card, or done through fastboost flash system blob and flash zip.
Click to expand...
Click to collapse
Whatever Rom came on the device,(Good thing to have, da) I'm not familiar with this device.

tylerleo said:
Whatever Rom came on the device,(Good thing to have, da) I'm not familiar with this device.
Click to expand...
Click to collapse
As far as i know, i have installed the stock rom, or atleast multiple versions of it with no success as it gives me an error stating something like staging or system when trying to write it.

gio3505 said:
As far as i know, i have installed the stock rom, or atleast multiple versions of it with no success as it gives me an error stating something like staging or system when trying to write it.
Click to expand...
Click to collapse
Hmm, I'd Download a stock Rom for the device offline, take on the sd card and put it on there real quick and try to flash that, if not, you probably bricked your device. I wouldn't know how to fix it beyond that. Ask the dev that made the Rom were everything that went south and an email to cwm wouldn't hurt either

I am also not sure if I need to have my external sd card formatted a certain way or download a specific CWM to allow flashing the stock rom. Ive spent over 10 hours trying to figure this out, very frustrating.

I have run CWM 6.0.4.6, CWM 6.0.4.7, and older versions to see if I could flash the stock rom with no luck. I have also tried different versions of TWRP but they always hang and reboot my tf700. I get errors ranging from status 6, status 7, cannot mount data, cannot mount staging, and cannot mount system. I am completely lost on what I can do. I have even tried a seperate sdcard to see if maybe the one I was originally using was bad with no luck. GG :/

gio3505 said:
I have run CWM 6.0.4.6, CWM 6.0.4.7, and older versions to see if I could flash the stock rom with no luck. I have also tried different versions of TWRP but they always hang and reboot my tf700. I get errors ranging from status 6, status 7, cannot mount data, cannot mount staging, and cannot mount system. I am completely lost on what I can do. I have even tried a seperate sdcard to see if maybe the one I was originally using was bad with no luck. GG :/
Click to expand...
Click to collapse
You gotta stop flashing stuff and slow down!
During all of this you never posted your bootloader version, so you may have been on the wrong bootloader to begin with - who knows.
When you hit the Wipe Data in the bootloader menu you caused the BL do write a wipe data command to the misc partition, causing the tablet to boot to recovery each time you booted (I'm guessing here) and then interrupting it. Usually, with CWM installed, it eventually sorts it out and executes the wipe data command, but that takes hours! You just have to leave it alone.
Hard to tell where you are now since you flashed all kinds of stuff since then.
Can you still boot into the bootloader and have a fastboot connection?
What's the BL version number?
If you boot, what does it boot into?
The picture links are broken - at least in Tapatalk. Post them again?

berndblb said:
You gotta stop flashing stuff and slow down!
During all of this you never posted your bootloader version, so you may have been on the wrong bootloader to begin with - who knows.
When you hit the Wipe Data in the bootloader menu you caused the BL do write a wipe data command to the misc partition, causing the tablet to boot to recovery each time you booted (I'm guessing here) and then interrupting it. Usually, with CWM installed, it eventually sorts it out and executes the wipe data command, but that takes hours! You just have to leave it alone.
Hard to tell where you are now since you flashed all kinds of stuff since then.
Can you still boot into the bootloader and have a fastboot connection?
What's the BL version number?
If you boot, what does it boot into?
The picture links are broken - at least in Tapatalk. Post them again?
Click to expand...
Click to collapse
Yes, the pictures are broken. You can still copy paste the url though. Couldnt figure out why it wouldnt work.
The tablet boots into the first screen that states it is unlocked, but does not go any further.
There is no bootloader version on the top left when holding down power + volume down.
I can still get to the place where it allows me to wipe data or fastboot, but the android icon to boot into android is now gone.
adb does not recognize my device even after manually installing the drivers, but fastboot works fine.
Is there any other way to find my bootloader version?

gio3505 said:
Yes, the pictures are broken. You can still copy paste the url though. Couldnt figure out why it wouldnt work.
The tablet boots into the first screen that states it is unlocked, but does not go any further.
There is no bootloader version on the top left when holding down power + volume down.
I can still get to the place where it allows me to wipe data or fastboot, but the android icon to boot into android is now gone.
adb does not recognize my device even after manually installing the drivers, but fastboot works fine.
Is there any other way to find my bootloader version?
Click to expand...
Click to collapse
Maybe you want to edit your post with the urls then.... Makes it easier for people trying to help...
You're seriously messed up, I think. I see a USB icon in there which would indicate that your bootloader is ancient. But then it says: "starting USB fastboot protocol".
Is that after you selected the USB icon?
Anyway, I think you're only chance is buster99's method to get it back. Did you try that already?
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Naturally you have to extract the system blob from the 10.6.1.14.10 US Asus firmware, but then you can try to fastboot flash it with buster's method.
Good luck!

berndblb said:
Maybe you want to edit your post with the urls then.... Makes it easier for people trying to help...
You're seriously messed up, I think. I see a USB icon in there which would indicate that your bootloader is ancient. But then it says: "starting USB fastboot protocol".
Is that after you selected the USB icon?
Anyway, I think you're only chance is buster99's method to get it back. Did you try that already?
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Naturally you have to extract the system blob from the 10.6.1.14.10 US Asus firmware, but then you can try to fastboot flash it with buster's method.
Good luck!
Click to expand...
Click to collapse
Its starts the usb fastboot automatically if no input is selected. I had a different bootloader up until i tried that thing that buster did. It always gives me an error like cant write to system or something if i try it.

gio3505 said:
Its starts the usb fastboot automatically if no input is selected. I had a different bootloader up until i tried that thing that buster did. It always gives me an error like cant write to system or something if i try it.
Click to expand...
Click to collapse
Which blob did you flash with buster's method?
I'm afraid you flashed something totally incompatible with your tablet...
You did not generate your nvflash blobs sometime prior to this, did you?

berndblb said:
Which blob did you flash with buster's method?
I'm afraid you flashed something totally incompatible with your tablet...
You did not generate your nvflash blobs sometime prior to this, did you?
Click to expand...
Click to collapse
I flashed the asus stock rom downloaded from their website. The US version as it was bought in the US (right? 0.o). I hadnt heard of nvflash before trying to install a rom so i did not make a backup.

gio3505 said:
I flashed the asus stock rom downloaded from their website. The US version as it was bought in the US (right? 0.o). I hadnt heard of nvflash before trying to install a rom so i did not make a backup.
Click to expand...
Click to collapse
Are you sure you downloaded the correct firmware? For the TF700?
Do you still have the original zip you extracted the blob from?
Post the exact file name please.

berndblb said:
Are you sure you downloaded the correct firmware? For the TF700?
Do you still have the original zip you extracted the blob from?
Post the exact file name please.
Click to expand...
Click to collapse
US_epaduser10_6_1_14_10_UpdateLauncher (2)
or
US_epaduser_VER104425UpdateLauncher
or
US_epad_user_9_4_5_30_20120907_UpdateLauncher
Ive downloaded a lot of different versions from the asus website. The last one came from a forum post listing older firmware, which I have tried a lot of different ones.

gio3505 said:
US_epaduser10_6_1_14_10_UpdateLauncher (2)
or
US_epaduser_VER104425UpdateLauncher
or
US_epad_user_9_4_5_30_20120907_UpdateLauncher
Ive downloaded a lot of different versions from the asus website. The last one came from a forum post listing older firmware, which I have tried a lot of different ones.
Click to expand...
Click to collapse
You flashed all of those blobs???
In which order?
With what result?
Jeez - I think you're done for...
Sorry mate, but gotta catch some sleep now. Maybe somebody else has a bright idea...

berndblb said:
You flashed all of those blobs???
In which order?
With what result?
Jeez - I think you're done for...
Sorry mate, but gotta catch some sleep now. Maybe somebody else has a bright idea...
Click to expand...
Click to collapse
I flashed the newest one first, and it gave me one of those errors that wouldnt allow me to flash it, and i tried the others with the same result. So technically i didnt flash any of them. I have been able to flash some roms, but they wouldnt boot so i would be stuck where i was when i started.

gio3505 said:
I flashed the newest one first, and it gave me one of those errors that wouldnt allow me to flash it, and i tried the others with the same result. So technically i didnt flash any of them. I have been able to flash some roms, but they wouldnt boot so i would be stuck where i was when i started.
Click to expand...
Click to collapse
Right stop flashing random stuff - you have combinations of JB4.2.1, JB4.1.1 and ICS 4.0.3 just listed there.
Let me put a call out to @lj50036 who may be able to save you but if you have messed the bootloader up with no nvflash backups you are not going to be happy with the result. If you can still get to the bootloader screen then he can perform miraculous superhero acts and *maybe* save your device.

gio3505 said:
I flashed the newest one first, and it gave me one of those errors that wouldnt allow me to flash it, and i tried the others with the same result. So technically i didnt flash any of them. I have been able to flash some roms, but they wouldnt boot so i would be stuck where i was when i started.
Click to expand...
Click to collapse
Shoot me an email at [email protected]
We can use hangouts see if there is a solution to your issue ...
Thx Josh

Best ROM for ASUS TF300T for internet browsing and youtube

Hi everyone!
After three years of a very PAINFUL experience with my TF300T, I was about to throw it out of the window. But I actually thought that I could maybe try to install some custom ROM to make it work better.
The tablet is really almost unusable, because of the fact it is so slow. Youtube videos lags beyond imagination and often the audio desyncronizes with the video itself. Browsing experience is equally sluggish with either the stock browser and chrome.
I would like to ask you guys which ROM you think is the best for these things: Youtube watching and browsing. Of course I could use other apps, but this is the main purpose of the tablet for my actual needings.
I have been reading about Katkiss roms, but there are a few versions around and I really do not know anything about flashing roms and customizing android devices. This would actually be my very first time.
The only thing I did was reverting the tablet to Android 4.1 with the official Asus installation file. After a couple of days, noticing I wasn't experiencing any significant improvement, I let the tablet automatically update again to the latest 4.2 version through the update function.
Considering this, I would also kindly ask you to eventually link me the NOOB PROOF installation guides for the ROMs you will advice me to install. I am quite scared to just destroy the tablet
Thanks in advance to whoever will spend some time to bother answering me! And sorry for any grammar mistake I could have made writing this, english is not my native language.
Francesco

Being on the last Asus firmware update is a good condition to think about installing a custom rom on your tablet. However first of all you have to do your homework as follows:
1. Unlock your boot loader with the Asus unlock tool after download from the Asus web site,
2. Install the custom recovery Kang TWRP [email protected] (http://forum.xda-developers.com/transformer-tf300t/development/recovery-twrp-t3046479). There is also the install instruction!
After done this both successfully you are ready to install one of the best custom rom ever "KatKiss Nougat 7.1 Release" http://forum.xda-developers.com/transformer-tf300t/development/rom-t3453702. Download the latest Rom, Gapps and SuperSu there in post #1. Please follow the install instruction given by the developer in post #1 exactly . After that you will enjoy the new life of your tablet.

ebonit said:
Being on the last Asus firmware update is a good condition to think about installing a custom rom on your tablet. However first of all you have to do your homework as follows:
1. Unlock your boot loader with the Asus unlock tool after download from the Asus web site,
2. Install the custom recovery Kang TWRP [email protected] (http://forum.xda-developers.com/transformer-tf300t/development/recovery-twrp-t3046479). There is also the install instruction!
After done this both successfully you are ready to install one of the best custom rom ever "KatKiss Nougat 7.1 Release" http://forum.xda-developers.com/transformer-tf300t/development/rom-t3453702. Download the latest Rom, Gapps and SuperSu there in post #1. Please follow the install instruction given by the developer in post #1 exactly . After that you will enjoy the new life of your tablet.
Click to expand...
Click to collapse
Thank you for your answer!
I have already downloaded the latest Asus unlock tool (version 8) and I'm waiting for the tablet to charge to 100% before doing anything.
I have also take a good look at the KatKiss Nougat 7.1 version 12 you linked me. I understand this version is quite new, so I guess it could be less stable and optimized than the older Marshmallow version. I have also read a few people complaining about wi-fi disconnect issues (which I would definitely hate to have).
I do not care about a specific android version for my tablet, I just want it to run smoothly and without any issues and headaches considering this, would you advice me to install the Marshmallow version or the latest Nougat one?

Kalynor said:
I do not care about a specific android version for my tablet, I just want it to run smoothly and without any issues and headaches considering this, would you advice me to install the Marshmallow version or the latest Nougat one?
Click to expand...
Click to collapse
Finally it's up to you which one you are going to use. I had been on MM 6.0.1 since version#10. Now I have been on N 7.1.0 since version #6. I have never had any problems with WiFi, Audio, Calendar or something like that. All versions run very well, smoothly and stable.
However in both cases you need Kang TWRP in order to be able to format /data to F2FS. This gets the better performance.

ebonit said:
Finally it's up to you which one you are going to use. I had been on MM 6.0.1 since version#10. Now I have been on N 7.1.0 since version #6. I have never had any problems with WiFi, Audio, Calendar or something like that. All versions run very well, smoothly and stable.
However in both cases you need Kang TWRP in order to be able to format /data to F2FS. This gets the better performance.
Click to expand...
Click to collapse
Thanks again for the time you spend answering a total noob
At this point I would like to ask which version do you actually like the most, before deciding myself.
Plus, I'm getting ready to install everything, but I'd need some confirmations first.
I have just successfully unlocked the boot loader.
Now, to install the Kang TWRP, do I need to download something called "fastboot"? I read this on another guide, because the actual link to the Kang TWRP doesn't exactly tell me how to properly install it. Or at least, I feel like there are advanced instructions I can't fully understand.
After installing the Kang recovery, the guide says I should do these things:
1) do a full wipe , if you have issues make sure that you format /data (format is different than wipe). I guess I can do the WIPE from the recovery menu. Should I format /data after said wipe? If the answer is YES, how should I do that?
2) Change /data filesystem to f2fs. The guide once again doesn't tell me how should I change this thing.
3) Flash the rom. I guess I have to install the ROM from the recovery menu.
4) Flash the SuperSU zip. I assume I can do this from the recovery menu aswell
5)Flash gapps. Always from the recovery menu?
6) Wipe cache/dalvik. No additional info is provided, how should I do that?
7) Reboot
Thanks in advance for the clarifications eventually provided I feel like I'm just adventuring myself in a new, huge world.

Kalynor said:
Thanks again for the time you spend answering a total noob
At this point I would like to ask which version do you actually like the most, before deciding myself.
Plus, I'm getting ready to install everything, but I'd need some confirmations first.
I have just successfully unlocked the boot loader.
Now, to install the Kang TWRP, do I need to download something called "fastboot"? I read this on another guide, because the actual link to the Kang TWRP doesn't exactly tell me how to properly install it. Or at least, I feel like there are advanced instructions I can't fully understand.
After installing the Kang recovery, the guide says I should do these things:
1) do a full wipe , if you have issues make sure that you format /data (format is different than wipe). I guess I can do the WIPE from the recovery menu. Should I format /data after said wipe? If the answer is YES, how should I do that?
2) Change /data filesystem to f2fs. The guide once again doesn't tell me how should I change this thing.
3) Flash the rom. I guess I have to install the ROM from the recovery menu.
4) Flash the SuperSU zip. I assume I can do this from the recovery menu aswell
5)Flash gapps. Always from the recovery menu?
6) Wipe cache/dalvik. No additional info is provided, how should I do that?
7) Reboot
Thanks in advance for the clarifications eventually provided I feel like I'm just adventuring myself in a new, huge world.
Click to expand...
Click to collapse
First of all you need „Minimal ADB and Fastboot“. The USB driver must be installed on your PC.
Download “Minimal ADB and Fastboot”. Make a folder C:/Fastboot and extract it there and install it on your PC. Download Kang TWRP and put it into the folder C:/Fastboot and rename it to twrp.img
Start your device in fastboot mode and connect it with your PC. Open “Minimal ADB and Fastboot” and put in "fastboot devices". The device should appear as "xxx device".
Put in "fastboot -i 0x0B05 flash recovery twrp.img" without " ".
After that you should have Kang TWRP. Format F2FS with TWRP: Wipe => Advanced wipe, check the box for data then click on Repair or change file system, then click F2FS. But /Data only not /System or /Cache!!!
Finally do all 7 steps. Flash rom, gapps and SuperSU in one run. Wipe dalvik/cache. After that reboot.

ebonit said:
First of all you need „Minimal ADB and Fastboot“. The USB driver must be installed on your PC.
Download “Minimal ADB and Fastboot”. Make a folder C:/Fastboot and extract it there and install it on your PC. Download Kang TWRP and put it into the folder C:/Fastboot and rename it to twrp.img
Start your device in fastboot mode and connect it with your PC. Open “Minimal ADB and Fastboot” and put in "fastboot devices". The device should appear as "xxx device".
Put in "fastboot -i 0x0B05 flash recovery twrp.img" without " ".
After that you should have Kang TWRP. Format F2FS with TWRP: Wipe => Advanced wipe, check the box for data then click on Repair or change file system, then click F2FS. But /Data only not /System or /Cache!!!
Finally do all 7 steps. Flash rom, gapps and SuperSU in one run. Wipe dalvik/cache. After that reboot.
Click to expand...
Click to collapse
Thanks, really! You're very kind I'm already downloading everything needed.
Which version do you actually prefer? Are there any difference on the battery life between them?
And also, if I install for example Nougat, can I eventually revert to Marshmallow if I want to?

Kalynor said:
Thanks, really! You're very kind I'm already downloading everything needed.
Which version do you actually prefer? Are there any difference on the battery life between them?
And also, if I install for example Nougat, can I eventually revert to Marshmallow if I want to?
Click to expand...
Click to collapse
Of course, but it needs always a clean install (format data).

ebonit said:
Of course, but it needs always a clean install (format data).
Click to expand...
Click to collapse
I'm trying to install the recovery, but it seems that something is going wrong.
This is what appears on the screen:
C:\Fastboot>fastboot -i 0x0B05 flash recovery twrp.img
target didn't report max-download-size
sending 'recovery' (7126 KB)...
OKAY [ 2.805s]
writing 'recovery'...
OKAY [ 8.019s]
finished. total time: 10.825s
After that, it seems that nothing has actually changed. I tried rebooting with C:\Fastboot>fastboot -i 0x0B05 reboot but it just reboots normally. If I try going in recovery mode, I still have the old stock recovery mode.
What am I doing wrong?
(Ofc, in the meanwhile I'm pressing the thanks button )

Kalynor said:
I'm trying to install the recovery, but it seems that something is going wrong.
This is what appears on the screen:
C:\Fastboot>fastboot -i 0x0B05 flash recovery twrp.img
target didn't report max-download-size
sending 'recovery' (7126 KB)...
OKAY [ 2.805s]
writing 'recovery'...
OKAY [ 8.019s]
finished. total time: 10.825s
After that, it seems that nothing has actually changed. I tried rebooting with C:\Fastboot>fastboot -i 0x0B05 reboot but it just reboots normally. If I try going in recovery mode, I still have the old stock recovery mode.
What am I doing wrong?
(Ofc, in the meanwhile I'm pressing the thanks button )
Click to expand...
Click to collapse
What bootloader do you have? MUST BE ON A BOOTLOADER ENDING IN 27.1 or 27.5.
Please check starting fastboot by power on and volume down. In the left corner should appear "WW_epad-10.6.1.27.5".

ebonit said:
What bootloader do you have? MUST BE ON A BOOTLOADER ENDING IN 27.1 or 27.5.
Please check starting fastboot by power on and volume down. In the left corner should appear "WW_epad-10.6.1.27.5".
Click to expand...
Click to collapse
It appears this line: Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.6.1.27.5-20130902" A03
EDIT: solved, I had to press volume UP to enter RCK!

It seems that everything went ok, but I got ERROR 70: insufficient space when installing gapps. How can I solve that?
Eventually figured it out myself, I had to take either the pico or nano version! Gonna do it all again

Kalynor said:
It seems that everything went ok, but I got ERROR 70: insufficient space when installing gapps. How can I solve that?
Eventually figured it out myself, I had to take either the pico or nano version! Gonna do it all again
Click to expand...
Click to collapse
open_gapps-arm-7.1-pico-20161030
Please don't forget flashing Rom, Gapps and SuperSU in one run!!!

ebonit said:
open_gapps-arm-7.1-pico-20161030
Click to expand...
Click to collapse
Actually trying the marshmallow version now I will eventually move to Nougat in a few days! Thanks for all the help.

Kalynor said:
Actually trying the marshmallow version now I will eventually move to Nougat in a few days! Thanks for all the help.
Click to expand...
Click to collapse
Congratulations! You did a good job. It was a great pleasure to help you. Hope to meet you again in the MM threat!

ebonit said:
Congratulations! You did a good job. It was a great pleasure to help you. Hope to meet you again in the MM threat!
Click to expand...
Click to collapse
Thanks mate! Really!
I am experiencing an issue though. I am getting wi-fi disconnecting every couple of minutes, or even less. I've also written in the marshmallow thread, hoping to get some answer.
Is there a way to fix this? Will eventually the new build Nougat solve this?

Kalynor said:
Is there a way to fix this? Will eventually the new build Nougat solve this?
Click to expand...
Click to collapse
I'm sorry, but I have no idea. Timduru suggests "Try increasing the group rekeying interval on your router".
If I were in your boots, I would try a clean installation of Nougatella to see whether it's solved or not.

ebonit said:
I'm sorry, but I have no idea. Timduru suggests "Try increasing the group rekeying interval on your router".
If I were in your boots, I would try a clean installation of Nougatella to see whether it's solved or not.
Click to expand...
Click to collapse
Thanks as always for the suggestions.
I had some time today and flashed Nougatella. Unfortunately, the wi-fi issue it's still there. No sign of improvement at all.
I'm starting to get a bit mad on this. Is there any previous version without any known wifi issues? I am even open to try other ROMs. I just want my tablet to be good for internet browsing and youtube watching...

Kalynor said:
Thanks as always for the suggestions.
I had some time today and flashed Nougatella. Unfortunately, the wi-fi issue it's still there. No sign of improvement at all.
I'm starting to get a bit mad on this. Is there any previous version without any known wifi issues? I am even open to try other ROMs. I just want my tablet to be good for internet browsing and youtube watching...
Click to expand...
Click to collapse
I'm so sorry for that because I was very hopeful the issue will be solved.
First of all, please check your tablet within another stable network like a free WiFi somewhere. If there is still the same trouble please make a logcat and send it to Timduru. Maybe it helps to figure out the cause. Using the terminal emulator: su ->logcat. Save the file as "logcat.txt".

ebonit said:
I'm so sorry for that because I was very hopeful the issue will be solved.
First of all, please check your tablet within another stable network like a free WiFi somewhere. If there is still the same trouble please make a logcat and send it to Timduru. Maybe it helps to figure out the cause. Using the terminal emulator: su ->logcat. Save the file as "logcat.txt".
Click to expand...
Click to collapse
Thanks for the tip. Unfortunately I don't actually have the time to test other wi-fi networks, and above all, it would still pass A LOT of time between my log sending to timduru and EVENTUALLY him taking care of the issue (provided he would).
I'd need a quick solution to make the tablet work again, considering I haven't been using it for days because of this wifi problem.
Would the Lollipop katkiss version work with the same recovery? Are there still people lamenting the same issue even on lollipop?
Can you please tell me if there are any other decent ROMs I can try with the same TWRP recovery?