After the last OTA update, my Moto G5 started to boot with the following warning:
"
Your device has failed verification and may not work properly.
To learn more visit:
motorolacom/unlockbootloader
ID: N/A
Your device will boot in 5 seconds
"
It also started to restart randomly.
I did some research on the web and found out that this warning appears when someone unlocks/roots the device.
The problem is that I aver never unlocked the bootloader or rooted the device.
When I boot to fastboot it says "OEM Locked" and the app DevCheck says that I am not rooted.
It seems to me that the update corrupted something and now some piece of software flags my device as unlocked.
Besides the irritating screen, some apps are not working properly or cannot be downloaded from the store.
I tried to reset to factory settings and wipe caches. Problem still happens.
I'd like to know if you guys know a solution for this problem.
I saw on another post that this problem was happening on some Verizon Moto Zs and they provided a software to reinstall the rom
Unfortunately, Motorola has not released a software to do the same to unlocked devices.
My ROM version is: NPPS25.137-33-6 (yeah, there is an "S" that I don't find in the roms available here)
The baseband is: M8937_8000.122.02.45R
(CEDRIC_BRAZILDSDS_CUST)
I was thinking in loading the rom into internal memory, reboot in recovery mode and flash the rom using the option "Install package from zip".
Do you know if it would work without an unlocked bootloader. Is it safe?
Thank you for the help,
Don't know if you can flash the boot logo without an unlocked bootloader but if you can here it is
Put phone in fastboot mode
Download logo from link below
Enter the following in a windows command prompt where you have fastboot files (Google to learn howto install Android sdk) & the logo file
Code:
fastboot.exe flash logo logo-g5-fix.bin
http://drive.google.com/file/d/0B-idWfPYugGvREJaR3B0UFIxUkU/view?usp=sharing
If you can't then you have no option but to wait for Motorola to fix it if you really haven't modded your phone
TheFixItMan, I really appreciate your answer.
But in that case wouldn't I just be changing the warning screen?
The problems with Netflix and other apps would remain.
I need something to fix the cause of the problem.
Have you guys heard about that problem before?
This guy had the same problem, but verizon patched it:
https://community.verizonwireless.com/thread/921991
hoferbr said:
TheFixItMan, I really appreciate your answer.
But in that case wouldn't I just be changing the warning screen?
The problems with Netflix and other apps would remain.
I need something to fix the cause of the problem.
Have you guys heard about that problem before?
This guy had the same problem, but verizon patched it:
/QUOTE]
I have the same problem as you. Could you fix it?
Thank you,
Luciano
Click to expand...
Click to collapse
You can go back to stock using ADB update or by flashing VERIFIED images in bootloader mode. This will work even when bootloader is locked.
p8tgames said:
You can go back to stock using ADB update or by flashing VERIFIED images in bootloader mode. This will work even when bootloader is locked.
Click to expand...
Click to collapse
To flash using bootloader I need just to copy the .zip in the internal memory, reboot in reboot in bootloader mode and select the option "install from .zip file"?
Where do I find the verified image for my device?
If I flash an unverified image will my device brick ou the bootloader will present a "impossible to procede" screen?
Thank you for the help!
hoferbr said:
To flash using bootloader I need just to copy the .zip in the internal memory, reboot in reboot in bootloader mode and select the option "install from .zip file"?
Where do I find the verified image for my device?
If I flash an unverified image will my device brick ou the bootloader will present a "impossible to procede" screen?
Thank you for the help!
Click to expand...
Click to collapse
you can flash what ever you want in fastboot -
However - In terms of firmware, if you are trying to flash incorrect firmware then the verification check will fail and it will not flash
Just don't flash a new bootloader if you are worried about it - its not needed unless you are upgrading an android version and that version has an updated bootloader
So I am safe if I follow these steps:
Manually Update Android Nougat for Moto G5 (NPP25.137-33) via Recovery
First of all, Go to Settings –> About Phone –> Tap on Build Number 7 Times.
Go to Developer Options –> Enable USB Debugging.
Save Stock Android Nougat rom for Moto G5 and save it in Internal storage.
Reboot Moto G5 Plus to Recovery Mode.
Select Apply Update from SD Card.
Select the Downloaded ZIP file from SD Card.
Wait until Installation process Completes.
Once the Installation completed. Reboot the Phone.
If my ROM is a wrong version, will the bootloader detect and deny instalation?
hoferbr said:
So I am safe if I follow these steps:
Manually Update Android Nougat for Moto G5 (NPP25.137-33) via Recovery
First of all, Go to Settings –> About Phone –> Tap on Build Number 7 Times.
Go to Developer Options –> Enable USB Debugging.
Save Stock Android Nougat rom for Moto G5 and save it in Internal storage.
Reboot Moto G5 Plus to Recovery Mode.
Select Apply Update from SD Card.
Select the Downloaded ZIP file from SD Card.
Wait until Installation process Completes.
Once the Installation completed. Reboot the Phone.
If my ROM is a wrong version, will the bootloader detect and deny instalation?
Click to expand...
Click to collapse
if you are talking about an official ota update then it will fail - you cannot update like this
An offical ota zip requires a non rooted device, unmodified system partition and stock recovery
you maybe able to download the ota update and save it (its in the cache partition)
then use flashfire app to install it
note if its a custom rom than recovery mode will allow you to flash any zip and will flash anything unless the updater script specifies a certain build.prop target eg phone model or other criteria that would stop it flashing if it was false
If you want to flash firmware you need the firmware image and flash it via fastboot
TheFixItMan said:
if you are talking about an official ota update then it will fail - you cannot update like this
An offical ota zip requires a non rooted device, unmodified system partition and stock recovery
you maybe able to download the ota update and save it (its in the cache partition)
then use flashfire app to install it
note if its a custom rom than recovery mode will allow you to flash any zip and will flash anything unless the updater script specifies a certain build.prop target eg phone model or other criteria that would stop it flashing if it was false
If you want to flash firmware you need the firmware image and flash it via fastboot
Click to expand...
Click to collapse
I have the same problem, but I unlock the booloader after with the intention to relock when flashing a stock rom.
But every stock rom I have downloaded when flashing with mfastboot shows a version security downgrade error and cannot reflash stock rom.
My bootloader is B8.23.
Any help appreciatte.
jdonadel said:
I have the same problem, but I unlock the booloader after with the intention to relock when flashing a stock rom.
But every stock rom I have downloaded when flashing with mfastboot shows a version security downgrade error and cannot reflash stock rom.
My bootloader is B8.23.
Any help appreciatte.
Click to expand...
Click to collapse
You need firmware that matches or exceeds your current firmware version - you cannot flash a lower firmware version
TheFixItMan said:
You need firmware that matches or exceeds your current firmware version - you cannot flash a lower firmware version
Click to expand...
Click to collapse
Yeah, I see that, but looking into the stock rom .zip file I cannot find the correct ID that matches to my. But since I posted the reply, I´ve downloaded from a mirror in lolinet, and correct flash my phone.
Related
Hello, friends!
It's been a really long time after my Q900 and X3D-SE...
For those who are having trouble with Asus Fonepad 7 2014 FE170CG in terms of softbrick, kindly take some time to read this thread.
I am currently on Latest Kitkat with version: 11.2.3.33
1.) In terms of Rooting(Offcourse YES, this tab is rootable) i rooted this device with Rootzenphone.apk(attached below). Kindly follow the tutorial here to root the device. When it doesn't get rooted in first time, repeat it. I got it rooted at 1st time itself. After rooting, i removed all the apps i don't need!
2.) To update your Fonepad, download the appropriate zip firmware(zip rom) from the Asus site. Download the matching SKU's only. For eg: WW-WW, CN-CN, JP-JP etc... And i really don't know about installing CN firmware over WW variants. After downloading, rename your file accordingly. Eg: UL-K012-WW-11.2.3.33-user.zip to k012_sdupdate.zip and put the file in the root of external SD card. Time to backup all your critical data! Finally switch off your tab. Now press Vol up + Power buttons until you see the Asus logo. If you are in Jelly Bean, the options are slightly different where you have to choose SD update. Your tab will now reboot to recovery, installs the update and reboots back to the installed firmware. On the other hand, if you are in KitKat, the options like SD download and SD update won't be available because they are removed from the newer Fastboot images. The SD update and SD download are now replaced by recovery option which is the one you need to select. After that device will reboot and install the updates.
3.) To downgrade the firmware to JellyBean, download the appropriate version of the firmware file(I used UpdateLauncher_K012_WW_10_32_1_33_1.zip) and follow the steps as above. Your device will be downgraded. In this version the options on the Droidboot menu will be different from the KitKat version. Just choose SD update to install any other updates.
4.) This is the main part for which i am creating this thread!
THE SOFT BRICK
I was pulling off my hairs for about a day trying to figure out the problem.
Reason for my softbrick: I got a feeling that my device was slightly going slow and the amount of available free RAM was only 200MB. SO, i was considering to Downgrade the firmware from Kitkat to Jellybean. I downloaded the Jellybean firmware UpdateLauncher_K012_WW_10_32_1_33_1.zip from the Asus site and installed it using the method above! Everything went fine and device booted to JellyBean with the familiar interface. Everything was fine but i noticed that the device was slightly heating up and was missing many features like dual apps etc... Hence i decided to go back to KitKat which is were all the problems began! I downloaded the latest firmware UL-K012-WW-11.2.3.33-user.zip. Installation begun as usual but at the end, installation was terminated with a message error. I was shocked! When i rebooted the device i got a USB icon with a red progress bar in a second and went away! The device neither booted nor charged! I repeatedly tried this procedure but failed continuously. I booted to the Droid Boot and saw the firmware version was fine and can't figure what the problem was! But i noticed that the same JellyBean firmware installed again without any glitches and booted fine. When i tried the Kitkat firmware, it failed again and device didnt't boot. This is tricky part! So, i downloaded the first kitkat firmware UL-K012-WW-11.2.3.18.2-user.zip after the JellyBean and tried to install it. To my suprise, the installation went fine and device booted up with that KitKat firmware. Now i put the latest Kitkat firmware UL-K012-WW-11.2.3.33-user.zip to the external SD card and tried to install it and it successfully installed :victory: :victory: Now i am back on the latest firmware
My recommendation : If you do anything, make sure to backup data and have knowledge on what you are doing. Thanks for reading this thread. Please press thanks if i helped you!
Lollipop update has been released some time ago. Please remember to unroot before you update or else you'll get soft bricked.
downgrade and ota update
In lillipop i got major laggs and baterry drained more than 50% over night in standby mode.
So I downgrade to latest kitkat WW_V11.2.3.33 from asus site, using fastboot and intel temporary cwm recovery.
It works great but now ifwi is 64.33 from lollipop, not 64.25 from kitkat.
It seems there is an OTA update WW_V11.2.3.34 but I dont get notification for download.
Is there any way to downgrade ifwi version?
Or do I have to ask here someone for capture the WW_V11.2.3.34 OTA update from /cache and upload here?
Or is there any fix for lillipop horrible lag (2-3 secs after presing or swiping) and masive battery drain? I tried factory reset lollipop and even reinstall with fastboot erase system and intel thetered temp cwm install UL-K012-WW-12.8.1.26-user.zip
b0by said:
In lillipop i got major laggs and baterry drained more than 50% over night in standby mode.
So I downgrade to latest kitkat WW_V11.2.3.33 from asus site, using fastboot and intel temporary cwm recovery.
It works great but now ifwi is 64.33 from lollipop, not 64.25 from kitkat.
It seems there is an OTA update WW_V11.2.3.34 but I dont get notification for download.
Is there any way to downgrade ifwi version?
Or do I have to ask here someone for capture the WW_V11.2.3.34 OTA update from /cache and upload here?
Or is there any fix for lillipop horrible lag (2-3 secs after presing or swiping) and masive battery drain? I tried factory reset lollipop and even reinstall with fastboot erase system and intel thetered temp cwm install UL-K012-WW-12.8.1.26-user.zip
Click to expand...
Click to collapse
For some reasons, i too didn't get that update! I am also in 11.2.3.33 I flashed the device 4 times just to get this update but didn't!
b0by said:
In lillipop i got major laggs and baterry drained more than 50% over night in standby mode.
So I downgrade to latest kitkat WW_V11.2.3.33 from asus site, using fastboot and intel temporary cwm recovery.
It works great but now ifwi is 64.33 from lollipop, not 64.25 from kitkat.
It seems there is an OTA update WW_V11.2.3.34 but I dont get notification for download.
Is there any way to downgrade ifwi version?
Or do I have to ask here someone for capture the WW_V11.2.3.34 OTA update from /cache and upload here?
Or is there any fix for lillipop horrible lag (2-3 secs after presing or swiping) and masive battery drain? I tried factory reset lollipop and even reinstall with fastboot erase system and intel thetered temp cwm install UL-K012-WW-12.8.1.26-user.zip
Click to expand...
Click to collapse
Hello! Ifwi is easy! Take the KitKat Firmware and unzip it complitely, so that you have acces to the files of the rom.zip (Firmware)! In the Firmware (1st-Site) is a ifwi.zip! Unzip this ifwi.zip, and take the dnx_fwr.bin (VLC) and the ifwi.bin (VLC) file, and copy it to your adb/fastboot binarys! Then go to fastboot-mode and First: fastboot flash dnx dnx_fwr.bin, when its done, Second: fastboot flash ifwi ifwi.bin, when its done, reboot bootloader, and check ifwi-version! Should be the version you have flashed!
But do it in your own! Im not responsebile for failure or brick!
Bluetooth permission to receive apk
hi
i cant underestand English very well but i have question
i have asus fonepad 7 fe 170 cg kitkat and i rooted this but i cant receive .apk with Bluetooth for this reason i installed xposed and i downloaded Bluetooth ToolKit.apk
whit this program my bluetooth have permission to receive apk but i want to know what file chenged in root divice and in permission that my bluetooth can receive apk
please say me what file chenged???????
Are you getting play store links when you send an .apk file or can't receive files at all??? And i never installed xposed since it has no use for me....
roselanguste said:
Hello! Ifwi is easy! Take the KitKat Firmware and unzip it complitely, so that you have acces to the files of the rom.zip (Firmware)! In the Firmware (1st-Site) is a ifwi.zip! Unzip this ifwi.zip, and take the dnx_fwr.bin (VLC) and the ifwi.bin (VLC) file, and copy it to your adb/fastboot binarys! Then go to fastboot-mode and First: fastboot flash dnx dnx_fwr.bin, when its done, Second: fastboot flash ifwi ifwi.bin, when its done, reboot bootloader, and check ifwi-version! Should be the version you have flashed!
But do it in your own! Im not responsebile for failure or brick!
Click to expand...
Click to collapse
I have 4 .bin files in ifwi.zip:
CLVp_CSAX_FWR_DnX_20.3E.bin
CLVp_CSAX_OS_DnX_20.3E.bin
IFWI_v64.25_CSAX_PROD.bin
signed_CLVP_CSAX_SoftFuseFile.bin
Dont I have to flash them all? or just the ...FWR_DnX.bin and IFWI_v64.24....bin?
My dear friends, please concentrate on getting Clockworkmod and Cyanogenmod... I am trying real hard here. I contacted all the devs i could, none willing to help me! No device & vendor tree, Locked bootloader, No custom recovery, No stable ROM...... Really feeling so down
OK! You have Four ifwi-Files, Yes then Flash them All!
Expecting some help over here!!! Support me for creating device and vendor trees........
Downgrade IFWI version!
roselanguste said:
Hello! Ifwi is easy! Take the KitKat Firmware and unzip it complitely, so that you have acces to the files of the rom.zip (Firmware)! In the Firmware (1st-Site) is a ifwi.zip! Unzip this ifwi.zip, and take the dnx_fwr.bin (VLC) and the ifwi.bin (VLC) file, and copy it to your adb/fastboot binarys! Then go to fastboot-mode and First: fastboot flash dnx dnx_fwr.bin, when its done, Second: fastboot flash ifwi ifwi.bin, when its done, reboot bootloader, and check ifwi-version! Should be the version you have flashed!
But do it in your own! Im not responsebile for failure or brick!
Click to expand...
Click to collapse
Hello, i tried to downgrade IFWI version by following your method... Everything flashed successfully but the version number stays the same! For eg. if i flash version 64.25, it still stays the 64.33 version of Lollipop firmware only!!! Do you know why???
irfanjunaid said:
Hello, i tried to downgrade IFWI version by following your method... Everything flashed successfully but the version number stays the same! For eg. if i flash version 64.25, it still stays the 64.33 version of Lollipop firmware only!!! Do you know why???
Click to expand...
Click to collapse
Hello! Have you more than this two files in your ifwi.zip? In many cases there are more files in ifwi.zip! Unzip the ifwi.zip and flash all files what is in there! Token.files=fastboot flash token filename, dnx.files=fastboot flash dnx filename, and ifwi.files=fastboot flash ifwi filename! But i suggest you, when you not need this ifwi/dnx for anything, then you should stay on the newer ifwi?! ifwi is BIOS for Intel Phones! So you have KitKat with the newer BIOS-update from Lollipop! Its like a BIOS-update for PC!
Ever since i flashed that Lollipop 64.33 IFWI, i didn't get access to the 11.2.3.34 update at all! So, do you think this IFWI version is problem or Asus pulled that firmware from its servers???
@irfanjunaid , Hello sir.
I just got Asus model: k012 Stuck on logo.
Now i am downloading all the firmwares u mentioned in the OP, but one question .. Did u flash them via stock recovery or u flashed the temporary cwm recovery available .
Sobaro said:
@irfanjunaid , Hello sir.
I just got Asus model: k012 Stuck on logo.
Now i am downloading all the firmwares u mentioned in the OP, but one question .. Did u flash them via stock recovery or u flashed the temporary cwm recovery available .
Click to expand...
Click to collapse
Always flash Stock ROM via stock recovery.... I did via stock recovery... But don't forget, rename the downloaded zip file to k012_sdupdate.zip and put it into a clean formatted SD card. Now press volume up + Power button until you see Asus logo. Now choose Recovery. Now your tab boots to recovery, installs firmware and reboots itself.... Note: No downgrade possible, cannot change SKU(WW-CN etc.....)
I get stuck at the Asus Logo after intel splash.... with a spinning wheel that keeps on going and going and going.... I have download the files you mentioned above, put them on SD card but cannot boot into droidboot, it goes back to main screen. When I select Recovery, it runs about 5 seconds and gives error and then restarts. What seems to be the problem here?
Thanks!
Jabbacks said:
I get stuck at the Asus Logo after intel splash.... with a spinning wheel that keeps on going and going and going.... I have download the files you mentioned above, put them on SD card but cannot boot into droidboot, it goes back to main screen. When I select Recovery, it runs about 5 seconds and gives error and then restarts. What seems to be the problem here?
Thanks!
Click to expand...
Click to collapse
What version of firmware are you in now? Is it rooted? Did you try a factory reset? After factory reset allow tab to take some time to boot up... After that go developer settings -> turn ON usb debugging... Now in PC, run adb via commandline and run adb reboot bootloader... Now see if it goes to droidboot...
This is what I find in bootloader mode. Why can't it go in to droidboot?
IFWI Version: 64.25
SERIAL: E60KBC383526
DROIDBOOT VERSION: TW_FONEPAD-11.2.3.18.2-20141022
PRODUCT: K012
Following Firmwares:
UL-K012-WW-11.2.3.18.2-user.zip
UL-K012-WW-11.2.3.33-user.zip
I tried the old version but to no avail. Also the latest!
Thanks!
Jabbacks said:
This is what I find in bootloader mode. Why can't it go in to droidboot?
IFWI Version: 64.25
SERIAL: E60KBC383526
DROIDBOOT VERSION: TW_FONEPAD-11.2.3.18.2-20141022
PRODUCT: K012
Following Firmwares:
UL-K012-WW-11.2.3.18.2-user.zip
UL-K012-WW-11.2.3.33-user.zip
I tried the old version but to no avail. Also the latest!
Thanks!
Click to expand...
Click to collapse
This is the droidboot.... You can now connect your tab to PC and issue fastboot commands to it.... For example: Fastboot erase cache
But for heaven's sake please don't install lollipop update.....
Now try this: Fastboot erase cache
Fastboot erase userdata
Now choose reboot....
See if it boots up....
Hi folks ! i have read a lot but getting confused somehow. Can anyone tell me or guide how to root my HTC 10 on Nougat ?
Unlock bootloader
Flash latest TWRP
Flash latest SuperSU
Beware Unlocking bootloader resets phone
Make sure to Nandroid backup
Better would be to flash Magisk to obtain systemless MagiskSU. This will keep SafetyNet working which is needed for Apps like Android Pay and so on to run and work. On the other hand you can in addition install some miss without even modifying system which would enable you to just flash stick recovery and install official OTAs as soon as they hit.
Sent from my htc_pmeuhl using XDA Labs
5m4r7ph0n36uru said:
Better would be to flash Magisk to obtain systemless MagiskSU. This will keep SafetyNet working which is needed for Apps like Android Pay and so on to run and work. On the other hand you can in addition install some miss without even modifying system which would enable you to just flash stick recovery and install official OTAs as soon as they hit.
Sent from my htc_pmeuhl using XDA Labs
Click to expand...
Click to collapse
Can you provide me a link which can help ? i heard TWRP is not available for nougat . Also, for doing this Bootloader should be unlocked ? i got too many question . Can i flash mods if i get magisk root ?
rajkatiyar07 said:
Can you provide me a link which can help ? i heard TWRP is not available for nougat . Also, for doing this Bootloader should be unlocked ? i got too many question . Can i flash mods if i get magisk root ?
Click to expand...
Click to collapse
Bootloader needs to be unlocked. TWRP is compatible to Nougat - see TWRP thread. Latest Magisk can be found in the Magisk forum. Yes you can flash mods and install root Apps if you flash Magisk as it will flash MagiskSU as well.
All can be found in the respective threads, named above.
Sent from my htc_pmeuhl using XDA Labs
ordeniz said:
Unlock bootloader
Flash latest TWRP
Flash latest SuperSU
Beware Unlocking bootloader resets phone
Make sure to Nandroid backup
Click to expand...
Click to collapse
Flashed latest TWRP, but it won't boot into TWRP. Tried about 15 different TWRP versions, no luck. Any ideas?
TK3950 said:
Flashed latest TWRP, but it won't boot into TWRP. Tried about 15 different TWRP versions, no luck. Any ideas?
Click to expand...
Click to collapse
Detail your steps, please. Exactly what TWRP version are you trying to flash, and where did you get the TWRP (link to it)? Did you check the MD5 hash of the TWRP you flashed? https://twrp.me/, besides supplying all the official versions of TWRP for the HTC 10 "pme", also gives a link to the MD5 hash of each version in small print on the Download page for the version you choose "md5 for twrp-3.2.1-2-pme.img".
How are you trying to get into TWRP once you flash it? On the 10, after holding the Volume Down and Power buttons to boot into Download mode, choose "reboot to bootloader", then from the bootloader choose "boot to recovery mode".
I haven't been on Nougat since 8.0 came out so I can't personally test the latest TWRP with it, but if there's any problem with the latest versions with Nougat I'm sure it'd be mentioned in the TWRP thread here in the HTC 10 Development section. Have you asked about this issue there?
roirraW "edor" ehT said:
Detail your steps, please. Exactly what TWRP version are you trying to flash, and where did you get the TWRP (link to it)? Did you check the MD5 hash of the TWRP you flashed? https://twrp.me/, besides supplying all the official versions of TWRP for the HTC 10 "pme", also gives a link to the MD5 hash of each version in small print on the Download page for the version you choose "md5 for twrp-3.2.1-2-pme.img".
How are you trying to get into TWRP once you flash it? On the 10, after holding the Volume Down and Power buttons to boot into Download mode, choose "reboot to bootloader", then from the bootloader choose "boot to recovery mode".
I haven't been on Nougat since 8.0 came out so I can't personally test the latest TWRP with it, but if there's any problem with the latest versions with Nougat I'm sure it'd be mentioned in the TWRP thread here in the HTC 10 Development section. Have you asked about this issue there?
Click to expand...
Click to collapse
Hey, thanks for the quick reply mate.
Bootloader unlocked through the HTCDev site instructions. DL mode shows device unlocked, software modified, and S-On. SD Card is inserted. Fastboot in download mode to flash every .img listed on twrp and all .img files from the unofficial list. Didn't check the MD5's, thought it was pretty unlikely that all failed, but I'll try that when I'm out of work. Attempting to flash from Download Mode, using "fastboot flash recovery twrp***.img", *** changing per version. From bootloader mode, when I choose "Boot to recovery mode", I get the HTC logo + red disclaimer, then a reboot, more HTC logo + red disclaimer, then back into bootloader mode. Google searches have suggested using unofficial TWRP 3.0.3-6 or 3.0.3-9, but these files are nowhere to be found anymore. DL links here on xda seem to have been removed. 3.0.3-10 and -11 produce the same error as all other .img files. I've tried this on a machine at home and a machine at my job, so that's two different networks as well.
As a secondary, I've also tried "fastboot erase recovery" a few times before flashing TWRP images, same result.
Edit (2/3/18 @ 16:01): Verified the MD5 hashes, everything has downloaded correctly. Even if anyone has a copy of the 3.0.3-6 or -9 .img files, I'd be willing to try those out too.
TK3950 said:
Hey, thanks for the quick reply mate.
Bootloader unlocked through the HTCDev site instructions. DL mode shows device unlocked, software modified, and S-On. SD Card is inserted. Fastboot in download mode to flash every .img listed on twrp and all .img files from the unofficial list. Didn't check the MD5's, thought it was pretty unlikely that all failed, but I'll try that when I'm out of work. Attempting to flash from Download Mode, using "fastboot flash recovery twrp***.img", *** changing per version. From bootloader mode, when I choose "Boot to recovery mode", I get the HTC logo + red disclaimer, then a reboot, more HTC logo + red disclaimer, then back into bootloader mode. Google searches have suggested using unofficial TWRP 3.0.3-6 or 3.0.3-9, but these files are nowhere to be found anymore. DL links here on xda seem to have been removed. 3.0.3-10 and -11 produce the same error as all other .img files. I've tried this on a machine at home and a machine at my job, so that's two different networks as well.
As a secondary, I've also tried "fastboot erase recovery" a few times before flashing TWRP images, same result.
Click to expand...
Click to collapse
EDITING---
santod040 said:
EDITING---
Click to expand...
Click to collapse
Any news mate? Being able to root this phone was a major condition when I bought it.
I had trouble updating my Honor 6X (BLN-L21) after I rooted it, so I searched the whole xda to gain some information. Finally I made it, so I thought I could share this information with you guys, hope it helps, but I do not take responsibility if not, as you may have already heard, the Honor 6X (like every Kirin device) is very easy to brick.
- If everything is gone alright you should keep all of your data, apps and settings.
- If there is a big update, like from MM to N you maybe should backup all your stuff and relock the bootloader to update (big updates can relock frp so you can't unlock your bootloader then a rollback is the only way.
Successfully tried from:
B360 to B365
B365 to B367
Short Version (for expert users):
1. uninstall busybox bynaries and the Xposed Framework
2. uninstall magisk (inside the app)
3. flash stock recovery.img (of your actual firmware)
4. flash stock boot.img (of your actual firmware)
5. make OTA update (Reminder: safe update file)
6. flash twrp again and root
7. you are all done
Detailed Version:
#cmd commands#
1. backup your system over TWRP #adb reboot recovery# and do a backup there (for safety reasons)
2. #fastboot reboot#
3. uninstall busybox bynaries and the Xposed Framework(not just the app) (if you have it)
4. uninstall magisk (in app over "complete Uninstall button")
5. restart to bootloader #adb reboot bootloader#
6. flash stock recovery #fastboot flash recovery recovery.img# [use the recovery out of your actual firmware, how to extract is explained in the Forum I added at the end
7. flash stock boot #fastboot flash boot boot.img# [also use the extracted version of your actual package]
8. #fastboot reboot#
9. download update over OTA Update app (System update) in stock system. -> If the "System updater" app does not provide a Full version of the update package, the update could get stopped at 8% saying it could not verify the update, if so, just take the step to the error and reboot, if you then search for an update again, the "System updater" should now show you a Full version of the update package. like "BLN-L21C432B365-FULL"
10. you should safe that update files out of the HwOUC folder, so you can extract the recovery.img and boot.img later before you restart your device to do the update, because the system deletes these files after successful update
11. update over OTA Update app (System update) in stock system
12. restart to bootloader (#adb restart bootloader#)
13. flash twrp again #fastboot flash recovery twrp-3.1.1-0-berlin.img# [use the OpenKirin twrp edition (the official leads to a bootloop] -> [url]https://forum.xda-developers.com/honor-6x/development/twrp-t3583413[/URL]
14. Important is not to boot to system after flashing TWRP, exactly like as you installed it the first time. So you do #fastboot reboot# and then Vol down + lock
15. backup your system over TWRP (for safety reasons)
16. #adb reboot recovery#
17. flash Magisk zip in TWRP again
18. reboot in twrp
19. you are ready to go with the latest stock rom
How to extract boot.img and recovery.img out of your actual firmware is explained here:
[url]https://forum.xda-developers.com/honor-6x/how-to/extract-stock-recovery-img-boot-img-img-t3676880[/URL] thanks @Khan ubaid
citizenserious said:
the Honor 6X is very easy to brick.
Click to expand...
Click to collapse
Not just the 6X but every Kirin device.
This work only with packages like "xxxB360-FULL" or even with smaller downloaded packages that just updates some files? And, if I choose to do this with the FULL package do i have to re modify all the settings that i use actually?
RedSkull23 said:
This work only with packages like "xxxB360-FULL" or even with smaller downloaded packages that just updates some files? And, if I choose to do this with the FULL package do i have to re modify all the settings that i use actually?
Click to expand...
Click to collapse
I already tried it with the FULL package (edited the Guide btw.) you keep all your settings and stuff like before.
If it doesn't show you the FULL package just try the update until it fails, the system than will show you a FULL version of the update after the restart and research. That worked for me so far.
Hope I could help
citizenserious said:
I already tried it with the FULL package (edited the Guide btw.) you keep all your settings and stuff like before.
If it doesn't show you the FULL package just try the update until it fails, the system than will show you a FULL version of the update after the restart and research. That worked for me so far.
Hope I could help
Click to expand...
Click to collapse
What a nice notice, thanks dude! I already own the FULL, i only was worried about the fact that i could lose my data with the FULL one, i waa seeing it a clean firmware install but after this i can go straight with the update. I'll do that later today
RedSkull23 said:
What a nice notice, thanks dude! I already own the FULL, i only was worried about the fact that i could lose my data with the FULL one, i waa seeing it a clean firmware install but after this i can go straight with the update. I'll do that later today
Click to expand...
Click to collapse
I have done it that way yesterday, from B365 to B367 with the FULL package.
But nevertheless please back up your data.
edit: please let us know if it worked for you too
Thank for this guide. I might use this when an update comes.
[email protected] said:
Click to expand...
Click to collapse
What's the matter?
citizenserious said:
I have done it that way yesterday, from B365 to B367 with the FULL package.
But nevertheless please back up your data.
edit: please let us know if it worked for you too
Click to expand...
Click to collapse
Finally i found some time to dedicate on updating my phone, and I'm happy to say that it worked. I made from B360 to B365 and from B365 to B367, both worked at first shot. The only thing that i just can't understand is why the OTA package downloaded yesterday worked immediately, while the same B365-FULL package downloaded a month ago, copied on PC before starting it and later started didn't. With stock recovery and boot images obviously. I tried to start it later but nothing, i tried dload method with the update.app but neither that worked. Probably the OTA downloaded creates a sort of signature that can't be recreated that easily, if the same package fails through dload method... But what matters most is that now I'm on B367, protected with the latest security patch. Sorry for the late answer, time is hard to find... Thanks
Hi
Can someone upload the boot.img and and recovery.img from B367
Thanks in advance
Archerous said:
Hi
Can someone upload the boot.img and and recovery.img from B367
Thanks in advance
Click to expand...
Click to collapse
B367 of which model BLN-LXXCXXX?
shashank1320 said:
B367 of which model BLN-LXXCXXX?
Click to expand...
Click to collapse
I forgot sorry
BLN-L21C432B367
Archerous said:
I forgot sorry
BLN-L21C432B367
Click to expand...
Click to collapse
Check repository thread. Redskull23 has updated there. You may find in OP also in that thread. Link to the thread in my signature
shashank1320 said:
Check repository thread. Redskull23 has updated there. You may find in OP also in that thread. Link to the thread in my signature
Click to expand...
Click to collapse
There is no B367 in the Repository,no boot.img or recovery. thanks for you help
I wait for the next update,and i will not forget to save the update.app to pc. And extract the files
Archerous said:
There is no B367 in the Repository,no boot.img or recovery. thanks for you help
I wait for the next update,and i will not forget to save the update.app to pc. And extract the files
Click to expand...
Click to collapse
@RedSkull23, please see bro. You have updated to this and may be able to share :good:
shashank1320 said:
@RedSkull23, please see bro. You have updated to this and may be able to share :good:
Click to expand...
Click to collapse
I share ist,with the next update :good:
shashank1320 said:
@RedSkull23, please see bro. You have updated to this and may be able to share :good:
Click to expand...
Click to collapse
If we find the B367 package I'll upload everything from it!
I was on rooted BLN-L24C5678B360, and I want to take the OTA 365, so I flashed stock recovery and boot, reboot into system and started the update, but it failed, afterwards the phone stuck at booting up screen.
I have to boot into fastboot and run "fastboot oem relock [my unlock code]" to relock it, then followed by a factory reset. But when it comes to update, it failed again. Upon reboot, it stuck again with the message "Your device has failed verification and may not work properly."
What did I do wrong?
Update: recovered with the official rollback software to 6.0.
shadowcliffs said:
I was on rooted BLN-L24C5678B360, and I want to take the OTA 365, so I flashed stock recovery and boot, reboot into system and started the update, but it failed, afterwards the phone stuck at booting up screen.
I have to boot into fastboot and run "fastboot oem relock [my unlock code]" to relock it, then followed by a factory reset. But when it comes to update, it failed again. Upon reboot, it stuck again with the message "Your device has failed verification and may not work properly."
What did I do wrong?
Click to expand...
Click to collapse
You can try full firmware for b365 if available via dload.
Unlock your bootloader and it will boot to twrp and then boot normally.
Hi.
I rooted my M2 10 Wifi (A01W) with Kingroot and apparently now it's unroot (Magisk Manager said that). Even I made a factory reset.
I have the _B007 version and when I try to upgrade via OTA to _B008, it always fail and show "Failed to check the update files. Please download the package again".
I've working with ADB, Fastboot... and I could see that it's unroot, but the Bootloader is Unlock and I can't Relock it. Maybe it's the reason because the OTA doesn't work.
So I got a fastboot code with DC-UNLOCKER and tried to relock (fastboot oem relock CODE) and the answer was:
FAILED (Remote: root type is risk)
If I execute "fastboot oem check-rootinfo":
old_stat: RISK
now_stat: RISK
change_time: xxxxxxxxx
Apparently, the Recovery is stock, with EMUI logo showing 3 options:
Reboot, Wipedata/factory reset and Wipe chache partition
I made the factory reset that way.
Any idea? Thanks.
ma2crmam said:
Hi.
I rooted my M2 10 Wifi (A01W) with Kingroot and apparently now it's unroot (Magisk Manager said that). Even I made a factory reset.
I have the _B007 version and when I try to upgrade via OTA to _B008, it always fail and show "Failed to check the update files. Please download the package again".
I've working with ADB, Fastboot... and I could see that it's unroot, but the Bootloader is Unlock and I can't Relock it. Maybe it's the reason because the OTA doesn't work.
So I got a fastboot code with DC-UNLOCKER and tried to relock (fastboot oem relock CODE) and the answer was:
FAILED (Remote: root type is risk)
If I execute "fastboot oem check-rootinfo":
old_stat: RISK
now_stat: RISK
change_time: xxxxxxxxx
Apparently, the Recovery is stock, with EMUI logo showing 3 options:
Reboot, Wipedata/factory reset and Wipe chache partition
I made the factory reset that way.
Any idea? Thanks.
Click to expand...
Click to collapse
Well, I've read that flashing a system.img extracted from the UPDATE.APP I would can restore the Stock ROM... but I don't find a complete Stock ROM for Mediapad M2 10 Wifi (A01W).
I found the OTA in Romfirmware or Fordroid (sorry, I'm new user and I can not post external links). With this I can flash BOOT.img and RECOVERY.img, but the problem persist.
Does someone has any idea... or where can I get the complete Stock ROM?
Thanks!!!
ma2crmam said:
Well, I've read that flashing a system.img extracted from the UPDATE.APP I would can restore the Stock ROM... but I don't find a complete Stock ROM for Mediapad M2 10 Wifi (A01W).
I found the OTA in Romfirmware or Fordroid (sorry, I'm new user and I can not post external links). With this I can flash BOOT.img and RECOVERY.img, but the problem persist.
Does someone has any idea... or where can I get the complete Stock ROM?
Thanks!!!
Click to expand...
Click to collapse
Stokk ROM maybe available through a paid service by easy firmware. Got my LTE Stock ROM frim there. For the Wi-Fi edition you could first take a look here.
Sent from my HTC U11 using XDA Labs
5m4r7ph0n36uru said:
Stokk ROM maybe available through a paid service by easy firmware. Got my LTE Stock ROM frim there. For the Wi-Fi edition you could first take a look here.
Sent from my HTC U11 using XDA Labs
Click to expand...
Click to collapse
Thanks!!! I didn't know that page. It's fine and does not look very expensive.
Just one more doubt.
The firmaware I need (as read on the tablet) is M2-A01w...B008 for West Europe
The firmware that the page shows is M2-A01w...B008CUSTC100D001
Do you know what CUSTC100D001 mean? Could I used it without problems?
ma2crmam said:
Thanks!!! I didn't know that page. It's fine and does not look very expensive.
Just one more doubt.
The firmaware I need (as read on the tablet) is M2-A01w...B008 for West Europe
The firmware that the page shows is M2-A01w...B008CUSTC100D001
Do you know what CUSTC100D001 mean? Could I used it without problems?
Click to expand...
Click to collapse
Glad it helped and yes it is not so expensive regarding the fact that there are all sorts of official firmware (mostly leaked ones) available for a lot of manufacturers.
The CUST reference at the end if the firmware version can be found in settings > about the tablet in the very last line. Mine is in German, So translated this line would state something like adapted/customized version. D001 is definitely Western Europe,this should be fine.
If not familiar how to install it google or search the forum for dload method. It will tell you what to do.
Sent from my HTC U11 using XDA Labs
I've done:
1. Get the correct firmware (version ...B007) and extract the RECOVERY.IMG and UPDATE.APP.
2. Flash the RECOVERY with Fastboot and install the UPDATE with the "dload" in the SD.
3. Reboot in RECOVERY MODE, wipe all and restore factory settings.
4. Then, the tablet was updated via OTA to the ...B008 version.
Then, positive:
1. The OTA works fine.
2. I was abble to install the Nextlix App and the HBO Spain App plays videos. Both didn't work before.
3. If I execute "fastboot oem check-rootinfo":
old_stat: RISK
now_stat: SAFE
Then, negative:
1. I can't relock the Bootloader yet. When I try to relock (fastboot oem relock CODE) and the answer was again: FAILED (Remote: root type is risk)
Well, for normal use that's enough, but... THE RELOCK is becoming personal!!!
Hi,
I have a Samsung A32 SM-A325F and the bootloader is not unlocked.
The device was running Android 12 and i decided to update to Android 13 via OTA update; so i downloaded the OTA update and clicked 'install', then the device rebooted trying to apply that update but something went wrong and now the device is in bootloop, recovery and download mode are both accessible.
I already tried to download various firmwares (Android 12 and 13).
I tried to flash these firmwares both ways through SD Card and Odin (As Admin) and all flashed successfully but nothing changed, still in bootloop.
It's important for me to don't erase DATA (I flashed the firmwares with HOME_CSS and not the stock CSS, so DATA wouldn't be formatted)!
If someone knows how to fix this i would appreciate a comment,
Thanks.
Quark Thonos said:
Hi,
I have a Samsung A32 SM-A325F and the bootloader is not unlocked.
The device was running Android 12 and i decided to update to Android 13 via OTA update; so i downloaded the OTA update and clicked 'install', then the device rebooted trying to apply that update but something went wrong and now the device is in bootloop, recovery and download mode are both accessible.
I already tried to download various firmwares (Android 12 and 13).
I tried to flash these firmwares both ways through SD Card and Odin (As Admin) and all flashed successfully but nothing changed, still in bootloop.
It's important for me to don't erase DATA (I flashed the firmwares with HOME_CSS and not the stock CSS, so DATA wouldn't be formatted)!
If someone knows how to fix this i would appreciate a comment,
Thanks.
Click to expand...
Click to collapse
there's no way to solve it without wiping /data or taking to samsung
i think the only way you could solve it is by NAND Erasing and repartitioning the phone using a .pit file, but afaik that uses odim...
applesucksLmao said:
there's no way to solve it without wiping /data or taking to samsung
i think the only way you could solve it is by NAND Erasing and repartitioning the phone using a .pit file, but afaik that uses odim...
Click to expand...
Click to collapse
I double that. Only complete re-flashing. Here are the instructions. And here you can download the full stock firmware.
Ok,
Thank you.
Quark Thonos said:
Hi,
I have a Samsung A32 SM-A325F and the bootloader is not unlocked.
The device was running Android 12 and i decided to update to Android 13 via OTA update; so i downloaded the OTA update and clicked 'install', then the device rebooted trying to apply that update but something went wrong and now the device is in bootloop, recovery and download mode are both accessible.
I already tried to download various firmwares (Android 12 and 13).
I tried to flash these firmwares both ways through SD Card and Odin (As Admin) and all flashed successfully but nothing changed, still in bootloop.
It's important for me to don't erase DATA (I flashed the firmwares with HOME_CSS and not the stock CSS, so DATA wouldn't be formatted)!
If someone knows how to fix this i would appreciate a comment,
Thanks.
Click to expand...
Click to collapse
After downgrading android or any firmware is mandatory a format of the /data filesystem, otherwise, bootloop will happen. Maybe try setting up adb and pulling your files via the recovery mode.
Quark Thonos said:
Hi,
I have a Samsung A32 SM-A325F and the bootloader is not unlocked.
The device was running Android 12 and i decided to update to Android 13 via OTA update; so i downloaded the OTA update and clicked 'install', then the device rebooted trying to apply that update but something went wrong and now the device is in bootloop, recovery and download mode are both accessible.
I already tried to download various firmwares (Android 12 and 13).
I tried to flash these firmwares both ways through SD Card and Odin (As Admin) and all flashed successfully but nothing changed, still in bootloop.
It's important for me to don't erase DATA (I flashed the firmwares with HOME_CSS and not the stock CSS, so DATA wouldn't be formatted)!
If someone knows how to fix this i would appreciate a comment,
Thanks.
Click to expand...
Click to collapse
Flash your device using SP flash tool.
Please make a scatter firmware first using the odin files and then flash the phone in BROM mode.