yashsingh1/xdaforums huggingface dataset:
[Captivate Q&A, Help & Troubleshooting] Val D.:
Heh... you formatted the system and shut the phone down? What OS you expect it to load now?

Make sure you have installed correct drivers (read here in this thread). Use Windows 7 PC, if possible. Download one-click back to stock GB with bootloaders (see stickies). Run the file as Administrator and leave it open on the screen. Remove the battery, SIM, SD card (if you have one). Reinstall the battery only, hold both volume keys, plug the phone to PC (see Download mode?). Make sure Odin recognizes the phone (yellow port), and hit Start. Once you have stock GB loaded, don't make anything stupid. Read this Guide how to update it to latest stable JellyBean (CM10.1.3).
[Captivate Q&A, Help & Troubleshooting] insanethomas5:
I tried the above in every way except Win 7, gana install partition now and try it it though.
[Captivate Q&A, Help & Troubleshooting] 4-2ndtwin:
Deleted...
[Captivate Q&A, Help & Troubleshooting] studentofknowledge:
Please help: Stuck in the Recovery mode, cant install update

I've been working on this for HOURS and I dont know whats wrong. My phone is rooted by the way. The steps say:

Download the following

1.[Firmware Download] CM10.2 Android 4.3 JB Firmware.

2. [Google Apps download] Google Apps on your Laptop/PC.

Part Two- (Final Steps of Upgrade for Captivate SGH-I897)

Download the above file into PC and Please don’t extract.

Now copy both firmware and google apps into SD card of your Captivate SGH-I897.

Now turn off your Captivate SGH-I897 .

Now restart your Captivate SGH-I897 in debugging mode (by Using Volume Down Key and Home Key together while switching on use Power button ).

Now it will give a warning, Press Volume Down to enter debugging mode.

When your Captivate SGH-I897 in recovery please select “wipe data factory reset” and “wipe cache partition“.

Then return to the main menu and select “Install Zip from SD card” and choose firmware zip file from SD card.

Now upload the file and apply installation.

When installation get over do same for google apps.

Wait till process complete of google apps.

Now return back to recovery menu and reboot Captivate SGH-I897 now.

Updation process is completed.

I am stuck on the bolded in red part. When I search for the firmware I cannot find it anywhere, I checked every folder I see. I even went back and pasted the link into a folder that was showing up when in recovery but then once in recovery, that folder is empty! I dont know why the files are hidden and I cannot install them.

Please help, anyone...
[Captivate Q&A, Help & Troubleshooting] 4-2ndtwin:
^

Do u currently have a dev'd kernel that includes cwm recovery ? Or do u have stock kernel ? Because u can't install zip files from stock recovery.

There is a Stickied Flashing Guide in this forum if ya need some more info on getting a kernel with cwm recovery.

And Val D. posted a link to his Guide, 3 posts up from urs also.
[Captivate Q&A, Help & Troubleshooting] studentofknowledge:
No, I dont have a cwm recovery, I dont know where to get the one I need so to install it. I guess the steps for installing may be easy to find. Do you think that's why they're not showing up in any of the folders? And can you please help me with the steps I need to go through? Today is the first day I first learned about rooting, recovery mode, kernels, and all of that, so I'm quite new to all of this, I don't want to mess up my phone by doing anything wrong.

Thank you,

B.
[Captivate Q&A, Help & Troubleshooting] 4-2ndtwin:
The Guides that i mentioned before will help u step by step.

Read the Stickied Theads, as they contain very useful and helpful info. This phone is over 3yrs old, so all the info that u need is here, u just have to spend some time reading. And be sure u r confident in what u r doing with ur phone before u flash anything, etc. Just don't want ya to mess up ur phone. :thumbup:
[Captivate Q&A, Help & Troubleshooting] studentofknowledge:
I found out what the issue was. I removed my SD card and instead copied the files into the internal memory and was able to locate them that way. Now when once I start installing the firmware I get this error:

Install /sdcard/external_sd ...

