Database Info

How I Unbricked my Nfuse

I've been a regular visitor on XDA. I am a semi-newbie at this point as I have flashed several ROM's successfully so that's my definition of a semi-newbi . I made some newbie mistakes this time around and soft bricked my Nfuse. It took a lot of reading but I managed to resolve the issue. I have appreciated the detailed posts on this site so I wanted to contribute and detail how I unbricked my Nfuse to help others.
I successfully loaded ICS CM9 for Infuse and spent the afternoon setting up all my apps. At the end of it all I decided it was time to back up the ROM via the ROM Manager app like I had done with GB. So I kicked off the backup and then it boot looped a few times and then it would only boot to CWM. I can't tell if doing this caused it or it not (anyone know if a ROM Manager backup should have worked here?)
I decided to start over so I began the Heimdall 'Stock_SGH_I997_UCLB3_Repartition-One-Click.jar' to get back to GB Rom. In the middle of the flash, it barfed and the phone disconnected from USB. Booted the phone and it was now in a state with the phone and computer icons with a yellow triangle ! in-between. I was now in a state where I could not boot to Download Mode.
More research and I found out about Adam Outler's Heimdall 'One Click Unbrick' and it brought it back to life. I was then able to get back into download mode, flash back to stock ('Stock_SGH_I997_UCLB3_Repartition-One-Click.jar' & 'SGH_I997 Entropy Test Kernel-One-Click.jar') from Entropy and got into GB. Then followed up with the CM9 ICS install using 'update-cm-9.0.0-RC0-infuse4g-05272012-UNOFFICIAL-signed.zip' and 'gapps-ics-20120429-signed.zip'.
So I am back to ICS (and love it!). I just wanted to express my thanks for all the work others have done to provide us with these tools. I had already ordered a JIG from eBAY and was going to have to wait for it to be delivered to see if it would get me into download mode. I thought I was in a hard brick at one point as I found conflicting posts about what a hard brick really is. I now know a hard brick is dead as a doornail so I was in a soft brick situation. I was also considering sending the phone to be JTAG repaired for $40 but I am happy it was a soft brick.
In any case, my phone is resurrected and I am happy and I hope this post helps others.
Tai'Shar

Tai'Shar said:
I've been a regular visitor on XDA. I am a semi-newbie at this point as I have flashed several ROM's successfully so that's my definition of a semi-newbi . I made some newbie mistakes this time around and soft bricked my Nfuse. It took a lot of reading but I managed to resolve the issue. I have appreciated the detailed posts on this site so I wanted to contribute and detail how I unbricked my Nfuse to help others.
I successfully loaded ICS CM9 for Infuse and spent the afternoon setting up all my apps. At the end of it all I decided it was time to back up the ROM via the ROM Manager app like I had done with GB. So I kicked off the backup and then it boot looped a few times and then it would only boot to CWM. I can't tell if doing this caused it or it not (anyone know if a ROM Manager backup should have worked here?)
I decided to start over so I began the Heimdall 'Stock_SGH_I997_UCLB3_Repartition-One-Click.jar' to get back to GB Rom. In the middle of the flash, it barfed and the phone disconnected from USB. Booted the phone and it was now in a state with the phone and computer icons with a yellow triangle ! in-between. I was now in a state where I could not boot to Download Mode.
More research and I found out about Adam Outler's Heimdall 'One Click Unbrick' and it brought it back to life. I was then able to get back into download mode, flash back to stock ('Stock_SGH_I997_UCLB3_Repartition-One-Click.jar' & 'SGH_I997 Entropy Test Kernel-One-Click.jar') from Entropy and got into GB. Then followed up with the CM9 ICS install using 'update-cm-9.0.0-RC0-infuse4g-05272012-UNOFFICIAL-signed.zip' and 'gapps-ics-20120429-signed.zip'.
So I am back to ICS (and love it!). I just wanted to express my thanks for all the work others have done to provide us with these tools. I had already ordered a JIG from eBAY and was going to have to wait for it to be delivered to see if it would get me into download mode. I thought I was in a hard brick at one point as I found conflicting posts about what a hard brick really is. I now know a hard brick is dead as a doornail so I was in a soft brick situation. I was also considering sending the phone to be JTAG repaired for $40 but I am happy it was a soft brick.
In any case, my phone is resurrected and I am happy and I hope this post helps others.
Tai'Shar
Click to expand...
Click to collapse
You're welcome, Tai.
from the op:
1. To cleanly install the latest ATT Infuse UCLB3 Gingerbread leak. No hassle One-Click. Then enjoy the lastest leak of Infuse GB.
2. To Restore your phone to factory state.
3. To Restore your phone from boot loops, Samsung Logo, Soft Brick - non-hardware related failures from bad flashes, borked partitions or mismatch voodoo partitions. (I suspect many users will use it for this purpose)
Scenario #1: Oh, gosh! I would love to have the latest GB leak from AT&T! How to I do that? What in the world is Odin? Ain't it some mythological Norse deity?
Heimdall 1 click - done!
Scenario #2: I think I did something to my phone. It's not working right. My wifi is dropping like a leaky faucet. My Market is not working. I hate my phone! I wish it was like factory.
Heimdall 1 click - done!
Scenario #3: Oh crap! I just #@#% in my pants! I bricked my phone. OMG!!! I'm stuck on SAMSUNG logo! I'm boot looping! I lost recovery! Help me!!!
Heimdall 1 click - done.

