Database Info

Brickbug in Laymans terms

Hi guys, I recently downloaded the app from this XDA user that verifies if you're in danger of bricking your device.
Apparently I am, the app says 'this is a chip with KNOWN issues'. I don't really understand what causes the issue, if I'm actually in danger or I just shouldn't do XYZ. Would anyone with more knowledge please take the time to explain as best they can what the situation is?
I'm running AOKP with UCLE2, and it seems plenty of people are sticking with ICS roms so it doesn't seem to be that heavy a situation.

I'm pretty sure the brickbug is only caused from recoveries that use ICS kernels. Currently the skyrocket doesnt have any recovery available that has an ICS kernel so I'm pretty sure were in the green.

BaconStep said:
I'm pretty sure the brickbug is only caused from recoveries that use ICS kernels. Currently the skyrocket doesnt have any recovery available that has an ICS kernel so I'm pretty sure were in the green.
Click to expand...
Click to collapse
Thank you, from what I was reading it had to do with a method of erasing that corrupted the eMMc, but I honestly didn't understand anything more than that and from the thread here it basically said 'if you flash a ROM, it may be your last'.
There was a lot of technical talk that I didn't quite follow.
And I am aware this isn't Q/A forum, but a possible hard brick I thought deserved more light.

whosgotlag said:
Thank you, from what I was reading it had to do with a method of erasing that corrupted the eMMc, but I honestly didn't understand anything more than that and from the thread here it basically said 'if you flash a ROM, it may be your last'.
There was a lot of technical talk that I didn't quite follow.
And I am aware this isn't Q/A forum, but a possible hard brick I thought deserved more light.
Click to expand...
Click to collapse
yes and no, but its not by flashing rom with cwm read this http://forum.xda-developers.com/showthread.php?t=1621679

whosgotlag said:
Thank you, from what I was reading it had to do with a method of erasing that corrupted the eMMc, but I honestly didn't understand anything more than that and from the thread here it basically said 'if you flash a ROM, it may be your last'.
There was a lot of technical talk that I didn't quite follow.
And I am aware this isn't Q/A forum, but a possible hard brick I thought deserved more light.
Click to expand...
Click to collapse
I might not be %100 on the money but I remember something with ics leaks and recoveries cause super bricks.
Sent from my SAMSUNG-SGH-I727 using xda premium

It's not flashing a ROM that causes bricks. It's using the wipe functions with ics kernels. Aka, if you're on ics and you have one of the chips in question, and you perform wipe functions in cwm you have a good chance of bricking at some point. Maybe not next time, maybe not in the next 30 wipes, but it will most likely happen at some point according to what's been happening with other users of the chips.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

My understanding is that if you use a gingerbread based cwm (which is any of the cwm versions posted on XDA) to wipe that you "should" be safe. It's when you use Factory Data Reset while on ics using the gui that you risk getting the bug. (ie DO NOT go into Settings/Backup and Reset/Factory Data Reset).
EDIT: Also do not go into stock 3e recovery to wipe data after flashing the one-click leaks. I'm assuming that recovery was based on an ics kernel, but I could be wrong about that. But to be safe, DON'T!
This post explains that it is because the Skyrocket and t989 have separate recovery and kernel partitions: http://forum.xda-developers.com/showpost.php?p=27140915&postcount=122

I'm not completely sure now as there seems to be two differing takes on the situation. I am on AOKPs latest R4INS linaro build, using the 5.8.somethingsomething recovery from here. I've been told it's a Gingerbread Recovery. But I don't know how to actually tell or what the difference is.
If the problem is ICS recovery then I should theoretically be fine. If the problem is ICS builds in general then I'm in danger. And if the problem is ICS kernel then I'm not sure if I'm in danger, I haven't specially flashed a new kernel, but I'm not sure if they are included with the ROM.
I'm sorry for these lines of questions. Still learning the technical aspect.

Its wiping with anything using an ics kernel so either from or recovery none of our recoveries use ics so that leads us to roms atm
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Is this issue expected to persist even once official ICS is released and specifically isolated to rooted devices, or should this be solved once we have the final build?