then in red letters: E: Short write of /tmp/sideload/package.zip (No space left on device)

Installation aborted.

Perhaps the firmware is faulty? I had downloaded the most up to date one from here: CyanogenMod Downloads

and now I see there has been a new one added just some hours ago. Should I download it?

Thanks,
[Captivate Q&A, Help & Troubleshooting] 4-2ndtwin:
^

Like i said before, take some time to do a lot of reading. All the info u need is here in this forum. Don't rush into something u r not sure of...u don't wanna make ur phone into a paper weight. :thumbup:
[Captivate Q&A, Help & Troubleshooting] chetansaraf:
... i think i am in deep trouble as my captivate is not being recognized by, i dont know how many PCs :crying:.

whether i connect charger or usb with PC i get 'Pre-Gingerbread Firmware upgrade fail screen' and none of the flashing tools are seeing the phone !!!

tried different PC's, cables and what not but cant get it through. please help ...
[Captivate Q&A, Help & Troubleshooting] 4-2ndtwin:
Have ya tried a Jig to get in Download mode ?

Have ya tried Heimdall yet ? It uses its own driver (not samsung's) that is installed to the one usb port on ur pc that u r connected to when u first use heimdall.

If neither of these work, then the micro usb port of your phone may be bad. Check out mobiletechvideos.com for the repair.
[Captivate Q&A, Help & Troubleshooting] 4-2ndtwin:
I recommend tryin a Jig first. U can make one easily or buy one. That screen u r seeing is the reason i had to make my 1st jig several yrs ago. Once i had the jig and it got me into the regular Download mode screen, my pc recognized my phone with no problem and i was able to flash successfully through Odin.
[Captivate Q&A, Help & Troubleshooting] chetansaraf:
..

---------- Post added at 09:57 PM ---------- Previous post was at 09:51 PM ----------

... Sir, I got no idea about Jig thing. And I have already tried heimdall and Odin. Kindly give me link about Jig so that I can try that as well ...
[Captivate Q&A, Help & Troubleshooting] 4-2ndtwin:
Here is a link to a thread on how to make one...and youtube probably has many videos. Just search for samsung download mode jig. Or search XDA about it as well.

http://xdaforums.com/showpost.php?p=9238587&postcount=1
[Captivate Q&A, Help & Troubleshooting] chetansaraf:
... thanx man. i fully got it after watchin the video. but one thing i ddnt understand is how is it gonna make computer find the phone. this thing is for puttin the phone in download mode !!!. please throw some light and pardon my innocence :laugh: ...
[Captivate Q&A, Help & Troubleshooting] 4-2ndtwin:
Not sure if it will help the pc to recognize it in ur case, but it did mine. Its just the next logical step in troubleshootin ur phone.
[Samsung Epic 4G Touch] Shader-LXIX:
Will qbkings video on flashing a costume recovery work on a stock rooted e4gt, Fi27 build. Would I end up using a ff18 custom recovery?
[Samsung Epic 4G Touch] g_ding84:
I am assuming yes. As using Odin you just need the right file.

http://xdaforums.com/showthread.php?t=1767421

download the 6.5 .TAR file and follow the video.

put your phone in download mode.

open ODIN, make sure only auto reboot is checked

load .tar file into pda slot.

hook your phone up to the cable. (you'll see a yellow box with COM:xx) means your connected.

press start.

Wait until phone has rebooted. Good to go
[Samsung Epic 4G Touch] Shader-LXIX:
Awesome I shall give that a shot after I read a couple more threads.
[Samsung Epic 4G Touch] g_ding84:
Yes make sure you read a lot of stuff here.

Don't know if you've seen this yet but check it out

http://xdaforums.com/showthread.php?t=1525495
[Samsung Epic 4G Touch] atruebmf:
Yes, I've intstalled the FF18 agat kernal on FI27 many times and works just fine...
[Samsung Epic 4G Touch] g_ding84:
I would recommend upgrading your kernel to Agat's 6.5 kernel or FI27 kernel repack.

Link: http://xdaforums.com/showthread.php?t=1767421 (agat's custom 6.5 kernel Safe recovery)

Link: http://xdaforums.com/showthread.php?t=1942823 (FI27 stock repack Safe recovery)
[Galaxy Note GT-N7000 General] Entropy512:
I was going to put this in the JB thread, but that has apparently been locked due to flaming.

As mentioned in other threads on the eMMC "brickbug", Samsung's official patch for this issue is NOT to remove MMC_CAP_ERASE, but to only disable secure erase in the kernel.

See: https://patchwork.kernel.org/patch/1383661/

Now, we've been highly disappointed that Samsung hasn't included this patch in many updates for a variety of devices. However, on analyzing the kernel, it appears it *might* be safe due to having Samsung's official patch.

If you unpack the kernel, and then run "strings" on the unpacked image, you will see the following:

M8G2FA
MAG4FA
MBG8FA
MCGAFA
VAL00M
VYL00M
KYL00M
VZL00M

e.g. the exact list from the above patch, in the correct order.

So it looks like the XXLS1 JB leak is *probably* safe from the Brickbug - unless Samsung is wrong about nonsecure erase being safe.
[Galaxy Note GT-N7000 General] shantanubarik:
+1

Good news for Note Community
[Galaxy Note GT-N7000 General] clandestino123:
I agree..... thanks for taking the time to share your findings with us.

:good:
[Galaxy Note GT-N7000 General] :
Good to see some improvements from Samsung! Thanks a lot Entropy.. without your precious help this wouldn't be possible :D
[Galaxy Note GT-N7000 General] mjrifath:
Many thanks Entropy..

So now we can do full wipe without any fear...??
[Galaxy Note GT-N7000 General] androidindian:
Brilliant..thanks mate!
[Galaxy Note GT-N7000 General] meethere:
thanks for the update.

Its great to see people like you care for the rest :)
[Galaxy Note GT-N7000 General] Livebyte:
Well, well.

Samsung finally at last!

Thanks Entropy for the good find. :D
[Galaxy Note GT-N7000 General] warfareonly:
Lets hope Samsung did a good job !

Now to download that leak.......
[Galaxy Note GT-N7000 General] qazibasit:
I am still wondering about the update. If we have the brick bug in ics how are we able to flash ota jelly bean?? Wont there be chances of bricking while updating our phone to jb.
[Galaxy Note GT-N7000 General] Entropy512:
The usual applies... Flashing anything via Odin is safe. Flashing anything from a safe kernel is safe. Flashing something with a "safe" update-binary should be safe even on a dangerous kernel.

I'm not going to guarantee the safety of the XXLS1 kernel, as it's hard to guarantee that it is doing what we think it is, but it is PROBABLY safe as opposed to definitively dangerous like any previous official ICS kernel binary. We won't know unless people take risks unfortunately... :(
[Galaxy Note GT-N7000 General] anubis1126:
ok using the jb rom i did indeed soft brick has taken 5 hrs to get my note working, i had a custom rooted 404 rom on with hydracore install the jb with cwm and that was it stuck on samsung logo ,so i then tried to flash stock 404 with pc odin and was stuck on flashing fs image,finally got it working with the pit method and by updating bootloader and clear efs, this has kinda scared me as after a cple hrs trying that it would be sent to repair

be aware this worked for me it may not for anyone else
[Galaxy Note GT-N7000 General] guitarplayerone:
[/COLOR]

I was going to write a sarcastic post but... that sucks

This means the Samsung work around did not work.

Either that or you might have repartitioned for no reason.

Did you try a nandroid restore first?
[Galaxy Note GT-N7000 General] shoey63:
So you bricked bricked flashing on Hydracore? I thought that was safe!
[Galaxy Note GT-N7000 General] randomtext:
He already flashed the jb leak, overwriting hc with its own kernel in the process. Flashing back to 4.0.4 on the leaked rom caused the soft brick, NOT hc.

Sent from my Asylumized shopping cart.
[Galaxy Note GT-N7000 General] shoey63:
He used PC Odin to "flash back". I thought that was safe too!

Anyway odin stuck on factoryfs and needing PIT file method to revive Note is SUPERBRICK, not "softbrick"
[Galaxy Note GT-N7000 General] howard bamber:
I've tried it a dozen times and seems to be ok

Ran the check and lost no memory at al :)