Rom Manager Backups and CM9 ICS
This might be a dumb question.... In my post above, does anyone know if using Rom Manager to perform a ROM Backup on ICS CM9 5/27/2012 build would or could cause the boot loop/soft brick? It probably is a coincidence but now I am not sure I want to try it again.
Tai'Shar Xda

Rom Manager Backup
Ah, never mind, just found it in the Nfuse CM9 ICS Rom thread. It does cause a boot loop: http://forum.xda-developers.com/showpost.php?p=26648460&postcount=1090
Tai'Shar Xda

I know you already found the answer, but do not use from manager. Do you backups from the nandroid in recovery only. From mgr will definitely give you issues.
Sent from my SGH-I997 using xda premium

ppalbicke said:
I know you already found the answer, but do not use from manager. Do you backups from the nandroid in recovery only. From mgr will definitely give you issues.
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
lol ah yes... brings back some unhappy memories...

Also...your yellow triangle with the ! Is still download mode...just a differnt mode-just an fyi that wasnt really that important....
Anyways glad you figured it out and posted to help.others who may not know how to use heimdal
Sent from my SAMSUNG-SGH-I997 using XDA

ppalbicke said:
I know you already found the answer, but do not use from manager. Do you backups from the nandroid in recovery only. From mgr will definitely give you issues.
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
Thanks for the input on this. I was about to research the best method for backup.
For backup of just the sdcard and all my photos and other personal files I've been using the Samba app. My PC has a mapped drive to the Samba share on the phone which is \sdcard. I use an inexpensive app on my PC called GoodSync and it checks every 10 min for the share and if it sees it after I enable Samba, it auto replicates all files to a folder on my PC. Not good for OS recovery but works well for personal data.
Tai'Shar Xda

mg2195 said:
Also...your yellow triangle with the ! Is still download mode...just a differnt mode-just an fyi that wasnt really that important....
Anyways glad you figured it out and posted to help.others who may not know how to use heimdal
Sent from my SAMSUNG-SGH-I997 using XDA
Click to expand...
Click to collapse
Thanks, I looked everywhere for the answer to that question.
Now that i recovered from a failed flash, I feel a bit more confident in replacing ROM's when I want to change the flavor.
I've read that these Samsung phones are really good for recovering from screw ups unlike other brands so i am glad I have the Infuse (but I have my eye on the new Galaxy III S).

[CAUTION][ICS][UPDATE][DOWNGRADE]Read before flashing ICS

After the ICS was leaked, it bought some good news and as well some bad news..
Some of our user have just bricked their mobile after performing a wipe data thru recovery..
The cause of error is yet unknown..
Out user vijai has published some of the known causes...
The credit goes to vijai for pointing it out
vijai2011 said:
CAUSES
Symptoms of super brick(caused by emmc bug):
1.Phone gets stuck at splash screen.
2.recovery gets stuck at whenever trying to access corrupted partition.
3.ODIN gets stuck at flashing factoryfs.
4.You can flash kernel but almost nothing else using both ODIN and cwm.
Sent from my GT-N7000 using xda app-developers
Click to expand...
Click to collapse
vijai2011 said:
FIX
No problem....temporary fix to avoid bricking is to avoid using cwm to flash anything,doing wipes in cwm,formatting partitions in cwm,doing factory reset through settings and by typing code in phone,removing large size files from sdcard.
The permanent fix is to disable MMC_CAP_ERASE in kernel while making it.Any kernel dev can do that easily I guess....
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
This definitely doesn't mean that all galaxy R handset are brick bug or you may encounter such problem..
Only a few have encountered the problem and the cause is yet unknown. This definitely, doesn't stop you from flashing ics..if you want to flash keep these things in mind.
Also, please do not completely rely on brick bug app from play store because the app (imo) is not supported to our device (correct me if i am wrong)
(i am no developer, just heard from my fellow user )
*****NOTE******
This applies to the Stock ROM released by machram and as well to all those ROM which are based/built upon the Stock ROM.
Click to expand...
Click to collapse
SO WHAT DOES IT MEANS TO YOU ?
If you have already flashed ICS, you are requested not to wipe data through CWM/Stock recovery and also do not factory reset the phone till the issue is identified. i.e. Once ICS === No Wipe (till its rectified)
Click to expand...
Click to collapse
Currently there are only two users who have hard bricked their phone after flashing ICS.
As you might be aware by now that the emmc brick bug app is not compatible with our phone.
The most elite developer Entropy512 wants to make it compatible and hence wants some sample..
Entropy512 said:
Can someone who experienced damage and still has their device contact me via PM? One of my contacts wants to collect a few damaged devices.
Click to expand...
Click to collapse
Note: I dnt recommend you to brick your phone
(thanks m.kochan, callmeventus, cooleagle)
A big thanks to entropy for showing interest to our device

