well i was excited to install android on my watch samsung gear sm-r750 so downloaded the rom and all the files needed , took a backup of my sysdata and everything was fine , flashed the custom recovery and i tried to boot in it and it worked then i tried flashing the cm12.1 that's when i got a huge prob , the clock got stuck at samsung logo , i waited and waited but it won't boot to system tried to go to recovery but even the recovery got stuck at the start blue screen , tried to restore the watch using restore to tizen file but when i try to flash i get this <ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1401)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 968 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> system-data.img
<ID:0/005> FAIL! (WP)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
i searched all over the internet for the official rom of the watch using the serial number and all the info but every time i try to flash a rom i fall into the same thing and it show the same thing anyone can help and i appreciate it for real i will provide u with everything u need
sm-r750
Click to expand...
Click to collapse
Can you search for SM-R750 Combination Firmware?
I have still limited time... here for instance:
https://shell.boxwares.com/default.aspx?DeviceModel=SM-R750&Type=All#fh5co-table
"We" need valid package... i can can remember trouble with corrupted downloads...
Please check for me...
Goal is to flash Combination Firmware and/or parts of it...
To see what is damaged...
Best Regards
adfree said:
Can you search for SM-R750 Combination Firmware?
I have still limited time... here for instance:
https://shell.boxwares.com/default.aspx?DeviceModel=SM-R750&Type=All#fh5co-table
"We" need valid package... i can can remember trouble with corrupted downloads...
Please check for me...
Goal is to flash Combination Firmware and/or parts of it...
To see what is damaged...
Best Regards
Click to expand...
Click to collapse
thanks well i was looking for the model and i found out that my watch is made in vietnam and bought from germany so downloaded germany package , tryied flashing every file but still no chance :/
tryied flashing every file but still no chance :/
Click to expand...
Click to collapse
Can we try to focus... on Combination Firmware?
Sorry I have only limited time and energy...
Goal is to bring back working OS...
Again.
A
Combination Firmware...
Give me Link what you have... or write Filename...
So we can research in same files...
WITHOUT force me to upload.
B
If you select/found/choose Combiantion Firmware... we can unpack repack...
Create new TAR files for Odin with less files...
I hope you know you can flash less files...
C
Bootloader seems okay...
Otherwise you can not flash...
But maybe PIT is wrong or something else is broken or Hardware damage...
It is not impossible that eMMC dies...
Best Regards
adfree said:
Can we try to focus... on Combination Firmware?
If you select/found/choose Combiantion Firmware... we can unpack repack...
Create new TAR files for Odin with less files...
I hope you know you can flash less files...
C
Bootloader seems okay...
Otherwise you can not flash...
But maybe PIT is wrong or something else is broken or Hardware damage...
It is not impossible that eMMC dies...
Best Regards
Click to expand...
Click to collapse
the combination firmwares i tryed were these 3 for model SM-R750 the 3 of them don't work start download then show error repartition
R750XXU1AOB1
R750XXU1AOB1
R750XXU2BOF1
the problem is that i only know the model of the watch but not whish firmware work with it , tried to find it using country but no chance anyway i'll tell u exactly what i tried , i tried all 4 parts rom that i found no one works, but back to the combination firmware , the problem is that i don't know whish security lvl it is , the only thing i found is the model number on the donwload screen :
odin mode
product name : SM-R750
current binary : custom
system status : official
qualcomm secureboot: enable
RP SWREV : S2 T1 R1 A1 P1
secure download : enable
Write protection : enable
when i download the rom nothing show on the screen of the watch except it starts loading and stop and in odin it shows the error , tried flashing a csc partition , the green bar reach the end then show fail
Code:
odin mode
product name : SM-R750
current binary : custom
system status : official
qualcomm secureboot: enable
RP [B]SWREV : S2[/B] T1 R1 A1 P1
secure download : enable
Write protection : enable
In this Mode we can see it is allready Software Revision 2 Bootloader on Device...
Remember Samsu.g Rollback Prevention Crap...
So 2 of 3 files are simple WRONG.
Code:
R750XXU[COLOR="Red"][B]1[/B][/COLOR]AOB1
R750XXU[COLOR="Red"][B]1[/B][/COLOR]AOB1
R750XXU[COLOR="Green"][B]2[/B][/COLOR]BOF1
Okay, I will download this file... so maybe we can proceed with tests...
All I know at the moment.. this is Qualcomm crap...
My QC times are long ago...
Best Regards
I have now this as reference...
Code:
COMBINATION-FTMA_R750XXU[COLOR="Green"][B]2[/B][/COLOR]BOF1_BoxWares.tar.zip
Code:
aboot.mbn
csc.img
dzImage
dzImage-recovery
modem.bin
modules.img
Ponte-EUR-OPEN-4G-v9.pit
ramdisk-recovery.img
rootfs.img
rpm.mbn
sbl1.mbn
sdi.mbn
system-data.img
tz.mbn
user.img
I have taken the csc.img and create TAR file...
Can you try to flash and report Odin Log?
Thanx in advance.
Best Regards
adfree said:
I have now this as reference...
Code:
COMBINATION-FTMA_R750XXU[COLOR="Green"][B]2[/B][/COLOR]BOF1_BoxWares.tar.zip
Code:
aboot.mbn
csc.img
dzImage
dzImage-recovery
modem.bin
modules.img
Ponte-EUR-OPEN-4G-v9.pit
ramdisk-recovery.img
rootfs.img
rpm.mbn
sbl1.mbn
sdi.mbn
system-data.img
tz.mbn
user.img
I have taken the csc.img and create TAR file...
Can you try to flash and report Odin Log?
Thanx in advance.
Best Regards
Click to expand...
Click to collapse
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1401)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 5 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> csc.img
<ID:0/005> FAIL! (WP)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and btw the download bar reached the end ( the green one )
adfree said:
I have now this as reference...
Code:
COMBINATION-FTMA_R750XXU[COLOR="Green"][B]2[/B][/COLOR]BOF1_BoxWares.tar.zip
Best Regards
Click to expand...
Click to collapse
well i have tried to make tar files of all the imgs inside the rom , somefiles like recovery and csc compleatly download before showing failed , the green bar reachs the end , for some files like rootfs and and system data it starts downloading then the green bar stuck at the beginning , can it be kind of a faulty partition ? odin can't find space to extract the tar files after downloading them so it fails
Sorry, nearly no time nor energy to spent toooo much time with your problem.
Suggestion.
Dump PIT file from Watch... Partition stuff...
As you have USB cable...
Try Tool Heimdall for instance...
https://forum.xda-developers.com/showthread.php?t=755265
Best Regards
Related
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.
Sent from my GT-I9300 using xda app-developers app
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...
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://forum.xda-developers.com/showpost.php?p=44162575&postcount=12
All Software floating somewhere around...
Bootloader, Flasher, Firmware etc...
Best Regards
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.
Sent from my SM-N9005 using Tapatalk now Free
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...
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...
In Video you can hear Qualcomm...
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
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
http://forum.xda-developers.com/showpost.php?p=54749533&postcount=4
Oh, not realized that Gear SM-V700 have maybe same CPU...
Code:
Exynos 4212
Maybe sboot.bin is flashable...
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...
Best Regards
GT-I9300 with SGH-I747 BOOTLOADER
Click to expand...
Click to collapse
http://forum.xda-developers.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...
Need to start from scratch...
Maybe DIRECT EMMC stuff ((JTAG)) would be mandatory to change Bootloader:
Code:
[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.
Best Regards
Edit 1.
Memo to me:
http://forum.xda-developers.com/gal.../util-sboot-checker-simple-downgrade-t2081748
How to downgrade boots on XXELLA or XXELLC and bypass the blacklist (or any other boot in existence as of this post)
(USE THESE COMMANDS AT YOUR OWN RISK)
> adb push sboot.bin /sdcard/sboot.bin
> adb push tz.img /sdcard/tz.img
> adb push param.bin /sdcard/param.bin
> adb shell
$ su
# dd if=/sdcard/sboot.bin of=/dev/block/mmcblk0p1
# dd if=/sdcard/tz.img of=/dev/block/mmcblk0p2
# dd if=/sdcard/param.bin of=/dev/block/mmcblk0p4
# rm /sdcard/sboot.bin
# rm /sdcard/tz.img
# rm /sdcard/param.bin
# reboot fota_bl
Click to expand...
Click to collapse
Flash back to old bootloader after updated new bootloader XXELLA
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-s3/general/how-to-flash-to-bootloader-updated-t2083860
Edit 3.
http://forum.xda-developers.com/showpost.php?p=50638048&postcount=68
AT+HIDSWVER?
Code:
I9300XXALE8/I9300PAPALE5/I9300XXLE8/I9300XXALE8
Click to expand...
Click to collapse
Very Helpfull and for study.
http://forum.xda-developers.com/showpost.php?p=55514573&postcount=36
:good:
Edit 4.
http://forum.xda-developers.com/galaxy-s3/general/ref-gt-i9305-hardware-hacking-t2939891
Memo to me...
Checklist...
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
Code:
<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
Need more time to understand...
But ist seems.
dd stuff works to write something...
I mean this stuff...
http://forum.xda-developers.com/gal.../util-sboot-checker-simple-downgrade-t2081748
I have not found way to check/dump mmcblk0p1... to confirm sboot.bin is written...
But 1 stupid test seems successfully...
I have written s-boot-mmc.bin from RD-PQ to sboot.bin partition mmcblk0p1
About result... not 100 % sure because I see nothing on Display... (damaged Display...)...
But I was not able to write after this action sboot.bin via Odin...
But all other Flash stuff worked with Odin... so I9300 was not bricked...
Also booting to Android ADB stuff...
After I have restored all 3 partitions with original I9300 stuff...
Code:
# dd if=/sdcard/sboot.bin of=/dev/block/mmcblk0p1
# dd if=/sdcard/tz.img of=/dev/block/mmcblk0p2
# dd if=/sdcard/param.bin of=/dev/block/mmcblk0p4
Odin allowed to write successfully GT-I9300_Boot_Recovery.tar
Code:
<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> sboot.bin
<ID:0/004> NAND Write Start!!
<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!!
After this I have checked again dd stuff... and modified param.bin, because mmcblk0p4 you can dump...
Short test with LO changed into HI for High Debug Mode... and changes visible...
Later I will try to check again s-boot-mmc.bin...
If you dump mmcblk0 you can find Header of eMMC...
Best Regards
dd and partition investigation...
Code:
[email protected]:/ # dd if=/dev/block/mmcblk0p3 of=/sdcard/noidea1.bin
dd if=/dev/block/mmcblk0p3 of=/sdcard/noidea1.bin
40960+0 records in
40960+0 records out
20971520 bytes transferred in 12.835 secs (1633932 bytes/sec)
[email protected]:/ #
What is in mmcblk0p3 and can I dump it...
mmcblk0p1 is only 0000/empty if you dump...
Code:
C:\adb>adb pull sdcard/noidea1.bin
6687 KB/s (20971520 bytes in 3.062s)
I can open with WinHex... 20 MB and see some content... no idea what it is yet...
---------- Post added at 02:08 PM ---------- Previous post was at 01:30 PM ----------
http://forum.xda-developers.com/showpost.php?p=55514573&postcount=36
I am drunken enough to test dump.bin from RD-PQ to write to I9300...
Will post result...
Steps...
- dump.bin copy to I9300 via ADB...
- ADB shell, su, dd... blabla...
Something like this:
Code:
[B]d[/B]anger[B]d[/B]anger if=/sdcard/dump.bin of=/dev/block/[B]mmcblk0[/B]
Okidoki... soon I know what happens...
Best Regards
Edit 1...
Code:
C:\adb>adb push dump.bin sdcard/dump.bin
5165 KB/s (33554432 bytes in 6.343s)
C:\adb>adb shell
[email protected]:/ $ su
su
[email protected]:/ # dd if=/sdcard/dump.bin of=/dev/block/mmcblk0
dd if=/sdcard/dump.bin of=/dev/block/mmcblk0
65536+0 records in
65536+0 records out
33554432 bytes transferred in 3.514 secs (9548785 bytes/sec)
[email protected]:/ # reboot fota_bl
reboot fota_bl
Hmm... dump.bin is written with Error from ADB... this means not it is really 1:1 written...
Android not start... as it seems...
But I can activate Download Mode via JIG... now I am trying to write via Odin, as THOR for Win not detect...
But hey... this looks interesting...
Code:
<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>
<ID:0/004> [B]There is no PIT partition.[/B]
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Maybe this sboot.bin from Tizen allow unsigned PIT files...
Because PIT I think I have somewhere for Tizen RD-PQ...
Will test...
Best Regards
Edit again...
Original I9300 files work... PIT + sboot.bin
Code:
<ID:0/004> Added!!
<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> 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 other test before failed...
unsigned Tizen PIT + Tizen RD-PQ sboot...
Hmmmmmmmm... maybe necessary sboot from Tizen was not written with dump.bin ...
Will check later again...
Now I will try to flash all Firmwarefiles and check if I9300 is ADB alive...
Or I have something killed...
Code:
<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...
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...
Best Regards
Edit 1.
Next stupid test with Odin 3.07...
Code:
<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
:angel:
Now I can try again stupid things...
http://forum.xda-developers.com/showpost.php?p=36506680&postcount=99
Do you know why the posted XXALE8 bootloader is a little different from my own DDed bootloader in the area from 0x5800 to 0x58FF?
EDIT: Sorry, I was comparing to the ALF1 bootloader.
Would it be better for me then to use my own DDed ALF1 BL image?
Param-file and my own mmcblk0p4 dump is identical.
However my own mmcblk0p2 dump is completely empty.
Click to expand...
Click to collapse
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://forum.xda-developers.com/showpost.php?p=36418798&postcount=63
you can check which bootloader you have from adb or a terminal with:-
getprop ro.bootloader
Click to expand...
Click to collapse
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:
Before stucked on Samsung Logo and not fully booted...
No idea when I have killed IMEI, EFS, Security etc...
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...
Code:
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...
If you prepared the Sd-card, then do format the sd-card for vfat file-system.
1. You can find the u-boot-mmc.bin file at Tizen system image
2. copy the u-boot-mmc.bin file to SD-card. (When you copy, do rename from u-boot-mmc.bin to u-boot.bin)
#cp u-boot-mmc.bin /media/<mount_point>/u-boot.bin
3. After insert the Sd-card, enter the recovery mode.
4. Press dwn->up->pwr.
5. Select "recovery from external Sd-card"...
6. after recovery completed, reboot.
Remember!! there must be "u-boot.bin" at SD-card.
Click to expand...
Click to collapse
I need deeper check available dump from RD-PQ and compare with I9300 dump...
Maybe uboot is in position of TZ or PARAM...
Best Regards
Download Mode key combo looks different for I9300 and RD-PQ
I9300:
Code:
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
To go to download mode :
remove battery (optionnal)
unplug USB
press Power Button + VolDown Button simultaneously.
plug in USB
Click to expand...
Click to collapse
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...
Code:
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...
I must wait for my spareparts... Display and keys... before I proceed with my experiments...
Best Regards
16 GB external SD card
Code:
[email protected]:/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)
internal memory...
Code:
[email protected]:/ # 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...
Code:
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...
Will proceed with study...
Best Regards
Edit 1.
Memo to me.
For repair Display + Volume keys...
https://www.youtube.com/watch?v=Rt8bl7oAPVU
This looks funny...
Code:
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) [email protected] 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
I hope your stupid stuff will work on i9300, I will test it definitly
After I read this...
Flashing the boot image and the platform Image (unplug, poweron+VolDown, plug in USB : UBoot Mode)
Click to expand...
Click to collapse
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...
Still waitng for my working Display to see something...
Other stuff...
III. Pieces
Anyway let's keep it simple.
Splitting is in my case the solution... :
Code:
->adb.exe shell dd if=/dev/block/mmcblk0 skip=0K count=600K >InternalSD.img.000
->adb.exe shell dd if=/dev/block/mmcblk0 skip=600K count=600K >InternalSD.img.001
->adb.exe shell dd if=/dev/block/mmcblk0 skip=1200K count=600K >InternalSD.img.002
....
Click to expand...
Click to collapse
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
I was able to identify uboot in this RD-PQ dump:
http://forum.xda-developers.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:
Code:
0x10000
uImage (Kernel) found at:
Code:
0xD43C00
modules.img not found in this 32 MB dump...
No idea yet, for what modules.img is used...
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
Build and make kernel module image as well.
Click to expand...
Click to collapse
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...
Memo to me...
http://forum.xda-developers.com/showpost.php?p=47234165&postcount=220
Code:
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...
Code:
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...
Must wait for my working display...
Meanwhile short stupid test...
Code:
<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
Hi guys,
I have bricked my tablet, when i try to "Nand Erase All" it keeps failing, can someone explain the problem
Odin Log:
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Erase...
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
---------------------------------------------------------------------
Status:
-Device: Galaxy Note 10.1 N8000, not rooted, Debugging mode disabled so no ADB:crying:
-Bootloop, No recovery mode, Can access Download mode:good:
----------------------------------------------------------------------
What I have tried so Far
- Removed the battery ( didn't work)
- Flashed bootloader --> (Flashed Successfully but didn't work)
- Flashed CWM recovery -->(Flashed Successfully, battery off then on, but didn't work, still cant access recovery mode)
- Flashed Stock firmware -->(Flashed Successfully but didn't work)
-Flashed (Stock/custom recovery) with Pit file re-partition checked --> (Repartitioned and Flashed Successfully but didn't work)
-I read about that I need to check "Nand Erase ALL" ( with Pit file on) to erase cache and every corrupted file
so I tried but I kept failing giving the error mentioned above, So any explanation why "Nand Erase All" fails, and any other suggestions for my current situation
Thanks in advance
scorpiohyena said:
Hi guys,
I have bricked my tablet, when i try to "Nand Erase All" it keeps failing, can someone explain the problem
Odin Log:
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Erase...
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
---------------------------------------------------------------------
Status:
-Device: Galaxy Note 10.1 N8000, not rooted, Debugging mode disabled so no ADB:crying:
-Bootloop, No recovery mode, Can access Download mode:good:
----------------------------------------------------------------------
What I have tried so Far
- Removed the battery ( didn't work)
- Flashed bootloader --> (Flashed Successfully but didn't work)
- Flashed CWM recovery -->(Flashed Successfully, battery off then on, but didn't work, still cant access recovery mode)
- Flashed Stock firmware -->(Flashed Successfully but didn't work)
-Flashed (Stock/custom recovery) with Pit file re-partition checked --> (Repartitioned and Flashed Successfully but didn't work)
-I read about that I need to check "Nand Erase ALL" ( with Pit file on) to erase cache and every corrupted file
so I tried but I kept failing giving the error mentioned above, So any explanation why "Nand Erase All" fails, and any other suggestions for my current situation
Thanks in advance
Click to expand...
Click to collapse
Update:
currently I am using heimdall, Trying to create a Custom Pit to skip bad sectors in recovery and boot partitions, any experience in that would be helpfull.
I am trying to figure out the pit files parameter to create a custom working file
scorpiohyena said:
Update:
currently I am using heimdall, Trying to create a Custom Pit to skip bad sectors in recovery and boot partitions, any experience in that would be helpfull.
I am trying to figure out the pit files parameter to create a custom working file
Click to expand...
Click to collapse
Hi there did you had any success trying to unbrick your tablet ??, I'm experiencing the same issues as you.
I've a rooted Note 10.1 N8013 running on stock firmware.
I've tried everything, all left for me is trying "Nand erase all" . but it fails everytime
Thank you !!
hi gays
can you tell me if the problem of nand eras all fail was solved ?
I was on DRL6 and Pie, and tried to do the CRK1 to DRL6 through Odin 3.13 Patched version, went into Odin mode on the phone. Added BL + AP + CP + HOME_CSC like the tutorial stated, Odin said (success 0 / failed 2), so I assumed I didn't have Samsung drivers installed, closed out of Odin and installed the drivers, rebooted Odin it seemed like it was going to work because it went further than the other tries but then it failed at "Complete(Write) operation failed."
I tried different cords, USB ports, turned off Firewall.
So, I figured I'd leave it alone, restarted my phone and it noticed it wouldn't reboot. I unplugged it, and held down the power button which booted up:
[UPLOAD MODE]
Unkown Error
----------------------
DDR Vendor: Samsung
SOC_HW_REVISION: 2.1
skip print_summary_to_lcd..
Generating summary...
>> General Info
>> DDR Info
>> RPM
>> TrustZone
>> Hypervisor
Done!
[To PC] Connect a USB cable or
[To SD] Press VOL_UP + VOL_DOWN
Click to expand...
Click to collapse
Tried Odin while in the mode and now this is what I'm getting:
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> skip file list for home binary
<ID:0/003> apdp.mbn
<ID:0/003> msadp.mbn
<ID:0/003> persist.img.ext4
<ID:0/003> dqmdbg.img.ext4
<ID:0/003> Home Binary Download
<ID:0/003> Total Binary size: 4907 M
<ID:0/003> SetupConnection..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Edit: Got it into Download Mode, this is what I'm getting now.
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 4920 M
<ID:0/004> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Edit 2: Did some Googling, and seen that my cache could've been corrupted. So, I went back into Download mode, flashed just CSC in Odin, and my phone worked again. So, being stubborn, I flashed BL + AP + CP without CSC and my phone is now Optimizing App, then reboots and continues the cycle. I'm now back in Upload Mode and stuck, phone won't turn off or anything.
[UPLOAD MODE]
Unkown Error
DDR Vendor: Samsung
SOC_HW_REVISION: 2.1
RAM dump by hard reset
lastSns: 0x5a
Generating summary...
General Info
DDR Info
DCVS Info
Recovered from an exception
Done.
[To PC] Connect a USB cable or
[To SD] Press VOL_UP + VOL_DOWN
Synchronous Exceoption
lr: 0x0000000085e37228
sp: 0x000000001407bba0
pc: 0x0000000085e37288
Click to expand...
Click to collapse
Edit 3: Back to Optimizing and rebooting again. It goes to completion but then reboots back to the Samsung logo.
What phone do you have? I had a similar problem that is almost exactly as you described. I have an N950U1 but I flashed the T-Mobile firmware to mine a few months ago. I believe that was my problem but I could be wrong. I posted in another thread about this. https://forum.xda-developers.com/at...in-flash-to-note-8-specific-computer-t3883398 . I think I could have flashed the unlocked firmware, but I haven't tried to see if that is the solution.
Hi,
I did a lot of trying to get twrp installed.
After a while I followed a hint and it worked but I lost Magisk.
After installing Magisk I got a bootloop. Magiskuninstaller didn't work and all other methods I know also didn't help.
Now I have only twrp working and maybe that's the only possibility to install anything, because in ODIN I always get failures
e.g.
Trying to install bootloader:
<ID:0/007> abl.elf
<ID:0/007> xbl.elf
<ID:0/007> xbl_config.elf
<ID:0/007> FAIL! (Auth)
and
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007>
<ID:0/007> Re-Partition operation failed.
or, when I tick Re-Partition in options
<ID:0/007> Can't open the specified file. (Line: 2006)
any help would be appreciated
Firstly, and please forgive me for nitpicking in your time of dread, if your device can power on it is not bricked, despite what so many uninformed folks say; "bricked" means there is no way to get it to even power on. And since I'm in 'education mode' there is no such thing as "soft brick"; it's like saying something is "kinda dead", and there is no such things as zombies irl.
Anyways, have you tried resetting the tab in recovery mode? Good instructions here:
https://www.hardreset.info/devices/samsung/samsung-galaxy-tab-s6/recovery-mode/
TiTiB said:
Anyways, have you tried resetting the tab in recovery mode? Good instructions here:
https://www.hardreset.info/devices/samsung/samsung-galaxy-tab-s6/recovery-mode/
Click to expand...
Click to collapse
First: Thanks for your support
But: I'm in twrp recovery not in stock
and I cannot enter safe mode
any solution for this?
Tronje said:
First: Thanks for your support
But: I'm in twrp recovery not in stock
and I cannot enter safe mode
any solution for this?
Click to expand...
Click to collapse
I don't think I've had to use button combos while in TWRP, but their purpose is to *force* your device in to a certain state (in this case Recovery), no matter what state they are currently in. Usually in such cases where it looks like critical files or operations are messed up, common, and sound, advice is to get back to stock and then do, whatever.
Other than that, I'll have to defer to what others have to say. Good Luck!
or is there a way to do it via sideload?
it's totally crazy, nothing seemes to work
I was able to install stock boot image and stock recovery that I extracted from firmware that I downloaded from samfrew hopefully I could solve the problems with odin - but failed
I'm even not able to shut down the tablet when connected to powercable - there is a permanent bootloop
I was able to take some photos. Maybe someone will realize what else I could try to do. The large photo shows, what happened when I tried to sideload several versions of the downloaded firmware
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tronje said:
or is there a way to do it via sideload?
it's totally crazy, nothing seemes to work
I was able to install stock boot image and stock recovery that I extracted from firmware that I downloaded from samfrew hopefully I could solve the problems with odin - but failed
I'm even not able to shut down the tablet when connected to powercable - there is a permanent bootloop
I was able to take some photos. Maybe someone will realize what else I could try to do. The large photo shows, what happened when I tried to sideload several versions of the downloaded firmware
View attachment 4988349
View attachment 4988351
View attachment 4988353
View attachment 4988355
Click to expand...
Click to collapse
I'm not an expert here by any means, but I think if you can get to fastboot/bootloader you can use ODIN to do a full restore. I would think you can also use fastboot to just restore the recovery partition as well.
ChrisDos said:
I'm not an expert here by any means, but I think if you can get to fastboot/bootloader you can use ODIN to do a full restore. I would think you can also use fastboot to just restore the recovery partition as well.
Click to expand...
Click to collapse
Dear,
did you really read my post?
I need real, detailled help because I'm always getting errors in Odin.
I think Odin is no longer an option.
Mostly it ends with an FAIL! (Auth)
or Re-Partition operation failed
or, when I tick Re-Partition in options: <ID:0/007> Can't open the specified file. (Line: 2006)
I was so desperate that I was looking for a PIT-file, who knows wherefore, but no success.
I ticked and unticked I think every possible options in Odin, tried several releases of firmware with several releases of Odin-Software and also different twrp releases.
My last hope was my old notebook, as I read, that sometimes there are differences in behaviour between some PC, but failed again.
Maybe a detailed instruction how and what to sideload or another PIT-File (I found only this one: GTS6L_EUR_OPEN.pit)
Maybe that's the problem: I'm using German firmware with European PIT? But I couldn't find European firmware oder German PIT
Tronje said:
Dear,
did you really read my post?
I need real, detailled help because I'm always getting errors in Odin.
I think Odin is no longer an option.
Mostly it ends with an FAIL! (Auth)
or Re-Partition operation failed
or, when I tick Re-Partition in options: <ID:0/007> Can't open the specified file. (Line: 2006)
Click to expand...
Click to collapse
Might want to use Frija to download the firmware. If ODIN is no longer an option, then all is lost. I highly doubt that is though. I've had issues with specific USB cables not working or a bad USB port. I wouldn't panic yet as TiTiB said. As long as you can get it to turn on and get to the bootloader, there should be a way to recover it.
Looks at the Tab 5Se, S10, note 10, etc threads on recoveries. The Tab S6 forums don't seem to be nearly as prolific as other forums.
I know you are at your wits end, but hang end there. Try using Frija to get the proper firmware. You might even try going back to the original or second release in August of last year. You key is going to be getting ODIN to do the work though. I also fine it ludicrous that the Samsung devices have so many different boot options using the keys. Evening the timing of pressing the buttons in a certain order is critical.
ChrisDos said:
Might want to use Frija to download the firmware.
Click to expand...
Click to collapse
ok, I did, downloaded, flashed with the same disappointing result
ChrisDos said:
If ODIN is no longer an option, then all is lost. I highly doubt that is though. I've had issues with specific USB cables not working or a bad USB port. I wouldn't panic yet as TiTiB said. As long as you can get it to turn on
Click to expand...
Click to collapse
I even cannot shut it down. That's what make me think, it's lost.
ChrisDos said:
and get to the bootloader, there should be a way to recover it.
Click to expand...
Click to collapse
I didn't find any. In bootloader there should be a warning message first before entering, but there is none. And later some characters (a status message or something like that) on the top of the screen, but there is none.
ChrisDos said:
Looks at the Tab 5Se, S10, note 10, etc threads on recoveries. The Tab S6 forums don't seem to be nearly as prolific as other forums.
Click to expand...
Click to collapse
that's my very last hope
Tronje said:
I even cannot shut it down. That's what make me think, it's lost.
Click to expand...
Click to collapse
All is not lost - If it powers on, it isn't bricked - Simply software malfunctioning. Would assume you've corrupted the system with Magisk, which means just flashing stock should fix it. No idea why Odin isn't working though, since you've already flashed back to stock recovery - Are you sure you have the correct Firmware? Your bootloader is probably locked again, so you won't be able to flash anything but stock.
bartleby999 said:
All is not lost - If it powers on, it isn't bricked - Simply software malfunctioning. Would assume you've corrupted the system with Magisk, which means just flashing stock should fix it. No idea why Odin isn't working though, since you've already flashed back to stock recovery - Are you sure you have the correct Firmware? Your bootloader is probably locked again, so you won't be able to flash anything but stock.
Click to expand...
Click to collapse
I tried all available firmware versions with different odin releases. It's always the same:
<ID:0/010> Initialzation..
<ID:0/010>Set PIT file..
<ID:0/010> DO NOT TURN OFF TARGET!!
<ID:0/010> FAIL! (Auth)
<ID:0/010>
<ID:0/010> Re-Partition operation failed.
Trying to flash twrp recovery:
<ID:0/007> NAND Write Start!!
<ID:0/007> SingleDownload.
<ID:0/007> recovery.img
<ID:0/007> vbmeta.img
<ID:0/007> FAIL! (Auth)
<ID:0/007>
I really really would like to know where this FAIL! (Auth) comes from. But all google search brought solutions not fitting to my situation.
Few minutes ago it just let me flash TWRP_T865_3.3.1-9.tar without grumbling - but there is no twrp recovery, only stock
<ID:0/007> Odin engine v(ID:3.1301)..
<ID:0/007> File analysis..
<ID:0/007> Total Binary size: 0 M
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> NAND Write Start!!
<ID:0/007> SingleDownload.
<ID:0/007> RQT_CLOSE !!
<ID:0/007> RES OK !!
<ID:0/007> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
with TWRP_T865_3.3.1-10L.tar I'm getting error message again
Tronje said:
I tried all available firmware versions with different odin releases. It's always the same:
...
Click to expand...
Click to collapse
I just posted a solution here: https://forum.xda-developers.com/showpost.php?p=82229527&postcount=7
Moe5508 said:
I just posted a solution here: https://forum.xda-developers.com/showpost.php?p=82229527&postcount=7
Click to expand...
Click to collapse
That's great news. Now I got one step further.
For the first time there are some characters on the screen. (see attached file)
... but FAIL! (Auth)
persists
when I tried flashing BL-File
That's great indeed.
Now we get down to the firmware issues...it appears you might have upgraded to a higher BL one which may not allow you to downgrade BL)...might I suggest you try a different firmware?
And you are also already OEM Unlocked, right?
Was this round one of flashing BL, or round two, as per my guide? Please PM me and lets troubleshoot that way rather...
Moe5508 said:
That's great indeed.
Now we get down to the firmware issues...it appears you might have upgraded to a higher BL one which may not allow you to downgrade BL)...might I suggest you try a different firmware?
And you are also already OEM Unlocked, right?
Was this round one of flashing BL, or round two, as per my guide? Please PM me and lets troubleshoot that way rather...
Click to expand...
Click to collapse
display shows
FRP LOCK : OFF
OEM LOCK : OFF (U)
so I think I'm unlocked
I tried all German 4 firmware releases and I always failed in step 1
I got my device in november with october release and upgraded to december release
Here's the full log of Odin, it always shows the same result:
<ID:0/010> Added!!
<ID:0/010> Odin engine v(ID:3.1301)..
<ID:0/010> File analysis..
<ID:0/010> Total Binary size: 152 M
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> NAND Write Start!!
<ID:0/010> SingleDownload.
<ID:0/010> abl.elf
<ID:0/010> xbl.elf
<ID:0/010> FAIL! (Auth)
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I could try to lock the device, but probably no good idea?
what is strange:
when I try to install twrp recovery I'm getting message
<ID:0/007> Added!!
<ID:0/007> Odin engine v(ID:3.1401)..
<ID:0/007> File analysis..
<ID:0/007> Total Binary size: 0 M
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> NAND Write Start!!
<ID:0/007> SingleDownload.
<ID:0/007> RQT_CLOSE !!
<ID:0/007> RES OK !!
<ID:0/007> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/007> Removed!!
but when I boot, there is no twrp recovery , only stock, nothing changed
Tronje said:
what is strange:
...
but when I boot, there is no twrp recovery , only stock, nothing changed
Click to expand...
Click to collapse
I think this is a TWRP issue then, and you can ask in the thread there...as far as I can recall with flashing TWRP, you must be quick again at first boot to NOT let the device boot fully...you need to boot directly into TWRP else the custom recovery won't stick...
Moe5508 said:
I think this is a TWRP issue then, and you can ask in the thread there...as far as I can recall with flashing TWRP, you must be quick again at first boot to NOT let the device boot fully...you need to boot directly into TWRP else the custom recovery won't stick...
Click to expand...
Click to collapse
Yes, I know. But I don't know what to do with twrp?
There seemes to be no operating system on the tab and there is no possibility to flash one from twrp. I flashed it just to see what would happen. It couldn't get worse.
What I need is a methode flashing by odin or something else with available firmware.
I only know odin. Is there something similar?
Tronje said:
I tried all available firmware versions with different odin releases. It's always the same:
<ID:0/010> Initialzation..
<ID:0/010>Set PIT file..
<ID:0/010> DO NOT TURN OFF TARGET!!
<ID:0/010> FAIL! (Auth)
<ID:0/010>
<ID:0/010> Re-Partition operation failed.
Trying to flash twrp recovery:
<ID:0/007> NAND Write Start!!
<ID:0/007> SingleDownload.
<ID:0/007> recovery.img
<ID:0/007> vbmeta.img
<ID:0/007> FAIL! (Auth)
<ID:0/007>
I really really would like to know where this FAIL! (Auth) comes from. But all google search brought solutions not fitting to my situation.
Few minutes ago it just let me flash TWRP_T865_3.3.1-9.tar without grumbling - but there is no twrp recovery, only stock
<ID:0/007> Odin engine v(ID:3.1301)..
<ID:0/007> File analysis..
<ID:0/007> Total Binary size: 0 M
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> NAND Write Start!!
<ID:0/007> SingleDownload.
<ID:0/007> RQT_CLOSE !!
<ID:0/007> RES OK !!
<ID:0/007> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
with TWRP_T865_3.3.1-10L.tar I'm getting error message again
Click to expand...
Click to collapse
Sorry but I have to ask, why are you repartitioning anything? The only option you should touch in Odin from the options available on the left side of the screen is automatic reboot as far as I'm aware.
I would slow down and reread from the beginning.
1. Get all the correct firmware, double checking model and version numbers (is it SM-T860 or SM-T860N for example).
2. Prioritize your tasks and do them 1 at a time (get recovery working correctly, then install stock firmware, then if desired install TWRP OR root, one or the other, don't attempt to speed things up and try flashing 2 operations at once).
3. Reread what you are about to attempt before you start the process.
4. Don't try and improve on the instructions you are following, follow them exactly.
If you do the above I really can't see how you can go wrong.
Feel free to PM me any questions and if I can help I will.
Good luck brother
Sent from my [device_name] using XDA-Developers Legacy app
Disclaimer:Your warranty is now void. Please read the post before asking questions, if you do not read the post and ask questions they will not be answered.
I am not responsible if you use this and brick your device or if your device blows up, implodes. Follow the instructions and you should be good.This is stock ROM with modifications.You must have an Unlocked Boot loader. This is only for SM-G981U, SM-G981U1 and SM-G981W. ALWAYS BACKUP YOU’RE DATA BEFORE FLASHING.Instructions:• Download the zip file.• Put the ROM.tar in AP slot with Odin.• Reboot• Wipe data• Enjoy!• Any Issues let me know!ROM FEATURES:- You will need to flash safety net fix from github.- 90 plus fonts - 3 Minit Battery and Clock Added- Circle Battery- Network Speed Options- Few others- ViPER4AndroidFX included just install drivers and everything works- Force Encryption Off All ROMS- Heavily Debloated- Bluetooth, Screenshare and Shealth working.- Disable shutter sound menu- AppLock Protection menu- Support RealTime Network Speed- Enable Camera during call- Voicecall recording- Data usage view on quick panel- Block call number menuSEE POST 2 FOR ROM DOWNLOAD LINKSTelegram BKLYNROMs To get your phone unlocked see this thread or @afaneh92 UnlockTWRP Thanks to @afaneh92
BKLYN Kernel Source >> SM-G988U
Donations are not required but are encouraging, If want to support my work just click Here
Changelog
01/22/2022 BKLYN_S20_ROM_A12_V_1.0.0
Download Link >> BKLYN_S20_ROM_A12_V_1.0.0
Based on : G981USQU2EULH
Post3
bklyn_syed said:
Post3
Click to expand...
Click to collapse
Great Rom. Working Flawless.
Thank You For this, Love for the s20.
gavilan2010 said:
Great Rom. Working Flawless.
Thank You For this, Love for the s20.
Click to expand...
Click to collapse
You welcome
Hey I notice in the settings you have scripts to debloat the rom further. Does the Bixby and other debloat stuff require reboots or anything else to work?
I'd love to permanently get rid of Bixby.
Thanks it work well.
ChongoDroid said:
Hey I notice in the settings you have scripts to debloat the rom further. Does the Bixby and other debloat stuff require reboots or anything else to work?
I'd love to permanently get rid of Bixby.
Click to expand...
Click to collapse
It just disables bixby and other apk. You have to turn off and turn it back on in order for it to work
bklyn_syed said:
It just disables bixby and other apk. You have to turn off and turn it back on in order for it to work
Click to expand...
Click to collapse
Hmm I tried every combination and it's still there. Using a 981w btw if it makes a difference.
ChongoDroid said:
Hmm I tried every combination and it's still there. Using a 981w btw if it makes a difference.
Click to expand...
Click to collapse
Can you make sure there are files etc/bk, it shouldn't matter I did test it on S20 Ultra
bklyn_syed said:
Can you make sure there are files etc/bk, it shouldn't matter I did test it on S20 Ultra
Click to expand...
Click to collapse
Yeah for some reason the script won't execute. I just copied the script and executed it in terminal and worked fine.
Weird
Tested and works. Any idea how to remove carrier name in status bar?
mattrb said:
Tested and works. Any idea how to remove carrier name in status bar?
Click to expand...
Click to collapse
Go to bk_settings apk go to status bar options make sure carrier label on lockscreen status bar is hide
is device encryption working ?
D3F0NC3UR said:
is device encryption working ?
Click to expand...
Click to collapse
Its turned off by default you can turn it on
BKLYN_S20_ROM_V1.1.0 based on G981USQU1DUCB. Remove your password/pin before flashing.
the button to open screen not working with 1.1 version
D3F0NC3UR said:
the button to open screen not working with 1.1 version
Click to expand...
Click to collapse
It shouldn't be any issues because s20 and ultra have the same system ui and framework. I am using same stuff on ulta. You can send me a PM with the issues
Failed, odin shows:
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1203)..
<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> SingleDownload.
<ID:0/004> abl.elf.lz4
<ID:0/004> Complete(Write) operation failed.
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
sslh2017 said:
Failed, odin shows:
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1203)..
<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> SingleDownload.
<ID:0/004> abl.elf.lz4
<ID:0/004> Complete(Write) operation failed.
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Are you using modify odin it doesn't look like you are