Thanks would be nice for my daring? Stupidity ? Did full wipes etc
[Galaxy Note GT-N7000 General] shoey63:
Actually it's the same as wiping on stock ICS recovery. Well done for trying to verify :thumbup:
[Galaxy Note GT-N7000 General] anubis1126:
what can i say i am a flashaholic flash at least once a week trying varied roms themes etc this time it just happened to me

redone pit file and gained a bit more space
[Galaxy Note GT-N7000 General] shoey63:
Happened to me too useing stupid Cwm.zip - accidentally hit factory reset and BANG! Superbrick! Thankfully grey retailer replaced it.:thumbup:
[Galaxy Note GT-N7000 General] roda1971:
Read please, he already bricked his note. Yes it's save to use odin.
[Galaxy Note GT-N7000 General] musashiro:
i also know that odin is and will always be safe.. ive used odin since my first android ... but what can you say about this guy?? http://xdaforums.com/showpost.php?p=33244016&postcount=9

he said he got bricked after flashing uk stock rom on odin while on PA..
[Galaxy Note GT-N7000 General] shoey63:
Yeah! WTF is going on! People bricking on "safe" kernels, PC Odin, deleting/transfering files on safe kernels. Can someone please explain?
[Galaxy Note GT-N7000 General] anubis1126:
pc odin is safe to use i always use it and will continue to do so
[Galaxy Note GT-N7000 General] Rivan_92:
This may sound hard but its my opinion and everyone can have one.. I believe that only idiots are bricking their devices,, They should read more before doing anything!