Caution:
Here's what to say from a user who bricked his phone
mj.vikram said:
Caution:
when you are running ICS on you mobile do not downgrade directly to GB using ODIN, if you flash any GB ROM ROM (Stock/Custom) using ODIN your mobile will be bricked.
Live example is myself i have bricked my mobile by do this.
TO avoid this first you restore previous backup using CWM and then flash what ever you want using ODIN.
even Unbrick your Galaxy R. 2. Downgrade bootloader to v2.0 guide wont help you, I have followed it but no use I have successively flashed stock rom by using this method but still no luck..
Click to expand...
Click to collapse
*******UPDATE********
Here is the new fix method
vijai2011 said:
And guys for the guide to safe flash:
Flash a GB kernel,boot into recovery,flash any rom.GB or ICS.Its safe to wipe in gb kernel.But once you flashed ICS you arent safe.If you need to wipe again,you need a GB kernel again.
This was the method we used in Note to wipe when had not got a safe kernel.
Click to expand...
Click to collapse
We have got one lucky user who is enough brave and tested this method
selva.simple said:
To make a conclusion to that, i have tested your method in Galax R buddy. I found that i had a GB kernel in my phone. So why wait till i reach home. Tested now itself. I tested two rounds. One is for getting ICS via CWM flash and the other is for getting ICS via CWM restore.
First Test:
1. Flashed GB kernel
2. Rebooted to Recovery
3. Wipe data
4. Flash ICS by CWM flash i.e., "Install from Zip" method
5. Reboot
Second Test:
First Three points are same. and finally Restored a nandroid backup of ICS i took earlier. Reboot
In both the method i was able to boot the phone and get the ICS ROM and ICS kernel. To add more,
After both boots, I tested the system apps and data apps - mainly Play store, Gmail, Music player, Gallery, Camera for any FC issues. Everything is working perfectly and no issues created apart from existing issues of ICS.
Click to expand...
Click to collapse

And I forgot to add that It is not necessary that brick occurs once you do the above said things....for example,brick may occur at 10th factory reset,100th flash etc....And it is safe to flash anything with Odin as it shouldn't invoke MMC_CAP_ERASE from kernel when flashing.
Sent from my GT-N7000 using xda app-developers app

vijai2011 said:
And I forgot to add that It is not necessary that brick occurs once you do the above said things....for example,brick may occur at 10th factory reset,100th flash etc....And it is safe to flash anything with Odin as it shouldn't invoke MMC_CAP_ERASE from kernel when flashing.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Yes i do agree..d problem may arise on 1st or on 100th wipe...
Bt the cause is yet unknown...
So imho, all the noobs shldnt do..who knows they get it for the first time...
Sent from my GT-I9103 using Tapatalk 2

Seriously? Removing large size files from sdcard can brick my phone?

Fusrodah said:
Seriously? Removing large size files from sdcard can brick my phone?
Click to expand...
Click to collapse
Dont know...but i have tried deleting large files as 1gb game data...such as max payne and asphalt7
No brick...
Sent from my GT-I9103 using Tapatalk 2

Fusrodah said:
Seriously? Removing large size files from sdcard can brick my phone?
Click to expand...
Click to collapse
Yes....sometimes.....it was reported by like 2 users have galaxy Note.While deleting large files,the phone stuck and force reboot caused damaged sdcard.
Sent from my GT-N7000 using xda app-developers app

vijai2011 said:
Yes....sometimes.....it was reported by like 2 users have galaxy Note.While deleting large files,the phone stuck and force reboot caused damaged sdcard.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Well, how much reports from Galaxy R users with bricks? I see one from mj.vikram. Anyone else?

So a little story now.
From where has this infamous brick bug appeared??
Analysis by kernel devs say that MMC_CAP_ERASE command in kernels are present from gb periods.But why hasn't it been causing problems in GB?That's because it was disabled as Google didn't see the need for it.
But in ICS they feel that just removing files causes security problems.so they thought of enabling MMC_CAP_ERASE command which will completely wipe instead of removing.
So why should it need to brick our devices?
That's because,one of the Google engineer said that our mmc uses buggy firmware that initiates wrong process when the kernel receives MMC_CAP_ERASE command.
Actually MMC_CAP_ERASE command and mmc buggy firmware are harmless on its own.But when both are combined the result is super brick.
Sent from my GT-N7000 using xda app-developers app

