Database Users

[HowTo] use 3G Dongle on TF101 *UPDATED 04/13/2012*

Hello,
(First sorry for my very bad english. It's not my natural language but I do my best for sharing with you!)
04/13 - UPDATE: Now 3G works for ICS with some ROMs like Megatron.
Revolver will be based on TF101G ICS ROM soon.
09/17 - UPDATE:Roach2010 and gnufabio have developped an apk that enable Mobile Network settings (for 3G dongle).
Their APK change the bootloader. (Read more and download)
So maybe this thread has no purpose except for issues and for the list of compatible dongles. If you have a dongle which work and which is not in the list.....
11/08 - UPDATE: 3G dongle works too with Extension-Kit/TFUSB1 Asus P/N 90-XB2UOKEX00020
You can find it here: http://shop.asus.fr/shop/fr/fr-FR/Home/1-Produits/1500-Collection-ASUS/1936-Accessoires-Eee-Pad/1937-Accessoires-Transformer-Prime-TF201/90-XB2UOKEX00070-Adaptateur-USB-externe-pour-ASUS-Eee-Pad.aspx (Thanks to ValenteL for information)
************************************************************
Bellow you can find the first post
Thank you,
Regards.
FIRST POST:
There is probably other ways to make the 3G Dongle working on TF101 but here you can find how we have done.
The follow lines work to have Prime v1.5 installed on your Transformer (works with any version!)
Then you could upgrade to Revolver 2.1.
Otherwise you can directly nvflash your TF101 with the Revolver 2.5 NVFlashed version of cuckoopt.
You just have to follow instructions on this post.
Don't forget to thank him if it works for you
Note: SetCpu doesn't seem to work. I don't know if the issue is coming from Revolver or HC. By re-installing SetCpu, it works one time then crashes.
A. Prime V1.5 Installation:
1. You have to backup all your data/apk from your Internal SD Card because we will make a clean install. So use your backup software.
Becareful. if you project to use Titanium Backup, his backup files are on the internal SD Card so afterwards, you have to move it to your MicroSD (from /mnt/sdcard/Titatium Backup to /data/Removable/MicroSD)
2. Download NVFlash: http://www.filefactory.com/file/ccda97c/n/nvflash.zip then the NVFlash version of Prime v1.5: http://www.sdx-downloads.com/devs/roach2010/flash_roms/prime_v1.5_nvflash.tar.bz2
Updated note: I am not able to activate the Mobile Network option with version 1.6 (even Zip version for ClockWorkMod nor NVFlash version).
But some people have succesfully activated it by flashing NetFinder 1.5 just after the fresh Install of Prime v1.6 and before rebooting the system ; it means in the same CWM
3. unpack NVFlash and Prime v1.5 in the same directory. The image files of Prime v1.5 should be unpacked into the NVFLashTF folder.
4. Connect your TF101 to your PC via USB. Then hold the volume UP and Power button until a NEW device named "APX" appears in the Device Manager. Note that the screen of the Transformer stays black.
5. Click on the APX to install drivers from directory USBPCDriver (included in NVFlash.zip)
info: I used Windows XP 32 bits.
6. Then run Download.bat if you are on Windows, download.sh for Linux users
7. When NVFlash is ended, reboot your TF101.
During boot, there is a setup wizard. Choose connection with "3G and Wifi", not "only Wifi"!!
At this step, you must have the Mobile Network option in Parameters.
8. Download Maxh2003 Script: http://android.modaco.com/index.php?act=attach&type=post&id=73836 (you need to be a register user on Modaco You could find another link some posts after!)
Download the Patch files for ACER A500 tab: http://forum.xda-developers.com/attachment.php?attachmentid=638588&d=1309189189
9. Unzip the script and the Patch file in the same directory.
If you want to upgrade to Revolver 2.1 version (HoneyComb 3.2), you must stop here and go to step B (chapter B).
Otherwise continue chapter A.
10. Connect your TF101 and run install-TF101.bat
11. Mobile Network option is here.
B. REVOLVER 2.1 Installation
1. Do a fresh install of Prime v1.5 NVFlsh version.
If it's not the case go back to the begin of this post and execute steps A.1 to A.9. then go back to B.2
2. Download this file
3. If you read this, Prime v1.5 NVFlash version is installed and you are in CWM Recovery screen.
Install the Recovery 2.1 version (Full). DON'T WIPE DATA
4. At the end, just reboot your system and verify that Mobile Network option is still here.
5. Then we have to install drivers for your dongle (see the list below for compatible dongles).
Let your TF101 on, connect it to your PC via USB cable and run install-TF101.bat via cmd.exe from Windows (tested under Windows XP x86 and Windows 7 x64)
C. List of COMPATIBLE DONGLES
Note: if your dongle is not in this list, but works with TF101, please tell me. It will be added to the list.
* ZTE MF 639 (might need roaming enabled to get data working)
* Alcatel X225L (thx to urko95)
* Vodafone K3765-H
* Vodafone K3715
* Vodafone K3565 / Huawei E160
* Huawei E156G (thx to sh337 for testing)
* Huawei E160G (thx to htc-hd2. His post)
* Huawei E161 (thx to zumbik. His post)
* Huawei E169
* Huawai E170
* Huawai E171
* Huawei E173 (ATTENTION: E173 EVO version NOT COMPATIBLE - thx to sronweb for his tests - Read more)
* Huawei E180 (thx to ValenteL. His post)
* Huawei E220 (thx to eyz. Connexion seems to be not stable. Read more)
* Huawei E270 (thx to eyz. His post)
* Huawei E1550
* Huawei E1552
* Huawei E1692
* Huawei E1750
* Huawei E1752
* Huawei E1762 (thx to bennyyen. His post)
* Huawei E1820
* Huawei E1823 (Thx to bswpt. His post)
* Huawei E2010 (Thx to madangryscientis. His post)
* HUAWEI K3520
* HUAWEI K3565 -Rev 2
Click to expand...
Click to collapse
D. About LED on HUAWEI 3G Dongle:[/B]
The LED indicator displays the current connection status of your Orange E1752 dongle, with each colour representing a different status:
When the LED displays green and is blinking twice every three seconds, this means that the dongle is powered on.
When the LED displays green and is blinking once every three seconds, this means that the dongle is attempting to register onto a 2G network.
When the LED displays blue and is blinking once every three seconds, this means that the dongle is attempting to register onto a 3G network.
When the LED displays solid green, this means that the dongle is connected onto a 2G network.
When the LED displays solid blue, this means that the dongle is connected onto a 3G network.
When the LED displays solid cyan, this means that the dongle is connected onto a 3G+ network
When the LED displays no colour, this means that the dongle is removed.
Click to expand...
Click to collapse
And dont forget to turn off the composite device of the 3G dongle.
Here how to do (thanks to Matchstick from Modaco who wrote these lines):
You can test this by plugging the stick into a PC and seeing if it detects the modem as a CD or Memory stick device as well as a modem.
If it does then the method I used to turn off the composite device (on Windows 7) was:
1) Install the software and drivers for the modem under windows and make sure that the connection software sees the modem correctly.
2) Go to Settings/Control Panel/Device Manager and if you expand the Modems section you should see your USB modem listed there
3) Double click on the entry for the modem to get the properties panel up and selected the Modem tab
4) You should see a line at the very top of the tab that says something like Port: COM11 - This is the virtual serial port that the PC uses to talk to the modem which we're going to use to send the command to turn off all the stuff we don't want.
5) Next we want to install a serial console application. PuTTY is perfect for this. If you don't have a copy you can get if from here,
http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html
6) Run putty, select Serial under Connection Typem and enter the port we found in step 4 (eg COM11) into the box marked Serial Line and press the Open button
7) An empty window should pop up, which if things are working correctly is connected to the Modem
8) Type "ATI" into the window (without the quotes) and press return. The ATI command asks the modem for basic information and it should respond with something like
Manufacturer: huawei
Model: E1752
Revision: 11.126.03.01.314
IMEI: 123456789012345
+GCAP: +CGSM,+DS,+ES
OK
9) If you see this then you are connected correctly, if you don't see a response try physicaly unplugging and reconnecting the modem into a different USB port and start again from step 2 after windows has loaded the drivers for the modem.
10) Assuming everything is OK, the we can send the command to turn off the stuff we don't want. To do this simply type "AT^U2DIAG=0" (again without quotes) into the putty window. you should see the response OK.
11) If you do then the composite device features should now be turned off and you are ready to try the modem in your transformer.
Click to expand...
Click to collapse
Remerciements/Thanks to AndroidRoot.mobi for NVFlash, Paul for Prime!, Maxh2003 for his script and help, Matchstick for his help, Dexter_nlb for his A500 patch and, of course, all our developers and users who help us.

