Related
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 ?
:crying::crying:can't able to flash twrp recovery image after all my bootloader is also unlocked it always shows (target max-sparse-size: 256MB
error: cannot load 'twrp.img': No error).......please help me what should i do...plzz help me developer, members plzz.:crying::crying:
Sounds like you're using an older version of fastboot. Try this one https://www.dropbox.com/s/bc1k1lol9nudy68/fastboot.zip?dl=0
Explain the steps you undertook to flash TWRP via fastboot.
If you haven't used the following,
fastboot flash recovery TWRP.xxxxxxx.img
fastboot boot TWRP.xxxxxx.img
where TWRP.xxxxxx.img is the name of the image file (while typing, pressing TAB after typing t autocompletes it, so that should help). I believe there is where you're going wrong.
Dear Team, I have MotoG4 Plus (Model XT1643).
Post selecting the data migration from internal storage to SD card, the phone stopped booting.
[[ Upon pressing the vol + power key ]] __
Restart bootloader screen shows
*oem_locked
*Software status: Modified (in yellow) __
Navigating to Bootloader logs screen, it shows
*failed to validate boot image
*ERROR: failed to pass validation, backup to fastboot Fastboot Reason: Fall-through from charger boot mode
Kindly suggest
Hmm, what were you trying to do prior to the soft boot? You mentioned data migration, how were you transferring data?
Given your bootloader is locked (OEM_locked), then something's corrupted your boot kernel and thus the bootloader isn't letting your device boot, as it can't verify your stock kernel signatures.
You may have to re-flash your stock ROM - can you remember which stock ROM build you had on your device?
chetana22 said:
Dear Team, I have MotoG4 Plus (Model XT1643).
Post selecting the data migration from internal storage to SD card, the phone stopped booting.
[[ Upon pressing the vol + power key ]] __
Restart bootloader screen shows
*oem_locked
*Software status: Modified (in yellow) __
Navigating to Bootloader logs screen, it shows
*failed to validate boot image
*ERROR: failed to pass validation, backup to fastboot Fastboot Reason: Fall-through from charger boot mode
Kindly suggest
Click to expand...
Click to collapse
Are u using dummy bootloader I guess not orginal
---------- Post added at 07:32 PM ---------- Previous post was at 07:26 PM ----------
No need to reflash u have to upgrade the bootloader then u have to flash the stock rom
@ Echo
Hmm, what were you trying to do prior to the soft boot? You mentioned data migration, how were you transferring data?
<<<< I was transferring data from phone memory to memory card via an option which says move media to SD card >>>>
Given your bootloader is locked (OEM_locked), then something's corrupted your boot kernel and thus the bootloader isn't letting your device boot, as it can't verify your stock kernel signatures.
You may have to re-flash your stock ROM - can you remember which stock ROM build you had on your device?
<<<< I have no idea about stock ROM build. If you can help, how would I know since my device is not starting? >>>>
@ usha55
Are u using dummy bootloader I guess not orginal
<<<< I do not know >>>>
---------- Post added at 07:32 PM ---------- Previous post was at 07:26 PM ----------
No need to reflash u have to upgrade the bootloader then u have to flash the stock rom
<<<< How do I upgrade? Please guide >>>>
@chetana22 thas makes confusion if you write post like that.
You just need to reflash boot.img only not whole ROM. To know the correct version of ROM and boot.img, post your phone's baseband/bootloader version, which is visible on bootloader screen.
____Mdd said:
@chetana22 thas makes confusion if you write post like that.
You just need to reflash boot.img only not whole ROM. To know the correct version of ROM and boot.img, post your phone's baseband/bootloader version, which is visible on bootloader screen.
Click to expand...
Click to collapse
Hi.
Im not able to upload the image. Pl. find baseband details below.
Baseband: M8952_70030.25.03.62.01R ATHENE_INDIA_DSDS_CUST
Pls let me know steps to reflash boot.img
chetana22 said:
Hi.
Im not able to upload the image. Pl. find baseband details below.
Baseband: M8952_70030.25.03.62.01R ATHENE_INDIA_DSDS_CUST
Pls let me know steps to reflash boot.img
Click to expand...
Click to collapse
If you have locked bootloader, flashing of older boot.img may not work. You need to flash whole firmware.
See here,
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138/page8
Download it and flash it, instructions are given there.
If you have important data on your phone, say photos/videos/or any file, then skip "erase userdata" command.. when you get device working, copy your data and then wipe your device.
Tried the method as given.
At the end ..it is repeatedly showing
FAILED (remote failure)
chetana22 said:
Tried the method as given.
At the end ..it is repeatedly showing
FAILED (remote failure)
Click to expand...
Click to collapse
Which stock firmware are you flashing that gives you this error? Please mention the build number.
You may have to try flashing with the NPJS25.93-14-10 stock ROM: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Flash as per below commands if you want to save your data (no need to re-lock your bootloader).
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
It does not work
echo92 said:
Which stock firmware are you flashing that gives you this error? Please mention the build number.
You may have to try flashing with the NPJS25.93-14-10 stock ROM: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Flash as per below commands if you want to save your data (no need to re-lock your bootloader).
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
It does not work
al3al3al3jandr0 said:
It does not work
Click to expand...
Click to collapse
What didn't work, please describe more about what happened?
From your other post, I saw that gpt and bootloader worked. Did you ensure that all the firmware files in your ADB folder are from the same patch? Some of them appear to have different dates. I would delete all the firmware files in your ADB folder (except your minimal ADB filled) and extract a fresh copy of the stock ROM to your ADB folder and try again. Double check you're extracting the NPJS25.93-14-10 ROM.
Now the error sends it to me in the boot.img
echo92 said:
What didn't work, please describe more about what happened?
From your other post, I saw that gpt and bootloader worked. Did you ensure that all the firmware files in your ADB folder are from the same patch? Some of them appear to have different dates. I would delete all the firmware files in your ADB folder (except your minimal ADB filled) and extract a fresh copy of the stock ROM to your ADB folder and try again. Double check you're extracting the NPJS25.93-14-10 ROM.
Click to expand...
Click to collapse
Now organize the original firmware and download the December OTA, replace the gpt.bin file with the OTA one. Now the error sends it to me in the boot.img
al3al3al3jandr0 said:
Now organize the original firmware and download the December OTA, replace the gpt.bin file with the OTA one. Now the error sends it to me in the boot.img
Click to expand...
Click to collapse
1) Why are you adding the December 2017 GPT.bin to the NPJS25.93-14-10 flash files? Mixing and matching patch levels especially with you re-locking the bootloader can be very risky, and could result in you bricking your device.
2)Are you getting the same error with flashing the boot.img? Can you confirm with an md5 checksum tool (http://www.winmd5.com/ ) that your boot.img (the kernel) has the md5 checksum: 61473507904cc98b5dcc508a1a35e657 If the checksum is different, I urge you again to doublecheck you've copied the right files from the stock ROM. If you're re-locking, you generally must have only the flash files from the same stock ROM patch level, you cannot mix and match old and new stock ROMs.
Again, if you're not sure, delete all the stock ROM files from your folder and re-extract clean, fresh copies from the stock ROM zip.
3)If you've updated to NPJS25.93-14-13 previously via OTA update (the December 2017 stock ROM), then you cannot use this method to re-lock your bootloader and flash the stock ROM. The stock ROM used to re-lock a Motorola device must be of the same build/newer than what you had on your device. You'd have to wait for the NPJS25.93-14-13 stock ROM.
thank you
echo92 said:
1) Why are you adding the December 2017 GPT.bin to the NPJS25.93-14-10 flash files? Mixing and matching patch levels especially with you re-locking the bootloader can be very risky, and could result in you bricking your device.
2)Are you getting the same error with flashing the boot.img? Can you confirm with an md5 checksum tool (http://www.winmd5.com/ ) that your boot.img (the kernel) has the md5 checksum: 61473507904cc98b5dcc508a1a35e657 If the checksum is different, I urge you again to doublecheck you've copied the right files from the stock ROM. If you're re-locking, you generally must have only the flash files from the same stock ROM patch level, you cannot mix and match old and new stock ROMs.
Again, if you're not sure, delete all the stock ROM files from your folder and re-extract clean, fresh copies from the stock ROM zip.
3)If you've updated to NPJS25.93-14-13 previously via OTA update (the December 2017 stock ROM), then you cannot use this method to re-lock your bootloader and flash the stock ROM. The stock ROM used to re-lock a Motorola device must be of the same build/newer than what you had on your device. You'd have to wait for the NPJS25.93-14-13 stock ROM.
Click to expand...
Click to collapse
ok thank you very much, you're right I'll have to wait
Sir, how to fix no found bootimage in m0t0 g4plus XT1643
Adityashankar said:
Sir, how to fix no found bootimage in m0t0 g4plus XT1643
Click to expand...
Click to collapse
Did this happen suddenly, and is this with the stock firmware or using a custom ROM?
You could try flashing the Oreo stock firmware: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Hello team, I have the same problem like chetana22 but with motorola one xt-1941-4. When i was transfering (probably) virus file from internal storage to usb flash memory, the phone stopped booting.
I have inportant and private files on internal storage, phone have quarantee... What can i do? Pls help
flash latest stock rom and skip the following instruction while flashing
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
MOTOROLA G5S PLUS - Start up failed
My phone is G5s PLUS ... Sorry
Hi All,
Moto G4 Plus XT1643 is my phone model.
Was not being used for past 6 months, and it got stuck the boot screen .
Tried the factory reset, it got stuck in the fast boot.
Then tried the tool given by Lenovo, no luck. The "fast boot" option in the software fails.
Anyway, came to our good old XDA.
tried the options in the forum https://forum.xda-developers.com/t/...c-01-security-patch-fastboot-7-0-8-1.3608138/
Now, i am stuck with the below screens, i have attached them
Allso, do i need to start a separate thread?
Kindly help me out.
Hello Guys,
I have a U Ultra with a boot problem.
Failure: It starts, show up the logo for a short time, than it shut down.
In fastboot mode the lock status is relocked. Flashing in fastboot there is no chance. Because the OEM Unlock flag in the rom is off. The recovery does nothing, same behavior as on startup...
The only way to get the phone back to life is the sideload via OTA flash zip file on a sdcard.
Problem: I don't have such a file with os 2.21.410.1, I have only a 1.64.401.10 file.
If I try this file it shows me a Version Androis-Info Error.
Where can I get such a flash file with the version 2.21.401.1 with oreo (european version)?
On the other side I try to patch the info.bin file but , the version is easy to patch but it seems so that this file has a byte in front, that changed in a unknown way and 8 bytes in the middle of the file with the same problem, this could be a file size or checksum I don't know what it is and how it will be generated. The rest of the file is filled with zeroes.
Does somebody have information about the file structure of the info.bin in the flash file?
I heared about LeeDrOiD, that he worked a long time for HTC, maybe he could help to get this phone back to life????
Phone Info:
C:\ADB>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_oceuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1578400000
(bootloader) serialno: ************
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: ***************
(bootloader) version-main: 2.21.401.1
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PZF10000
(bootloader) cid: HTC__034
Hope someone can help me...
davii
good/bad news
hi guys,
I run thru the infos from an other post here in the forum and that I have done successfully.
https://forum.xda-developers.com/u-ultra/help/howto-unbrick-ultra-t3891033
The behaviour is now a bit different, it runs now in a boot loop, the logo has change to the normal htc logo without red text. The recovery shows a red exclamation mark, and run in the bootloop...
The main problem remains, I need a 2.21.401.1 firmware file to flash on the phone... what a m....
I can't find such a file in the internet, the exe firmaware files end up on version 1.64... and I think, this are only us version files. I need HTC__034.
Any ideas?
Is it possible to patch a lower version of a firmware rom just to get the phone running, to open the OEM unlock, and than to flash whatever? I have an twrp backup of my mobile.
The firmware.zip file from @minhnewpro in OTA, where does it come from? The OTA looks like a twrp or titanium backup file. But I can't get it in my mobile without twrp...
Were it possible to integrate the twrp.img in the firmware.zip file as recovery partion? Would it help at all without the open bootloader, can twrp write things with a locked bootloader? I'm not so firm in that matter... In my understanding of this matter it can???
davii
davi133 said:
hi guys,
I run thru the infos from an other post here in the forum and that I have done successfully.
https://forum.xda-developers.com/u-ultra/help/howto-unbrick-ultra-t3891033
The behaviour is now a bit different, it runs now in a boot loop, the logo has change to the normal htc logo without red text. The recovery shows a red exclamation mark, and run in the bootloop...
The main problem remains, I need a 2.21.401.1 firmware file to flash on the phone... what a m....
I can't find such a file in the internet, the exe firmaware files end up on version 1.64... and I think, this are only us version files. I need HTC__034.
Any ideas?
Is it possible to patch a lower version of a firmware rom just to get the phone running, to open the OEM unlock, and than to flash whatever? I have an twrp backup of my mobile.
The firmware.zip file from @minhnewpro in OTA, where does it come from? The OTA looks like a twrp or titanium backup file. But I can't get it in my mobile without twrp...
Were it possible to integrate the twrp.img in the firmware.zip file as recovery partion? Would it help at all without the open bootloader, can twrp write things with a locked bootloader? I'm not so firm in that matter... In my understanding of this matter it can???
davii
Click to expand...
Click to collapse
Well, i used to have U Ultra and now it is dead =] and i can not do anything (Hardware problem), even i tried flash RUU by CMD or SD Card.
Back to your question. Maybe you only can try to boot into DOWNLOAD MODE => Bootloader => recovery => apply ota update.zip
minhnewpro said:
Well, i used to have U Ultra and now it is dead =] and i can not do anything (Hardware problem), even i tried flash RUU by CMD or SD Card.
Back to your question. Maybe you only can try to boot into DOWNLOAD MODE => Bootloader => recovery => apply ota update.zip
Click to expand...
Click to collapse
Thx dude,
I'm already on 2.21.401.1, there is no update for 2.21.401.1 in the net, no chance to flash a stock rom... :crying:
davi133 said:
Thx dude,
I'm already on 2.21.401.1, there is no update for 2.21.401.1 in the net, no chance to flash a stock rom... :crying:
Click to expand...
Click to collapse
hey guys, I have another idea...
my wifes mobile is the same..., and that mobile is on 1.64...,
were it possible to initiate the update on 2.21..., and then it downloads the update file. Where resides this update file? Can I get this file from my wifes mobile, to flash it on my mobile?
Does anybodey know this?
In my opinion this process is the same as the RUU flash, the file must be on a special partition, I think, then the mobile goes into RUU flash mode, and the command are fired to flash this rom, thats what I think...
davii
davi133 said:
Thx dude,
I'm already on 2.21.401.1, there is no update for 2.21.401.1 in the net, no chance to flash a stock rom... :crying:
Click to expand...
Click to collapse
Try to reflash OTA.zip by using stock recovery, maybe it will works.
minhnewpro said:
Try to reflash OTA.zip by using stock recovery, maybe it will works.
Click to expand...
Click to collapse
the recovery don't comes up, it also hangs in a bootloop. Or do you mean something different?
I can go to the fastboot mode, or in the bootmode for recovery, that dosen't help, I have no OTA with 2.21.401.1, that I could flash, just a lower version (1.64.401.10), that will be rejected by the RUU flash in because of the wrong version. To change the version in the bootloader I need a open bootload and a running os with adb, all that isn't the case.
I need OTA flashable rom with the 2.21.401.1 version to run it with RUU flash, and if this works is will work, that is the next question..., I think and hope it will work...
Why does the recovery didn't comes up, maybe that is the same problem as in the boot situation, the dead boot.img or a corrupted os, I don't know the reason, my last flash was a LeDrOiD, the boot.img maybe does no fit the original boot process. On the other hand, LeDrOiD was also an Oreo rom, as I had a problem with my magisk update I put back my original boot.img from my mobile backup, and my mobile boots up normaly, then I flashed back the LeDrOiD system things and it boots up normaly and magisk was fine.
I don't know whats wrong, why the recovery was gone, why the boot.img dosen't work and so on...
where resides the recovery.img? In the same partition as the boot partition or on its own partition?
Any other ideas?
davi133 said:
the recovery don't comes up, it also hangs in a bootloop. Or do you mean something different?
I can go to the fastboot mode, or in the bootmode for recovery, that dosen't help, I have no OTA with 2.21.401.1, that I could flash, just a lower version (1.64.401.10), that will be rejected by the RUU flash in because of the wrong version. To change the version in the bootloader I need a open bootload and a running os with adb, all that isn't the case.
I need OTA flashable rom with the 2.21.401.1 version to run it with RUU flash, and if this works is will work, that is the next question..., I think and hope it will work...
Why does the recovery didn't comes up, maybe that is the same problem as in the boot situation, the dead boot.img or a corrupted os, I don't know the reason, my last flash was a LeDrOiD, the boot.img maybe does no fit the original boot process. On the other hand, LeDrOiD was also an Oreo rom, as I had a problem with my magisk update I put back my original boot.img from my mobile backup, and my mobile boots up normaly, then I flashed back the LeDrOiD system things and it boots up normaly and magisk was fine.
I don't know whats wrong, why the recovery was gone, why the boot.img dosen't work and so on...
where resides the recovery.img? In the same partition as the boot partition or on its own partition?
Any other ideas?
Click to expand...
Click to collapse
Try extract recovery from ota.zip file and flash in download mode.
minhnewpro said:
Try to reflash OTA.zip by using stock recovery, maybe it will works.
Click to expand...
Click to collapse
hey dude,
please don't be serious but have you read my starting thread?
The bootloader is locked, you can't flash anything with fastboot! The only way to flash something is over RUU flash, so I'm a bit confused about your proposals :angel:
I hope I don't missunderstand things, because you are a senior member, and I do not want to upset anyone.
There is no OTA on the mobile so that the recovery can do it's job.
Wich OTA you mean? The real OTA from HTC look like:
OZA.zip
info.bin
zip_0.zip
zip_1.zip
etc...
Your and the other OTA's look like this:
OTA.zip
[dir] META-INF
[dir] preload
contexts.bin
etc....
Your OTA's are flashable from twrp, made with (I don't know, titanium backup)
A RUU flash want me to pass a real HTC OTA with a version higher or equal to that version that is installed before...
I know, there is a possibility to extract your OTA's but what is it good for? fastboot can't flash the recovery.img because the bootloader is locked.
That's my actual understanding of this matter and that's the behavior of the mobile.
If I'm wrong with something, please let me know.
davi133
new information on my side
The recovery comes up with these special key's (wait for the red exclamation, press power + VolUp).
Ok, but the information from htc support "WIPE DATA/FACTORY RESET" leads also to no success. Everything was made fine but after reboot is the bootloop.
The new menu in the recovery offers me to flash a real OTA from a ADB process or a SDcard, hmm, ok there is controled way now for doing this but I tryed all may real OTA's without success, because of the lower version or false cid's.
I asked the support for an actual OTA update file, but I dont think that they will give me that file.
The ADB process is a very restricted version of ADB, that mean's you can't get a shell or something like that, just the sideload and print some variables...
Is it possible to extract the real OTA, change something, and repack it?
davi133
davi133 said:
The recovery comes up with these special key's (wait for the red exclamation, press power + VolUp).
Ok, but the information from htc support "WIPE DATA/FACTORY RESET" leads also to no success. Everything was made fine but after reboot is the bootloop.
The new menu in the recovery offers me to flash a real OTA from a ADB process or a SDcard, hmm, ok there is controled way now for doing this but I tryed all may real OTA's without success, because of the lower version or false cid's.
I asked the support for an actual OTA update file, but I dont think that they will give me that file.
The ADB process is a very restricted version of ADB, that mean's you can't get a shell or something like that, just the sideload and print some variables...
Is it possible to extract the real OTA, change something, and repack it?
davi133
Click to expand...
Click to collapse
Hi Davi,
check this out (don't ask me what i had to do to get it... ):
2PZFIMG_OCEAN_NOT[email protected]80307_63.34_release_522808_signed_2_4
Rename the file to "2PZFIMG.zip" and place it in root of sdcard. Boot into download mode and confirm flash with volume+ button
thank you
Siluxsept said:
Hi Davi,
check this out (don't ask me what i had to do to get it... ):
2PZFIMG_OCEAN_NOT[email protected]80307_63.34_release_522808_signed_2_4
Rename the file to "2PZFIMG.zip" and place it in root of sdcard. Boot into download mode and confirm flash with volume+ button
Click to expand...
Click to collapse
been waiting for this firmware also..i will try this hope everything works
update
the flashing was succesfull on my htc ultra and its works..hope this can help also the op..
Siluxsept said:
Hi Davi,
check this out (don't ask me what i had to do to get it... ):
2PZFIMG_OCEAN_NOT[email protected]80307_63.34_release_522808_signed_2_4
Rename the file to "2PZFIMG.zip" and place it in root of sdcard. Boot into download mode and confirm flash with volume+ button
Click to expand...
Click to collapse
Thanks for this
Hi so I been seeing many people getting stuck on fastboot after flashing ROM so here is the method u can use if u can't boot to TWRP also.
I have tired on PA ROM and it works so idk about others ROMs ..
fastboot flash dtbo dtbo.img
fastboot flash logo logo.img
fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot flash misc misc.img (u can get on fastboot rom not .zip)
fastboot flash recovery recovery.img (recommend used twrp-3.3.1-2-davinci-fix).. Russian one
And after those comands do run TWRP auto installer.
U can find those files from fastboot stock ROM. This will save ur data and u won't needed to flash Stock ROM ..
Hope I explained everything if anything else needed comment down below.
Hi, i'm stuck in this fastboot limbo but can't find some of these files you mentioned: logo.img and misc.img
Where do i get them?
edit: nevermind, solved flashing fastboot miui with miflash pro.
EDIT 2: after flashing a rom i get stuck in fastboot everytime. How to avoid this?
Also tried flashing those files in that exact sequence but still stuck in fastboot.
My persist.img is shown not writable in cmd if I try to flash it. If I flash a rom using TWRP an error pops up saying "failed to mount /persist' (Invalid Argument).
SOLVED- Flashing persist.img from twrp "Install Image" works.
farhan20 said:
Hi so I been seeing many people getting stuck on fastboot after flashing ROM so here is the method u can use if u can't boot to TWRP also.
I have tired on PA ROM and it works so idk about others ROMs ..
fastboot flash dtbo dtbo.img
fastboot flash logo logo.img
fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot flash misc misc.img (u can get on fastboot rom not .zip)
fastboot flash recovery recovery.img (recommend used twrp-3.3.1-2-davinci-fix).. Russian one
And after those comands do run TWRP auto installer.
U can find those files from fastboot stock ROM. This will save ur data and u won't needed to flash Stock ROM ..
Hope I explained everything if anything else needed comment down below.
Click to expand...
Click to collapse
Could you (or anyone) please provide these files.
Reep1324 said:
Could you (or anyone) please provide these files.
Click to expand...
Click to collapse
Hi, this u can get from fastboot stock Rom, download fastboot stock Rom and extract them u will find.. if need help just tag me ..
farhan20 said:
Hi, this u can get from fastboot stock Rom, download fastboot stock Rom and extract them u will find.. if need help just tag me ..
Click to expand...
Click to collapse
i got the .img file but i cant install it via twrp or fastboot cause this partition is unmountable
do you have any idea? i flashed stock rom via fastboot but the error insists
Dr.Dinel said:
i got the .img file but i cant install it via twrp or fastboot cause this partition is unmountable
do you have any idea? i flashed stock rom via fastboot but the error insists
Click to expand...
Click to collapse
Hello, seems u need to repair ur partition from TWRP.
Also what u did that cause this ?
PS: I'm not expert or anything but I will try to help if I could.
farhan20 said:
Hello, seems u need to repair ur partition from TWRP.
Also what u did that cause this ?
PS: I'm not expert or anything but I will try to help if I could.
Click to expand...
Click to collapse
thanks for replying
i finally solved it, used a chinese twrp that has the option to install on persist partition and the rest was easy
My k20 bricked after install miui 11 Chine version i try to flashing with flash tool but after processing not working "error antirolback check error" please someone help me
hamidezat20 said:
My k20 bricked after install miui 11 Chine version i try to flashing with flash tool but after processing not working "error antirolback check error" please someone help me
Click to expand...
Click to collapse
Hi, please follow this setups and it should be fine .
If you run into errors flashing fastboot images to your device, edit the .bat files that came with it. Usually you want to edit "flash_all.bat"
For "Missmatching image and device":
Remove the lines highlighted in the screenshot from the file, save and try flashing it again.
For Antirollback Error:
Remove ALL lines ABOVE the highlighted lines in the screenshot from the file, save and try flashing it again.
Always make sure that you got the right image for your device. Removing check lines from these files can permanently brick your device if you use the wrong fastboot image.
farhan20 said:
Hi, please follow this setups and it should be fine .
If you run into errors flashing fastboot images to your device, edit the .bat files that came with it. Usually you want to edit "flash_all.bat"
For "Missmatching image and device":
Remove the lines highlighted in the screenshot from the file, save and try flashing it again.
For Antirollback Error:
Remove ALL lines ABOVE the highlighted lines in the screenshot from the file, save and try flashing it again.
Always make sure that you got the right image for your device. Removing check lines from these files can permanently brick your device if you use the wrong fastboot image.
Click to expand...
Click to collapse
like me please help me after installing miui 11 Chine version
hamidezat20 said:
like me please help me after installing miui 11 Chine version
Click to expand...
Click to collapse
U r stuck on fastboot right and u said u can't flash fastboot rom because u r getting anti roll back error so I gave u solution
How to fix this problem
Hello same me how to fixed step by step
First you need fastboot rom extract fastboot rom on your pc after extract find 3 file
1-boot
2-recovery
3-system
Flash with fastboot
Turn off your phone and going to fastboot
Type
Fastboot devices
Fastboot flash boot boot.img
Fastboot flash recovery recovery.img
Fastboot flash system system.img
Done device can't boot but you can install twrp China version link ?
https://www.lanzous.com/i6ahykh
after installation you can go to twrp
Download fastboot miui install from twrp
Sorry for me English
Oh my god, you saved me!
HI guys i flashed my mi 9t with twrp-3.3.1-2-davinci-fix it worked with miui.eu 9.8.15 after trying to flash miui 11 for about 6 hrs lol, anyway my phone is working but i would like to go back to stock and relock the bootloader but i cant find the mi 9t fastboot rom
timbook2 said:
HI guys i flashed my mi 9t with twrp-3.3.1-2-davinci-fix it worked with miui.eu 9.8.15 after trying to flash miui 11 for about 6 hrs lol, anyway my phone is working but i would like to go back to stock and relock the bootloader but i cant find the mi 9t fastboot rom
Click to expand...
Click to collapse
You're able to flash miui 11 after such long time or just 9.8.15?
farhan20 said:
Hi, please follow this setups and it should be fine .
If you run into errors flashing fastboot images to your device, edit the .bat files that came with it. Usually you want to edit "flash_all.bat"
For "Missmatching image and device":
Remove the lines highlighted in the screenshot from the file, save and try flashing it again.
For Antirollback Error:
Remove ALL lines ABOVE the highlighted lines in the screenshot from the file, save and try flashing it again.
Always make sure that you got the right image for your device. Removing check lines from these files can permanently brick your device if you use the wrong fastboot image.
Click to expand...
Click to collapse
hey i am getting file missmatching image and device error so i deleted those lines from .bat file but still getting the same error
lucifer said:
hey i am getting file missmatching image and device error so i deleted those lines from .bat file but still getting the same error
Click to expand...
Click to collapse
Hi, u deleted from flash all. Bat right and what's the error u r getting?
farhan20 said:
Hi, u deleted from flash all. Bat right and what's the error u r getting?
Click to expand...
Click to collapse
well it worked after i moved the file to c:/ drive but after flashing i lost widewine L1
When I got 9.8.15 working I stopped at least I got a working phone now, I will try and flash stock later.
I got anti rollback error trying to flash stock with miflash tool.