Database Develop

[Q] Help? boot loop at samsung logo!!

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

[Q] Superbrick, Softbrick, Pixel Salad ?huh?

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

super SUPER brick??? :(

i dont know ..what really happened.. doubt#1 : i was about to flash out new ROM for my note,, n thru CWM i wiped my fone thru factory/reset ,,, it never had got problems,, but today it did,, and after pressing reboot,,, nothing happend.. but yes the fone switched off,,and its never getting ON,.. not even boot screen,,, like DEAD,,, jus no response at al,,,
doubt#2 : after formating (wipe factory/reset) , i actually, removed my battery coz i was transferring ROM file to sd card through card reader,, and i had to remove my battery ... and after i slided in my battery ,, the phone died,,, no response,,, :crying: ... m dooomeedddd....
any suggestions,, plz plz plz .. i dont have warranty too.. i'm in ddeeep trouble .... . and i have already given to samsung service,, and even they havent noticed out the problem yet,,, is my phone really dead then????? :crying: :crying: :crying:

sajan1991 said:
i dont know ..what really happened.. doubt#1 : i was about to flash out new ROM for my note,, n thru CWM i wiped my fone thru factory/reset ,,, it never had got problems,, but today it did,, and after pressing reboot,,, nothing happend.. but yes the fone switched off,,and its never getting ON,.. not even boot screen,,, like DEAD,,, jus no response at al,,,
doubt#2 : after formating (wipe factory/reset) , i actually, removed my battery coz i was transferring ROM file to sd card through card reader,, and i had to remove my battery ... and after i slided in my battery ,, the phone died,,, no response,,, :crying: ... m dooomeedddd....
any suggestions,, plz plz plz .. i dont have warranty too.. i'm in ddeeep trouble .... . and i have already given to samsung service,, and even they havent noticed out the problem yet,,, is my phone really dead then????? :crying: :crying: :crying:
Click to expand...
Click to collapse
Did you wipe ./ reset on ICS? if so - probable brick..
Alternatively, Is your battery charged? tried alternate?
Can you get it into Download / Recovery mode... or are you getting nothing out of it at all..

1. Why did you think it was a good idea to pull the battery while doing something like this?
2. Wich kernel were you using?
3. Can you boot into Download mode?

sajan1991 said:
i dont know ..what really happened.. doubt#1 : i was about to flash out new ROM for my note,, n thru CWM i wiped my fone thru factory/reset ,,, it never had got problems,, but today it did,, and after pressing reboot,,, nothing happend.. but yes the fone switched off,,and its never getting ON,.. not even boot screen,,, like DEAD,,, jus no response at al,,,
doubt#2 : after formating (wipe factory/reset) , i actually, removed my battery coz i was transferring ROM file to sd card through card reader,, and i had to remove my battery ... and after i slided in my battery ,, the phone died,,, no response,,, :crying: ... m dooomeedddd....
any suggestions,, plz plz plz .. i dont have warranty too.. i'm in ddeeep trouble .... . and i have already given to samsung service,, and even they havent noticed out the problem yet,,, is my phone really dead then????? :crying: :crying: :crying:
Click to expand...
Click to collapse
Firstly why super super bricked, I never understand why super birck is even around either its bricked or not.
Anyway, where you running a ICS rom with the emmc bug kernel before factory wiping?
but if you pulled the battery before it had finished this could have also done it.
Try plugging the phone in to your computer and pressing the power button and using adb to try and connect to the device

that means its bricked ,,, like u asked me,,, reset on ICS/wipe..
tried alternate battery too,,didnt worked

everyone knows factory reset/wipe is dangerous on ICS even with CWM - this is more important to those who have no warranty on their Note. What I really don't understand is why do people still continue to wipe/reset if they knew the risk of bricking their device and then complain afterwards??

sajan1991 said:
that means its bricked ,,, like u asked me,,, reset on ICS/wipe..
tried alternate battery too,,didnt worked
Click to expand...
Click to collapse
Why did you do that? This section is litterally filled with warnings in every corner.
NEVER EVER DO A FULLWIPE ON ICS KERNEL

Still if you are able to put device in download mode(Vol down+home+power) then flash stock GB ROM and then wipe cache and data

same problem here too
my phone doesnt go in download mode or in recovery mode.....
can somebody explain the problem and probable come out with a solution

Can you fast boot from adb?
sent from my ICONia

chochweet said:
same problem here too
my phone doesnt go in download mode or in recovery mode.....
can somebody explain the problem and probable come out with a solution
Click to expand...
Click to collapse
Currently only solution is to send it for repairs or repartition to bypass the damaged section of the chip.
Sent from my GT-N7000 using xda premium

As simple as it can be... if the phone does not boot into download mode or into cwm... its a brick
If it enters cwm... you can try the pit file mode with a stock GB rom... or you could also try the repartition method with ADB (i did it by my self and it works, currently using that ex-bricked smartphone
Sent from my GT-N7000 using XDA Premium HD app

Has anyone noticed a definite lack of thanks in this thread?
Sent from my GT-N7000 using xda premium

does speed mod makes it safe to use CWM on emmc with brick bug? what should be done to make it safe to use LRK or LRG Stock Roms,and if i need to wipe before installing other rom is it safe to use CWM? i am going from LRG to LRK any need to Wipe or should go to GB then Wipe then ICS?

crossmedia said:
does speed mod makes it safe to use CWM on emmc with brick bug? what should be done to make it safe to use LRK or LRG Stock Roms,and if i need to wipe before installing other rom is it safe to use CWM? i am going from LRG to LRK any need to Wipe or should go to GB then Wipe then ICS?
Click to expand...
Click to collapse
yes speed mod is safe, so you can wipe in any safe kernel, but personaly i prefer wiping in Abyssnote kernel bec it is a GB kernel to be 100% in the safe side, and it doesn't take more than 10 sec to flash the abyys kernel zimage through mobile odin, before installing whatever, or wiping anything

but cwm. zip is not save
cwm from speedmod is
speedmod and flash cwm. zip is not
Sent from my GT-N7000 using Tapatalk 2

Touchscreen doensn't work anymore after root

Hello there,
i've rooted my GC with newest 4.1.2 Android and all went fine. Then i wanted to use the cool init.d Script, which makes it possible to set the extSdCard storeage as 'internal' and the internal as external Storeage, to get more space for a lot of Apps.
But for this init.d script i needed to use a compatible kernel. So thinking, the GalaxyCamera HW is almost the same like from the Galaxy S II Phone. i decied to use this tut: http://forum.xda-developers.com/showthread.php?t=1772234 to download the init.d script and siyah- kernel. getting this things into the Camera i should use ClockWorkMod.
And there the Problem starts: In ClockworkMod install-tool i sayed "yes" to install it for a Galaxy S III.. humm, device restarting into recovery and Screen flashes with disorientated GalaxyCamera Logo und went blank afterall... i rebootet and all went fine, but recovery was "corrupted" (with my luck i didnt make a backup in ClockWorkMod ROM Utility on Android... ( )
So i decided to start over and started to flashing (idont now why) the root- Restore file from Chainfire for the GalaxyCamera again. Recover Mode works fine again, but NOW on normal boot my Touchscreen doenst react anymore.
After trying with several Stock recoveries, even with 4.1.1 and so on an re- Routing.... issue still persists.. ( Can anyone help me, or did i just killed the Touchscreen Controller with this Action??

Do you try a hard reset, you probably can do it from recovery mode, but not sure.
Maybe he solve your issue ?

I've already tried. But thank you for your tip!
The Problem is (i guess) that ClockWorkMod or Chainfires Root, locked up some file- permissions and the Touchscreen- driver cant load into Memory. If it where possible for me to repartition the device, all locked Data gets wiped and a fresh Andoid flashed back to NAND . I tried this with Adam's Pit- File in Odin or Heimdall several Times with differen OS'es. No success.
Yesterday i Sent the camera in for repair to a Samsung Service Provider. I Hope they will fix it. Small problem: i couldnt reset the Flashcounter with an 'defective' Touchscreen! ... I hope they would not recognize my 20 custom OS restores!
I will inform you if my lovely GalaxyCamera gets fixed!

WEissbr0t said:
I've already tried. But thank you for your tip!
The Problem is (i guess) that ClockWorkMod or Chainfires Root, locked up some file- permissions and the Touchscreen- driver cant load into Memory. If it where possible for me to repartition the device, all locked Data gets wiped and a fresh Andoid flashed back to NAND . I tried this with Adam's Pit- File in Odin or Heimdall several Times with differen OS'es. No success.
Yesterday i Sent the camera in for repair to a Samsung Service Provider. I Hope they will fix it. Small problem: i couldnt reset the Flashcounter with an 'defective' Touchscreen! ... I hope they would not recognize my 20 custom OS restores!
I will inform you if my lovely GalaxyCamera gets fixed!
Click to expand...
Click to collapse
Dude, did you get your camera back?? I made he same mistake just a couple of hours ago.. I am feeling so depressed, I dont know what to do.
Did they say anything about the flash counter?

me too
I have had this problem as well. My camera has no touch on the screen after rebooting. I saw it flick and lock and then I tried to re-flash the rom etc, but it didn't help.
Sent to Samsung and they are saying that the motherboard and screen have to be replaced at a cost of $350. They are seeing if they can repair under warranty, but it doesn't sound too hopeful.... Perhaps, I will give up on my Galaxy Camera. I am not going to pay $350 to have the item repaired. I didn't know if it was a software fault or a hardware failure. I think it really should be a warranty issue....
Anyhow, I guess clockwork mod can really wreck things up..... Anyone, found a way to fix this issue? Why didn't the default Samsung ROM flash and factory reset fix the issue if it is supposedly software?

WEissbr0t said:
Hello there,
i've rooted my GC with newest 4.1.2 Android and all went fine. Then i wanted to use the cool init.d Script, which makes it possible to set the extSdCard storeage as 'internal' and the internal as external Storeage, to get more space for a lot of Apps.
But for this init.d script i needed to use a compatible kernel. So thinking, the GalaxyCamera HW is almost the same like from the Galaxy S II Phone. i decied to use this tut: http://forum.xda-developers.com/showthread.php?t=1772234 to download the init.d script and siyah- kernel. getting this things into the Camera i should use ClockWorkMod.
And there the Problem starts: In ClockworkMod install-tool i sayed "yes" to install it for a Galaxy S III.. humm, device restarting into recovery and Screen flashes with disorientated GalaxyCamera Logo und went blank afterall... i rebootet and all went fine, but recovery was "corrupted" (with my luck i didnt make a backup in ClockWorkMod ROM Utility on Android... ( )
So i decided to start over and started to flashing (idont now why) the root- Restore file from Chainfire for the GalaxyCamera again. Recover Mode works fine again, but NOW on normal boot my Touchscreen doenst react anymore.
After trying with several Stock recoveries, even with 4.1.1 and so on an re- Routing.... issue still persists.. ( Can anyone help me, or did i just killed the Touchscreen Controller with this Action??
Click to expand...
Click to collapse
I had the same problem dude, got the touchscreen replaced at the service center.
New touchscreen works totally fine.

Hi;
I'm using samsung galaxy camera. I wanted to root with odin. But I selected bootloader instead of PDA wrongly, Then I selected start. My Camera rebooted and not opened. Just showing "samsung galaxy camera" logo.
If somebody help me, I will happy.

Flash stock rom
7dervish said:
Hi;
I'm using samsung galaxy camera. I wanted to root with odin. But I selected bootloader instead of PDA wrongly, Then I selected start. My Camera rebooted and not opened. Just showing "samsung galaxy camera" logo.
If somebody help me, I will happy.
Click to expand...
Click to collapse
You should be able to flash the stock samsung standard rom. It will update everything including the bootloader. Haven't had this problem, but this solution seems logical. Download the full rom and flash with PDA option.
Good luck.

ant75 said:
You should be able to flash the stock samsung standard rom. It will update everything including the bootloader. Haven't had this problem, but this solution seems logical. Download the full rom and flash with PDA option.
Good luck.
Click to expand...
Click to collapse
Thank you,
I flashed stock rom. SGC opening but touchscreen did not work. Just otg cable with mouse.
I will send to samsung service on monday

7dervish said:
Thank you,
I flashed stock rom. SGC opening but touchscreen did not work. Just otg cable with mouse.
I will send to samsung service on monday
Click to expand...
Click to collapse
There is no solution for touchscreen problem. You just give service your camera and they change touchsreen. Cause it's a hardware problem

Jeah it definitively was an HW Problem. Got a New Touchscreen and all works fine
Gesendet von meinem GT-I9100 mit Tapatalk 2

A pity, read the solution, because I'm at the same point

[Q] whats this? i9001 bricked, damaged partition? cant wipe data, do factory reset.

Hi people,
i dont know where to go! i have read dozen of sites and post... am i right here?
my S+ i9001
PDA i9001xxkq7
Phone: i9001xxkpk
csc i9001dbtkp2
can:
boot in download mode
can boot recovery mode
can be flashed via odin
can NOT:
-boot to system (always hang or freeeze or shuts down when Samsung logo comes)
-data can not be wiped (Processbar starts but never really start doing something) CWM6. I had some other recoverys and they gave me some messages like can not accsess data/csc or something like these messages in other posts.
-can not do anything in recoverymode exepted, wipe cache.
-can not update zip
-can not gain accsess to sdcard ore sideby
-cant reboot in recovery.
i flashed with odin (and Aries.ops):
-broodROM_RC5
-the right StockROM
-phone seems to be bricked
-no access with Quickflash (dont know if debug mode was or is enabled)
i found some people with similar problems with other devices (i9000 // i9100), but not with the i9001. so i write it here.
always the answer was try a full wipe/reset, but i cant or dont know how to it when the recoverymod or stock recovery doesnt do it.
kind regards
Daniel
im Stuck! where do i have to start further steps?

incredibledan said:
Hi people,
i dont know where to go! i have read dozen of sites and post... am i right here?
my S+ i9001
PDA i9001xxkq7
Phone: i9001xxkpk
csc i9001dbtkp2
can:
boot in download mode
can boot recovery mode
can be flashed via odin
can NOT:
-boot to system (always hang or freeeze or shuts down when Samsung logo comes)
-data can not be wiped (Processbar starts but never really start doing something) CWM6. I had some other recoverys and they gave me some messages like can not accsess data/csc or something like these messages in other posts.
-can not do anything in recoverymode exepted, wipe cache.
-can not update zip
-can not gain accsess to sdcard ore sideby
-cant reboot in recovery.
i flashed with odin (and Aries.ops):
-broodROM_RC5
-the right StockROM
-phone seems to be bricked
-no access with Quickflash (dont know if debug mode was or is enabled)
i found some people with similar problems with other devices (i9000 // i9100), but not with the i9001. so i write it here.
always the answer was try a full wipe/reset, but i cant or dont know how to it when the recoverymod or stock recovery doesnt do it.
kind regards
Daniel
im Stuck! where do i have to start further steps?
Click to expand...
Click to collapse
+1
---------- Post added at 03:48 PM ---------- Previous post was at 03:03 PM ----------
The Same problem with my phone!!
I tried every thing every cwm recoveries and root stock rom and broodrom no boot
Please somebody can help us?
Thank you

I9001 cant format data and emmc
Update,
i finally got an CWM running! aktually 5.5.0.4 but the 6.0.1 and 6.0.2 alsoworked at the end.
now all i cant do is, formatting data and/or mount/format emmc.
Plugged in via USB Cable to PC i can access (internal) sdcard and copy all zips i want. I also cann install them, but i cant wipe data.
i geuss there is an hardware issue, so that all these fine mods are biting on stone, trying to format the "partition"
This results in unbootable systems..i think
At least i tried cm-9-20130220-EXPERIMENTAL-ariesve-rc5 with kernel 3.00, no luck.
i this hardbricked? damaged? i geuss im close to the final. but wich one.....
last try is this hint :http://forum.xda-developers.com/showthread.php?t=2173180
but ODIN crashes when trying the MD5 checksum
thanks for reading!
dan

...
tried to reduce the i9001reset.tar.md5 file with repacking it without the cache and system file. but the reset.zip still has 750mb and odin crashes checking the md5.
are there any other methods to check if the data partition or the emmc.ic is damaged? i cant format via CWM or stock recovery, results in endless process...
and Quickflasher also crashed trying to "wipe at start" mmcblk0p17 (data)
greetz from Berlin
Dan

samen problem
I got the samen problem, please some help. (10 hours working on it
I dit odin to stock
odin to recovery 6
formated sd
installed roms
nothing works, cant mount, cant wipe date,
Has it to do something with .ext (i dunno this really and dunno how to change

did you try to wipe data from stock recovery after install stock rom?
Sent from my GT-I9001 using xda app-developers app

danger
ATTENTION dont try the reset.zip partition recovery as described above! It has killed my phone! i lost any lifesigns from the device, no vital functions over the battery or powersupply. i just cant switch it on again.
this is my end with this!

macar said:
did you try to wipe data from stock recovery after install stock rom?
Sent from my GT-I9001 using xda app-developers app
Click to expand...
Click to collapse
yes, i tried but it did not work, neither from stock or custom ROM.

I'm having the exact same problems. It all started when I updated CWM to 6.0.2.8 as recomended by ivendor, in order to flash CM10. Since then I can't wipe data partition, and no matter what I flash (through both Odin and CWM), the phone doesn't boot anymore. Tried to restore original Samsung ROM, no success... Hasn't anyone figure it out? It seems a large number of user have dealt with this issue in the last days, perhaps the coder of CWM 6.0.2.8 should explain how to fix this mess.
I went to a local phone service, and they said they can't do anything, the whole internal memory has to be replaced. I can't believe this.

No solution?
I have exectly the same problem and i tried everything. I still can get to recovery and download mode, because i didnt mess with reseting broken partition. Can this be solved? I didnt find anyhing in threads, and it seems that a lot of people have this kind of problem now. It all happend on my s+ while i was trying to flash CM10 Beta4.

repair in warranty
Ledo13 said:
I have exectly the same problem and i tried everything. I still can get to recovery and download mode, because i didnt mess with reseting broken partition. Can this be solved? I didnt find anyhing in threads, and it seems that a lot of people have this kind of problem now. It all happend on my s+ while i was trying to flash CM10 Beta4.
Click to expand...
Click to collapse
OK Guys,
here im back. After killing the phone i called samsung i (i was still in warranty), an then i send it to an repair center of their choice. it tooks two weeks an here i got it back. dont know what they have done. but it didnt cost me anything.
end of story from me
greetz dan

search for emmc bug thread in development section http://forum.xda-developers.com/showthread.php?t=2224029
the recovery you have used was compiled over a 3.0 kernel, it has a bug that brick phones, like the galaxy s2 and galaxy note.

New motherboard
incredibledan said:
OK Guys,
here im back. After killing the phone i called samsung i (i was still in warranty), an then i send it to an repair center of their choice. it tooks two weeks an here i got it back. dont know what they have done. but it didnt cost me anything.
end of story from me
greetz dan
Click to expand...
Click to collapse
I got my phone back from service in a 4 days and they changed my motherboard. Now I have completely new motherboard (plus I didnt pay a thing because I still got warranty). Obviously they didn't find out whats wrong with my phone so they put new motherboard

Ledo13 said:
I got my phone back from service in a 4 days and they changed my motherboard. Now I have completely new motherboard (plus I didnt pay a thing because I still got warranty). Obviously they didn't find out whats wrong with my phone so they put new motherboard
Click to expand...
Click to collapse
I managed to "rescue" my eMMC-bricked phone by doing everything I could find about the eMMC brick bug killed my i9001. No root but I can live with that until someone comes up with a better fix.. Good luck, I wish I had a better step by step instruction list on how I did it but honestly I just frantically tried things over and over in different order and finally got it going.
http://forum.xda-developers.com/showthread.php?t=2234489
I guess...
1. Get TWRP 2.2.2.1 or CWM 5.5.0.4/the new 2.6-based 6.0.2.8 CWM recovery flashed.
2. Use QuickWipe (link in my post to the OP).
3. Use ODIN 4.43 to flash that 1.4GB fixmev2.tar file (I did it at least 2-3 times during different stages)
4. Follow the instructions in the links in my post.
5. Good luck.
6. Wait for the devs to solve this problem permanently with new kernels and ROMs and thank them when they solve it.

Scyphe said:
I managed to "rescue" my eMMC-bricked phone by doing everything I could find about the eMMC brick bug killed my i9001. No root but I can live with that until someone comes up with a better fix.. Good luck, I wish I had a better step by step instruction list on how I did it but honestly I just frantically tried things over and over in different order and finally got it going.
http://forum.xda-developers.com/showthread.php?t=2234489
I guess...
1. Get TWRP 2.2.2.1 or CWM 5.5.0.4/the new 2.6-based 6.0.2.8 CWM recovery flashed.
2. Use QuickWipe (link in my post to the OP).
3. Use ODIN 4.43 to flash that 1.4GB fixmev2.tar file (I did it at least 2-3 times during different stages)
4. Follow the instructions in the links in my post.
5. Good luck.
6. Wait for the devs to solve this problem permanently with new kernels and ROMs and thank them when they solve it.
Click to expand...
Click to collapse
EDIT: after it died last night (tried to force root permissions and it would no longer boot) and fiddling to get it back to working condition I tried flashing the file in this post (http://forum.xda-developers.com/showpost.php?p=38671295&postcount=2) to reset partitions and the phone is now stone dead... a true brick.. absolutely nothing happens when I try to power up, enter recovery mode, whatever.. it's dead... stone cold..