Not sure why I've flashed several roms in APX from w7 64 bit just fine.

It seems that these drivers don't work for win7 64 and works for Vista 64.
Perhaps they are unsigned.... didn't know. I don't make more tests.
Regards.

Looking good. Now to get a 3G plan and dongle...

Anyone get this working?

to kasimodo
Could you upload Maxh2003's scrift file here. I can't download it from your link.
Thanks

nsec said:
to kasimodo
Could you upload Maxh2003's scrift file here. I can't download it from your link.
Thanks
Click to expand...
Click to collapse
Here the file.
Regards

insmod is having no luck with these kernel modules, none are loaded, and I get nothing??? what's the deal? has anyone got this working including the OP or is this just a theoretical WIP

dan-htc-touch said:
insmod is having no luck with these kernel modules, none are loaded, and I get nothing??? what's the deal? has anyone got this working including the OP or is this just a theoretical WIP
Click to expand...
Click to collapse
Hello it's not a theoretical WIP.
Look here
Can you give more details please?
Regards,

oh... I guess insmod won't work on the modules without a compatible modem plugged in then?

many thanks! got it to work on my E1750
although you might want to put the instruction steps to remove the storage on the modem (only works after I did it):
Insert modem into pc and wait for driver to install
check in device manager which com port is assignated to your modem
download putty
here the.earth.li/~sgtatham/putty/latest/x86/putty.exe
close every program related to modem
run putty
click serial below port number and then change port number to one previously founded
click open
write atz and press enter, modem should answer ok
write ati and press enter, modem should give name, type, etc
write AT^U2DIAG=0 and press enter, zero cd is now disabled

