Related
Help i was playing fruit ninja on my ace with cm 7.2 by vo-1..... after some time my phone became very hot so i turned if off for a while then switched it back on then this what happens it loops on samsung logo ...i cant boot into CWM recovery but luckily i could go into download mode and i tried to flash stock rom through odin but unfortunately after completion when it tries to boot it loops continuosly on samsung logo;-(
ANY HELP?..
Try to flash a mulit-package rom like 2.3.3 KP0.
Farooq95 said:
Help i was playing fruit ninja on my ace with cm 7.2 by vo-1..... after some time my phone became very hot so i turned if off for a while then switched it back on then this what happens it loops on samsung logo ...i cant boot into CWM recovery but luckily i could go into download mode and i tried to flash stock rom through odin but unfortunately after completion when it tries to boot it loops continuosly on samsung logo;-(
ANY HELP?..
Click to expand...
Click to collapse
no need! just do a factory wipe! thats it!
Sent from my GT-S5830 using xda premium
jinavs did you read this:
i cant boot into CWM recovery
Click to expand...
Click to collapse
But Farooq95 have you try to go to the stock recovery after flashing the stock rom?
dragonnn said:
Try to flash a mulit-package rom like 2.3.3 KP0.
Click to expand...
Click to collapse
yes i even tried to go into stock recovery but same thing happens
When you flash the mulit-package and you can't go into recovery then I think you phone is damaged. Only what can you try more is using adb to get into recovery:
Code:
adb reboot recovery
At boot loop you mean the Samsung boot animation - or the logo that displays immediately when you try turn on you phone?
dragonnn said:
Try to flash a mulit-package rom like 2.3.3 KP0.
Click to expand...
Click to collapse
i have flashed stock S5830JPKKP9 wich is my baseband But can u provide me link for 2.3.3 kpo
Is S5830JPKKP9 a mulit-package? When yes than it isn't necessary to flash 2.3.3 KP0, doesn't make any difference. You can found 2.3.3 KP0 here https://hotfile.com/dl/127701476/7d30a8b/S5830XWKPO.rar.html but this is an European rom.
The logo when i immediately turn on da phone
I have bad news to you - I think you phone is damaged. Only what you can do is flash a mulit-package. When this doesn't help you must go to the service center. But try before turn on you phone put out the battery for a few minutes.
EDIT
Have posted wrong link, post edited - now it's ok.
Thanks for your effort ill try that... but wat is multipackage? Can i use adb to get into recovery as u said before?
multipackage is an firmware that is split in more files - flashing it make a eraser of all internal memory (have update my previous post whit correct link). You can try adb, but I think you will get "error - no device" because adb works on when the kernel boots - that means it will help when you have a classic boot loop on the boot animation - not on the SAMSUNG logo.
Are u sure that there is no other way to fix this?
Definitely yes.
Pls say cause im taking this to service centre 2morrow
I think the problem is you have overheat you phone - did you play on it when charging the battery? And second I think it isn't good to turn of you phone when he gets hoot - better to let it on and cools slow down.
I found out what really caused this problem so the day before i installed this app called "mobile odin" it asked me root permissons so i allowed it..then it said that the app is not compable with my device and then it asked me to allow it to create a dump file and it said that it could take almost 30 mins to complete and make that app compatible with my device...so i allowed it after 30min it said finished dumping after that i didnt switch off or reboot the phone that day...but i rebooted the phone the other day when it became hot while playing which caused this problem...i am saying this because some other user bricked his/her phone the same way!
I think I lost my phone now the same why -.- damit
Farooq95 said:
I found out what really caused this problem so the day before i installed this app called "mobile odin" it asked me root permissons so i allowed it..then it said that the app is not compable with my device and then it asked me to allow it to create a dump file and it said that it could take almost 30 mins to complete and make that app compatible with my device...so i allowed it after 30min it said finished dumping after that i didnt switch off or reboot the phone that day...but i rebooted the phone the other day when it became hot while playing which caused this problem...i am saying this because some other user bricked his/her phone the same way!
Click to expand...
Click to collapse
While MobileOdin is not compatible with a Galaxy Ace http://forum.xda-developers.com/showthread.php?t=1347899 I'm not sure how it would have bricked your phone when you didn't actually ask it to do anything.
As others have said, considering the inability to enter recovery after flashing a new bootlader & rom etc, a hardware error appears more likely perhaps as a result of overheating.
Too late it had to replace motherboard....
Sent from my GT-I9100 using xda app-developers app
Seriously can someone please explain to me what the heck the above mean? I get the notion of a brick but what the heck is the difference between Super brick? Hard / Soft Brick? Finally, not really brick but what's Pixel Salad!?
Thanks!
altrstar said:
Seriously can someone please explain to me what the heck the above mean? I get the notion of a brick but what the heck is the difference between Super brick? Hard / Soft Brick? Finally, not really brick but what's Pixel Salad!?
Thanks!
Click to expand...
Click to collapse
Soft brick= a FAILURE of the device that can be reverted by the user
Hard brick= a FAILURE of the device that has to be reverted via external devices see jtag
Superbrick= a FAILURE of the device where the only solution the service center and a replacement of the component that malfunctions.
Pixel salad = a problem of the graphics unit or the screen to display correctly the image and put instead random colored pixels on some areas of the screen or the whole screen.
This is my interpretation of those issues everyone can correct it if he thinks that those expansions are incorrect.
Hope it helped you understanding few of those issues.
GL& HF
Sent from my GT-N7000 using Tapatalk 2
Braxos said:
Soft brick= a FAILURE of the device that can be reverted by the user
Hard brick= a FAILURE of the device that has to be reverted via external devices see jtag
Superbrick= a FAILURE of the device where the only solution the service center and a replacement of the component that malfunctions.
Pixel salad = a problem of the graphics unit or the screen to display correctly the image and put instead random colored pixels on some areas of the screen or the whole screen.
This is my interpretation of those issues everyone can correct it if he thinks that those expansions are incorrect.
Hope it helped you understanding few of those issues.
GL& HF
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
You are spot on!!
Hi, I flashed N7000ZSLPF ICS with bootloader and rooted afterwards. Everything was perfect until i decided to flash cm9 nigthly signed.zip and did a direct reboot. Now nothing happens when i try to turn the phone on
What kind of brick is this? Can somebody please tell me ?
Is there any possibilities to get the phone fixed?
Thank you all for your answers allready
Wish u all a nice day
Nefret90 said:
Hi, I flashed N7000ZSLPF ICS with bootloader and rooted afterwards. Everything was perfect until i decided to flash cm9 nigthly signed.zip and did a direct reboot. Now nothing happens when i try to turn the phone on
What kind of brick is this? Can somebody please tell me
Click to expand...
Click to collapse
I'm not 100% sure, but performing a flash under lpf isn't recommended. How did you root lpf after flashing? And when you say "did a direct reboot" what do you mean? Also when you say doesn't turn on at all, do you mean no display whatsoever or enters Samsung boot loop? Are you able to enter recovery or download mode?
Sent from my GT-N7000 using xda premium
Nefret90 said:
Hi, I flashed N7000ZSLPF ICS with bootloader and rooted afterwards. Everything was perfect until i decided to flash cm9 nigthly signed.zip and did a direct reboot. Now nothing happens when i try to turn the phone on
What kind of brick is this? Can somebody please tell me ?
Is there any possibilities to get the phone fixed?
Thank you all for your answers allready
Wish u all a nice day
Click to expand...
Click to collapse
You should have read the warning about LPx kernels (LP1, LP5, LP6, LPY, LPF)
Wiping or flashing in recovery will probably cause superbrick.
Sent from my GT-N7000 using XDA
Nefret90 said:
Hi, I flashed N7000ZSLPF ICS with bootloader and rooted afterwards. Everything was perfect until i decided to flash cm9 nigthly signed.zip and did a direct reboot. Now nothing happens when i try to turn the phone on
What kind of brick is this? Can somebody please tell me ?
Is there any possibilities to get the phone fixed?
Thank you all for your answers allready
Wish u all a nice day
Click to expand...
Click to collapse
The way to go from ANY non-CM9-based ICS Rom to a CM9-based Rom is via Gingerbread.
You should've first used PC Odin to go back to GB, root your Rom, then flash CM9.
You have most probably superbricked your phone.
SpyderTracks said:
I'm not 100% sure, but performing a flash under lpf isn't recommended. How did you root lpf after flashing? And when you say "did a direct reboot" what do you mean? Also when you say doesn't turn on at all, do you mean no display whatsoever or enters Samsung boot loop? Are you able to enter recovery or download mode?
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Did root using cfs root trough Odin Pc. With a direct boot i mean that i just rebooted without doing the partiton thing just flashed the image and rebooted.
And when i say doesnt turn on at all i mean that absolutely nothing happens, no power at the screen no detection trough usb on pc no download mode or anything.
tryied to flash before and did just reboot, back then did just got the boot looop probem and did a recovery to ics. this last time i tried again to show a friend in a hurry and failed epicly
Nefret90 said:
Did root using cfs root trough Odin Pc. With a direct boot i mean that i just rebooted without doing the partiton thing just flashed the image and rebooted.
And when i say doesnt turn on at all i mean that absolutely nothing happens, no power at the screen no detection trough usb on pc no download mode or anything.
tryied to flash before and did just reboot, back then did just got the boot looop probem and did a recovery to ics. this last time i tried again to show a friend in a hurry and failed epicly
Click to expand...
Click to collapse
You are definitely bricked, I fear. Head to the nearest service centre.
I am from Kuwait ..
I purchased Samsung galaxy Note N7000 15 Days before
I have Installed King Droid ICS mania 2.1 later yesterday i updated to King droid ICS mania 3.0 and Samsung galaxy s3 Mod updated .. after that i restarted my NOTE but its not booting
i can go to Download mode and Recovery mode ..
even i can see the Install ZIP from SD card and all in CW ..when i Update it says
Can't Mount EMMC
I tried to Mount also But failure ..
I tried Stock rom of ICS official to Update Using ODIN 1.85 .. it stops at
<ID:0/008> factoryfs.img ..
I am worried I cant go for warranty Bcoz at Boot It says Binary count (5)
Please Help me Out
Hi, I need some advice. I dropped my Galaxy S in a puddle. It was submerged for the just a second, but when I fished it out, the screen had gone 'weird', so I got the battery out as quickly as possible, then dried it out for a few days in the airing cupboard. I then tried it and it started up okay, then when I swiped to unlock the screen, it froze. since then I have been unable to boot the phone. It shows the Galaxy logo, then restarts and continues that loop.
I wondered if maybe the software has just been corrupted during its bath, so I thought i might try flashing a ROM onto it to see if that would recover. I found that I could not enter recovery mode but download mode opened okay. I have tried flashing a few ROMS using Odin. I am completely new to this and have never flashed my phone before, so steep learning curve. I have so far tried - I9000XWJW5 which I believe is normally used before installing Cyanogen mod. I also downloaded the T-Mobile Stock ROM and one with this filename - CF-Root-XX_OXA_JW4-v4.4-CWM3RFS. All of these successfully downloaded to the phone and I could see the progress bar on the phone. Unfortunately I still cannot get the phone into recovery mode.
So, whats your opinion? is my phone screwed? Is there anything else I can try which may help, like formatting or anything like that.
Any help would be very much appreciated.
try search for value pack 2.3.6 and flash it then root it after that I believe you should get the recovery option.
erpurohit said:
try search for value pack 2.3.6 and flash it then root it after that I believe you should get the recovery option.
Click to expand...
Click to collapse
Unfortunately I think that was the file - I9000XWJW5 I had already tried.
did you rooted your phone after flashing
erpurohit said:
did you rooted your phone after flashing
Click to expand...
Click to collapse
Can I do that without being able to get into recovery mode?
I've just been reading that I can use a PIT file to repartition during flashing. Is it worth trying? I noticed in the Value pack TAR file it does not have a PIT file. I got one downloaded from somewhere else called - s1_odin_20100512.pit worth a shot?
I tried including the pit file as well. Odin reported success but phone is still continuous boot loop and I cannot get recovery mode up. Do you think one of those USB things that get you into download mode would help? I'm beginning to think the internal SD is knackered, or something like that.
I think the memory is brocken but i don't realy know. Send it to Samsung for a check
Sent from my GT-I9001 using xda app-developers app
I'll try them, will they still help me after I've tried reinstalling ROM etc?
Yes they will repair it if you pay for
Sent from my GT-I9001 using xda app-developers app
Hi guys, i gonna tell you about how my i9001 was stuck in a bootloop. Maybe you could help me. I'm sick of it.
Cause: I installed cm10 and cwm5 or 6 as recovery and upgrade my device using Ota Updater. When I restarted my i9001, it got stuck in a bootloop.
What my i9001 can display: It can access to rampdump mode and download mode. In case I try to turn on my i9001 or access to recovery mode the Samsung logo/word is shown twice and stops showing anything else. It often gets stuck showing the typical grey battery flat (with a loading stopped) and the black screen alternately. This is caused when I a disconnect the USB cable from my computer/laptop.
Attempts: i've tried everything except for the right solution. Lots of forum threads and nothing works for me. I've tried:
1.- Boot_loader for device boot.
2.- I've flashed an stock rom: XXKQP, and 2 more: BVKPC y XXKQ1. Each one are official.
3.- And then recovery-clockwork-5.5.0.4 and -6.0.1.2.
4.- I've tried, then, flashing feamodrecovery 1.2.
5.- Nothing works for me.
I've been using Odin 4.43. AriesVE in OPS section and when flashing these roms: one package. For recovery packages: one package and pda (I tried these two options).
I can't reach at recovery mode. Any help would be greatly appreciated. Greetings!
have a look here http://forum.xda-developers.com/showpost.php?p=30415128&postcount=1
When phone boots there's nearlz always a solution
Sent from my GT-I9001 using xda app-developers app
slow--welder59, any of these solutions helped me. I tried with any other combination of combos but nothing happened. I didn't know to use adb method. I installed adb drivers but it didn't detect my device. When I entered to download mode and pressed Install (in the program) tried to download something but it stopped.
Any suggestion?
Can anyone help me? I want to exhaust all possible options.
zerohhorez said:
Can anyone help me? I want to exhaust all possible options.
Click to expand...
Click to collapse
What happens when you try to format data from recovery...?
If you get some errors, write them here...
If everything goes well, then it is not what im expecting (in that case problem is probably easier to solve)...
sava92ns said:
What happens when you try to format data from recovery...?
If you get some errors, write them here...
If everything goes well, then it is not what im expecting (in that case problem is probably easier to solve)...
Click to expand...
Click to collapse
The problem is just this. I cannot go to recovery mode. Just shows Samsung twice and powers off.
zerohhorez said:
The problem is just this. I cannot go to recovery mode. Just shows Samsung twice and powers off.
Click to expand...
Click to collapse
Can you open 'Download mode'?
sava92ns said:
Can you open 'Download mode'?
Click to expand...
Click to collapse
Yes I can, and that's the reason why I don't give up hope. However, I've tried installing some stock roms and recoveries and nothing worked for me.
Try one of the following (or both even if your desperate):
http://forum.xda-developers.com/showthread.php?t=1922505 (broodROM RC5 download link) [recomended]
http://broodplank.net/old/flashsamsungi9001.php (skip chapter 5 as it doesn't apply) [if that doesn't work]
edit:: USB Drivers: http://forum.xda-developers.com/showthread.php?t=961956
stepie22, thank you for your help. Nothing worked for me.
First link: another typical manual for installing a stock rom via Odin. During the process my device powered off. It was supposed to reboot. After the process ended, i disconnected it from PC and its screen showed a grey empty battery (with a loading in the middle) and word "Samsung" alternatively.
Second link: this was the solution for my first brick. Then, my device showed this yellow triangle. This second time is annoying me. I haven't found any solution to change, at least, the behaviour of my device.
Any other different solution? Thnks guys.
zerohhorez said:
Then, my device showed this yellow triangle.
Click to expand...
Click to collapse
See this ... if that is the triangle, find that part on the wiki page.
Maybe your device got the eMMC Bug?
Normally your Device would be hardbricked if you "over" flashed.
If nothing works out try this:
Have a look in this thread:
http://forum.xda-developers.com/showthread.php?t=2224029
Download CWM Recovery 6.0.2.8 ODIN Package and flash it in "Download Mode" the regular way (AriesVE.ops and onepackage).
Then maybe you are able to enter Recovery Mode again...
This might be not your problem, but you could give it a try:
Some people had issues with rebooting in recovery, so there is a fix in this post
http://forum.xda-developers.com/showpost.php?p=24831012&postcount=1330
Hopefully one helps you!
Greetings
I am having a sudden sudden death problem on my device, but in my research I only knew a solution for the I9300 model through a XXELLA bootloader for android JB, and I did not find anything related to this for my device.
I wonder if you also have a solution to the problem on this device that I have.
Someone to help me?:crying:
Oshmar said:
I am having a sudden sudden death problem on my device, but in my research I only knew a solution for the I9300 model through a XXELLA bootloader for android JB, and I did not find anything related to this for my device.
I wonder if you also have a solution to the problem on this device that I have.
Someone to help me?:crying:
Click to expand...
Click to collapse
Can you specify what exactly do you mean by "Death"?
Does the phone boot into download mode or recovery mode?
Does it make anything when it's connected to charger?
The device stops in the logo, it simply does not initialize, it goes into normal download mode, but even after the process of installing the rom (numerous attempts) it initializes, but after 2 minutes it goes back to the dead state, ie, And stuck in the logo.
Oshmar said:
The device stops in the logo, it simply does not initialize, it goes into normal download mode, but even after the process of installing the rom (numerous attempts) it initializes, but after 2 minutes it goes back to the dead state, ie, And stuck in the logo.
Click to expand...
Click to collapse
Stuck at what logo, splash screen logo or boot animation logo?
Well, i suggest u to flash back to tock rom using odin and start again from there.. U might want to repartition you phone too. to repartition, pit file is required, google it and you'll find one.. Good luck.
Oshmar said:
The device stops in the logo, it simply does not initialize, it goes into normal download mode, but even after the process of installing the rom (numerous attempts) it initializes, but after 2 minutes it goes back to the dead state, ie, And stuck in the logo.
Click to expand...
Click to collapse
If Odin fails to flash the stock rom, try flashing with another version of Odin like v3.07 or v3.09, and try other cable and other USB Port, also try flashing the stock rom with a pit ONLY if the error in Odin's log is related to repartitioning.
MigoMujahid said:
If Odin fails to flash the stock rom, try flashing with another version of Odin like v3.07 or v3.09, and try other cable and other USB Port, also try flashing the stock rom with a pit ONLY if the error in Odin's log is related to repartitioning.
Click to expand...
Click to collapse
Just what I did, flashing in other versions, for version v3.09 the installation was successful, however when starting to configure account, wifi and etc. Restart by yourself and freeze the logo again.
This is very strange because there is no malfunction in the device, the card is intact. I believe that version 4.1.2 is the most appropriate for this device, since I have seen many reports of people warning not to upgrade to 4.4 because of this problem.
But now it does not make any difference, I'm going to trade it for an Optimus G touch that I really needed to get LG to work.
Oshmar said:
Just what I did, flashing in other versions, for version v3.09 the installation was successful, however when starting to configure account, wifi and etc. Restart by yourself and freeze the logo again.
This is very strange because there is no malfunction in the device, the card is intact. I believe that version 4.1.2 is the most appropriate for this device, since I have seen many reports of people warning not to upgrade to 4.4 because of this problem.
But now it does not make any difference, I'm going to trade it for an Optimus G touch that I really needed to get LG to work.
Click to expand...
Click to collapse
It might be a hardware issue, don't you think?
Coming from Samsung for being anything ... this device was stopped a long time, only took it to use a month and a half, I left Samsung a long time, I had hardware problem years ago with two devices of the brand, S4 GT-i9505 - GT-i9500, since then never again, more like my LG E977 is only with the touch screen failing, I found a service shop with interest in this GS3 and I will exchange it for the touch screen of the E977.