Database Users

[Q] Asus Vivo Tab E400CL won't boot only reboot with Bios error message

Hello ,
I got an Asus Tab today to fix booting issue .
The Tab won't boot correctly I have only a black Bios screen rebooting .
with this message while rebooting cycle..
Code:
American Megatrends
ASUS ME400C BIOS Revision 0501, Build Date
EC1 version: PAD-EC31C-0015
WINKEY version: ME400C-ECFG_0103.ROM
Read AtmelTouchFW Version failed, Recovery...
I tried to go to Bios setting without success , How may I handle this issue ?

I have the some problem how to gix pleasse

Huawei E392 4G USB Dongle stuck in download mode

Hi everyone
Please I need a real help
My Huawei E392 usb dongle stuck in download mode after a fault firmware upgrade
I was trying to flash my usb dongle and by mistake i choose the wrong firmware update and now the dongle is not recognized and can't restore the original firmware
and now application interface & diag interface are changed
Before firmware update in device manager :
Code:
3G Application Interface
3G PC UI Interface
And now I get :crying: :
Code:
FC Application Interface
FC UI Interface
Error when try to pass the correct firmware :
Code:
Error code:10, Find port failed.
Another important remark : The LED of dongle loop between blue and green color , 2seconds 2seconds signal
Can anyone help me :highfive:
Problem solved :
Finally my problem is solved
I forced the installation of the driver of Huawei 3G Application Interface and then Huawei Flasher tool recognized my modem and I used Resurrect Mode , Proccess finish successfully
Sorry for my English.

Help to restore bootloader on Nokia 6

Help to restore bootloader on Nokia 6

What happened? We are no magicians

ZeroPointMax said:
What happened? We are no magicians
Click to expand...
Click to collapse
The phone worked properly, but I wanted to install the European firmware, through the program QFIL I installed the firmware in the phone, and after that the phone does not turn on, or rather all the LEDs light up and the computer determines how Port Diagnostics 900E? I ported the drivers all without result. can not enter mode Downalds mod ...

Evgeny_14 said:
The phone worked properly, but I wanted to install the European firmware, through the program QFIL I installed the firmware in the phone, and after that the phone does not turn on, or rather all the LEDs light up and the computer determines how Port Diagnostics 900E? I ported the drivers all without result. can not enter mode Downalds mod ...
Click to expand...
Click to collapse
Oops, you bricked your device. You cannot flash another region if that was your intention... You can either go to customer support or try to make a USB flash cable to force the files onto your device (pls use original firmware for your device). I know that this was mentioned in the forum before but I cannot remember where exactly and I don't know if it is actually working. If it fails, your device is pretty much ******...

Just use the OST Tools and official firmware to root ur device.
Tutorial video:
OST Tools and firmware download: https://forum.xda-developers.com/nokia-6/development/nokia-6-official-firmware-mena-region-t3664441
Recovery download: https://forum.xda-developers.com/no...ecovery-project-nokia-6-t3650499/post73625011
Guide: https://forum.xda-developers.com/no...de-how-to-flash-custom-recovery-root-t3702354

Nokia 6 (TA-1003) bootloader restore how?
Dear,
My phone will not start up
How can i restore the bootloader an reflash the firmware?
I hope on a solution!
Greet,
Marno