dan-htc-touch said:
oh... I guess insmod won't work on the modules without a compatible modem plugged in then?
Click to expand...
Click to collapse
Probably. is you 3G Dongle in the "compatibility list".
If yes, you have to turn off the composite device of the 3G dongle.
Here how to do (thanks to Matchstick from Modaco):
Code:
You can test this by plugging the stick into a PC and seeing if it detects the modem as a CD or Memory stick device as well as a modem.
If it does then the method I used to turn off the composite device (on Windows 7) was:
1) Install the software and drivers for the modem under windows and make sure that the connection software sees the modem correctly.
2) Go to Settings/Control Panel/Device Manager and if you expand the Modems section you should see your USB modem listed there
3) Double click on the entry for the modem to get the properties panel up and selected the Modem tab
4) You should see a line at the very top of the tab that says something like Port: COM11 - This is the virtual serial port that the PC uses to talk to the modem which we're going to use to send the command to turn off all the stuff we don't want.
5) Next we want to install a serial console application. PuTTY is perfect for this. If you don't have a copy you can get if from here,
http://www.chiark.greenend.org.uk/~sgtatha...y/download.html
6) Run putty, select Serial under Connection Typem and enter the port we found in step 4 (eg COM11) into the box marked Serial Line and press the Open button
7) An empty window should pop up, which if things are working correctly is connected to the Modem
8) Type "ATI" into the window (without the quotes) and press return. The ATI command asks the modem for basic information and it should respond with something like
Manufacturer: huawei
Model: E1752
Revision: 11.126.03.01.314
IMEI: 123456789012345
+GCAP: +CGSM,+DS,+ES
OK
9) If you see this then you are connected correctly, if you don't see a response try physicaly unplugging and reconnecting the modem into a different USB port and start again from step 2 after windows has loaded the drivers for the modem.
10) Assuming everything is OK, the we can send the command to turn off the stuff we don't want. To do this simply type "AT^U2DIAG=0" (again without quotes) into the putty window. you should see the response OK.
11) If you do then the composite device features should now be turned off and you are ready to try the modem in your transformer.
Regards