When I had my gs2 i777 and the bug first showed up it only affected users who flashed the leaked stock ics kernel. Those on custom kernels such as cm9 or aokp were not affected. Also page 7 of the gotbug app post (linked by the op in this thread) has all of the details posted by entropy512 the Dev who discovered the bug.
Sent from my SAMSUNG-SGH-I727 using xda premium

whosgotlag said:
I'm not completely sure now as there seems to be two differing takes on the situation. I am on AOKPs latest R4INS linaro build, using the 5.8.somethingsomething recovery from here. I've been told it's a Gingerbread Recovery. But I don't know how to actually tell or what the difference is.
If the problem is ICS recovery then I should theoretically be fine. If the problem is ICS builds in general then I'm in danger. And if the problem is ICS kernel then I'm not sure if I'm in danger, I haven't specially flashed a new kernel, but I'm not sure if they are included with the ROM.
I'm sorry for these lines of questions. Still learning the technical aspect.
Click to expand...
Click to collapse
If you are on an ics ROM, you would be on an ics kernel. Therefore you would have a chance of bricking if you wipe.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

xcrazydx said:
If you are on an ics ROM, you would be on an ics kernel. Therefore you would have a chance of bricking if you wipe.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
But doesn't recovery not use the same kernel as the ROM uses?

Well I'm on the leak but I'm not gonna take the chance and wipe anything. If I really needed to do a wipe or a factory reset I would just fire Odin up and flash back stock and then do a wipe. But from what I've read if I understand it right and correct me if I'm wrong it only happens when you wipe or reset using either cwm or GUI and select to format SD. If I understand it right as long as you don't format the SD when wiping or factory data reset you should be OK. So please someone if I've misunderstood please correct me... as I said if I need to wipe or reset I'll flash back to stock and do it.. your gonna lose your data either way so might as well not take the chance...
Sent from my SAMSUNG-SGH-I727 using xda premium

garydv2002 said:
Well I'm on the leak but I'm not gonna take the chance and wipe anything. If I really needed to do a wipe or a factory reset I would just fire Odin up and flash back stock and then do a wipe. But from what I've read if I understand it right and correct me if I'm wrong it only happens when you wipe or reset using either cwm or GUI and select to format SD. If I understand it right as long as you don't format the SD when wiping or factory data reset you should be OK. So please someone if I've misunderstood please correct me... as I said if I need to wipe or reset I'll flash back to stock and do it.. your gonna lose your data either way so might as well not take the chance...
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
as of now, all cwm recoveries on this i727 forum r based in gb, even if u flashed a rom based on the ics, cwm is never part of the rom as it is flashed seperatly, the only time that would happen is when u odin a stock firmware

garydv2002 said:
Well I'm on the leak but I'm not gonna take the chance and wipe anything. If I really needed to do a wipe or a factory reset I would just fire Odin up and flash back stock and then do a wipe. But from what I've read if I understand it right and correct me if I'm wrong it only happens when you wipe or reset using either cwm or GUI and select to format SD. If I understand it right as long as you don't format the SD when wiping or factory data reset you should be OK. So please someone if I've misunderstood please correct me... as I said if I need to wipe or reset I'll flash back to stock and do it.. your gonna lose your data either way so might as well not take the chance...
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Do not wipe anything on ics atm in GUI cwm is your friend
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

skrambled said:
My understanding is that if you use a gingerbread based cwm (which is any of the cwm versions posted on XDA) to wipe that you "should" be safe. It's when you use Factory Data Reset while on ics using the gui that you risk getting the bug. (ie DO NOT go into Settings/Backup and Reset/Factory Data Reset).
EDIT: Also do not go into stock 3e recovery to wipe data after flashing the one-click leaks. I'm assuming that recovery was based on an ics kernel, but I could be wrong about that. But to be safe, DON'T!
This post explains that it is because the Skyrocket and t989 have separate recovery and kernel partitions: http://forum.xda-developers.com/showpost.php?p=27140915&postcount=122
Click to expand...
Click to collapse
This exactly. The stock recoveries are the main dangerous part. Flash off of it before you do anything. While we have the same problem with the chip, it seems we're not likely to encounter it if you don't use the format operations while on the ics kernels. The 4 current modded recoveries we have are all based on gingerbread. (well 3 are, and the fourth is believed to be unless he has his own leaks)