You´re welcome to prove me wrong by posting proof of a dev or someone else that knows much about avoiding bricks but still bricked the phone..
[Galaxy Note GT-N7000 General] anubis1126:
i for one am not stupid i have been flashing etc for years now on different devices and tablets no matter who you are or how good you may be each and every one of us that flashes runs the same risk
[Galaxy Note GT-N7000 General] Abagnale:
Yes and no....

Remember the problem with one of the IcsStunner version?;)

And the truth is that when Note came out, Xda was flooded with noobs who didn't want to "waste their time" on reading.
[Galaxy Note GT-N7000 General] Entropy512:
On XXLS1??? I thought the "dangerous" CWM.zip variants were pretty much long gone...
[Galaxy Note GT-N7000 General] Entropy512:
Mostly, they have left something out of their history that was important.

Or they just got unlucky and had a hardware failure unrelated to Superbrick.

So far I haven't seen any definitive confirmation that someone bricked while wiping with the XXLS1 stock kernel - partly because there are so many safe recoveries/update-binaries now. I don't know if we'll ever know for sure if it's safe because the only way to know is for people to put their device at risk (e.g. wipe using XXLS1 kernel, using a "non-safe" recovery, etc.)
[Galaxy Note GT-N7000 General] Entropy512:
Well, he left out the (likely) step of wiping after flashing stock ICS...

If you don't wipe, OF COURSE it's going to bootloop!
[Galaxy Note GT-N7000 General] shoey63:
That was a while ago actually:o Was on stock ICS and wiped on the CWM.zip that you subsequently said was dangerous. I have checked the strings on new 6.0.** versions, and they have "secure wipe" suppressed. I've done nandroid backups/restores plus wipes on them too (running stock ICS kernel). They are perfect for users who want to stay on pure non-rooted stock. Not so good if you flash a zip with format commands in updater script and an unpatched update-binary. However on XXSL1 a format command sent to kernel would result in nosecure erase - correct?
[Galaxy Note GT-N7000 General] msedek:
Yes but entropys point it's that there's no way to prove that nonsecure erase its completely safe unless someone risk the device by wiping on stock jb kernel and that wouldn't prove anything either because it can happen on wipe number 1 or wipe number 2000.. So the best thing to do its not erasing at all and patch all the kernels by disabling "emmc cap erase".. Also entropy did say that he's not sure about the safety on hex patched kernels