This is not the worst scenario. In worst case you're gonna get hardbrick with no possibility to turn your device on.
MMC_CAP_ERASE on - wasn't present in every ICS version, at least not for S2 (I know that NOte users had bigger problem with that). All previous 4.0.3 were totally safe. Latest 4.0.4 - unfortunately not. It's not really buggy firmware that causes any problem here. According to Entropy512 (I guess the best xda-expert in that matter) MMC_CAP_ERASE was activated in order to improve writing speed. Hard brick occur if the all three conditions are fulfilled here:
1) You have a faulty (brickable) emmc-chip
2) If MMC_CAP_ERASE command is activated in kernel
3) If you perform wipe/restore nand backup/install roms (wipe-type) where:
a) cwm recovery - very high risk
b) stock recovery - lower risk but still not equal 0.
So faulty emmc chip is a bomb, mmc_cap_erase is a fuse, wiping in cwm - is a trigger or fire!
Not all devices are endangered, only those with brickable emmc-chips. In regard to Note or S2 it's easier because those devices have great dev support and there were thoroughly examined. So there are known some ways to bypass this problem. In case of SGR is much harder. First of all ... we don't know which chips are really sane and which are not.

Fusrodah said:
Well, how much reports from Galaxy R users with bricks? I see one from mj.vikram. Anyone else?
Click to expand...
Click to collapse
Just two as of now so don't panic !
You can use ICS 4.0.4 but till the cause of the bricking is confirmed just don't preform any Wipe data / Wipe Cache / Factory reset operations while on ICS 4.0.4 ROM.
As per mkochan if you want to go back to the stock ROM for giving it to the service center / etc then directly flash GB / 2.3.x ROM without wiping the cache / data using CWM.
m.kochan10 said:
1) To avoid brick = don't wipe, don't do factory reset, do not restore nandbackups.
a) If you wanna to get rid of this fw.version
-> Flash a safe kernel / or best stock rom directly via Odin.
-> Wipe after installation process is done. NOT BEFORE!
2) To recover...one guy from Note section wrote a tutorial for those bricked devices that was able to turn on. He managed to recover it but he had to sacrifice 2-3 gb of internal storage. If device is not bootable then it's a motherboard replacement.
3) Turning off this function in kernel is not easy thing. I don't think this flag can be easily removed. I'm not a kernel guy....so I'm sorry but don't know much more about that. Our devs can take a look, maybe they can find a solution.
4) Bootloaders cannot be flashed via recovery, not via mobile odin either. And FW-odin version is still unavailable so I assume you still have GB ones.
5) About USB jig - Is your DM protocol the same like before? 2.0? (people with 2.1 have never been able to used jig as far as I remember)
Click to expand...
Click to collapse

Okay, we must wait for kernel with disabled MMC_CAP_ERASE. I hope we'll get it. Thanks for the information.

Oh my god
I did factory reset in ics because my keyboard dissappeared. Will my device hard brick?
I cannot understand why Samsung realeses a firmware which should make our mobile dead! What is this function even for?
Sent from my GT-I9103 using xda premium

You can find sort of explanation on the previous page

Just wondering should I worry about this if the bug eMMC app reports that I have a sane chip?

Google86 said:
Just wondering should I worry about this if the bug eMMC app reports that I have a sane chip?
Click to expand...
Click to collapse
I think app is not working for SGR, both user have used this app and app shown sane chip yet those both guys devices are bricked.
We should contact dev of app to make comp with SGR.
Sent from my CM7.2 powered Galaxy R using Tapatalk 2.

Damn it , I knew this would happen.....
"Friends forever." - Ventus

Guys actually you could check if you have any bad blocks in any partition through gpartrd in adb.Just looking its info.will post when I find some.
Sent from my GT-N7000 using xda app-developers app

OP please add this also,
Caution:
when you are running ICS on you mobile do not downgrade directly to GB using ODIN, if you flash any GB ROM ROM (Stock/Custom) using ODIN your mobile will be bricked.
Live example is myself i have bricked my mobile by do this.
TO avoid this first you restore previous backup using CWM and then flash what ever you want using ODIN.
even Unbrick your Galaxy R. 2. Downgrade bootloader to v2.0 guide wont help you, I have followed it but no use I have successively flashed stock rom by using this method but still no luck ..
Sorry i have't seen this thread and created new one, so if you think i have created duplicate one please ask Justin to delete it....

mj.vikram said:
OP please add this also,
Caution:
when you are running ICS on you mobile do not downgrade directly to GB using ODIN, if you flash any GB ROM ROM (Stock/Custom) using ODIN your mobile will be bricked.
Live example is myself i have bricked my mobile by do this.
TO avoid this first you restore previous backup using CWM and then flash what ever you want using ODIN.
even Unbrick your Galaxy R. 2. Downgrade bootloader to v2.0 guide wont help you, I have followed it but no use I have successively flashed stock rom by using this method but still no luck ..
Click to expand...
Click to collapse
Dude i dont have a GB Backup (CWM BACKUP)
and dude, what you gonna do now, how will you get back your phone ???

