Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,769,208 Members 37,920 Now Online
XDA Developers Android and Mobile Development Forum

[Workshop] Unbrick fully bricked I9070

Tip us?
Junior Member - OP
Thanks Meter 20
Posts: 22
Join Date: Apr 2008
ok, UART debug up and partially running on my SIII mini: debug messages displayed on terminal but keystrokes do not reach the phone, this is secondary for me at the moment, I may have a bad contact somewhere.

Tested on my dead I9070: no display, so the Xloader on my eMMC is garbaged (or Xloader UART debug is disabled, but this is less likely).

As expected, I now have to figure out how to have flashloader boot files upload *and* debug working together to understand what's wrong with my compiled boot files. I think the "trigger UART" thing is a good track, but I'm really puzzled by how to have the USB *and* the UART setup at the same time.
I fear to fry something by having phone D+/D- connected to USB port of the PC and connected at the same time to my Prolific TxD/RxD + 5V VCC connected to PC USB... sounds like a bad thing.

Another track would be USB debug I see in some parts of the code, but I don't know how to read the debug from there, more code to inspect...
The Following 2 Users Say Thank You to flentus For This Useful Post: [ Click to Expand ]
Junior Member
Thanks Meter 0
Posts: 13
Join Date: Jul 2014
got it~

---------- Post added at 02:03 PM ---------- Previous post was at 01:22 PM ----------

I also have a fully bricked I9070( not I9070P).I`m waiting for your good news.Thanks first.
Paul L.
Paul L.'s Avatar
Senior Member
Thanks Meter 3768
Posts: 841
Join Date: Nov 2011
Location: Mendoza, Argentina
I received this PM, I believe it can be useful for others experimenting with it

Originally Posted by flentus
Ola Paul,

I contact you on an advise from Cocafe.
I launched a while ago the thread "[Workshop] Unbrick fully bricked I9070" (
I'm looking for help to acheive the task as I don't have very much time to spend on it due to huge work I have this year.

Would you be ok to participate if you have a little spare time and interest in it?
I think I'm very close to the solution, and this would help a lot of 9070 owners (and maybe SIII mini and Sony too).

As explained in my thread, I have difficulties getting the disclosed sources to build correctly up to the end when integrated with Google SDK. As a result the "finalizing" scripts (that gather the binaries and tidy the "out" directory) don't execute: I end up with a large mess and STE tools don't work out of the box. I have to gather the pieces one by one to have them run which is very time consuming and error prone.

I can say that the recovery process won't need any kind of soldering, wiring or whatever: just a regular USB cable and the right sofware.
The disclosed sources contain everything we need: PBL/SBL sources, signing tool+certificates, the software to talk to the iROM + various documentation.
The problem is just a question of assembling the pieces...

My idea is to assemble an Xloader (PBL) + Uboot (SBL) + recovery and boot from that to execute recovery.
The "flashkit" tool enables this process, I quote the docs: "If 'programming' boot indication is used as boot indication, the PC will send a completely new set of boot code to the ME. This is used when a loader is downloaded during service mode startup via the Flash Tool Backend.".

Tell me if you wish to help me, or if you know someone who has competencies and would wish to!
I speek average spanish if you prefer to exchange in this language.

I am sorry for pointing this out, STE tools wont work ever on i9070, the reason being that we do not have a STE bootloader, heck, most of the low level stuff do not resemble the ST-Ericsson Montblanc development board. You can't even change the bootloader arguments, you can only add to them (the way I first enabled SELinux), the Samsung Bootloader version that we have may be not as restrictive as others, but Sonys bootloader resembles more to STE's than ours.

The only way you may found how to restore it is accessing the JTAG mode (something that is determined only if JTAG is connected and recognized) and depends solely on the emergency bootloader (if that exists, because I am not sure how the device powers on without PBL), the "seconds" of power you get on the USB is the device looking for JTAG.

The "disclosed" sources are for ST-Ericsson devices

Something you should do, is analyze the structures of /dev/block/mmcblk0p10, which contains our partition table (GUID Partition Table - GPT).

Simple way of doing it, you have to do dd if=/dev/block/mmcblk0p10 of=/sdcard/janice.pit on terminal emulator, this is ROM agnostic, because the structures are the same on both stock and any custom ROM. Of course, that is from a working device, I'll do that and drop it here later since I am working on something else right now, and thanks diegoch for discovering this.

Anyway, as diego pointed to me, our partition table is like this.

PIT, CSPSA, EFS, MODEM fs, SBL, SBL2, PARAM, IPL modem, MODEM, Kernel, Kernel2, system, data, cache, preload, fota, sdcard

This is the correct order I believe, since basically, when you use ODIN and use a PIT file, the partition table gets rewritten according to whatever is on that .pit file. So PIT is basically the GPT partition table; obviously SBL is the Samsung bootloader, and SBL2 I believe it's either stage 2.5 or a backup of the first.

So, no clue by going the STE way, something familiar here.

So, I may say something good at the end, see if the i9100 guys ever did it, and go from there, since our device is largely based around i9100 (Galaxy S II)
Desire. Discipline. Dedication.
Samsung Galaxy S Advance GT-I9070
Samsung Galaxy Mini GT-S5570
Acer Iconia Tab 500
Sony Xperia Live with Walkman
Motorola Defy
Motorola Moto G
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes