curious is there anyway to completely wipe everything so I have a clean slate then install latest bootloader and recovery
And then of course rom of my choice I'm assuming this is pretty easy and I have to have all the media on the external SD card or computer?
Sent from my XT897 using xda premium
Why would you want to do that???
If you have the latest bootloader, you are fine.
If you have a working recovery compatible with the bootloader, you're fine.
If you want to flash a new bootloader you need your recovery to do it.
If you do not have a bootloader and no recovery, you have a brick!
Your system partition gets formatted each time you flash a ROM.
To start with a squeaky clean system you format your data partition AFTER making sure that you have a working bootloader/recovery combination and the ROM installed.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Related
already rooted. is there a step by step to downgrade to ics. really miss my flash player. can't get it to work on jb.
There is not a way to downgrade at the moment if you are running the OTA JB.
Btw flash can still work with JB using the stock browser. Here's a copy of the recent flash player if you need it
https://www.box.com/shared/b58c065aae3988d53e04
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
DMardroid said:
There is not a way to downgrade at the moment if you are running the OTA JB.
Btw flash can still work with JB using the stock browser. Here's a copy of the recent flash player if you need it
https://www.box.com/shared/b58c065aae3988d53e04
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
I would think to truly do this, you would need to flash the bootloader, system, and recovery all at the same time so everything is in sync with ICS, just not worth it.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
funnel71 said:
I would think to truly do this, you would need to flash the bootloader, system, and recovery all at the same time so everything is in sync with ICS, just not worth it.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
Well, can't we just download the latest ICS factory image from Asus? Or would the bootloader prevent us from even using the factory ICS image?
naddie said:
Well, can't we just download the latest ICS factory image from Asus? Or would the bootloader prevent us from even using the factory ICS image?
Click to expand...
Click to collapse
When I was locked, I tried to take the zip and put it in internal storage. It installed the downgrade as it called it, but when done, I was still on jb. I would think if you're on jb and force flashed the ICS blob it would possibly brick the device because jb has different permissions and from what I've read a different partition table all together.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
funnel71 said:
When I was locked, I tried to take the zip and put it in internal storage. It installed the downgrade as it called it, but when done, I was still on jb. I would think if you're on jb and force flashed the ICS blob it would possibly brick the device because jb has different permissions and from what I've read a different partition table all together.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
I don't believe it has a different partition table but even if it did, asus blobs include the partition table in every update so that wouldn't be an issue, the issue however is that you cannot download the bootloader, the bootloader is now signed seperately to the rest of the update to prevent abuse like what we did with the tf201 to obtain nvflash access. When you unlock the bootloader signature remains enabled while the blob flashing signature check is disabled. This has a side effect of preventing downgrades as the bootloaders pre-JB do not have this same signing mechanism in place.
funnel71 said:
When I was locked, I tried to take the zip and put it in internal storage. It installed the downgrade as it called it, but when done, I was still on jb. I would think if you're on jb and force flashed the ICS blob it would possibly brick the device because jb has different permissions and from what I've read a different partition table all together.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
I actually attempted to downgrade last night. Quite frankly, I think that I came close o a few soft bricks. I tried flashing a custom ICS rom...no go. I tried loading the firmware from the Asus website to the root of the SD card and restart...no go. I tried force flashing the firmware using recovery mode, and it completed "successfully." When I rebooted...no go...and no ROM. This is when I started getting worried, because when I tried to boot into recovery, I received a red error message saying that there was a mismatch. I hard rebooted again, and booted into recovery, and reflashed my JB Rom. I did everything BUT use fastboot to load an ICS recovery image. I didn't want to take that risk.
My suggestion....leave it alone. I am leaving it to the experts. And if you are not an expert, then LEAVE IT TO THEM TOO!
aarsyl said:
I actually attempted to downgrade last night. Quite frankly, I think that I came close o a few soft bricks. I tried flashing a custom ICS rom...no go. I tried loading the firmware from the Asus website to the root of the SD card and restart...no go. I tried force flashing the firmware using recovery mode, and it completed "successfully." When I rebooted...no go...and no ROM. This is when I started getting worried, because when I tried to boot into recovery, I received a red error message saying that there was a mismatch. I hard rebooted again, and booted into recovery, and reflashed my JB Rom. I did everything BUT use fastboot to load an ICS recovery image. I didn't want to take that risk.
My suggestion....leave it alone. I am leaving it to the experts. And if you are not an expert, then LEAVE IT TO THEM TOO!
Click to expand...
Click to collapse
Good suggestion haha - now I have been reading about nvflash being usable for the tf300, but only if you were on the ICS bootloader, wondering if you can do an nvflash type backup - don't know much about it - but after backup, upgrade to jb, then use backup to return to ICS...
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
I tried every method out there to get back to ICS. So there is no way. Tried fastboot, tried adb, tried wolfs downgrade method, tried restoring a backup with CWM and TWRP and many more. So unfortunately there is no way, but Scotts and Seanz Roms were the best Roms on ICS, so I think I dont have to, cause I have the best Roms to choose.
Only thing missing is NVflash and OC (its been working on )
Have you tried erasing everything
mikaole said:
I tried every method out there to get back to ICS. So there is no way. Tried fastboot, tried adb, tried wolfs downgrade method, tried restoring a backup with CWM and TWRP and many more. So unfortunately there is no way, but Scotts and Seanz Roms were the best Roms on ICS, so I think I dont have to, cause I have the best Roms to choose.
Only thing missing is NVflash and OC (its been working on )
Click to expand...
Click to collapse
I recently just restored my bricked Tf300 by using these commands from fastboot thanks to user Buster99
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adt-bundle\platform-tools\blob (this is my path - your's may vary depending where you stored your blob)
fastboot -i 0x0B05 reboot
this completely erased my system, fixed my bootloo and brought it back to stock. Can there be a way to erase the bootloader this way???
Link to how i recovered "http://forum.xda-developers.com/showthread.php?p=45386598#post45386598"
Hi,
I was wondering if you just flashed with fastboot the blob file as I am gettin an error and cannot upgrade to JB.
Is this the only way for it though?
http://forum.xda-developers.com/showthread.php?t=1853145
Best and thank you very much (using WW version),
Blubberor
P.S.: As CM10 is switched to JB bootloader, I and a lot of others need to upgrade...
look here
I was using CM10 on the ICS bootloader. I downloaded the most recent JB update from Asus to my pc and unzipped once. I copied that zip to my internal memory. Booted into recovery. Using TWRP, I wiped cache, dalvik, system, factory reset. Then installed the Asus zip. Voila, updated to the JB bootloader. I then downloaded twrp 2.3.1 for JB bootloader to my pc and put it with my adb/fastbbot files. Rebooted into fastboot and installed TWRP. Rebooted into recovery, made a backup and installed CM10 10/31/12 nightly for JB.
Sent from my Transformer Pad TF300T using xda premium
Maybe I am too stupud but
I have a TF300TG
I ejected my micro sd card so format should not matter.
I still get Error7.
If I edit updater-script it just failes instantly.
I am using TWRP ICS recovery for TF300T but this should not matter as well??
Can someone with a TF300TG can give me a hint how to update?
Best,
Blubberor
http://forum.xda-developers.com/showthread.php?t=1942688
this is what worked
you have to be careful not to have any SPACES in the filename.. then its working!
Hello.
A was installed a recovery on my tablet ( CWM ) and rooted.
Then i wipe all ( data/factory reset, cache, dalvik cache ) and the i was install cm10.1
Now my tablet are stuck on asus logo and i cannot do anything.
My firmware is 10.4.2.18 ( i was updated then a was rooted my tablet )
What can i do?
Sorry my english.
Thank you.
Please someone.
Nobody?
My tablet is on from yesterday because if i turn off she turn on
Sent from my LG-P500 using xda app-developers app
READ COMPLETELY BEFORE ATTEMPTING!
While the tablet is on, hold power down until it turns off. As soon as it turns off press volume down while still holding the power button. That will enable you to choose to go back into your recovery or fastboot. Recovery will be the icon labeled RCK and fast boot will be the USB icon.
You could also choose to just enter RCK (recovery) and try to do a factory reset, try to flash the ROM again or flash another ROM from your SD card.
If you are positive you have choosen and flashed the correct ROM the first time, did you remember to do a factory reset, clear cache and dalvik before flashing the ROM? That could very well be the reason you are in a boot loop.
If you are using CWM as your recovery and cannot use it to flash a new ROM from your SD card, you may need to flash TWRP using fast boot in order to flash a different ROM from your SD card.
There is a TWRP thread in the development section. Download the TWRP recovery blob and flash it using fast boot.
You also have another option. You can choose to flash back to stock using fastboot. Here is a great tutorial that will guide you step by step on how to do it. If you are unsure of what to do and want a quick fix, use this. Make sure to thank him for the great tutorial after you finish if you decide to go this route.
http://forum.xda-developers.com/showthread.php?p=35805045
Good luck
Sent from my LG-LG855 using Xparent Green Tapatalk 2
Hello.
Yes, i was sellected factory reset first ( wipe data / factory reset ).
I have jellybro and cm10.1 on my sdcard. I wipped all more times and try to install roms, but the result was same.
In this case, shoud it by solve it in the same way?
Sent from my LG-P500 using xda app-developers app
I had this problem with mine when I was flashing it, but I was still on the ICS firmware when I tried to flash CM10, that's what caused the problem since the boot partition gets resized in the stock JB update.
Are you sure you were on a 4.1 OTA stock update before you tried this? Have you tried wiping data/system/cache and re-flashing the ROM again?
I ran a backup of my stock rom before flashing CM10, so when it wouldn't boot after the initial flash, I restored, and it was then stuck at the ASUS screen saying 'unlocked device' what I had to do to mine was extract boot.blob from cm9.1, boot the tablet into fastboot, and then run fastboot -i 0x0B05 flash boot boot.blob that got me booted back into a live tablet. I then took the JB OTA, and started over, flashing recovery, root, doing another backup, and then wiping and flashing CM10, which worked perfectly.
HOWEVER. If you're 100% certain you were on JB already, this may not be the case.
Yes. I was on jb 4.1.1, kernel 3.1 ( i,m not sure, but this i remember ) and, for sure, firmware 10.4.2.18
Sent from my LG-P500 using xda app-developers app
I would use the link I posted above. It will at least get you back to stock. It's a very easy tutorial to follow. Once you get the tablet where it will boot, then you can decide on another ROM.
Sent from my Transformer Pad TF300T using Xparent Purple Tapatalk 2
I wanna thank you...
It works now... the is you very much
Sent from my Transformer Pad TF300T using Xparent Blue Tapatalk 2
slackware87 said:
I wanna thank you...
It works now... the is you very much
Sent from my Transformer Pad TF300T using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
AWESOME! Glad it worked for you.
Sent from my LG-LG855 using Xparent Green Tapatalk 2
Hi guys.
Two weeks ago I upgraded my P920 from stock GB 2.3.5 to xbsall's ported ICS 4.0.4 and installed ClockworkMod Recovery v6.0.1.5 (Touch).
This weekend I flashed xbsall's custom ICS v5.2, which includes Team Win Recovery Project v2.2.2.1 (Touch).
Now I have both Recoveries installed and working!
I can access CWM through 3D+Power+Vol UP and TWRP through 3D+Power+Vol Down.
Is this normal? Will this create any problem?
I had the same setup only with acuras touch recovery instead of the 6.0.1.5
I flashed stuff from both, backed up and restored from both with no problems that i had knowledge of. Im trying darkroom international v2 now which i flashed from xbsa5.2 through the same touch recovery after wiping cache/dalvik/data/format data/format system...no problems what so ever, still have recovery and running fine.
Sent from my LG-SU760 using xda premium
I think you have one recovery installed on separate partition and the other one on system
Sent from my LG-SU760 using xda app-developers app
True that. On Xbsa5.2 twrp recovery is on system partition. Both will work but twrp will disappear if you wipe your system. Cwm should stay on recovery.
Sent from my LG-SU760 using xda premium
the ManaWhoney said:
True that. On Xbsa5.2 twrp recovery is on system partition. Both will work but twrp will disappear if you wipe your system. Cwm should stay on recovery.
Sent from my LG-SU760 using xda premium
Click to expand...
Click to collapse
Does that mean it's ok and no problem will appear?
If you flash a new rom through twrp and format system you will just loose twrp. Same if you wipe system with cwm but either way you will still have cwm on your recovery partition. You can easily change that by flashing twrp through the fast boot tool though if you want it back but you can only have one recovery on the recovery partition at once. XBSA rom is just awesome enough to have the temporary recovery included on system. No matter what you do though, they all will work fine but i repeat if you wipe system you will loose the twrp recovery you have now. Until you do though you have both so use whatever you like
Sent from my LG-SU760 using xda premium
the ManaWhoney said:
If you flash a new rom through twrp and format system you will just loose twrp. Same if you wipe system with cwm but either way you will still have cwm on your recovery partition. You can easily change that by flashing twrp through the fast boot tool though if you want it back but you can only have one recovery on the recovery partition at once. XBSA rom is just awesome enough to have the temporary recovery included on system. No matter what you do though, they all will work fine but i repeat if you wipe system you will loose the twrp recovery you have now. Until you do though you have both so use whatever you like
Sent from my LG-SU760 using xda premium
Click to expand...
Click to collapse
I'm confortable with CWM, so there's no problem if I loose TWRP.
Plus, can I delete TWRP to gain system space?
That I dont know nor do I know how to do it
Sent from my LG-SU760 using xda premium
daniel.mota said:
I'm confortable with CWM, so there's no problem if I loose TWRP.
Plus, can I delete TWRP to gain system space?
Click to expand...
Click to collapse
Anyone knows how to do this?
It takes only 4.5mb
Hello
So i decided that i was going to upgrade my bootloader from 4.1 to 4.2 so i could keep installing CM10.1 nightlies. I downloaded all the necessary files (Stock Asus, twrp2.5-42 and CM10.1 nightly), put them on my SD and rebooted into the bootloader. Here's where i think i screwed things up. While in the bootloader i accidently selected the Wipe Data option. It did completed teh wipe and booted into a fresh Andriod install. So i rebooted back into the bootloader and went into twrp and flashed the stock Asus update. After rebooting into hung (after 30 minutes) at the Asus screen with the spinning circle. I rebooted holding the power button and tried letting it load again and after another 30 min still "loading"
i can still get into the bootloader and twrp (fastbooted that back on) but i can't flash any ROM's successfully
My question is did i screw up the partition table or file system since i have read that this can happen. If so how can i verify this and can i fix it? IS there anyway to recover my tablet or am i going to have to pay Asus to fix it?
Thanks
No, no brick you have to flash stock Asus firmware blob via fastboot then flash latest twrp then flash Asus firmware in twrp
Sent from my sensational HTC Desire C
noahvt said:
No, no brick you have to flash stock Asus firmware blob via fastboot then flash latest twrp then flash Asus firmware in twrp
Sent from my sensational HTC Desire C
Click to expand...
Click to collapse
Tried that same result...see attached pic for my i think the partition might be screwed
Sent from my GT-I9000 using xda app-developers app
Why do you think it's screwed?
BTW if you used the correct version of twrp (-jb for 4.1 -4.2 for 4.2) it should have wiped them correctly!
Sent from my sensational HTC Desire C
noahvt said:
Why do you think it's screwed?
BTW if you used the correct version of twrp (-jb for 4.1 -4.2 for 4.2) it should have wiped them correctly!
Sent from my sensational HTC Desire C
Click to expand...
Click to collapse
Because it says tmpfs...which i think means temp file system
also i didn't do the wipe in twrp i did it in the bootloader
Yes, the bootloader contacts the recovery and the recovery peforms the wipe! If you have an older version of twrp: it doesn't know the partitions so it wipes Them wrong!
Sent from my Transformer Pad TF300T using xda app-developers app