brensim said:
many thanks! got it to work on my E1750
although you might want to put the instruction steps to remove the storage on the modem (only works after I did it):
Insert modem into pc and wait for driver to install
check in device manager which com port is assignated to your modem
download putty
here the.earth.li/~sgtatham/putty/latest/x86/putty.exe
close every program related to modem
run putty
click serial below port number and then change port number to one previously founded
click open
write atz and press enter, modem should answer ok
write ati and press enter, modem should give name, type, etc
write AT^U2DIAG=0 and press enter, zero cd is now disabled
Click to expand...
Click to collapse
What kind of OTG adapter are you using for this?

Hi all,
will this work with the Huawei E173u2 , the second version adapted for (pseudo)"4G" networks

I am with stock 3.1 + root.
Does it work or I need to install PRIME anyway?

At the moment, everyone who has got this to work has had to install Prime 1.5 (and several of us had to install the NVFlash specific version of Prime)

acid12 said:
Hi all,
will this work with the Huawei E173u2 , the second version adapted for (pseudo)"4G" networks
Click to expand...
Click to collapse
Is this similar to the huawei E367 ? As I'm looking at the E367 at the moment.
One easy(ish) way to check is to follow Steps 1-8 from post 12, then enter the command "AT^GETPORTMODE" (without the quotes)
If you get a response like
"^getportmode:type:WCDMA:Qualcomm,MDM:0,NDIS:1,DIAG:2,PCUI:3,CDROM:4"
then the E173u2 is using the new interface like the E367 and at the moment I can't get it to work.
It may be that the drivers aren't compatible (I'm not seeing ttyUSB0-ttyUSB2 devices appearing in /dev/) or it may just be that I haven't got the correct interfaces enabled.
There's information on the AT commands for the new-style Huawei modems here
http://www.dd-wrt.com/phpBB2/viewtopic.php?p=618504

Matchstick said:
At the moment, everyone who has got this to work has had to install Prime 1.5 (and several of us had to install the NVFlash specific version of Prime)
Click to expand...
Click to collapse
So i think that it is not only root needed but also something that in PRIME is present and that we can not add to stock rom.....
thanks

chrispazz said:
I am with stock 3.1 + root.
Does it work or I need to install PRIME anyway?
Click to expand...
Click to collapse
you can try by using Settings/Privacy then Reset to factory
Then restart and hen wizard ask you to choose for "3g and wifi" or "wifi only" choose 3g and wifi
Afterward you must see mobile network in settings.
tell us and don't forget to backup your data

Kasimodo said:
you can try by using Settings/Privacy then Reset to factory
Then restart and hen wizard ask you to choose for "3g and wifi" or "wifi only" choose 3g and wifi
Afterward you must see mobile network in settings.
tell us and don't forget to backup your data
Click to expand...
Click to collapse
Ok. I have to wait for my docking to come back from ASUS (RMA) and then I will try.
TY

[HELP] Issues when flashing a kernel