[Q] maybe i brick my phone

i have a motorola atrix 2 at&t(MB865).my phone was 2.3.6
1. I try to flash this firmware 5.5.1-EDEM-28-37-MEARET_cfc.xml.zip from this site http://sbf.droid-developers.org/edison/list.php with rsd.at 7/20 rsd was writting fail.i tried again with same result.after this my phone had problem with boot.the only method for boot was "vol down"+"vol up"+"power" and after i was pressing "Normal powerup".after all these my phone booted normal and worked normal.
2.after i flashed the Blur_Version.55.13.25.MB865.ATT.en.US.zip (ics) from this http://forum.xda-developers.com/showthread.php?t=1779968 and my phone was working normal but with the same problem with the boot.
3.after i tried to use this utillity http://forum.xda-developers.com/showthread.php?t=1805975 .this process had some failure and after this my phone is unable to boot.
with "vol down"+"vol up"+"power" i can choose normal power up, but phone stucks at boot image.in addition i can choose recovery and phone boots at recovery mode.i choose to update from sd with this file Blur_Version.55.13.25.MB865.ATT.en.US.zip but my phone writes that its unable to flash this.
4.after i try to flash InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID28 5.zip with rsd.the rsd wrote fail at 3/20 in addition i use the replace.zip with the same result.
5.after i try again the 3rd step with same results.
can anyone help me?

This whole mess started when you tried to flash MEARET firmware on your AT&T phone. NEVER mix firmware!
And trying recovery at this point is not going to work, as the ICS zip is just a large patch file for 2.3.6. And since it failed on the fxz, a portion of your system is missing so ICS won't install. You need to fxz back.
What step is the script falling at? A screenshot would be helpful.
And for the future, please post questions in the Q&A form.
Sent from my SAMSUNG-SGH-I727 using xda premium

you mean at 3rd step?
sorry.please move this thread at q&a

Yes the script from step three is what's going to save you here.
But we need to know where it's failing at.
Sent from my SAMSUNG-SGH-I727 using xda premium

i can see that problem is with cbt, recovey and cdrom partition.

Uh oh.
Which ICS version did you install? Please show need the thread.
I need to know which leak it was.
Sent from my SAMSUNG-SGH-I727 using xda premium

Blur_Version.55.13.25.MB865.ATT.en.US.zip

Well I hate to tell you man. But you are soft bricked until we find an fxz for ICS.
Recovery and cdrom are failing because cdt.bin isn't flashing. And we haven't found a fix for this yet.
Although the strange thing is that this shouldn't be happening on the first leak... but it is...
So you're bricked mate.
Sent from my SAMSUNG-SGH-I727 using xda premium

ok, i will wait.
thanks.
but please explain to me.i had a motorola a1200 and a siemens sx1.when i flashed a firmware, all the flash memory erased and new data wrote at flash.if i had bootloader, all was fine.the only method to brick a phone was to replace the battery when flash the bootloader(or flash false bootloader).
at A2, why when i write a new bootloader and new mbr(and partition table?) is necessary to flash the same or newer edition of firmware?this is because bootloader is locked?
i thought when i flash a new firmware, all the flash memory erased and writes new data(at the begining the bootloader, after mbr with partition table, after the image(i think this is the kernel of linux) and all other the data)

macnick said:
i have a motorola atrix 2 at&t(MB865).my phone was 2.3.6
1. I try to flash this firmware 5.5.1-EDEM-28-37-MEARET_cfc.xml.zip from this site http://sbf.droid-developers.org/edison/list.php with rsd.at 7/20 rsd was writting fail.i tried again with same result.after this my phone had problem with boot.the only method for boot was "vol down"+"vol up"+"power" and after i was pressing "Normal powerup".after all these my phone booted normal and worked normal.
2.after i flashed the Blur_Version.55.13.25.MB865.ATT.en.US.zip (ics) from this http://forum.xda-developers.com/showthread.php?t=1779968 and my phone was working normal but with the same problem with the boot.
3.after i tried to use this utillity http://forum.xda-developers.com/showthread.php?t=1805975 .this process had some failure and after this my phone is unable to boot.
with "vol down"+"vol up"+"power" i can choose normal power up, but phone stucks at boot image.in addition i can choose recovery and phone boots at recovery mode.i choose to update from sd with this file Blur_Version.55.13.25.MB865.ATT.en.US.zip but my phone writes that its unable to flash this.
4.after i try to flash InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID28 5.zip with rsd.the rsd wrote fail at 3/20 in addition i use the replace.zip with the same result.
5.after i try again the 3rd step with same results.
can anyone help me?
Click to expand...
Click to collapse
Use rsdlite and flash the Asian or Chinese stock firmware worked for me when I had this issue now I'm running 4.1.1 cm10 jb and its awesome!
If this works for you hit my thanks button
P.s phone must be in fast boot mode
Sent from my MB865 using XDA Premium HD app

