Database Users

Bell unlocked GT-I9000M (Galaxy S) hung on startup screen

Dummy me, I was trying to root the KG3 (2.3.3) firmware and made a mistake and messed up my phone. Now it just hangs on the startup animation. I can still get into download mode, so my question is, how do I get it back up and running.
Directions with Odin (I presume) and a stock Bell KG3 firmware????
Any help would be appreciated.

Instructions and firmware are here
http://forum.xda-developers.com/showthread.php?t=1102881
Sent from my GT-I9000 using xda premium

Found that just a few minutes ago, thanks. Phone is now up and running, albeit, I'm gonna need to remove some apps as they're FC'ing. Luckily I have a backup (not that recent, but it'll do) of my contacts.
Since I'm here, I wonder if I shouldn't just throw the latest and greatest on it. Hints???

You know your phone is pretty much an I9000 with an m on the end. If you want to use the latest JVU then go for it. It's as simple as using only the jvu pda file and using the 2.3.3 ugkg3 phone and csc files... Flash same way in odin. Then flash chainfire to get root.
Sent from my GT-I9000 using xda premium

This is what I'm using with kg3 modem and csc. http://forum.xda-developers.com/showthread.php?t=1391207. Rooted with semaphore kernel... Find it in development...I'm also using DMore rom but sadly it is unavailable now.
Sent from my GT-I9000 using xda premium

JVU is most recent this thread also has a link to a root kernel. http://forum.xda-developers.com/showthread.php?t=1431596
Sent from my GT-I9000 using xda premium

Thanks, I appreciate the guidance.
I managed to load JVZ on the phone successfully and have rooted it with the corresponding Semaphore.

Cruisin1966 said:
Found that just a few minutes ago, thanks. Phone is now up and running, albeit, I'm gonna need to remove some apps as they're FC'ing. Luckily I have a backup (not that recent, but it'll do) of my contacts.
Since I'm here, I wonder if I shouldn't just throw the latest and greatest on it. Hints???
Click to expand...
Click to collapse
I have the same phone. The build date was july 2011 as the screen on my first one (build date july 10) cracked completely.
With both phones, i've been doing custom roms on it since i received it back from bell in january 2011 (due to the froyo upgrade issue).
I would definitely suggest Team icssgs (Ice Cream Sandwich 4.03). Been running it now for 5 days and really really enjoying the phone more. But that's me .. i was using DarkyROM JVU previously and had freezes when i tried to use the video camera, and trying to view my contacts.
Good luck in your decision...

ordio said:
. . . I would definitely suggest Team icssgs (Ice Cream Sandwich 4.03) . . .
Click to expand...
Click to collapse
Can you direct me to the list of steps to get this on my phone????

XXLS1 JB leak and eMMC "brickbug" safety

I was going to put this in the JB thread, but that has apparently been locked due to flaming.
As mentioned in other threads on the eMMC "brickbug", Samsung's official patch for this issue is NOT to remove MMC_CAP_ERASE, but to only disable secure erase in the kernel.
See: https://patchwork.kernel.org/patch/1383661/
Now, we've been highly disappointed that Samsung hasn't included this patch in many updates for a variety of devices. However, on analyzing the kernel, it appears it *might* be safe due to having Samsung's official patch.
If you unpack the kernel, and then run "strings" on the unpacked image, you will see the following:
Code:
M8G2FA
MAG4FA
MBG8FA
MCGAFA
VAL00M
VYL00M
KYL00M
VZL00M
e.g. the exact list from the above patch, in the correct order.
So it looks like the XXLS1 JB leak is *probably* safe from the Brickbug - unless Samsung is wrong about nonsecure erase being safe.

+1
Good news for Note Community

I agree..... thanks for taking the time to share your findings with us.
:good:

Good to see some improvements from Samsung! Thanks a lot Entropy.. without your precious help this wouldn't be possible

Many thanks Entropy..
So now we can do full wipe without any fear...??
Sent from my GT-N7000 using xda app-developers app

Brilliant..thanks mate!
Sent from my GT-N7000 using xda premium

