yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] alecxs:
if you can see anything on tablet, it's already powered on. if the handshake is made it should stay off in preloader mode.
[Android Q&A, Help & Troubleshooting] remyxk:
Yea maybe the tablets not powering off all the way, what do you think? What should I try?

Also I think the problems with the handshake, it's keep getting:

..........Preloader
Preloader - [LIB]: Status: Handshake failed, retrying...
[Android Q&A, Help & Troubleshooting] alecxs:
try in bootrom mode with --preloader flag
[Android Q&A, Help & Troubleshooting] remyxk:
Can you write the command I have to use with that flag? Maybe I'm using the wrong command.
[Android Q&A, Help & Troubleshooting] remyxk:
I tried using mtk_gui with that flag and bootrom mode and I was able to get it to connect for a few seconds but it disconnected again, do you know what may be causing this?

View attachment 6038122

Spoiler content hidden.
[Android Q&A, Help & Troubleshooting] alecxs:
never seen that gui - the command line for dumping boot.bin is linked here #15

DeviceClass - USBError(5, 'Input/Output Error') means something is wrong with Python, connection or driver.
[Android Q&A, Help & Troubleshooting] remyxk:
Okay I tried using mtk_gui but this time I only held down the volume button up and it worked! :) (I got the recovery, and vendor partitions too.)

Just in case it matters, heres the debug log:

Spoiler content hidden.

Also, how do I make sure that these are the right partitions and are not corrupted in anyway because the debug log had "[15:53:35]: Failed to dump sector 60416 with sector count 32768 as C:\Users\iinea\Downloads\Partitions\boot.bin." even though it said it succeeded and I got the files

And how would I backup my device just in case anything goes wrong?

EDIT: This is what I got when I tried dumping the boot partition without the GUI:

Spoiler content hidden.

It said it failed at the end, but I still got a boot.bin file.
[Android Q&A, Help & Troubleshooting] alecxs:
idk maybe just a bug regarding that checksum. patch the boot.bin with Magisk it will tell you if something is wrong.
[Android Q&A, Help & Troubleshooting] remyxk:
Okay the device doesn't have a ramdisk so I patched the recovery.bin file instead and it worked. we're making progress lol
[Android Q&A, Help & Troubleshooting] alecxs:
you can try to boot the image without flashing it, first. once rooted, you can try the direct install method into boot partition.

fastboot boot magisk_patched-26400_dAcr3.img
[Android Q&A, Help & Troubleshooting] remyxk:
I can't brick my device without actually flashing it right?

also what did you mean by the direct install method? according to Magisk, my device doesn't have a ramdisk and the only way I can root it is if I use the recovery partition.
[Android Q&A, Help & Troubleshooting] alecxs:
that's what Magisk App says. but the Magisk instructions say different.

trial & error you will see. the Direct Install method is straight from Magisk App AFTER the device is already rooted.

in case you bricked device, unbrick it by flashing the unmodified partition dump from fastboot.
[Android Q&A, Help & Troubleshooting] remyxk:
alright so I did the command and it transferred the image but nothing happened after that. I held down the power button after and it just booted back up normally, no root.

am I supposed to reboot into recovery with fastboot or something?

EDIT: When I went into recovery mode, I saw a dead Android logo and text that said "No Command", hopefully I didn't ruin the recovery partition lol. Any way to fix this?
[Android Q&A, Help & Troubleshooting] alecxs:
if fastboot boot not working, flash the file instead. then reboot into recovery.

fastboot flash recovery magisk_patched-26400_dAcr3.img