Code:
whiteboi-hakz
can you tell to me which firmware you mean? and where i can find.
Code:
Fall of Enosis
i forget to tell you that i did the ics ota update from at&t.
so maybe i have the same problem with others...

macnick said:
Code:
whiteboi-hakz
can you tell to me which firmware you mean? and where i can find.
Code:
Fall of Enosis
i forget to tell you that i did the ics ota update from at&t.
so maybe i have the same problem with others...
Click to expand...
Click to collapse
http://sbf.droid-developers.org/edison/list.php
There is the firmware you wanted dude
Download retail Chinese
Sent from my MB865 using XDA Premium HD app

macnick said:
Code:
Fall of Enosis
i forget to tell you that i did the ics ota update from at&t.
so maybe i have the same problem with others...
Click to expand...
Click to collapse
If you did the OTA ICS update you WILL NOT be able to flash the FXZ back. We have no way out of this right now. And if you are bootlooping or stuck on the splash screen then you are bricked. Sorry mate.
Please read these threads:
http://forum.xda-developers.com/showthread.php?t=1897042
http://forum.xda-developers.com/showthread.php?t=1882335
whiteboi-hakz said:
http://sbf.droid-developers.org/edison/list.php
There is the firmware you wanted dude
Download retail Chinese
Sent from my MB865 using XDA Premium HD app
Click to expand...
Click to collapse
Whiteboi, thanks for your consideration of others but PLEASE, research before you try to help others. For one thing, he is on an MB865 AT&T phone and therefore MUST download the firmware for an AT&T phone. The international versions of the A2 are completely different, including radio, WiFi and the like. NEVER mix firmwares.
Also, he already flashed international firmware which is what got him into this predicament in the first place. He also installed the OTA update for ICS for which there is NO GOING BACK. Read the threads I gave him and educate yourself man.
I applaud you generosity, but if he wasn't already bricked, your advice would have surely/quite possibly bricked him. Be careful man.
Read, read, read!

Fall of Enosis said:
If you did the OTA ICS update you WILL NOT be able to flash the FXZ back. We have no way out of this right now. And if you are bootlooping or stuck on the splash screen then you are bricked. Sorry mate.
Please read these threads:
http://forum.xda-developers.com/showthread.php?t=1897042
http://forum.xda-developers.com/showthread.php?t=1882335
Whiteboi, thanks for your consideration of others but PLEASE, research before you try to help others. For one thing, he is on an MB865 AT&T phone and therefore MUST download the firmware for an AT&T phone. The international versions of the A2 are completely different, including radio, WiFi and the like. NEVER mix firmwares.
Also, he already flashed international firmware which is what got him into this predicament in the first place. He also installed the OTA update for ICS for which there is NO GOING BACK. Read the threads I gave him and educate yourself man.
I applaud you generosity, but if he wasn't already bricked, your advice would have surely/quite possibly bricked him. Be careful man.
Read, read, read!
Click to expand...
Click to collapse
Dude it works and he can then reflash his fw so what's the big deal the one I bricked was at&t non international and that method worked great but I'll take your advice man
Sent from my MB865 using XDA Premium HD app

i tried your method without any Success.
so "fall of enosis" is right.maybe the solve of the problem is to find an ics firmware(from at&t????)

macnick said:
i tried your method without any Success.
so "fall of enosis" is right.maybe the solve of the problem is to find an ics firmware(from at&t????)
Click to expand...
Click to collapse
OK well was worth a try I guess ay try his method and let's us know
Sent from my MB865 using XDA Premium HD app

macnick said:
i tried your method without any Success.
so "fall of enosis" is right.maybe the solve of the problem is to find an ics firmware(from at&t????)
Click to expand...
Click to collapse
Yeah man, if you OTA'd to ICS then I can almost guarantee it will fail at step 3 of the flash process which is the cdt.bin. If you are using the script it will also fail on the recovery portion and the cdrom portion. These are both because of the cdt.bin As of right now, we have no fix for this. Once again, this is the reason we are recommending people to ONLY use the first leak, and not OTA to ANYTHING unless it's 2.3.6 GB. Once again, reference the links I sent you.
You're bricked sir.
Until we find an ICS fxz. Which might be A LONG TIME.
Time to get a replacement/new phone.

Fall of Enosis said:
Yeah man, if you OTA'd to ICS then I can almost guarantee it will fail at step 3 of the flash process which is the cdt.bin. If you are using the script it will also fail on the recovery portion and the cdrom portion. These are both because of the cdt.bin As of right now, we have no fix for this. Once again, this is the reason we are recommending people to ONLY use the first leak, and not OTA to ANYTHING unless it's 2.3.6 GB. Once again, reference the links I sent you.
You're bricked sir.
Until we find an ICS fxz. Which might be A LONG TIME.
Time to get a replacement/new phone.
Click to expand...
Click to collapse
Thanked you as earned it man
Sent from my MB865 using XDA Premium HD app