Tapatalking on my GT-N7000
[Galaxy Note GT-N7000 General] musashiro:
what if he wiped on stock ICS kernel and got the problem from there???
[Galaxy Note GT-N7000 General] msedek:
If he wiped on stock ics kernel "WIDELY KNOWM AS UNSAFE" well there's nothing else to say about it.. You are bastly warned about to not wipe on unsafe kernels but there's always some people stupid enough to ignore the warnings and even worse they want to spread the voice of that wiping on stock non rooted ICS kernels its safe

Tapatalking on my GT-N7000
[Galaxy Note GT-N7000 General] anubis1126:
i wiped on hydracore which i have a few times i do not wipe on a stock rom as this is as they say not my first rodeo and am back on on rooted and with hydacore now
[Galaxy Note GT-N7000 General] Corininha:
I did it several times between today and yesterday. I saw your post because I was searching for info related to the kernels, as I want to go for Rocket Rom but not sure if is safe from Crash Rom (that was giving me many errors) or I should flash Eybee's back then go for Rocket. Anyway, I am not asking, I am just saying that I did full wipes and partitioned system/preload on XXLS1 and I don't seem to have a problem. :eek:

I hope I will manage to keep it that way.
[Galaxy Note GT-N7000 General] Phil3759:
I have amazing news

Good news: I elucidated the mystery of loosing the possibility to format internal sd from within Settings / Storage / Format USB with my JB stock patched kernels

Bad news: It is caused by patching the binary sequence to avoid brick bug :eek:

Now, we are stuck... until Samsung release the source for JB :p

Detailed Info:

After repacking new leaked JB kernels for i900/n7000, internal sd could no more be formatted from phone (Format USB storage)

After revising all my code, I noted that even a simple unpack / repack of stock kernel without any modification, still causes the issue. So, it was restricted to my unpack / repack process

I tried changing mkbootimg, recompiling it, using third party scripts, same result.

I finally decided not to patch the binary sequence for emmc_cap_erase to try it: Stock kernel, unpacked and repacked worked

I tried my kernel, unpack / repack with editing initramfs but no patching for emmc_cap_erase: Again, it WORKS

Conclusion: the binary sequence is no more linked absolutely to the emmc_cap_erase. As xda Elite developer Entropy512 said, Samsung added probably a workaround for the brick bug without patching emmc_cap_erase. However, without their source code for JB, no one can assert it at 100%

I am a bit hesitant: continue to binary patch (I know your answer Entropy512) knowing it probably add bugs (bad idea I think), or let users go stock unpatched and pray when using leaked firmware?

I know Entropy512 you never liked the approach, and I fully understand and recognize the reasons. However, I have 0 super brick bug reports for my many kernel releases. So, under ICS, it did work. Now clearly, we reach the limit...
[Galaxy Note GT-N7000 General] Phil3759:
Or...

They changed the format command and now we have proof the patching works as it now disable formatting...

edit: I tried a patched stock kernel. Wipe data/factory reset from stock recovery still works. Only format internal sdcard is affected after the patch

Hope these help some one give some conclusions
[Galaxy Note GT-N7000 General] anon67:
This really seems a good news to all of us.it seems all attention is with JB (its expected - not complaining) :) ,but Samsung also pushed out DDLRB to ICS. Can that be analyzed to see if that has emmc bug patched?
[Galaxy Note GT-N7000 General] shoey63:
Well I can confirm that Samsung has DEFINITELY patched JB kernels to suppress "secure erase". I verified this by wiping on stock JB kernel with unsafe CWM.zip (several times plus formats as well). It is the same one that has bricked countless brickbug affected devices on ICS kernels. Doing such operations on stock ICS results in an instant superbrick.

