samsung i9100 and "Firmware upgrade encountered an issue..." - Galaxy S II Q&A, Help & Troubleshooting

Hi,
i have an old samsung i9100 (galaxy S2) that i would like to prepare for my 9 yo kid.
i wanted to upgrade ROM to android 7 but it crashed and when phone boots it displays "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
I read a lot of articles and saw several videos about it but nothing work as they said.
Therefore i was thinking to flash a new version of TWRP at first like 3.1.1 but when i do that in ODIN 3.12 it always failed. Phone is normally connected as COM1.
The same issue i have when i try to flash a new rom...it fails on CACHE part.
Someone can help me please ? I already flashed a lot this phone without any issue as 2 other Samsung S5 Neo. So i do not understand what is the problem.
if i try Heimdall i got this error when i run "heimdall print-pit --verbose" command:
Code:
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Manufacturer: "SAMSUNG"
Product: "Gadget Serial"
length: 18
device class: 2
S/N: 0
VID:PID: 04E8:685D
bcdDevice: 021B
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 83
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0040
polling interval: 00
endpoint[1].address: 02
max packet size: 0040
polling interval: 00
Claiming interface...
Setting up interface...
Initialising protocol...
ERROR: Failed to send data: "ODIN"
Releasing device interface...
thx

is there someone on this part of forum ?

Flash Lineage 16 or Carbon 7!
We give children the best things.
Let him learn. When you help your child, he will quickly chase you away.
The message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" means that you have lost the stock ROM system partitions.
You need to flash again the ROM stock you find in the Carbon thread.
With the help of Odin you flash in the download mode.

I have the stock ROM but ODIN still do not send data to mobile. Even a single PIT file worked but did not allow to flash stock ROM
heimdall just show it in command line with "ERROR: Failed to send data: "ODIN"" as error
here it is where it stucks when i upload stock firmware using ODIN 1.85
using ODIN 3.12 is almost the same issue:
i tried in comptibility "Windows XP - SP 2" and also in SP3... running ODIN under administrator
unfortunately, nothing helped so far. any idea ?

Related

[Q] Heimdall support