nrm5110 said:
Do not wipe anything on ics atm in GUI cwm is your friend
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
The bottom line is all wiping (for sd/usb cards too) should be done with a gb cwm if you're using an ics based rom. Correct?
Sorry to beat a dead horse but the amount of information and disinformation out there is staggering...

Locoman_ said:
The bottom line is all wiping (for sd/usb cards too) should be done with a gb cwm if you're using an ics based rom. Correct?
Sorry to beat a dead horse but the amount of information and disinformation out there is staggering...
Click to expand...
Click to collapse
Agreed. I've looked at MANY threads and everyone seems to have a different idea of what causes the brick and what steps to take to avoid it. I've read cwm wiping can cause the brick but here it says cwm is safe. Its hard to know what to think
Sent from my soon to be rooted I727

Mike on XDA said:
Agreed. I've looked at MANY threads and everyone seems to have a different idea of what causes the brick and what steps to take to avoid it. I've read cwm wiping can cause the brick but here it says cwm is safe. Its hard to know what to think
Sent from my soon to be rooted I727
Click to expand...
Click to collapse
My understanding is that when on an ICS based rom wiping with a GB based recovery IS ok. Wiping with an ICS based recovery is NOT ok. Using the ICS gui to wipe is NOT ok.
Would love to have this confirmed.

Want to root but....

Hi,
So basically I got a Verizon galaxy s3 running stock 4.0.4 and updated to the latest software from Samsung and Verizon. I've been told to root and am a bit skeptical. Is a hard brick a realistic possibility and what other problems can I possibly encounter. I don't want to break this $800 device but I want to enjoy it to its fullest. I want to run a rom that just gives me stock jelly bean with no touchwiz or anything with good performance and battery life. Can someone please reply to these questions with some answers and possibly tell me the steps necessary to get this to work for me if it is not a risky process. Maybe refer to some videos or other posts? Also do I need to check other compatibilities like kernel version etc?
Any help is GREATLY APPRECIATED.
Sent from my SCH-I535 using xda app-developers app

Just look in dev section under how to root.
Or youtube root vzw gs3
Ive rooted and unrooted twice with no issues
The devs make it so easy if u just follow the steps
https://www.youtube.com/watch?v=cuiJYKV2GGU&feature=youtube_gdata_player
Sent from my SCH-I535 using Tapatalk 2

Tumblr said:
Hi,
So basically I got a Verizon galaxy s3 running stock 4.0.4 and updated to the latest software from Samsung and Verizon. I've been told to root and am a bit skeptical. Is a hard brick a realistic possibility and what other problems can I possibly encounter. I don't want to break this $800 device but I want to enjoy it to its fullest. I want to run a rom that just gives me stock jelly bean with no touchwiz or anything with good performance and battery life. Can someone please reply to these questions with some answers and possibly tell me the steps necessary to get this to work for me if it is not a risky process. Maybe refer to some videos or other posts? Also do I need to check other compatibilities like kernel version etc?
Any help is GREATLY APPRECIATED.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
No one is going to tell you you can't break your phone, because you can. And the only one who is going to be responsible for it is you. That said, the way the S3 is designed, with (someone please correct me if I'm wrong) a separate space for the recovery partition (unlike my old DX), it isn't likely. After you root and install cwm, you can always re-flash with recovery, or if things really go sideways, cable it to the PC and use the same method you use for Root66 - ODIN. As for "how dangerous is it?", well, obviously everyone on the forum has done it, or is about to, so....
Search for Root66 Verizon That is where you will get started.
Then after root66, run the ez bootloader unlock app if you want to rom it. Oh, and back up your imei before you start flashing roms.

Perhaps I am overly cautious, but I've not yet seen a pattern to the lost IMEI condition after ROMming, so only have rooted (and then unrooted) when I need that level of access to perform certain functions - such as using Titanium Backup or changing file permissions, etc.
These methods of rooting and unrooting have been very quick and pain-free for me.
I have decided to put off a custom recovery and custom ROMs until the lost IMEI conditions have been identified. The bricking possibilities are less a concern, because I've always been careful about customizing my Android phones.
- ooofest

