yashsingh1/xdaforums huggingface dataset:
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] force70:
Sure does!
[ZTE Grand X V970] mickeygriman:
Hello my zte v970 screen looks very dull with colors as dead can do to improve
[7" Kindle Fire HD General] shugs81:
Well.... no effing clue whats happened.... it must've updated recently as no longer rooted or using golauncher... getting rather annoyed at the inability to access the internal storage via usb...

Windows brings up a massive message that when i googled it the fix was to apparently unplug the pc.... which resolved a few issues but still get the same issues with the kindle... which sucks.... managed to connect briefly with Linux but now it just seem to not acknowledge it at all....

I had what i thought were the latest drivers as i only installed them a couple of days ago.. (rediscovered scummvm!!!)

Any ideas what I can do? I want to re root and flash a totally new rom as the amazon one is truely awful

And which is the best root method for 7.4.6? If there is one....

Thanks again peeps!
[7" Kindle Fire HD General] LinearEquation:
You would probably benefit most by using KFFA to return to 7.2.3 then root, remove OTA updates and install GApps. This way when you go to install a custom ROM, you have a matching boot loader. In order to put a custom ROM on, you need to flash a 2nd boot loader and TWRP. All this is covered in great detail on here. If you have questions do ask.
[7" Kindle Fire HD General] elyorch:
I recommend Paranoid Android indeed!
[Tizen Software Development] skim0322:
I've been following Tizen development fir a while now and was wondering if there are any ports to Samsung Galaxy S3? I expected there to be a port for this device already seeing as how its the same device they handed out to the developers.
[Tizen Software Development] adfree:
Nice idea...

But many unsolved problems...

RD-PQ is labeld with I9300A... yes...

But Call and GPS is for instance disabled...

Nobody knows or want tell us, if Hardware is 1:1... acccept Display...

Then Security is much higher in I9300...

Generally it seems JTAG is locked by password... so only SD card reanimation seems to work...

I9300 seems not cheap enough to do stupid tests... :D

Tizen is not finished...

Only funny rumours...

Only few Devs with RD-PQ...

The other RD210 is "obsolete"...

Too much work for nothing...

Too risky to brick I9300...

Maybe 2014, if Tizen is REALLY on market somewhere... with Tizen store open etc.

Then maybe I9300 cheap or worthy enough to try porting...

Anyway...

Feel free to find faster solution to flash RD-PQ Firmware for tests...

At your own risk.

http://xdaforums.com/showpost.php?p=44162575&postcount=12

All Software floating somewhere around...

Bootloader, Flasher, Firmware etc...

Best Regards
[Tizen Software Development] ash99:
There's nothing at present. Once Tizen matures and hopefully internal builds leak out we may be in luck. Lots of unknown variables at present.
[Tizen Software Development] adfree:
http://www.youtube.com/watch?v=F_Z1CKU0fpk#t=63

Maybe this Video could give also few answers, why I9300 is not first choice to play with Tizen... :D

It seems limited in repair solutions...

I9300 I think is pretty secured in Bootloader, to prevent other OS to execute...

If you make mistakes... as Tizen needs special Boot... you have an little problem.

Not everyone is able to reanimate via SD card nor be able to replace any SMD parts... :eek:

In Video you can hear Qualcomm... :D

So I think this is 1 reason, why RD-PQ has no working Baseband nor GPS...

Also I think, Tizen Software for Calling/GPS is not public...

To integrate MODEM functions of your own... see "our" Android port to bada...

Over 2 years...

Best Regards
[Tizen Software Development] adfree:
http://www.ebay.de/itm/Samsung-Gala...3?pt=LH_DefaultDomain_205&hash=item3f2fde814d

Maybe such Live Demo Unit easier to flash with Tizen RD-PQ Firmware...

Caution, this device on ebay seems NOT working...

No idea if Download Mode is available or...

Best Regards
[Tizen Software Development] adfree:
http://xdaforums.com/showpost.php?p=54749533&postcount=4

Oh, not realized that Gear SM-V700 have maybe same CPU...

Exynos 4212

Maybe sboot.bin is flashable...

:confused:

Okay, at this moment maybe total stupid nonsense to try with I9300...

But maybe next year... 2015...

2015... the year of Tizen... or maybe 2025... :D

Best Regards
[Tizen Software Development] adfree:
http://xdaforums.com/galaxy-s3/help/help-gt-i9300-sgh-i747-bootloader-t2923668

I have now time and few PCBs from I9300 to do few stupid tests... :D

Need to start from scratch... :rolleyes:

Maybe DIRECT EMMC stuff ((JTAG)) would be mandatory to change Bootloader:

[B]sboot.bin[/B]

I am not uptodate now... but I can't find any Bootloader tweaking threads with custom boot...

But I am charging now batteries for tests. :D

Best Regards

Edit 1.

Memo to me:

http://xdaforums.com/galaxy-s3/orig-development/util-sboot-checker-simple-downgrade-t2081748

http://xdaforums.com/galaxy-s3/general/how-to-flash-to-bootloader-updated-t2083860

Edit 3.

http://xdaforums.com/showpost.php?p=50638048&postcount=68

Very Helpfull and for study.

http://xdaforums.com/showpost.php?p=55514573&postcount=36

:good:

Edit 4.

http://xdaforums.com/galaxy-s3/general/ref-gt-i9305-hardware-hacking-t2939891
[Tizen Software Development] adfree:
Memo to me...

Checklist... :D

Download JIG... for Download Mode

Because I have no Volume keys...

And I have again no working Display for test PCBs...

Blind again...

Odin I have...

Firmware...

I9300XXDLI8_I9300OXADLI8_I9300XXDLI8_HOME.tar.md5

<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXDLI8_I9300OXADLI8_I9300XXDLI8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> modem.bin
<ID:0/004> system.img
<ID:0/004> hidden.img
<ID:0/004> tz.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Completed..
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
<ID:0/008> Added!!

Now I need Firmware with Root or ...

Need stock not custom and not latest... better older stuff... an oldest Boot...

...

Need time for study and search...

Best Regards
[Tizen Software Development] adfree:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXDLI8_I9300OXADLI8_I9300XXDLI8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> modem.bin
<ID:0/004> system.img
<ID:0/004> hidden.img
<ID:0/004> tz.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Completed..
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!

My I9300 is working with Odin, but for now not start into Android...

:rolleyes:

Seems I have killed some Security thingie... maybe I have erased IMEI or something in this direction...

I can't see Display output... because my test I9300 is with broken Display...

Maybe next days or week I will buy micro USB to HDMI Adaptor and check if this work only if Android is fully booted or if this is Hardware feature... and you can see Download Mode on TV...

:confused: :D

Best Regards

Edit 1.

Next stupid test with Odin 3.07...

<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> [B]Erase[/B]...

No idea yet... wait...

Edit 2.

Fixed my starting problem... by writing EFS via Odin...

I9300_Repair_efs.tar.md5

:cool: :angel:

Now I can try again stupid things... :D
[Tizen Software Development] adfree:
http://xdaforums.com/showpost.php?p=36506680&postcount=99

Now I have XXALE8 sboot.bin...

First I checked only sboot, param and tz with other Firmware...

result off dd mmcblk0p1 is empty sboot.bin dump...

But...

http://xdaforums.com/showpost.php?p=36418798&postcount=63

Now I flash fully XXALE8... and check agin if dump is empty...

Best Regards

Edit 1.

Hmmm... still sboot.bin dump empty...

Now checking mmcblk0 dump...

Nice sideeffect of XXALE8... I have now fully access again to my test I9300 PCB

:good: :cool:

Before stucked on Samsung Logo and not fully booted...

No idea when I have killed IMEI, EFS, Security etc... :o
[Tizen Software Development] adfree:
Blind tests with broken Display are very hard... I have to buy working Display for further tests...

So I can see what is written on Screen...

For now it seems with DD it is possible to write sboot... into mmcblk0p1...

Also s-boot-mmc.bin from Tizen RD-PQ "accepted"... Android starts...

My test device have also no Volume + and - key...

So I have to collect all spareparts and repair my test device to work proper ... so I can see what is on Screen visible...

If really sboot aka s-boot-mmc.bin is written. So in theory other key combinations for SD Card support should work...

RECOVERY MODE
-when second bootloader was broken.
-select volume up/down key
and enter the mode using power key.

From SD Card
-Recovery 2nd bootloader from
sd card

From Internal Card
-Recovery 2nd bootloader from
internal card that image is fused
at shipped

Exit

This text can be found in 300 KB s-boot-mmc.bin...

Hmmm...

u-boot-mmc.bin seems the second Bootloader... in my opinion...

I need deeper check available dump from RD-PQ and compare with I9300 dump...

Maybe uboot is in position of TZ or PARAM...

:confused:

Best Regards
[Tizen Software Development] adfree:
Download Mode key combo looks different for I9300 and RD-PQ

I9300:

Step 4. Set your phone in download mode (Turn off phone, then hold Volume Down+Home+Power button simultaneously) Then it ask you to press a Volume Up button to continue.

3 keys + 1 for confirm...

RD-PQ:

https://wiki.tizen.org/wiki/Reference_Device-PQ

2 keys only...

If I have working Display so I will repair also all keys...

For now I have no working key... only Power... Volume + and - is absent/missing...

Home key seems damaged...

For DL Mode I have simple USB JIG... plug in and it is working.

:good:

Short analyze of dump.bin from RD-PQ... and compared with my dump of mmcblk0...

S3 Android	Tizen RD-PQ dump
0000 0000	- 512 Byte header + EFI stuff
0000 4400	- PIT file	0x8000
- ??? data
0001 0000 - end - 0000 zero/empty	uboot

PIT File is on differnt position... uboot starts at 0x10000 in RD-PQ... and I9300 have 12 MB empty space at this position...

AND very funny... I made in my working I9300 again dd dump... and I saw Tizen PIT is not overwritten, also it seems uboot is not overwritten/deleted... :D

I must wait for my spareparts... Display and keys... before I proceed with my experiments...

Best Regards
[Tizen Software Development] adfree:
16 GB external SD card

shell@android:/mnt/extSdCard # dd if=/dev/block/mmcblk0 of=/mnt/extSdCard/dumpFULL1.bin
of=/mnt/extSdCard/dumpFULL1.bin <
/mnt/extSdCard/dumpFULL1.bin: write error: [B]File too large[/B]
8388608+0 records in
8388607+1 records out
4294967295 bytes transferred in 382.610 secs (11225444 bytes/sec)

:confused:

internal memory...

shell@android:/ # dd if=/dev/block/mmcblk0 of=/sdcard/dumpF_v2.bin
dd if=/dev/block/mmcblk0 of=/sdcard/dumpF_v2.bin
/sdcard/dumpF_v2.bin: write error: No space left on device
22945825+0 records in
22945824+0 records out
11748261888 bytes transferred in 2501.178 secs (4697091 bytes/sec)

I am trying meanwhile to dump maximum...

sdcard is limited by free space... so I can "only" dump 11 GB.

I can find param often...

S3 Android	Tizen RD-PQ dump
0000 0000	- 512 Byte header + EFI stuff
0000 4400	- PIT file	0x8000
- ??? data
0001 0000 - end - 0000 zero/empty	uboot

0200 0000	PARAM 1
D600 0000	PARAM 2
0E48 0000	PARAM 3
1C78 0000	PARAM 4
1D70 0000	PARAM 5

tz not found yet in 11 GB...

Maybe sboot and tz is in last 5 GB... at end of file?

I have tested external 16 GB card... here after 4 GB finish... no idea yet why... maybe FAT limitation...

Maybe need to format via I9300...

:confused:

Will proceed with study...

Best Regards

Edit 1.

Memo to me.

For repair Display + Volume keys...

https://www.youtube.com/watch?v=Rt8bl7oAPVU
[Tizen Software Development] adfree:
This looks funny...

bootargs=Please use defined boot bootcmd=run mmcboot bootdelay=0 baudrate=115200 checkpit=if test ${pit_ver} = 13; then setenv mmcbootpart 2;setenv mmcrootpart 11;setenv mmccsapart 4;else setenv mmcbootpart 2;setenv mmcrootpart 5;setenv mmccsapart 1;fi; bootk=run loaduimage; bootm 0x40007FC0 updatemmc=mmc boot 0 1 1 1; mmc write 0 0x50800000 0 0x800; mmc boot 0 1 1 0 updatebackup=mmc boot 0 1 1 2; mmc write 0 0x51000000 0 0x400; mmc boot 0 1 1 0 updatebootb=mmc read 0 0x51000000 0x80 0x800; run updatebackup updateuboot=mmc write 0 0x50000000 0x80 0x800 updaterestore=mmc boot 0 1 1 2; mmc read 0 0x50000000 0 0x800;mmc boot 0 1 1 0; run updateuboot setupboot=run updatemmc; run updateuboot; run updatebootb mmcboot=run checkpit; set bootargs root=/dev/mmcblk0p${mmcrootpart} rw rootfstype=ext4 rootwait ${console} ${meminfo} ${debuginfo} ${bootmode} ${lcdinfo} ${muicpathinfo} ${lpjinfo} ${opts} csa=/dev/mmcblk0p${mmccsapart}; run loaduimage; bootm 0x40007FC0 bootchart=set opts init=/sbin/bootchartd; run bootcmd boottrace=setenv opts initcall_debug; run bootcmd verify=n rootfstype=ext4 console=console=ttySAC2,115200n8 mbrparts=8M(csa),60M(boot),60M(qboot),1G(platform),3G(data),150M(csc),-(ums) meminfo=fbmem=24M@0x52000000 kernelname=uImage loaduimage=ext4load mmc ${mmcdev}:${mmcbootpart} 0x40007FC0 ${kernelname} mmcdev=0 opts=resume=179:3 uartpath=ap usbpath=ap pit_ver=13 silent= ramdump=both ver=U-Boot 2011.03 accepted/tizen/2.3/wearable/20141031.071205-1-g61220ee (Nov 25 2014 - 23:11:35) SLP_VAR_PART=csa /dev/mmcblk0p1 /csa ext4 data=journal SLP_LCD_LEVEL=0 SLP_SWITCH_SEL=0 SLP_NATION_SEL=0 SLP_ROOTFS_NEW=0 SLP_KERNEL_NEW=0 SLP_FLAG_RTL=0 SLP_FLAG_FUS=0 SLP_FLAG_FOTA=0 SLP_FLAG_EFS_CLEAR=0

Taken from param.bin inside migrate_2.3_bootloader.tar... found here:

https://wiki.tizen.org/wiki/Flash_Tizen_2.3_Image_to_Reference_Device

download.tizen.org/releases/2.3/2.3-mobile/bootloader/migrate_2.3_bootloader.tar.gz

Maybe for study also the other file interesting...

http://download.tizen.org/releases/2.3/2.3-mobile/bootloader/

Best Regards
[Tizen Software Development] Korgan1983:
I hope your stupid stuff will work on i9300, I will test it definitly ;)
[Tizen Software Development] adfree:
After I read this...

I've searched via Google for Download Mode RD-PQ... and found this Pic...

Now with my knowledge that Odin checks text string ODIN... which is in sboot...

And Thor checks text string THOR.. which we can find in uboot...

So what I need is to find way to execute uboot on I9300...

I have no idea, if sboot from RD-PQ is really written... because I can not find text string ODIN inside...

:confused:

Still waitng for my working Display to see something... :D

Other stuff...

Taken from here:

https://forums.oneplus.net/threads/partition-info-and-dd-backup.49114/page-2

I hope this info will help me... to dump whole 16 GB... in near future... for study...

Best Regards
[Tizen Software Development] adfree:
I was able to identify uboot in this RD-PQ dump:

http://xdaforums.com/showpost.php?p=55514573&postcount=36

http://download.tizen.org/releases/system/

http://download.tizen.org/releases/system/Tizen_RD-PQ_System_20130716_1.tar

In Tizen_RD-PQ_System_20130716_1.tar included u-boot-mmc.bin can be found 1:1 at address:

0x10000

uImage (Kernel) found at:

0xD43C00

modules.img not found in this 32 MB dump...

No idea yet, for what modules.img is used...

:confused:

Best Regards

Edit 1.

Some data of modules.img seems near 0x13C0400...

Maybe some Header of file is written somewhere else...

Will check later...

Edit 2.

modules.img seems Kernel related...

https://wiki.tizen.org/wiki/Porting_Guide/Getting_Source_Code&Build

Short checked uimage (Kernel) in dump...

Seems not 1:1 written like file content uimage...

Maybe spare data or decompressed... or something else... too lazy now to check...
[Tizen Software Development] adfree:
Memo to me...

http://xdaforums.com/showpost.php?p=47234165&postcount=220

SDCARD MODE
COPY BINARY FROm SDCARD..
COPY BINARY TO EMMC..
SDCARD DOWNLOAD COMPLETED.

Will check sboot.bin for these text strings...

Later more...

Meanwhile I am trying to split dump... to get whole 16 GB eMMC with internal sdcard space...

dd if=/dev/block/mmcblk0 skip=0 count=10000000 of=/sdcard/dump_v1.bin
dd if=/dev/block/mmcblk0 skip=10000000 count=10000000 of=/sdcard/dump_v2.bin
dd if=/dev/block/mmcblk0 skip=20000000 of=/sdcard/dump_v3.bin

Need an while to check if this is working... proper...

Theory...

first 5 GB... then second 5 GB... then last 6 GB...

Remember, only 11 GB free space... so not possible at 1 move...

I need only the last 6 GB for my study... first 11 GB I have allready...

Best Regards

Edit 1.

Memo to me...

1 test could be change THOR string into ODIN in 1Click Thor for Windows...

To see if Protocol is maybe same...
[Tizen Software Development] adfree:
Must wait for my working display... :(

Meanwhile short stupid test...

<ID:0/004> Added!!
<ID:0/004> Thor engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)

2.1.0_public.exe edited text string THOR ROHT into ODIN NIDO ...

ThorOneClick...

RD-PQ-REF-RSA_2.2.0_RC11_WiFi.exe if I remember correct have same Thor Version...

Maybe next time I'll sniff USB to see what is sent and received...

Best Regards
[Tizen Software Development] scholbert:
Hi adfree!

I had a look into the binary, these strings are not included, but there are similar messages... at least it should be possible to recover u-boot in the public area of emmc.

The problem would be to get SLP programmed right in place.

As i refered to in my tech thread about i9305, sboot is placed in the BOOT area of eMMC on all latest devices.

Could be, that there where some early devices, which used some other mode to boot from eMMC, which is much closer to boot from a SD-card.

Anyway, would be interesting to create a bootable MicroSD with SLP bootloader, block onboard eMMC with the tweezer trick and see what happens.

Would be best to get a real UART connection to the board for these experiments.

This way you're always connected and no need to fiddle around with this resistor stuff ;)

It's nice that you try to make a whole dump for research, but the secret of boot process relies on the very first sectors and parts in eMMC.

The most interesting question would be if SLP bootloader will be executed on production units once in the right place. As you might know all primary bootloaders for Exynos are signed to match the silicon.

There's a root key stored in the Exynos e-fuse area at 0x10100000, but i never got access to these registers from userland.

If this key from a production unit is identical to RD-PQ it's fine.

Otherwise signed SLP would never get executed on standard S3.

Another thing to mention is that TZSW is an essential part on production units.

So sboot and TZSW have always play together here nicely.

On RD-PQ there's only SLP bootloader which is signed.

So it seems that afterwards the world is nearly open... maybe trustzone is used at another stage or different security mechanism is used in Tizen.

My conclusion is, that if SLP is accepted and we'll find a proper setup for the rest of eMMC, this will be it :good:

EDIT:

Just found this thread again, which gives some insights on low level boot mechanism on Exynos 4.

http://forum.odroid.com/viewtopic.php?f=51&t=1365

Keep on having fun!!!

scholbert
[Tizen Software Development] adfree:
:o

You could be right...

Stupid me did few "mistakes"...

1 mistake to try with broken Display and to see nothing... but... :rolleyes:

Yesterday I did few tests...

1.

Downloaded and installed App:

System Info for Android

http://xdaforums.com/showpost.php?p=36441074&postcount=73

With ADB related Tool:

[B]Ultimate touchscreen control for android[/B]

http://xdaforums.com/showthread.php?t=2786395

I've made Screenshots...

2.

getprop ro.boot.bootloader

App confirms this ADB shell output...

I have no idea, what I did to see nothing...

Maybe I was drunken or complete tired... :o

So App confirms this putput... :good:

And it seems not Kernel related... as old Firmware XXALE8 shows this too.

3.

To be sure, sboot.bin checks integrity...

I've made few tests...

Changed few textstrings in sboot.bin...

Then I have tried other sboot.bin from Gear SM-V700...

http://xdaforums.com/showpost.php?p=54797252&postcount=6

Nothing killed my I9300 and not changed because sboot ignores these attempts...

And I have totally forgotten... :o

sboot.bin and PIT is signed by RSA 2048 key...

256 Byte signature at end of file...

RD-PQ sboot.bin is NOT signed... :rolleyes:

Summary...

unsigned or modified sboot.bin not accepted from I9300 Retail because RSA selfcheck...

Hmmmmm... this brings me back to Live Demo Unit...

Maybe here is unsigned boot + PIT possible...

http://xdaforums.com/showpost.php?p=31587295&postcount=47

:confused:

No idea if booting from SD card or tweezers trick allow modified or unsigned Code:

https://www.youtube.com/watch?v=JXvOcGJ6zXo

Or maybe it is possible to erase public key from I9300 Retail...

:confused:

:confused:

I have 2 Live Demo Unit PCBs I9300X ...

But I can not dump sboot.bin to check if it is signed or not... :rolleyes:

I hope this week I got my working Display... to proceed...

Best Regards
[Tizen Software Development] adfree:
Looks like S3 for me...

:confused:

http://www.tizenexperts.com/2015/05/leaked-images-of-the-upcoming-samsung-z2-tizen-smart-phone/

P.S.:

Meanwhile I have working Display for further tests with I9300... but I am too lazy... :o

I have seen interesting Pics here about PCB:

https://developer.tizen.org/forums/general-support/micro-sim-support-under-rd-pq-device

Best Regards
[Tizen Software Development] skim0322:
Are you stopping with the development? If not, are there any advancements?