Database Develop

[Q] Broken HTC First - Any way to fix it?

Hello,
right next to me I have an HTC First which seems broken. It's my father's phone, and he is terrible at really telling what happened, so I will spare you the details, except that he was - the last time the device actually worked - maybe downloading some navigation app from a website (http://www.viamichelin.de/).
The First doesn't turn on any more, when you connect a charging or a usb cable, all that happens is that the home + the menu button shortly light up. The screen is most likely not cracked, it seems all in all perfectly fine.
Linux tells me the following about the HTC First as an USB device:
Code:
$ lsusb
Bus 004 Device 009: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
$ dmesg
[ 4099.008909] usb 4-1.4: new high-speed USB device number 7 using ehci-pci
[ 4099.094091] qcserial 4-1.4:1.0: Qualcomm USB modem converter detected
[ 4099.094249] usb 4-1.4: Qualcomm USB modem converter now attached to ttyUSB0
[ 4372.398567] usb 4-1.4: USB disconnect, device number 7
[ 4372.398780] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
[ 4372.398804] qcserial 4-1.4:1.0: device disconnected
[ 4375.398363] usb 4-1.4: new high-speed USB device number 8 using ehci-pci
[ 4375.521723] hid-generic 0003:05C6:F006.0009: hiddev0,hidraw6: USB HID v1.11 Device [HID 05c6:f006] on usb-0000:00:1d.0-1.4/input0
[ 4379.820165] usb 4-1.4: USB disconnect, device number 8
[ 4380.006727] usb 4-1.4: new high-speed USB device number 9 using ehci-pci
[ 4380.091837] qcserial 4-1.4:1.0: Qualcomm USB modem converter detected
[ 4380.091977] usb 4-1.4: Qualcomm USB modem converter now attached to ttyUSB0
So what do you think? Any suggestions on how I could probably fix this device?
Thank you very much in advance,
Peter

maybe try to flash it back to stock rom via RUU

hlp me friends
same problem ...please tell me how to flash my htc first....plz hlep me

restoring to stock
first of all you must know that this will wipe everything from your phone,so make a backup of personal data... you will need to download the RUU package which has the original stock firmware from this link:
http://www.androidruu.com/?developer=Myst
download this one because this can be s-off: RUU_MYST_UL_Cingular_US_1.08.502.1_Radio_1.15.40.0 0.13_2_10.64.40.33AL_release_316579_signed_2.exe
do you have installed the drivers and is your bootloader unlocked from htc dev?
of course it must be unlocked
1-reboot into bootloader
2-open cmd and type: fastboot oem lock
this will relock your bootloader so you can proceed to install the RUU (if you dont know fastboot comands ask me to send you the files and give you further instructions)
3-now its time to grab the rom.zip from RUU. run the file which you downloaded and i will tell you 2 ways to get the rom.zip
*the first one is to find it to temporary files,pres the windows key + R and type %temp% and there are to many folders,but in one of them you will find it
*the second one is from task manager,open RUU.exe and open taske manager (ctrl+shift+esc),go to applications,right click on ruu ,click on go to process,it will direct you to sth highlighted and again right click on it,click on open file location and here you are at the folder where is located rom.zip . copy it at the folder where you have fastboot.exe and close the RUU application
4-now is time to install the rom.zip,type in cmd:
fastboot oem rebootRUU
(the screen must show htc logo and a dark background)
5- the final step is flashing zip,type again in cmd:
fastboot flash zip rom.zip
(the cmd will show some automated scripts and after a couple of minutes your phone will be completly reverted to stock)
6-if you want to s-off and install a custom rom,first head up to htcdev.com to unlock your bootloader,download moonshine s-off for htc first and it will s-off your htc and root it,install a custom recovery and choose your favorite rom)
Sorry for my bad english,but im trying to do my best !
For any problem contact me !
If i helped you,press the thanks button

wifi problem
Dear,
I have htc first & im face wifi problem after connecting data connecting from sim.
Please resolved if possible.
Thanx & regrds
Kamran siddiqui

