Related
Hi all...
First of all, please forgive me if i open an already covered issue, but i am lost in your forum LOL...
To the point. My bootlogo has dissapeared, but boots normally, sound included...
I have restored it two times with different results...
The first time, i saw the stock recovery working for a minute or more. The second one, it took a few seconds, but worked right...
But suddenly, my bootlogo was gone...
Any clues?
BTW, it is rooted with Superoneclick 2.3.3... Could it be...?
Sent from my GT-I9100 using xda premium
worf_1977 said:
Hi all...
First of all, please forgive me if i open an already covered issue, but i am lost in your forum LOL...
To the point. My bootlogo has dissapeared, but boots normally, sound included...
I have restored it two times with different results...
The first time, i saw the stock recovery working for a minute or more. The second one, it took a few seconds, but worked right...
But suddenly, my bootlogo was gone...
Any clues?
BTW, it is rooted with Superoneclick 2.3.3... Could it be...?
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Backup data and factory reset .
jje
try data/fatory wipe ore flash a custom rom ore flash a bootlogo by omega files
Hazerd said:
try data/fatory wipe ore flash a custom rom ore flash a bootlogo by omega files
Click to expand...
Click to collapse
Right... Flash a custom ROM... Great... And if i dind't know exactly how to revert back to my stock ROM?
Sent from my GT-I9100 using xda premium
JJEgan said:
Backup data and factory reset .
jje
Click to expand...
Click to collapse
Factory reset is my first option. I have done it, but as i said in the first post, the second time was different from the second, and i don't want to brick a phone that is less than a week, not even for the ICS ROMS. No way, mate...
Sent from my GT-I9100 using xda premium
worf_1977 said:
Factory reset is my first option. I have done it, but as i said in the first post,
No you said restore so i was unsure of what method . Nandroid restore or factory reset .
the second time was different from the second, and i don't want to brick a phone that is less than a week,
Less than a week old and two factory resets then its a warranty return .
But as warranty is now void you need to remove root and all traces of root and reset the custom rom counter if needed to zero with a usb jig .
By bootlogo what exactly do you mean the Samsung Galaxy logo before the boot animation .
Although either would have been restored to out of the box with a factory reset and you should have lost root at the same time .
It is a i9100 not one of the other variants ???
Alternative is to try and flash a stock Samsung rom via Odin .
jje
Click to expand...
Click to collapse
It is a I9100 plain, vodafone in my country. And yes, i meant the bootanimation, just after the samsung logo, while the chime sounds and the phone vibrates...
Any help i can use?
Sent from my GT-I9100 using xda premium
worf_1977 said:
It is a I9100 plain, vodafone in my country. And yes, i meant the bootanimation, just after the samsung logo, while the chime sounds and the phone vibrates...
Any help i can use?
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Looks like the firmware on the phone both current and what is held in the factory reset restore cache is damaged or the phone has a hardware/memory card problem .
You could source the original Samsung stock boot logo QMG files and try to replace them if phone is rooted using root explorer .
jje
JJEgan said:
Looks like the firmware on the phone both current and what is held in the factory reset restore cache is damaged or the phone has a hardware/memory card problem .
You could source the original Samsung stock boot logo QMG files and try to replace them if phone is rooted using root explorer .
jje
Click to expand...
Click to collapse
And where i can download the .qmg files?
I have isolated the problem with them. I just need thise files...
Thanx
Sent from my GT-I9100 using xda premium
hello,
Im new here
I've been upgrading to ICS from the official update which is N7000DXLP9-----------------------2012 May-----------N7000OLBLP6-----------Indonesia from http://forum.xda-developers.com/showthread.php?t=1424997
it works great, until I see some red frame around and tried to fix it by going to buildprop and editing the buildtype from dev to user (what I found on the internet), but then I found out that mine is already user so I tried changed it to dev and when I restart, the phone stuck on samsung logo,but I am still able to go to recovery mode,the problem is I cant get odin to flash any rom to my note, it always stuck at factoryfs.img. then I installed abys kernell to wipe my factory reset, cache, dalvik, then I started to flash with odin again, with the patched pit file I got from http://forum.xda-developers.com/showthread.php?t=1667886, and the official update from http://forum.xda-developers.com/showthread.php?t=1424997, suddenly it works, and I tried to restore data from CWM ( stupid me)....turns out it got back again on the logo samsung and stuck there and so i tried flashing again and it started to stuck around factoryfs everytime, I tried to use abyss but this time after I wiped everything and used the patched pit file like before, it still stuck, so I found a post from the internet, it was custom ICS, i forgot where i got it but i have the file if you'd like to know, and so i tried, then it leaves me with my counter started to count 1 and still stuck at factoryfs....and I cant even go to recovery mode now, I have tried USB JIG and I succeeded to turn the counter back to zero but still stuck at factoryfs.img and still cant go to recovery mode even through bootloader,..... please help! i love my gnote
finally i got my note back....
but it was by guarantee. ... and still i would like to know how to get out of such stuck.... please help
Sent from my GT-N7000 using xda premium
how did u get it out ??
i m stuck at the same spot now
theunborn said:
finally i got my note back....
but it was by guarantee. ... and still i would like to know how to get out of such stuck.... please help
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Hi Bro m stck at the same position as u so can u please tell me how did u get this fixed ?
Honestly it is all very confusing. Best to stick to a reputable source for flashing and troubleshooting.
There are dangerous guides on the internet not updated to circumnavigate later discovered brick.
Sent from my GT-N7000 using Xparent ICS Tapatalk 2
well guys seems my sgs2 i9100 died on me.
I'm an experienced user so I know what I'm doing, but this time seems it died.
what happened.
flashed new LQ5 sammy rom via odin for a quick test drive, all went smooth and tested all I had to test.
then it was time to flash another rom via odin.
as always before flashing another rom, I boot into fake recovery using cwm 5.8.1.5 and erase all partitions, system,data & cache and then reeboot straight to download mode to reflash the other rom via odin.
well this time, after erasing partitions I reebooted but it just went dead.
I tried about everything, even booting with usb jig into download mode, but it just doesnt work. screen is always black no message no signal no nothing.
what can I try to before RMA this Sucker ?
edit: solved by repair center replacing PBA MAIN
tks in advance,
remorema
remorema said:
well guys seems my sgs2 i9100 died on me.
I'm an experienced user so I know what I'm doing, but this time seems it died.
what happened.
flashed new LQ5 sammy rom via odin for a quick test drive, all went smooth and tested all I had to test.
then it was time to flash another rom via odin.
as always before flashing another rom, I boot into fake recovery using cwm 5.8.1.5 and erase all partitions, system,data & cache and then reeboot straight to download mode to reflash the other rom via odin.
well this time, after erasing partitions I reebooted but it just went dead.
I tried about everything, even booting with usb jig into download mode, but it just doesnt work. screen is always black no message no signal no nothing.
what can I try to before RMA this Sucker ?
tks in advance,
remorema
Click to expand...
Click to collapse
Well nothing, there are only to things that can resurrect this paperweight for you, and my guess is that you have neither of them
1. Fix it using JTAG
2. Change the PCB
So send it off to a repair centre near you mate
Best regards
Sendt fra min GT-I9300 med Tapatalk2
Ratata82 said:
Well nothing, there are only to things that can resurrect this paperweight for you, and my guess is that you have neither of them
1. Fix it using JTAG
2. Change the PCB
So send it off to a repair centre near you mate
Best regards
Sendt fra min GT-I9300 med Tapatalk2
Click to expand...
Click to collapse
I have good soldering skills but For jtag looks like there´s a box needed, and since its still under warranty I guess I'll try to RMA before opening and permanently void my warranty.
Sounds like you hit the eMMC brick. I know this sounds cruel but it gave me the heads up as I was about to flash the new LQ5 ROM. Might think twice about it. Don't mess about with it, just send it off for repair and play dumb.
Sent from my GT-I9100 using Tapatalk 2
themadba said:
Sounds like you hit the eMMC brick. I know this sounds cruel but it gave me the heads up as I was about to flash the new LQ5 ROM. Might think twice about it. Don't mess about with it, just send it off for repair and play dumb.
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
I think it has to do with the fake recovery. once this LQ5 firmware as a new pit file different from the older gingerbread one. and the fake recovery might not be prepared to deal with the partitions the way this new pit repartitoned
If you stay off the recovery, the rom works flawlessly, its my bad habbit of formatting the partitions before flash that screwd me
its nice that I have a usb jig and the counter is zero that way they cannot acuse me of using non official firmware.
Can you explain to me what the “fake" recovery is? Do you mean custom recovery?
Sent from my GT-I9100 using Tapatalk 2
themadba said:
Can you explain to me what the “fake" recovery is? Do you mean custom recovery?
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
this http://www.clockworkmod.com/rommanager
you can boot into stock recovery and from there boot into fake recovery without the need to having a custom recovery installed in your phone.
Interesting. You didn't have ClockworkMod Recovery then? Because ROM Manager and CWMR don't get on together. Just return your phone to Samsung and say the update failed in Kies. It's a 50/50 chance they will fix it. But it's worth a try.
Sent from my GT-I9100 using Tapatalk 2
The same has happened to me after an LQ5 NanDroid backup. Phone is dead, cannot boot, get recovery to start, no Odin, no Jig; nothing. Will it have to be sent for repair peeps?
Sent from my HTC Desire using XDA App
fs1023 said:
The same has happened to me after an LQ5 NanDroid backup. Phone is dead, cannot boot, get recovery to start, no Odin, no Jig; nothing. Will it have to be sent for repair peeps?
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
either that or a jtag box.
Sent from my STM712HCZ using Tapatalk 2
Well if it is the eMMC brick, even a JTAG repair won't save it. A new motherboard is in place. Just send it to Samsung and play stupid
Sent from my GT-I9100 using Tapatalk 2
This is really bad if Samsung enabled MMC_CAP_ERASE in this new kernel, they absolutely should not have done this given the known consequences...
Sent from my GT-N7000 using Tapatalk 2
themadba said:
Well if it is the eMMC brick, even a JTAG repair won't save it. A new motherboard is in place. Just send it to Samsung and play stupid
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
if jtag cant save it does that mean samsung wont be able to confirm what appened to the board?
Sent from my STM712HCZ using Tapatalk 2
remorema said:
if jtag cant save it does that mean samsung wont be able to confirm what appened to the board?
Sent from my STM712HCZ using Tapatalk 2
Click to expand...
Click to collapse
if ur phone is bricked samsung will not knw wat u had done
just act stupid in front of them
i did the same thing when i had bricked by phone
i told them i was updating the phone in kies and after that my phone din start
What build did you die on? Saying "LQ5" is useless - with ICS you MUST include the FULL build identifier including region code when talking about a given build.
Well now I might be little more cautious, but I have wiped multiple times using the dial code and it worked fine.
Might be the touch recovery done something or you!
Have to be sure before everyone gets Bizzurk about the Emmc brick, which we didn't have until now.
Fix it by JTAG / univ on Samsung Centre
Sent from my GT-I9100 using xda premium
neerajganga said:
if ur phone is bricked samsung will not knw wat u had done
just act stupid in front of them
i did the same thing when i had bricked by phone
i told them i was updating the phone in kies and after that my phone din start
Click to expand...
Click to collapse
yep
will do that
Sent from my STM712HCZ using Tapatalk 2
The LQ5 release the OP is talking about is the leaked Samsung release of 4.0.4 for the GS2. Leaked a few days ago by sammobile.com. Is there any way to tell if the MMC_CAP_ERASE is still present in Samsung's new kernel? Or that is is at least equal to 0?
Sent from my GT-I9100 using Tapatalk 2
Mobile Odin Pro
Just a heads up. I purchased and used Mobile Odin Pro from since the release and have always used that ever since to flash leaked or official samsung roms due to the fact the pc version bricked my i5800 years back. Happy to say, It never failed me, Also it has support for Wipe Data and Also Dalvik cache. Options to Enable Ever Root, Inject Super Su (Best), And Mobile Odin so your always ROOTED :good:. Gotta hand it to Chainfire for his awesome works. I would suggest for everyone to use it for a worry free Day anytime changing non custom recovery roms, also I have had problems using superuser in the past when trying to install CWMR. Never with Super SU Pro, That's why I use it. Before thinking this post is not useful, think about it, you would be able to wipe data before flashing with no need to worry and perform it via fake recovery or CWMR. Also Odin performs MD5 checksum at your request to ensure its official.
Hi, i'm a new user of SG SII, and i don't know much about it. I was trying to install new ROM on it, first I tried to unroot my phone with CF ROOT, after that everthing was OK. Then i tried to install REVOLT JB i9100 ver 2.8.2, when i got by CWM in recovery, instead of clicking wipe data, then cache and ccache partition i did: wipe data/factory reset, and wipe cache partition, wipe dalwik cache and format system. I flashed kernel and during ROM installation phone turned off and did turn on. i think it's hard bricked. I don't know what to do, please help.
Are you still able to get into don't download mode o your phone ? ( volume down, home key, power button )
If so, reflash your kernel and go from there.
Also have a look at CyanogenMod, they have a good post with instructions on here.
Sent from my GT-I9100 using xda premium
x
Dorbian said:
Are you still able to get into don't download mode o your phone ? ( volume down, home key, power button )
If so, reflash your kernel and go from there.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
no, phone doesn.t response on anything, even if i'm charging the battery.
Try removing your battery and unplug cables.
Then try download or recovery mode again.
If it really doesnt work then there is probably something fried on your system board, doubt anything you can do about it as i had the same not that long ago out of the blue.
Sent from my GT-I9100 using xda premium
.
Dorbian said:
Try removing your battery and unplug cables.
Then try download or recovery mode again.
If it really doesnt work then there is probably something fried on your system board, doubt anything you can do about it as i had the same not that long ago out of the blue.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Did it and still nothing, do you think that maybe JIG plug could be a good idea?
You could always give it a go, havent had any experience with i myself tho so hopefully someone else here can give you a hand
Sent from my GT-I9100 using xda premium
I had a similar issue with sgs1 back in the day. I built a jig and got it working so give it a shot if you can. Its worth it for the cost of a jig surely?
Sent from my GT-I9100 using xda app-developers app
.
ok, i'll try to do it. but i have to ask if that will not work, can i save my phone by changing main board on warranty in service?
You can always tell them that you were updating via kies and it dropped dead just like that.
Your battery was low when you tried to flash it, wasn't it?
try a jig first tho; there's something fishy about those wipes you mentioned.
pawlo130 said:
Hi, i'm a new user of SG SII, and i don't know much about it. I was trying to install new ROM on it, first I tried to unroot my phone with CF ROOT, after that everthing was OK. Then i tried to install REVOLT JB i9100 ver 2.8.2, when i got by CWM in recovery, instead of clicking wipe data, then cache and ccache partition i did: wipe data/factory reset, and wipe cache partition, wipe dalwik cache and format system. I flashed kernel and during ROM installation phone turned off and did turn on. i think it's hard bricked. I don't know what to do, please help.
Click to expand...
Click to collapse
On some occasions flashing a device can use 40-50% of battery to prep and flash device which is why its advised to never flash your phone unless you have at least 50-60% battery.
If power cuts out during flashing procedure it can damage nand/ic chip, corrupt bootloader, corrupt sdcards etc.
After leaving it plugged into to charger overnight try a USB jig to see if you can get it to wake up in download mode, If you can re-flash rom and go from there.
gastonw said:
You can always tell them that you were updating via kies and it dropped dead just like that.
Your battery was low when you tried to flash it, wasn't it?
try a jig first tho; there's something fishy about those wipes you mentioned.
Click to expand...
Click to collapse
battery was about 70%, so it should not have turned off
pawlo130 said:
battery was about 70%, so it should not have turned off
Click to expand...
Click to collapse
then I was right with the fishy wipes.
pray for the jig.
From what you described, it couldn't have hard bricked your phone. In fact, it isn't easy to hard brick our phone unless you install that infamous ICS 4.0.4 leaked ROM or mess with flashing of PIT file. Try to use another fully charged battery to boot up or go into CWM recovery.
Sent from my GT-I9100 using Tapatalk 2
xdanoober said:
From what you described, it couldn't have hard bricked your phone. In fact, it isn't easy to hard brick our phone unless you install that infamous ICS 4.0.4 leaked ROM or mess with flashing of PIT file. Try to use another fully charged battery to boot up or go into CWM recovery.
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
while i was installing new rom, process was like 0% for about 5 minutes, and then phone just turned off. When i did flashing and installing CWM everything was ok. I rooted it with CF root.
Exact same problem here. Followed the root guide to the letter and all OK. Set omega rom installing and it stayed at 0 for five mins then it shut off. Now no life at all.
Gonna build a jig tomorrow so I'll update here if it works.
Really hope so as it's a mates phone.
I've done my s3, s1 and the Mrs s2 without it going wrong so I'm not sure how it went wrong this time.
Sent from my GT-I9300 using xda premium
SkinBobUk said:
Exact same problem here. Followed the root guide to the letter and all OK. Set omega rom installing and it stayed at 0 for five mins then it shut off. Now no life at all.
Gonna build a jig tomorrow so I'll update here if it works.
Really hope so as it's a mates phone.
I've done my s3, s1 and the Mrs s2 without it going wrong so I'm not sure how it went wrong this time.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Your phone have got super brick, and the JIG nothing to do.... You must go to service.
The reason for this is stock kernel who has kode cause brick.
Sorry for my english!
Ah that's a shame. Fingers crossed it's still under warranty or it's gonna be an expensive month.
Sent from my GT-I9300 using xda premium
SkinBobUk said:
Ah that's a shame. Fingers crossed it's still under warranty or it's gonna be an expensive month.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Don't worry will be fine. JTAG must be repair all
Wysyłane z mojego GT-S6500D za pomocą Tapatalk 2
Hi guys
I have looked through a lot of threads before I decided to start this one with my issue.
my friend flashed the S3 from 4.1.2 to 4.2.2, so then I flashed it to 4.3 (BTU-I9300XXUGMK6)
It worked, but with lots of issues like some apps doesn't work, and random restarts.
So I decided to downgrade back to 4.1.2 with Odin, and guess what? I got stuck in a loop with Samsung Galaxy III screen. so i went into recovery mode to reset/factory restore setting and nothing happened.
So I tried installing another version of 4.1.2, and now I'm stuck at the installing loop, where the android has a cube thingy rotating in the stomach, then goes back to Samsung Galaxy III screen and repeat. It looks like as if the phone is trying to install the firmware, but it restarts before it happens?
Interesting thing is that I can get into download mode, but thats it.
Another thing is when I tried to flash it back to 4.3, everything in Odin was a success and when the phone starts to reboot and install...there is a green robot lying with exclamation mark and then reboots and repeats.
Any help
Thanks
Boot into recovery then factory reset, flash only 4.3 first with Odin.
If you've corrupted the efs folder during your downgrade then you'll need to restore a backup, no backup then pay for a repair.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Boot into recovery then factory reset, flash only 4.3 first with Odin.
If you've corrupted the efs folder during your downgrade then you'll need to restore a backup, no backup then pay for a repair.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Thank you! This is very helpful, much more than other threads that I've find, since not many have the same problem as I have.
I can't even reach recovery mode....so I guess the only way is to pay for a firmware repair from Samsung....
I did back up the phone data, but I guess that didn't help much.
Try the rescue firmware, search in general forum, but follow the guide exactly as it includes a pit.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Try the rescue firmware, search in general forum, but follow the guide exactly as it includes a pit.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
OMG! That surely saved my life....my phone is back!!!!!! No more playing around now...
too bad I can't post link but I found the rescue firmware.
Thank you so much