I always got an error on ce rom at 8 percent.
Anyone please help!
Thanks!
If you want to get help you need to give us more details:
Device model, original ROM version the version you are trying to upgrade to, the PC OS you are using (XP / Vista), error code you are getting.
Only then an answer might be found.
levenum said:
If you want to get help you need to give us more details:
Device model, original ROM version the version you are trying to upgrade to, the PC OS you are using (XP / Vista), error code you are getting.
Only then an answer might be found.
Click to expand...
Click to collapse
Yup !!! thats right,
I'll only add here to post all the vital data of your phone,IPL/SPL...?
Hi there ,
I have oneplus 5t running on android 10 official build my phone lags too much in this os
I just want to rollback to android 9 or 8 if possible please little help needed about the process.
I tried to search bt some says it possible via unbrick tool n some says via service center so please clear me about this.
Thanks in adwance
Hello Guys,
I have a XP6 head unit running Android 9 and I want to update it to Android 10.
The current Build Number is
rk3399-userdebug 9 PI 20200423.174740 test-keys
I've downloaded both version of Android 10 but the installation aborts.
HA3_rk3399_10.0_ota(20200724)升级包
HA3_rk3399_10.0_ota(20200915)升级包
Can anyone help with this problem and update my unit to Android 10?
Thanks guys
No way! Crazy
Assuming failure before reading forums and wanting a reply with step by step.
Next post will list what has been tried from the hours of effort and multiple posts, hint, my signature.
After a bit of experimenting (and a lot of fights with the bootloader since it always decided to relock itself preventing me from simply using fastboot) I managed to get the global fw to run on an AT&T device.
TLDR: You can just dd the global partitions while rooted and then restore through adb sideload.
Guide: https://github.com/filiphsandstrom/surface-duo
quick question.
for step number 2 "Use payload_dumper from the rooting guide to extract the partition images", am i extracting the partition images from the Global version or the AT&T version?
So does this mean anyone using this firmware has sim unlock? I saw on the GitHub you mentioned it works on another network outside of AT&T
edchuxda said:
quick question.
for step number 2 "Use payload_dumper from the rooting guide to extract the partition images", am i extracting the partition images from the Global version or the AT&T version?
Click to expand...
Click to collapse
The global version. The script will then dd those to the correct place
I had great success with this and have relocked the bootloader as a normal duo device thanks, if anyone has any questions about how i managed it let me know. Thanks so much @filfat
I just wanted to thank the OP for making this process easy with the instructions and for the new life given to this phone. Now that the phone has been converted to the global version what happens if another update comes down the pipe? Do we flash the global version, at&t version or sit tight and await further instructions ?
@Draco32 or @filfat
First:
1|duo:/data/local/tmp # chmod +x globalify.sh && ./globalify.sh;
./globalify.sh[7]: syntax error: unexpected 'newline'
1|duo:/data/local/tmp #
Why error?
Next:
I am assisted by the guide on this page:
GitHub - filiphsandstrom/surface-duo: Convert a Surface Duo AT&T to the global variant.
Convert a Surface Duo AT&T to the global variant. Contribute to filiphsandstrom/surface-duo development by creating an account on GitHub.
github.com
I'm on step 8. At 47%, it shows me an aborted installation message. Reason: incompatibility.
How to solve it?
I took the system from:
https://android.googleapis.com/packages/ota-api/package/a9bfdee15f2137f020fffded98b4bdee5d8bec8e.zip
Hoffman404 said:
@Draco32 or @filfat
First:
1|duo:/data/local/tmp # chmod +x globalify.sh && ./globalify.sh;
./globalify.sh[7]: syntax error: unexpected 'newline'
1|duo:/data/local/tmp #
Why error?
Next:
I am assisted by the guide on this page:
GitHub - filiphsandstrom/surface-duo: Convert a Surface Duo AT&T to the global variant.
Convert a Surface Duo AT&T to the global variant. Contribute to filiphsandstrom/surface-duo development by creating an account on GitHub.
github.com
I'm on step 8. At 47%, it shows me an aborted installation message. Reason: incompatibility.
How to solve it?
I took the system from:
https://android.googleapis.com/packages/ota-api/package/a9bfdee15f2137f020fffded98b4bdee5d8bec8e.zip
Click to expand...
Click to collapse
The way i did it to simplify was to just copy and paste the commands unfortunately my shell wasn't executing the script correctly I had some errors
Eazii said:
I just wanted to thank the OP for making this process easy with the instructions and for the new life given to this phone. Now that the phone has been converted to the global version what happens if another update comes down the pipe? Do we flash the global version, at&t version, or sit tight and await further instructions ?
Click to expand...
Click to collapse
I have the same question when the duo announcing the newest OTA. The at&t Duo which turned to a global variant can update by OTA or must flash the new images by this method.
Draco32 said:
The way i did it to simplify was to just copy and paste the commands unfortunately my shell wasn't executing the script correctly I had some errors
Click to expand...
Click to collapse
copy and paste what commands exactly? are you saying do each .img 1 by 1? or something else? i copy/paste the commands from the github but i got stuck at 47% same as the other guy.
I just received a OTA update and it failed. I followed this method to unlock my At&t version.
How do I go about updating, but more importantly which OTA should I be looking to flash, At&t or Global?
run sideload to 94% already but still locked sim. how to know if esim is working?
Eazii said:
I just received a OTA update and it failed. I followed this method to unlock my At&t version.
How do I go about updating, but more importantly which OTA should I be looking to flash, At&t or Global?
Click to expand...
Click to collapse
Can you please confirm if esim capability was available or not after installing global variant image?
thanks!
Hi everybody,
I noticed this repository wasn't up anymore which I thought was a crying shame so I managed to track down the source code and re-uploaded it here:
GitHub - EyeCantCU/surface-duo-globalify: Converts AT&T Surface Duo to global firmware
Converts AT&T Surface Duo to global firmware. Contribute to EyeCantCU/surface-duo-globalify development by creating an account on GitHub.
github.com
I make no promises this will work successfully on your device and take no responsibility for whatever may happen. My Duo (I want in on that 3/ds and Windows 11 action) is in the mail and I'm going to be trying this myself.
CertifiedBlyndGuy said:
Hi everybody,
I noticed this repository wasn't up anymore which I thought was a crying shame so I managed to track down the source code and re-uploaded it here:
GitHub - EyeCantCU/surface-duo-globalify: Converts AT&T Surface Duo to global firmware
Converts AT&T Surface Duo to global firmware. Contribute to EyeCantCU/surface-duo-globalify development by creating an account on GitHub.
github.com
I make no promises this will work successfully on your device and take no responsibility for whatever may happen. My Duo (I want in on that 3/ds and Windows 11 action) is in the mail and I'm going to be trying this myself.
Click to expand...
Click to collapse
the link was unable now. Cloud u share it again?
cyhd said:
the link was unable now. Cloud u share it again?
Click to expand...
Click to collapse
A bit of googling found the repo https://github.com/kenpc-git/surface-duo
I wonder if updates worked after this? would this be a way for AT&T users to get the latest 12L update?
Anyone who used this and is running it still? Any issues?
Worked for me, flashed it to global and it automatically upgraded to 12L
When I try the adb sideload I have the following message:
------------------
E:
(adbd status 5)
Install from ADB completed with status 1.
Installation aborted.
-------------------
Can someone help on this ? Thank you.
Hoffman404 said:
@Draco32 or @filfat
First:
1|duo:/data/local/tmp # chmod +x globalify.sh && ./globalify.sh;
./globalify.sh[7]: syntax error: unexpected 'newline'
1|duo:/data/local/tmp #
Why error?
Next:
I am assisted by the guide on this page:
GitHub - filiphsandstrom/surface-duo: Convert a Surface Duo AT&T to the global variant.
Convert a Surface Duo AT&T to the global variant. Contribute to filiphsandstrom/surface-duo development by creating an account on GitHub.
github.com
I'm on step 8. At 47%, it shows me an aborted installation message. Reason: incompatibility.
How to solve it?
I took the system from:
https://android.googleapis.com/packages/ota-api/package/a9bfdee15f2137f020fffded98b4bdee5d8bec8e.zip
Click to expand...
Click to collapse
I had the same issue regarding "syntax error: unexpected 'newline' "
Any clue or update to it?
Draco32 said:
I had great success with this and have relocked the bootloader as a normal duo device thanks, if anyone has any questions about how i managed it let me know. Thanks so much @filfat
Click to expand...
Click to collapse
Could you tell the process of relocking bootloader?
Hello guys,
I have seen a lot of topics on this subject and honestly i don`t know were to start. Yes, i am a old guy and total noob on flashing roms and so on...
Recently my carrier in RO, Vodafone has implemented an option that allows using ESIM on other devices. that being said i proceed activation the option and trying to make my trusty companion R815F to work. Went to Samsung care and they told me that the watch is using an UK region code and will not work with my RO carrier. ( bought the watch also in Romania but .. well apparently it was destinate for other country code)
My watch :
Model number: SM-R815F
Serial: RFAN31FSY2E
SW version: R815FXXU1HVG1 SM-R815FZKABTU
Tizen version: 5.5.0.2
What have i done till now:
- developer mode on
-debug mode on
-download ODIN
-download SDK
-connected to watch via CMD
-tried launch_app csc-manager.csc-pre-configuration - getting an error " internal/external comand ... etc"
Now, being a total noob i don`t understand the next steps:
- do i need combination file and firmware rom for changing the region ?
- do i need to downgrade to tizen 4 in order to do something ? ( how to ?)
- where to find stock firmware - which one to choose because i found something that is paid and i don't want to waste money on something that is not working
Please if anybody can help me or give me a hint were to start it will be much appreciated.
Thank you,
A
Code:
COMBINATION-FT40_R815FXXU1ATA1.tar.md5
Risk because untested...
ATA1 could be dangerous outdated...
No idea from where to download this file... for free...
I will do some search...
Best Regards
Thanks for the feedback. i will wait for your findings.
Hi,
Sorry for being so impatient But did you find something?
Thank you,
A
Sorry.
I have nearly nothing on my HDDs... only really old files.
My suggestion for you.
Search for Firmware Files in Internet...
You can post here what you found. BEFORE you try,,,
For instance start with this file:
Code:
COMBINATION-FT40_R815FXXU1ATA1.tar.md5
Sorry I have my own problems and limited time and energy...
So you at your own...
Good Luck.
Best Regards
You searched for SM-R815 - CombinationFirmware.com
combinationfirmware.com
Here seems only older...
You searched for SM-R815 - Samsung Combination File
samsungcombinationfile.com
Here seems no F...
Found via Google...
I finally made it work thank to user: Jon199102 on Reddit.
He point me to a "hidden feature" of Galaxy Wearables - hidden menu to activate QR code searching/integrating -> auto or manually set up the ESIM. after enabling it i scan my qr code from VDF Ro and 10 minutes later everything was working
I don't really know if it is allowed to post the link to Reddit but here it goes :
https://www.reddit.com/r/GalaxyWatch/comments/qqip1p
Thank you adfree for your time and knowledge sharing. helped me also in understanding a little bit the region change
Thanks