the No Command screen is part of recovery mode, play with volume buttons to proceed into actual recovery menu (I think it's Volume Up + Power)
[Android Q&A, Help & Troubleshooting] remyxk:
Alright thank you, let me try that
[Android Q&A, Help & Troubleshooting] remyxk:
I can't get it to open system with Magisk, when I hold down the recovery key combo (power + volume up), a screen pops up where I choose either recovery mode, fastboot mode, or normal mode, the splash screen comes after. View attachment 6038246
[Android Q&A, Help & Troubleshooting] alecxs:
flash patched recovery again then boot straight into recovery mode, otherwise recovery is overwritten with stock recovery on next boot. not sure about the bootmenu but I guess recovery mode is the right selection.
[Android Q&A, Help & Troubleshooting] remyxk:
Thank you so much! I tried going into recovery mode right from the flash recovery page and it worked! :)
[Android Q&A, Help & Troubleshooting] remyxk:
I have to reflash the patched recovery each time my device restarts. Is there a workaround for this or how would I do the direct install method you were talking about?
[Android Q&A, Help & Troubleshooting] alecxs:
in Magisk, select Direct Install
[Android Q&A, Help & Troubleshooting] remyxk:
Do I keep Recovery mode checked or not?
[Android Q&A, Help & Troubleshooting] alecxs:
Trial & Error idk #36
[Android Q&A, Help & Troubleshooting] remyxk:
I tried it with recovery mode off and it worked. Thank you so much for all the help! 😄
[Android Q&A, Help & Troubleshooting] protechtedd:
Just wanted to say thank you to @remyxk and @alecxs for explaining the process for rooting this K10 tablet.

I've had this tablet for a few years but never bothered to root it. I wanted to use it for a project recently and was able to successfully root.
[Android Q&A, Help & Troubleshooting] bibikalka:
So do I understand this correctly here?

I can dump all partitions with mtkclient, add magisk to boot image, and flash it back?

What about unlock, can I do

python mtk da seccfg unlock

using the same mtkclient? Will this wipe the /data partition?

I guess with all partitions dumped, I should be reasonably safe to try stuff - I can always go back to bootrom to put them back. Is this indeed the case?
[Android Q&A, Help & Troubleshooting] alecxs:
yes, if bootloader is unlocked. for some older devices it's even possible on locked bootloader, depends on avb version.

yes, that is inofficial bootloader unlock.

yes, unlocking bootloader usually requires factory reset. although experts claim it's possible to decrypt data after inofficial unlocking, the author of mtkclient says different. It won't wipe the userdata partition, but encryption keys are bonded to dm-verity, which is bonded to bootloader lock state. it will most likely break encryption.

no. this assumption is based on the idea that every data is stored in partitions - which is not the case.

yes, but avoid booting into android or factory reset at all costs. as soon as the encryption keys in keystore are changed, the backup of userdata + metadata becomes useless. (there is only one exception if your device is just FDE encrypted)
[Samsung Galaxy Note 10+ ROMs, Kernels, Recoveries,] Thanos:
If you are reading this, it's because you are viewing from a mobile application.

This thread redirects to:

https://xdaforums.com/galaxy-s6/orig-development/read-xda-developers-gpl-t3034575
[Samsung Galaxy Watch] kaspalone:
Hello.

Long time lurker, 1st time subscriber here.

I have a Galaxy watch, 46mm, SM-R800NZSAXAR. US version, non LTE. I have it with the latest firmware that was released for it about a month or two ago. I just dont know the serial for that FW version.

My issue is that, the Watch, suddenly turned off, and when i try to boot it up, it shows the "Samsung Galaxy Watch" logo, and turns off again. I can access the download mode, the Odin mode and have even tried the "Recovery" option but this does not work.

I've read on other threads that I can try to re-flash the FW to the device via NetOdin and the right FW version and that MIGHT help getting it back up working. Thing is, i have NO IDEA what FW version to get. I see all sort of numbering but i cannot tell which one should i get, and the information i have come accross is confusing.

So, could you guys point me in the right direction, so maybe i get the proper FW and try to repair my watch? I've already talked with Samsung Customer Support, and they want me to send the device for repair... thing is I'm not in the US no more, and that'd be a real pain in the ass.

Thank you in advance.
[Samsung Galaxy Watch] Hexoer17:
Pudiste repararlo

Me pasó lo mismo con el mismo modelo flashee con lo que encontré y ya funciona aunque tiene tizen 4.0.0
[Samsung Galaxy Watch] KruseLudsMobile:
Why not just exchange it?

- R. Kruse Ludington

Galaxy Note 8<-5<-3<-S3<-Nexus; Droid X; HTC HD2<-Touch Pro 2<-Tilt<-8525; O2 XDA II<-XDA; Motorola StarTac
[Samsung Galaxy Watch] kaspalone:
With whom? why? How?

Where I Live, doing that kinda thing is not that easy. Besides, I still want my watch.
[Samsung Galaxy Watch] adfree:
netOdin only 1 Version leaked... since monthS... yearS...

