yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Q&A, Help & Troubleshooting] fadelabu:
Thanks for reply. I tried in the past days all the steps suggested in the link you provided, nothing of them solve my USB problem. As I mentioned in my explanation, when I goes to the "Unknown device" properties, in "details" option, "ID Hardware" appears as "USB/UNKNOWN".

I tried with "ZADIG" from "Heimdall" plugin the phone in download mode and the result is the same, appear as "Unknown device", and vendor or product appears as 000... I really think my phone USB is broken.

It´s possible to do anything in CWM mode directly? Thanks for support.
[Galaxy S I9000 Q&A, Help & Troubleshooting] xsenman:
Yes , you can flash ROMs, using CWM, just copy ICS or JellyBean ROMS to your external SD card, via SD card adapter direct to PC, and flash using CWM

Check this out! You , YES! you are an " Android ". Not your phone but U.

You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone

How to say Thank you? If you find any post helpful on XDA, click on their Thanks button

If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.​
[Galaxy S I9000 Q&A, Help & Troubleshooting] fadelabu:
8. After this I switched on the phone but the start menu remained with the Semaphore logo. I only have access to the CWM Recovery mode, I’ve been trying all the possibilities and options in the menu, putting the files in the external or internal memory, using different wipes… and reading a lot of forums but until now it’s been impossible to solve this issue.

This is the error message:

“Installing update...

E:Error in /sdcard/update.zip (status 0)

Installation aborted”

9. I’ve tried to install Update.zip and the ROMs but without succeeding. I’ve read different posts in XDA referred to “Status 0” topic but every solution proposed requires computer connection.

Any idea? Thanks one more time for your support.
[Galaxy S I9000 Q&A, Help & Troubleshooting] xsenman:
[26] Problem:- ClockworkMod Recovery giving Status 0 error "Installation aborted".

Quote:

Solution:- Most likely you have a incompatible CWM, or your Zip files are corrupted or you have mounted /system or /data

Most of this answers are all found in the Links below, on every post I make.

Anyway just flash the ICS semaphore kernel in zip format available here , afetr flashing do not reboot but power down and enter CWM using combo keys and flash a Jelly Bean ROM using CWM Recovery

Check this out! You , YES! you are an " Android ". Not your phone but U.

You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone

How to say Thank you? If you find any post helpful on XDA, click on their Thanks button

If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.​
[Galaxy S I9000 Q&A, Help & Troubleshooting] fadelabu:
SOLVED

After following the simple steps that you indicated I have a phone again. Thanks for your explanation, patient and time.
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] Barok:
Pls i lost this installer while flasing my rom. i need it to restore my SMS.
[Asus  Eee Pad Transformer Prime] rayman:
The AndroidRoot.Mobi Team is proud to present Flatline: Nvflash for TF201 Jellybean!

This release allows generating nvflash blobs for your specific device, making your device unbrickable as long as you have a copy of the blobs.

As a brand new feature, it will also enable wifi and upload a copy of the blob to androidroot's server. Later, a solution will be released to retrieve the blobs from the server if you ever loose them.

https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/

Credit goes to the AndroidRoot.Mobi team:

Bumble-Bee (Apache14), IEF, kmdm, lilstevie & RaYmAn.
[Asus  Eee Pad Transformer Prime] joshkun:
Great job

Thanks for your efforts. This is great. We waited for this so long. :good:
[Asus  Eee Pad Transformer Prime] ricardo1976:
Anyone tried this?

I have a tf201 with jellybean .18 update. Brick Chances??
[Asus  Eee Pad Transformer Prime] beckzz:
so anybody already tried that?

i'm runnin Voyager2k's PA-Builds with 4.1.1 bootloader ...so if anybody could report if it's working...

unfortunately u never managed to create my blobs with nvflash - switched to JB to fast... :p

Grz
[Asus  Eee Pad Transformer Prime] Namidairo:
Check what bootloader you are on in the bootloader menu you get when you hold down Vol-Down on boot.

10.4.2.15 is what you are looking for.

Anything else and you'll probably have issues :)

Naturally, if you are running Voyager2k's PA builds or my CM 10.1/2 builds, it *should* work.

As for Hairybean, 1.51 should be fine, 2.2/2.3 will need you to downgrade first.
[Asus  Eee Pad Transformer Prime] nestortoledo:
Hi nice work guys

I have TF201 Bootloader version: 10.4.2.18

