Problem:
My GSII was running normally on the latest RootBox version, Dorimax Kernel 7.46, I was using SD Maid Pro, to Optimize database, I didn't actually knew what the function do, but it has to do something with improving the performance of my phone, and i already used it before many times.
But this time it was stuck for like 10 minutes while optimizing database so i turned off my phone and turned it on again, and BAM, stuck on samsung logo, I couldn't access recovery, only download mode.
Steps I already took:
Here is the log from ODIN:
Step that I'm thinking of taking:
I suspected then that I had to go nasty and flash PIT and re-partition.
Basically this is the last solution for hopeless flashaholics, so based on these threads (1) (2) I downloaded the pit zip, but it contained lots of patched pit files, and each for different brick area.
The problem I cannot access recovery mode so I can't know the bricked part. I read in the thread that if I don't know i have to try each one (92 pit files).
And that was a solution for the MMC_CAP_ERASE brick, which actually is not present if i'm using Dorimanx Kernel or JB AOSP ROMs.
So now I'm not sure if flashing pit will be the correct solution, I was starting to think of flashing a bootloader as in thread
So fellow flashaholics, before I mess up with pit files, and f*ck my phone more, any more suggestions?
(Btw I don't have yellow triangle, so basically I can send it to repairing service or whatever, but actually staying without a smartphone for at least a week is quite impossible for me, if you know what I mean)
My GSII was running normally on the latest RootBox version, Dorimax Kernel 7.46, I was using SD Maid Pro, to Optimize database, I didn't actually knew what the function do, but it has to do something with improving the performance of my phone, and i already used it before many times.
But this time it was stuck for like 10 minutes while optimizing database so i turned off my phone and turned it on again, and BAM, stuck on samsung logo, I couldn't access recovery, only download mode.
Steps I already took:
- 1. Flashed Dorimanx Kernel 7.45 .tar with Odin -> Odin Stuck at NAND Write Start
- 2. Flashed Stock Roms, ICS (I9100XXLPH and I9100XWLPG) and JB (I9100XWLS8_I9100FOPLS3) -> Odin Stuck at NAND Write Start (Failed)
- 3. Flashed it on a different Laptop (x86 and x64) -> Same results.
Here is the log from ODIN:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100_XEU_I9100XWLPG_PRE-ROOTED_I9100XXLPX_I9100XEULP5.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)Step that I'm thinking of taking:
I suspected then that I had to go nasty and flash PIT and re-partition.
Basically this is the last solution for hopeless flashaholics, so based on these threads (1) (2) I downloaded the pit zip, but it contained lots of patched pit files, and each for different brick area.
The problem I cannot access recovery mode so I can't know the bricked part. I read in the thread that if I don't know i have to try each one (92 pit files).
And that was a solution for the MMC_CAP_ERASE brick, which actually is not present if i'm using Dorimanx Kernel or JB AOSP ROMs.
So now I'm not sure if flashing pit will be the correct solution, I was starting to think of flashing a bootloader as in thread
So fellow flashaholics, before I mess up with pit files, and f*ck my phone more, any more suggestions?
(Btw I don't have yellow triangle, so basically I can send it to repairing service or whatever, but actually staying without a smartphone for at least a week is quite impossible for me, if you know what I mean)