But still work...

Look here about how to use...

https://xdaforums.com/showpost.php?p=73503787&postcount=150

Now you need Firmware for your SM-R800...

Please try to search to through Threads here... somewhere few users posted Links...

Best Regards

Edit 1...

Clicking weired around...

https://xdaforums.com/smartwatch/galaxy-watch/update-firmware-netodin-t3895010

Edit 2...

Clicking weirder and harder leads to this post...

https://xdaforums.com/showpost.php?p=79689619&postcount=44
[Samsung Galaxy Watch] kaspalone:
Hey, hello!

I read thru them already, and that's what got me confused. Cuz it was not clear which one was the most recent or the right one for an SM-R800 US. Could you tell me or guide me on how to determine which one would be the right one to get before proceeding?

Thanks.
[Samsung Galaxy Watch] adfree:
Alphabet...

All in 1 package...

ALL CSC...

US is CSC XAR

You see XAR...

CSC means something like Customer Sales Code...

IMHO try this:

OXA_EU_R800XXU1[B]C[/B]SE1.zip

More then it will explode... :D

In worst case... if you still out of luck... you need USB cable...

Look at Video:

https://xdaforums.com/showpost.php?p=78545468&postcount=74

Good Luck.

Last hint:

OWN risk!

Best Regards
[Samsung Galaxy Watch] adfree:
Here is overview about valid Firmwareversions for XAR ( US region):

http://doc.samsungmobile.com/SM-R800/XAR/doc.html

I hope you see why I wrote Alphabet... ;)

All files are leaked... :angel:

Nobody shared latest CRG4 in public...

Best Regards
[Samsung Galaxy Watch] kaspalone:
I understood the Alphabet reference. I was thinking it had something to do about it but was not sure.

Anyway, i followed your "advice" and downloaded the FW, flashed it, the procedure finished properly (NetOdin said it was successful), Watch restarted, and NOTHING happened. It's still not booting. Just shows the logo and turns off again. So I'm thinking is really a hardware problem. I'm gonna have to send it back to the USA for repairs and hope they honor the warranty.

I still dont understand why cant I buy the product in one country and get service for it in another if it's withing the warranty time.... but w/e.

Thanks man for your help. This will deter me from buying anything Samsung for awhile.
[Samsung Galaxy Watch] adfree:
:o

Sorry to read about no real success...

If you have time... you could check ODIN Mode... look here as example:

https://xdaforums.com/showpost.php?p=73607036&postcount=1

You could upload Photo if you want... or write all infos as text...

Maybe Warranty Void value allready changed...

:confused:

Best Regards

Edit 1.

Here is Video about Galaxy Watch... how to enter and leave Odin aka Download Mode:

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

But my eyes can not see the Values...:D :o

0 (0x0000)

This is "best"...

All other Values are not good in case of warranty...
[Samsung Galaxy Watch] kaspalone:
Hello.

This is the data you requested:

ODIN MODE

Product name: SM-R800

CURRENT BINARY: Samsung Official

SYSTEM STATUS: Official

REACTIVATION LOCK: Off

Secure Download: Enabled

CARRIER ID:

WARRANTY VOID: 0 (0x0000)

AP SWREV: B:1 K:0 S:0

I have absolutely no idea what happened with the device. It just wont boot beyond the logo.

If you have something else i could try, lemme know. Getting if service by an official samsung rep will be a daunting task, since is a US device and i Dont live in the US... is covered with a warranty tho. I just have to jump thru a lot of hoops to send it there.
[Samsung Galaxy Watch] adfree:
Thanx for info.:good:

Official looks good... otherwise something like Custom....

OFF is IMHO better as ON if you have trouble... = less Security

All Zero is best... otherwiseyou got more problems for Service Repair... but as you told... other contry = nearly NO chance...

IMHO

I would test this Factory/Service Firmware...

OXA_[B]COMBINATION[/B]-FT40_R800XXU1ARI2.tar.md5.zip

If this Firmware starts complete on your SM-R800... check if WiFi and BT is usable...

Then you could try to flash again Stock Firmware...

Again.

OWN risk... not official supported by Samsung because leaked Tool + leaked Firmware...

