yashsingh1/xdaforums huggingface dataset:
[Asus  Eee Pad Transformer Prime] mrw1215:
Yeah, people have been recommending ditching CWM for TWRP to me for a little while, now, and I continued sticking with it because I was so familiar with it and didn't want to bother with anything else. Didn't know there was a problem with the current version for the Prime. But yeah, I think I'm definitely going to make the jump to TWRP if/ when I get my Prime back up and running.

The biggest issue for me is, I'm not very familiar with actually using ADB/ command prompts for any of this stuff. Every device I've unlocked/ rooted, I used an automated script to do it, so I didn't have to bother with any of that. I also did read over the stuff about nvflash, but I couldn't really make heads or tails out of the instructions, so I thought it'd be best for me to not tamper with it. Figured I was playing safe with my Prime, so I wasn't concerned, anyway.

I believe I can still access fastboot on my Prime (I don't technically know what "fastboot" is or does, though); if I power it on holding down the power and volume down buttons, I get three options (wipe data, fastboot USB mode, and reboot), but I haven't tried connecting it to a computer yet. I'll take a look at your link.
[Asus  Eee Pad Transformer Prime] mrw1215:
Hm. So from what I gather, I need to get a new blob file; the one in the link you provided talks about getting it from the Virtuous Prime ROM, but the reason this concerns me is, VP seems like a stock ROM, and the unbricking thread notes that if you apply a stock blob file after installing CWM, you get an unrecoverable brick. So... not sure if I should use the Virtuous Prime blob file, or what? I don't want to permanently break my Transformer Prime. :/
[Asus  Eee Pad Transformer Prime] Striatum_bdr:
Gosh.... Stock blob = Asus blob downloaded from Support Center...

Just follow the instructions.
[Asus  Eee Pad Transformer Prime] mrw1215:
Oh, okay, so the VP blob isn't "stock" then? I guess I'll give it a whirl then. Probably tomorrow, though, as I don't have much time today.
[Asus  Eee Pad Transformer Prime] mrw1215:
I'm not so sure I've set up fastboot on my computer correctly... I followed some instructions on a random site I googled, but I don't know if it worked. I put my Prime in fastboot mode, and when I connected it to my computer, Windows found and downloaded a "Fastboot" driver. But when I opened a command prompt and entered "fastboot devices", nothing happened.
[Asus  Eee Pad Transformer Prime] qery:
Ok you sould use Universal Naked Drivers from developer forums.

VP is based on stock rom, but it is made for unlocked devices, so it does not hardbrick you (I think it doesn't flash bootloader).

You need to have files Android Platform Tools (from Android SDK) installed (or copied in folder). To this folder you copy files needed to be flashed (mine is c:\program files (x86)\android\android-sdk\platform-tools\). Then you open cmd from there (in explorer press Shift+Right click and select Open command window here).

Now reboot tablet while holding VolDown and select Fastboot (usb icon). Next connect to pc.

After that you should be able to use fastboot commands.
[Asus  Eee Pad Transformer Prime] mrw1215:
Okay, thanks everyone, looks like I'm back up and running!

Just a question; am I reading it right that with the newest version of TWRP, you can't do backups and restores without having done that nvflash thing?
[Asus  Eee Pad Transformer Prime] mrw1215:
Hm. This is probably unrelated, but... I'm not sure TWRP is working correctly. I installed it via GooManager after I got back up and running (I had tried to flash it via fastboot when unbricking, but for some reason, it didn't take, and I was still on CWM). Anyway, in TWRP, when I do my wipes, it doesn't appear to actually have any effect, even though it goes through the process and says they were successful. Also, when I try to install a ROM, the zips don't appear on the sdcard folder in TWRP, even though they are, in fact, on there.

Putting them on an external card allows TWRP to see them and flash them, but because TWRP apparently isn't actually doing the wipes (even though it says it is), I'm having trouble flashing other ROMs (because I'm basically "dirty flashing" from Virtuous). In particular, I'm trying to flash Blackbean; after the boot animation, it goes through the "Android is upgrading" thing for what I assume is still the Virtuous Prime stuff, then I get an error about system.media (something like that) not responding, and then it quickly goes back to the boot animation and continues to loop from the aforementioned error to the boot animation over and over until I force turn the tablet off.

Anyone know what the heck is going on? Why does it seem like TWRP isn't actually wiping the tablet, and why is it not recognizing the zips in the internal sdcard folder?
[Asus  Eee Pad Transformer Prime] qery:
Yes. If you don't want nvflash, use older version - in OP it says that 2.2.1+ needs nvflash bootloader.

Try using older version of TWRP.
[Asus  Eee Pad Transformer Prime] Striatum_bdr:
And in case of problems, report in twrp thread with a logcat.
[T-Mobile LG G2x] redishbrown:
Is there an apk of dsp manager that's for stock gingerbread?
[T-Mobile LG G2x] nycelitemaster:
Yes you can use but it might crash.

Sent via G2X-SINGH-UI
[T-Mobile LG G2x] hardy272:
Yes

i have the dspmanager in stock 2.3.3 V21E installed, i pushed on /system/app/ , but if you want ,can install normally , volume+ is a good option too :)

(sorry for my bad english i am from Nicaragua n.n/ )
[T-Mobile LG G2x] kesara:
Here you go . Works on 2.3.4

http://db.tt/17cKox5Z
[Eee Pad Transformer Q&A, Help & Troubleshooting] apols:
used "Asus Transformer Recovery Boot -MoDaCo", won't boot normally without cold boot

I used this crap app from the play store called "Asus Transformer Recovery Boot - MoDaCo" when I was having trouble rebooting into recovery a few months ago. It's an app that forces the next boot to go straight to recovery. Unfortunately, it breaks it and now every boot goes straight to recovery unless I intercept it and do a cold boot.

I've tried uninstalling the app, i've wiped my rom multiple times (wiping everything). I'm on an older version of CWM. I tried using goo manager to install the latest version of TWP, but it has to reboot to do it, and as soon as it does, it goes straight into CWM.

Is there a flashable zip I can use to restore the bootloader in this situation?

Link to app: https://play.google.com/store/apps/...S5tb2RhY28udHJhbnNmb3JtZXJyZWNvdmVyeWJvb3QiXQ..
[Eee Pad Transformer Q&A, Help & Troubleshooting] itj1228:
First cold boot into android, hold power and volume down, then allow the tablet to cold boot.

Now you should be inside android. Open terminal emulator and type

Su enter then type

echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0

NOTE=the 0 are zeros

This will fix the immediate issue. This will remove the boot flag causing the tablet to go into recovery. Unfortunately this will not allow you to boot into recovery normally, only by cold boot then press up to enter recovery.

To fix this issue, personally i flashed Team Win recovery 2.2 i think it is in XDA. Awesome touch recovery!

You will have to download the new recovery, boot into recovery by holding power and volume down, then press volume up when prompted.

flash the new recovery. This will remove the boot Flag fix and it'll only boot into recovery so you'll have to use power and volume trick again.

once in android, run terminal emulator again and insert that command above. Reboot the tablet and you will see the progress bar under the eee pad splash screen. This will update your recovery at that time. Let it reboot.

Now the tablet should be fixed and reboot, and reboot into recovery should work as expected.

Understand i'm not responsible if you break your tablet..Proceed with caution.

This is what i did on my b90 tablet.

Hope this helps. It only took me about 13 hours to figure this out.
[Eee Pad Transformer Q&A, Help & Troubleshooting] apols:
You're the man, will try this when I'm back home tomorrow.
[Galaxy S II Android Development] maddoguk:
Nice work.
[Galaxy S II Android Development] Smoky:
Great job :thumbup:

So it will replace the wipe options in CWM. ;)