OxygenOS install bricked my phone (and there are no Windows machines around)

I think I've managed to successfully brick my phone through the following process...
1. boot into recovery
2. enable sideload mode
3. adb sideload the OxygenOS beta 9 image (downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_openbeta_9/)
Everything went smoothly and the sideload process finished successfully. Rebooted the phone, wandered away for a bit...and now it's just a black screen that won't turn on. Plugging it into my laptop I see that is identifying itself as a QUSB__BULK device:
Code:
usb 1-1.4.4: new high-speed USB device number 18 using xhci_hcd
usb 1-1.4.4: New USB device found, idVendor=05c6, idProduct=9008
usb 1-1.4.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-1.4.4: Product: QUSB__BULK
usb 1-1.4.4: Manufacturer: Qualcomm CDMA Technologies MSM
qcserial 1-1.4.4:1.0: Qualcomm USB modem converter detected
usb 1-1.4.4: Qualcomm USB modem converter now attached to ttyUSB0
What are my options at this point? All of the recovery guides I've been able to find so far start by downloading some Windows utilities, and I don't have easy access to a Windows machine.

Use the Hard Brick guide, download the full tool unbrick guide and it should work fine, follow method 2. you can find hard unbrick guide on google.

Unfortunately, the hard unbrick guide (if you mean forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/) seems to be Windows-only (it has instructions for downloading lots of Windows device drivers, etc), and as I said in my original question, I don't have a Windows machine handy.

So I have not looked alot around but I haven't seen any guides or something for Linux, but 2 ideas:
1: try that guide, maybe Linux won't need the drivers and it would work just fine.
2: you can download a windows image, install it on a Virtual Machine,unbrick your phone and then delete the VM and everything.

Is your phone's bootloader unlocked? If yes, things will much more simple.
anyway, try download full 3.2.8 ROM from OP site, boot your phone to fastboot mode and sideload it.

Is it possible to reflash a zune through nvidia's apx protocal?

Good Evening ,
I've got a zune that through it's "wonderful" update feature, decided to freeze and leave the flash chip blankish...
Occasionally when I plug in the zune I get what I believe is the nvidia chip, putting itself into apx mode.
dmesg:
usb 3-4.2: new high-speed USB device number 9 using xhci_hcd
usb 3-4.2: New USB device found, idVendor=0955, idProduct=7416
usb 3-4.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 3-4.2: Product: APX
usb 3-4.2: Manufacturer: NVIDIA Corp.
Click to expand...
Click to collapse
From my understanding, nvflash is what people use to flash the firmware using the apx protocol but I can't seem to get it to recognize the zune.
When it runs, I get:
Nvflash v1.8.90246 started
rcm version 0X4
UnKnown device found
Click to expand...
Click to collapse
or
Nvflash v1.8.90246 started
rcm version 0X4
Device not found
Click to expand...
Click to collapse
I assume thats because the zune uses a Nvidia Tegra APX 2600 chip (pre tegra one chip).
Has anyone gotten nvflash to work with older nvidia chips or reversed the apx protocol?
I was able to find a site where someone reversed part of it but due to site rules I can't post the link.

Bricked Redmi 4a

Hi folks, lately I wanted to root my phone to disable annoying storage shortage popups, and chose path of TWRP (twrp-3.2.2-0-rolex) + SuperSU (SR5-SuperSU-v2.82-SR5-20171001224502)
But after I flashed recovery partition with fastboot I wasn't able to boot my device, was continuously seeing MI logo.
By the way after I flashed recovery partition I checked boxes to install TWRP app.
I was following instructions in this thread: https://forum.xda-developers.com/redmi-4a/how-to/root-redmi-4a-t3726735
But as a result I wasn't able to boot my device, after some more lookup in one of forums I read that problem could be solved by replacing aboot system file with file provided by author.
Problem is that that file was prepared for Redmi 3S, while mine is 4A.
As a result I have totally bricked phone, which doesn't want to boot, even display is not turning on.
After leaving phone for few days, i started to see that hope as red LED light on home button was blinking when holding power button.
Now in my Linux machine I see these logs:
usb 1-2: new high-speed USB device number 9 using xhci_hcd
usb 1-2: New USB device found, idVendor=05c6, idProduct=900e
usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-2: Product: QHSUSB__BULK
usb 1-2: Manufacturer: Qualcomm CDMA Technologies MSM
Anyone have idea how I can get access to internal storage again?
I want to replace that aboot file with original one, and continue solving ROOTing issue.
Thanks in advance!