Best Regards
[Samsung Galaxy Watch] kaspalone:
I'm making arrangements to send it to Samsung US to get it repaired. If all fails, then I'll get my hands dirty again. It's still covered by the warranty, the problem is to get it to Samsung US hands for repair.

Thanks for your help tho. I'll keep this bookmarked for future reference.
[Samsung Galaxy Watch] mangust479:
Hi,

I have the same problem with the clock, did you manage to repair it?
[Samsung Galaxy Watch] mangust479:
I solved the problem with my watch in the following way:

1. Firmware R800XXU1DSL1 (available at 4pda) using the standard method, but you MUST include the Phone Bootloader Update check box in Odin. Then press Start, Odin will update the firmware and swipe a new loader to fix the problem. It helped me, I also tried to repair the clock for 2 weeks with the same problem and wanted to carry them to the service.
[Samsung Galaxy Note 10+ Themes, Apps, and Mods] Thanos:
If you are reading this, it's because you are viewing from a mobile application.

This thread redirects to:

https://xdaforums.com/note-7/themes/read-regarding-paid-themes-xda-t3444478
[Samsung Galaxy Note 10+ Accessories] Thanos:
If you are reading this, it's because you are viewing from a mobile application.

This thread redirects to:

https://xdaforums.com/galaxy-s6/accessories/warning-spam-sell-trade-xda-t3297136
[Samsung Galaxy M40 Guides, News, & Discussion] Thanos:
Please Post All Questions In The Q&A Section.

They do not belong in the General Section.

If you are missing your threads, this is probably why.

They will be moved or closed depending on their material.

Per Rule 15
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] simonhcai:
I'm trying to edit a video it's only short but when I try the circle spins and won't stop and when I press on edit tools it's says waiting for video to load any help please...
[Samsung Galaxy M40 Guides, News, & Discussion] Thanos:
If you are reading this, it's because you are viewing from a mobile application.

This thread redirects to:

https://xdaforums.com/galaxy-s9/how-to/telegram-chat-channels-forward-t3763966
[Touch Diamond, MDA Compact IV ROM Development] tom_codon:
Hi all..!

Diamond Project team worked on SSPL,Hard-SPL for Diamond device.And now we're release it 4 free :)

After flashing HardSPL you'll be able to flash any Diamond ROM to your device!

This tool will allow you to change the ROM language, flash cooked ROMs, custom splash screens, etc...

INSTRUCTIONS :

Connect Diamond to computer using USB cable

Make sure ActiveSync icon is GREEN

Extract sspl-diamond-1.23.zip and run SSPL.bat

Your device will go to bootloader.Device screen should be now TRI-COLOR and show "1.23.Jump" and "USB"

Unplug and Re-Plug the USB cable

Phone screen should still be tri-color and still show "USB" ,the activesync icon gray

if not, the loading process has failed and you'll have to repeat it again.

If all was OK then u extract Diamond-Flash-Splash.zip and click to ROMUpdateUtility.exe it will update for u Splash screen htc.After that if all fine.That sure u have sspl version working.

Go to sspl-diamond-1.23 again.Run it to get SPL 1.23.Jump and now extract Diamond-HardSPL-1.23.zip and just install Hard-SPL with same

* NOTE :

This version just works for devices having SPL 1.23.

Will not works in Devices has SPL 1.34

With SPL 1.34 version.We will update in next days :)

Important:

Use at your own risk! I'm not responsible for any damage to your device caused by using the attached files.

Credits:

Pof, Des, Olipro and thanks to luigivsf for testing this.

DONATIONS :

Any donation amount is greatly appreciated and strong incentive my team to continue research on new devices
[Touch Diamond, MDA Compact IV ROM Development] rvbcrs:
Great work guys!!

Now all I need is: THE DIAMOND! :)
[Touch Diamond, MDA Compact IV ROM Development] LlabTooFeR:
Nice realise bro :) You do that! ;)
[Touch Diamond, MDA Compact IV ROM Development] tabarda:
Good work tom.