Envoyé depuis mon GT-I9100 avec Tapatalk
[Galaxy S II Android Development] GoJo ^^:
If i go back to a 4.0.3 stock firmware, no brick risk then, right?
[Galaxy S II Android Development] Phil3759:
No brick risks on the i9100 with official 4.0.3 fw
[Galaxy S II Android Development] shoey63:
These files also work on Note N7000:good: If using on CWM in preparation for installing new ZIP Rom "unmounted" partitions need to be "remounted" (mounts and storage). As per Phil3759's initial warnings. (For Note users - don't know about GSII users)
[Galaxy S II Android Development] shoey63:
I know u don't own a Note Phil, but any idea what's going on with this guy? http://xdaforums.com/showpost.php?p=31307524&postcount=1. (BTW, ur wiping scripts are pretty much instantaneous in stock 3e ICS recovery).
[Galaxy S II Android Development] Phil3759:
I planned to add a pause so users can change their mind and unplug battery before the wipe. A bit out of time now. Busy on the PhilZ-cwm6 kernel

But, if I remind this thread or someone post again later, I could add it

Will be looking at your link
[Galaxy S II Android Development] Phil3759:
Sorry, seems software or specific hardware issue

Never experienced this, and many note users too

Nothing to do with superbrick in my opinion
[Galaxy S II Android Development] rodirodi:
Very nice idea and good work!

Tested on I9100. No problem.

Thank you!
[Galaxy S II Android Development] kenshinjar:
Hi Phil3759,

can I use this for Note GT-N7000, which official Rom or custom Rom?

waiting for your reply. thanks
[Galaxy S II Android Development] Phil3759:
Yes, it will be safe on the note, no format commands issued
[Galaxy S II Android Development] Entropy512:
delete_recursive can leave the filesystem in an unclean state. Using this workaround is not advisable.

It is better to use an update-binary that has been rendered safe by building with BOARD_SUPPRESS_EMMC_WIPE.

Run this to check an update-binary for safety:

strings update-binary |grep MMC

It should return:

warning: %s: Wipe via secure discard suppressed due to bug in EMMC firmware

Any update-binary versions that have that string are safe to use.
[Galaxy S II Android Development] Phil3759:
Thank you a lot for the input.

However, Chainfire just answered me in his CF-Root for the n7000 that using format commands in update.zip could still brick an unsafe kernel whatever recovery (patched or non patched) it uses. Now, you say that a patched binary in update.zip will make it safe what ever kernel/recovery combo it is

If you confirm it, I will update my post. CF disagree the use of format commands in update.zip (yes, I know, if there are FS errors, they will not be fixed without format)
[Galaxy S II Android Development] shoey63:
Good news Phil! Ran Entropys command on Temp CWM Touch 6.0.12 update-binary and got this "ubuntu@ubuntu:~/Desktop/binary$ strings update-binary |grep MMC

warning: %s: Wipe via secure discard suppressed due to bug in EMMC firmware

EMMC

EMMC:" Unfortunately doesn't produce same result in update-binary for ur wiping script. So simply swap update binary, change "delete-recursive" to "format", re-sign file and job done right? (That's assuming u trust Entropy, and who doesn't?)
[Galaxy S II Android Development] Phil3759:
Update 08.10.2012:
[Galaxy S II Android Development] shoey63:
Well it's one thing to contribute theoretical information, but it's another to actually go ahead and do it! I hope Entropy is right, I'm about to use script to do factory reset based on his assertion that "format" commands in zips with update binarys that contain "secure discard supressed" are safe.:fingers-crossed:

---------- Post added at 07:54 PM ---------- Previous post was at 07:10 PM ----------

Entropy's right! No problems whatsoever :victory: Flashed factory reset, format commands and all. and the patched update-binary prevented my Note from bricking! It only took seconds:good: (Man.... that was a wild ride):cyclops:
[Galaxy S II Android Development] albertorodast2007:
There's no updated binaries zip file for wiping dalvik right?
[Galaxy S II Android Development] shoey63:
Looks like PhilZ forgot. Im sure he will get around to it. The old one is safe too. Just wont work if there is file corruption.
[Galaxy S II Android Development] mayekk:
nice and simple, great work !
[Galaxy S II Android Development] Phil3759:
Wiping dalvik should be safe as there is no dalvik partition, so no format commands issued

Factory reset is wipe data (so dalvik too)
[Galaxy S II Android Development] shoey63:
Glad you cleared that up. So factory reset does all "3 wipes" Data/cache & therefore Dalvik as well.:cool:
[Galaxy S II Android Development] crixalis:
I have a question. I flash with odin stock 4.0.4 then again with odin speedmode (safe kernel from description). Its safe for me to wipe data from CWM or from rom (factory reset) ?

Thanks
[Galaxy S II Android Development] Phil3759:
Did not get your question!
[Galaxy S II Android Development] crixalis:
With stock kernel 4.0.4 and speedmode kernel its safe to wipe data from recovery? Its chance to brick my phone ?

Sorry for my english
[Galaxy S II Android Development] Phil3759:
Wipe from stock recovery is safe. Speedmod i do not know
[Galaxy S II Android Development] shoey63:
Useing Philz wiping scripts or kernels wont brick your phone. If u want to know if Speedmod recovery is safe to wipe from directly, maybe u should enquire on that forum.

---------- Post added at 05:42 PM ---------- Previous post was at 05:39 PM ----------

....if Philz wiping scripts or temp recovery are used:)
[Galaxy S II Android Development] crixalis:
Thanks for replay
[Galaxy S II Android Development] shoey63:
No problem:thumbup:
[Galaxy S II Android Development] albertorodast2007:
Isn't too much to ask for scripts for us using dual boot? ;)
[Galaxy S II Android Development] Phil3759:
If you are on dual boot, then you are on custom kernel. Custom kernel should be all safe or ditched by users. Why would you need such a script?
[Galaxy S II Android Development] albertorodast2007:
Yeah, dumb question. :laugh: I'm just being paranoid.
[Galaxy S II Android Development] Dexter_prog:
Is anyone actually using these scripts? I wonder why this thread has so few replies
[Galaxy S II Android Development] Phil3759:
did you read the 32 posts above?
[Galaxy S II Android Development] Dexter_prog:
yeah, but being this the solution to the brick-bug thingy I assumed it would get more replies and overall interest.
[Galaxy S II Android Development] Phil3759:
Most are on fixed kernels now...

If you do not see the need of it, do not bother...

Take it as a learn code thread
[Galaxy S II Android Development] shoey63:
Every now and then someone on stock ICS wants to do a wipe

But doesn't want to use custom kernel or even temp CWM. And unless they are prepared to do factory reset from stock recovery, this is they only way.
[Galaxy S II Android Development] MontAlbert:
Sorry, new to sgsii stuff..my mate wants me to update his phone so am reading now...if he is on a rooted stock ICS do I need this? Or is the easy fix just to flash a new cfroot kernel in Odin first and then all will be good?

When flashing a new rom how does this bug work? If he already has cwm on there can I just flash a new rom and kernel in cwm after wiping? Or should I flash these files first just in case?

Thanks
[Galaxy S II Android Development] shoey63:
Go here http://xdaforums.com/showthread.php?t=1877270

Read OP and flash appropriate kernel. Cf-root is not 100% safe but Philz kernels are. After that you can wipe and flash without bricking, so no need for these scripts.

---------- Post added at 09:18 PM ---------- Previous post was at 09:04 PM ----------

@Phil3759. Just noticed you have unleashed new 2.0 recovery for GSII.:beer: Does this mean you have reworked touch code already!?
[Galaxy S II Android Development] Phil3759:
No, I am now on build 2.20 (internal)