I dont know whether its due to a locked bootloader or what but when I try to flash a new kernel (Doomlord's 2.0GHz) I get the following appear on flashtool
Code:
07/024/2012 21:24:00 - INFO - FASTBOOT version info: [ version: 0.3 ]
07/024/2012 21:24:23 - INFO - Selected kernel (boot.img or kernel.sin): C:\Program Files (x86)\Android\android-sdk\platform-tools\boot.img
07/024/2012 21:24:23 - INFO - Flashing selected kernel
[B]07/024/2012 21:24:23 - INFO - FASTBOOT Output:
sending 'boot' (7900 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.002s
07/024/2012 21:24:23 - INFO - Please check the log before rebooting into system[/B]
07/024/2012 21:24:58 - INFO - Device will now exit fastboot mode and start booting into system
07/024/2012 21:24:59 - INFO - Device disconnected
07/025/2012 21:25:15 - INFO - Device connected with USB debugging off
07/025/2012 21:25:15 - INFO - For 2011 devices line, be sure you are not in MTP mode
07/025/2012 21:25:22 - INFO - Finished Fastboot Toolbox
07/025/2012 21:25:32 - INFO - Device connected with USB debugging on
07/025/2012 21:25:35 - INFO - Connected device : R800
07/025/2012 21:25:35 - INFO - Installed version of busybox : BusyBox v1.19.0 (2011-08-14 23:46:58 CDT) multi-call binary.
07/025/2012 21:25:35 - INFO - Android version : 2.3.4 / kernel version : 2.6.32.9-perf
07/025/2012 21:25:38 - INFO - [B]Root Access Allowed[/B]
any ideas on how to solve this. I know this is probably a VERY NOOBY thing to ask but I can flash everything, push files VIA adb, flash ROMS and what ever but kernels are being a PITA for this R800i

Bootloader is locked, you need to unlock.
Sent from my Darkforest Powered Xperia™ PLAY

just unlocked bootloaded but now my homebutton has stopped working any ideas?

Root U.K. Three Xperia Arc S 4.1.L.0.8

Perfect guide for rooting U.K. Three Xperia Arc LT18i 4.1.L.0.8 only...
Rooting your mobile may void the warranty and you are doing it at your own risk. Sony would be in no way responsible for any damage...
Go to settings > Security > Mark "Unknown sources"
Settings > Developer options > Mark USB debugging
Settings > Xperia > connectivity > USB connection mode > select MSC mode
================================================== ==================================================
You should have
Flashtool
http://androxyde.github.com/Flashtool/
------Download------
1 ) Arc S - Kernel
http://www.4shared.com/file/qNTvdPI6/Lt18i_41A0562_Kernel.html
2) Go to C:/ Drive > flashtool > firmwares > delete everything present and Put the kernel
3) Run Flashtool click on the flashing icon ( left side below "file" option)
Select flashmode > ok
Setup should be like this > select OK
Follow the steps connect your mobile and flash.
Flashtool may show error after flashing kernel, no worries. Even your build number, android version won't change. Everything would remain same. So please don't go to phone settings to check anything
4) After flashing restart your device, It may not start completely, may remain at Sony logo or blank/black.
Whatever the status is, just restart your device and proceed with the rooting--->
( Make sure you close flashtool before running the rooting toolkit )
Now connect your mobile to PC and Root Your Phone
If you face problem in downloading the toolkit then here it is
http://www.mediafire.com/?7dp5k73by10inbf
[ READ THE FOLLOWING CAREFULLY! ]
This script will:__________
1.root ur device using "andorid emulator" trick
2.install Busybox (1.18.4)
3.install SU files (ICS specific)
4.do some checks for free space, tmp directory (will remove Google Maps if required)
Before u begin:___________
1.make sure u have installed adb drivers for ur device
2.enable "USB DEBUGGING" - from (Menu\Settings\Developer Options\Development)
3.enable "UNKNOWN SOURCES" - from (Menu\Settings\Security)
4.[OPTIONAL] increase screen timeout to 10 minutes
5.connect USB cable to PHONE and then connect to PC
6.skip "PC Companion Software" prompt on device
[ WARNING ]
make sure that no other adb server is running in background (e.g.: Flashtool, PCC, SEUS) and disable any antivirus
[ How to install? ]
1.extract ALL the files in the zip
2.now just double click on "runme.bat"
3.sit back read the on screen instructions
4.the device will reboot a couple of times
5.when the script finishes it will say "ALL DONE"
5) Download 4.1.L.0.8 Kernel here....
http://www.4shared.com/zip/u6W3yREf/LT18i_41L08_Kernel.html
Credits goes to Androxyde, Bin4ry, Doomlord
and
Dhruv Shah for uploading 4.1.L.0.8 Kernel
Sent from my LT18i using xda premium

Device stuck on "Sony" screen FIX

There has been a lot of cases of this happening lately, so to save time here is the answer
So...
You have successfully soft-bricked your phone, and now are worried / wondering how to get out?
Easy
You will need a functioning computer with ADB drivers installed (flashtool has a driver installer you can use), and an internet connection
~~On Computer~~
First things first, you will need to Download FLASHTOOL - and you will also need to download the FIRMWARE for your phone (they are all the same - D5833/D5803)
Now upon opening flashtool it will say you need to move files from *flashtool/folder* to *.flashtool/folder* -- move the files and also move the .ftf (firmware file) to this new folder
Once completed that click the lightning bolt in flashtool and click the firmware you downloaded and click flash
~~On Device~~
Hold POWER + VOLUME buttons down until the device vibrates 3 times (It is now turned off)
While turned off hold the VOLUME DOWN button while plugging phone into the computer (should see the LED turn red - green/blue then off)
Flashtool will now say device is connected in flashmode and will flash the firmware
DONE
note for windows 8 + users
adb drivers do not always work with win8 and above, please follow these steps to get adb to work
arsradu said:
Or, you can do this:
run cmd.exe as Administrator (right click -> Run as administrator)
type this command:
Code:
bcdedit /set testsigning on
reboot
install drivers. Agree to installing unsigned drivers when you see the pop-up. Drivers should be correctly installed now.
run cmd.exe as Administrator (right click -> Run as administrator)
type this command:
Code:
bcdedit /set testsigning off
reboot
That's all.
Click to expand...
Click to collapse