thanks for the update.
Its great to see people like you care for the rest

Entropy512 said:
I was going to put this in the JB thread, but that has apparently been locked due to flaming.
As mentioned in other threads on the eMMC "brickbug", Samsung's official patch for this issue is NOT to remove MMC_CAP_ERASE, but to only disable secure erase in the kernel.
See: https://patchwork.kernel.org/patch/1383661/
Now, we've been highly disappointed that Samsung hasn't included this patch in many updates for a variety of devices. However, on analyzing the kernel, it appears it *might* be safe due to having Samsung's official patch.
If you unpack the kernel, and then run "strings" on the unpacked image, you will see the following:
Code:
M8G2FA
MAG4FA
MBG8FA
MCGAFA
VAL00M
VYL00M
KYL00M
VZL00M
e.g. the exact list from the above patch, in the correct order.
So it looks like the XXLS1 JB leak is *probably* safe from the Brickbug - unless Samsung is wrong about nonsecure erase being safe.
Click to expand...
Click to collapse
Well, well.
Samsung finally at last!
Thanks Entropy for the good find.

Lets hope Samsung did a good job !
Now to download that leak.......

I am still wondering about the update. If we have the brick bug in ics how are we able to flash ota jelly bean?? Wont there be chances of bricking while updating our phone to jb.
Sent from my GT-N7000 using xda app-developers app

qazibasit said:
I am still wondering about the update. If we have the brick bug in ics how are we able to flash ota jelly bean?? Wont there be chances of bricking while updating our phone to jb.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
The usual applies... Flashing anything via Odin is safe. Flashing anything from a safe kernel is safe. Flashing something with a "safe" update-binary should be safe even on a dangerous kernel.
I'm not going to guarantee the safety of the XXLS1 kernel, as it's hard to guarantee that it is doing what we think it is, but it is PROBABLY safe as opposed to definitively dangerous like any previous official ICS kernel binary. We won't know unless people take risks unfortunately...

ok using the jb rom i did indeed soft brick has taken 5 hrs to get my note working, i had a custom rooted 404 rom on with hydracore install the jb with cwm and that was it stuck on samsung logo ,so i then tried to flash stock 404 with pc odin and was stuck on flashing fs image,finally got it working with the pit method and by updating bootloader and clear efs, this has kinda scared me as after a cple hrs trying that it would be sent to repair
be aware this worked for me it may not for anyone else

[/COLOR]
anubis1126 said:
ok using the jb rom i did indeed soft brick has taken 5 hrs to get my note working, i had a custom rooted 404 rom on with hydracore install the jb with cwm and that was it stuck on samsung logo ,so i then tried to flash stock 404 with pc odin and was stuck on flashing fs image,finally got it working with the pit method and by updating bootloader and clear efs, this has kinda scared me as after a cple hrs trying that it would be sent to repair
be aware this worked for me it may not for anyone else
Click to expand...
Click to collapse
I was going to write a sarcastic post but... that sucks
This means the Samsung work around did not work.
Either that or you might have repartitioned for no reason.
Did you try a nandroid restore first?

anubis1126 said:
ok using the jb rom i did indeed soft brick has taken 5 hrs to get my note working, i had a custom rooted 404 rom on with hydracore install the jb with cwm and that was it stuck on samsung logo ,so i then tried to flash stock 404 with pc odin and was stuck on flashing factoryfs....
Click to expand...
Click to collapse
So you bricked bricked flashing on Hydracore? I thought that was safe!

shoey63 said:
So you bricked bricked flashing on Hydracore? I thought that was safe!
Click to expand...
Click to collapse
He already flashed the jb leak, overwriting hc with its own kernel in the process. Flashing back to 4.0.4 on the leaked rom caused the soft brick, NOT hc.
Sent from my Asylumized shopping cart.

randomtext said:
He already flashed the jb leak, overwriting hc with its own kernel in the process. Flashing back to 4.0.4 on the leaked rom caused the soft brick, NOT hc.
Sent from my Asylumized shopping cart.
Click to expand...
Click to collapse
He used PC Odin to "flash back". I thought that was safe too!
Anyway odin stuck on factoryfs and needing PIT file method to revive Note is SUPERBRICK, not "softbrick"