Will this work for me or only work with 10.4.2.15?
[Asus  Eee Pad Transformer Prime] riven67:
Wow this is awesome! My boot loader is 10.4.2.15_20120917 I think that is the right one, the date is not mentioned in the instructions can anyone confirm this is the right one?

Does it matter what ROM you are running? I am on Voyager2k's PA399 4.3 RC2 ROM with OC'd kernel.

I am so happy you guys did not forget about us poor jellybeaners! Lol thanks for all the hard work.
[Asus  Eee Pad Transformer Prime] prana22:
Ugh. I need help please

So I was to the step where I was flashing the AndroidRoot BL and I got an error. ERROR: DO NOT REBOOT check /tmp/AndroidRoot/ptpatcher_patch.log. Seek support on IRC #asustransformer on freenode IRC. I tried the IRC chat but didn't see anyone. I believe I may have been on the wrong boot loader but I'm not sure. Any help would be greatly appreciated.

*edit* I was able to get some more info by doing adb shell:

/tmp/AndroidRoot # ls -l

ls -l

-rw-rw-rw- 1 root root 195 Sep 25 03:17 pt_patch.log

/tmp/AndroidRoot # cat pt*

cat pt*

LOG: ptpatcher

LOG: ---------

LOG: start patching...

LOG: reading pt...

LOG: failed to open file

LOG: done

LOG: verifying pt...

LOG: invalid PT image

LOG: error in callback 0

LOG: failed!

/tmp/AndroidRoot #
[Asus  Eee Pad Transformer Prime] jynlude:
I got to the part where you run the wheelie --blob blob.bin command, but am getting this: Error 3 receiving response from command

I'm pretty sure I'm successfully in APX mode and have reinstalled the universal naked drivers after the first time booting into apx. My initial problem was that it was unable to detect APX mode, but after a reinstall of the drivers, it seemed to have fixed that problem.

Anyone else seeing error 3 and have a resolution?

I'm on 10.4.2.18
[Asus  Eee Pad Transformer Prime] Makrilli:
Maybe it's becaude wrong bootloader?
[Asus  Eee Pad Transformer Prime] DirtyWizard:
According to this post : http://xdaforums.com/showpost.php?p=45902481&postcount=2 that bootloader should also work..
[Asus  Eee Pad Transformer Prime] flumpster:
I have just tested using the TF300 files on the Hairybean 2.31 bootloader and everything is working ok.

I don't want to post in here instructions as it might confuse people who are on the stock bootloader so I will put them in my thread later.
[Asus  Eee Pad Transformer Prime] rchristy:
Thanks for the well done job. My TF201 was on 10.4.2.18. After successfully applied the steps, the BL changed to 10.4.2.15.

Now the question is how can I change back to TWRP? Fastboot didn't overwrite the Flatline recovery.
[Asus  Eee Pad Transformer Prime] GappaX:
I had the same bootloader as you, got downgraded to .15.

Well, I just flashed back TWRP (had 2.5.0.0 before, now 2.6.3.0), no problems - so it should work.

Used this:

fastboot -i 0x0b05 flash recovery openrecovery-twrp-2.6.3.0-tf201-JB.blob
[Asus  Eee Pad Transformer Prime] jynlude:
:( any thoughts on what i did wrong?:

1. reboot into apx mode by powering up while holding volume up

2. tab would vibrate and a blank screen would be there, i'd release the power and volume up buttons

3. run wheelie --blob blob.bin

4. at first, the tablet would show to be unrecognized per adb "waiting for apx mode", so i reinstalled the naked drivers

5. run wheelie --blob blob.bin

6. received the error message pasted below:

Waiting for device in APX mode...

[=] Chip UID: 0x15c7d7a4b20060c

[=] RCM Version: 0x30001

[-] Error 3 receiving response from command

some further info is that i'm on the stock 4.1.1 bootloader (for now), rooted and unlocked, twrp 2.6

maybe i should re-create my blob.bin file?
[Asus  Eee Pad Transformer Prime] prana22:
I was on that bootloader and now I'm stuck. I can boot to the Flatline CWM but nothing will mount. Fastboot and ADB still work. Is there anything I can do to recover this?
[Asus  Eee Pad Transformer Prime] flumpster:
Did you use the prime version of the files when you was still on the tf300 kernel? That would probably do what you describe and he lists what bootloader you should be on for prime.

In my thread i have instructions for what to do if on the tf300 Bootloader so it sounds like you didn't follow either.
[Asus  Eee Pad Transformer Prime] prana22:
I get that I screwed up. I've already got a reminder in a bricked tf201. But hey, thanks for the response.
[Asus  Eee Pad Transformer Prime] flumpster:
That isn't what I asked but i am guessing by your reply that that is what you did.

Try one of the methods in the following post to try to get back a working recovery.

http://xdaforums.com/showpost.php?p=40149294&postcount=8
[Asus  Eee Pad Transformer Prime] prana22:
Sorry. I'm just pissed that I missed that I was on the wrong bootloader. Totally my fault and I own it. Thanks. It seems that I no longer can boot into the bootloader three icon menu anymore. So now it just boots to the flatline CWM. So now fastboot won't work. Only adb.
[Asus  Eee Pad Transformer Prime] flumpster:
Can you still boot into the os?

If not try going into flatline cwm and doing adb reboot bootloader.

If this lets you into the bootloader try flashing the recovery in the link I gave you in fastboot. If that doesn't work see if the OS icon in bootloader will let you back into android and try the second method.
[Asus  Eee Pad Transformer Prime] prana22:
'adb reboot bootloader' got me back to the 3 icon screen. I did try the twrp.blob and it says that it says sending 'recovery' and writing 'recovery' and it finishes. But when I reboot it still just loads the Flatline CWM.

BUT we're getting somewhere! I was able to boot into Android and tried the second method. When I reboot, it unfortunately goes back to the Flatline CWM. I have tried it a few times and consistently boot the tablet to the OS. The only catch is I have to do the adb reboot bootloader and then select the Android icon. All other situations it seems to just boot to the FlatLine CWM.
[Asus  Eee Pad Transformer Prime] flumpster:
The second method is probably your best bet and I can't see why it wouldn't work.

After you run the commands in terminal emulator from market did you restart or power off normally without selecting recovery from the shutdown menu?

You need to not select recovery from shutdown menu.

---------- Post added at 06:11 AM ---------- Previous post was at 06:02 AM ----------

I have to take my daughter to school soon but if what I typed above doesn't work try following the instructions for brick 1a in the following link to see if you can get out of that cwm loop.

http://xdaforums.com/showthread.php?t=1514088
[Asus  Eee Pad Transformer Prime] prana22:
Yes, i tried both just selecting restart and tried it a second time powering it off and then hitting the power to turn it on again. Do the permissions on the twrp.blob have to be a certain way? Currently they are [rw rw r].
[Asus  Eee Pad Transformer Prime] flumpster:
Permissions shouldn't matter but it needs to be on the root of the internal sdcard and not the microsd card.
[Asus  Eee Pad Transformer Prime] prana22:
Yeah, it is. I don't even have a micro SD in. When I run it has:

15932+1 records in

15932+1 records out

8157288 bytes transferred in 6.023 secs[/QUOTE]

I think it is mapping /sdcard to /storage/emulated/legacy. Could that be the problem?
[Asus  Eee Pad Transformer Prime] flumpster:
It has been so long since I wrote and tested them instructions but it looks like the correct byte size of the TWRP so it is probably finding it just fine on the /sdcard.
[Asus  Eee Pad Transformer Prime] prana22:
You read my mind... I just tried that and it worked! Thank you for all your help. I seriously thought I was bricked.

The one thing I have left to figure out is installing twrp. I can't seem to get the FlatLine CWM off. I just tried doing the fastboot method with the .img file and it acts like is working but it still boots into Flatline CWM when I reboot.
[Asus  Eee Pad Transformer Prime] flumpster:
So what do you have now ? You now have it booting into android if you just power it on, can get into bootloader by holding volume down and power but when you go to recovery it is still flatline cwm ?
[Asus  Eee Pad Transformer Prime] prana22:
That is correct. I can't get a new recovery on it.
[Asus  Eee Pad Transformer Prime] flumpster:
Take a look at the instructions and the files at the end of the HairyBean thread and try following that and see if the correct recovery to do the nvflash process will flash for your bootloader. It will look exactly the same as the one you have now but you shouldn't have the mounting problem if successful.
[Asus  Eee Pad Transformer Prime] prana22:
Will do. I really appreciate your help. I kicked you a donation. I know it isn't much, but again thanks for your help. I thought it was bricked.

Quick questions. Am I using the TF300 flatline recovery file because I am on the TF300 bootloader?
[Asus  Eee Pad Transformer Prime] Thomasba:
Clearly I'm being thick and doing something wrong. I've followed Flumpsters thread and installed the naked drivers. I opened the command window and typed in the first line of code and all I get is "waiting for device"

When I'm in Windows 7 (64) Device manager shows "Android Device" with "Asus Transformer Prime ADB interface" below it further down the tree is "Portable Devices" and beneath that is Transformer Prime TF201 and there are no exclamation marks alongside either of them.

When I'm in bootloader I just have "Android Device" with "Asus Fastboot Interface" below it.

Ideas anyone?
[Asus  Eee Pad Transformer Prime] flumpster:
Yes you are. The mounts changed between the 4.1 and the 4.2 bootloaders (as you already know) and the TF300 flatline recovery works with hairybean 2.31's bootloader.
[Asus  Eee Pad Transformer Prime] Diodato:
Flatline backup/restore and external SD

First of all very big thanx for giving us, people with JB, the nvflash access possibility.

I'm a newbie trying to play with first roms, so wanted to backup the current state for eventual future recovery. And I wanted to backup to an external SD.

Does the flatline recovery support an external SD? At first I thought that maybe because I didn't mount the external card my first backup went to the internal flash without asking for destination, but then under the "mount" option I get no item for mounting an external SD.
[Asus  Eee Pad Transformer Prime] jynlude:
just wanted to bump this up to see if anyone has encountered this issue or has any advice? i'm too scared to flash androwook with the 7 or so files that i was able to successfully get with this process. Unsure if the following files are critical enough to get me comfortable in case I brick:

nvflash --resume --rawdeviceread 0 2944 bricksafe.img

nvflash --resume --read 14 factory-config.img

nvflash --resume --read 7 unlock-token.img
[Asus  Eee Pad Transformer Prime] prana22:
I was able to go through and do the entire process. I have the files I need to have the nvflash backup. And yet... I still cannot get it to flash a new recovery. Still the same issue where it won't mount the sdcard. I've tried doing with fastboot with a .img. Any ideas?
[Asus  Eee Pad Transformer Prime] riven67:
I'm no dev and I do not have any technical fixes to try but have you tried a different sd-card? I had one crap out on me because it was accidentally ejected while the tab was going to sleep, that card was useless from then on I even tried to format it in windows using 3 different partitioners and no dice. I got a new one and all was well again. So maybe it is the little thing this time. :confused:
[Asus  Eee Pad Transformer Prime] flumpster:
Are you saying that you can now access wheelie?

I'm in bed at the moment but if you can access wheelie I will give you an sos file and some instructions later to try and flash in there.

Let me know.
[Asus  Eee Pad Transformer Prime] wwjoshdew:
I've gotten SO MANY FREAKING COMMENTS, Tweets, and Messages from people asking "What if my Prime CAME WITH Jelly Bean". Now I can update my TF201 NVFlash video with links to this XDA Thread! Thanks [MENTION=962182]rayman[/MENTION]!!

http://www.youtube.com/watch?v=J3ypzUaKxvo
[Asus  Eee Pad Transformer Prime] prana22:
Yes I can access wheelie. No rush. Any time you can get to it. I'm hitting the sack.
[Asus  Eee Pad Transformer Prime] flumpster:
Attached is blob.zip.

Download it and extract it in the /nvflash folder that you created on your hard disk.

Hold down shift and right click on the folder and select "Open command window here".

Place yourself into APX mode by holding Volume Up and Power.

Run the following commands.

wheelie.exe --blob blob.bin
nvflash.exe -r --download 5 blob.SOS

Once finished restart the prime and see if anything has changed.
[Asus  Eee Pad Transformer Prime] rayman:
Make sure you are using Flatline *and* the most recent version of wheelie.

If you are using pre-JB blobs, you need to use the old wheelie. - nvidia unfortunately changes the protocol a lot so it has to match up to work.

I would try regenerating blobs and making sure you use the right versions.
[Asus  Eee Pad Transformer Prime] prana22:
I wasn't using an external sd card.

---------- Post added at 08:44 AM ---------- Previous post was at 08:42 AM ----------

Flumpster, you rock. That worked like a charm and I'm back to normal.
[Asus  Eee Pad Transformer Prime] flumpster:
Phew.. Glad it's sorted and thanks for the donation mate.

Try to chill in future when things go wrong. If it had been hard bricked there is nothing you could have done about it anyway and stressing about things you cannot change is a waste of energy (I am an old fart now tho and took me years to realize this). ;)
[Asus  Eee Pad Transformer Prime] InMyBedNow:
nvflash --resume --go