Help Pls, I think I've just Bricked my phone :(

I've installed the new CM10 on my P500, It's working just fine, the problem is I have no GSM reception, it doesn't detect my sim card. When I upgraded from my GingerBread Void version, I wiped the system clean, and I do believe (knowing what I know know) that I've erased everything, including my baseband.
I've been looking into the problem and it seems that I should have kept the base-band (or something).
I've downloaded the LGMDP and the V20 Baseband in order to try to rewrite it. But no dice. After I hit download the End window shows nothing but the IMEI, no Bluetooth ADDR, nothing, just the IMEI.
Also no NV2 file is generated.
Does anyone have a clue?

Does it boot but not ask for the PIN to unlock the SIM?
Sent from my LG-P500 using xda app-developers app

Yes, it boots just fine. The CM10 works brilliantly ), smooth and clean, but I have no GSM, it simply doesn't detect my SIM. If I try to make a call it says something like "no network detected"

In the "about phone" menu, the baseband reads "Unknown"

Ok, I've been reading some more and It would seem that the phone is not literally "Bricked". I think I have to flash a stock rom back in order to get the right baseband. Please correct me if I am wrong because this is what I am going to do when I get home, being that I'm at work right now I have no way of testing anything.

Well if it boots, you haven't got a high-tech brick. I had a similar problem recently although I didn't check in any of the menus like you said. I knew when it didn't ask for the pin. For some reason it wasn't detecting the STK.apk although it was there.
Have you got some kind of file explorer (root enabled) installed? If so, check /system/app to see if STK is there. If not then you need to put it there (get it from another ROM). And edit the permissions to RW-R--R--.
As it was there for me, I tapped it so it installed (as a user app) and then uninstalled it and rebooted and it was fine. I guess it just needed reminding that it is, first and foremost, a telephone.
Formatting everything through recovery shouldn't wipe your baseband but if you still get nothing there are tuts here about flashing BB.
Hope you get it solved.
Sent from my LG-P500 using xda app-developers app

Hmm, thank you, I'll be sure to check that.

If you were on Void before you transitioned to cm10, most probably you may just have to flash an "old BB fix" ( available in many threads in this forum, just search) as Void was for old BB & all the current new ROMS including CM10 are on new BB. Avoid new BB flashing thru LGMDP or any other means as far as possible. old BB fix can be used without any side effects on CM 9/10 based ROMS.
Sent from my LG-P500

Thanks for the advice, but I've already tried that last night, unfortunately it didn't help

digsf said:
Thanks for the advice, but I've already tried that last night, unfortunately it didn't help
Click to expand...
Click to collapse
If your using AmonRa recovery you have to mount system before you flash obb fix or it wont work.

At the moment I'm using Team Win recovery, but I'll definitely give that a try

At the moment I'm using Team Win recovery, but I'll definitely give that a try.

digsf said:
At the moment I'm using Team Win recovery, but I'll definitely give that a try.
Click to expand...
Click to collapse
Thanks 3ncrypt3d_droid, ur right. I missed mentioning that, & I use AmonRa too...

pmvyas said:
Thanks 3ncrypt3d_droid, ur right. I missed mentioning that, & I use AmonRa too...
Click to expand...
Click to collapse
Glad I could help

Thanks Jerry.
digsf - did this solve your problem ?

Not at the moment, I've finally gotten home, I'm working on it right now )

Brilliant, I've got it working, I'd like to thank all of you, especially WidowCranky and 3ncrypt3d_Droid who gave me the right clues . The permission wasn't set on my TeamWin recovery and the BBFix Update wouldn't work. Set the permission right, flashed the fix. Works perfectly. Thank you all very much. I am officially on Jelly Bean

Congrats & enjoy.
Sent from my LG-P500

digsf said:
Brilliant, I've got it working, I'd like to thank all of you, especially WidowCranky and 3ncrypt3d_Droid who gave me the right clues . The permission wasn't set on my TeamWin recovery and the BBFix Update wouldn't work. Set the permission right, flashed the fix. Works perfectly. Thank you all very much. I am officially on Jelly Bean
Click to expand...
Click to collapse
There is another work around for that issue also, just to keep from having to apply the baseband patch after flashing ROMs. Instead of flashing P500 ROMs, flash P509 ROMs instead. The hardware is identical, only difference is baseband. P509 will always be old baseband as they never got official GB support from LG. Just a thought. That's assuming the dev for the ROM you are using builds for P509 too. Again, just a thought.

Glad you got it working, glad I could help, even if only in a small way.
Enjoy JB.
Sent from my LG-P500 using xda app-developers app

[Q] bricked and terrified 4.3

okay i upgraded to 4.3 OTA and tried to revert back and soft bricked my phone. I still have access to download mode and the stock recovery. I know now that i can not revert but is there any way of getting it back to 4.3 so i can have a phone again?
thanks for the future help.