ooofest said:
Perhaps I am overly cautious, but I've not yet seen a pattern to the lost IMEI condition after ROMming, so only have rooted (and then unrooted) when I need that level of access to perform certain functions - such as using Titanium Backup or changing file permissions, etc.
These methods of rooting and unrooting have been very quick and pain-free for me.
I have decided to put off a custom recovery and custom ROMs until the lost IMEI conditions have been identified. The bricking possibilities are less a concern, because I've always been careful about customizing my Android phones.
- ooofest
Click to expand...
Click to collapse
the IMEI backups are stupid easy.

ddurandSGS3 said:
the IMEI backups are stupid easy.
Click to expand...
Click to collapse
Sure, though I've seen mixed results after applying a backup because something went wrong with the IMEI. Owners who can't get out of roaming, etc. Recovery doesn't appear to be fool-proof, but I'm open to more information.
I'd rather find out what is causing those problems in the first place before experiencing the issue and not knowing why.
- ooofest

Also, is a SD card necessary for flashing roms or rooting or can I do it all to the on board storage?
Sent from my SCH-I535 using xda app-developers app

Also, is a SD card necessary for flashing roms or rooting or can I do it all to the on board storage?
Thanks so much
Sent from my SCH-I535 using xda app-developers app

You can do it without an SD card, however I don't think it is a great idea...
You want do a backup before you do anything like flashing, etc.. the backup goes onto your SD card so if you run into issues and have to reset, the flash drive is not affected. I don't think it is the best idea to put your backups onto the internal storage.

ooofest said:
Sure, though I've seen mixed results after applying a backup because something went wrong with the IMEI. Owners who can't get out of roaming, etc. Recovery doesn't appear to be fool-proof, but I'm open to more information.
I'd rather find out what is causing those problems in the first place before experiencing the issue and not knowing why.
- ooofest
Click to expand...
Click to collapse
There appears to currently be no danger with IMEI now. There is nvbackup/nvrestore in terminal, the synergy flashable zip, and several manual recovery tools even if you didn't make a backup - including a fix for roaming.

Beemer533 said:
You can do it without an SD card, however I don't think it is a great idea...
.
Click to expand...
Click to collapse
I do all my CWM backups to the internal storage as my 64 gig card is not FAT32.
I have backed up & restored perfectly fine from the internal storage.
I left my card at the default file system as I don't want to be limited to a 4 gig file size. I do copy the backups to my PC weekly however.....

jmorton10 said:
I do all my CWM backups to the internal storage as my 64 gig card is not FAT32.
I have backed up & restored perfectly fine from the internal storage.
I left my card at the default file system as I don't want to be limited to a 4 gig file size. I do copy the backups to my PC weekly however.....
Click to expand...
Click to collapse
This is true.. I wasn't thinking about that. But when I said i didn't think it was a good idea, I didn't mean that because it wouldn't work; only that if your backup was on the internal storage and you had to do a wipe your backup would be gone.
Of course if you are backing up to a PC, then so much the better!

