Database Info

Going to root, am I doing it right?

I am on stock 4.0.4 with a locked bootloader. I want to have root with the stock rom, nothing else just root.
So I am gonna use the tool provided here,
http://forum.xda-developers.com/showthread.php?t=1544940
I have already installed drivers and have the tool downloaded.
Then I would like to flash the stock google 4.0.4 rom that will let me receive OTA updates. Is this the right file?
http://forum.xda-developers.com/showthread.php?t=1569509
Or can I just flash the stock rom from here?
http://forum.xda-developers.com/showthread.php?t=1572307
I heard there are problems flashing stock rom with CWR if the stock recovery isnt removed? Thats why I dont know if I should flash the stock image.
Is the process of flashing rom with CWR recovery the same as with stock recovery?
My phone is the i9023.
Thanks a bunch in advance.

Gambler_3 said:
I am on stock 4.0.4 with a locked bootloader. I want to have root with the stock rom, nothing else just root.
So I am gonna use the tool provided here,
http://forum.xda-developers.com/showthread.php?t=1544940
I have already installed drivers and have the tool downloaded.
Then I would like to flash the stock google 4.0.4 rom that will let me receive OTA updates. Is this the right file?
http://forum.xda-developers.com/showthread.php?t=1569509
Or can I just flash the stock rom from here?
http://forum.xda-developers.com/showthread.php?t=1572307
Is the process of flashing rom with CWM recovery the same as with stock recovery?
Thanks in advance.
Click to expand...
Click to collapse
Baseband version? under about phone

billchen0014 said:
baseband version? Under about phone
Click to expand...
Click to collapse
i9023xxki1.
Sorry should have specified my phone in the OP.

Best way is to do it manually. You can find all of the steps required here. The only difference is that you should be flashing the latest recovery from here and the latest superuser.zip file when flashing with recovery.
Note, unlocking bootloader will cause loss of EVERYTHING on the device that you have put on there (sdcard, apps, data partition, etc).

Harbb said:
Best way is to do it manually. You can find all of the steps required here. The only difference is that you should be flashing the latest recovery from here and the latest superuser.zip file when flashing with recovery.
Note, unlocking bootloader will cause loss of EVERYTHING on the device that you have put on there (sdcard, apps, data partition, etc).
Click to expand...
Click to collapse
You suppose thats better to do manually so I will have latest version of recovery and superuser?
And yes I am aware of the data loss waited sometime to finish all my games now I am ready to lose all my app data.

Harbb said:
Best way is to do it manually. You can find all of the steps required here. The only difference is that you should be flashing the latest recovery from here and the latest superuser.zip file when flashing with recovery.
Note, unlocking bootloader will cause loss of EVERYTHING on the device that you have put on there (sdcard, apps, data partition, etc).
Click to expand...
Click to collapse
Do it this way. The one click is fine but using Android SDK and going through all that will help you in the long run. This way you know the process in case something goes wrong. It may be confusing at first but worth it. It will teach you a lot more than flashing a one click!
I learnt a lot from this and feel much more experienced and capable because of it. I know I will be able to solve any major issues using Android Debug Bridge (adb).

Okay then I am gonna try the manual way and gonna take out time for it. Now I just need to know what do I flash once I have unlocked bootloader and installed CWR?
I just want the stock google rom and receive OTA if nexus S continues to be supported by google.

You won't need to reinstall the ROM if you are currently on 4.0.4. The ROM stays there as-is. Feel free to do your wipes in recovery and reflash stock 4.0.4 through CWM if you must. You flash CWM to your phone and then superuser through CWM.
Steps:
Setup ADB/fastboot
Bootloader --> fastboot oem unlock --> agree
Bootloader --> fastboot flash recovery recovery.img --> this will give you CWM
Recovery --> flash superuser.zip and, if you must, wipe and reflash ICS (flash su AFTER this if done)
Reboot --> bingo
Also note, with stock ROMs it will replace your current recovery with stock recovery on each boot. If you want to keep CWM, delete /system/etc/flash-recovery.sh when you first boot. You'll have to reflash recovery afterward and it will stick.

Oh I was of the impression that unlocking bootloader wipes everything means it wipes the OS as well. That is nice if it's just data and not the OS, dont think I would reflash it if it's not needed.
Can you explain what you mean by will have to reflash recovery? I will have to do that even if I delete that file on first boot? And whats the drawback if I dont delete that file and stick with stock recovery?

