i'm trying to uptade the phone by mobile upgrade but it's still says that is no greater upgrade. i go to TWRP and wipe system , then i use the mobile upgrade and it says the same . i unplug phone from pc and then phone take bootloop
sorry for english
I bricked my idol 3 4.7 too.
I restore stock rom with twrp and the phone stuck in bootloop.
No download mod, no recovery, adb/fastboot dont see the phone.
My pc recognize the phone as QHSUSB_BULK.
After I was looking for drivers, this QHSUSB_BULK change to ALCATEL HS-USB Diagnostics 9006.
I tried repair with Mobile Upgrade Q 4.9.2 but the process stucked at "Scanning you mobile phone"
Sorry for bad English.
Thank you in advance for your help.
And when you plug it, it doesn't even show the "Alcatel Onetouch" screen?
Sent from my GT-I9000 using XDA Free mobile app
Yes, screen doesn't show anything. When i hold power button, i think the phone may restart because the driver disappear and come back on my pc.
Try holding down arrow (or up arrow) while turning the phone on....one arrow put the phone in recovery mode...the other puts the phone in download mode....in download mode you should be able to use alcatel's software...in recovery mode (assuming you installed TWRP) you should be able to restore a backup.
i make mistake: update boot from 6045 on my 6039h and now see only logo alcatel. mobile upgrade q cant connect to my device, fastboot commands not working. just can enter to recovery mode (only wipe data/factory reset and wipe cache).
i revived my idol 3 (6039h) with backup maked from twrp one day ago
1. install mobile upgrade q 4.9.2 for drivers
2. download 6039Y_TWRP_with_gdisk and unpack
3. install QPST 2.7.422
4. turn off phone and connect to pc, wait when battery icon disappear
5. now press and hold: volume up down and power button - that sequence. release power button but still hold volume up and down. you must see that (i know it is hard to get that):
press long power up button - screen should be clean black
now you can see in windows manager device new port:
6. run qfil.exe from qpst.
select port Android HS-USB QDLoader 9008
programmer path: from 6039Y_TWRP_with_gdisk > prog_emmc_firehose_8916.mbn
search path: select 6039Y_TWRP_with_gdisk
load xml: rawprogram0.xml and patch0.xml
look screen for details
7. restart phone and you should see twrp mode
8. now you can restore your backup
mobile upgrade q 4.9.2
after this you should install twrp from this post
because only this can install modified ota updateCode:
Start Download Program Path:C:\Program Files (x86)\Qualcomm\QPST\bin\6039Y_TWRP_with_gdisk\prog_emmc_firehose_8916.mbn COM Port number:5 Sahara Connecting ... Sahara Version:2 Start Sending Programmer Sending Programmer Finished Switch To FireHose Max Payload Size to Target:49152 Bytes Device Type:eMMC Platform:8x26 Disable Ack Raw Data Every N Packets Ack Raw Data:False Skip Write:False Always Validate:False Use Verbose:False COM Port number:5 Sending NOP NOP: Fail Code: 9 Unable to send FireHose NOP, Device is not in Firehose mode ! Download Fail:System.Exception: Failed to send Firehose NOP to the phone. at QC.QMSLPhone.Phone.QPHONEMS_FireHoseNOP() at QC.SwDownloadDLL.SwDownload.FireHoseDownloadImage(Boolean bResetPhone, List`1 rawprogramFilesList, List`1 patchFilesList, Single& fImageSizeInMB, Single& fThroughput) Download Fail:FireHose Fail FireHose Fail Finish Download
Ok thanks for the input and advice. As a last ditch effort, is there a way to create or modify the twrp file as a "signed" zip file so that I could boot into it via stock recovery. This was how I rooted my old Galaxy S2, although it was a CWM recovery.
Can you post a screenshot where the option is? I'm not doubting your word but perhaps he's looking in the wrong place? I'm back on TWRP so can't look in the stock recovery myself.
reboot system now apply update from ADB apply update from sdcard apply update from phone storage wipe data/factory reset wipe cache partition reboot to bootloader power down view recovery log
This is a snapshot from the recovery menu of 6039y.If it's right off the main page like that then I can confirm it's not on the 6045. It's been one of the main issues with folks bricking their devices...if their rom gets messed up and they have factory recovery they have no way to get into bootloader to do anything to repair the device. Seems alcatel needs to add the reboot to bootloader to our recovery. I wonder where we could report that.
Is there a way to "lock" recovery so the updates cannot replace twrp? TWRP allows adb access and reboot to bootloader.
if ! applypatch -c EMMC:/dev/block/bootdevice/by-name/recovery:18393344:f9062580503eb61b315a5d12c5c6b3bb133aa4b2; then ....etc.