Softbrick caused by LPY - How did you recover your phone?

[M3TALLICA]

There have been few more cases of Superbrick since Chasmodo's and now I'm worried that there would be more of such cases when people start flashing custom LPY ROMs, LPY mods and use Stock and Clockwork recovery functions.

I have created this thread specially for those people to share their methods/experience - when the softbrick happened to them and how they managed to recover their phone (symptoms such as nand write failure, factoryfs failure etc).

So if more of such incidents happen, possible solutions would be at one place.

Please do not troll! Do not post comments such as 'So far so good', 'No problem what so ever'. I have flashed LPY multiple times myself but I'm still not sure.

Do not post solutions if you have not successfully tried it yourself.

Regards.

 

[JamieD81]

fixed my superbrick by sending it back to india to get sent in for new motherboard

 

[M3TALLICA]

fixed my superbrick by sending it back to india to get sent in for new motherboard

Thanks a lot sir.
I successfully returned to GB fourth time (Had used stock recovery many times). Gotta wait till experts find a solution.

 

[JamieD81]

Thanks a lot sir.
I successfully returned to GB fourth time (Had used stock recovery many times). Gotta wait till experts find a solution.

if its a hardbrick super brick, then it will need a motherboard replaced because it would fry your emmc, which there is no recovery unless u send out or replace yourself
*motherboards are as much as the digitizer..

 

[M3TALLICA]

if its a hardbrick super brick, then it will need a motherboard replaced because it would fry your emmc, which there is no recovery unless u send out or replace yourself
*motherboards are as much as the digitizer..

Yeah. But few users said that they got write failure error but were able return to GB successfully.
Some of them used PIT file, others used different kernels.
Perhaps it was 'nearly superbrick'.

 

[wildestpixel]

Yeah. But few users said that they got write failure error but were able return to GB successfully.
Some of them used PIT file, others used different kernels.
Perhaps it was 'nearly superbrick'.

If you could recover it was a softbrick, nothing more. This thread is about hard bricks - for which as stated there's only one answer - mainboard replacement.

 

[JamieD81]

If you could recover it was a softbrick, nothing more. This thread is about hard bricks - for which as stated there's only one answer - mainboard replacement.

+1 perfect reply

 

[M3TALLICA]

Entropy was refering to Epic 4G Touch forum so I searched there and found useful info there. Credit goes to xST4T1K

How to Avoid Brick

-If you are on ICS with an ICS kernel, DO NOT WIPE! this has the potential to brick your device (until source arrives, just have patience)
-Using a bad USB cable to ODIN back to GB from ICS
-Rom Manager
-Touch recovery
-Avoid flashing any custom rom in stock ICS recovery
-Avoid restoring a GB backup when running an ICS leak
-Avoid restoring a ICS backup when running a GB rom
-Always use PC odin to return GB - Do flash custom GB kernel on non-GB rom to flash GB firmware

 

[wildestpixel]

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

So if more of such incidents happen, possible solutions would be at one place.

Please do not troll! Do not post comments such as 'So far so good', 'No problem what so ever'. I have flashed LPY multiple times myself but I'm still not sure.

Do not post solutions if you have not successfully tried it yourself.

Regards.

Your post in itself is tantamount to trolling.

 

[M3TALLICA]

Your post in itself is tantamount to trolling.

If you do not have anything useful to say, better stay away from this thread.
I am not offering you the job.
And you don't seem to have much knowledge than proving
superbrick != softbrick

 

[chasmodo]

You should change the title of your thread. As it was already pointed out,
superbrick can only be cured by MoBo replacement, period.

Everything else is a soft brick.

 

[JamieD81]

You should change the title of your thread. As it was already pointed out,
superbrick can only be cured by MoBo replacement, period.

Everything else is a soft brick.

100% accurate

nothing about superbrick is anything to do with softbricking a device.

 

[M3TALLICA]

Thanks Chas.
People won't contribute but will waste time on what is what and what's not.

 

[tazzix]

I had to use a combination of many things:

- Heimdall to flash CF-Root kernel to get CWM (PC Odin equivalent for Mac, older 1.3.0 because 1.3.2 does not work) introduced the bad yellow triangle but thats better than having a brick

- CWM refused to restore any backup or wipe anything (FREAKED OUT)

- Used CWM to flash Abyss 3.9 (I know 4.2 is recommended but had this on the phone)

- Used Redpill restore my backup

- Booted fine, but unable to remount /system/ as rw, tried a lot but no luck so far, I guess I will not be able to flash again.