I learnt pretty early to have a backup file, saved in multiple locations with all the tools needed to recover from the soft brick. Shat myself first time it happened, phone was only a few weeks old.

mrrflagg said:
I learnt pretty early to have a backup file, saved in multiple locations with all the tools needed to recover from the soft brick. Shat myself first time it happened, phone was only a few weeks old.
Click to expand...
Click to collapse
haha same
Only put this tutorial up because some people might not have flashtool / know how to use it
or do not know how to get the firmware files

nzzane said:
haha same
Only put this tutorial up because some people might not have flashtool / know how to use it
or do not know how to get the firmware files
Click to expand...
Click to collapse
Thank you!
For Windows, maybe it would be nice to mention that it's not gonna work (by default) in Windows 8, 8.1 and 10, so Windows 7 is recommended for this.
There is, however, a way (actually, there are 2, but I found one of them to be easier than the other) to get those drivers installed on Windows 8 and above.
You can find it here.

nzzane said:
There has been a lot of cases of this happening lately, so to save time here is the answer
So...
You have successfully soft-bricked your phone, and now are worried / wondering how to get out?
Easy
You will need a function computer with ADB drivers installed (flashtool has a driver installer you can use) and an internet connection
~~On Computer~~
First things first, you will need to Download FLASHTOOL - and you will also need to download the FIRMWARE for your phone (they are all the same - D5833/D5803)
Now upon opening flashtool it will say you need to move files from *flashtool/folder* to *.flashtool/folder* -- move the files and also move the .ftf (firmware file) to this new folder
Once completed that click the lightning bolt in flashtool and click the firmware you downloaded and click flash
~~On Device~~
Hold POWER + VOLUME buttons down until the device vibrates 3 times (It is now turned off)
While turned off hold the VOLUME DOWN button while plugging phone into the computer (should see the LED turn red - green/blue then off)
Flashtool will now say device is connected in flashmode and will flash the firmware
DONE
note for windows 8 + users
adb drivers do not always work with win8 and above, please follow these steps to get adb to work
Click to expand...
Click to collapse
Thank you thank you thank you!!! I almost cried
Stupid me... After installing locked dual recorver, i wiped the system and switched the phone off... It game me a warning sign saying there was no OS, and I said yup, no worries (thought it was like PCs where boot OS has nothing to do with Android).
Phone got stuck on the Sony logo and the only way to do anything was to use the hard reset button!! YOU SAVED ME!

Bump
Many people still get themselves stuck in this issue :3

yep stuck on Sony screen
here what flash tool says;
12/048/2017 21:48:23 - INFO - Selected Bundle for Sony Xperia Z3 Compact(D5803). FW release : 23.0.A.2.93. Customization : Customized CE1
12/048/2017 21:48:23 - INFO - Preparing files for flashing
12/048/2017 21:48:24 - INFO - Please connect your device into flashmode.
12/048/2017 21:48:32 - INFO - Device connected in flash mode
12/048/2017 21:48:32 - INFO - Opening device for R/W
12/048/2017 21:48:32 - INFO - Reading device information
12/048/2017 21:48:32 - INFO - Phone ready for flashmode operations.
12/048/2017 21:48:32 - INFO - Opening TA partition 2
12/048/2017 21:48:32 - INFO - Current device : D5803 - YT9115XKA6 - 1288-7915_R2D - 1285-6521_23.5.A.1.291 - GLOBAL-LTE_23.5.A.1.291
12/048/2017 21:48:32 - INFO - Closing TA partition
12/048/2017 21:48:32 - INFO - Start Flashing
12/048/2017 21:48:32 - INFO - Ending flash session
12/048/2017 21:48:32 - ERROR - Can't read a byte value
12/048/2017 21:48:32 - ERROR - Error flashing. Aborted