The above command does not work for me, but every other step worked fine. Can i just reboot by long pressing the power? Please respond quickly. Thanks!

EDIT: So I just held power for ~15 seconds and the tablet rebooted normally with no errors, so I'm guessing I'm fine, but I would still like someone to confirm please :). I also received all the NVFLASH blobs and .img files.
[Asus  Eee Pad Transformer Prime] Diodato:
I'm in trouble. Originally had JB (10.4.2.18) got nvflash access and saved all the important blobs as well as the backup made under the flatline recovery. Played around with Cyanogenmod 10.2 Unofficial but wanted to go back. I have learned the hard way of the changes of Android from 10.1 to 10.2 so a simple restore wasn't the way. I guess the only way was to reflash all the partitions. As usual it was late night and the first flash went wrong. After the reboot I lost access to everything, even nvflash. Right now wheelie just wait indefinitely.

E:\>wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================

Waiting for device in APX mode...
[=] Chip UID: 0x15c7d7a444c2411
[=] RCM Version: 0x30001

[=] CPU Model: Tegra 3
[+] Sending bootloader...
Sending file: 100 %

A user had a similar situation (http://xdaforums.com/showpost.php?p=32421009&postcount=514) and was able to get back nvflash access using wheelie 0.2 (http://xdaforums.com/showpost.php?p=32365961&postcount=489). So under Linux I tried the same and got:

$ sudo ./wheelie -r --blob blob.bin
Wheelie 0.2 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x15c7d7a444c2411
[=] RCM Version: 0x30001

[-] Error 3 receiving response from command
$

instead of:

[+] Sending BCT
Sending file: 100 %
[+] Sending ODMData 0x5
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash

I guess I need an updated wheelie 0.2 ...

Any help to regain nvflashh access would be appreciated.
[Asus  Eee Pad Transformer Prime] joshkun:
Try to use Flumbster's drivers there is one called "android-winusb2" stead of the naked ones and after installing try it if still no go.

Try pulling the usb out and reconnecting then try again I hope this will help this worked for me. :o
[Asus  Eee Pad Transformer Prime] Thomasba:
Thanks for that, i did after god knows how many attempts manage to get them on and I'm now all blobbed out :)
[Asus  Eee Pad Transformer Prime] joshkun:
Glad to her that :D
[Asus  Eee Pad Transformer Prime] Restorer:
ROTFL. I'll tell you what, I'm pretty blobbed out myself just trying to follow this thread - is there nothing that is straightforward about this damned tablet :D?

I see that most of the questions and answers in this thread relate specifically to flumpster's particular bootloader/ROM combination and I have been trying to find answers to my questions but still can't see any definitive ones.

1. Will Flatline work OK with a newly unlocked device still sporting stock 10.4.2.18 bootloader version, stock recovery and latest

stock

ROM (rooted using motochopper method)?

2. Has anyone actually done this yet?

3. All the posts here seem to relate to custom ROMs (not just HairyBean). Also is it advisable to replace the stock recovery with TWRP before starting the process?

I have picked up that the bootloader will be changed back to the 10.4.2.15 version and leaves behind the method's own CWM recovery but people seem to be encountering problems after that? Have people successfully flashed the latest TWRP after the process completes and then updated bootloader back to 10.4.2.18? Or maybe there is no conflict between the bootloader flashed by Flatliner and the 10.4.2.18 stock ROM?

Any advice as always would be much appreciated.
[Asus  Eee Pad Transformer Prime] flumpster:
1. Yes

2. Probably

3. No need to.
[Asus  Eee Pad Transformer Prime] Restorer:
Thanks for the fast reply!

The "probably" is what worries me and hence my question :laugh:. The last thing I want to be with all this flashing of bootloaders on the Prime is a pioneer :D ! It almost looks to me like the cure is worse than the disease :D.

Sorry, flumpster, I should have made my last question in that post number 4.

4. I have picked up that the bootloader will be changed back to the 10.4.2.15 version and leaves behind the method's own CWM recovery but people seem to be encountering problems after that? Have people successfully flashed the latest TWRP after the process completes and then updated bootloader back to 10.4.2.18? Or maybe there is no conflict between the bootloader flashed by Flatliner and the 10.4.2.18 stock ROM?

The idea of having a even a Mobi.root modified CWM recovery on there for long worries me after all the dire warnings we've had only ever to use TWRP on JB :laugh:
[Asus  Eee Pad Transformer Prime] flumpster:
4. After finishing the process and you have all your backups stored in triplicate then flash the "Downgrade Hairybean 4.1.1 Bootloader & Recovery.zip" from post 2 of the Hairybead thread and it will take you back to the proper bootloader and a compatible TWRP.