Now for details, how did I get the softbrick in the first place:
- Bought and installed Mobile Odin PRO
- Downloaded LPY .tar.md5 and cf-root LPY kernel
- Asked Mobile Odin to flash LPY .tar.md5 without wipe (stock kernel, because most posts on XDA said to do it separately) and wanted to keep my data and apps
- Stuck on Samsung logo

hmmm, no recovery installed
- flash CF-root kernel for CWM, via heimdall
- factory reset (wipe data)
- Yipee boot into marvelous ICS-LPY
- Ooops all my data and apps are in GB
- Backup via CWM current ICS
- Restore GB backup
- nothing, no boot, no recovery, nothing, well download mode was still showing up, so recovered as mentioned above.

 

[eitama]

I had to use a combination of many things:

- Heimdall to flash CF-Root kernel to get CWM (PC Odin equivalent for Mac, older 1.3.0 because 1.3.2 does not work) introduced the bad yellow triangle but thats better than having a brick

- CWM refused to restore any backup or wipe anything (FREAKED OUT)

- Used CWM to flash Abyss 3.9 (I know 4.2 is recommended but had this on the phone)

- Used Redpill restore my backup

- Booted fine, but unable to remount /system/ as rw, tried a lot but no luck so far, I guess I will not be able to flash again.




Now for details, how did I get the softbrick in the first place:
- Bought and installed Mobile Odin PRO
- Downloaded LPY .tar.md5 and cf-root LPY kernel
- Asked Mobile Odin to flash LPY .tar.md5 without wipe (stock kernel, because most posts on XDA said to do it separately) and wanted to keep my data and apps
- Stuck on Samsung logo

hmmm, no recovery installed
- flash CF-root kernel for CWM, via heimdall
- factory reset (wipe data)
- Yipee boot into marvelous ICS-LPY
- Ooops all my data and apps are in GB
- Backup via CWM current ICS
- Restore GB backup
- nothing, no boot, no recovery, nothing, well download mode was still showing up, so recovered as mentioned above.

So in my opinion all you had to do to avoid the damage was flash GB to do your wiping, and never backup/restore. (providing you want to use LPY)

 

[tazzix]

So in my opinion all you had to do to avoid the damage was flash GB to do your wiping, and never backup/restore. (providing you want to use LPY)

I would guess so, and wish I knew that earlier, it was supposed to be able to UPGRADE without wipe, otherwise if I would have gone the standard way of backup, titanium backup, wipe, flash; I would not have goten any damage for sure.

 

[equalness]

For me it has been to Flash a wipe rom.

Skickat från min GT-N7000 via Tapatalk 2

 

[kirkla79]

Installed LPY w/ root via mobileOdin pro without issue, but was having many issues with FC's. I was thinking of doing a full wipe, but decided to see if it was safe considering the issues with the previous leaked ICS roms, checked xda where I saw the warning about LPY.

Decided to go back to GB by flashing AbyssNote kernel 4.2, then restoring backup.

The most recent backup gave me an error, so I went to the back before that. Everything seemed to go fine but on reboot I got stuck at the Samsung logo.

Was able to still get in cwm so I reflashed AbyssNote kernel, then flashed Cassie Xtralite rom, which is the gb rom that I had been on before flashing ICS.

Everything booted up so I went through the procedure to get Cassies rom up and running and everything has been fine since.

Will try ICS again at some point but will wait a little bit longer until things seem more sorted.

 

[bmcsfuze]

I came directly from Rocket v23 and flashed with mobile odin pro with the original instructions of Dr. Ketan from here: http://forum.xda-developers.com/showpost.php?p=25916135&postcount=1840 I could never get passed the "Samsung" logo so flashed directly back to Rocket V22 (23 wouldn't work for some reason) via CWM. After reading that there could be some issue with the CF Root I just reflashed the same way minus the zimage file. I got stuck at the "Samsung" logo this time but tried "Factory Reset" and it worked like a charm. The funny thing was that I didn't lose any data (pics, music, vids, etc.)

 

[Princeomi]

I came directly from Rocket v23 and flashed with mobile odin pro with the original instructions of Dr. Ketan from here: http://forum.xda-developers.com/showpost.php?p=25916135&postcount=1840 I could never get passed the "Samsung" logo so flashed directly back to Rocket V22 (23 wouldn't work for some reason) via CWM. After reading that there could be some issue with the CF Root I just reflashed the same way minus the zimage file. I got stuck at the "Samsung" logo this time but tried "Factory Reset" and it worked like a charm. The funny thing was that I didn't lose any data (pics, music, vids, etc.)

In a Factory Reset you only lose your apps, contacts, gmail settings etc.. i.e. what you have in the system.