Related
Hi everyone... I've tried searching and seen references to this kind of thing, but no download links or guides...
So I've got my Nexus S (bootloader unlocked, rooted, stock 2.3.4 until attempting the following, I have no Sim card in this phone), and I tried to flash 2.3.6, and while the update appeared to run just fine, the wifi won't turn on, just gives "error". So I attempted several things, reflashing the update, flashing the 4.04 update (which was the original point), etc, but they all give the following; installation aborted, assert failed, error in xxx.zip, "status 7".
Anyways... I'm a bit at a loss, I've never had this problem, or any problems flashing ROMs on other phones or updates. It seems no update.zip, or any .zip, will install. Back in my captivate days, there was a very handy program called Odin, and it had a master clear functionality that brought you back to the stockest of stock. Ideally... is there a tool like this for the Nexus S? I don't care about whether or not it re-locks the bootloader, I can unlock it again in just a couple minutes... but I need help.
I've read guides about "return to stock" but they all involve flashing a .zip. I need a way to push past that, and get back to 2.3.4, or alternatively, a way to completely reinstall 2.3.6.
I know an Odin exists for the Nexus S, but is there a way to use that to reset to stock?
Thank you so much anyone who can help...
Do you see an android and exclamation mark as you enter recovery? This means you have stock recovery and you cannot flash anything that hasn't been signed by google here. Stock is flashed on each boot on a stock ROM, you need to rename/delete /system/etc/install-recovery.sh to stop this.
If you don't have stock recovery, update to the latest CWM (touch or not is irrelevant) and try again. It's recommended to do a full wipe (data/factory reset, format /system and optionally format /boot) when doing a major ROM change (ie, CM to non-CM, GB to ICS, etc), and failure to do so could leave you with some interesting problems like that wifi issue.
And as always, make sure you backup properly before flashing -anything-.
edit to answer more questions: Odin is available for the Nexus S but near-useless. Fastboot can do just as much, and there are official fastboot images released by google to bring you back to a pure stock state. You'll just need an unlocked bootloader to do that, though you can relock straight afterward with no repercussions.
Harbb said:
Do you see an android and exclamation mark as you enter recovery? This means you have stock recovery and you cannot flash anything that hasn't been signed by google here. Stock is flashed on each boot on a stock ROM, you need to rename/delete /system/etc/install-recovery.sh to stop this.
If you don't have stock recovery, update to the latest CWM (touch or not is irrelevant) and try again. It's recommended to do a full wipe (data/factory reset, format /system and optionally format /boot) when doing a major ROM change (ie, CM to non-CM, GB to ICS, etc), and failure to do so could leave you with some interesting problems like that wifi issue.
Click to expand...
Click to collapse
Heh, yeah I guess I should have wiped previous to running this upgrade. I guess I was hoping data would preserve, because theoretically it should have been just like the Google OTA.
And I have CWM... I'm not sure if it is the latest version, but the phone can't get any data connectivity so I can't update it.
Harbb said:
edit to answer more questions: Odin is available for the Nexus S but near-useless. Fastboot can do just as much, and there are official fastboot images released by google to bring you back to a pure stock state. You'll just need an unlocked bootloader to do that, though you can relock straight afterward with no repercussions.
Click to expand...
Click to collapse
Ok, so fastboot is my solution. I've used that to unlock my bootloader, but little else (on a Mac, because terminal is super easy to use, but I've got PC access too). I've found the Google fastboot images, do you (or anyone reading this) know of a good fastboot image flashing guide?
Dareoth said:
Heh, yeah I guess I should have wiped previous to running this upgrade. I guess I was hoping data would preserve, because theoretically it should have been just like the Google OTA.
Click to expand...
Click to collapse
Some people supposedly had troubles with the ICS update and keeping all data as-is, though i've not experienced it myself, but it is definitely possible and with such a big update, if it's in your power to start fresh it is always the best option. It was more of a general statement, not directed at your situation - something to keep in mind
Dareoth said:
And I have CWM... I'm not sure if it is the latest version, but the phone can't get any data connectivity so I can't update it.
Click to expand...
Click to collapse
You can flash the latest CWM through fastboot from your PC or Mac, you can grab the latest file from here. Name it whatever you like and put it in a known folder (preferrably current folder) and : fastboot flash recovery recovery.img
Dareoth said:
Ok, so fastboot is my solution. I've used that to unlock my bootloader, but little else (on a Mac, because terminal is super easy to use, but I've got PC access too). I've found the Google fastboot images, do you (or anyone reading this) know of a good fastboot image flashing guide?
Click to expand...
Click to collapse
Of course i do
Great, I'm all set now. Thanks so much.
(Also for linking to that ref guide again, I had read it three times, but I didn't get how to use it until I went in going, I just need the fastboot commands, which is all that guide gives.)
Your welcome mate. All you need for that is setting up the android SDK or essentially downloading platform-tools seperately. There are guides all over the place describing how to do this for Windows, Mac and Linux as it is no different from getting oem unlock to work, they're just mostly disguised as rooting guides.
Once you do it the first time it's quite simple, but it can definitely be confusing before that
Hey all,
I just replaced my TF700 through Best Buy's super replacement program, and thank God I got one at .26. I am going through the process of rooting, unlocking, NVFlashing, recovery, etc. and have a question. To get back up to current ROMs, should I install ASUS firmware updates incrementally? Or can I just flash say CM 10.1 or CleanROM right over .26?
Thanks!
I_EAT_BABIES said:
Hey all,
I just replaced my TF700 through Best Buy's super replacement program, and thank God I got one at .26. I am going through the process of rooting, unlocking, NVFlashing, recovery, etc. and have a question. To get back up to current ROMs, should I install ASUS firmware updates incrementally? Or can I just flash say CM 10.1 or CleanROM right over .26?
Thanks!
Click to expand...
Click to collapse
Don't know about CM10.1, but as for CleanRom, I think it's fair to say that as long as you have the lastest or second latest bootloader, you can flash CRomI on it.
Like I said, don't know about CM, because I never tried it, no matter how much I wanted to be on 4.2, because I am super happy with CRomI, which as an Asus based Rom works flawlessly with the dock
I_EAT_BABIES said:
Hey all,
I just replaced my TF700 through Best Buy's super replacement program, and thank God I got one at .26. I am going through the process of rooting, unlocking, NVFlashing, recovery, etc. and have a question. To get back up to current ROMs, should I install ASUS firmware updates incrementally? Or can I just flash say CM 10.1 or CleanROM right over .26?
Thanks!
Click to expand...
Click to collapse
No you can't, you need JB bootloader, you need to flash a full JB firmware from Asus. Others, may just flash the JB bootloader independently. After you have JB bootloader then you can flash cm10 or Cleanrom since they build on JB base. (cm10 and cleanrom don't included bootloader, just rom and kernel)
Thanks guys.
I'm assuming even just flashing the bootloader will wipe my recovery?
I_EAT_BABIES said:
I'm assuming even just flashing the bootloader will wipe my recovery?
Click to expand...
Click to collapse
If you extract the bootloader from the full blob and flash only that (or use a stand-alone bootloader blob extracted by someone else), then it won't wipe your recovery.
But if you don't know 100% what you are doing, it is safer and easier to flash the complete firmware and re-flash the recovery via fastboot.
Remember that a recovery incompatible with the bootloader in combination with "wipe data" leads to a brick (which can be solved with nvflash or otherwise by Asus only).
Hi
I have a ASUS TF300T and have installed the TWRP bootloader as recommended by another site.
I have tried Cyanogenmod 9, Cyanogenmod 10 and Cyanogenmod 10.1 nightly and none of them will boot. The device gets stuck at the ASUS logo screen and I get no further.
Obviously I have cleared cache etc (I'm familiar with the basics of installing a different ROM).
Can anyone advise me what to do? I have restored to the default ASUS software through a backup I made but I am really not happy with the performance of this.
I either want to be able to get Cyanogenmod on this tablet or I'd like to restore it to the default bootloader to make it ready for sale.
Thanks so much in advance.
You need to make sure that the version of CM you're flashing will work with your bootloader. So far, it doesn't seem like you're paying attention to that. CM9 only works with the ICS bootloader. Early CM10 builds only worked with the ICS bootloader, but newer CM10 builds only worked with the 4.1 bootloader. The official CM10.1 only works with the 4.1 bootloader. The unofficial CM10.1 is testing support for the 4.2 bootloader and only works with the 4.2 bootloader.
If you don't know which bootloader you have, there are a couple ways to tell. First, do you remember the last OTA update you took? If it was version 9.something, you are on the ICS bootloader. If it was 10.4.something, you are on the 4.1 bootloader. If you are up to 10.6.something, you are on the 4.2 bootloader. If you do not remember the last OTA you took, you can boot the tablet to the bootloader, and it will tell you which version it is at the top of the screen.
And yes, the whole bootloader version thing is needlessly complicated, but it's not the devs' faults. ASUS is the one that kept changing how the bootloader worked. Complain to them if you want. I and the others here will be happy to help you figure it out, but we had nothing to do with making this difficult. We all hate it, too.
EndlessDissent said:
You need to make sure that the version of CM you're flashing will work with your bootloader. So far, it doesn't seem like you're paying attention to that. CM9 only works with the ICS bootloader. Early CM10 builds only worked with the ICS bootloader, but newer CM10 builds only worked with the 4.1 bootloader. The official CM10.1 only works with the 4.1 bootloader. The unofficial CM10.1 is testing support for the 4.2 bootloader and only works with the 4.2 bootloader.
If you don't know which bootloader you have, there are a couple ways to tell. First, do you remember the last OTA update you took? If it was version 9.something, you are on the ICS bootloader. If it was 10.4.something, you are on the 4.1 bootloader. If you are up to 10.6.something, you are on the 4.2 bootloader. If you do not remember the last OTA you took, you can boot the tablet to the bootloader, and it will tell you which version it is at the top of the screen.
And yes, the whole bootloader version thing is needlessly complicated, but it's not the devs' faults. ASUS is the one that kept changing how the bootloader worked. Complain to them if you want. I and the others here will be happy to help you figure it out, but we had nothing to do with making this difficult. We all hate it, too.
Click to expand...
Click to collapse
Hi there. Many thanks for your detailed and helpful response. I've never had to worry about this before as I've only rooted Samsung and HTC devices.
The bootloader is version 10.6.1. Judging by what you've said, I should be able to use Cyanogenmod 10.1 nightlies but unfortunately the same problem is replicated across this too.
How should I proceed?
Many thanks!
mattburley said:
Hi there. Many thanks for your detailed and helpful response. I've never had to worry about this before as I've only rooted Samsung and HTC devices.
The bootloader is version 10.6.1. Judging by what you've said, I should be able to use Cyanogenmod 10.1 nightlies but unfortunately the same problem is replicated across this too.
How should I proceed?
Many thanks!
Click to expand...
Click to collapse
No, the official CM10.1 nightlies are for the 4.1 bootloader (OTA version 10.4.x). You are on the 4.2 bootloader. You have two options here:
1. Downgrade to OTA version 10.4.2.20 and flash the official CM10.1 nightlies. There are several guides in these forums for doing this. The process is easy, but there are caveats. See CAUTION below.
Or
2. Use the unofficial CM10.1 for the 4.2 bootloader. You can find it HERE. I believe that the only thing broken right now is the camera.
CAUTION: Keep in mind, if you choose the downgrade method, you must be absolutely sure that you're flashing the correct recovery version. With the 4.2 bootloader like you have now, you need a recovery that ends in "-42". With the 4.1 bootloader, you need a recovery that ends with "-JB". Obviously, you have the correct recovery now, but if you decide to downgrade to the 4.1 bootloader, then back to the 4.2 bootloader, each requires a different recovery version. If you were to flash a "-JB" recovery with the 4.2 bootloader, you WILL BRICK YOUR TABLET. Not trying to scare you, but it happens a lot. Just skim through a few of the threads involving bricked tablets, and more often than not, it's because they use the wrong recovery for their bootloader. As long as you're careful, read the OP of any development threads, and double check which files you're flashing, you should be fine.
Honestly, if you don't need a working camera, it's probably best to stay on the OTA you're currently on, and flash the unofficial CM10.1. Otherwise, if you downgrade, just take baby steps and read carefully.
EndlessDissent said:
You need to make sure that the version of CM you're flashing will work with your bootloader. So far, it doesn't seem like you're paying attention to that. CM9 only works with the ICS bootloader. Early CM10 builds only worked with the ICS bootloader, but newer CM10 builds only worked with the 4.1 bootloader. The official CM10.1 only works with the 4.1 bootloader. The unofficial CM10.1 is testing support for the 4.2 bootloader and only works with the 4.2 bootloader.
If you don't know which bootloader you have, there are a couple ways to tell. First, do you remember the last OTA update you took? If it was version 9.something, you are on the ICS bootloader. If it was 10.4.something, you are on the 4.1 bootloader. If you are up to 10.6.something, you are on the 4.2 bootloader. If you do not remember the last OTA you took, you can boot the tablet to the bootloader, and it will tell you which version it is at the top of the screen.
And yes, the whole bootloader version thing is needlessly complicated, but it's not the devs' faults. ASUS is the one that kept changing how the bootloader worked. Complain to them if you want. I and the others here will be happy to help you figure it out, but we had nothing to do with making this difficult. We all hate it, too.
Click to expand...
Click to collapse
EndlessDissent said:
No, the official CM10.1 nightlies are for the 4.1 bootloader (OTA version 10.4.x). You are on the 4.2 bootloader. You have two options here:
1. Downgrade to OTA version 10.4.2.20 and flash the official CM10.1 nightlies. There are several guides in these forums for doing this. The process is easy, but there are caveats. See CAUTION below.
Or
2. Use the unofficial CM10.1 for the 4.2 bootloader. You can find it HERE. I believe that the only thing broken right now is the camera.
CAUTION: Keep in mind, if you choose the downgrade method, you must be absolutely sure that you're flashing the correct recovery version. With the 4.2 bootloader like you have now, you need a recovery that ends in "-42". With the 4.1 bootloader, you need a recovery that ends with "-JB". Obviously, you have the correct recovery now, but if you decide to downgrade to the 4.1 bootloader, then back to the 4.2 bootloader, each requires a different recovery version. If you were to flash a "-JB" recovery with the 4.2 bootloader, you WILL BRICK YOUR TABLET. Not trying to scare you, but it happens a lot. Just skim through a few of the threads involving bricked tablets, and more often than not, it's because they use the wrong recovery for their bootloader. As long as you're careful, read the OP of any development threads, and double check which files you're flashing, you should be fine.
Honestly, if you don't need a working camera, it's probably best to stay on the OTA you're currently on, and flash the unofficial CM10.1. Otherwise, if you downgrade, just take baby steps and read carefully.
Click to expand...
Click to collapse
Fantastic, thanks for that. I never use the camera - so I just wanted to check. I flash the "cm-10.1-20130430-EXPERIMENTAL-tf300t.zip - 161.95 MB" file found at http://forum.xda-developers.com/showthread.php?t=2252990 just as I would with any other Cyanogenmod version?
Thanks!
mattburley said:
Fantastic, thanks for that. I never use the camera - so I just wanted to check. I flash the "cm-10.1-20130430-EXPERIMENTAL-tf300t.zip - 161.95 MB" file found at http://forum.xda-developers.com/showthread.php?t=2252990 just as I would with any other Cyanogenmod version?
Thanks!
Click to expand...
Click to collapse
Yup. Other than the bootloader version fiasco, flashing ROMs and stuff is just like any other device.
Oh, make sure you have the Gapps, too (I'm sure you knew that already, though). The normal ones at Goo.im work fine.
Oh, and just for future reference, if you want to apply a brand new OTA update and go back to CM, wait a week or two before taking the OTA update. Don't go flashing willy nilly. Let the devs figure out the changes they need to make, if any. This is especially important for recoveries. Sorry for hammering in the whole "CAREFUL!" thing so hard, but I've seen way too many threads about bricked tablets. It gets depressing.
EndlessDissent said:
Yup. Other than the bootloader version fiasco, flashing ROMs and stuff is just like any other device.
Oh, make sure you have the Gapps, too (I'm sure you knew that already, though). The normal ones at Goo.im work fine.
Oh, and just for future reference, if you want to apply a brand new OTA update and go back to CM, wait a week or two before taking the OTA update. Don't go flashing willy nilly. Let the devs figure out the changes they need to make, if any. This is especially important for recoveries. Sorry for hammering in the whole "CAREFUL!" thing so hard, but I've seen way too many threads about bricked tablets. It gets depressing.
Click to expand...
Click to collapse
That seems to have done the trick!! Thanks so much for your help.
So, if Cyanogenmod asks me to update I should wait a while before applying it?
Cheers!
mattburley said:
That seems to have done the trick!! Thanks so much for your help.
So, if Cyanogenmod asks me to update I should wait a while before applying it?
Cheers!
Click to expand...
Click to collapse
Since you're using the unofficial build, you won't be able to use the CM Updater. Or, at least, I would assume you can't. I'm pretty sure that it would download the newest official version, and the official ones won't boot. So you'll have to watch the unofficial thread for updates for now, until everything's fixed and it becomes official.
As for waiting to update, that applies to the ASUS OTA updates, not the CM updates. ASUS, as I've mentioned, makes changes to the bootloader in some of their OTAs that can cause bricks. If you're just updating CM nightlies, you shouldn't have anything to worry about. It's the stock updates that get hairy.
If you would like more stuff working, you could downgrade your tablet to 4.1 (forum.xda-developers.com/showthread.php?t=2195883), and install CyanogenMod 10.
I just flashed the experimental on the 4.2 bootloader and I'm stuck on the CM boot screen with the spinning circle. Any idea why this might have occurred?
Me too. Just sits there spinning. Went to my backup for now.
Yeah, I just restored my backup as well after several attempts at getting CM 10.1 to work
roberto767 said:
Yeah, I just restored my backup as well after several attempts at getting CM 10.1 to work
Click to expand...
Click to collapse
I have the 4.2 boot loader. So I finally figured out you the 4.2 version recovery instead of the JB version. That unofficial one still would not work so I flashed this and it works great.
http://forum.xda-developers.com/showthread.php?t=2204166
thx for this thread, I had these issues myself,,, shame it wont work on 4.2 bootloader
Stuck at CyanogenMod Logo durng boot
Your detailed explanation is very much appreciated.
I am using the 4.2 bootloader and TWRP. I flashed the CM 10.1 Experimental version referenced in your post.
When I try to boot, I get stuck in at the CyanogenMod logo. This is the same place I got stock when I tried using the Nightlies and the Stable version. Any thoughts on what is going wrong?
EndlessDissent said:
No, the official CM10.1 nightlies are for the 4.1 bootloader (OTA version 10.4.x). You are on the 4.2 bootloader. You have two options here:
1. Downgrade to OTA version 10.4.2.20 and flash the official CM10.1 nightlies. There are several guides in these forums for doing this. The process is easy, but there are caveats. See CAUTION below.
Or
2. Use the unofficial CM10.1 for the 4.2 bootloader. You can find it HERE. I believe that the only thing broken right now is the camera.
CAUTION: Keep in mind, if you choose the downgrade method, you must be absolutely sure that you're flashing the correct recovery version. With the 4.2 bootloader like you have now, you need a recovery that ends in "-42". With the 4.1 bootloader, you need a recovery that ends with "-JB". Obviously, you have the correct recovery now, but if you decide to downgrade to the 4.1 bootloader, then back to the 4.2 bootloader, each requires a different recovery version. If you were to flash a "-JB" recovery with the 4.2 bootloader, you WILL BRICK YOUR TABLET. Not trying to scare you, but it happens a lot. Just skim through a few of the threads involving bricked tablets, and more often than not, it's because they use the wrong recovery for their bootloader. As long as you're careful, read the OP of any development threads, and double check which files you're flashing, you should be fine.
Honestly, if you don't need a working camera, it's probably best to stay on the OTA you're currently on, and flash the unofficial CM10.1. Otherwise, if you downgrade, just take baby steps and read carefully.
Click to expand...
Click to collapse
---------- Post added at 05:32 PM ---------- Previous post was at 05:15 PM ----------
I resolved this problem by wiping data using the Bootloader Wipe Data option and the TWRP Wipe Data option. (I probably did not need both.)
roberto767 said:
I just flashed the experimental on the 4.2 bootloader and I'm stuck on the CM boot screen with the spinning circle. Any idea why this might have occurred?
Click to expand...
Click to collapse
rdh23 said:
Your detailed explanation is very much appreciated.
I am using the 4.2 bootloader and TWRP. I flashed the CM 10.1 Experimental version referenced in your post.
When I try to boot, I get stuck in at the CyanogenMod logo. This is the same place I got stock when I tried using the Nightlies and the Stable version. Any thoughts on what is going wrong?
---------- Post added at 05:32 PM ---------- Previous post was at 05:15 PM ----------
I resolved this problem by wiping data using the Bootloader Wipe Data option and the TWRP Wipe Data option. (I probably did not need both.)
Click to expand...
Click to collapse
Just an FYI: the official CM10.1 now supports the 4.2 bootloader. It has for over a month now. Plus, the experimental build has been abandoned.
Same story again
Hello.
I am having the exact same problem : I unlocked my tf300t, flashed it with twrp 2.6.3.0. That went well, so I then installed cyanogen CM10.2.0-tf300t (I am summarizing here, but I did follow all the necessary steps, including the backup, the cache wipe etc). My latest android version was 4.2.1 and I have bootloader 10.6.1.27.5 which, as far as I know, should be compatible with CM 10.2
After flashing the CM install, upon reboot I get the cyanogen logo with the arrow spinning eternally while it just hangs there.
The worst part is that when I restored from my backup, upon reboot it does the exact same thing : I see the asus logo and a spinning circle below and nothing more.
Any idea what I should to to try and fix that ? I was thinking of trying the CM11 (nightly). Thanks.
M
p.s. I did make sure to get the right recovery for my bootloader, i.e. openrecovery-twrp-2.6.3.0-tf300t-4.2.blob
Emalice said:
Hello.
I am having the exact same problem : I unlocked my tf300t, flashed it with twrp 2.6.3.0. That went well, so I then installed cyanogen CM10.2.0-tf300t (I am summarizing here, but I did follow all the necessary steps, including the backup, the cache wipe etc). My latest android version was 4.2.1 and I have bootloader 10.6.1.27.5 which, as far as I know, should be compatible with CM 10.2
After flashing the CM install, upon reboot I get the cyanogen logo with the arrow spinning eternally while it just hangs there.
The worst part is that when I restored from my backup, upon reboot it does the exact same thing : I see the asus logo and a spinning circle below and nothing more.
Any idea what I should to to try and fix that ? I was thinking of trying the CM11 (nightly). Thanks.
M
Click to expand...
Click to collapse
What OS is your PC running??
lj50036 said:
What OS is your PC running??
Click to expand...
Click to collapse
windows 7 64bits...
adb
Emalice said:
windows 7 64bits...
Click to expand...
Click to collapse
You have the adb driver install?? if so turn your tablet off and in a command window move to the directory that adb is in and type
Code:
adb logcat > logcat.txt
now boot your tablet.... your PC will pick it as adb device and output the logcat to a text file in that directory post the logcat file....Let the logcat run for about 90 sec or so.....
I have my tablet still on ICS, locked, all stock ROM, except I used a root exploit for ICS to have root.
What I would like to know; what is the best method for me to be able to happily try out different ROM's without fluffing up and bricking my tablet?
I know I need to unlock, install customer recovery. Is NVFlash backup necessary?
I've also got a HTC Desire HD which I've flashed with many ROM's without ever running into issues.
The Asus TF300 seems different and I've seen too many posts where people have bricked their devices.
Is it true that flashing a ROM designed for one version of the bootloader, on a device with a different version will brick your device?
Also it is true that certain wipes from recovery brick your device?
psjw12 said:
Is it true that flashing a ROM designed for one version of the bootloader, on a device with a different version will brick your device?
Also it is true that certain wipes from recovery brick your device?
Click to expand...
Click to collapse
Yes flashing a rom on a 4.2 bootloader that was made to work on a 4.1 bootloader will most likley cause a bootloop or a softbrick but should be able to be recovered in most cases.
The main cause of bricked devices atm is flashing the incorrect recovery for your bootloader version. This is flashing a non-4.2 recovery on a 4.2 bootloader, causes a fastboot flash brick - more info on this in my how-to in sig below.
I'm not sure about bricking your devices using wipes in recovery but the wipe data option in the bootloader menu will in most cases brick the device.
Not sure what the best method is but I pefer using the fastboot method over the twrp method but it's up to you, however the fastboot method does seem to work even with a locked device (but try at own risk).
It's up to if you want to do the NVFlash backup, it is suposed to be a fail safe in case of brick, although this does seem to depend on how the device was bricked. ie does not seem to work with the fastboot flash brick.
If you need more info or would like a step-by-step on how to unlock and upgrade for your situation just let me know.
pjc21 said:
It's up to if you want to do the NVFlash backup, it is suposed to be a fail safe in case of brick, although this does seem to depend on how the device was bricked. ie does not seem to work with the fastboot flash brick.
Click to expand...
Click to collapse
How is a fastboot flash brick caused?
pjc21 said:
If you need more info or would like a step-by-step on how to unlock and upgrade for your situation just let me know.
Click to expand...
Click to collapse
Thank you. I understand what to do but I don't feel confident. I've been happy flashing my HTC Desire HD for a long time and never had issues but I've seen so many bad stories on these forums it's really making me uncomfortable. I really want to go ahead and flash my device as it's slow and keeps crashing, and I want to be able to flash different ROM's without breaking a sweat. But I'd rather have a slow crashing device than a bricked one.
pjc21 said:
ie does not seem to work with the fastboot flash brick.
Click to expand...
Click to collapse
Sources? I've never seen anyone with NVFlash even say they experienced any bricks. I don't see why it wouldn't be recoverable. As far as I've seen, everyone who succumbed to the "4.1 recovery on 4.2 bootloader" brick had no NVFlash backups. Unless you're talking about a different brick, in which case you lost me. NVFlash should work just fine with any brick. Unless you brick it while restoring your NVFlash backups, in which case, you're boned.
EndlessDissent said:
Sources? I've never seen anyone with NVFlash even say they experienced any bricks. I don't see why it wouldn't be recoverable. As far as I've seen, everyone who succumbed to the "4.1 recovery on 4.2 bootloader" brick had no NVFlash backups. Unless you're talking about a different brick, in which case you lost me. NVFlash should work just fine with any brick. Unless you brick it while restoring your NVFlash backups, in which case, you're boned.
Click to expand...
Click to collapse
No sources, I was just going off a few comments in this thread but they don't state weather they did actually have nvflash backup or not, just that there was no fixing with nvflash.
I agree with you that as long as you can boot to apx and have nvflash backup and don't brick during nvflash restore then you should be able to unbrick from any brick.
Sorry for any confusion here.
pjc21 said:
No sources, I was just going off a few comments in this thread but they don't state weather they did actually have nvflash backup or not, just that there was no fixing with nvflash.
Click to expand...
Click to collapse
Where? I went through the thread backwards from the last page back to page 7 or 8. Only one person even mentioned NVFlash, and he was asking if he could use NVFlash backups from a different tablet because he didn't have any of his own (that's not possible because of the way the bootloaders are signed). I also didn't see anyone actually tell him it wasn't possible. He was the third to last post in the thread.
So nobody in that thread (after page 7, anyway) said anything about NVFlash let alone that it doesn't work. NVFlash should work just fine to fix the fastboot bricks, just like any other brick.
Edit: So one other guy in a random post just kind of said NVFlash wouldn't work, nothing else - no details at all. A couple people asked him for details and proof, but he never replied. I have a feeling he meant NVFlash couldn't help because he didn't have any backups. If you have the NVFlash backups, you can recover from pretty much any brick.
Thank you guys for your help.
So does the following plan sound safe to you?
1. Backup my device (apps, data and sdcard)
2. Unlock with Asus unlock tool (v7 right?)
3. Do NVFlash Backup
4. Do official ASUS upgrade to JB 4.1 (I would do this by extracting the download from their site onto my SD card right? Because once unlocked I won't get offered any updates)
5. Once on JB, flash the correct 4.1 TWRP onto my recovery via Fastboot
6. Get Flash happy with my 4.1 compatible ROM's, do a few data wipes in between.
Sounds good to me. As long as you check version numbers and filenames carefully, there shouldn't be a problem.
What about on an Unlocked device
Back in March when Jelly Bean 4.2 came out I went from a rooted and unlocked machine to the newest stock os (10.6.1.8) I am looking to upgrade to the official 10.6.1.15.3 that is available on the ASUS site. Is it as simple as downloading the ASUS updateLauncher and putting it on my sd card and running it from the tablet? Or am I at risk being on an unlocked device, do I need to add any other steps?
teedoe said:
Back in March when Jelly Bean 4.2 came out I went from a rooted and unlocked machine to the newest stock os (10.6.1.8) I am looking to upgrade to the official 10.6.1.15.3 that is available on the ASUS site. Is it as simple as downloading the ASUS updateLauncher and putting it on my sd card and running it from the tablet? Or am I at risk being on an unlocked device, do I need to add any other steps?
Click to expand...
Click to collapse
From what I know you should be able to upgrade from stock version to a newer stock version without any issues. The only thing I'm not sure about is if that method will wipe all your data. I'd advise a backup first.
psjw12 said:
From what I know you should be able to upgrade from stock version to a newer stock version without any issues. The only thing I'm not sure about is if that method will wipe all your data. I'd advise a backup first.
Click to expand...
Click to collapse
Well now I am stuck, here is what I tried without success.
Backed up my data
Downloaded the newest file from ASUS - 10.6.1.15
Placed file on my internal SD
Renamed it to US_epad-user-10.6.1.15.3.zip
System Update is detected so I tried to run it from the OS - but it fails, gives me a Unknown Error (2) and restores itself to previous. I tried it twice with no luck.
Any idea how I can get this file to update.
Thanks,
teedoe said:
Well now I am stuck, here is what I tried without success.
Backed up my data
Downloaded the newest file from ASUS - 10.6.1.15
Placed file on my internal SD
Renamed it to US_epad-user-10.6.1.15.3.zip
System Update is detected so I tried to run it from the OS - but it fails, gives me a Unknown Error (2) and restores itself to previous. I tried it twice with no luck.
Any idea how I can get this file to update.
Thanks,
Click to expand...
Click to collapse
Did you remove any apps or system files? If your ROM isn't 100% exactly stock before the update, the update will fail.
It was a simple mistake, I just needed to extract the zip file I downloaded from ASUS one time and then transfer it to my SD card. Worked perfectly after that and I did not lose any data or apps.
Thanks to all on the forums for your advice and help!
Hi, I unlocked my TF300T sotck ICS 4.0.3 with the Asus app, I flashed CWM and the root_signed thingy without a problem. I then did a data wipe, cache and dalvik wipe and flashed CM10 stable build for TF300T and the Gapps zip. I reboot and it's stuck on ASUS screen. I'm currently doing a restore of the "nandroid". Will this restore my tablet to ICS? What did I do wrong? How do I get either Cm10 to work or return to the ICS? Also, if I need to flash something else, how do I do it? Does the CWM recognize msd cards? Because all I have on the internal memory is the CM10 which currently did not work for me. I'm a little desperate right now. Thanks.
EDIT: DAMN IT, I just got an error restoring data. What the hell do I do? Please!
i tried restoring again and reflashing cm10 and the gapps and still nothing changes. I did wipe again the caches and still nothing. Also I can't download other roms to the tablet because my computer doesn't recognize the tablet because it hasn't booted and the cwm won't recognize micro sd cards. So I think flashing something else isn't an option. Did I break my tablet completely? I'm almost in tears
I tried several things due to some searches on different forums but nohitng works. I tried wiping caches and reflashing Cm10, didn't work. I tried pluggin my tablet to my computer and sending the asus stock rom via ADB and flashing that, but CWM gives me an "installacion aborted" error. I just don't know what to do nor I understand what went wrong. I did everything according to multiple tutorials. Unlocking, flashing CWM and rooting went just fine. But installing CM10 ended up pretty much destroying my tablet. I wanna kill myself.
I think you have a brick??!! :'( cm10 is jellybean and you where on ics and you probably didn't flash the jellybean bootloader did you?
Sent from my ASUS Transformer Pad TF300T
Not a single tutorial said that I had to do that. Every tutorial says "unlock bootloader, flash cwm, flash root_signed, flash cmrom". I did just that. Are you telling me that my tablet is lost forever?
in most cm threads (except cm9) their is stated that you atleast need android 4.1.1 with it's bootloader or 4.2 with it's bootloader, what i suggest you try is to flash a bootloader and upgrade staight to 4.1.1 you can download the firmware from asus the links are on this guide: http://forum.xda-developers.com/showthread.php?p=39272826 FOLLOW THIS GUIDE CORRECTLLY OR YOU MIGHT PERMANENTLY BRICK YOUR TABLET!!!!
EDIT: if you get an error during flash it's probably the drivers or a fastboot flash brick wich is only fixable by replacing the motherboard!!
Sent from my ASUS Transformer Pad TF300T
If what you say is true, then you can't flash CM10 on a stock ICS tablet, and that goes against every freaking tutorial I've read before messing with my tablet.
What exactly is your bootloader version?
Sent from my ASUS Transformer Pad TF300T
I'm not sure what my answer is. The "bootloader" was unlocked by the Asus app from their website. I did that by downloading (I believe it was V7) the apk from their website and installing that and unlocking the tablet. From there on, I just followed did fastboot flashing CWM and rooting. I never read a tutorial that said "you should flash JB bootloader before installing cm10". In fact I thought that just by unlocking the tablet, rooting and flashing the custom recovery one could just install a custom rom regardless of wether it's JB or not. It's funny because I didn't want to upgrade to stock JB because it seemed buggy from a lot of reviewers, and CM10 was the classic option to have JB and a lot of great features and speed. So I google time and time again how to flash CM10 on a ICS stock ASUS. I just followed the tutorials for that.
is my tablet unrecoverably bricked? I also tried fastbooting and "flash system blob" with the blob for the ICS 4.0.3 firmware, after a while of "sending" the file in the command prompt, I got a blue progress bar in the fastboot screen on the tablet and then "FAILED". So I guess that doesn't work either.
Nothing will work?
Try entering fastboot reboot: does your tablet reboot or does it hang?
cm10 is android 4.1 it seems logical that it only runs on a 4.1 bootloader and not on an ics one! most posts must have said that you atleast need jelllybean 4.1.1
I was confused in the beginning aswell because my phone accepts any rom no matter what bootloader version!
Sent from my ASUS Transformer Pad TF300T
If it makes so much sense that CM10 with JB 4.1 only boots with the JB bootloader, then how the hell one can go from ICS to CM10?! Google tutorial flash cm10 on asus tf300t stock ics and you'll find a thousand tutorials not one of which says you need JB bootloader. I mean, I assume one could upgrade to the official JB rom and then unlock bootloader, etc, but I'm telling you, every tutorial that said "stock ics to cm10" did no mention the bootloader version issue. I'm not trying toblame anyone other than myself for "bricking" my tablet, but I read so many tutorials to ensure I wouldn't mess it up that I'm very upset about this.
I can use fastboot and adb commands. But I haven't been able to flash the ICS stock rom so far. First of all, it's not on the Asus website anymore, and the one I got from the web gave me this error on CWM "instaling update.. installation aborted". I also tried flashing the .blob via fastboot and it also failed. It seems nothing works. Any thoughts, anyone?
philos64 posted links to some old ICS ASUS firmwares in this post:
http://forum.xda-developers.com/showpost.php?p=33883254&postcount=3
Maybe worth a try ? Never been on ICS myself - just thought I'd mention this source...sorry for wasting your time if this is what you already tried.
Yeah, I tried flashing the ICS 9.4.3.30 (my stock rom) and it didn't fly (said installation aborted) and also tried to flash it as a blob and it failed. I guess I deserve this, but I just can't bellieve this isn't fixable.
samus88 said:
Yeah, I tried flashing the ICS 9.4.3.30 (my stock rom) and it didn't fly (said installation aborted) and also tried to flash it as a blob and it failed. I guess I deserve this, but I just can't bellieve this isn't fixable.
Click to expand...
Click to collapse
We would like to know what bootloader you now have. You use the bootloader menu to get to cwm. Tell us how many ICONS you have and what they are. This way we will have more info to consider options if any.
It's ICS. I have the Wipe Data and the Coldboot option. If I'm connecte with the usb cable, there's also the usb icon.
Currently I don't have the tablet, because I send it to a tech support place and they should give me a repair budget (if they deem it repairable, I guess) by tomorrow, but I'm not confident that they'll be able to fix it. So I'm still open to suggestions. Thanks!
samus88 said:
It's ICS. I have the Wipe Data and the Coldboot option. If I'm connecte with the usb cable, there's also the usb icon.
Currently I don't have the tablet, because I send it to a tech support place and they should give me a repair budget (if they deem it repairable, I guess) by tomorrow, but I'm not confident that they'll be able to fix it. So I'm still open to suggestions. Thanks!
Click to expand...
Click to collapse
I reread the thread and I believe I would make a blob with just stock recovery (4.03) to match your bootloader. I know fastboot is failing on a complete blob but may process something as small as recovery. The blob could also be pushed to your tablet with adb and flash with that.
I made these choices as a place to begin since we need to match your bootloader.
Once stock recovery was in place we could use adb to push a once unzipped stock firmware (4.03) and get stock recovery to install it for us.
Thanks a lot man. When I get the tablet back and you make me that blob I'll definitely give it a try. Although I have a question, I already have the once unzipped stock ICS on my tablet (pushed it with ADB), how do I install it with stock recovery should flashing that blob work?
samus88 said:
Thanks a lot man. When I get the tablet back and you make me that blob I'll definitely give it a try. Although I have a question, I already have the once unzipped stock ICS on my tablet (pushed it with ADB), how do I install it with stock recovery should flashing that blob work?
Click to expand...
Click to collapse
With stock recovery in place go into bootloader and pretend you are going into cwm that activates stock recovery now. If android lays down we'll rename the zip to EP201_768_SDUPDATE.zip and try again.
I'll download 4.03 and make the recovery blob tomorrow so we'll be ready.
Sorry about that. I read "I would make" as "I will make", lol. Is there a stock recovery 4.0.3 blob on the internet for download? I'll get some sleep now, but I'll try to prepare everythng for when I get the tablet back, assuming I don't have fixed for me by tech support (although I'd love not to have to pay forit, right)
samus88 said:
Sorry about that. I read "I would make" as "I will make", lol. Is there a stock recovery 4.0.3 blob on the internet for download? I'll get some sleep now, but I'll try to prepare everythng for when I get the tablet back, assuming I don't have fixed for me by tech support (although I'd love not to have to pay forit, right)
Click to expand...
Click to collapse
No, there is the full blob in the factory firmware and that is what I'll use. It only takes a couple of minutes to extract the recovery image file which might flash and then re-blob just the recovery partition.
Downloading takes longer than everything else.
Update:
This zip contains stock 4.03 recovery as a blob and as an image file.
Unzip and try flashing the blob - if it fails try flashing twice more or until success. If it still fails try flashing the image file - three times if it fails.
Note:
These are to be flashed with fastboot or adb, not cwm.
Great, thanks man. Unfortunately, I won't have my tablet until at least wednesday because of the holiday on my country (independence day and such). But I'll give it a try and get back to you.