clumsywalker said:
Hi folks, lately I wanted to root my phone to disable annoying storage shortage popups, and chose path of TWRP (twrp-3.2.2-0-rolex) + SuperSU (SR5-SuperSU-v2.82-SR5-20171001224502)
But after I flashed recovery partition with fastboot I wasn't able to boot my device, was continuously seeing MI logo.
By the way after I flashed recovery partition I checked boxes to install TWRP app.
I was following instructions in this thread: https://forum.xda-developers.com/redmi-4a/how-to/root-redmi-4a-t3726735
But as a result I wasn't able to boot my device, after some more lookup in one of forums I read that problem could be solved by replacing aboot system file with file provided by author.
Problem is that that file was prepared for Redmi 3S, while mine is 4A.
As a result I have totally bricked phone, which doesn't want to boot, even display is not turning on.
After leaving phone for few days, i started to see that hope as red LED light on home button was blinking when holding power button.
Now in my Linux machine I see these logs:
usb 1-2: new high-speed USB device number 9 using xhci_hcd
usb 1-2: New USB device found, idVendor=05c6, idProduct=900e
usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-2: Product: QHSUSB__BULK
usb 1-2: Manufacturer: Qualcomm CDMA Technologies MSM
Anyone have idea how I can get access to internal storage again?
I want to replace that aboot file with original one, and continue solving ROOTing issue.
Thanks in advance!
Click to expand...
Click to collapse
Your better choice must be flash with fastboot method. You did some mistakes its better do a clean flash. If you have some sensors or wifi issues after that you must do a edl mode flash.
Your problem was you don't flashed lazyflasher to remove the crypto of the data partition

manucarcor said:
Your better choice must be flash with fastboot method. You did some mistakes its better do a clean flash. If you have some sensors or wifi issues after that you must do a edl mode flash.
Your problem was you don't flashed lazyflasher to remove the crypto of the data partition
Click to expand...
Click to collapse
Try with test point. I do before when i put miui 10 for mi 6.

Did you fix it?
If not then short the test point . In your device manager on the PC you make sure that there is Qualcomm hs-usb qdloader 9008 port and use a old version of Mi Flash tool 2015 because latest version of Mi Flash tool can't detect it after that download the Global ROM flash it via MI Flash tool and get the magic done make sure you select flash all .....

Complete Wipe system , dalvik and cache , also vendor , data too and Install ROM as new ...

Hardbricked when trying to install Linegae OS