Thanks.;)
[Touch Diamond, MDA Compact IV ROM Development] rorydaredkign:
great work. means i can flash as soon as i get it :)
[Touch Diamond, MDA Compact IV ROM Development] athanaso77:
Very very very good work guys!!! :D
[Touch Diamond, MDA Compact IV ROM Development] RizwanKhan:
awesome .. now i just gotta wait till June 2nd when my diamond will ship to me :) hehehe come to papa
[Touch Diamond, MDA Compact IV ROM Development] itje:
well done bro :)
[Touch Diamond, MDA Compact IV ROM Development] alipi2007:
thanxxxxxxxxx

keep it up!!!!!!!!!!
[Touch Diamond, MDA Compact IV ROM Development] doog:
Fantastik

simply fabulous and fantastic guy great work now i want Diamond out i hope in two week :D

thanks thanks for all works
[Touch Diamond, MDA Compact IV ROM Development] hdubli:
good work tom.. :)
[Touch Diamond, MDA Compact IV ROM Development] christonge:
Nice work Tom... looks like this is going to be a great project and there´s some great cooks in the kitchen. Can´t wait...
[Touch Diamond, MDA Compact IV ROM Development] tramuyo:
BTW... for all users

Im luigivsf ;)
[Touch Diamond, MDA Compact IV ROM Development] liamhere:
i can't wait...but ill have to

i can upgrade in july with orange

so i will playing with you guys soon...i hope :)
[Touch Diamond, MDA Compact IV ROM Development] Tatchan:
You guy crazy! I haven't get my Diamond yet and you're ready for new ROM flashing? :D
[Touch Diamond, MDA Compact IV ROM Development] wlinsong:
i buy a HTC Diamond from HongKong hkcsl.com ,but i can't use SSPL
[Touch Diamond, MDA Compact IV ROM Development] tom_codon:
Okie brother.

U can contacts me with msn.I will help for install sspl,hard-spl ;)
[Touch Diamond, MDA Compact IV ROM Development] lonely_night:
Thanks for the great job!!!
[Touch Diamond, MDA Compact IV ROM Development] manaaa:
hi,

im just out of interest... is that your paypal adress h_dubli@hotmail.com ?
[Touch Diamond, MDA Compact IV ROM Development] tom_codon:
yes brother :)
[Touch Diamond, MDA Compact IV ROM Development] jockyw2001:
HTC combatting SSPL

We carried out various experiments on wlinsong's Diamond tonight and the result is very bad news for Diamond users. At least for users who have the latest radio version 0.93.25 and SPL 1.34.0000. Users with older radio 0.91.25.16 and SPL 1.23.0000 can consider themselves very lucky.

As a matter of fact HTC is combatting the SSPL method by write-protecting the ram area in which the SPL resides. As far as I know the radio is responsible for this and therefore we can call radio 0.93.25 another "Radio from Hell" :mad:

I'm waiting for my own device as I still have a few tricks in my bag :)

Perhaps it's time for "FrankenDiamond" :D

EDIT: I've called support from Olipro & Cmonex -> keyword "relocation"
[Touch Diamond, MDA Compact IV ROM Development] tramuyo:
if them protect SPL area it can be fixed with FrankenDiamond... theres so much power with bootloader commands ;) so I count on "Franken Diamond"
[Touch Diamond, MDA Compact IV ROM Development] tom_codon:
sure we can play with it.But we need all friends here want to play together

As soon we can get device for test,Franken diamond will be release for free :)
[Touch Diamond, MDA Compact IV ROM Development] rtao:
I would have to believe anyone who get their Diamond from HK will all use the latest SPL and Radio, since mine appears that way, and I got mine from the local store here in Hong Kong instead of HKCSL (the carrier)
[Touch Diamond, MDA Compact IV ROM Development] DesktopMan:
This is discouraging. Might even have to wait and see how it pans out before I buy a Diamond.

What's the difference between SSPL and hardSPL?
[Touch Diamond, MDA Compact IV ROM Development] XuMEPA:
Äîáðûé äåíü!

Óñòàíîâèë îäíó ôèãíþ íà Touch Diamond. Â ðåçóëüòàòå WinMobile çàâèñàåò ñðàçó ïîñëå çàãðóçêè (òèïà ïðè ïîäãðóçêå Today). Ñ ActiveSync íå ñîåäèíÿåòñÿ (õîòÿ íà ñåêóíäó âûñâå÷èâàåò îêîøêî - åñëè òêíóòü êàáåëü âî âðåìÿ "çåë¸íîãî" Startup ýêðàíà WinMobile, íî òóò æå ïðîïàäàåò è âèñíåò).