I was able to successfully apply erased firmware by following your instructions.....Thanks a ton

Fire HD10 (2019) bricked itself

Hi,
A few days ago, my Fire HD10(2019) refused to power on, or rather it would show some life (amazon screen IIRC), but go no further. Now it doesn't even do that.
On a PC I can see whats its doing across USB. "Bus 002 Device 083: ID 0e8d:0003 MediaTek Inc. MT6227 phone" on usb for about 45 seconds, then it disconnects for maybe 20s, and then repeats. Now I take the 0e8d:0003 device to be the amazon bootloader - so looks to me like the bootloder works, but crashes hard and restarts as soon as it tries to start android. So looks like the box is bricked.
I've tried the various buttons to go into fastboot - no success. Neither "adb devices" nor "fastboot devices" can see the device. On first booting, the machine brings up a serial interface (USB ACM device), alas I've not been able to connect to this.
So what are my options of getting into the machine? If I can't access the bootloader via the serial interface, are there UART pins on the board? If so where? If I can access the bootloader, can I switch to fastboot mode, so I can reflash the android OS? Where is the best place to look for info like this?

davidsummers said:
Hi,
A few days ago, my Fire HD10(2019) refused to power on, or rather it would show some life (amazon screen IIRC), but go no further. Now it doesn't even do that.
On a PC I can see whats its doing across USB. "Bus 002 Device 083: ID 0e8d:0003 MediaTek Inc. MT6227 phone" on usb for about 45 seconds, then it disconnects for maybe 20s, and then repeats. Now I take the 0e8d:0003 device to be the amazon bootloader - so looks to me like the bootloder works, but crashes hard and restarts as soon as it tries to start android. So looks like the box is bricked.
I've tried the various buttons to go into fastboot - no success. Neither "adb devices" nor "fastboot devices" can see the device. On first booting, the machine brings up a serial interface (USB ACM device), alas I've not been able to connect to this.
So what are my options of getting into the machine? If I can't access the bootloader via the serial interface, are there UART pins on the board? If so where? If I can access the bootloader, can I switch to fastboot mode, so I can reflash the android OS? Where is the best place to look for info like this?
Click to expand...
Click to collapse
It is actually the mediatek bootrom (your device can have mtk-su temp root access, if you downgrade). You must have one of the early release ones that have access to it. My guess there is something wrong with the preloader... While i can't pin it down, the information to reload is all in this thread...
New Fire HD10 2019 Bootless Root Method + Bootloader Unlock Brainstorming
There's a new Fire 10 coming out, with an Octacore processor, USB-C charging, and FireOS based on Pie: https://arstechnica.com/gadgets/2019/10/amazons-new-fire-hd-10-tablet-costs-149-and-charges-via-usb-c/ I most certainly don't need any more...
forum.xda-developers.com

Yes it was an early device. Alas it connected to the web, and updated itself from 7.3.1.0 before I disabled most of the amazon processes. So the original mtk-su for 7.3.1.0 never worked on my machine. Alas can't use this any more - as can't get into android any more.
I'm up to page 30 of the thread you posted, alas nothing read so far has managed to get into the machine.

And first progress - bypass_utility version 1.4.2. can connect (when run as root) and gives:
[2023-01-22 14:32:12.028038] Waiting for device
[2023-01-22 14:32:39.691833] Found port = /dev/ttyACM0
[2023-01-22 14:32:40.083041] Device hw code: 0x788
[2023-01-22 14:32:40.083391] Device hw sub code: 0x8a00
[2023-01-22 14:32:40.083586] Device hw version: 0xca00
[2023-01-22 14:32:40.083770] Device sw version: 0x0
[2023-01-22 14:32:40.083959] Device secure boot: True
[2023-01-22 14:32:40.084143] Device serial link authorization: False
[2023-01-22 14:32:40.087904] Device download agent authorization: True
[2023-01-22 14:32:40.088223] Disabling watchdog timer
[2023-01-22 14:32:40.092031] Disabling protection
[Errno 5] Input/Output Error
[2023-01-22 14:32:41.464834] Payload did not reply