it will be ok
Tumblr said:
Hi,
So basically I got a Verizon galaxy s3 running stock 4.0.4 and updated to the latest software from Samsung and Verizon. I've been told to root and am a bit skeptical. Is a hard brick a realistic possibility and what other problems can I possibly encounter. I don't want to break this $800 device but I want to enjoy it to its fullest. I want to run a rom that just gives me stock jelly bean with no touchwiz or anything with good performance and battery life. Can someone please reply to these questions with some answers and possibly tell me the steps necessary to get this to work for me if it is not a risky process. Maybe refer to some videos or other posts? Also do I need to check other compatibilities like kernel version etc?
Any help is GREATLY APPRECIATED.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
i was a little scared also but i did it a cpl times already.i thought i bricked my phone so i took it to verizon and got a replacment.come to find out i just had to put it in download mode and flash a stock rom..its easy once u understand a little..i just downloaded a rom [aokp[ jb to my computer u will love this one] then gapps and put them on sd card. i downloaded ez unlock and ez recovery from play store. u also have to install clock work mod thats was the easiest for me. unlock the bootloader first from ez unlock then go into ez recovery and reboot recovery. before u wipe everything go into sd card and make sure the rom and gapps are there.once u see them then wipe data, cache and delvic cache. then flash rom then flash gapps then reboot.BEFORE U WIPE DATA MAKE A BACKUP OF UR STOCK ROM.!!!! SORRY so long .. good luck u will love aokp jb 4.1.1

[Q] Remove a boot problem

I installed a wrong program through CWM and after that there is a yellow watermark on the phone. (attached show the screen).
Pleaaaase help me to fix the phone. I tried many roms but no results.
My tablet is GT-N8000.

Can you provide more information. Like what you flashed how you done it.and what you can and can't do with the tab as it is.Like do you have cwm can you get Odin Joe's to work.
Kies has a emergency recocery try that first if no go try flashing a stock rom with Odin.just guessing with the partial info you provided
Be careful and good luck

erica_renee said:
Can you provide more information. Like what you flashed how you done it.and what you can and can't do with the tab as it is.Like do you have cwm can you get Odin Joe's to work.
Kies has a emergency recocery try that first if no go try flashing a stock rom with Odin.just guessing with the partial info you provided
Be careful and good luck
Click to expand...
Click to collapse
I accidentally installed busybox by CWM but it was designed for galaxy tab 10.1 instead of galaxy note 10.1. Now, the device has some problems like it does not detect the sim cart and so on. I can install new frameworks and I have CWM but nothing happens when I install new framework or wipe the device. Also, I tried a stock rom but .... .
I really need help.
sorry for bad english.

Never would have guessed busybox that is usually pretty generic and doesn't have much to do with nonroot apps would cause issues like what you seem to be experiencing.. crazy stuff but good luck!
If nothing else Odin back to newest stock using the stock Odin package that is usually found among your device "stickied" threads. I don't have a gnote but I have had many galaxy devices and Odin is the cure for all ills
Sent from my Galaxy Nexus using Tapatalk 2

How can I reset the device to first time run state. Like it asked me about personal info and gmail account at start up?
each time I install new framework it begins to the OS without asking about these info.

Could always try to install busybox from the market.. Exactly what zip did you use and where did it come from please I would like to look inside it
Sent from my Galaxy Nexus using Tapatalk 2

wizayne said:
Could always try to install busybox from the market.. Exactly what zip did you use and where did it come from please I would like to look inside it
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Here is the zip file, I tried to install ubuntu and I followed an instruction in youtube but it was for galaxy tab 10.1 instead of galaxy note. I acted like a stupid. I'm totally messed up.
here is the link and file:
mirror20.downloadandroidrom.com/download/GalaxyTab10.1/tools/su_busybox_misc-sam_tab_10.1-061611.zip?token=162686692

stulker said:
Here is the zip file, I tried to install ubuntu and I followed an instruction in youtube but it was for galaxy tab 10.1 instead of galaxy note. I acted like a stupid. I'm totally messed up.
here is the link and file:
mirror20.downloadandroidrom.com/download/GalaxyTab10.1/tools/su_busybox_misc-sam_tab_10.1-061611.zip?token=162686692
Click to expand...
Click to collapse
FLASH STOCK IN ODIN.
Sent from my GT-N7100 using XDA Premium HD app

Mister_Mxyzptlk said:
FLASH STOCK IN ODIN.
Sent from my GT-N7100 using XDA Premium HD app
Click to expand...
Click to collapse
NOT WORKED!!
GOD DAMMIT. I wonder why the device run into the OS and not asked me about my personal info like the first time that I started the phone. can you tell me how to delete all data in the device even the download counter?

stulker said:
NOT WORKED!!
GOD DAMMIT. I wonder why the device run into the OS and not asked me about my personal info like the first time that I started the phone. can you tell me how to delete all data in the device even the download counter?
Click to expand...
Click to collapse
Flash stock in ODIN. Wipe data/factory reset in stock recovery. Reboot. Enjoy.
Check Triangle Away thread for flash counter. You didn't do your homework. You should learn how to recover your device BEFORE you frak it up. Good luck.
Sent from my GT-N7100 using XDA Premium HD app

There is point when I start in system recovery it shows:
E: failed to mount /efs (Invalid argument)
is it ok?
also the yellow hint in the screen that I showed in the first comment indicates a software error.

Mister_Mxyzptlk said:
Flash stock in ODIN. Wipe data/factory reset in stock recovery. Reboot. Enjoy.
Check Triangle Away thread for flash counter. You didn't do your homework. You should learn how to recover your device BEFORE you frak it up. Good luck.
Sent from my GT-N7100 using XDA Premium HD app
Click to expand...
Click to collapse
I think language barrier is keeping open from understanding
OK go here follow instructions for flashing Tom with Odin.download stock rom. You do not have to flash cwm flash stock rom instead boot your tablet
Never flash your device or install software until you know how to revert back
I do not recommend new to android people to tinker with this device. Stay stock for now
http://forum.xda-developers.com/showthread.php?t=1831152
Off topic hi Mister prp area here. I love Louisville

erica_renee said:
I think language barrier is keeping open from understanding
OK go here follow instructions for flashing Tom with Odin.download stock rom. You do not have to flash cwm flash stock rom instead boot your tablet
Never flash your device or install software until you know how to revert back
I do not recommend new to android people to tinker with this device. Stay stock for now
http://forum.xda-developers.com/showthread.php?t=1831152
Off topic hi Mister prp area here. I love Louisville
Click to expand...
Click to collapse
Thank you for your help. But I think I have a different problem. I flashed stock rom (several big roms about 1GB) but nothing happened. When I try to wipe data/factory reset it shows E; failed to mount /efs (Invalid argument). I think I need to mount /efs and format it.

I think I missed some files in the efs folder. the phone status shows that some basic info are missed from the phone. check the attached.

Qhsusb_dload

I am not trying to place blame on anyone here I only want others to be aware of this. I know of one other guy who bricked his in the 4.2 AOKP Unofficial thread. I am not sure what this guy did.
This is exactly what I did.
Coming from the UCLL3 DeOdexed I rebooted to CWM v6.0.2.7.
Wiped and or formatted cache/system/data/dalvik accordingly.
Flashed the ROM (after previously checking MD5SUM), it seemed to go okay.
Flashed SuperSU v1.04 (MD5SUM checked and used before)
Flashed 12/20/2012 GApps (MD5SUM checked and I had flashed on two other JB CM ROMs), looking back I should have known right then something was wrong because it seemed to take longer than it should have.
Flashed JustunBean’s Aroma (themes only and had flashed that on at least two other ROMs)
Tried to flash MrMad’s TW Add on v1.3.3 (which I used on two other CM10.1 ROMs)
That is where things went bad. CWM came back saying something to the effect of “some errors cannot be overlooked” I said “WHAT”? I tried to flash it again with the same error.
I then tried to reboot system. No signs of life. No Samsung Logo.
After pulling battery and trying to boot again I pulled the battery again then hooked it up to pc. That is where I got windows needs to install drivers for your device “DHSUSB_DLOAD”.
I am looking into getting it fixed at MobileTechVideos.
Like I said not blaming anyone just letting people know that it can happen. This may be my first post and I am no Pro or a Dev but I have been flashing on the Skyrocket for almost two years to the day. I admit I am a Flash-Aholic.
Clarification. Nearly two years to the day plus or minus six or seven months

I've seen this error on other devices and it happens when some one flashes a international ROM on a north american phone. I'm not say that's what u did. only way to fix is jaytag. you wrote over the partition that communicates with the CPU.

It also happened to me when I flashed the AOKP 4.2 couple days ago and my phone just replaced by AT&T under warranty. Below is what I learned might result in this:
-Wipe internal SDcard in recovery
-Flash ROM at low battery level (was about 40%)

ka724ka said:
It also happened to me when I flashed the AOKP 4.2 couple days ago and my phone just replaced by AT&T under warranty. Below is what I learned might result in this:
-Wipe internal SDcard in recovery
-Flash ROM at low battery level (was about 40%)
Click to expand...
Click to collapse
that wouldnt do it, but since you and op flashed aokp4.2 could be something within the rom that did it or internal ram failure, or it could be user error

xstokerx said:
I've seen this error on other devices and it happens when some one flashes a international ROM on a north american phone. I'm not say that's what u did. only way to fix is jaytag. you wrote over the partition that communicates with the CPU.
Click to expand...
Click to collapse
It was the ROM for the skyrocket out of the Skyrocket thread. Thanks for the info though.
[/QUOTE] ka724ka It also happened to me when I flashed the AOKP 4.2 couple days ago and my phone just replaced by AT&T under warranty. Below is what I learned might result in this:
-Wipe internal SDcard in recovery
-Flash ROM at low battery level (was about 40%)
[/QUOTE]
Thanks for the info. I did not wipe internal SD although I have wiped internal SD many times before and battery was over 90%.
[/QUOTE] vincomthat wouldnt do it, but since you and op flashed aokp4.2 could be something within the rom that did it or internal ram failure, or it could be user error
[/QUOTE]
Thank you for the info. I hope it was not user error I took the same steps and procedures for all the ROM flashes that I have flashed and I have flashed many a ROM. I hope it is not RAM problems because I plan to get it Jtag-ed so my son can use it. The Skyrocket is an awesome phone.

One question. Why would you try to root the phone again after installing aokp zip?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

xstokerx said:
I've seen this error on other devices and it happens when some one flashes a international ROM on a north american phone. I'm not say that's what u did. only way to fix is jaytag. you wrote over the partition that communicates with the CPU.
Click to expand...
Click to collapse
holeindalip said:
One question. Why would you try to root the phone again after installing aokp zip?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Some developers use SuperUser and I prefer SuperSu so I flash the SuperSU file that I have.

CodeNameRedNeck said:
Some developers use SuperUser and I prefer SuperSu so I flash the SuperSU file that I have.
Click to expand...
Click to collapse
could u not have just deleted superuser then downloaded supersu from the market?

You could do that or just flash it while you are already there.

why woul you flash the SUperSU when all you have to do is download the app from market and click switch and reinstall superSU doesnt mess with any of the files tha could cause this issue

Well given many others have dl'd installed and successfully used aokp I'm going with user error.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

mtdew said:
Well given many others have dl'd installed and successfully used aokp I'm going with user error.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Yes thank you mtdew. With just about 250 downloads of the 4.2.1 ROM and 60 of the 4.2.2 I would have to agree with that.
I'm sorry that it has happened while trying to use my ROM, it is in no way intentional.
You do however root, flash ROMs at your own risk. Its a chance you take and sometimes things like this do happen.
Thanks
Toyes
Sent from my SGH-I727 using Tapatalk 2

I also recently had experience with qhsusb download but unofficial aokp port and just for future reference jtags are not always the solution; mobiltech repairs was unable to unbrick it through JTAG as the onboard emmc controller was unresponsive and I'm currently waiting for a repair through samsung; it gave me a new respect of the dangers of flashing.

killablack said:
I also recently had experience with qhsusb download but unofficial aokp port and just for future reference jtags are not always the solution; mobiltech repairs was unable to unbrick it through JTAG as the onboard emmc controller was unresponsive and I'm currently waiting for a repair through samsung; it gave me a new respect of the dangers of flashing.
Click to expand...
Click to collapse
Erm.. You should change your user name dude..

[Q] No signal problem, just want to go back to before everything

Today I decided to root my phone, and did so with z4root. Then I installed a rom, using ClockWorkMode recovery, and crystal rom cm10 Jelly Bean. Everything works fine, except I get no cover/connection at all. From what I gathered by googling all day I probably didn't upgrade my old baseband to a new one, thus causing all of this. I get a null IMEI.
The version on my LG P500 was 2.2. I didn't make no backup whatsoever (I know, I know...).
Can I revert all the stuff I did today, returning to a factory state? Or any way to solve this mess?
Please, help.

Filooou said:
Today I decided to root my phone, and did so with z4root. Then I installed a rom, using ClockWorkMode recovery, and crystal rom cm10 Jelly Bean. Everything works fine, except I get no cover/connection at all. From what I gathered by googling all day I probably didn't upgrade my old baseband to a new one, thus causing all of this. I get a null IMEI.
The version on my LG P500 was 2.2. I didn't make no backup whatsoever (I know, I know...).
Can I revert all the stuff I did today, returning to a factory state? Or any way to solve this mess?
Please, help.
Click to expand...
Click to collapse
If you don't have a backup try this one.
http://forum.xda-developers.com/showthread.php?t=1060121
For the firmware look at my last post.
http://forum.xda-developers.com/showpost.php?p=39007064&postcount=7
.
But there are few known issues with KDZ updater i.e. you should never remove your battery when you are in emergency mode. As this can hard brick your phone.
.
Otherwise you can use this.
http://forum.xda-developers.com/showthread.php?t=1816154

Filooou said:
Today I decided to root my phone, and did so with z4root. Then I installed a rom, using ClockWorkMode recovery, and crystal rom cm10 Jelly Bean. Everything works fine, except I get no cover/connection at all. From what I gathered by googling all day I probably didn't upgrade my old baseband to a new one, thus causing all of this. I get a null IMEI.
The version on my LG P500 was 2.2. I didn't make no backup whatsoever (I know, I know...).
Can I revert all the stuff I did today, returning to a factory state? Or any way to solve this mess?
Please, help.
Click to expand...
Click to collapse
Don't do what the person above says, it will brick your phone and you will not be able to use your phone at all. Download lgmdp and flash v20g baseband through it (for files and tutorial search Google), do not interrupt the process. After it has finished, restart your phone and your network signal will come back.
Sent from my LG-P500 using xda app-developers app

Junior Einstein said:
Don't do what the person above says, it will brick your phone and you will not be able to use your phone at all. Download lgmdp and flash v20g baseband through it (for files and tutorial search Google), do not interrupt the process. After it has finished, restart your phone and your network signal will come back.
Sent from my LG-P500 using xda app-developers app
Click to expand...
Click to collapse
Mr. Junior Einstein, read the whole post before you say anything. Stop provoking me to take any step against you.
I already posted a link for lgmdp thread for the convenience of user.

Thank you.
Unfortunately the computer won't recognize my phone when I connect it, if I don't switch mass storage on. Can I follow that procedure anyway? Otherwise how do I fix it?
Thanks.

KDZ should be the absolute last option you try, only if all else has failed and you r ready to accept a chance of a brick . Instead You can just flash the old bb fix http://forum.xda-developers.com/showthread.php?p=39893089. This works for all roms ( makes them compatible with phones whose base band has not been upgraded). Enter recovery, flash rom, reboot then flash old bb fix then reboot. Works flawlessly. You have to flash this after every new rom you try and you can be on old bb for ever. No worries. Hope this helps.
Sent from my LG-P500

Junior Einstein said:
Don't do what the person above says, it will brick your phone and you will not be able to use your phone at all. Download lgmdp and flash v20g baseband through it (for files and tutorial search Google), do not interrupt the process. After it has finished, restart your phone and your network signal will come back.
Sent from my LG-P500 using xda app-developers app
Click to expand...
Click to collapse
KDZ will not brick your phone. If anything, LGMDP is just as likely to brick your phone. It is all about what you do or do not do, as in: do be careful, and do not interrupt the process until it says complete. This is true for BOTH programs.
I've used KDZ more than 20 times and not once have I bricked my phone.

I was able to fix using the old baseband fix here.
Thank you very much for your help!

Filooou said:
I was able to fix using the old baseband fix here.
Thank you very much for your help!
Click to expand...
Click to collapse
Glad to help

sweetnsour said:
KDZ will not brick your phone. If anything, LGMDP is just as likely to brick your phone. It is all about what you do or do not do, as in: do be careful, and do not interrupt the process until it says complete. This is true for BOTH programs.
I've used KDZ more than 20 times and not once have I bricked my phone.
Click to expand...
Click to collapse
I'm sorry to say that you are wrong. When flashing baseband through lgmdp, you have 0% chances of bricking your phone.
Sent from my LG-P500 using xda app-developers app

Junior Einstein said:
I'm sorry to say that you are wrong. When flashing baseband through lgmdp, you have 0% chances of bricking your phone.
Sent from my LG-P500 using xda app-developers app
Click to expand...
Click to collapse
Both have near equal chances of bricking / not bricking. All depends on how much you understand what each tool does, how it works & and what precautions you take.
Blind usage could lead to the grave whereas both are life savers too !!

Junior Einstein said:
I'm sorry to say that you are wrong. When flashing baseband through lgmdp, you have 0% chances of bricking your phone.
Sent from my LG-P500 using xda app-developers app
Click to expand...
Click to collapse
0% chance?:
http://forum.xda-developers.com/showthread.php?t=1513191
Like what pmvyas said, it all depends on the user.