On the i9100, the issue is present too, but not at default settings

By the way, I debugged it now:

- main cause is my "highlight on first touch function": selects menu on first touch and validates on finger lifted

- if I use easier implementation of "highlight on finger lifted", this will be fixed quickly (Koush Touch uses this way of highlight/validate on finger lifted)

If you scroll too fast, at end or start of scroll, your finger curves on the screen and even eventually touches it with or near your nail. If you try it slowly, you can see in that case that despite you scroll from top to bottom, at the end of movement your finger touches a previous position before it is lifted. This abuses my code checks.

The easiest solution is to put finger on screen, slide down maintaining same surface (not curving finger too much), and lift finger without curving it too much. That way, you get a very clean scroll that can be fast

Hope you get what I mean.

I like the highlight on first touch implementation unique to my code, so I am trying to fix the code using more robust one

If it ends up too hard to fix or not perfect, I would revert, or offer option, to use "easy scrolling mode" which toggles this highlight on first touch part and reverts to a select on finger lifted code. That way, scrolling will not cause too much issues even if you abuse with this fast scrolling

Fact is that cwm code is not something like ors file manager or your android apps. The gui is very rudimentary and should stay that way in my opinion as it is a recovery, not an OS

Most people would only care about functions. Few will find a real use of my GUI. I do it for fun and because I hated scrolling in default non touch cwm6
[Galaxy S II Android Development] shoey63:
So no "run Ubuntu from recovery"? in next release;) Hehe... OK will try "non-abusive" scrolling and let you know.
[Galaxy S II Android Development] SilviuMik:
Phil3759 thank u for Samsung_Wipe_Data_System_Cache_2.0-signed.zip is almost perfect for what i need when flashing new roms .

I would like to ask u if u can add an option or tell me how to do it myself to delete internal sdcard too ( not external one ) when using this zip

I know is not needed by some but i would like to start fresh when installing stock rom on my phone .

I tryed to look with terminal emulator at what partition /sdcard is mounted but is different from /data /system /cache

Thank u in advance !
[Galaxy S II Android Development] Phil3759:
Stock recovery already offers to format sdcard, no?

That can also be done within phone

Finally, many think it is much safer to do from PC than within the phone, brick issues wise

Anyway, here's the fstab path

#internal sd
/emmc	vfat	/dev/block/mmcblk0p11

#external sd
/sdcard	vfat	/dev/block/mmcblk1p1
[Galaxy S II Android Development] SilviuMik:
No stock recovery does not offer to delete sdcard :/

And from phone, after rom is installed it already gets populated with lot of crap :D

But thank u for the dev/block i will try to modify the script and let u know if it works or not

No ideea if this line would work :/ google returns no results