As soon as you boot into stock android it will replace the recovery. So if that file is there on first boot, it will replace it while booting and you will be without CWM (stock instead). After first boot you can delete the file (you can reflash a ROM which has this deleted, or delete it yourself from a stock ROM, or even use adb or a recovery-based file manager to delete the file, then you won't have this problem at all) and it will no longer reflash stock recovery, but you would already have the stock one and need to flash CWM one more time to get it to stick. Easiest way is to just flash CWM and delete it within android imo, saves mounting commands and the such.
No downside really. If you need to flash something for one reason or another you'll just have to reflash CWM before you do so. Once rooted, ROM Manager can do this for you within android anyway.

I had already downloaded and installed the drivers from the one click root thread and my computer shows the android adb thing when I connect my phone with USB debugging.
But as you guys suggested I am gonna do the manual way. So do I just skip the installing driver on computer in the part 1 of this guide?
http://forum.xda-developers.com/showthread.php?t=1007782

In my bootloader menu why is it showing my phone as an i9020?? Is it normal?

Gambler_3 said:
In my bootloader menu why is it showing my phone as an i9020?? Is it normal?
Click to expand...
Click to collapse
Because you have a Nexus S with amoled. That's the i9020. The i9023 is SLCD.

DeuXGod said:
Because you have a Nexus S with amoled. That's the i9020. The i9023 is SLCD.
Click to expand...
Click to collapse
He has the i9023 to my knowledge. It is completely normal, though. Bootloader and recovery for i9020 and i9023 series are the same, this can be attributed to the issue with 4.0.3 recovery backlight not turning on.
If fastboot recognises your phone in the bootloader (the fastboot menu), your drivers are installed an working perfectly.

Finally got to the unlock bootloader screen, didnt do it just yet but now I know how to do it.
I must say the guide is a bit outdated, the software has changed quite a bit seems. The most frustrating part was that the fastboot file is actually in the platform tools folder instead of the tools folder which I didnt figure for a while. I will hold off rooting when I have a whole day off because once I lose everything I would be very anxious to get my phone back to normal which will take time.
Thanks for the help harbb, if I have any problem flashing recovery and superuser I will come back for more help.
And yes I have the LCD version i9023.

Btw the guide said the fastboot will be in the tools folder but the tools folder had a read me that "adb has moved to the platform tools folder" this is how I figured to go to that folder and thats where the fastboot file actually was.
Now it says I should put the recovery image in the tools folder so should I do that or put it in the platform tools folder?

In the instructions for the flashing recovery I am not understanding one thing.
6 - Then back on the SNS select Power Off (Reboot also works)
Part 4 - Root
1 - Power ON the SNS
So after flashing recovery I have to reboot? Since I am on stock rom that would bring back the stock recovery so how would I flash superuser then?
If I delete the stock recovery can I still get OTA updates?

fastboot and adb is now in platform tools, that is correct. Easiest way is to put your recovery in there too so you don't have to type in the absolute file path to it, don't put it in tools.
Don't power off or reboot the phone. After you flash recovery go straight into the recovery menu and root, flash custom ROMs, kernels, etc. You can transfer files to flash via the mounts and storage --> mount usb storage menu. After this feel free to reboot.

Harbb said:
fastboot and adb is now in platform tools, that is correct. Easiest way is to put your recovery in there too so you don't have to type in the absolute file path to it, don't put it in tools.
Don't power off or reboot the phone. After you flash recovery go straight into the recovery menu and root, flash custom ROMs, kernels, etc. You can transfer files to flash via the mounts and storage --> mount usb storage menu. After this feel free to reboot.
Click to expand...
Click to collapse
Just wanted to update that I successfully unlocked and rooted. Thanks a bunch mate.

Gambler_3 said:
Just wanted to update that I successfully unlocked and rooted. Thanks a bunch mate.
Click to expand...
Click to collapse
Good work, been wandering what you were up to on this
Hope you enjoy the possibilities.

Stock JB with custom recovery?

Is there or can it be built; a stock JB ROM which includes the stock JB bootloader with a custom recovery included? For example, those on .26 could flash and then only need to flash the supersu.zip to gain root. This would make it entirely pc-less.

wpbear said:
Is there or can it be built; a stock JB ROM which includes the stock JB bootloader with a custom recovery included? For example, those on .26 could flash and then only need to flash the supersu.zip to gain root. This would make it entirely pc-less.
Click to expand...
Click to collapse
It's very easy to flash recovery onto a stock jelly bean rom. I'm going to post a super detailed video for people like you. I forgot how to flash stuff using fastboot but remembered yesterday. I'll send you a link but in the meantime flash the stock jelly bean rom straight from asus website so you will be on Jelly bean and have the jelly bean boot loaders
Sent from my OGparanoid CM D2tmo

I can do it but fastboot is a pain in the ass and needs a pc. Are you saying my logic to make that custom rom is not possible for technical reason.

1-Have your unzipped files directly in the C drive.
2-have fastboot and the recovery in the same folder on your C drive and name it infinity root. If your on twrp make sure you followed directions and renamed the recovery you downloaded to (twrp.blob)
3-now we need to open up a command prompt. Hit start on your computer and enter cmd to open one up.
4-put your device in fastboot mode and plug it in.
5-enter (cd c:\infinity root) or you could type infi(tab to fill in the rest)
6-type (adb device) to be sure the drivers are good and your computer is seeing the device. It should say daemon started successful
7-now we're going to flash recovery (fastboot -i 0x0B05 flash recovery twrp.blob) This is obviously to flash twrp recovery. If wanting to flash CWM you would have to enter the name of that recovery after typing recovery. Hit enter. You should have a time it finished flashing.
8-type (fastboot -i 0x0B05 reboot) your all done rock on!
Sent from my OGparanoid CM D2tmo

................

wpbear said:
I can do it but fastboot is a pain in the ass and needs a pc. Are you saying my logic to make that custom rom is not possible for technical reason.
Click to expand...
Click to collapse
I'm sorry I read your post in a hurry. I thought you wanted to get recovery on your JB device. You'll need to flash a recovery image first if on jelly bean. You can't root without having a recovery image to flash root you can't flash a modified rom without getting recovery on your device! I just went through this. You'll need a PC to get recovery on your device to make any modifications
Sent from my OGparanoid CM D2tmo

mike216 said:
I'm sorry I read your post in a hurry. I thought you wanted to get recovery on your JB device. You'll need to flash a recovery image first if on jelly bean. You can't root without having a recovery image to flash root you can't flash a modified rom without getting recovery on your device! I just went through this. You'll need a PC to get recovery on your device to make any modifications
Sent from my OGparanoid CM D2tmo
Click to expand...
Click to collapse
that is why I'm asking for a custom rom with stock JB for system, stock boot loadera but with a custom recovery.

wpbear said:
that is why I'm asking for a custom rom with stock JB for system, stock boot loadera but with a custom recovery.
Click to expand...
Click to collapse
As far as I know there isn't a way
Sent from my OGparanoid CM D2tmo

Use twrp. goo manager can install for you no pc needed or course you need to be rooted.

Please Help - Updated JB bootloader - can't boot

I just bought a new Infinity today to replace my Prime. I never bothered unlocking/rooting/etc the Prime but given I'm starting from scratch thought I'd go that route out of the box on the Infinity.
I've been carefully reading all of the guides, etc and have used the unlock tool, then created the nvflash backup files (which involves a custom bootloader first).
I then decided I'd take a stab at trying CleanROM Inheritance. One of the first notes indicates that the latest JB Bootloader is required, so I went ahead and downloaded the US JB Bootloader from the link and flashed as described. Now I can't boot up anymore. I can still get to recovery, etc, but I don't know what I should do next. Was this the wrong thing to do? Or did it not flash right?
What should I do next? I'm not new to flashing but w/ my Galaxy Nexus things have always gone pretty smoothly.
Thanks in advance.
EDIT: Note I tried the initial steps for custom bootloader when setting up for nvflash ( http://androidroot.mobi/t3_nvflash/ ) but it doesn't work this time around...
From the link:
"Now that you are in fastboot mode please run the following command to flash the AndroidRoot bootloader:-
$ fastboot -i 0x0b05 flash staging ebtblob.bin"
But this has no effect....
ALSO,
I had not accepted the software update from Asus yet so I was still on ICS. Does that have anything to do w/ my problem? What should I do?

Kidd_Funkadelic said:
I then decided I'd take a stab at trying CleanROM Inheritance. One of the first notes indicates that the latest JB Bootloader is required, so I went ahead and downloaded the US JB Bootloader from the link and flashed as described. Now I can't boot up anymore. I can still get to recovery, etc, but I don't know what I should do next. Was this the wrong thing to do? Or did it not flash right?
What should I do next?
Click to expand...
Click to collapse
Simply boot to recovery and install CROMI.

Kidd_Funkadelic said:
EDIT: Note I tried the initial steps for custom bootloader when setting up for nvflash ( http://androidroot.mobi/t3_nvflash/ ) but it doesn't work this time around...
From the link:
"Now that you are in fastboot mode please run the following command to flash the AndroidRoot bootloader:-
$ fastboot -i 0x0b05 flash staging ebtblob.bin"
But this has no effect....
Click to expand...
Click to collapse
Are you on Windows? The "$" sign is not used under Windows -- have you tried typing "fastboot -I.... " ?

_that said:
Simply boot to recovery and install CROMI.
Click to expand...
Click to collapse
Are you suggesting that the JB bootloader is not the issue? I would think if I get stuck at the asus screen then it doesn't matter what the ROM is.
Either way I'm stuck at the moment w/out adb and no SD card. I'm running out on my lunch break to pick one up, which should be all I need to get working again. To be safe I'm going to go back to the .30 ICS stock image first. Once I know that worked, I'll take another stab at CROMI.

Kidd_Funkadelic said:
Are you suggesting that the JB bootloader is not the issue? I would think if I get stuck at the asus screen then it doesn't matter what the ROM is.
Click to expand...
Click to collapse
My train of thought was this: You said you can still get to recovery. TWRP supports adb, so you can send the CROMI zip via adb (or use a microSD card if you have one), then install it. CROMI is based on JB, so it is compatible with the JB bootloader, and should boot fine after installation.

_that said:
My train of thought was this: You said you can still get to recovery. TWRP supports adb, so you can send the CROMI zip via adb (or use a microSD card if you have one), then install it. CROMI is based on JB, so it is compatible with the JB bootloader, and should boot fine after installation.
Click to expand...
Click to collapse
Gotcha. I didn't realize TWRP supported adb. Anyway I was able to get back up and running w/ my nvflash backups, though I have to say finding info on actually using the backup files took a ton of digging and some trial and error... Now to try again at CROMI!

I did something very similar and am not sure how to proceed. I have the latest version of twrp and my infinity is rooted + unlocked. It was running ics. I then found what was likely the same US jb bootloader link under a thread that gave instructions for installing cromi. After flashing the jb bootloader via recovery, I got a loading bar, then while attempting to boot is got stuck on the Asus screen. Rebooting leads to a reboot loop. I can still access twrp recovery. Flashing cromi or reflashing the same bootloader yields an error message.
I never did anything with nvflash.
What should I do next? Still kind of fresh to this.

SilentOrchestra said:
Flashing cromi or reflashing the same bootloader yields an error message.
Click to expand...
Click to collapse
And now we are supposed to guess what error message you saw?
The next step is to set up an adb connection from a computer to your TWRP. This way you can get more detailed info what went wrong.

SilentOrchestra said:
I did something very similar and am not sure how to proceed. I have the latest version of twrp and my infinity is rooted + unlocked. It was running ics. I then found what was likely the same US jb bootloader link under a thread that gave instructions for installing cromi. After flashing the jb bootloader via recovery, I got a loading bar, then while attempting to boot is got stuck on the Asus screen. Rebooting leads to a reboot loop. I can still access twrp recovery. Flashing cromi or reflashing the same bootloader yields an error message.
I never did anything with nvflash.
What should I do next? Still kind of fresh to this.
Click to expand...
Click to collapse
To me that sounds like an incompatible bootloader, e.g. ICS bootloader trying to load JB ROM. Could you check the bootloader version?

FordPrefect said:
To me that sounds like an incompatible bootloader, e.g. ICS bootloader trying to load JB ROM. Could you check the bootloader version?
Click to expand...
Click to collapse
I agree, it seems you never updated to a JB rom. A JB boot loader needs a JB Rom, It seems the JB boot loader wont boot ICS. Just flash Cromi and you should be good.
Tylor
Sent from my ASUS Transformer TF700T Infinity Pad Using Tapatalk HD
Rom: CleanRom Inheritance 3.4.4 Odex
Kernal: Hundsbuah V2.0 OC 1.75 GHz
Theme: Timberwolf's Blues & Jazz Theme V1.9

Stuck on ASUS screen while installing CM10

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.

[Q] Overwriting CWM with TWRP and replacing 4.1 with 4.2

Hello everyone!
I'm hoping to get a little bit of guidance from the members here regarding my TF300T. Last week I started down the road to unlocking my TF300 and honestly, I am finding it painfully slow to use. I also have a Samsung Note 2 and find it just blazing fast compared to my TF300. I read a little bit online and having tried a "Factory Rest" etc. I found it still lagged at key entry, browsing etc.
I successfully unlocked my TF300 and then installed CWM. I think however, that the guide I was following was a little outdated (?) because when I went looking for a new ROM to install, most posts STRONGLY recommended TWRP. So my first question is:
If I follow the instructions here:
h t t p : / / teamw.in/project/twrp2/97
using, openrecovery-twrp-2.5.0.0-tf300t-JB.blob specifically, will TWRP automatically install over CWM (on the bootloader partition I believe)? My research and gut is telling me "yes", but I'm hesitant to do this without some additional confirmation.
As a side note, my TF300 currently has Android version 4.1.1 installed. Build: WW_epad-10.4.2.20-20121228.
On another note, I tried to update to Android 4.2 by downloading : TF300T-WW_epad-10_6_1_15_3-UpdateLauncher.zip from the ASUS Website. I extracted the file : WW_epad-user-10.6.1.15.3.zip onto the root of my SDCard, put the card into my TF300. From what I read online, the TF300 was supposed to recognize the file (which it did and I clicked "Install update"). The TF300 rebooted it booted directly into CWM and I received the following error at the bottom of the screen:
E:Invalid command argument
I'm not sure why that error came up, the only thing I can think of is because I have CWM installed?? Can I use CWM to "install zip from sdcard" and would it install Android 4.2? Or if I can successfully install TWRP, can I then use it, to install the 4.2 update? If I do, then would I have to then immediately install openrecovery-twrp-2.5.0.0-tf300t-4.2.blob as I've upgraded to Android 4.2?
Thanks everyone for your help!!!

ACaton said:
Hello everyone!
I'm hoping to get a little bit of guidance from the members here regarding my TF300T. Last week I started down the road to unlocking my TF300 and honestly, I am finding it painfully slow to use. I also have a Samsung Note 2 and find it just blazing fast compared to my TF300. I read a little bit online and having tried a "Factory Rest" etc. I found it still lagged at key entry, browsing etc.
I successfully unlocked my TF300 and then installed CWM. I think however, that the guide I was following was a little outdated (?) because when I went looking for a new ROM to install, most posts STRONGLY recommended TWRP. So my first question is:
If I follow the instructions here:
h t t p : / / teamw.in/project/twrp2/97
using, openrecovery-twrp-2.5.0.0-tf300t-JB.blob specifically, will TWRP automatically install over CWM (on the bootloader partition I believe)? My research and gut is telling me "yes", but I'm hesitant to do this without some additional confirmation.
As a side note, my TF300 currently has Android version 4.1.1 installed. Build: WW_epad-10.4.2.20-20121228.
On another note, I tried to update to Android 4.2 by downloading : TF300T-WW_epad-10_6_1_15_3-UpdateLauncher.zip from the ASUS Website. I extracted the file : WW_epad-user-10.6.1.15.3.zip onto the root of my SDCard, put the card into my TF300. From what I read online, the TF300 was supposed to recognize the file (which it did and I clicked "Install update"). The TF300 rebooted it booted directly into CWM and I received the following error at the bottom of the screen:
E:Invalid command argument
I'm not sure why that error came up, the only thing I can think of is because I have CWM installed?? Can I use CWM to "install zip from sdcard" and would it install Android 4.2? Or if I can successfully install TWRP, can I then use it, to install the 4.2 update? If I do, then would I have to then immediately install openrecovery-twrp-2.5.0.0-tf300t-4.2.blob as I've upgraded to Android 4.2?
Thanks everyone for your help!!!
Click to expand...
Click to collapse
Flashing official rom will automatically overwrite your recovery. In other words, your custom recovery will be gone. Do it with fastboot commands instead of SD Card. If you upgrade to 4.2 (10.6.xxx), you'd need to flash the 4.2 custom recovery again.
If you have CWM, the device doesn't detect the official rom automatically when you select RCK. Flash 4.1 official without custom recovery if you want that to happen.
Once on 4.2 bootloader, you'd have to use either TWRP or the CMW version in the flatline (NV Flash) img. No other CWM works. CMW Flatline installs custom roms ok, but does not back up well, if at all. Which leaves you with TWRP as the only viable alternative. I'd suggest you create the NVflash files first, then install TWRP 4.2.
After that, you can flash any 4.2 or 4.3 custom roms.

graphdarnell said:
Flashing official rom will automatically overwrite your recovery. In other words, your custom recovery will be gone. Do it with fastboot commands instead of SD Card. If you upgrade to 4.2 (10.6.xxx), you'd need to flash the 4.2 custom recovery again.
If you have CWM, the device doesn't detect the official rom automatically when you select RCK. Flash 4.1 official without custom recovery if you want that to happen.
Once on 4.2 bootloader, you'd have to use either TWRP or the CMW version in the flatline (NV Flash) img. No other CWM works. CMW Flatline installs custom roms ok, but does not back up well, if at all. Which leaves you with TWRP as the only viable alternative. I'd suggest you create the NVflash files first, then install TWRP 4.2.
After that, you can flash any 4.2 or 4.3 custom roms.
Click to expand...
Click to collapse
Ok, so to clarify, if I want to flash the official rom from Asus to upgrade from Android 4.1 to 4.2 then I should use fastboot instead of trying via the SD Card. In the process however, it will overwrite CWM (the custom recovery) correct?
Where would I find the instructions on how to use fastboot to install the official rom? I know it would be from the command line, but what exactly would the command be?
Once I've installed the official Asus 4.2 rom, then I can install TWRP correct?
Thanks

There is a useful script. Actual command is
Code:
fastboot -i 0x0b05 flash staging blob
It will overwrite CWM with stock recovery so You may like to install custom one. But be sure that it suitable for 4.2 bootloader.

Graiden05 said:
There is a useful script. Actual command is
Code:
fastboot -i 0x0b05 flash staging blob
It will overwrite CWM with stock recovery so You may like to install custom one. But be sure that it suitable for 4.2 bootloader.
Click to expand...
Click to collapse
Thanks!!
For my own edification, the command from what I can interpret is:
fastboot - the program
-i 0x0b05 - the USB identification
flash - command to flash (as opposed to say reboot)
staging - this I'm not sure of ... staging because it's a new rom that's going to be installed. Curious why it wouldn't be system, as aren't I installing a new system rom?
blog - the blob file I want flashed.
Correct?

Yes. As I understand this, staging - partition used to store something that going to be flashed. Blob from stock firmware contain data for bootloader, recovery, boot, system partitions. Here full description of fastboot command.

I want to update my android too.
I have twrp installed but I want install official rom.
I'll use fastboot (After read some threads, including this) but I have some doubts:
the blob to use is from WW_epad-user-10.6.2.6.zip with 782MB ?

nbranquinho said:
I want to update my android too.
I have twrp installed but I want install official rom.
I'll use fastboot (After read some threads, including this) but I have some doubts:
the blob to use is from WW_epad-user-10.6.2.6.zip with 782MB ?
Click to expand...
Click to collapse
Hey there. Here is my experience with doing what was mentioned in this thread.
I had CWM installed. I downloaded the official Asus stock ROM and followed the fastboot instructions above. The official ROM over wrote everything. Took about ... maybe 5 minutes total. The new official ROM worked like a charm.
I then reinstalled TWRP. No issues. I used TWRP to install Cromi-X, which is awesome. Also, no problems.
The only thing I found weird, is that I had cleared all cache etc. and I thought I had deleted all my data by doing so, but everything on my "Internal SD Card" was there even after I installed a fresh copy of Cromi-X.
As for what blob you should use (and I'm STILL A NEWB) I'm pretty sure you need to match the blob to the type of tablet you have. If you go into : Settings --> About Tablet --> Kernel version, (pretty sure that's the right spot) you should see something like "WW_epad" or "US_epad".
Over all, this was one of the most simple "tech" processes I've ever experienced.

ACaton said:
Hey there. Here is my experience with doing what was mentioned in this thread.
I had CWM installed. I downloaded the official Asus stock ROM and followed the fastboot instructions above. The official ROM over wrote everything. Took about ... maybe 5 minutes total. The new official ROM worked like a charm.
I then reinstalled TWRP. No issues. I used TWRP to install Cromi-X, which is awesome. Also, no problems.
The only thing I found weird, is that I had cleared all cache etc. and I thought I had deleted all my data by doing so, but everything on my "Internal SD Card" was there even after I installed a fresh copy of Cromi-X.
As for what blob you should use (and I'm STILL A NEWB) I'm pretty sure you need to match the blob to the type of tablet you have. If you go into : Settings --> About Tablet --> Kernel version, (pretty sure that's the right spot) you should see something like "WW_epad" or "US_epad".
Over all, this was one of the most simple "tech" processes I've ever experienced.
Click to expand...
Click to collapse
Thx for the alert, I already have the correct blob for my tablet.
The process work fine and now I have the JB installed on my Tablet!
Thx.