Related
Is this real ? i really cant access boot loader , just the recovery with the no command screen
can you confirm ??
if so then what i think that this device is already dead
It has a fasboot mode, for now I can only access it via adb (adb reboot bootloader). It shows a black screen with fastboot mode at the bottom.
It also has a stock recovery mode, shows 'no command' but can be activated by pressing power button.
After you've activated it:
Vol+ to select
Vol- navigate down
Power to go back
Adb No devices found , idk why my Laptop doesn't detect my desire 820s
wil try now just installed htc sync manager
okay it worked and i went to fastboot mode , when i give a cmd order it says waiting for device
eg..... fastboot oem info
Same here
fastboot oem unlock
FAILED (remote: unknown command)
fastboot oem get_identifier_token
FAILED (remote: unknown command)
any idea ?
Nc.netcat said:
Same here
fastboot oem unlock
FAILED (remote: unknown command)
fastboot oem get_identifier_token
FAILED (remote: unknown command)
any idea ?
Click to expand...
Click to collapse
Mediatek Htc devices do not need bootloader unlocking, you can flash anything from fastboot mode
---------- Post added at 04:16 PM ---------- Previous post was at 04:10 PM ----------
Mohamed Yaser said:
Is this real ? i really cant access boot loader , just the recovery with the no command screen
can you confirm ??
if so then what i think that this device is already dead
Click to expand...
Click to collapse
You are right, Mediatek HTC devices dont have bootloader. Infact mediatek htc phones can be flashed with SP Flash tool just like micromax phones. I know this is true for htc 816g.
sziraqui said:
Mediatek Htc devices do not need bootloader unlocking, you can flash anything from fastboot mode
.
Click to expand...
Click to collapse
hhmm
fastboot flash recovery recovery.img => partition 'recovery' not support flash
but flashing recovery with SP flash tool will work for sure.
1. Put your custom recovery in the firmware folder,
2. del stock recovery.img,
3. rename your custom recovery as recovery.img,
4. load scatter file,
5. uncheck everything except recovery
6. click download and then connect your powered off phone to pc while holding vol down
someone Please confirm if this works with 820s, without worrying about bootloader
sziraqui said:
but flashing recovery with SP flash tool will work for sure.
1. Put your custom recovery in the firmware folder,
2. del stock recovery.img,
3. rename your custom recovery as recovery.img,
4. load scatter file,
5. uncheck everything except recovery
6. click download and then connect your powered off phone to pc while holding vol down
someone Please confirm if this works with 820s, without worrying about bootloader
Click to expand...
Click to collapse
It works. How about flashing a RUU?
Gibz97 said:
It works. How about flashing a RUU?
Click to expand...
Click to collapse
Can mention on which device you have checked it, does it has locked bootloder (if exists)?
RUU in mediatek? i dont think mediatek phones have RUU, (try "fastboot oem rebootRUU" to check)
But if it does, you can extract rom.zip from the RUU THEN EXTRACT system.img, boot.img and recovery.img
Then keep copy this to your firmware folder (containg scatter file)
load scatter file
Uncheck everything except system,boot and recovery in sp flash tool
Click download and connect your powered off device to pc holding vol down
sziraqui said:
Can mention on which device you have checked it, does it has locked bootloder (if exists)?
RUU in mediatek? i dont think mediatek phones have RUU, (try "fastboot oem rebootRUU" to check)
But if it does, you can extract rom.zip from the RUU THEN EXTRACT system.img, boot.img and recovery.img
Then keep copy this to your firmware folder (containg scatter file)
load scatter file
Uncheck everything except system,boot and recovery in sp flash tool
Click download and connect your powered off device to pc holding vol down
Click to expand...
Click to collapse
I've done that but the phone usually cannot boot into the system.
BTW I am on Kitkat 4.4.4 without Sense and I want to flash Lollipop 5.0.2 Sense 7.
The RUU is from a Taiwanese variant 820ys which runs Lollipop 5.0.2 and Sense 7 out of the box, same models(htc_a50ml_dtul)
The problem is that the Kitkat Firmware has smaller partitions compared to the lollipop one. An example is the Kitkat system partition which is about 1.4Gbs while Lollipop has about 4.9Gbs, so I cannot flash with the same scatter file.
So I edit the scatter file to inflate the partitions in order to accommodate the big Lollipop files (sytem.img,recovery.img and boot.img) and perform firmware upgrade.
What could be stopping it from booting? Is it due the fact that the Lollipop boot and recovery are verified? Thanks in advance
Screenshots for Kitkat and Lollipop firmware files below
Gibz97 said:
I've done that but the phone usually cannot boot into the system.
BTW I am on Kitkat 4.4.4 without Sense and I want to flash Lollipop 5.0.2 Sense 7.
The RUU is from a Taiwanese variant 820ys which runs Lollipop 5.0.2 and Sense 7 out of the box, same models(htc_a50ml_dtul)
The problem is that the Kitkat Firmware has smaller partitions compared to the lollipop one. An example is the Kitkat system partition which is about 1.4Gbs while Lollipop has about 4.9Gbs, so I cannot flash with the same scatter file.
So I edit the scatter file to inflate the partitions in order to accommodate the big Lollipop files (sytem.img,recovery.img and boot.img) and perform firmware upgrade.
What could be stopping it from booting? Is it due the fact that the Lollipop boot and recovery are verified? Thanks in advance
Screenshots for Kitkat and Lollipop firmware files below
Click to expand...
Click to collapse
well this question will take the thread off topic. I would request you to create a new thread regarding this issue under "q&a,help and troubleshooting". Chances of your problem getting solved are higher if you do so. I will post my views regarding your issue in that thread. And i apologize to OP, because i only started answering questions irrelevant to his thread.
i totally accept off topics if they are helpful
sziraqui said:
but flashing recovery with SP flash tool will work for sure.
1. Put your custom recovery in the firmware folder,
2. del stock recovery.img,
3. rename your custom recovery as recovery.img,
4. load scatter file,
5. uncheck everything except recovery
6. click download and then connect your powered off phone to pc while holding vol down
someone Please confirm if this works with 820s, without worrying about bootloader
Click to expand...
Click to collapse
Hi.
It worked, but pressing Vol UP, not down. Anyway i've installed Recovery but when i try to access it from bootloader the device stopped me tellig that is for Android developers. I think that is because at the top of bootloader screen it tell "LOCKED". Any solution?
htc desire 820 softbrick not connecting with fastboot
I managed to track down the RUU for A5_DUG with CID: HTC__622 (Asia_HK version). The filename is:
0P9CIMG_A5_DUG_L50_DESIRE_SENSE60_MR_hTC_Asia_HK_2.34.708.1_Radio_1.13.3230.27.0303_13.19.3230.00D_F_release_443977_combined_signed_2_4.zip
I have uploaded it to MEGA here: [url]https://mega.nz/#!28QiwDqA!NovlOSELHcoW7D8LgT2UdYVfQn07QDtmhvC7AMEJz-4[/URL]
Please note that this RUU is of the Lollipop version. It is possible downgrade to it from marshmallow, and then update via OTA (and I recommend that you do so for more memory space. I have done this myself).
How to flash an RUU:
NOTE: This guide is relevant to all variants and CIDs of the device. However, the RUU that I linked above ONLY works for the specific variant+CID mentioned above! If you have a different variant OR CID you will need to find the correct RUU for your device. You can get your CID with:
Code:
fastboot oem readcid
NOTE 2: This guide is formatted incorrectly, and does not display correctly in the XDA app...
If you have unlocked the bootloader, you need to lock it. Run this command in FASTBOOT (ignore any errors that appear):
Code:
fastboot oem lock
Copy the RUU file to a MicroSD card. You must use a MicroSD card, it does NOT work on the internal storage! (I haven't tested with OTG but it might work)
Rename the file to 0P9CIMG.zip
Insert the MicroSD card into the device. Now boot to the bootloader (if you are in FASTBOOT choose HBOOT) and after a few seconds it will ask you if you want to update.
Choose yes. The process will take a while and the device will reboot at least once.
At the end it will tell you to press power to reboot. That means you are done and the device is restored to stock conditions.
Hi,
is it possible to relock the bootloader to original factory mode.
fastboot oem lock (will erase userdata)
Also you should restore the fbop partition: /dev/block/bootdevice/by-name/fbop
For more reference see:
https://forum.xda-developers.com/axon-7/help/lock-unlocked-bootloader-t3444044
https://forum.xda-developers.com/showpost.php?p=68738854&postcount=100
Also please don't open a thread to a question that has already been answered several times.
After i unlocked bootloader my phone now is recognized as A2017U. When i relock it will it then recognized as original A2017G ?
I am interested in a tutorial about going back to stock for G model
The procedure for the g model is no different than the U model except you have to revert the bootloader (fbop partition) because the european model is quite restricted.
For making a tutorial I would need to know exactly what you modified.
There are already good step by step guides in this forum. All I could offer you are my backup files for the recovery and bootloader for the 2017G with update B08.
Bomberus said:
The procedure for the g model is no different than the U model except you have to revert the bootloader (fbop partition) because the european model is quite restricted.
For making a tutorial I would need to know exactly what you modified.
There are already good step by step guides in this forum. All I could offer you are my backup files for the recovery and bootloader for the 2017G with update B08.
Click to expand...
Click to collapse
At the moment i am on B09 rooted but I installed it via TWRP using DrakenFx's tutorial from here : https://forum.xda-developers.com/showpost.php?p=68873485&postcount=3
Futhermore when I unlocked the bootloader I was on B03 and I saved the aboot.img and fbop_lock.img .
Now I would like to go back to fully stock to prepare for the android N update.
I would highly appreciate it if you could offer me some directions for this matter.
Never tried this method (so I take no responsibility) but in order to receive ota you need an unmodified system with locked bootloader.
To lock your bootloader:
First backup all your apps, data and internal sdcard !
Connect your phone to a PC and start adb:
Type: "adb reboot bootloader"
Phone will restart: (if you are on linux, run fastboot with root permission)
Type: "fastboot oem device-info" (just to check things)
"fastboot oem lock" (will lock your bootloader)
According to DrakenFX you should have the stock recovery already installed. So you can flash a sd card upgrade from ZTE "http://www.ztedevice.com/support/detail?id=98CEB24F9FFD433EA99EC424163149A6" (to bring you back to stock)
If you still have TWRP use DrakenFX files to flash your system back to stock, but this time do not flash supersu.
You should be good to go and just have to wait for ZTE to release the update and apply it via the updater UI.
BTW this is my fastboot oem device-info output:
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.059s]
finished. total time: 0.059s
Click to expand...
Click to collapse
dodo34 said:
Hi,
is it possible to relock the bootloader to original factory mode.
Click to expand...
Click to collapse
You mind my asking the reason WHY you want to Relock?
If is cuz the N update , I'll rather keep it unlock base on @lokissmile thread and I'm 100% sure I'll be releasing N TWRP Flashable Zips for all variants when N is available.
i have G model and flashed the aboot of the U modell.
How to flash back now the aboot of the G modell back ?
Any help for the G modell ?
dodo34 said:
Any help for the G modell ?
Click to expand...
Click to collapse
as far my understanding the G model have factory images right? just download the one you were using and flash it using custom recovery.
LifeSupportZ said:
as far my understanding the G model have factory images right? just download the one you were using and flash it using custom recovery.
Click to expand...
Click to collapse
@dodo34
This is correct, the full image should be the one that contains both the emmc_appsboot.mbn (this is your aboot or bootloader partition) and the fastboot.img (the fbop or fastboot command partition) as well as recovery.img. This will set everything back to stock in one swoop. Otherwise you have to reflash the signed (tenfars) TWRP to flash back the fastboot image and then falsh back stock, since regular TWRP will either not be there anymore or will not run since BL is locked now
P.S, you can leave the fastboot alone for the purposes of OTA, no update so far hes checked on it and i am not sure if there is a G package with it since it has not changed from release, so as long as the image you flash has the bootloader and recover you should be good for N
P.S.2 Actually I see a little catch 22 here. If you lock the BL first, then you will not be able to run TWRP or boot into system if it was modified. You would need to flash the "signed" version of TWRP or flash stock recovery before locking the BL. Stock would be preferable since it can flash the factory package withouht modifications. If using TWRP i think you have to change updater-script to remove a .... and i just found another catch 22. The updater-script will look for product name P996A04 and if yours shows as 2017U the it will report back P996A01 so you will have to have a signed TWRP on there no matter what. Either to flash the backed up aboot fbop and recovery and then flash the full factory package through stock recovery or mod the updater-script and remove the assert line and flash the whole thing with TWRP. What do you get in TWRP shel when you run this "getprop ro.product.model"
peramikic said:
@dodo34
This is correct, the full image should be the one that contains both the emmc_appsboot.mbn (this is your aboot or bootloader partition) and the fastboot.img (the fbop or fastboot command partition) as well as recovery.img. This will set everything back to stock in one swoop. Otherwise you have to reflash the signed (tenfars) TWRP to flash back the fastboot image and then falsh back stock, since regular TWRP will either not be there anymore or will not run since BL is locked now
P.S, you can leave the fastboot alone for the purposes of OTA, no update so far hes checked on it and i am not sure if there is a G package with it since it has not changed from release, so as long as the image you flash has the bootloader and recover you should be good for N
P.S.2 Actually I see a little catch 22 here. If you lock the BL first, then you will not be able to run TWRP or boot into system if it was modified. You would need to flash the "signed" version of TWRP or flash stock recovery before locking the BL. Stock would be preferable since it can flash the factory package withouht modifications. If using TWRP i think you have to change updater-script to remove a .... and i just found another catch 22. The updater-script will look for product name P996A04 and if yours shows as 2017U the it will report back P996A01 so you will have to have a signed TWRP on there no matter what. Either to flash the backed up aboot fbop and recovery and then flash the full factory package through stock recovery or mod the updater-script and remove the assert line and flash the whole thing with TWRP. What do you get in TWRP shel when you run this "getprop ro.product.model"
Click to expand...
Click to collapse
if he mod the updater_script from official zte update to make it flash friendly, this is what i'll do,
* Mod updater script and remove aboot and recovery for now
* flash new zip without file mention above
* boot to bootloader while having custom recovery
* lock back the bootloader
* boot to custom recovery and perform " format data "
* create a flashable zip with stock aboot and recovery
* flash new zip with aboot and recovery
* reboot to recovery and check if boot to stock recovery and while in there perform a factory reset
i know is a lot of steps but, seems like is the way to go to get everything back in place without zte noticing anything.
Now i am on B06.
I put update.zip B08 and select update. But it boots to TWRP recovery and update fails.
@dodo34 If you are trying to restore from the OS system update you need to reflash your stock recovery for it to work properly. Wait for someone to confirm what I just said, but that's how it worked for me.
how can i flash my original recovery. what is the command for cmd ?
Please help restoring back original recovery.
dodo34 said:
Please help restoring back original recovery.
Click to expand...
Click to collapse
rczrider said:
Putting Your Axon 7 Back to Stock
If you want to revert back to stock and re-lock your bootloader (eg. sending the phone in for warranty work or are selling it), you should be able to do that using the steps below. It worked for me, anyway, exactly as written below.
Copy everything off your internal storage that you don't want to lose. If you're not rooted (so already stock, but with unlocked bootloader), skip to step 6 below. Otherwise, continue.
Grab the "StockSystem" zip for your variant from this thread and place on your microSD card: http://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
Reboot into TWRP and wipe system, data, dalvik, and cache
Flash the StockSystem zip and power off (doing so will restore stock boot but does not appear to restore recovery)
Boot into EDL mode and flash stock recovery only: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
Power off the phone, plug from computer, and then boot into stock recovery (hold Vol+ and press Pwr, continue holding Vol+ until recovery comes up)
Select "Wipe data / factory reset" and then "Yes"
After that finishes, select "Reboot to bootloader"
Plug in your phone into your computer and do: fastboot oem lock (see second post if this doesn't work and says <waiting for device>)
Your phone will reboot and should have been totally wiped (including internal storage) by doing the above
This should leave you with a stock, locked, and unrooted phone that can take OTAs. Note: it's possible (in fact, likely) that an OTA could break the ability to unlock your bootloader and gain root again, so be careful about going back to stock if you think you'll want to unlock/root later on!
If you need any stock files for B20 or B27 (stock recovery for re-locking, for example), you can get them here: http://forum.xda-developers.com/axon-7/development/untouched-b20-boot-recovery-files-t3443818
Click to expand...
Click to collapse
Try this guide from newbie unlock thread.
I get this error.
C:\Users\Intel\Downloads\Axon7\ADB>axon7tool -r
Usage:
axon7tool -r <boot|recovery|gpt> ...
axon7tool -w <boot|recovery>
C:\Users\Intel\Downloads\Axon7\ADB>axon7tool -r recovery
Connecting to device...
S: failed to read command
S: Failed to receive hello
terminate called after throwing an instance of 'std::runtime_error'
what(): error: Unknown error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
what i did.
Flashed Draken TWRP System Image B06
Flashed Draken TWRP Stcok Recovery B06
Flashed full update.zip B08
Now my phone is recognized as A2017G on the PC
But when i reboot the phone i get a message that the phone is unlocked and not trusted ?
why ?
Does anyone have stock rom npns25.137-93-14 for xt1685 for fastboot flash ???
I am trying to get oreo OTA update to work, and i had twrp installed, tried to flash stock recovery.img "not sure i got the right version" but update to oreo failed for some reason....
Think i maybe must flash the stock rom again and lock bootloader....
There is no image leak for 137-93-14, however using this tool on your pc you can download and flash the latest system images for your device. Install it, connect, select rescue and reboot your phone to fastboot. It will format the phone so make sure you have backups of your files.
Disclaimer:I do not take responsibility for your bricked device. Try it at your own risk.
Notice:This guide is written mainly with these references:
Golv's Reply under Thread "NEW link add ...HTC U11 RUU 3.31.401.1 Dual sim"
paulpier007's GUIDE for Downgrading using HTC DevInfo Tool
Jason10246's Thread for Downgrading using hosd.img with RUU Decrypt Tool
Captain_Throwback's Thread for RUU Decrypt Tool
Introduction:
HTC started to use hosd partition to verify version number when you try to flash RUU since I do not know when for that I have been fairly unaware on HTC devices. A signature error 132 is returned when you try to downgrade with only a changed version number after reading Golv's downgrade guide. Which as a result I decided to write a new guide with a more general but not detailed guide for those with basic understandings of how to do this.
Requirements:
You have read those four threads above
RUU Decrypt Tool and Internet connection
RUU file that you would like to downgrade to
TWRP recovery
HTC adb and fastboot drivers installed and you have no issue finding your device in adb & fastboot
htc_fastboot
Steps:
Use RUU Decrypt Tool to decrypt your RUU using firmware option -f. You need internet connection to do this.
After completed, look for hosd.img in the output folder.
Change version number using Golv's method with HTC Version Tool. You can find it as the attachment.
Flash hosd.img file in bootloader, not download mode.
htc_fastboot flash hosd [pathToHosd.img]
Reboot to Download mode. If successful, the OS version will be the same as your RUU file that we would like to downgrade to.
Flash RUU in Download mode and it is done.
However, if your HTC U11 is the same as mine, Single SIM US Unlocked (WHL), you can just grab the 2.42.617.7 hosd.img that I extracted earlier which is in the attchments.