format("fat32", "EMMC", "/dev/block/mmcblk0p11", "0")
[Galaxy S II Android Development] Phil3759:
try vfat instead of fat32 instead and let me know
[Galaxy S II Android Development] SilviuMik:
failed to verify whole-file ... seems i can`t modify the zip in windows ( 7zip + notepad++) without breaking compatibility with stock recovery

O well :) thank u anyway ! i will format internal sdcard before rom flash, and after reboot to recovery and apply your script for rest :)
[Galaxy S II Android Development] Phil3759:
I will look at it later, a bit busy now. Not sure about the edify command for sdcard, so do not want to post garbadge
[Galaxy S II Android Development] fulltank:
Worked fine in Galaxy Note ..
[Galaxy S II Android Development] cicciocant:
Does it work in jb stock based rom for n7000?

Inviato dal mio GT-N7000 con Tapatalk 2
[Galaxy S II Android Development] shoey63:
Good question! I will check and report back.

---------- Post added at 07:32 PM ---------- Previous post was at 07:11 PM ----------

I'm back and not bricked:D Yes these files work from stock JB and are safe:thumbup:

---------- Post added at 07:35 PM ---------- Previous post was at 07:32 PM ----------

@Phil3759. You can change title to ICS/JB if you want:)
[Galaxy S II Android Development] Phil3759:
done edit :)

They should work as they rely on mount points and JB still allows us to flash test signed files in recovery
[Galaxy S II Android Development] zachs_xda:
Does this mean CWM will not exist as well after wipe?

Is there an Odin tar / tar.md5 file that would let me flash CWM back and get the phone to boot to CWM at least?
[Galaxy S II Android Development] Phil3759:
CWM is in /boot partition, so not affected
[Galaxy S II Android Development] Serdxx:
this is safe no brick for s2 and galaxy note?

is that this bug happen on SGS3-XXEL5?

hehe..

can i used it too?

just ask
[Galaxy S II Android Development] shoey63:
It is safe and works on all ICS stock kernels for n7000 and i9100. Latest JB stock kernels are problematic. Philz temp recoveries are another option if you want to safely wipe without flashing custom kernel.
[Galaxy S II Android Development] megosu:
Hi,

I need some help,

I tried a Factory reset v2.0 on my GT-I9100 and it is stuck on Formatting /data

It does the same thing from CWM...

Would you know how to format or wipe /data ? My phone is currently stuck in boot loop because I can't clear /data

I'm desperate :/
[Galaxy S II Android Development] Phil3759:
Maybe your /data is broken?

Try flashing a whole new WIPE rom from PC odin (not mobile odin). XXLSJ for example, with the 3 tar files, is wipe

If it fails, try it with pit file
[Galaxy S II Android Development] megosu:
Could it be the brick bug ? I can only go in DL mode or recovery mode now.

I tried to restore I9100BVLPH_I9100TMULPH_I9100BVLPE_HOME.tar.md5 which is what I had before the issue (ICS 4.0.4 from my carrier) but it is still stuck on the animated boot logo.

I don't have any pit file though :/

Would you still recommend trying to get XXLSJ ?

---------- Post added at 08:58 PM ---------- Previous post was at 08:55 PM ----------

if your advice is to try XXLSJ, could you kindly point me to the files ?

thank you

PS: I have spent 2 whole days on this issue, literally...
[Galaxy S II Android Development] shoey63:
Have you wiped using CWM.zip (Not Philz but the one on youtube etc.)on stock recovery at any stage? I ask because you mention CWM and stock recovery has no CWM.
[Galaxy S II Android Development] megosu:
yes... I saw this piece of info too late.... even if I spent a lot of time to prepare everything, it never came up.

I followed CM9.1 wiki installation, at no point they mentioned it, it is sad.

but since I can still enter DL mode, I was hoping maybe it is not the brick bug.

What do you think ?

Can I repartition or something to fix this mess ?
[Galaxy S II Android Development] Phil3759:
Not necessarily LSJ, any wipe rom will do the trick, but I do not recall any 4.0.4 ROM being wipe. Often these are leaks

XXLSJ leak at least is wipe and "probably" brick bug free without risks to flash it

It also comes with a pit as a last resort.

Please confirm pit use in General section before trying it or you will mess your phone

XXLSJ: http://xdaforums.com/showthread.php?t=1994313

edit: if you wiped with an older 5.x cwm, you could have broken your /data. It is not the superbrick bug (phone not dead), but maybe an intermediate agonizing state in that case (sorry for you if it is that). maybe you'd better asking in General section before trying further. There are guides how to try to fix a partially broken partition

Search to find them
[Galaxy S II Android Development] shoey63:
He wiped on bad CWM.zip BEFORE attempting to flash your file Phil. Damage already done. Repartition or ne MOBO is only way out now:mad:
[Galaxy S II Android Development] Phil3759:
Sadly it seems the case. One more victim of the bug

The Moral: flashing is never a 100% safe operation and is 100% a fatal risk operation if people do not read and search