Entropy512 said:
The usual applies... Flashing anything via Odin is safe. Flashing anything from a safe kernel is safe. Flashing something with a "safe" update-binary should be safe even on a dangerous kernel.
I'm not going to guarantee the safety of the XXLS1 kernel, as it's hard to guarantee that it is doing what we think it is, but it is PROBABLY safe as opposed to definitively dangerous like any previous official ICS kernel binary. We won't know unless people take risks unfortunately...
Click to expand...
Click to collapse
I've tried it a dozen times and seems to be ok
Ran the check and lost no memory at al
Thanks would be nice for my daring? Stupidity ? Did full wipes etc
Sent from my GT-N7000 using Tapatalk 2

howard bamber said:
I've tried it a dozen times and seems to be ok
Ran the check and lost no memory at al
Thanks would be nice for my daring? Stupidity ? Did full wipes etc
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Actually it's the same as wiping on stock ICS recovery. Well done for trying to verify :thumbup:

what can i say i am a flashaholic flash at least once a week trying varied roms themes etc this time it just happened to me
redone pit file and gained a bit more space

anubis1126 said:
what can i say i am a flashaholic flash at least once a week trying varied roms themes etc this time it just happened to me
redone pit file and gained a bit more space
Click to expand...
Click to collapse
Happened to me too useing stupid Cwm.zip - accidentally hit factory reset and BANG! Superbrick! Thankfully grey retailer replaced it.:thumbup:
Sent from my GT-N7000 using xda app-developers app

toasted s3i9300gt

Hi everyone , im sorry to tell but from begining i had problems with my s3 , i had a error and the battery was consumed very fast on standby then i rooted , installed other kernels roms etc , for nothing , i had an onscreen time of maximum 2.5 hours with everything shutted down gps sync geo localization setting all ...
Now i had installed original jelly bean flashed with odin and syah kernel the latest version from 1 month ago dont know exactly if something new came up.
My problem is that somehow when the phone was charging i was sending some emails and i felt a burned smell , i checked and the place in wich comes the plug into the phone was like toasted, from then i couldnt charge the phone no more and i cant put back the jelly bean using odin no more ...
The question is how do i put the original rom from tmobile germany back into my phone without odin , just with recovery mod ?
i coulndt find nothing on internet regarding this , just using odin , because when i try to start the phone i just pop the image with syah kernel and the guys from waranty will see this and my phone will be sended back as defect as i send it .
please help

Use mobile odin there is free version for xda http://forum.xda-developers.com/showthread.php?t=1347899 and paid on play store it can do all that desktop odin can and even more.

Tenacius D said:
Use mobile odin there is free version for xda http://forum.xda-developers.com/showthread.php?t=1347899 and paid on play store it can do all that desktop odin can and even more.
Click to expand...
Click to collapse
quick answer quick solving
thanks alot dude, one more thing if they see that i have still cwm recovery mode installed on the phone will they still make my waranty void ?

Use triangle away first. And then flash stock rom. Stock rom flash will install stock recovery automatically
Sent from my GT-I9300 using xda app-developers app

prabhjots said:
Use triangle away first. And then flash stock rom. Stock rom flash will install stock recovery automatically
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
well dont know how i managed to screw it complete up , it just doesnt want to install a new rom and the triangle pops up on download mode...
i hope they dont see it somehow ...

Sounds like a power surge that fried the charging circuit to me.
Sent from my GT-I9300 using xda premium

2 Notes ( pure stock ) get bricked after malaysia official jelly bean update.

