Related
So, my brand new Transformer came yesterday (From Amazon) and it has an SBK v2 bootloader (sbk detect under mac, serial is BC0KAS), here is what I understood, and ask for questions, after many reading, can you please confirm or correct?
1- SBK v1 can be rooted, put custom roms, return back to stock, unbrick in case something goes wrong with nvflash. [CONFIRMED]
2- SBK v2 can be rooted? (some say B70 can, or is it just B70 with SBK v1?) [CONFIRMED]
3- SBK v2 can have custom roms? (depends on point 2)? [CONFIRMED]
4- SBK v2 cannot have ClockWorkMod? [Wrong, SBKv2 CAN have ClockWorkMod]
5- SBK v2 does NOT support nvflash, so if you softbrick you cannot recover (I am certain of this one, I guess). [CONFIRMED, if you damage ROM & clockworkmod = BRICK]
What can be done then with an SBK v2 device? wait for developers to find the ways to crack it (as sbkv1), or have an nvflash working?
Is there some petition open to tell Asus to unblock the bootloader as they did with the Transformer Prime?
currently (after 1 day), I am already thinking of returning it back.
I know i might be asking a lot of questions, but information is not easily available in 1 thread.
Update:
New question: with SBKv2 is it possible to return back to stock (Stock ROM, unrooted with stock recovery)?
Thanks in advance...
SBK doesn't keep you from rooting from what I understand, the firmware version does (current 8.6.5.21 has been cracked and can be rooted by nachoroot, or if not can be firmware upgraded to 8.6.6.19 and rooted with razorclaw)
SBK2 simply keeps you from using NVFlash to recover, as far as I know, once you are rooted, you can install CWM recovery on any SBK version.
Just alot of SBK2 owners have not rooted or installed CWM if they did root for fear of losing their recovery (if you bungle the recovery, you may be able to flash your recovery through the ROM, if you mess up your ROM, you can flash another ROM through CWM or stock recovery, BUT if your recovery img is corrupted AND your ROM stops working, SBK1 can flash both via NVFlash, SBK2 is effectively bricked)
EDIT: SBK2 USED to keep you from being able to root when NVFlash was the only method available for rooting and installing superuser and busybox, see here
http://forum.xda-developers.com/archive/index.php/t-1347388.html
I was going to say I will try to NVFlash my device and tell you if it is SBK1 or 2, I assumed it would be SBK2 because it is B70, but lo and behold it was SBK1..I would have been lucky a few months ago before the razorclaw app was developed and SBK2 was rooted, but I didn't get my TF until after that..
So, SBK1 here have gone to stock many times, but cannot confirm the procedure for SBK2 tablets, though I assume it is possible. Thought for sure I was going to be able to come back and say my TF was SBK2 and had been to stock, but nope haha
EDIT: considering you can backup your entire setup via CWM, recovery mage and all, and flash it wthin CWM (like restoring the backup) is evidence to me that you can no doubt unroot an SBK2 as long as you have a working recovery image.
From what I understand, the first thing to do on a new device is to have root (with the tools you mentioned), once you have this (stock ROM with root), you can install CWM, and with CWM you can install custom and stock roms.
but how can I bring back the standard Stock recovery? when I have stock unrooted ROM I can't flash Recovery partition from the Android itself, and nvflash doesn't work on SBK2. can CWM be used to flash a stock recovery over itself?
Is there any chance that Asus will unlock the TF101 when it releases the tool to unlock the Transformer Prime (in February, as promissed)? in case they both use same blocking technology?
mcbyte_it said:
From what I understand, the first thing to do on a new device is to have root (with the tools you mentioned), once you have this (stock ROM with root), you can install CWM, and with CWM you can install custom and stock roms.
but how can I bring back the standard Stock recovery? when I have stock unrooted ROM I can't flash Recovery partition from the Android itself, and nvflash doesn't work on SBK2. can CWM be used to flash a stock recovery over itself?
Is there any chance that Asus will unlock the TF101 when it releases the tool to unlock the Transformer Prime (in February, as promissed)? in case they both use same blocking technology?
Click to expand...
Click to collapse
Yes you can flash stock recovery over cwm from within cwm, you have to have the file..i found it and have it on my hard drive, but can't remember where i got it from..the same procedure as going stock on sbk1 tablets
The proof that you can flash recovery while in recovery mode is that you can install higher versions or different developer's versions of recoveries from cwm. Im sure when running cwm it is being read from ram so flashing the recovery partition will only affect your recovery after you reboot (i.e. Can technically go into cwm, flash recovery partition first and then flash stock rom, but i believe packages are available to flash both at once, and there would be no reason to do it in this order, but im pretty sure it could be done)
Somewhere on here is a guide how to return to stock to prepare for the ics update, it should contain the odd bits and links to fill in my sparse knowledge.
Getting back to stock ROM and recovery
http://theunlockr.com/2011/11/28/how-to-unroot-and-remove-cwm-recovery-on-asus-transformer/
That's the one!
8329 recovery.zip.. Btw it should be noted that the recovery image is not region-branded, that should mean it will work with any region, while you will need to make sure to get the region-specific firmware..
And i did the procedure in reverse from that thread, not to confuse, but i:
Placed both files (recovery and firmware) into my sd card root
Booted into cwm and flashed stock recovery, wipe everything before powering down
Rebooted into recovery again and flashed the firmware with stock recovery.
I think it will work either way, i left my rooted rom in place so i could install cwm if the recovery flash failed, i suppose the alternative is leaving your recovery in place in case the stock rom flash fails..i just like knowing on the first reboot whether my first flash was successful and not flashing blind imo.
Bump.
This post suggest new Transformers can be nvflashed too.
http://forum.xda-developers.com/showthread.php?t=1518552
Waiting for answer from OP to see what he has to say.
Anyone else got any news?
josteink said:
Bump.
This post suggest new Transformers can be nvflashed too.
http://forum.xda-developers.com/showthread.php?t=1518552
Waiting for answer from OP to see what he has to say.
Anyone else got any news?
Click to expand...
Click to collapse
SBK v2 is still not nvflash compatible
josteink said:
Bump.
This post suggest new Transformers can be nvflashed too.
http://forum.xda-developers.com/showthread.php?t=1518552
Waiting for answer from OP to see what he has to say.
Anyone else got any news?
Click to expand...
Click to collapse
That thread is full of bad information and garbage. I would forget it exists.
I was under the impression from reading different Asus statements that the sbk for TF-101 was going to be released with ICS the way it was with TF-201, did Asus not keep their word on this?
Cheers!
-M
Xda member since 2007
dragon_76 said:
I was under the impression from reading different Asus statements that the sbk for TF-101 was going to be released with ICS the way it was with TF-201, did Asus not keep their word on this?
Cheers!
-M
Xda member since 2007
Click to expand...
Click to collapse
That would be news to me. If you could find a source for this statement, I would be interested.
From what I understood reading (this forum and other sites), the story is different between TF101 and TF201: the Prime has the bootloader locked/encrypted, and with it locked you can't even install the CWM recovery, while with sbkv2 you can do everything except nvflash, so i doubt that asus will release anything for the sbkv2 transformers.
anyway, i am not following the subject, but does the new Prime unlocker allow something like nvflash to work?
mcbyte_it said:
5- SBK v2 does NOT support nvflash, so if you softbrick you cannot recover (I am certain of this one, I guess). [CONFIRMED, if you damage ROM & clockworkmod = BRICK]
Click to expand...
Click to collapse
What can I do with brick? Only waiting for some solution?
Did Asus could repair it for a fee?
RMA
Thinking about calling ASUS to ***** about this tablet being locked and demanding the opportunity to either downgrade to sbk1 or upgrade to a prime. I'll let y'all know my findings.
Styxiak said:
What can I do with brick? Only waiting for some solution?
Did Asus could repair it for a fee?
Click to expand...
Click to collapse
Until a solution is found, you can use a bricked device as a very nice door stop.
Sent from my Transformer TF101 using Tapatalk 2
A solution has been found
http://forum.xda-developers.com/showthread.php?t=1688447
nvflash for sbk v2,finally ?
android root .mobi has a released a a solution, i am going to try it, will post results when done
The revival of the thread from the dead! -dun dun dun-!
Anyway, yes 'Wheelie!' Nvflash for Sbkv2 devices has been released, and works very well on my b70 Sbkv2
it only works on the tf101 though, not the G or Slider.
I'm about to buy used Eee Pad Transformer TF101, with dock/keyboard. It has serial number starting with B90KAS and latest firmware update (ICS).
What is the current status of bootloader unlocking craft? Would I be able to install Ubuntu/OpenSUSE and/or use custom kernels with latest KatKiss ROMs?
As a fresh TF300-owner I was wondering if it is possible to create a nandroid backup (and restore oc) without unlocking my device.
I have rooted my device, but don't need unlocking (no intentions to flash roms). However, a full backup gives me some peace of mind. Is there any way to achieve this without unlocking? (I think I know the answer, but I hope I missed a way to achieve this...)
Aside, as I am asking already, do you have advice to maximize root-advantage? I have rooted specifically for the Switch Me-app (purchased, it is so good!) and for AdFree.
As I have root now, do you guys have any suggestions for "must-have" apps or tweaks that require root?
Any help is appreciated, thanks in advance!
Ok, have been reading further and what I already thought seems to be true: Without unlocking no nandroid backup...
Well, good to know and to keep in mind. Of course, if I missed something, I love to hear :fingers-crossed: And if anyone has suggestions for root-dependend apps or tweaks, I'm still interested
Thus far I found the following suggestion myself:
Minor tweaks and speed increase , specific post 261 as I am on WW fw .30
Some app suggestions from the Prime topic
Needless to say more suggestions are always welcome
Simply put..nandroid backup is a function of cwm recovery. To get cwm recovery installed, the boot loader must be unlocked. So therefore, no nandroid backup can occur without an unlocked boot loader. I've seen a windows root program with other Android devices that roots, unlocks the boot loader, installs cwm recovery and offers its own internal backup feature. But again, that's only possible with an unlocked boot loader
Sent from my SGH-I777 using Tapatalk 2
cavsoldier19d said:
Simply put..nandroid backup is a function of cwm recovery. To get cwm recovery installed, the boot loader must be unlocked. So therefore, no nandroid backup can occur without an unlocked boot loader.
Click to expand...
Click to collapse
Yes, after searching, reading, re-reading, more searching, reading again, another google attempt (at that time I wasn't searching for the answer, but for my desired answer (to find out that the desired answer doesn't exist) ) I finally came to this conclusion too.
Well, no nandroid backup then for me, cause don't want to unlock bootloader, except the backup there is no need for me (at least not yet, future experience might change my opinion).
Thanks for explaining anyway!
Isn't there another way of installing CWM tho? Defy's can install it with a locked bootloader (2ndinit).
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
There may be other methods to installing cwm recovery, however no matter which method u use, it will still require unlocking the boot loader. Unlocking the boot loader and flashing a custom recovery are two seperate processes
Sent from my SGH-I777 using Tapatalk 2
That's what I mean tho, the Defy didn't have an unlocked bootloader but still had CWM...
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Yes u are right. There is an app (i dont remember the name), which let u to install cwm on locked bootloader. However it needs to have possibility to flash cwm port for specific phone/tablet and now it can only flash port for tf300 - it is flashing this for tf101 and it can brick our tf300.
Sent using r800i with DoomKernel v14 (460mHz/1.21gHz)
Every Android device is different when it comes to rooting, flashing roms and flashing recoveries. Its the same reason why we can't just use one root program for all Android devices unlike jail breaking an iPhone. Every Android manufacturer and model will vary with boot loaders, partitions, root exploits and everything else. What may work for one Android device will not work for another. And at this time, on the tf300, there is no other way to install a custom recovery without unlocking the boot loader...unless we just had a breakthrough that I'm not aware of. We are all hoping for that breakthrough to come.
Sent from my SGH-I777 using Tapatalk 2
If you are able to root the device and install busybox, there is a method!
cavsoldier19d said:
Simply put..nandroid backup is a function of cwm recovery. To get cwm recovery installed, the boot loader must be unlocked. So therefore, no nandroid backup can occur without an unlocked boot loader. I've seen a windows root program with other Android devices that roots, unlocks the boot loader, installs cwm recovery and offers its own internal backup feature. But again, that's only possible with an unlocked boot loader
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Actually, nandroid backups aren't limited to recovery. You could nandroid using fastboot if you like. Recovery just makes it easier. In fact, pretty much every function of recovery can be performed using fastboot. You need to unlock the bootloader to access fastboot, though, so that doesn't really help here. Just thought I'd point that out.
Hi all,
After having successfully rooted my TF700 lately (while keeping the bootloader locked), I've been looking into unlocking the bootloader so I can flash a custom ROM (thinking about CROMI). Before flashing a custom ROM, people seem to recommend getting nvflash in order.
My problem is, however, I'm already on JB, and my understanding is that you need an ICS .26 bootloader (or earlier) in order to setup nvflash. I know that it's possible to downgrade the firmware from JB to ICS (in fact, this is what I did in order to be able to root my device - going from the latest JB to ICS .30); however, after searching around a fair bit, I'm still not clear on whether it's possible to revert the bootloader to an earlier version.
Can someone please clarify this for me. If I've already updated my device to JB, is there absolutely no way for me to set up nvflash?
Thanks!
joshnl said:
Hi all,
After having successfully rooted my TF700 lately (while keeping the bootloader locked), I've been looking into unlocking the bootloader so I can flash a custom ROM (thinking about CROMI). Before flashing a custom ROM, people seem to recommend getting nvflash in order.
My problem is, however, I'm already on JB, and my understanding is that you need an ICS .26 bootloader (or earlier) in order to setup nvflash. I know that it's possible to downgrade the firmware from JB to ICS (in fact, this is what I did in order to be able to root my device - going from the latest JB to ICS .30); however, after searching around a fair bit, I'm still not clear on whether it's possible to revert the bootloader to an earlier version.
Can someone please clarify this for me. If I've already updated my device to JB, is there absolutely no way for me to set up nvflash?
Thanks!
Click to expand...
Click to collapse
Once you're on JB, the lowest you can downgrade is ICS .30. You're too late for Nvflash. No way around it.
Okay... sucks, but thanks for the info. That's what I was afraid of.
Since that is the case, how critical is it to set up nvflash before getting into the whole custom ROM thing? Am I crazy to get into it without nvflash as a backup plan?
joshnl said:
Since that is the case, how critical is it to set up nvflash before getting into the whole custom ROM thing? Am I crazy to get into it without nvflash as a backup plan?
Click to expand...
Click to collapse
There is a bug in the bootloader that you should be aware of: If your recovery is broken because it is
* too old, designed for the ICS bootloader, or
* you erased it via fastboot
then you should NEVER EVER choose "wipe data" from the bootloader menu. Except you want an expensive paperweight. Because then you can't even enter fastboot to fix it. This is the only situation where nvflash would really help you out.
If you always test any newly flashed recovery first by using the power+volume buttons, you are safe.
Thanks, _that!
_that said:
There is a bug in the bootloader that you should be aware of: If your recovery is broken because it is
* too old, designed for the ICS bootloader, or
* you erased it via fastboot
then you should NEVER EVER choose "wipe data" from the bootloader menu. Except you want an expensive paperweight. Because then you can't even enter fastboot to fix it. This is the only situation where nvflash would really help you out.
If you always test any newly flashed recovery first by using the power+volume buttons, you are safe.
Click to expand...
Click to collapse
I know man who did wipe data from bootloader, it didn't brick him He has done this today on unlocked, TWRP and CROMI on TF300T. The newest bootloader fix it.
Hazard17 said:
I know man who did wipe data from bootloader, it didn't brick him He has done this today on unlocked, TWRP and CROMI on TF300T. The newest bootloader fix it.
Click to expand...
Click to collapse
It would not brick him if he installed the latest version the either recovery -- that's exactly what _that said.
Simply put, just keep your recovery up-to-date when major versions release and update the bootloader. When things such as this happen, they will be posted in the rom threat, just make sure you read thoroughly. Also, read the change log before upgrading the recovery, and if you use TWRP use GooManager and it will upgrade it for you at a tap of a button.
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.