desesperated
richardpimenov2001 said:
Just use the OST Tools and official firmware to root ur device.
Tutorial video:
OST Tools and firmware download: https://forum.xda-developers.com/nokia-6/development/nokia-6-official-firmware-mena-region-t3664441
Recovery download: https://forum.xda-developers.com/no...ecovery-project-nokia-6-t3650499/post73625011
Guide: https://forum.xda-developers.com/no...de-how-to-flash-custom-recovery-root-t3702354
Click to expand...
Click to collapse
Hi there. I'm a new user so i don't have enought privileges to make a tread about my issues. So i will try to be the most clear possible.
I got a Nokia 6 TA-1039 so i tryed to root it and that's why I'm here.
First of all the phone is now on Qualcomm HS-USB Qloader singed on 04/01/2013 and it's 2.1.0.5 version, by Xiaomi Technology Inc., then when i connect to the PC it recognizes it in that port. In the other hand, the device doesn't make any noise or dispolay anything on the screen, but in the pc it appears when i connect it.
I have downloaded following the treads the firmware Nokia_TA-1025_MSM8937_25082017_7.1.1.zip and extracted it. I was trying to use it with QFIL version 2.0.0.5 and using as configuration the next steps:
-Download protocol: 0-Sahara
-Device type: UFS
Validation mode: 0-No validation
[
then when i run it i found the next errors:
Error function: Sahara _rx_data: 194 unable to read packet header Only read 0 bytes
Error function: Sahara_main: 854 sahara protocol error
Error function: Sahara_main: 265 Uploading image using sahara protocol failed
Download fail: Sahara fail: QSaharaServer fail: Process fail
Then i tryed to flash it using Xiaomi MiFlash.exe and the errors are:
Cant found programmer file
Cannot recive Hello packet
cannot read hello packet
adittional to this I have a cable that i think that it's a EDL cable by GPGIndustries like this
http://shop.gpgindustries.com/produc...ml?pb=108&pc=2
I'm very desesperated about this. If someone can call me or help me in any way i really appreciate it.

grandroid7 said:
Dear,
My phone will not start up
How can i restore the bootloader an reflash the firmware?
I hope on a solution!
Greet,
Marno
Click to expand...
Click to collapse
I had exactly the same thing. . You must send the phone to the service.

Maxpowers88 said:
Hi there. I'm a new user so i don't have enought privileges to make a tread about my issues. So i will try to be the most clear possible.
I got a Nokia 6 TA-1039 so i tryed to root it and that's why I'm here.
First of all the phone is now on Qualcomm HS-USB Qloader singed on 04/01/2013 and it's 2.1.0.5 version, by Xiaomi Technology Inc., then when i connect to the PC it recognizes it in that port. In the other hand, the device doesn't make any noise or dispolay anything on the screen, but in the pc it appears when i connect it.
I have downloaded following the treads the firmware Nokia_TA-1025_MSM8937_25082017_7.1.1.zip and extracted it. I was trying to use it with QFIL version 2.0.0.5 and using as configuration the next steps:
-Download protocol: 0-Sahara
-Device type: UFS
Validation mode: 0-No validation
[
then when i run it i found the next errors:
Error function: Sahara _rx_data: 194 unable to read packet header Only read 0 bytes
Error function: Sahara_main: 854 sahara protocol error
Error function: Sahara_main: 265 Uploading image using sahara protocol failed
Download fail: Sahara fail: QSaharaServer fail: Process fail
Then i tryed to flash it using Xiaomi MiFlash.exe and the errors are:
Cant found programmer file
Cannot recive Hello packet
cannot read hello packet
adittional to this I have a cable that i think that it's a EDL cable by GPGIndustries like this
http://shop.gpgindustries.com/produc...ml?pb=108&pc=2
I'm very desesperated about this. If someone can call me or help me in any way i really appreciate it.
Click to expand...
Click to collapse
I dont know if this would help you guys or not but this is portable one,
You dont need to configure any sahara file or anything, just select mbn file then xml and hit download
This tool helped me alot for so many other phone which gave me sahara error
Find the tool in the attachment
Hope this will help you
Hit thanks button if you find this helpful
Happy flashing
jurek09 said:
I had exactly the same thing. . You must send the phone to the service.
Click to expand...
Click to collapse

Can't flash anything - ODIN MODE - UDC START

Hello,
I just got two used note3 phones from different sellers and try to install twrp.
The phones run Android 5.0
I can boot into Bootloader, into (stock) recovery and into system.
But neither with Linux/heimdall nor with Windows/Odin I can talk to the phone or flash a twrp recovery.
Under Linux a
Code:
heimdall print-pit --no-reboot --verbose --resume
results in this:
Code:
Heimdall v1.4.1
Copyright (c) 2010-2014 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: "Sasmsung"
Product: "MSM8960"
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.01
endpoint[0].address: 82
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: 0200
polling interval: 00
endpoint[1].address: 01
max packet size: 0200
polling interval: 00
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
Some devices may take up to 2 minutes to respond.
Please be patient!
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
Session begun.
Downloading device's PIT file...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
. . .
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
. . .
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: libusb error -7 whilst receiving packet.
Releasing device interface...
When I boot into bootloader mode it shows
ODIN MODE
then then the normal information and ends with
UDC START
(see attachment)
Does anybody know what's wrong here?
Thanks in advance

Odin at what point does the flash fail .
You have flashed Samsung usb drivers ??

JJEgan said:
Odin at what point does the flash fail .
You have flashed Samsung usb drivers ??
Click to expand...
Click to collapse
Please provide PIT FILE 32GB before you get this problem. Its your cases like me get this one. Put this pit file on colum PIT and then put this your firmware blablabla.md5.tar then flash it.

OP be very carefull re PIT .
Flashing can brick your phone.

JJEgan said:
OP be very carefull re PIT .
Flashing can brick your phone.
Click to expand...
Click to collapse
Im trying this step and look success almost done.

Post the Odin log? Tried different USB cables and USB ports?

JJEgan said:
Odin at what point does the flash fail .
You have flashed Samsung usb drivers ??
Click to expand...
Click to collapse
I had the Samsung drivers installed, but still had an unknown SM Bus controller.
Solved this now (it's a freshly installed windows 7 only for this task)
Now the phone shows up in Odin, but I am unsure how to continue.
I downloaded N9005XXSGBPL6_N9005DBTGBOI1_N9005XXUGBOJ1_HOME from sammobile which contains a file named N9005XXSGBPL6_N9005DBTGBOI1_N9005XXUGBOJ1_HOME.tar.md5
I guess I have an "old" model ans so selected this file for "AP" and hit GO. Attached is the screenshot of the result:
When I now restart the phone I get a Message:
"Firmware Upgrade encountered an issue. Please select recovery mode in Kies & try again".
that's weird to ma as Samsung suggests SmartSwitch for models with Android5. But SmartSwitch says "model not supported".
Kies tries to conect forever.
In Odin under "Options" neither "Re-Partition" nor "Nand Erase" is checked. Is this correct?
I'm pretty clueless now

Try a different version of Odin, USB cables, and USB ports.

audit13 said:
Try a different version of Odin, USB cables, and USB ports.
Click to expand...
Click to collapse
I already did change cable and port (and even the computer). Don't know where to get a different Odin version.
However, it's hard for me to imagine how a different USB cable should solve a size problem.
But I don't know, what that "size" error actually means.

I have always had good success with Odin 3.07: https://www.google.ca/url?sa=t&rct=...ad-odin-3-07&usg=AOvVaw0Rcrx5CDctRzS99UIaD36F
If a stock firmware cannot be flashed via Odin/Windows, you may have to have the phone force flashed using alternative hardware such as an Octopus box: https://octopusbox.com/

audit13 said:
I have always had good success with Odin 3.07: https://www.google.ca/url?sa=t&rct=...ad-odin-3-07&usg=AOvVaw0Rcrx5CDctRzS99UIaD36F
Click to expand...
Click to collapse
OK, I got this version now. Unfortunately it produces the same error as posted above. Size error upon flashing hidden.img
. . . hours later. . .
I found a pit file here https://www.sammobile.com/forum/showthread.php?t=30482
And with the HLTE_EUR_OPEN.pit I was able to flash that stock Android5. So at least the phone is alive again. :good:
What I don't understand: My phone came with a N9005BTUGBOJ1 ROM which seems to be British Telecom, Right? But I am in Germany. Is that of any relevance to me?
However. Now I'm back at step one, flashing TWRP and finally LineageOS
That worked fine
So obviously I bricked my phone with Heimdall. With Odin v3.04 flashing has been a pretty straight forward process. The new Odin build failed at the hidden partition.
The "only" problem left is that LineageOS doesn't recognize my SIM-card. :crying:

N9005BTUGBOJ1 ROM
That looks like the CSC not rom .
CSC is customer services basically local network details like APN .
No British Telecom network .
BTU modem is the generic UK modem for non branded devices .

JJEgan said:
N9005BTUGBOJ1 ROM
That looks like the CSC not rom .
CSC is customer services basically local network details like APN .
Click to expand...
Click to collapse
Maybe I used the wrong naming term. Phone status shows this:
Baseband version: N9005XXUGBOj1
The name of the stock ROM I flashed is N9005XXSGBPL6_N9005BTUGBOJ1_N9005XXUGBOJ1_HOME.tar.md5
JJEgan said:
No British Telecom network .
BTU modem is the generic UK modem for non branded devices .
Click to expand...
Click to collapse
Thank you for the clarification. Which one is suitable for Germany? Does it matter at all? With the stock firmware telephony seems worked normally. Only with LineageOS no SIM-Card is detected.

Samsung Galaxy A3 (SM-A300FU) - water damage + fun with flashing

Samsung Galaxy A3 (SM-A300FU) went for a deep swim. A phone shop asked to fix it broke screen, another 2 shops told me to forget about it. So, I replaced the screen myself The screen works, but there is something strange happening.
What works:
- I can get into download mode (*), screen work fine
- I can start the phone (static logo OK, animated logo doesn't show). I can hear sounds, pressing volume works, but the screen stays black.
- I can download photos/videos over usb MTP with linux (phone screen black)
- the phone just beeped, (I guess, for low battery), so the main part of the system seems to be partially OK
What doesn't work"
- screen stays black after normal full start
-(*) download mode a few days ago worked fine, so I downloaded pit file. I also have the original firmware. Now when I try to download pit or flash with heimdall I get:
Code:
[..]Initialising protocol...
WARNING: Control transfer #1 failed. Result: -9
WARNING: Control transfer #2 failed. Result: -9
WARNING: Control transfer #3 failed. Result: -9
WARNING: Control transfer #4 failed. Result: -9
WARNING: Control transfer #5 failed. Result: -9
WARNING: Control transfer #6 failed. Result: -9
Protocol initialisation successful.
[..]
or
Code:
[..]
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
[..]
I tried 4 different cables + 3 usb ports to make sure it's not hardware.
I can provide full logs, but looks like part of the firmware is fried as the result of the water damage. And than probably I made it worse by multiple blind resets (power + vol down) when getting into download mode and resets when getting out of the download mode.
The firmware on the phone was original, no mods, no recovery, no root, no developer mode allowed, no adb over usb.
Any idea how to recover from it? At this stage I need to get contacts, but I'm ready for factory reset just to get the phone back to working condition. Is it worth to get A3 jig or it only helps to get into the download mode?
P.S. Screen stays black after power cycle with vol up + home. Should it go into recovery mode?
P.S.S. The screen is not yet glued in, so I have easy access to the internals of the phone.

I managed to flash twrp recovery, downloaded contacts and then I flashed full firmware. But the screen stays black after normal boot.
The screen in TWRP & download works OK. Any ideas what might be wrong?