First of all, recently im seldom visit n7000 forum since I has upgraded to n7100. Now my n7000 using by my wife.
Last week malaysia jelly bean firmware has been out. All my friends and colleagues are upgrade thru kies.
Unfortunately something happened. 2 of my colleagues called me for sos at the same day. ( the 2nd day after upgraded). Both told me stucked at note logo. They both passed the devices for me and check whats the problem.
1st devices.
- completely stock and ugraded to official jelly bean firmware thru kies.
- failed to boot into recovery mode. Download mode ok.
- use odin flash stock ginger rom but failed at nand write start.
- sent to ssc and get mobo free replacement within 3 hours. ( under warranty.
2nd devices.
- completely stock and ugraded to official jelly bean firmware thru kies.
- totally no respond, unable to boot in any mode even using what kind of method, pull out battery and using spare battery.
-sent to ssc, get replied from ssc within 1 hour and need replace mobo with all cost rm740.50.
Both of my frends told that they did NOTHING. But the devices automatically get turn off and another keep restart and stucked.
As my knowledge, this syndrome can be consider as sds, which great different as n7000 brick bug.
Im really wonder why this will happen. Is this related to jelly bean firmware which caused the sds occured?
Sent from my GT-N7100 using xda premium

Brought to you by the world's largest Android phone manufacturer, Samsung.

Im afraid what happen to both phone is what we called 'bootloop bug' on JB.. Stuck on N7000 logo and not going to Samsung animation.... happen when you pull out the bettery without properly power off the phone or when you make a force Reboot.. Its sucks when happened to average user, my phone also infected by bootloop bug...solved by flashing Philz kernel, Speedmod kernel or TWRP kernel by Ficeto...
Sent from my GT-N7000 using Tapatalk HD

zai89 said:
Im afraid what happen to both phone is what we called 'bootloop bug' on JB.. Stuck on N7000 logo and not going to Samsung animation.... happen when you pull out the bettery without properly power off the phone or when you make a force Reboot.. Its sucks when happened to average user, my phone also infected by bootloop bug...solved by flashing Philz kernel, Speedmod kernel or TWRP kernel by Ficeto...
Sent from my GT-N7000 using Tapatalk HD
Click to expand...
Click to collapse
Thanks for reply. I know about the bootloop bug. My n7000 previously also having the same bootloop issue before fixed method out. But now the case was different. Is refuse to boot in recovery mode. ( my both fren completely in stock recovery). And one of the affected devices was totally unable to manually boot into any mode..no download mode and no recovery mode.
And both devices confirmed by ssc was need to replace mobo.
Worst to worst ssc only give 1month warranty for the new mobo replacement.
Sent from my GT-N7100 using xda premium

Well my best advice that root your phone and change the kernel to a safe one like philz if you are using jb.
Sent from my GT-N7000 using xda premium

Just a question what's the RM? Thanks.
Sent from my GT-N7000 using xda premium

TheNoticer said:
Just a question what's the RM? Thanks.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Ringgit Malaysia...Malaysian currency

I recently upgraded to JB using PC Odin and while fiddling around, got locked at boot screen. It no longer went to recovery mode but luckily was able to boot to download mode and I flashed Philz's kernel using PC Odin. Got phone working but with yellow triangle. Chainfire's remove triangle did not run in JB. So switched back to GB, removed triangle and back to JB with Philz's kernel ready in sd card to flash ASAP. So far so good.

NEED HELP!!

Ive been having some issues with my note 3 sm-n9005. out of no where the phone started spazing out meaning it overheats aps randomly close i cant download any apps from the play store(always getting this error 960 or it says package file invalid) and the phone sometimes restart it self so right now i have no use of the phone. I've tried rooting it and trying some custom roms like cm i tried the bobcat rom but that did working and i used the omega rom all of them did the same thing. I'm not sure if the note has some bad flies that causing it to do what its ding so i would really like it if somebody could have me. I live in the Bahamas so i don't have the luxury of sending the phone back I'm not even sure if the phone can be fix im sure its a software problem i just don't know now how to fix it. and right now i had it on a stock rom and i tried rooting it again and now it would up then restart and then go into recovery mode. i rooted it usinf clockwork mod. SOMEBODY HELP ME PLZ!!:crying:

rashadblack242 said:
Ive been having some issues with my note 3 sm-n9005. out of no where the phone started spazing out meaning it overheats aps randomly close i cant download any apps from the play store(always getting this error 960 or it says package file invalid) and the phone sometimes restart it self so right now i have no use of the phone. I've tried rooting it and trying some custom roms like cm i tried the bobcat rom but that did working and i used the omega rom all of them did the same thing. I'm not sure if the note has some bad flies that causing it to do what its ding so i would really like it if somebody could have me. I live in the Bahamas so i don't have the luxury of sending the phone back I'm not even sure if the phone can be fix im sure its a software problem i just don't know now how to fix it. and right now i had it on a stock rom and i tried rooting it again and now it would up then restart and then go into recovery mode. i rooted it usinf clockwork mod. SOMEBODY HELP ME PLZ!!:crying:
Click to expand...
Click to collapse
my suggestions?
flash a stock ROM, and do a clean up (factory reset & clear cache) from stock recovery. This is the simple way.
my guess (if I'm wrong, correct me), you come back from CM/AOSP to TW, and it start to be like this.

Well im not sure if I had rooted it properly but I did all that I downloaded the stock hk rom to try see if thag will get it from booting in recover I know thats the easy fix. My big issue are all the other problems I had before I even tried to root the phone
Sent from my GT-I9300 using XDA Free mobile app

rashadblack242 said:
Well im not sure if I had rooted it properly but I did all that I downloaded the stock hk rom to try see if thag will get it from booting in recover I know thats the easy fix. My big issue are all the other problems I had before I even tried to root the phone
Sent from my GT-I9300 using XDA Free mobile app
Click to expand...
Click to collapse
stock HK firmware ?
Is your device is N9005 HK/Taiwan version ?
if not, you can't just use the HK/Taiwan firmware onto your N9005.

Its the sm-n9005 the international model
Sent from my GT-I9300 using XDA Free mobile app

rashadblack242 said:
Its the sm-n9005 the international model
Sent from my GT-I9300 using XDA Free mobile app
Click to expand...
Click to collapse
if yours is the international model of 32GB N9005, it is strongly suggested not to flash HK/Taiwan firmware.
This 2 firmware is basically only for HK/TW N9005, which is earlier was came in 16GB. Means the partition is different from the 32GB.
after that, they come up with 32GB, but... I might be wrong (correct me if I do), I read somewhere the partitioning also different.
So, Why don't u flash other international firmware ?
Have you tried other than HK/Taiwan firmware ?

I believe so as well. Regardless either 16 or 32gb HK fw doesn't play well with other regions n9005
Sent from my SM-N9005 using Tapatalk

Well what region do you suggest I flash on it?
Sent from my GT-I9300 using XDA Free mobile app

I haven't has yet. I downloaded a UK rom thats about it I dont know what else to try
Sent from my GT-I9300 using XDA Free mobile app

UK rom should be fine
Sent from my SM-N9005 using Tapatalk

Ok so do you have any other idea how to fix the other issues I described because flashing a new rom wont slove it.
Sent from my GT-I9300 using XDA Free mobile app

rashadblack242 said:
Ok so do you have any other idea how to fix the other issues I described because flashing a new rom wont slove it.
Sent from my GT-I9300 using XDA Free mobile app
Click to expand...
Click to collapse
If you haven't flash stock rom then just flash it first to see if the issue persists. Factory reset and wipe cache from stock recovery after done odin flashing.
If issues persist, root you phone again, install custom recovery sych as TWRP, use DrKetan's imei backup tool here
http://forum.xda-developers.com/showthread.php?t=2698639,
make a nandroid backup if your current rom, wipe system/data/cache(don't wipe internal or external storage if you save your nandroid backup and imei backup in any of them else you will lost it. You will never know when they would be handy if you lost your imei in any way). Then flash again stock with odin.
My friend's note3 has terrible lag after upgrade to KitKat. It took a few minutes after reboot just to get unlocked so I helped him to reflash using odin but after 3 different firmwares flashed still not get resolved. I did the same. No more issue after that.
Sent from my SM-N9005 using Tapatalk