Hello, i have ZTE axon 7 ZTE A2017G model. When i bought it from china, via allieexpress, it was on stock 4.0 mifavor chinese version. It was not updating to the latest nougat. I tried updating manually via recovery mode through SD card. I was succesful to update it to 7.1.1 nougat. Unfortunately my Mobile network became completely disabled. I understand that i used an incorrect firmware. Current build number: ZTE A2017GV1.2.0B05. How and what should i do in order to restore my mobile network. I am currently living in UK. Should i completly hard reset, install chinese or Eu version, i am confused. Anyone can help me with this?
Hi,
Hardwares are different between china and europe model, therefore radio firmwares within the roms also.
I would advise you to flash the latest chinese version of the rom to go back to normal.
However if you have an unlocked bootloader, you can try flashing only the radio modem via adb.
Good luck
Cojy said:
Hi,
Hardwares are different between china and europe model, therefore radio firmwares within the roms also.
I would advise you to flash the latest chinese version of the rom to go back to normal.
However if you have an unlocked bootloader, you can try flashing only the radio modem via adb.
Good luck
Click to expand...
Click to collapse
Thank you. And maybe if you would so kind, any links for the best guide how to flash radio modem via adb?
Cheers
A bit of a late reply, I did not get any notification.
First reboot into fastboot (adb reboot bootloader, the screen ued to display fastboot on my other android phone)
After that it is a 'fastboot flash radio signed_radio.img'
You can flash every .img file that you find in a rom via fastboot (if you have issues with gyroscope, modem, radio...)
here are some common commands:
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash rpm rpm.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
It is usually fastboot flash <component> <component>.img like flash boot boot.img or flash radio radio.img...
Let us know if it solves your issue
Cojy said:
A bit of a late reply, I did not get any notification.
First reboot into fastboot (adb reboot bootloader, the screen ued to display fastboot on my other android phone)
After that it is a 'fastboot flash radio signed_radio.img'
You can flash every .img file that you find in a rom via fastboot (if you have issues with gyroscope, modem, radio...)
here are some common commands:
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash rpm rpm.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
It is usually fastboot flash <component> <component>.img like flash boot boot.img or flash radio radio.img...
Let us know if it solves your issue
Click to expand...
Click to collapse
Thanks for the reply.
Unfotrunately, i am completely new to this kind of thing. I managed to reboot into fastboot. But now im not sure what to do. Do i just put in commands? Do i need to download the radio.img files or? If you would be so kind to provide a bit more detail to this.
Thanks again
Fruktoze said:
Thanks for the reply.
Unfotrunately, i am completely new to this kind of thing. I managed to reboot into fastboot. But now im not sure what to do. Do i just put in commands? Do i need to download the radio.img files or? If you would be so kind to provide a bit more detail to this.
Thanks again
Click to expand...
Click to collapse
The usual saying is don't do that if you don't know what you are doing ! This could block your phone and you would have a hard time restoring it if you are not at ease with that sort of things.
This being said, you need to retrieve the .img file from your operating system image, put it in your adb folder (or whatever folder but you will have to add the path) and run the aforesaid commands.
Related
I managed to soft brick my Storm with one of the CM13 updates (both normal boot and recovery just resulted in a black flickering screen), it seems others are having similar issues so here are instructions for restoring your phone to the stock image, this fixed the brick for me.
You need fastboot so download and install the Android SDK if not already present: http://developer.android.com/sdk/installing/index.html
Download and uncompress the stock Cyanogen OS fastboot zip: https://cyngn.com/support
Boot your phone into fastboot mode, (plug in USB then hold down vol+ and power until rebooted, keep holding vol+ until in fastboot)
Start a shell/command prompt on your computer to execute the commands below.
THIS WILL WIPE EVERYTHING!!! - THIS IS A COMPLETE STOCK RESTORATION!!!
Execute these fastboot commands from within the extracted stock zip directory:
Code:
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot erase DDR
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl1bak sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash tzbak tz.mbn
fastboot flash hyp hyp.mbn
fastboot flash hypbak hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash cache cache.img
fastboot erase splash
fastboot flash splash splash.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
If the cache command gives an error try continuing anyway.
If you want to try to save your user data skip the userdata command, but no guarantees.
Search the other threads on XDA for instructions on booting or flashing custom recoveries, ROMs, root etc.
I've also bricked my Storm with cm13 update in January . I flashed every img using fastboot and it recovered. i skipped the other files and it still works. Good that someone written tutorial for others. I was planning to write it by myself but you were faster
I have made a simple batch script that executes the commands by itself. You need to unzip and place these 2 files into images direction. It should look like this:
View attachment 3656958
Click on picture to make it bigger
then just connect your device in fastboot mode and open the FLASH-ALL.bat file. Press enter. It will flash all the images. IT WILL ONLY WORK IF FILES WILL BE PLACED LIKE ON THE SCREENSHOT!!
I got blinking brick. I can not go into fastboot
@up Don't connect the usb cord. While it's blinking press and hold vol up+ power for 10 seconds, release power button and it should go into fastboot.
If no, let it fully discharge, and then try volup + power
95% of the time flashing system should do the trick. Otherwise the flashall argument should save you a lot of typing.
aciupapa said:
I've also bricked my Storm with cm13 update in January . I flashed every img using fastboot and it recovered. i skipped the other files and it still works. Good that someone written tutorial for others. I was planning to write it by myself but you were faster
Click to expand...
Click to collapse
my storm is dead, i cant get into recovery or download mode....any advice...i did get it rooted and the recovery...i flash the cm 13 kipper and it went dead...red light comes on when charging or usb connection.
miSAKe said:
I managed to soft brick my Storm with one of the CM13 updates (both normal boot and recovery just resulted in a black flickering screen), it seems others are having similar issues so here are instructions for restoring your phone to the stock image, this fixed the brick for me.
You need fastboot so download and install the Android SDK if not already present: http://developer.android.com/sdk/installing/index.html
Download and uncompress the stock Cyanogen OS fastboot zip: https://cyngn.com/support
Boot your phone into fastboot mode, (plug in USB then hold down vol+ and power until rebooted, keep holding vol+ until in fastboot)
Start a shell/command prompt on your computer to execute the commands below.
THIS WILL WIPE EVERYTHING!!! - THIS IS A COMPLETE STOCK RESTORATION!!!
Execute these fastboot commands from within the extracted stock zip directory:
Code:
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot erase DDR
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl1bak sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash tzbak tz.mbn
fastboot flash hyp hyp.mbn
fastboot flash hypbak hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash cache cache.img
fastboot erase splash
fastboot flash splash splash.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
If the cache command gives an error try continuing anyway.
If you want to try to save your user data skip the userdata command, but no guarantees.
Search the other threads on XDA for instructions on booting or flashing custom recoveries, ROMs, root etc.
Click to expand...
Click to collapse
Perfect, thanks.
Would have worked FIRST time if I'd read your instructions properly, instead it worked the SECOND time. Important to download "the stock Cyanogen OS fastboot zip" from the Cyngn support page - there are two similar looking files and obviously I picked the wrong one first.
Thanks again.
miSAKe said:
Hello,
As you know, cyngn.com is unavailable. i need kipper files, specially original recovery.img
do you know any alive link(s)? or can you upload/send to me?
thanks very much
Click to expand...
Click to collapse
ftabashir said:
miSAKe said:
Hello,
As you know, cyngn.com is unavailable. i need kipper files, specially original recovery.img
do you know any alive link(s)? or can you upload/send to me?
thanks very much
Click to expand...
Click to collapse
here
https://www.androidfilehost.com/?w=files&flid=59917
Click to expand...
Click to collapse
ghertas said:
ftabashir said:
here
https://www.androidfilehost.com/?w=files&flid=59917
Click to expand...
Click to collapse
thanks. but this is the whole ROM. i downloaded it and couldn't find "recovery.img". how can i find original recovery for kipper (wileyfox storm)?
Click to expand...
Click to collapse
ftabashir said:
ghertas said:
thanks. but this is the whole ROM. i downloaded it and couldn't find "recovery.img". how can i find original recovery for kipper (wileyfox storm)?
Click to expand...
Click to collapse
cm-13.1.2
instal via ADB Fastboot
youtube help you to how instal
recovery.
https://www.androidfilehost.com/?fid=24727376692773052
full rom
https://www.androidfilehost.com/?fid=24727369092694607
Click to expand...
Click to collapse
ghertas said:
ftabashir said:
cm-13.1.2
instal via ADB Fastboot
youtube help you to how instal
recovery.
https://www.androidfilehost.com/?fid=24727376692773052
full rom
https://www.androidfilehost.com/?fid=24727369092694607
Click to expand...
Click to collapse
Thanks. but I downloaded recovery from this link.
Then i tried to run "fastboot flash recovery cm-13.1.2-ZNH2KAS3NA-kipper-boot-debuggable-6c1a30b194.img"
but it said:
OEM locked device can't boot unsigned image. Do you want to continue?
Yes
No
I pressed no and it said:
target reported max download size of 268435456 bytes
sending 'recovery' (20866 KB)...
OKAY [ 0.791s]
writing 'recovery'...
FAILED (remote: Image could brick the device. Flashing canceled.)
finished. total time: 2.129s
I ran the command again and this time I chose Yes and it said:
target reported max download size of 268435456 bytes
sending 'recovery' (20866 KB)...
OKAY [ 0.783s]
writing 'recovery'...
OKAY [ 16.962s]
finished. total time: 17.751s
but as it said, when i try to boot recovery i saw this message: OEM locked device can't boot unsigned image. oem unlock or flash signed boot image.
I need a signed recovery, but i couldn't find such recovery anywher. Please help me
Also when i try to run fastboot oem unlock it says that: FAILED (remote: oem unlock is not allowed)
So the only solution would be installing a signed recovery.
Note: 3day ago i installed a custom recovery without oem unlock. now my device stops at boot animation and i cant boot into android. also i can't boot into recovery because oem is locked and recovery is not signed. I need a signed recovery.
Click to expand...
Click to collapse
miSAKe said:
I managed to soft brick my Storm with one of the CM13 updates (both normal boot and recovery just resulted in a black flickering screen), it seems others are having similar issues so here are instructions for restoring your phone to the stock image, this fixed the brick for me.
You need fastboot so download and install the Android SDK if not already present: http://developer.android.com/sdk/installing/index.html
Download and uncompress the stock Cyanogen OS fastboot zip: https://cyngn.com/support
Boot your phone into fastboot mode, (plug in USB then hold down vol+ and power until rebooted, keep holding vol+ until in fastboot)
Start a shell/command prompt on your computer to execute the commands below.
THIS WILL WIPE EVERYTHING!!! - THIS IS A COMPLETE STOCK RESTORATION!!!
Execute these fastboot commands from within the extracted stock zip directory:
Code:
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot erase DDR
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl1bak sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash tzbak tz.mbn
fastboot flash hyp hyp.mbn
fastboot flash hypbak hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash cache cache.img
fastboot erase splash
fastboot flash splash splash.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
If the cache command gives an error try continuing anyway.
If you want to try to save your user data skip the userdata command, but no guarantees.
Search the other threads on XDA for instructions on booting or flashing custom recoveries, ROMs, root etc.
Click to expand...
Click to collapse
How did you enter fastboot without enabling usb debugging/developer option?
Hello,
I rooted my phone from the guidance provided here on XDA and it was very easy.. I unlocked bootlader installed TWRP recovery and now I am using custom roms such as nuclear nougat rom. Now I want to sale my phone and sadly people here in Multan, Pakistan are scared to buy a rooted phone even shops as well. So I thought is there any way to fully unroot and get this device into its stock shape with Cyanogen OS with lollipop , locked bootlader and that normal recovery which is there?
I have searched but no proper way is available, can anyone please guide me step by step or provide me a step by step link.
It would be much appreciated
Try all in one toolkit, flash stock firmware with that, u can also lock bootloader with that
Sent from my ZUK+Z1 using Tapatalk
Nobody wants to buy that phone with cos 12.1 when you can have it with LineageOS 7.1.2:laugh:
Nizamani said:
Try all in one toolkit, flash stock firmware with that, u can also lock bootloader with that
Sent from my ZUK+Z1 using Tapatalk
Click to expand...
Click to collapse
can you please provide a step by step procedure of that? I have never used all in one toolkit
Nizamani said:
Try all in one toolkit, flash stock firmware with that, u can also lock bootloader with that
Sent from my ZUK+Z1 using Tapatalk
Click to expand...
Click to collapse
Shaheer12345 said:
can you please provide a step by step procedure of that? I have never used all in one toolkit
Click to expand...
Click to collapse
strongst said:
Nobody wants to buy that phone with cos 12.1 when you can have it with LineageOS 7.1.2:laugh:
Click to expand...
Click to collapse
That is infact true, phone gets 100 times better in every way but when i posted the ad people were like "there must be something wrong with your phone which you are not mentioning otherwise who roots this phone"
and I was like "to make it bug free and better obviously"
Shaheer12345 said:
Hello,
I rooted my phone from the guidance provided here on XDA and it was very easy.. I unlocked bootlader installed TWRP recovery and now I am using custom roms such as nuclear nougat rom. Now I want to sale my phone and sadly people here in Multan, Pakistan are scared to buy a rooted phone even shops as well. So I thought is there any way to fully unroot and get this device into its stock shape with Cyanogen OS with lollipop , locked bootlader and that normal recovery which is there?
I have searched but no proper way is available, can anyone please guide me step by step or provide me a step by step link.
It would be much appreciated
Click to expand...
Click to collapse
STEPS TO FLASH COS12.1 VIA FASTBOOT
1/ Install zuk drivers & ADB fastboot in pc
2/ Then dwnld cos fastboot 1 (https://www.androidfilehost.com/?fid=673368273298936352)
3/ After dwnld complete , extract cos zip file in adb folder (location must be in c drive )
& Connect phn with pc & reboot to fastboot mode / bootloader
4/ Then type all commands 1 y 1
Commands?
fastboot -i 0x2b4c flash modem NON-HLOS.bin
fastboot -i 0x2b4c flash sbl1 sbl1.mbn
fastboot -i 0x2b4c flash dbi sdi.mbn
fastboot -i 0x2b4c flash aboot emmc_appsboot.mbn
fastboot -i 0x2b4c flash rpm rpm.mbn
fastboot -i 0x2b4c flash splash splash.img
fastboot -i 0x2b4c flash tz tz.mbn
fastboot -i 0x2b4c flash boot boot.img
fastboot -i 0x2b4c flash recovery recovery.img
fastboot -i 0x2b4c flash -S 512M system system.img
fastboot -i 0x2b4c flash cache cache.img
fastboot -i 0x2b4c flash userdata userdata.img
fastboot -i 0x2b4c flash userdata userdata_64G.img
fastboot -i 0x2b4c flash persist persist.img
These codes will bring you back to stock os .
For locking bootloader: fastboot -i 0x2b4c oem lock
Only For X829 owners... 16s stock rom
https://mega.nz/#!ZG4G1YiS!FHW2u7EAwzVkXr1djEJlAaoZxa2AvjkZlakCRuLLmZw
https://drive.google.com/file/d/0B9KXxWUKQWYBaml4aEhFeFV5N2M/view
Extract zip file in adb on your c:/ directory.
Fastboot rom execute Chinese bat file in fastboot mode.
---Instructions---
How to flash it! First flash or boot twrp via fastboot. Do a clean wipes. Reboot into fastboot. Execute the chinese word bat file.
There will be a few error. Missing file. The zip provided was not complete. Missing stock recovery etc. Anyway, it work. For stock recovery here https://forum.xda-developers.com/le-max-2/development/official-lemax2x820x822-t3508823
After finishing youget fully working stock 5.8.16s LEX829.
Also these will change ur device info in fastboot to le_x2_na_oversea
More info >> https://forum.xda-developers.com/showpost.php?p=72708251&postcount=29
If you have problems with bat.. Put all rom files Inside tools file type on cmd as administrator one by one
It may some files missing inside rom... Don't worry
fastboot flash ddr ddr.mbn
fastboot flash dsp adspso.bin
fastboot flash boot boot.img
fastboot flash bluetooth BTFM.bin
fastboot flash cmnlib cmnlib.mbn
fastboot flash cmnlibbak cmnlib.mbn
fastboot flash cmnlib64 cmnlib64.mbn
fastboot flash cmnlib64bak cmnlib64.mbn
fastboot flash devcfg devcfg.mbn
fastboot flash devinfo devinfo.bin
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot flash hyp hyp.mbn
fastboot flash hypbak hyp.mbn
fastboot flash keymaster keymaster.mbn
fastboot flash keymasterbak keymaster.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash pmic pmic.elf
fastboot flash pmicbak pmic.elf
fastboot flash rpm rpm.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash splash splash.img
fastboot flash system system.img
fastboot flash tz tz.mbn
fastboot flash tzbak tz.mbn
fastboot flash xbl xbl.elf
fastboot flash xblbak xbl.elf
fastboot reboot
Hey @CrisBalGreece
Could you give some more specification of the rom?
paxcolo said:
Hey @CrisBalGreece
Could you give some more specification of the rom?
Click to expand...
Click to collapse
Official 16s X829 fastboot rom from US officials forums.
Thank you for posting this man ?
im getting error zipfile is corrupt shuld i download again?
Ok I downloaded it again and it's saying zip file corrupted still
allrockedout said:
im getting error zipfile is corrupt shuld i download again?
Ok I downloaded it again and it's saying zip file corrupted still
Click to expand...
Click to collapse
Check your adb and drivers otherwise go manually one by one. Read OP info. Download it only through pc.
I just got my x829 with a shop rom that does not allow for OTA updates.
Is your stock rom the same one I have on my phone currently?
Please help I know it's not exactly related but I'm getting this in twrp now
I don't understand fastboot and CMD very well
This is to complicated i just want to flash its not working
Here's a log from twrp I'm still getting corrupt zip file error, when trying to flash official x829 zip ?
https://mega.nz/#!dFYVTBYY!NSzhFbQca87Em5XtnQ_-sCKf4FDFwWe0s3avpKkRjKo
Hi
I have x829 and now I'm on 19S indian. But this rom doesn't support polish language and I want back to original 16S from USA.
I do not have TWRP installed, can I rename the file to update.zip and move it to the root directory? Then install from recovery ?
ymmi21 said:
Hi
I have x829 and now I'm on 19S indian. But this rom doesn't support polish language and I want back to original 16S from USA.
I do not have TWRP installed, can I rename the file to update.zip and move it to the root directory? Then install from recovery ?
Click to expand...
Click to collapse
I haven't try that but you can still try it through fastboot commands.
CrisBalGreece said:
Only For X829 owners... 16s stock rom
If you don't know how to flash fastboot rom and make the above just flash this through TWRP
TWRP zip Flashable rom
https://mega.nz/#!ZG4G1YiS!FHW2u7EAwzVkXr1djEJlAaoZxa2AvjkZlakCRuLLmZw
Click to expand...
Click to collapse
I tried this file with renamed to update but after reboot and turn on it to normal recovery I received update field - file incorrect.
Something like that. But I pushed back button and then phone restart normally but on 19S.
Any idea ? How back to 16S without fastboot (now I'm at work) and TWRP ?
ymmi21 said:
I tried this file with renamed to update but after reboot and turn on it to normal recovery I received update field - file incorrect.
Something like that. But I pushed back button and then phone restart normally but on 19S.
Any idea ? How back to 16S without fastboot (now I'm at work) and TWRP ?
Click to expand...
Click to collapse
Yes I was afraid so. Try to contact with your seller or put TWRP and after installation put back the official recovery with the same Way.
Why on web I find only files for x822 and x820 ? Where is a department with the files of rom for USA version X829 ?
ymmi21 said:
Why on web I find only files for x822 and x820 ? Where is a department with the files of rom for USA version X829 ?
Click to expand...
Click to collapse
I don't know. You may ask to moderators to make new threads for x829.
allrockedout said:
Here's a log from twrp I'm still getting corrupt zip file error, when trying to flash official x829 zip
https://mega.nz/#!dFYVTBYY!NSzhFbQca87Em5XtnQ_-sCKf4FDFwWe0s3avpKkRjKo
Click to expand...
Click to collapse
This Logcat is from flashing and backing up Omni rom for max2. That you have or this is the one you try to wipe. Sorry I haven't understood....
Yes I know that I can write to moderators for new threads but for what ? I'm looking this rom on Leeco company site. Not here. (not exactly, this family of xda is big support )
Why do not they have it on their website ? I found only for Chinese and Indian versions, but not for USA (x829).
---------- Post added at 01:57 PM ---------- Previous post was at 01:55 PM ----------
CrisBalGreece said:
I don't know. You may ask to moderators to make new threads for x829.
Click to expand...
Click to collapse
ymmi21 said:
Yes I know that I can write to moderators for new threads but for what ? I'm looking this rom on Leeco company site. Not here.
Why do not they have it on their website ? I found only for Chinese and Indian versions, but not for USA (x829).
---------- Post added at 01:57 PM ---------- Previous post was at 01:55 PM ----------
Click to expand...
Click to collapse
I don't know why. All so given by my friends in Greece that they have it and flash to give it back to seller after fingerprint issues.
CrisBalGreece said:
Only For X829 owners... 16s stock rom
https://mega.nz/#!ZG4G1YiS!FHW2u7EAwzVkXr1djEJlAaoZxa2AvjkZlakCRuLLmZw
https://drive.google.com/file/d/0B9KXxWUKQWYBaml4aEhFeFV5N2M/view
Extract zip file in adb on your c:/ directory.
Fastboot rom execute bat file in fastboot mode.
If you have problems with bat.. Put all rom files Inside tools file type on cmd as administrator one by one
fastboot flash ddr ddr.mbn
fastboot flash dsp adspso.bin
fastboot flash boot boot.img
fastboot flash bluetooth BTFM.bin
fastboot flash cmnlib cmnlib.mbn
fastboot flash cmnlibbak cmnlib.mbn
fastboot flash cmnlib64 cmnlib64.mbn
fastboot flash cmnlib64bak cmnlib64.mbn
fastboot flash devcfg devcfg.mbn
fastboot flash devinfo devinfo.bin
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot flash hyp hyp.mbn
fastboot flash hypbak hyp.mbn
fastboot flash keymaster keymaster.mbn
fastboot flash keymasterbak keymaster.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash pmic pmic.elf
fastboot flash pmicbak pmic.elf
fastboot flash rpm rpm.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash splash splash.img
fastboot flash system system.img
fastboot flash tz tz.mbn
fastboot flash tzbak tz.mbn
fastboot flash xbl xbl.elf
fastboot flash xblbak xbl.elf
fastboot reboot
If you don't know how to flash fastboot rom and make the above just flash this through TWRP
TWRP zip Flashable rom
https://mega.nz/#!ZG4G1YiS!FHW2u7EAwzVkXr1djEJlAaoZxa2AvjkZlakCRuLLmZw
Click to expand...
Click to collapse
Where you found this rom or it is yours ?
Which exactly bat file I have to open ?In file of first link I find 2 bat files, scripts.bat and some chinese signs.bat ?
File of last link (kind of like for twrp) is the same like file of first link ?
Where are differences ?
Rom 16s
CrisBalGreece said:
Check your adb and drivers otherwise go manually one by one. Read OP info. Download it only through pc.
Click to expand...
Click to collapse
1. Error when unzipping on file system.img !
2. Link to download firmware for TWRP the same as for flashing in FASTBOOT !!!
Please fix it, thanks in advance
What is the safest way to apply the newest updates? I am still on April, been afraid to do anything without asking first.
Is there a simple way, and will I still be able to unlock/root again?
Same question. Accent being on 'safe'.
SmilingPerson said:
What is the safest way to apply the newest updates? I am still on April, been afraid to do anything without asking first.
Is there a simple way, and will I still be able to unlock/root again?
Click to expand...
Click to collapse
maybeme2 said:
Same question. Accent being on 'safe'.
Click to expand...
Click to collapse
Either flash a custom rom that's been updated with the latest security patch
Or flash an official stock firmware but remember the chances of it being the latest security patch is slim
Obviously if your device is not bootloader unlocked you can't flash custom roms - you can flash official stock firmware via fastboot but I wouldn't bother as you will already be on the latest available firmware so just wait for the next ota update to arrive
TheFixItMan said:
Either flash a custom rom that's been updated with the latest security patch
Or flash an official stock firmware but remember the chances of it being the latest security patch is slim
Obviously if your device is not bootloader unlocked you can't flash custom roms - you can flash official stock firmware via fastboot but I wouldn't bother as you will already be on the latest available firmware so just wait for the next ota update to arrive
Click to expand...
Click to collapse
See this thread ...
https://forum.xda-developers.com/moto-g7/help/ota-rooted-phone-t3956012
I copied out the important parts..
1. Download the latest firmware.
2. Install adb & fastboot
3. Flash with these commands:
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash dtbo dtbo.img
fastboot flash logo logo.bin
fastboot flash boot boot.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 system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash vendor vendor.img_sparsechunk.2
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
DO NOT RUN THIS ONE ---- fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
you will then need to patch boot with magisk again.
TheFixItMan said:
Either flash a custom rom that's been updated with the latest security patch
Or flash an official stock firmware but remember the chances of it being the latest security patch is slim
Obviously if your device is not bootloader unlocked you can't flash custom roms - you can flash official stock firmware via fastboot but I wouldn't bother as you will already be on the latest available firmware so just wait for the next ota update to arrive
Click to expand...
Click to collapse
The latest for the xt1962-1 retail is the August security patch. That's pretty good considering Lenovomoto.
I hit the notice for the June 1, 2019. Failed to install. Tried using the Lenovo Moto Smart Assistant and it bricked my phone. Now have to wait on Motorola to send a replacement. Very frustrated right now. WTF an OTA failed and the LMSA bricked the phone. SMH...
Don't try to apply the updates or LSMA without locking the bootloader (again) first. Afterwards unlock and reroot using same method as before. I'm sure there will be plenty of full wipes so back up accordingly.
zenful said:
Don't try to apply the updates or LSMA without locking the bootloader (again) first. Afterwards unlock and reroot using same method as before. I'm sure there will be plenty of full wipes so back up accordingly.
Click to expand...
Click to collapse
Locking the bootloader is not a cinch either.
Makes you wonder if the safest course might not be to just ignore the updates and stay with the android version you have.
Which is more dangerous, staying with the 'not-updated' working phone or trying to update and risking a bricked phone?
maybeme2 said:
Locking the bootloader is not a cinch either.
Click to expand...
Click to collapse
From my understanding, you need a signed/original boot.img that of which if you didn't make a backup of yours before rooting, than the LSMA can help. I'm thinking removing Magisk and full factory resetting will be necessary as well.
As for obtaining a copy of a signed/official boot.img
sd86 said:
Head on over to https://support.lenovo.com/us/en/downloads/ds101291 and download the tool, after installed put your phone in bootloader/fastboot mode and go through the rescue steps up until the firmware is downloaded, do not click rescue after the firmware is fully downloaded just head on over to C:\ProgramData\LMSA\Download\RomFiles and open the downloaded firmware and take the boot image from there and copy it to your fastboot tools folder and flash that boot.img check that the firmware matches the version installed on your phone before flashing the boot.img.
Click to expand...
Click to collapse
About the
fastboot oem lock
Click to expand...
Click to collapse
skuppej said:
The trick is to run `fastboot oem lock` 3x (not 2x) before flashing boot.img, and then run `fastboot oem lock` one last time after this is done.
Click to expand...
Click to collapse
(Above info found in this thread about relocking the bootloader)
maybeme2 said:
Which is more dangerous, staying with the 'not-updated' working phone or trying to update and risking a bricked phone?
Click to expand...
Click to collapse
I can't give you a definite answer, but the way I perceive this is;
Should I keep a version of my OS that does not have the most recent security updates but has been rooted?
Click to expand...
Click to collapse
I hope this info helps and brings some clarity for you.
zenful said:
Don't try to apply the updates or LSMA without locking the bootloader (again) first. Afterwards unlock and reroot using same method as before. I'm sure there will be plenty of full wipes so back up accordingly.
Click to expand...
Click to collapse
Phone was locked and not rooted. It's now FUBAR and Moto is sending me a replacement.
Hi all,
This is a long shot, I hope there is someone somewhere that can help with this issue. I know it's a fairly old phone now, but if anyone has any knowledge about android recovery, it would be greatly appreciated!
Version: OxygenOS 3.6.1.
Rooted via Magisk and Bootloader Unlocked years ago.
The problem was unexpected. It was suffering battery drains for the past month, and last night, whilst on charge, I noticed it restarted. And now it's stuck on the OnePlus LOGO Screen. D:
I can only access FASTBOOT and NOT RECOVERY mode.
What I've tried:
MSM RECOVERY TOOL (w/ QCOM drivers)
Installing ABD Interface Drivers to try an ADB Sideload (but can't get to recovery)
Fastboot flashing stock and TWRP recoveries (can't boot into it - error dtb not found).
Fastboot flash_Ox211.cmd *
Spoiler: * flash_Ox211.cmd does the following
Code:
rem adb reboot-bootloader
fastboot flash boot boot.img
fastboot flash system system.img
rem fastboot erase recovery
rem fastboot flash recovery unofficial_twrp_2.8.7.0-bacon.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash sdi sdi.mbn
fastboot flash pmic pmic.mbn
fastboot flash hyp hyp.mbn
fastboot flash bluetooth BTFM.bin
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash oem_stanvbk static_nvbk.bin
rem fastboot flash userdata userdata_64g.img
pause
rem fastboot reboot
None of the above has worked or has fixed recovery mode.
I want to keep my userdata. Is it possible to access that partition, and/or somehow do an 'adb backup'. It might be impossible without the recovery
To keep documenting my findings on extra things that I have done or will do.
Reseating the battery
I have drained the battery and taken the battery connection out the phone for an hour.
UPDATE: After re-plugging, and putting it into charge, the phone bootloops now instead of staying stuck on the OnePlus/Android LOGO continuously. NO CHARGING INDICATOR.
Replacing the battery
If it's a battery issue, then a replacement might work. I have ordered one.
UDPATE: TBD
Fastboot Flashing other recovery img's
dtb not found (or device tree blob) - was an issue when I tried booting into a flashed recovery (stock or TWRP). According to some forum posts, it may be due to flashing the wrong recovery version on the device.
UPDATE:
stock []
twrp-2.8.7.0-oneplus2 [] - no dtb error
twrp-3.0.0-1-oneplus2 []
twrp-3.0.2-1-oneplus2 []
twrp-3.2.1-0-oneplus2 []
...
↑ Doing a fastboot boot <recovery>.img bootloops the phone.
Try asking in the op2family discord server, there are some pretty knowledgeable ppl there. Also you could try asking _undead, he's the one who made lineage 19.1 for op2, see in Original Android Development on this forum.
Huh, it sounds like you're having a similar issue as me. Except I can access recovery but not fastboot... and sideloading isn't working for me.