Êóøìàð, âîîáøýì.

Åñòü ëè êàêîé-íèáóäü ñóïåð õàðä-ðåçåò (òèïà hard-êíîïêàìè) ?

P.S. Åñëè âûòÿíóòü êàðòî÷êó - òî çàãðóæàåòñÿ ñîôò-òåëåôîí äëÿ emergency çâîíêà. Íà ñîôò-òåëåôîíå êíîïêè ðàáîòàþò, íî êðîìå ýòî ñîôò-òåëåôîíà - îïÿòü æå íè÷åãî íå íàæèìàåòñÿ (íèêàêèå èêîíêè è íèêàêèå õàðä-êíîïêè êðîìå reset).

Do you have any idea, áðàòöû ?
[Touch Diamond, MDA Compact IV ROM Development] terry888_1978:
Man,where I can get the SPL 1.34.0000, SPL 1.23.0000 is not work on My Diamond, and How to Built a Diamond CHS ROM? it must wait HTC's CHS?
[Touch Diamond, MDA Compact IV ROM Development] terry888_1978:
sorry for my fool. My Diamond SPL is 1.34.0000 Radio 0.93.25.NS16 ,rom 1.34.831.1WWE, how can i unlock it? SSPL is not work on it.please help.
[Touch Diamond, MDA Compact IV ROM Development] XuMEPA:
Hi guys!

Di you have any information how make FORCED HARD-RESET for HTC Touch Diamond ?

Soft method isn't working because WinMobile freeze at 1 moment after "greed" startup screen passed. (startup passed, all booting but any keys don't pressed, any commands don't running - it all have no reaction on any my action).

I want to run hard-reset for this device.

Anybody help me ?
[Touch Diamond, MDA Compact IV ROM Development] SecureGSM:
Q:

write-protecting the RAM area or moving pages to write-protected areas?
[Touch Diamond, MDA Compact IV ROM Development] falojjah:
same quistion ?
[Touch Diamond, MDA Compact IV ROM Development] walshieau:
if you own one, check your User Manual or use the search function on this forum, i posted about it earlier today...
[Touch Diamond, MDA Compact IV ROM Development] tom_codon:
http://xdaforums.com/showthread.php?t=397009
[Touch Diamond, MDA Compact IV ROM Development] SecureGSM:
exactly my point... full stop...
[Touch Diamond, MDA Compact IV ROM Development] andyleung14a:
How about is "go to bootloader.Device screen should be now TRI-COLOR"?
[Touch Diamond, MDA Compact IV ROM Development] zjason:
thx，hahaha
[Touch Diamond, MDA Compact IV ROM Development] hi25man:
Me too:confused:
[Touch Diamond, MDA Compact IV ROM Development] walshieau:
thats because the SSPL DOES NOT WORK! and will not work currently. Stay tuned for more updates.
[Touch Diamond, MDA Compact IV ROM Development] tom_codon:
SSPL,Hard-SPL for version 1.34 working in progress.Will update later :)
[Touch Diamond, MDA Compact IV ROM Development] ringhio99:
For tom_codon........ PVT!
[Touch Diamond, MDA Compact IV ROM Development] hi25man:
Thanks....Waiting:D
[Touch Diamond, MDA Compact IV ROM Development] funkyr:
Hi guys,

Sorry for the newbie question, but what do all these unlocks actually do or allow you to do?

Thanks
[Touch Diamond, MDA Compact IV ROM Development] bobcntsa:
cf first post :

After flashing HardSPL you'll be able to flash any Diamond ROM to your device!

This tool will allow you to change the ROM language, flash cooked ROMs, custom splash screens, etc...
[Touch Diamond, MDA Compact IV ROM Development] athosk:
How do I find???

Hi all

My Diamond has the following Device info:

Rom version: 1.34.831.1 WWE

Radio Version: 0.93.25.NS16

Protocol version: 52.24.25.08H

Could I upgrade or shall I wait for a newer version?

Thnx
[Touch Diamond, MDA Compact IV ROM Development] jockyw2001:
You've got the Radio from Hell so you can't use the current SSPL.

See here

You have to wait a while for a solution.