The question about the safety of "non-secure" erase still remains....
[Galaxy Note GT-N7000 General] :
You do know it doesnt always result in superbrick.A lot of people thought because someone did it and didnt brick that it is safe. But that wasnt the case.
[Galaxy Note GT-N7000 General] guitarplayerone:
crazy necropost but fixing a brick by the pit method implies that you actually had a hard brick- permanently corrupted partitions.

the pit method works by repartitioning the memory to avoid these bad blocks, but they are still there on the phone- permanent hardware damage, the blocks cannot be reprogrammed because as soon as the system encounters them (even to read) it will lock up.

a soft brick implies something which is fixable at the software level- eg a ROM not booting because you broke something in /system or with the kernel. Generally this implies the bootloader is intact, but more importantly that there are no sectors of corrupted blocks at the physical level.

just for noobs who might be reading this

i mourn the loss of 3gb on your internal memory

---------- Post added at 01:18 PM ---------- Previous post was at 01:13 PM ----------

+1

There are ways that a kernel could nuke your memory besides the MMC_CAP_ERASE bug which is well-documented. It's also not clear if some folks might be 'at risk' for using unsafe wipe methods in the past, and this JB kernel puts them at continued risk

People have bricked on ICS from issues besides it, it's just much more rare.
[Galaxy Note GT-N7000 General] shoey63:
Flashing unsafe CWM.zip on stock ICS and THEN wiping is a sure-shot superbrick - first time. (Happened to me) My point is that it doesn't occur on JB, so secure erase has indeed been patched. However it should be noted that wiping on stock ICS or JB 3e recovery is exactly the same (non-secure erase) and should be avoided (unless you believe Samsung about the safety of such wiping). I'm confused about the guy above superbricking after flashing a ROM on Hydracore kernel. That is suppposed to be a safe kernel:confused:
[Galaxy Note GT-N7000 General] :
you tought me again something new about the brickbug. bah hum, brickbug lol and the 3e stooge recoveries

lets hope the brickbug wont return
[Galaxy Note GT-N7000 General] shoey63:
Lets hope so!
[Galaxy Note GT-N7000 General] cicciocant:
Now with JB source Kernel is it possibile to be sure of safety of kernel?
[Android Themes] petrukgrinder:
for update
[Android Themes] Aria:
Nice tutorial ;)

thanks :)
[Android Themes] petrukgrinder:
with my pleasure..
[Android Themes] Mockingbird:
I would spam your thanks button if you do this status bar for latest minicm7 2.2.1 ;)
[Android Themes] saldymhmd:
mantap !!! nice tutorial ! i've been searching for this tutorial and now i found it :)
[Android Themes] dredremon:
what cm7 theme your using can u share?
[Android Themes] AChep:
heheh, that's my jelly bean statusbar :D
[Android Themes] PsyGik:
Where have I gone wrong?? Clear text is also displayed along with the image.

Have attached SystemUI.apk after doing all the mods (except network thing)

-------------------EDIT-----------------------------------

solved. Had to edit strings.xml

Now the problem is the clear button won't stay at the right corner. Screenshot attached..
[Android Themes] AiphNday:
Nice..

I like your guide..

:D
[Android Themes] m.ali.ozkaya:
CWM or AROMA installer???:rolleyes:

Mobil cihazdan gönderildi..

aOS 2.3.6 BNC-GIO-R2

MMB-Tweaks_0.9_Fix
[Android Themes] AiphNday:
What is the point of your question??

:what:
[Android Themes] x-dira:
Thanks man! nice guide

Next.....!

Guide 4.0 : How To Make Customization Your Setting Button ^0^

---------- Post added at 02:49 AM ---------- Previous post was at 02:47 AM ----------

how to edit strings.xml?

thanks
[Android Themes] Imperticus:
Doesn't work for me unfortunately. CM7 on LG P990. No status bar.