I have a XT1572 (Indian variant dual sim) . The sim card works good on both 6.0 & 7.0 (official roms) however remains undetected on any custom rom . Any guidance would be of great help .
Using magisk? It will cause that. Flash magisk uninstaller and reboot system once before flashing a new rom.
Tried but no success
jason2678 said:
Using magisk? It will cause that. Flash magisk uninstaller and reboot system once before flashing a new rom.
Click to expand...
Click to collapse
So I was on stock mm , had magisk -uninstalled and rebooted afterwards . Installed RRemix(RR-N-v5.8.5-20171230-clark-Final) . Again no sim . Attaching two screen shots for your reference .
One thing to note I have a dual sim variant and under all custom roms imei of only one is being displayed .
This whole thing is very strange since I could run Lineage very easily on the same phone sometime back , roughly around Oct'17 . Used the phone on stock nougat afterwards .
Anyone ?
Sir2taj said:
So I was on stock mm , had magisk -uninstalled and rebooted afterwards . Installed RRemix(RR-N-v5.8.5-20171230-clark-Final) . Again no sim . Attaching two screen shots for your reference .
One thing to note I have a dual sim variant and under all custom roms imei of only one is being displayed .
This whole thing is very strange since I could run Lineage very easily on the same phone sometime back , roughly around Oct'17 . Used the phone on stock nougat afterwards .
Click to expand...
Click to collapse
@antariksh
I am very well aware of the fact that lineage would not run on nougat modem. Have tried aicp rremix unofficial lineage etc . The issue remains the same no sim detected .
What I have done for installation -
fastboot install marshmallow/nougat build (depending upon the custom rom)
flash latest twrp
in twrp factory reset (don't mount/unmount anything, all default)
rom boots but doesnt detect any sim .
details of only one imei of the two is displayed under about phone .
Sir2taj said:
@antariksh
I am very well aware of the fact that lineage would not run on nougat modem. Have tried aicp rremix unofficial lineage etc . The issue remains the same no sim detected .
What I have done for installation -
fastboot install marshmallow/nougat build (depending upon the custom rom)
flash latest twrp
in twrp factory reset (don't mount/unmount anything, all default)
rom boots but doesnt detect any sim .
details of only one imei of the two is displayed under about phone .
Click to expand...
Click to collapse
Have you tried this version with this guide?
P.S: Nougat has 9 system.img_sparsechunk's. So flash accordingly and then try any other custom ROMs.
P.P.S: Flash Modem twice if you get any 'prevalidation failed error'
antariksh said:
Have you tried this version with this guide?
P.S: Nougat has 9 system.img_sparsechunk's. So flash accordingly and then try any other custom ROMs.
P.P.S: Flash Modem twice if you get any 'prevalidation failed error'
Click to expand...
Click to collapse
Will try the guide and get back to you
Update
Tried each and every step as per your suggestions . No change .
The phone is failing to recognize sims on all custom roms .
Sir2taj said:
Will try the guide and get back to you
Update
Tried each and every step as per your suggestions . No change .
The phone is failing to recognize sims on all custom roms .
Click to expand...
Click to collapse
@antariksh pls help
Sir2taj said:
@antariksh pls help
Click to expand...
Click to collapse
I'm afraid it must be your device issue.
Cause last week I followed the same steps to Flash Stock Nougat and went back to NucleaROM.
You sure you are using Nougat Modem based Custom ROMs?
antariksh said:
I'm afraid it must be your device issue.
Cause last week I followed the same steps to Flash Stock Nougat and went back to NucleaROM.
You sure you are using Nougat Modem based Custom ROMs?
Click to expand...
Click to collapse
Very very strange because I do recall that all these custom ROMs used to run fine without any such stupid issues back in October last year . its really disheartening. Yes I am using nougat firmwares for nougat modem compatible ROMs and mm firmware for rhe mm compatible one's . Its just that be it any custom ROM this thing won't work at all ! Is it anyhow related to recovering phone from brick state because I do remember that I had to flash the bootloader on a memory card in order to get the device up ?
Appreciate your efforts brother.
i have similar problem
antariksh said:
Have you tried this version with this guide?
P.S: Nougat has 9 system.img_sparsechunk's. So flash accordingly and then try any other custom ROMs.
P.P.S: Flash Modem twice if you get any 'prevalidation failed error'
Click to expand...
Click to collapse
HI there , I hope my constant requests aren't bothering . If they are kindly let me know & I shall refrain in future .
I just realised one thing . On installing nougat fastboot file from " https://forum.xda-developers.com/moto-x-style/general/xt1572firmwareclarkretasiaindiads7-t3735257" as per suggestions I get model as XT 1572 on connection to PC . Although in recovery mode when connected (twrp) the same pc recognizes the phone as XT1575 . Is it normal ?
Sir2taj said:
HI there , I hope my constant requests aren't bothering . If they are kindly let me know & I shall refrain in future .
I just realised one thing . On installing nougat fastboot file from " https://forum.xda-developers.com/moto-x-style/general/xt1572firmwareclarkretasiaindiads7-t3735257" as per suggestions I get model as XT 1572 on connection to PC . Although in recovery mode when connected (twrp) the same pc recognizes the phone as XT1575 . Is it normal ?
Click to expand...
Click to collapse
Yep. It is normal. TWRP was probably based out on XT1575. But it doesn't matter.
Only modems differ between XT1575 and XT1572.
Flash the MM firmware, make sure the modem has no validation issues, then flash the custom ROM you want. Flashing with Nougat firmware won't allow boots. Also, sometimes the MM firmware just doesn't work, and flashing stock firmware will "rejuvenate" it.
parker.stephens said:
Flash the MM firmware, make sure the modem has no validation issues, then flash the custom ROM you want. Flashing with Nougat firmware won't allow boots. Also, sometimes the MM firmware just doesn't work, and flashing stock firmware will "rejuvenate" it.
Click to expand...
Click to collapse
I wanted to try installing it on 6.0 . The install process didn't initiate saying that the bootloader (A**52) isnt compatible.
Plus I noted that on downgrading to 6.0 from 7.0 the loader and gpt bin gave failure errors in fastboot.
Sir2taj said:
I wanted to try installing it on 6.0 . The install process didn't initiate saying that the bootloader (A**52) isnt compatible.
Plus I noted that on downgrading to 6.0 from 7.0 the loader and gpt bin gave failure errors in fastboot.
Click to expand...
Click to collapse
GPT is not downgradeable and it doesn't need to flash successfully. Also, one you are on 0xA052 firmware, you can't go back, but you can edit the rom's files and make it skip the bootloader check. This is a quote of myself on how to do that from the LOS thread,
"Extract the ROM zip into it's own subdirectory. Then go into the folder META-INF, then com, then google, android, then open updater-script in a text editing program. I prefer Notepad++. Locate the line that says assert getprop ro.bootloader. Should be line 2. You can either add your bootloader by copying another item, or this is easier, edit a line already there, such as "|| getprop("ro.bootloader") == "0xA048" ||" and replace 0xA048 with 0xA052 or the bootloader your device has. Then save it by going to the root folder, not the folder labeled "lineage-14.1-xxxxxxxx-nightly-clark-signed", but the folder with the folders install, META-INF, system, and etc. Select everything by dragging your cursor over all the files, then right-click, send-to, compressed zip. Name it anything, then copy it to your device however you prefer, I just sideloaded it in TWRP. If you get an error talking about a digest file, you might have accidentally deleted something you shouldn't have."
parker.stephens said:
GPT is not downgradeable and it doesn't need to flash successfully. Also, one you are on 0xA052 firmware, you can't go back, but you can edit the rom's files and make it skip the bootloader check. This is a quote of myself on how to do that from the LOS thread,
"Extract the ROM zip into it's own subdirectory. Then go into the folder META-INF, then com, then google, android, then open updater-script in a text editing program. I prefer Notepad++. Locate the line that says assert getprop ro.bootloader. Should be line 2. You can either add your bootloader by copying another item, or this is easier, edit a line already there, such as "|| getprop("ro.bootloader") == "0xA048" ||" and replace 0xA048 with 0xA052 or the bootloader your device has. Then save it by going to the root folder, not the folder labeled "lineage-14.1-xxxxxxxx-nightly-clark-signed", but the folder with the folders install, META-INF, system, and etc. Select everything by dragging your cursor over all the files, then right-click, send-to, compressed zip. Name it anything, then copy it to your device however you prefer, I just sideloaded it in TWRP. If you get an error talking about a digest file, you might have accidentally deleted something you shouldn't have."
Click to expand...
Click to collapse
Will give it a try
parker.stephens said:
GPT is not downgradeable and it doesn't need to flash successfully. Also, one you are on 0xA052 firmware, you can't go back, but you can edit the rom's files and make it skip the bootloader check. This is a quote of myself on how to do that from the LOS thread,
"Extract the ROM zip into it's own subdirectory. Then go into the folder META-INF, then com, then google, android, then open updater-script in a text editing program. I prefer Notepad++. Locate the line that says assert getprop ro.bootloader. Should be line 2. You can either add your bootloader by copying another item, or this is easier, edit a line already there, such as "|| getprop("ro.bootloader") == "0xA048" ||" and replace 0xA048 with 0xA052 or the bootloader your device has. Then save it by going to the root folder, not the folder labeled "lineage-14.1-xxxxxxxx-nightly-clark-signed", but the folder with the folders install, META-INF, system, and etc. Select everything by dragging your cursor over all the files, then right-click, send-to, compressed zip. Name it anything, then copy it to your device however you prefer, I just sideloaded it in TWRP. If you get an error talking about a digest file, you might have accidentally deleted something you shouldn't have."
Click to expand...
Click to collapse
Iam gettign error 6 . Pls share the edited updater script for bootloader - A0.52
I've got exactly the same issue.... Sim not detected on Nougat, can't boot Marshmallow roms.
Someone found a fix to this?
Perhaps I'm not the only one having the issue of no sim
Sir2taj said:
Perhaps I'm not the only one having the issue of no sim
Click to expand...
Click to collapse
i have the same issue my friend and i dont know what to do.
Related
Can anyone share it with me please? I see no one has uploaded it yet.
ahrion said:
I see no one has uploaded it yet.
Click to expand...
Click to collapse
Because the phone is not out yet! (In the west)
ahrion said:
Can anyone share it with me please? I see no one has uploaded it yet.
Click to expand...
Click to collapse
I'm no dev but I have to wonder, would the software have files written/coded in English inside of it. is it a convention ?
I would like to know if there is the possibility of installing the original firmware international version of axon7 Chinese model without root?
Unless the software checks at the start of the flashing process fail to match ROM with phone (so you don't try to flash a ROM for a different phone, which would brick it) it should work. As an aside, root/no root does not affect flashing, locked/unlocked boot-loader does but for ROMs signed by the manufacturer this isn't an issue either
ahrion said:
Can anyone share it with me please? I see no one has uploaded it yet.
Click to expand...
Click to collapse
i have the 4GB modle ...can you tell me how i can i do it
am rely to help if you can root the device and get it clean without chines apps and am facing not compatible apps from google play and that rely frustrating in addition i can even install some apps related to my google plus or banks app it refuse to install ( not compatable )
abunhyan said:
i have the 4GB modle ...can you tell me how i can i do it
am rely to help if you can root the device and get it clean without chines apps and am facing not compatible apps from google play and that rely frustrating in addition i can even install some apps related to my google plus or banks app it refuse to install ( not compatable )
Click to expand...
Click to collapse
expect ZTE releases the International firmware, then let's install on the Chinese model
I hope so......
how can i flash Stock ROM with twrp, when i make install from Zip, it died with this Error Message:
" Updater process ended with Error: 8
Error installing zip file'external_sd/update.zip"
and when i flash as Image, i have many Images like boot, echarge, mdtp, recovery and splash.img... whichs the right that after reboot my phone is boot and install the rom?
Or anyone can say me why starts my wifi(has no mac adress) and the fingerprint(can not add fingerprint) not on my Phone A2017G B03?
Schattenklinge said:
how can i flash Stock ROM with twrp, when i make install from Zip, it died with this Error Message:
" Updater process ended with Error: 8
Error installing zip file'external_sd/update.zip"
and when i flash as Image, i have many Images like boot, echarge, mdtp, recovery and splash.img... whichs the right that after reboot my phone is boot and install the rom?
Or anyone can say me why starts my wifi(has no mac adress) and the fingerprint(can not add fingerprint) not on my Phone A2017G B03?
Click to expand...
Click to collapse
It seems that a mismatch between the system and boot causes issues with WiFi.
thx i know, but with the 2 adb calls to modemst has not worked...
and i am not shure we i can flash the boot and the /system with the right img.
I'm unable to unpate as of right now because I have TWRP recovery installed.
When I try to, it tells me " Package expects fingerprint of *original device fingerprint* this device has TWRP\Team_Win_Recovery_Proejct/ailsa_ii
Updater process ended with ERROR: 8
Error installing zip file '@/cache/recovery/block.map'"
I tried removing the part of the script that checks this, but then I got a different error (I don't remember what it was, it said something about "Boot:1826459185:1U57126581(Random numbers not the actual ones) contains unexpected content" or something like that
So I was wondering, how would I go and update to the new Android 7.0 update? (I also have the zip file of the update locally)
I would assume that I could flash stock recovery but a. I don't have the stock recovery.img, and b. I was reading around and someone mentioned that if I flashed stock recovery it'd delete all my data.
I'd be highly disappointed if the only way I could update to the 7.0 update is by deleting all my data. I'm sure there must be some way around it.
Can anyone help me out? I'm sure I'm not the only one that'll have this issue
EDIT: Flashed Recovery.img (Only recovery.img, via fastboot)
Results: Recovery is flashed and working.
Phone does boot up perfectly fine, no issues
Data is NOT lost.
Flashing the 7.0 update(A2017UV110B15) (Via stock recovery) [Remember to put it on your SDCard]:
Verifying update package...
Verified.
"EMC /dev/block/bootdevice/by-name/boot****load of numbers)" has unexpected contents
Aborted
Click to expand...
Click to collapse
( Same error as when I removed device verification.. maybe this is a user error and not a system/update error )
( Maybe I failed to download the update zip properly? I'll try the OTA update instead )
Downloading..
Rebooting..
Installing System Update...
Has unexpected contents
Package mixmatched
Aborted
Click to expand...
Click to collapse
( No, not a user error I suppose.. I don't know what is wrong then! This is odd )
System update failed
Reason: The system update package did not match the phone
Click to expand...
Click to collapse
And for the record, I am on A2017UV1.0.0B29
Andrew S.S. said:
I'm unable to unpate as of right now because I have TWRP recovery installed.
When I try to, it tells me " Package expects fingerprint of *original device fingerprint* this device has TWRP\Team_Win_Recovery_Proejct/ailsa_ii
Updater process ended with ERROR: 8
Error installing zip file '@/cache/recovery/block.map'"
I tried removing the part of the script that checks this, but then I got a different error (I don't remember what it was, it said something about "Boot:1826459185:1U57126581(Random numbers not the actual ones) contains unexpected content" or something like that
So I was wondering, how would I go and update to the new Android 7.0 update? (I also have the zip file of the update locally)
I would assume that I could flash stock recovery but a. I don't have the stock recovery.img, and b. I was reading around and someone mentioned that if I flashed stock recovery it'd delete all my data.
I'd be highly disappointed if the only way I could update to the 7.0 update is by deleting all my data. I'm sure there must be some way around it.
Can anyone help me out? I'm sure I'm not the only one that'll have this issue
Click to expand...
Click to collapse
Flashing stock recovery will not delete your data. Find your stock firmware download on the forum or zte, pull recovery.img from it and flash in twrp.
Of course those who whine about wiping data usually are the ones who need to do it most.
FYI I updated, flashed twrp and then restored data from my b29 backup without issue. At least this way you can make a new backup before attempting.
You can also wait for the flashable .zips to show up and avoid all the hassle.
lafester said:
Flashing stock recovery will not delete your data. Find your stock firmware download on the forum or zte, pull recovery.img from it and flash in twrp.
Of course those who whine about wiping data usually are the ones who need to do it most.
FYI I updated, flashed twrp and then restored data from my b29 backup without issue. At least this way you can make a new backup before attempting.
You can also wait for the flashable .zips to show up and avoid all the hassle.
Click to expand...
Click to collapse
Read my updated comment; Sorry that I didn't just edit the thread. And that makes sense. I think it would be wise for me to just wait.
First of all, flash rollback zip from DrakenFX.
Then update via OTA. That's all. I've done these steps yesterday and I'm using Nougat now.
WesTD said:
First of all, flash rollback zip from DrakenFX.
Then update via OTA. That's all. I've done these steps yesterday and I'm using Nougat now.
Click to expand...
Click to collapse
I saw your post then had forgotten about it til now ( haven't checked ) but in the last month I've forgotten where the rollback zip is located / what thread. Any help would be appreciated.
Only use ota if you don't want twrp/root anymore.
Andrew S.S. said:
I saw your post then had forgotten about it til now ( haven't checked ) but in the last month I've forgotten where the rollback zip is located / what thread. Any help would be appreciated.
Click to expand...
Click to collapse
Here you go; https://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
Hi there, good to see you.
After struggling to find any helpful information about rooting ZTE Blade A2 plus, I finally was able to root>soft brick>hard brick>stock flash>repeat this beautiful device. So thought to share it here so that it becomes helpful for someone in need.
Device Information: https://forum.xda-developers.com/ge...te-blade-a2-plus-5-5-fhd-mt6750t-3gb-t3480759
Prerequisite: Winrar Latest version, VCOM and device drivers (MT67xx), General intelligence to download the attachments and to arrange everything in order and you're good to go
Step 1: Install custom recovery (We'll install TWRP)
a} Download recovery and preloader
b} Download Scatter file
c} Download SP Flash tools
d} Only tick recovery and preloader and select the downloaded files and flash it
e} When the process finishes and SP flash tools displays done, remove the phone and press "Vol Up+Power" to boot into recovery. It may ask you to make /system writable if you want swipe as indicated
f} Done enjoy
Note: Take this opportuniy to first of all backup your stock rom using TWRP and save it elsewhere.
Step 2: Rooting (With Magisk Or Super SU)
a} Download Magisk or Super SU flashable zip as per your need
Note: Magisk gives most of the Super SU features and doesn't trips google security net so you are able to use banking apps while rooted with magisk
b} Place downloaded zip in your sd card
c} Boot into TWRP recovery and flash the said zip
d} Done enjoy
Step 3: Flashing stock rom (Only russian version as of now)-Language is english bloatwares are Russian
a} Download Stock Rom from https://yadi.sk/d/RZLBrKKv3LxejN
Note: It contains PC Flashable stock rom along with scatter files and NVRAM backups so it'll help if you lose IMEI during the process, it is advisable to keep this offline as backup in case links stops working.
b} Flash the downloaded stock rom with SP flash tools
Note: This stock rom doesn't support VOLTE so i advice you to first take a full backup of your initial rom after installing TWRP, also please share that backup here as well so as i could add it to this thread to make it helpful for someone who has already lost VOLTE inclusing me
Conclusion: I'll be very happy if this information proves useful to you in any manner and also request you to must share your backup for me to get VOLTE back.
Thank You
MIUI 9 For A610 Plus
Preview:
Many many thanks Alfonso for making this vary valuable post . I think A2 Plus and A610 Plus are almost same , so kindly check this ROM me and may solve your volte problem
ww.getdroidtips.com/miui-9-zte-blade-a610-plus/[/url]
Rajevpmavoor said:
Preview:
Many many thanks Alfonso for making this vary valuable post . I think A2 Plus and A610 Plus are almost same , so kindly check this ROM me and may solve your volte problem
ww.getdroidtips.com/miui-9-zte-blade-a610-plus/[/url]
Click to expand...
Click to collapse
Although the rom is bugless but, unfortunately VOLTE didn't work.
MIUI 9 For A610 Plus
Did you flash this new MIUI 9 ROM , I think it has volte and it is in Android M.
Alfonso Osnofla said:
Although the rom is bugless but, unfortunately VOLTE didn't work.
Click to expand...
Click to collapse
does it boot into meta mode on pressing volume down+power button??( bcoz my fone boots into meta mode on doing so)
and how to go into bootloader?
while using sp flash tool i power off the fone and then connect it to sp flash tool via usb cable ...fone gets detected and but download for twrp doesnt occur ..it says PMT changed for the rom, select format all+ download ....
but i didnt do format all coz i dont have flashable stock rom...
I lost my IMEI after flash ROM, not able to retrieve IMEI
Issue in camera & Finger Lock
Alfonso Osnofla said:
Although the rom is bugless but, unfortunately VOLTE didn't work.
Click to expand...
Click to collapse
I have checked both ROM, Miui ROM camera is look like .02MB, No VOLTE, Finger Print lock is not working
Thanks. I have messed up anyway...
Anybody have a complete Readback (Using SP-Flash Tools) copy of (volte) rom?
I lost Imei, From the given NVram.bin, Could not edit Imei using BPGL.... pull as Maui Meta and SN writer can not do this with present update.
I need to revert back. please help with ROM copy and NVRAM Edit.
Alfonso Osnofla said:
Hi there, good to see you.
After struggling to find any helpful information about rooting ZTE Blade A2 plus, I finally was able to root>soft brick>hard brick>stock flash>repeat this beautiful device. So thought to share it here so that it becomes helpful for someone in need.
Device Information: https://forum.xda-developers.com/ge...te-blade-a2-plus-5-5-fhd-mt6750t-3gb-t3480759
Prerequisite: Winrar Latest version, VCOM and device drivers (MT67xx), General intelligence to download the attachments and to arrange everything in order and you're good to go
Step 1: Install custom recovery (We'll install TWRP)
a} Download recovery and preloader
b} Download Scatter file
c} Download SP Flash tools
d} Only tick recovery and preloader and select the downloaded files and flash it
e} When the process finishes and SP flash tools displays done, remove the phone and press "Vol Up+Power" to boot into recovery. It may ask you to make /system writable if you want swipe as indicated
f} Done enjoy
Note: Take this opportuniy to first of all backup your stock rom using TWRP and save it elsewhere.
Step 2: Rooting (With Magisk Or Super SU)
a} Download Magisk or Super SU flashable zip as per your need
Note: Magisk gives most of the Super SU features and doesn't trips google security net so you are able to use banking apps while rooted with magisk
b} Place downloaded zip in your sd card
c} Boot into TWRP recovery and flash the said zip
d} Done enjoy
Step 3: Flashing stock rom (Only russian version as of now)-Language is english bloatwares are Russian
a} Download Stock Rom from https://yadi.sk/d/RZLBrKKv3LxejN
Note: It contains PC Flashable stock rom along with scatter files and NVRAM backups so it'll help if you lose IMEI during the process, it is advisable to keep this offline as backup in case links stops working.
b} Flash the downloaded stock rom with SP flash tools
Note: This stock rom doesn't support VOLTE so i advice you to first take a full backup of your initial rom after installing TWRP, also please share that backup here as well so as i could add it to this thread to make it helpful for someone who has already lost VOLTE inclusing me
Conclusion: I'll be very happy if this information proves useful to you in any manner and also request you to must share your backup for me to get VOLTE back.
Thank You
Click to expand...
Click to collapse
Just try http://www.ztedevice.com/support/detail?id=FE22BEF5C33D4A17BCDA20AAE2631951 ( http://download.ztedevice.com/support/product/569/201802111051594/sd/20180211105554767.zip )
sd card update using twrp.
But first remove the first line from update script file located inside the zip.
Just reply.
Need MIUI rom
Heyy plz gime me teh rom for zte blade A2 plus i really need a miui rom for zte blade A2 plus...
Help I'm confused.
Reading the comments i got to know that many people lost their IMEI and VOLTE , I want to root the device So can anyone tell me when does this problem occur (loosing volte and imei) during rooting or while flashing a custom rom?
kingksath said:
I lost my IMEI after flash ROM, not able to retrieve IMEI
Click to expand...
Click to collapse
Did you loose your IMEI on rooting or while flashing any custom Rom?
http://www.mediafire.com/file/6768c1x7dqyd818/update.zip
version 4 sd card update
vasilemk said:
http://www.mediafire.com/file/6768c1x7dqyd818/update.zip
version 4 sd card update
Click to expand...
Click to collapse
What is it for?
Is it for volte?
vasilemk said:
http://www.mediafire.com/file/6768c1x7dqyd818/update.zip
version 4 sd card update
Click to expand...
Click to collapse
Is this an update to the Stock Rom?
hi, can u help me please, iam tryin to update with twrp , i did remove first line from script but i have error.
Found a way to unlock bands on MTK based phones by flashing basebands from phones with the same chipset. Doing this by using SPFLASH and flashing md1 files. Still unable to connect to cell network on my Doogee bl12000. Flashed this phones MD1, was wondering if anybody could provide me with the nvdata and nvram from the ZTE blase a2 plus. Hoping by flashing those files can connect to a U.S. network.
Hello,
I'm having big problems flashing any ROM on my Oneplus 5 atm.
At the beginning of this month, I wanted to unroot my rooted Android 8.0 or 8.1 (One of them, it was OxygenOS, but not the newest version)+ Xposed Oneplus 5.
I got a couple of errors, most of the time error 7.
After hours, old and new recoverys (TWRP) from blu_spark, codeworkx and some xda user recoverys and diffrent OxygenOS versions i finally managed it to install a Oxygen version with Android 7.1.1 on the phone. The Problem was: I always got errors (Installation failed) when I wanted to intall Software Updates no matter if I tryed it by myself or with the official system update in android.
So and today the official beta build of OxygenOS for 9.0 released and I was so stupid and thought I can make this an easy one.
Now I'm sitting here since 9:30am and try to flash Android 9, or any Android except 7.1.1 (only Oxygen Versions). Most of the Time i'm getting ERROR:7, it doesnt matter with which Recovery or Build.
When I got this problem at the first Time, my Phone was shown as "" (The error was something like: This Package is for a "Oneplus 5" this is a "").
When I get this scentence now (not every Recovery is showing it) it says my Phone is a "OnePlus5T", but i have a Oneplus 5.
Also (maybe partly) important things are:
- I tryed to edit the updater-script and delete the assets lines but there were no asset lines. Tryed it anyways and it didnt work. (and i really dont want to try this again)
I tryed to google this error for hours and many people meant that this is the way to go but I dont belive it. Isn't there any way to rename my phone, if yes: what do I have to do? I have TWRP and access to the command prompt aswell. If anyone can successfully create the 9.0 beta without the assets I would be happy but i dont think that is the solution for my problem, just a workaround.
- I think the problem is just something about my devices name. The strange part is that it accepted 7.1.1. And this was 100% a Oneplus 5 ROM.
- 7.1.1 isnt the way to go for me anymore. I dont like android 7 and it has so old security patches..
- Fingerprint sensor and screen got replaced
thank you for reading this and maybe helping me. I dont have the best language skills, if you need more Information about my Phone, please ask
EDIT1: As I said, 7.1.1 is still successfull, i tryed it a couple of mins ago. no error 7 or sth
maybe you can try revert to fully stock setup{without TWRP) and update to pie?
I have problem with error 7 when i tried to flash latest open beta (pie). I didn't find any solution.... :crying:
petryrety said:
I have problem with error 7 when i tried to flash latest open beta (pie). I didn't find any solution.... :crying:
Click to expand...
Click to collapse
Make sure the download isn't corrupt or if you extract the compatibility.zip use a recommended tool.
I had this problem couple of months ago. I solved it by flashing an old os version then flashing stock recovery(I don't remember if I locked the bootloader). boot in to the phone and download and update through ota( I did 3 updates this way). Then install twrp and root. Now I can flash any oos update without error 7.
May work
This is a post I wrote for another thread. I have found that this method fixes the error 7 issue, and allows you to update all the way to Pie without issues. When updating to Pie, use 7-Zip, not winrar or any other non-recommended programs to remove compatibility.zip from the firmware archive before flashing. I found that winrar causes treble errors or error 7.
https://forum.xda-developers.com/showpost.php?p=78523940&postcount=13
iwantademo123 said:
This is a post I wrote for another thread. I have found that this method fixes the error 7 issue, and allows you to update all the way to Pie without issues. When updating to Pie, use 7-Zip, not winrar or any other non-recommended programs to remove compatibility.zip from the firmware archive before flashing. I found that winrar causes treble errors or error 7.
https://forum.xda-developers.com/showpost.php?p=78523940&postcount=13
Click to expand...
Click to collapse
Yeah, that's what I wrote here https://forum.xda-developers.com/oneplus-5/help/massive-problems-error7-t3878372/post78503983 and in flashing instructions for open beta and stable builds in their first posts.
strongst said:
Yeah, that's what I wrote here https://forum.xda-developers.com/oneplus-5/help/massive-problems-error7-t3878372/post78503983 and in flashing instructions for open beta and stable builds in their first posts.
Click to expand...
Click to collapse
That's good, It's good advice. I am just stressing to everyone in this thread, how important it is to follow that and use a recommended tool to remove compatibility.zip because removing compatibility.zip sounds very trivial thing, but it's actually really important to use a tool like 7-Zip that doesn't break the firmware in the process.
Also, the link to my other post ( https://forum.xda-developers.com/showpost.php?p=78523940&postcount=13 ) should be detailed and comprehensive enough to help people with error 7 in other scenarios or that are trying to update to oreo or other stock firmwares too. This method restores the phone back to factory condition, including all the partitioning. Updating with a locked bootloader can fix a lot of update errors. I've found that after 5.1.5 it is safe to unlock the bootloader and take updates. But as you mentioned, for an unlocked bootloader, compatibility.zip needs to be removed from the firmware archive, and a tool such as 7-Zip must be used to do so as other archive managers break the update entirely (with error 7).
Good luck everyone trying to update, hope our advice helps :good:
So I flashed OOS 5.0.1 then went back to stock recovery. I then locked my bootloader. After which I booted into OxygenOS and updated it all the way to pie(took 3 OTAs). Now I've got a locked bootloader and pie but I'm wondering if the process to unlock the bootloader is the same or different now that there is a vendor drive?
TurtleSandals said:
So I flashed OOS 5.0.1 then went back to stock recovery. I then locked my bootloader. After which I booted into OxygenOS and updated it all the way to pie(took 3 OTAs). Now I've got a locked bootloader and pie but I'm wondering if the process to unlock the bootloader is the same or different now that there is a vendor drive?
Click to expand...
Click to collapse
The unlocking process of the bootloader is the same!
I am having the exact same problem, tried everything from above. Can get anything more recent than 7.1.1 on my oneplus 5. evrything else is error 7. Any update
mathgerm said:
I am having the exact same problem, tried everything from above. Can get anything more recent than 7.1.1 on my oneplus 5. evrything else is error 7. Any update
Click to expand...
Click to collapse
Please see here https://forum.xda-developers.com/on...xygenos-4-5-2-7-1-1-ota-t3627003/post79938097
Hello!
I have unlocked the bootloader of my Mate 10 lite and proceeded to flash TWRP and Magisk onto the device. But in doing so, I get an awful looking screen when I boot the device, so I thought I should relock the bootloader, now that TWRP has been flashed.
...I immediately regretted relocking the bootloader, as the system was inaccessible until I re-unlocked the bootloader and was able to access TWRP and the system again. So my question is, can you lock the bootloader with TWRP installed and still access the system?
Also, if I want to go back to full-stock, I have to download a stock ROM for the system from firmwarefinder and flash it with some tool, correct?
Tsun_Pooka said:
So my question is, can you lock the bootloader with TWRP installed and still access the system?
Click to expand...
Click to collapse
Unfortunately, it's impossible...
You can flash Stock ROM for the system from firmwarefinder (fullOTA-MF only!) using HwOTA, HuRupdater, Huawei Multi-tool (RUFI).
If You want to go back to full-stock with locked bootloader (not re-locked) , You have to flash Service ROM from dload (this process will erase all the data from your device!).
Tsun_Pooka said:
Hello!
I have unlocked the bootloader of my Mate 10 lite and proceeded to flash TWRP and Magisk onto the device. But in doing so, I get an awful looking screen when I boot the device, so I thought I should relock the bootloader, now that TWRP has been flashed.
...I immediately regretted relocking the bootloader, as the system was inaccessible until I re-unlocked the bootloader and was able to access TWRP and the system again. So my question is, can you lock the bootloader with TWRP installed and still access the system?
Also, if I want to go back to full-stock, I have to download a stock ROM for the system from firmwarefinder and flash it with some tool, correct?
Click to expand...
Click to collapse
How you unlock the bootloader?
bozka1 said:
Unfortunately, it's impossible... If You want to go back to full-stock with locked bootloader (not re-locked) , You have to flash Service ROM from dload (this process will erase all the data from your device!).
Click to expand...
Click to collapse
Thanks for the tips! By the way, what is dload? If it's a website, I cant find it (the fact that dload is short of "download" doesn't really help). I am now in need of that full-stock ROM.
Tsun_Pooka said:
By the way, what is dload?
Click to expand...
Click to collapse
https://forum.xda-developers.com/mate-10/help/formatting-dload-method-t3815949/page2
Whew. I got the bootloader AND FRP locked on me, and now I don't have a usable system. So now, I have to rely on eRecovery to download a 3GBs package and hope all things go well...the problem is, I'd need to find a place that offers fast WiFi...my internet is terrible.
EDIT: Got the system back up thanks to eRecovery. I'm not sure if I want to root or install a custom recovery on the Lite. I've realized even more that I should cherish my older phone, my Samsung Galaxy Win. At least this one isn't complicated or protected by Fort KNOX.
When u play with custom roms, u appreciate the customization/optimizations offered by developers, thanks to them. But with the time, u always feel stock ROM was best for this n that reasons. Recent 2/3 times I was able to use Huru Updater to get back to Stock ROM and it worked well (needs TWRP installed, and you may need to switch to other TWRP if u get error from existing)
You seem to be a beginner, so I would suggest to get help from some friends who can do it for you. Or obviously u can try ur self again and again, and learn good things until something finally works for u. You were able to relock bootloader so it means u have the code for ur device for locking/unlocking, save this code on at least 2 different places (email, google drive, dropbox etc.). Then u can easily unlock ur device again, and install Stock ROM etc.
usman400 said:
When u play with custom roms, u appreciate the customization/optimizations offered by developers, thanks to them. But with the time, u always feel stock ROM was best for this n that reasons. Recent 2/3 times I was able to use Huru Updater to get back to Stock ROM and it worked well (needs TWRP installed, and you may need to switch to other TWRP if u get error from existing)
You seem to be a beginner, so I would suggest to get help from some friends who can do it for you. Or obviously u can try ur self again and again, and learn good things until something finally works for u. You were able to relock bootloader so it means u have the code for ur device for locking/unlocking, save this code on at least 2 different places (email, google drive, dropbox etc.). Then u can easily unlock ur device again, and install Stock ROM etc.
Click to expand...
Click to collapse
Custom ROMs are the best thing to happen to the Galaxy Win, even if the available choices all have their compromises. But with the M10 lite, I think it's better to stick with stock and mod it. And I'm not exactly a beginner, but rooting the Galaxy Win and modifying it was no hard ordeal. Or the Galaxy Grand for that matter, which I changed its ROM entirely. The Mate 10 lite however, oh dear (wipes sweat).
I've got the system back up and re-fitted it with TWRP and installed Magisk. And yet, when I try backing up the data partition with TWRP, I meet a peculiar error. Excerpt from recovery.log:
Code:
I:addFile '/data/misc/bluedroid' including root: 1
==> set selinux context: u:object_r:bluetooth_data_file:s0
found policy '/data/misc/bluedroid' - '1DK' - '3c2755a577289547'
I:addFile '/data/misc/bluedroid/K+hpne9pCUEHa,R422fJJA' including root: 1
==> set selinux context: u:object_r:bluetooth_data_file:s0
I:Error adding file '/data/misc/bluedroid/K+hpne9pCUEHa,R422fJJA' to '/external_sd/TWRP/BACKUPS/FFY5T18328016218/2019-06-08--20-21-17/data.f2fs.win000'
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:InfoManager saving '/external_sd/TWRP/BACKUPS/FFY5T18328016218/2019-06-08--20-21-17/data.info'
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.
I:Copying file /tmp/recovery.log to /external_sd/TWRP/BACKUPS/FFY5T18328016218/2019-06-08--20-21-17/recovery.log
I:Set page: 'action_complete'
I:operation_end - status=1
Searching on the internet, I found the solution was to delete the file that stops the operation from finishing. However, using MiXplorer with full root permissions, I...couldn't find the file...? There's only bt_config.bak, bt_config.conf and macbt. Nothing else. What the heck is up with all that?
I'd appreciate a solution to this.
Tsun_Pooka said:
Custom ROMs are the best thing to happen to the Galaxy Win, even if the available choices all have their compromises. But with the M10 lite, I think it's better to stick with stock and mod it. And I'm not exactly a beginner, but rooting the Galaxy Win and modifying it was no hard ordeal. Or the Galaxy Grand for that matter, which I changed its ROM entirely. The Mate 10 lite however, oh dear (wipes sweat).
I've got the system back up and re-fitted it with TWRP and installed Magisk. And yet, when I try backing up the data partition with TWRP, I meet a peculiar error. Excerpt from recovery.log:
Code:
I:addFile '/data/misc/bluedroid' including root: 1
==> set selinux context: u:object_r:bluetooth_data_file:s0
found policy '/data/misc/bluedroid' - '1DK' - '3c2755a577289547'
I:addFile '/data/misc/bluedroid/K+hpne9pCUEHa,R422fJJA' including root: 1
==> set selinux context: u:object_r:bluetooth_data_file:s0
I:Error adding file '/data/misc/bluedroid/K+hpne9pCUEHa,R422fJJA' to '/external_sd/TWRP/BACKUPS/FFY5T18328016218/2019-06-08--20-21-17/data.f2fs.win000'
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:InfoManager saving '/external_sd/TWRP/BACKUPS/FFY5T18328016218/2019-06-08--20-21-17/data.info'
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.
I:Copying file /tmp/recovery.log to /external_sd/TWRP/BACKUPS/FFY5T18328016218/2019-06-08--20-21-17/recovery.log
I:Set page: 'action_complete'
I:operation_end - status=1
Searching on the internet, I found the solution was to delete the file that stops the operation from finishing. However, using MiXplorer with full root permissions, I...couldn't find the file...? There's only bt_config.bak, bt_config.conf and macbt. Nothing else. What the heck is up with all that?
I'd appreciate a solution to this.
Click to expand...
Click to collapse
I am certainly not up to what u r indicating so cant suggest a solution, earlier in my reply, I was only
indicating my experience with custom ROMs. I havent yet come across a single custom ROM for mate 10
lite that has no problems. Earlier Galaxy S4 Mini, there was custom ROM which was awsome, not a single issue
But for mate 10 lite camera problem is most common. Stock camera app often doesnt work or partially
works, restart of the app etc. You can install open camera, but it does not give u best shots, and filters.
Other issues are already discussed in every custom ROM thread, so I had to come back to Stock ROM
with magisk to remove any system apps that I dont need plus other goodies that magisk offers u (modules)
Alright, so I am supposed to install 347, but I uhh...can't, because I don't think TWRP is able to do it. What am I supposed to do in order to carry out the update successfully?
Tsun_Pooka said:
Alright, so I am supposed to install 347, but I uhh...can't, because I don't think TWRP is able to do it. What am I supposed to do in order to carry out the update successfully?
Click to expand...
Click to collapse
Flash the stock erecovery whenever i root my phone i always stick with stock recovery not custom recovery(TWRP)
Theres another method to flash the stock recovery but... This is my method on how to flash stock recovery(erecovery)
PC ONLY!!! and MAKE SURE TO HAVE UNLOCKED BOOTLOADER AND FRP!!!
1.Download MultiTool from https://pro-teammt.ru/en/multi-tool-huawei-honor/
2.Make sure to install Huawei driver from the MultiTool
3.Download This File i provided Here https://mega.nz/#!nZxl2AwZ!6qRIIRbLK4Ub80dPMae4HQQ7e-O49_f2BZ8PhbuZTYM
4.Go to MultiTool and go to recovey Section an select file that you download earlier
5.Make sure to CONNECT USB CABLE TO YOR PC now Reboot your device into Bootloader mode by PRESSING VOLUME DOWN BUTTON and CONNECT THE CABLE TO YOUR PHONE
6.Now on the MultiTool click on Flash Recovery_Ramdisk andlet it flash...,
7.Now You Have The Stock Recovery Installed Now You Can Install Offical Firmware Update On Your Phone
8.All Done
I Hope I Help You
I will follow your guide later today or tomorrow! Thank you for the help!
Tsun_Pooka said:
I will follow your guide later today or tomorrow! Thank you for the help!
Click to expand...
Click to collapse
Np
LoneWolfz said:
Np
Click to expand...
Click to collapse
I just did your instructions today. All was going well up until installation of the new update. The first time, it rebooted when the progress bar was at 6%, then it rebooted again to the recovery, went up to 6% again before showing this screen:
Code:
Software install failed!
Failed to check the update files
Please download the package again
> Reboot system now
So I'm back to square one basically.
Also, I can't install updates to the built-in Huawei apps for some reason, even after flashing the stock recovery. I'm not sure what to do with both issues now...
Tsun_Pooka said:
I just did your instructions today. All was going well up until installation of the new update. The first time, it rebooted when the progress bar was at 6%, then it rebooted again to the recovery, went up to 6% again before showing this screen:
So I'm back to square one basically.
Also, I can't install updates to the built-in Huawei apps for some reason, even after flashing the stock recovery. I'm not sure what to do with both issues now...
Click to expand...
Click to collapse
Try to download the update again
Usually when i tried to install new update(100+Mb) i will ended up what the code said but downloading a Full Update(3.49Gb) Fixed the problem
Just refresh the update in setting and install it
bozka1 said:
Unfortunately, it's impossible...
You can flash Stock ROM for the system from firmwarefinder (fullOTA-MF only!) using HwOTA, HuRupdater, Huawei Multi-tool (RUFI).
If You want to go back to full-stock with locked bootloader (not re-locked) , You have to flash Service ROM from dload (this process will erase all the data from your device!).
Click to expand...
Click to collapse
But can you unlock the bootloader later on with the same code if you wanted or is this it?
Deathecho said:
But can you unlock the bootloader later on with the same code if you wanted or is this it?
Click to expand...
Click to collapse
Yes you can use the same unlock code again.
LoneWolfz said:
Try to download the update again
Usually when i tried to install new update(100+Mb) i will ended up what the code said but downloading a Full Update(3.49Gb) Fixed the problem
Just refresh the update in setting and install it
Click to expand...
Click to collapse
The full update actually installed. Thanks for the tip!
I just still can't update my built-in Huawei apps.
Tsun_Pooka said:
The full update actually installed. Thanks for the tip!
I just still can't update my built-in Huawei apps.
Click to expand...
Click to collapse
Np