I understand that as of now Odin is the only option, but does anyone know if Heimdall is being worked on to work for the SGS3? Thanks.
I've not asked/talked/heard about it from anyone. But i could try to find out.
I would appreciate any information. Thanks in advance. I'm new to this forum, coming from the Evo 4g. Over there I know who to talk to, but I am pretty clueless when it comes to Sammy. I am reading as much as I can though.
Sent from my PC36100 using xda app-developers app
I've emailed Benjamin Dobell (hope i spelled that right), the creator of Heimdall. I'm just awaiting a response.
mrhaley30705 said:
I've emailed Benjamin Dobell (hope i spelled that right), the creator of Heimdall. I'm just awaiting a response.
Click to expand...
Click to collapse
Wow, thanks. You really went above and beyond for me. I was mostly expecting to get flamed or ignored. Cheers.
Sent from my PC36100 using xda app-developers app
All i did was send an email. It is a legitimate question since some type of flash utility is usually required to mod a Samsung phone. I used Heimdall and Odin on my captivate, but preferred Heimdall when flashing bootloaders.
FWIW, Heimdall is known to work with the international S3, and I don't see why it shouldn't work with the US variants.
I haven't rooted yet (as I'm giving it a few days unrooted), but when I do, it'll be with Heimdall, as my phones never touch Windoze (and Odin.exe) if they don't have to. My Captivate was only ever connected to my Linux boxes.
I have tried using Heimdall with my AT&T '747 and was unable to get the phone to communicate with my PC. I have read in various non-authoritative places that this is a known issue but I haven't really seen it any where I'd consider to be reliable just yet. I can't confirm 100% that its a Heimdall issue as I haven't used is successfully with another phone (I'm coming from fastboot land).
[email protected]:/home/mmschnei# heimdall flash --recovery Desktop/recovery.img
Heimdall v1.3.1, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
ERROR: Failed to initialise protocol!
Re-attaching kernel driver...
Click to expand...
Click to collapse
NOTE: I have tried this with Heimdall v1.3.2 and v1.3.1. In the above snippet I am using 1.3.1 but I get the exact same message in 1.3.2.
Can anyone else confirm that heimdall does NOT work for them in linux/mac?
Please keep us updated if you hear back from Mr. Dobell.
heimdall v1.3.2
So, I just checked heimdall v1.3.2 out from git (not touched in 3 months), built it, put my phone in download mode, then connected USB (using Fedora 17):
Code:
Jun 30 16:16:56 ivy kernel: [ 853.566542] usb 2-1.6.2: new high-speed USB device number 104 using ehci_hcd
Jun 30 16:16:56 ivy kernel: [ 853.641091] usb 2-1.6.2: New USB device found, idVendor=04e8, idProduct=685d
Jun 30 16:16:56 ivy kernel: [ 853.641096] usb 2-1.6.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jun 30 16:16:56 ivy kernel: [ 853.641099] usb 2-1.6.2: Product: MSM8960
Jun 30 16:16:56 ivy kernel: [ 853.641101] usb 2-1.6.2: Manufacturer: Sasmsung
Jun 30 16:16:56 ivy kernel: [ 853.641770] cdc_acm 2-1.6.2:1.0: This device cannot do calls on its own. It is not a modem.
Jun 30 16:16:56 ivy kernel: [ 853.641822] cdc_acm 2-1.6.2:1.0: ttyACM0: USB ACM device
Jun 30 16:16:56 ivy mtp-probe: checking bus 2, device 104: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6.2"
Jun 30 16:16:56 ivy mtp-probe: bus: 2, device: 104 was not an MTP device
Linux sees it (though "Sasmsung" is typo'd in udev), and heimdall detects it, but it couldn't print-pit, so, probably not working:
Code:
[[email protected]:0j:1023h:0e:5.85MB sgs3]$ sudo heimdall detect
Device detected
[[email protected]:0j:1024h:0e:5.85MB sgs3]$ sudo heimdall print-pit
Heimdall v1.3.2, Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
ERROR: Failed to initialise protocol!
Re-attaching kernel driver...
Development and support will continue for Heimdall for the foreseeable future. Unfortunately I have been very very busy lately and haven't even had time to respond to all my e-mails, so I definitely haven't made a lot of development progress.
I do own an international SGS3 so Heimdall will definitely support that device. Heimdall 1.3.2 unfortunately broke compatibility with several devices as I attempted to add support for certain Galaxy Player devices. The SGS3 is one such affected device. So for now I recommend using version 1.3.1.
Benjamin Dobell said:
Development and support will continue for Heimdall for the foreseeable future. Unfortunately I have been very very busy lately and haven't even had time to respond to all my e-mails, so I definitely haven't made a lot of development progress.
I do own an international SGS3 so Heimdall will definitely support that device. Heimdall 1.3.2 unfortunately broke compatibility with several devices as I attempted to add support for certain Galaxy Player devices. The SGS3 is one such affected device. So for now I recommend using version 1.3.1.
Click to expand...
Click to collapse
Thank you so much! I truly appreciate your response and all your work.

Install Android on I9300_TIZEN device

Hi all,
I own one i9300_TIZEN phone thanks to a Tizen event, and since I've saw what Tizen OS looks like (no comment), I'm really interesting in flashing Android on the device. Before coming in the forum and asking question, I previously made researchs and try some things.
So first I tried heimdall in order to directly flash a recovery (i hoped it will be as easy) but it gives the following output :
Code:
[email protected] ~/Desktop $ sudo heimdall flash -RECOVERY recovery-clockwork-touch-6.0.3.1-i9300.img --verbose --stdout-errors --no-reboot
[sudo] password for padawan:
Heimdall v1.4 RC1
Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Initialising connection...
Detecting device...
Manufacturer: "SAMSUNG"
Product: "SLP"
length: 18
device class: 2
S/N: 0
VID:PID: 04E8:685D
bcdDevice: 0100
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.00
endpoint[0].address: 83
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.FF
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 02
max packet size: 0200
polling interval: 00
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
WARNING: Control transfer #1 failed. Result: -9
WARNING: Control transfer #1 failed. Result: -1089611880
WARNING: Control transfer #2 failed. Result: -9
WARNING: Control transfer #2 failed. Result: -1089611880
WARNING: Control transfer #3 failed. Result: -9
WARNING: Control transfer #3 failed. Result: -1089611880
WARNING: Control transfer #4 failed. Result: -9
WARNING: Control transfer #4 failed. Result: -1089611880
WARNING: Control transfer #5 failed. Result: -9
WARNING: Control transfer #5 failed. Result: -1089611880
WARNING: Control transfer #6 failed. Result: -9
WARNING: Control transfer #6 failed. Result: -1089611880
ERROR: Failed to send data: "ODIN"
ERROR: Failed to send data: "�"
Releasing device interface...
It seems that the device is just not recognize by the tools, and I don't know how to solve this issue.
So for the moment I don't really know how to proceed. I know that first I may have to do a dump of my device in order to reflash it in case of issue. I saw that I may be able to do it thanks to Tizen commands, but I'm not completely sure. Some tizen tools looks very similar to android ones (like sdb with the same functions that adb), but I didn't know if it may be a solution (because tizen commands may do tizen stuff, and that's not what I'm looking for).
It may also be useful for me to know the exact hardware of my device. It may be very close to i9300, but I want to be sure before doing anything.
Another solution may be to flash a I9300 .pit file to "flash" my device, but I never use it before so i don't really understand the real risks of this solution and the process.
So for the moment I don't really know how to proceed, that's why i'm creating this thread.
Thank you,
up
I think there will no further investigation in this case. I'm interested too. But to less people got access to this devices.
So I think we have to wait until the tizen release.
Gesendet vom Handy mit Tapatalk.
Catscratch said:
I think there will no further investigation in this case. I'm interested too. But to less people got access to this devices.
So I think we have to wait until the tizen release.
Gesendet vom Handy mit Tapatalk.
Click to expand...
Click to collapse
I know but my main problem is that I don't know the tools needed to make these investigations. I don't want someone to write a precise tutorial, but I just need some advices to go further in my investigations.
http://www.youtube.com/watch?v=JXvOcGJ6zXo
Maybe in this way...
Untested from Tizen to Android...
Best Regards
Edit 1.
As hint...
Odin Tool for Android receive ODIN as text string for identification from Android handset...
Thor receive THOR from Tizen crap...
I can not try complete... as no Android nor Tizen real handset here in my hands...
Short played with S8500 and SBL Bootloader from Android handsets...
http://forum.xda-developers.com/showpost.php?p=44162575&postcount=12
http://forum.xda-developers.com/showpost.php?p=44188307&postcount=13
Edit 2.
Found this Decrypted:
https://hotfile.com/dl/234791315/5b8c314/GSIII_Recovery_guide_v2.pdf.html?lang=en
I have found this encrypted Doc and files too...
Nascar encrypted files seems often used by Sxmsung...
2.2.1 is released...
Maybe big "surprice"...
http://download.tizen.org/releases/2.2.1/tizen-2.2.1/images/RD-PQ-REF/
No idea why the wifi Version is 1100 MB big...
Best Regards

S5830i flashing problem

Yesterday I got a S5830i that I should try to fix. The background story is that the Google Play Services took over aprox. 100 MB (a large amount of device memory), so they were deleted or their updates were. That led the phone to being unresponsive so the battery was removed (that's what I was told). After that the phone keeps reseting ... splash screen, samsung boot animation ... over and over again.
So I checked what could be done. The phone has a stock ROM and it's not rooted. First i've found out that /data cannot be mounted (Error mounting data). Other topics suggested only flashing stock firmware using Odin.
Then I installed drivers on a windows machine, prepaired Odin with pit and a stock firmware. Then I've put the phone into download mode. The problem is ... the phone is not detected in Odin whatsoever ... changing drivers, installing kies ... nothing. Device manager says that the phone is unknow device and no driver helps.
The last attempt was on my linux machine running a ubuntu 14.04 derivate. Using heimdall 1.4.0 I only get Device detected. Using a hemdall frontend I can get it to print pit too ...
Code:
Initialising connection...
Detecting device...
length: 18
device class: 2
S/N: 3
VID:PID: 04E8:685D
bcdDevice: 0001
iMan:iProd:iSer: 2:1:3
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 83
max packet size: 0040
polling interval: 05
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 20
endpoint[1].address: 02
max packet size: 0200
polling interval: 20
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
ERROR: Setting up interface failed!
Releasing device interface...
Re-attaching kernel driver...
And here it stops. I'm always getting error that setting up interface has failed. Just for test I flashed the CWM and some ROM from xda. Everything was invalidated after restart ... stock recovery, error mounting data.
Is there anything I can do? I really tried almost everything.
Update: after reinstallation of all drivers the phone can be flashed. However, after odin flash is complitet, phone reboots and recovery says "cannot mount /data (invalid arguments)" at the multi CSC section. Close but not there yet. What to do?

Cannot use Odin/Heimdall

Hey everyone, I am trying to flash my SM-G9650 with TWRP but both Odin and Heimdall fail in doing so. I've tried Odin on Windows 10 (with Samsung drivers), Heimdall on Windows 10 (with WinUSB or LibUSBk) and even Heimdall on Manjaro Linux (with libusb) but none work. They all either hang at initialising, during initialising, or just fail with no error (Odin). For instance, Heimdall on Manjaro Linux gives this:
Code:
Heimdall v1.4.2
Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
ERROR: Failed to send handshake!ERROR: Protocol initialisation failed!
Releasing device interface...
And this is what appears on my download mode:
Code:
RPMB fuse blown
RPMB Provisioned
CURRENT BINARY:Samsung Official
OEM LOCK: OFF
REACTIVATION LOCK: OFF
WARRANTY VOID: 0X0
QUALCOMM SECUREBOOT: ENABLE
RP SWREV : b9(2,2,2,9,2) K9 S9
SECURE DOWNLOAD: ENABLE
DID: 20208B2BEA756311
I've tried the usual, different USB ports, cables, restarting PC, but nothing makes the trick. I even tried to flash the official Samsung firmware, same bit (9) and everything but still, nothing. Both OEM Unlock and USB Debugging are enabled, and I think I don't need to use CROM Service anymore, and if I do I'm in an uncomfortable situation because it doesn't even open on my Android 10 firmware...
frangamer18922 said:
Hey everyone, I am trying to flash my SM-G9650 with TWRP but both Odin and Heimdall fail in doing so. I've tried Odin on Windows 10 (with Samsung drivers), Heimdall on Windows 10 (with WinUSB or LibUSBk) and even Heimdall on Manjaro Linux (with libusb) but none work. They all either hang at initialising, during initialising, or just fail with no error (Odin). For instance, Heimdall on Manjaro Linux gives this:
Code:
Heimdall v1.4.2
Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
ERROR: Failed to send handshake!ERROR: Protocol initialisation failed!
Releasing device interface...
And this is what appears on my download mode:
Code:
RPMB fuse blown
RPMB Provisioned
CURRENT BINARY:Samsung Official
OEM LOCK: OFF
REACTIVATION LOCK: OFF
WARRANTY VOID: 0X0
QUALCOMM SECUREBOOT: ENABLE
RP SWREV : b9(2,2,2,9,2) K9 S9
SECURE DOWNLOAD: ENABLE
DID: 20208B2BEA756311
I've tried the usual, different USB ports, cables, restarting PC, but nothing makes the trick. I even tried to flash the official Samsung firmware, same bit (9) and everything but still, nothing. Both OEM Unlock and USB Debugging are enabled, and I think I don't need to use CROM Service anymore, and if I do I'm in an uncomfortable situation because it doesn't even open on my Android 10 firmware...
Click to expand...
Click to collapse
Did you manage to find out what the problem was? I have a similar situation with a Note 10+. I am starting to suspect that Samsung made it unflashable after certain update, like i've read som devices can be..
And by the way how did you manage to flash official firmware?

PX5 Maskrom flash error prepare idb fail

Hello folks,
I've been fighting for three days with my PX5 board from my Xtrons radio.
As the first I tried to flash the core board with OTP USB cable with Android 10.
First I did it with the loader that I connected to the RK Dev Tool and then I clicked on RUN!
Everything went to the end without Fefler. Log file here:
20:27:03 217 RKDevTool v2.7.1.0 start run
20:29:23 860 RKDevTool v2.7.1.0 start run
20:38:00 243 Layer<>: RunProc is ending, ret=0
21:14:18 490 Layer<>: RunProc is ending, ret=0
21:25:10 623 RKDevTool v2.7.1.0 start run
21:33:09 243 RKDevTool v2.7.1.0 start run
22:20:46 879 Layer<1-4>:Test Device Start
22:20:46 886 Layer<1-4>:Test Device Success
22:20:46 890 Layer<1-4>:Check Chip Start
22:20:46 895 Layer<1-4>: Check Chip Success
22:20:46 899 Layer<1-4>:Get FlashInfo Start
22:20:46 902 <LAYER 1-4> INFO:FlashInfo: 00 00 A4 03 00 04 04 00 28 00 01
22:20:46 906 <LAYER 1-4> INFO:GetFlashInfo-->Emmc storage.
22:20:46 911 Layer<1-4>:Get FlashInfo Success
22:20:46 915 Layer<1-4>repare IDB Start
22:20:46 918 <LAYER 1-4> INFO:CS(1) (29824MB) (SAMSUNG)
22:20:46 929 Layer<1-4>repare IDB Success
22:20:46 931 Layer<1-4>ownload IDB Start
22:20:47 056 Layer<1-4>ownload IDB Success
22:20:47 058 Layer<1-4>:Wait For Loader Start
22:20:47 633 Layer<1-4>:Wait For Loader Success
22:20:47 635 Layer<1-4>:Test Device Start
22:20:47 641 Layer<1-4>:Test Device Success
22:20:47 649 Layer<1-4>: Download gpt...
22:20:47 666 Layer<1-4>: Download uboot at 0x00004000...
22:20:47 848 Layer<1-4>: Download trust at 0x00006000...
22:20:48 007 Layer<1-4>: Download misc at 0x00008000...
22:20:48 020 Layer<1-4>: Download dtbo at 0x0000c000...
22:20:48 030 Layer<1-4>: Download vbmeta at 0x0000e000...
22:20:48 044 Layer<1-4>: Download boot at 0x0000e800...
22:20:49 208 Layer<1-4>: Download recovery at 0x0001e800...
22:20:51 116 Layer<1-4>: DownloadSparse super at 0x00150c00...
22:20:51 116 INFOownloadSparseImage-->erase start,file=..\rockdev\Image\super.img,unsparse=9437184,partition=9437184
22:20:53 460 INFOownloadSparseImage-->write sparse start,total_chunk=3084
22:22:08 987 Layer<1-4>: DownloadSparse oem at 0x00a50c00...
22:22:08 987 INFOownloadSparseImage-->erase start,file=..\rockdev\Image\oem.img,unsparse=2097152,partition=2097152
22:22:09 435 INFOownloadSparseImage-->write sparse start,total_chunk=14
22:22:12 927 Layer<1-4>: RunProc is ending, ret=1
22:25:41 358 Layer<>: RunProc is ending, ret=0
Click to expand...
Click to collapse
Then I unplugged the USB cable and I no longer have a connection.
Today I tried again and with the help of short circuits from contact to ground and I have Maskrom connection.
Like HERE
Then I clicked on erase under UPDATE FIRMWARE and everything went to the end without any problems. Then I tried to UPDATE the appropriate inage but keep getting the error "prepare idb fail" and connection are lost.
Can someone help me?
Does anyone have what idea how do I get ahead?
thanks
Try different versions of rktool, Ive experienced this problem before.
Unfortunately does not help! I tried with 3-4 versions of rktool and also with RockChip_Batch_Tool_v1.8.
Always the same.
I would try two different thing, first see if you have a USB 2 only port and test using that one, second trick that has worded many times for me is using a VM under virtualbox, i find the client(1/2 cpu's only) being a little slower helps and setting usb 2 under settings.
darkspr1te
Hello people,
I reinstalled my core board, but without an operating system it is practically empty.
Then the radio switched on and booted from SD card with Android 10 installation.
The radio boots from the SD card and the display shows ANDROID 10 lettering and then the Androird 10 is being installed and "the circle" can be seen.
After a short time you can see Android male on the display and it says "ERROR".
Then the picture below appears.
What does that mean?
And what am i doing wrong?
vouager said:
Hello people,
I reinstalled my core board, but without an operating system it is practically empty.
Then the radio switched on and booted from SD card with Android 10 installation.
The radio boots from the SD card and the display shows ANDROID 10 lettering and then the Androird 10 is being installed and "the circle" can be seen.
After a short time you can see Android male on the display and it says "ERROR".
Then the picture below appears.
View attachment 5426343
What does that mean?
And what am i doing wrong?
Click to expand...
Click to collapse
While I have never had sent to me a SOM with defective storage, it's entirely possible. Every SOM sent to me was recoverable.
You're welcome to send the SOM to me in New Zealand with return freight. No cost other than freight.
Hello marchnz ,
Thank you for your offer, but unfortunately because of our distance and postage costs it does not pay off that I send you the part to NZ.
I bought a new PX5 and my radio works again.
1 week ago everything was ok with the old PX5 and worked perfectly with Android 9
Then I tried to install Android 10 and this mistake happened.
think I'm doing something wrong.
Maybe I have to format flash memory first, but how? Or do I need special files.
I don't want to give up on that part, especially because of my job as an electronics technician and of pure curiosity.
If you can help me in any way it will be great. But shipping and returning really doesn't pay off.
Thanks,
At least it happens to you about test devices, I always fail, I don't know what to do anymore, we have the same board.
Could you upload the files you have to see if I have something that I should not or how you tried to flahse it.
What is a new plate worth and where did you get it? Sorry for my English I use the google translator. greetings from Spain
i have this case, i try lot of many things but nothing happen. so i try plug usb to other port on my computer and it's work. so i think, may be it have some trouble on usb port. or please try on other computer or laptop

Categories

Resources