This is similar what happened to me. I have never done anything with my phone as far as rooting and I tried reverting to stock 4.1.2. In Odin I kept getting the "Nand Start! Fail (Auth)" because of the locked bootloader I guess. I flashed some other firmware that was unofficial with the locked bootloader and now I get the "unauthorized software detected" and I cant do anything but enter Odin download mode. What should I do?

that is exactly what is happing to me. same error and all.

Once you took the OTA 4.3 you got locked in. No way of going back.
Sent from my SCH-I535 using Tapatalk

I dont want to go back just get rid of the soft brick so i can use it

im having the same problem and need to get it fixed please help anyone???!!!! im leaving for florida in two days and have nothing else. HELP!!!!

If you took the OTA and tried to flash 4.1.2 Odin or unlock bootloader you are Hard bricked , no method or recovering it yet.
If you have stock recovery and download mode , only hope is wait for 4.3 .tar file

Theres no custom recovery I can flash and flash some other software or something?

Elemt said:
Theres no custom recovery I can flash and flash some other software or something?
Click to expand...
Click to collapse
Nope , once you take 4.3 OTA you done , no flashing anything. And once you try to flash recovery or revert to older software you are bricked.
Sorry to be the bear of bad news.
There is a full thread of why and how so many devices have been bricked
http://forum.xda-developers.com/showthread.php?t=2575661

jlyle said:
Nope , once you take 4.3 OTA you done , no flashing anything. And once you try to flash recovery or revert to older software you are bricked.
Sorry to be the bear of bad news.
There is a full thread of why and how so many devices have been bricked
http://forum.xda-developers.com/showthread.php?t=2575661
Click to expand...
Click to collapse
Do you know if anyone is working on a fix? or a .tar file of 4.3?

dvdavid2 said:
Do you know if anyone is working on a fix? or a .tar file of 4.3?
Click to expand...
Click to collapse
Thanks for the info. hopefully a fix will be done soon. And do you know how i should keep to see when the work around is finished .
thanks in advanced guys.

This might give you a chance to unbrick.... possibly
http://forum.xda-developers.com/showthread.php?t=2581166

I got the "unauthorised software detected" on my phone like 3 days ago from messing up on a recovery and all I did was go into the Verizon store and said idk what happened and they called technical support and they asked me if I flashed software on my phone and I just said "no, I just plugged it into my laptop and it did this" so they said they will just send me a new sgs3 and I just got it today.
Pretty simple.
And I don't have insurance .
Hit thanks if I helped
Sent from my SCH-I535 using xda app-developers app

ScubaSteev said:
I got the "unauthorised software detected" on my phone like 3 days ago from messing up on a recovery and all I did was go into the Verizon store and said idk what happened and they called technical support and they asked me if I flashed software on my phone and I just said "no, I just plugged it into my laptop and it did this" so they said they will just send me a new sgs3 and I just got it today.
Pretty simple.
And I don't have insurance .
Hit thanks if I helped
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Funny thing is Verizon can tell if phone was hacked with, and can choose to add the cost of phone to your bill so this method is not highly recommended.
Sent from my SCH-I535 using xda app-developers app

jlyle said:
Funny thing is Verizon can tell if phone was hacked with, and can choose to add the cost of phone to your bill so this method is not highly recommended.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Any break throughs????

dvdavid2 said:
Any break throughs????
Click to expand...
Click to collapse
None that I have seen
Sent from my SCH-I535 using xda app-developers app

jlyle said:
Funny thing is Verizon can tell if phone was hacked with, and can choose to add the cost of phone to your bill so this method is not highly recommended.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Not to mention it is basically fraud, and is the main reason Verizon decided to start locking down phones in the first place.
I understand everyone is taking risks when flashing custom, and flashes can go wrong even when you do everything right, but there is VERY little chance of bricking your phone if you take your time and do a bit of research before you hit any buttons. And if you do manage to brick your phone, man up and pay for a new phone or pay for it to be fixed. Otherwise stop treating your $600 piece of technology like a toy.

BattsNotIncld said:
Not to mention it is basically fraud, and is the main reason Verizon decided to start locking down phones in the first place.
I understand everyone is taking risks when flashing custom, and flashes can go wrong even when you do everything right, but there is VERY little chance of bricking your phone if you take your time and do a bit of research before you hit any buttons. And if you do manage to brick your phone, man up and pay for a new phone or pay for it to be fixed. Otherwise stop treating your $600 piece of technology like a toy.
Click to expand...
Click to collapse
The first time I ever rooted, I was worried about bricking. So i read everything I could find relevant.
Why in the world anyone would flash without reading is beyond me. Every single thread in Verizon Galaxy S3 at least mentions, if not totally devoted, to how bad 4.3 is and if you flash something on it you will brick.
I just don't get it.
Sent from my Last Ever Samsung Device.

If you do a battery pull and start back up in download mode (might take a couple of times to get it to work) then use the Verizon software upgrade assistant it should fix it but you will be stuck with 4.3. Worked for me