davidsummers said:
And first progress - bypass_utility version 1.4.2. can connect (when run as root) and gives:
[2023-01-22 14:32:12.028038] Waiting for device
[2023-01-22 14:32:39.691833] Found port = /dev/ttyACM0
[2023-01-22 14:32:40.083041] Device hw code: 0x788
[2023-01-22 14:32:40.083391] Device hw sub code: 0x8a00
[2023-01-22 14:32:40.083586] Device hw version: 0xca00
[2023-01-22 14:32:40.083770] Device sw version: 0x0
[2023-01-22 14:32:40.083959] Device secure boot: True
[2023-01-22 14:32:40.084143] Device serial link authorization: False
[2023-01-22 14:32:40.087904] Device download agent authorization: True
[2023-01-22 14:32:40.088223] Disabling watchdog timer
[2023-01-22 14:32:40.092031] Disabling protection
[Errno 5] Input/Output Error
[2023-01-22 14:32:41.464834] Payload did not reply
Click to expand...
Click to collapse
It has been a long time. Maybe try disconnecting the battery, not sure if it is staying in bootrom mode.... I remember mine had to have the battery removed or it would try to goto the preloader (i think). I used the process to downgrade back to 7.3.1.0, but it was like a year ago.

Michajin said:
It has been a long time. Maybe try disconnecting the battery, not sure if it is staying in bootrom mode.... I remember mine had to have the battery removed or it would try to goto the preloader (i think). I used the process to downgrade back to 7.3.1.0, but it was like a year ago.
Click to expand...
Click to collapse
Yes - mine stayed in 0e8d:0003 mode, when the device bricked itself - made no difference with battery on or off, always when through the same minute cycle, where the device would disconnect, then reboot.
Interesting after running the bypass utility - it has stayed up in the 0e8d:0003 mode - and hasn't rebooted.

davidsummers said:
Yes - mine stayed in 0e8d:0003 mode, when the device bricked itself - made no difference with battery on or off, always when through the same minute cycle, where the device would disconnect, then reboot.
Interesting after running the bypass utility - it has stayed up in the 0e8d:0003 mode - and hasn't rebooted.
Click to expand...
Click to collapse
it disabled the watchdog timer. From what is can see everything points to a potential wrong setup..
bypass_utility/README.md at master · MTK-bypass/bypass_utility
Contribute to MTK-bypass/bypass_utility development by creating an account on GitHub.
github.com

This post shows the same error as you read through it.
Payload did not reply · Issue #13 · MTK-bypass/exploits_collection
[Errno 5] Input/Output Error Payload did not reply
github.com

OK - using SP_Flash_Tool v5.2008 to attempt to flash maverick-downgrade-7.0_PR7310_940N and I get the error:
Connect BROM failed: STATUS_SEC_AUTH_FILE_NEEDED(-1073545198)
Disconnect!
BROM Exception! ( ERROR : STATUS_SEC_AUTH_FILE_NEEDED (-1073545198) , MSP ERROE CODE : 0x00.
[HINT]:
Please select a valid authentication file or ask for help.)((ConnectBROM,../../../flashtool/Conn/Connection.cpp,105))
So where do I get the authentication file from?

Michajin said:
it disabled the watchdog timer. From what is can see everything points to a potential wrong setup..
bypass_utility/README.md at master · MTK-bypass/bypass_utility
Contribute to MTK-bypass/bypass_utility development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
ah yes - that explains why it was rebooting. So guess I have to dig into [Errno 5] Input/Output Error.
Seems like only way I have into the tablet any more is the mediatek bootrom, but as the tablet is sick - if that doesn't work, then probably its permanently dead. E.g. even getting access to a uart wouldn't help.

You have to only do file by file.
5. bypass_utility run succes with message "Protection disabled"
6. Run SPFlash Tool and flash boot, recovery, vendor, system. Wait to finish
7. Hold power button 15s to power off (check Ports in Device Manager windows)
8. Hold volume up and power boot to recovery with triactangle icon
9. Hold power and tap volume up then choose reset factory
10. Reboot

Thanks Michajin - I'm obviously having problems with the bypass_utility, whilst it connects to the MediaTek bootrom, it is not able to disable protection - and test mode bombs out. I've taken this up on the bypass_utility thread:
xda bypass utility