Hi,
i think I hardbricked my Moto Z3 Play XT1929-8 when I tried to install Linegae OS 17.1 like described here https://forum.xda-developers.com/z3-play/development/lineage-os-moto-z3-play-t3873684 .
I successfully installed TWRP and tried to install the lineage zip from the thread with TWRP. The installation of Linegae locked successful for me. At the end of the Installation I got a message to reboot into the target System A or B where I selected B. This did not reboot instead there have been some mounting errors for 3 Partitions(I can't remember which one it was). After this TWRP asked me to reboot again. The result of this was the Hardbrick!!!
Now the device dosn't do anything when pushing the buttons. Especialy I don't get it into fastboot mode. When I connect via USB debian can't detect any device. dmesg repeats the following:
Code:
[952576.001408] usb 1-2: new high-speed USB device number 89 using xhci_hcd
[952576.129436] usb 1-2: device descriptor read/64, error -71
[952576.365420] usb 1-2: device descriptor read/64, error -71
[952576.601343] usb 1-2: new high-speed USB device number 90 using xhci_hcd
[952576.729392] usb 1-2: device descriptor read/64, error -71
[952576.965364] usb 1-2: device descriptor read/64, error -71
[952577.073403] usb usb1-port2: attempt power cycle
[952577.725243] usb 1-2: new high-speed USB device number 91 using xhci_hcd
[952577.725364] usb 1-2: Device not responding to setup address.
[952577.933337] usb 1-2: Device not responding to setup address.
[952578.141211] usb 1-2: device not accepting address 91, error -71
[952578.269197] usb 1-2: new high-speed USB device number 92 using xhci_hcd
[952578.269312] usb 1-2: Device not responding to setup address.
[952578.477351] usb 1-2: Device not responding to setup address.
[952578.685209] usb 1-2: device not accepting address 92, error -71
[952578.685294] usb usb1-port2: unable to enumerate USB device
Before I bricked my Device I got some version information via adb which might be helpful
Code:
[ro.build.version.all_codenames]: [REL]
[ro.build.version.ci]: [27]
[ro.build.version.codename]: [REL]
[ro.build.version.full]: [Blur_Version.28.11.27.beckham.retail.en.US]
[ro.build.version.incremental]: [5c49]
[ro.build.version.preview_sdk]: [0]
[ro.build.version.qcom]: [LA.UM.6.2.r1-07200-sdm660.0]
[ro.build.version.release]: [8.1.0]
[ro.build.version.sdk]: [27]
[ro.build.version.security_patch]: [2018-04-01]
[ro.vendor.build.date]: [Sat May 5 08:17:33 CDT 2018]
[ro.vendor.build.date.utc]: [1525526253]
[ro.vendor.build.fingerprint]: [motorola/beckham/beckham:8.1.0/OPW28.70-25/5c49:user/release-keys]
[ro.vendor.build.thumbprint]: [8.1.0/OPW28.70-25/5c49:user/release-keys]
I can't understand why it hard bricked TWRP was successfully installed and if anything was wrong with the Linegae OS Installation it should boot into fastboot mode or TWRP? But the real big question is how to unbrick it? Am I right when I say the device is realy dead on any USB connection so I have to get deeper into the hardware to understand whats wrong? Could anyone help me doing this?
Best regards
Zeilentrafo

Got it to Qualcomm 9008 Mode
Ok so i played around a bit with volume down and power on and the USB problem in dmesg disappeared. Debian was now able to detect the Qualcom Chipset in 9008 Mode what is quite nice. I installed the qdl tool to flash it back to stock ROM. I although tried to talk with sahara to the Phone which worked. But I'm not sure where to get the right mbn file to flash the stock ROM? I googled around but I didn't find any site which was serious. From the unserious sites I've got a good locking firmware.
I'm not quite sure what is possible with the qdl tool and which files from the firmware have to be given? Can anyone explain this to me?
Best regards
Zeilentrafo

So you hard bricked your Beckham, and for what I read, you're using linux and now the phone is detected as Qualcomm 9008, right?
If you still unable to access the fastboot mode, I recommend you check https://forum.xda-developers.com/z3-play/how-to/how-to-restore-bricked-z3-play-t3986061.
It work for me on Ubuntu, tge Windows Qualcomm driver are really glitchy.
Once you are able to access the fastboot mode I recommend you flash this firmware first https://forum.xda-developers.com/z3-play/help/base-band-lost-brick-t3951484 (firmware in post 4).
That firmware helped me recover base band, Imei.
After that you should be good to flash whatever.
Also when usin TWRP to install Lineage, check to what slot the Lineage is being installed, normally is on the opposite slot (for A/B devices).
So when you hit the reboot on TWRP it will give you the options again to reboot system, reboot recovery or reboot slot A or slot B.
Select the one where it got flash and I then select reboot again.
You can make sure of where it got install on the aame flashing process details on TWRP