Related
Hi A7 users,
Let's start this off be saying, bare with me English is not my primary language.....
OK now, the reason for this Thread is to find a definite solution for current users and future users who have run into boot issues cuz they were trying to :
A- Go back to Un-rooted and lock bootloader state.
B- Started Playing with root tools and make a huge mistake
C- Started playing with twrp not knowing what they were doing
D- All the above + started flashing images files and got worts.
E- Any other type of situation.
I Know we make mistakes and we learn from them and well here today we are going to try or rather say Find a permanent /define solution to all this issues with your help, so PLEASE ONLY POST IF YOU HAVE RUN INTO ANY OF THIS ISSUES AND HOW YOU GOT INTO THE ENCHILADA ( MESS ) .
If you have the solution to your previous boot problems send me a PM and I'll keep this Thread updated for everyone to see with your solution and of course credit to the user/s.
NOTE : Please mention which Axon 7 you are using e.g. :
- A2017 (Chinese Variant)
- A2017U (USA Variant)
-A2017G (UK/Europe/International Variant)
reserve 1
reserve 2
reserve 3
reserve solution 4
reserve solution 5
Anyone this issues please post you issue, how to got into the problem, device model and if you got it fix let us know.
https://www.youtube.com/shared?ci=05LD4Ja-h3k
You'd think with all the other posts about problems there'd be something here by now.
Always thank those who are helpful...and just ignore those who aren't.
Mine happened when I wiped Internal storage from twrp. This caused the phone to only see 4gb of internal storage. Came to xda and it was suggested to flash back original boot.img. once that was done 4gb issue was fixed and the radio was gone.
I did indeed try every solution offered (thanks again for all the effort, DrakenFX and others). But, I've come to the conclusion that this is not going to get fixed until XTE releases US images. For other people's sake I hope I am wrong, but I myself decided to proceed with the exchange where I bought it, as I was right at the end of my 14 days (newegg doesn't seem to give the 30 days that xte does). I may be out of an Axon 7 for a while, so for now I am on my amazon ads, Blu R1 HD (with ads defeated
Is there a guide to go back to stock for the A2017G?
i'm on B02 with root and the bootloader still locked.
Like to go back to stock now that ZTE is working on an update to give the A2017G an unlocked bootloader.
Hi all,
I am currently experiencing a bootloop on my Chinese Axon 7. Some of you regulars may have seen me asking in other threads because I've tried to fix it myself, but I've kind of run out of options. Sincerely hoping one of you can help me out!!! I'll buy the winner a beer or 2, haha!
Back story:
Was on B07 with root (tenfar's tool) with locked bootloader and had some issues with the ROM. Like vibrating when I opened the camera and battery drops. So I decided to upgrade to B09. Placed the OTA on SD card and went to: Settings -> update. Worked fine. So I connected it to my PC and made a dump (tenfar's dump tool) of my recovery and boot and stored them. Then I ran the Tenfar's tool, the B09 version and it went like the last one. But when I booted I didn't have wifi, and other issues came up. So I thought: did I make a mistake? So I read it again, checked the COM port again... all checked out. And used Tenfar's tool again. After that it didn't even boot anymore! It plays the nice boot animation and then gets stuck on the end screen with all the pictures.
So after that I restored my dumped recovery.img and boot.img. This is when I knew something was wrong: it still didn't boot! I reset data/cache in the stock recovery: no boot. Still stuck at the end of the boot animation.
What I've tried:
- Flashing the stock B09 update.zip with TWRP.
- Flashing the stock B09 update.zip without updater-script 'assert' and 'get-prop' line. TWRP says 'update.zip is corrupt'. Doesn't install.
- The I put it on SD card and internal memory and tried updating it with stock recovery: 'sorry you cant sdcard upgrade'. That's all it says.
- ADB sideload stock recovery: 'cannot load update.zip'.
I tried different ADB versions, Windows and Mac, different drivers... I tried formatting SD card as FAT32.. Tried different SD card.. Doesn't make a difference.
TWRP log says it can't pass the Zip verification when I try that. If I turn that off it says re.product.name is wrong. But I checked build.prop and updater-script. It's the same! But somehow TWRP comes up with a different one. Also tried removing getprop and assert lines from updater-script. But then it says: ZIP file is corrupt.
TWRP log after trying original, stock B09 flash:
http://pastebin.com/cJivE2TK
Build.prop: moved from /system with TWRP:
http://pastebin.com/b6rryc2n
Build.prop: ro.product.name=P996A03
Updater-script:
Code:
getprop("ro.product.device") == "ailsa_ii" || abort("This package is for \"ailsa_ii\" devices; this is a \"" + getprop("ro.product.device") + "\".");
assert(getprop("ro.product.name") == "P996A03");
But TWRP log: ro.product.name=cm_ailsa_ii
So, yeah, I've been trying on and off for the past couple of days in between work and travelling. Got a back-up phone so it's not that bad. But I really like this phone! It's just been such a pain in the ass the past few days...
I tried researching online and reading all the XDA posts. It is my fault this has happened and feel such a newb for not being able to fix it myself
Many thanks in advance!
aPexalpha said:
Hi all,
I am currently experiencing a bootloop on my Chinese Axon 7. Some of you regulars may have seen me asking in other threads because I've tried to fix it myself, but I've kind of run out of options. Sincerely hoping one of you can help me out!!! I'll buy the winner a beer or 2, haha!
Back story:
Was on B07 with root (tenfar's tool) with locked bootloader and had some issues with the ROM. Like vibrating when I opened the camera and battery drops. So I decided to upgrade to B09. Placed the OTA on SD card and went to: Settings -> update. Worked fine. So I connected it to my PC and made a dump (tenfar's dump tool) of my recovery and boot and stored them. Then I ran the Tenfar's tool, the B09 version and it went like the last one. But when I booted I didn't have wifi, and other issues came up. So I thought: did I make a mistake? So I read it again, checked the COM port again... all checked out. And used Tenfar's tool again. After that it didn't even boot anymore! It plays the nice boot animation and then gets stuck on the end screen with all the pictures.
So after that I restored my dumped recovery.img and boot.img. This is when I knew something was wrong: it still didn't boot! I reset data/cache in the stock recovery: no boot. Still stuck at the end of the boot animation.
What I've tried:
- Flashing the stock B09 update.zip with TWRP.
- Flashing the stock B09 update.zip without updater-script 'assert' and 'get-prop' line. TWRP says 'update.zip is corrupt'. Doesn't install.
- The I put it on SD card and internal memory and tried updating it with stock recovery: 'sorry you cant sdcard upgrade'. That's all it says.
- ADB sideload stock recovery: 'cannot load update.zip'.
I tried different ADB versions, Windows and Mac, different drivers... I tried formatting SD card as FAT32.. Tried different SD card.. Doesn't make a difference.
TWRP log says it can't pass the Zip verification when I try that. If I turn that off it says re.product.name is wrong. But I checked build.prop and updater-script. It's the same! But somehow TWRP comes up with a different one. Also tried removing getprop and assert lines from updater-script. But then it says: ZIP file is corrupt.
TWRP log after trying original, stock B09 flash:
http://pastebin.com/cJivE2TK
Build.prop: moved from /system with TWRP:
http://pastebin.com/b6rryc2n
Build.prop: ro.product.name=P996A03
Updater-script:
Code:
getprop("ro.product.device") == "ailsa_ii" || abort("This package is for \"ailsa_ii\" devices; this is a \"" + getprop("ro.product.device") + "\".");
assert(getprop("ro.product.name") == "P996A03");
But TWRP log: ro.product.name=cm_ailsa_ii
So, yeah, I've been trying on and off for the past couple of days in between work and travelling. Got a back-up phone so it's not that bad. But I really like this phone! It's just been such a pain in the ass the past few days...
I tried researching online and reading all the XDA posts. It is my fault this has happened and feel such a newb for not being able to fix it myself
Many thanks in advance!
Click to expand...
Click to collapse
PM I'll help you create a flashable zip base on B10 (Full update release), just make sure to have the following apps:
- 7Zip
- Notepad++
I am was rooting my axon a2017 on b10 chinnese version without any backup after rooting got password screen after boot then i was do factory reset and format data and all looking good but after that i saw that i dont have google play app so i installed macro gapps 6.0 after flashing phone stuck on axon screen (after zte logo) for long time i been wait up to 30 minutes and nothing was done..also i have the message on twrp about the modification(dont understand why i have this message all the time) i saw in xda forum that need to install supersu so i search on internet and was flash super su 2.65 and then when i am was boot device go to zte logo screen and then turning off when i connect the device as mtp device named as a2017u (whats worng with it??? I was flashed b10 root boot.img)
I regret about this root and want to back all to stock without any problems need help from someone
I need stock b10 boot.img if someone can upload
Many thanks!
---------- Post added at 04:23 AM ---------- Previous post was at 04:11 AM ----------
DrakenFX said:
PM I'll help you create a flashable zip base on B10 (Full update release), just make sure to have the following apps:
- 7Zip
- Notepad++
Click to expand...
Click to collapse
Its will help me too i think
Dear All,
ZTE Axon 7 A2017 (Chinese version) Stuck on Bootloader mode.
Device after power on will Stuck on ZTE logo even power button press longer also will Off and came back to square one and the only way to power off is via selection on bootloader page via volume button which consists of Recovery mode, Power Off, Bootloader and some other mode which I can't recall.
History of this issue. Please bear with long story.
Manage to install MM ROM with B13 via sd card installation via update software in phone setting. follow by Unlocked bootloader and Install TWRP 3.1.1.0 then try few different ROM until one day when I use Xiaomi flashtool my PC crash half way through during flashing resulting in device with Pure Chinese ROM and TWRP also got corrupted, when I said corrupted because I install TWRP 3.1.1.0 but when I go to Recovery mode it shows TWRP 3.0 something. with this corrupted TWRP when I try to install ROM it will show loading but end result is NIL meaning same ROM nothing change.
Until this stage I never did a TWRP backup because all this while the ROM is Not my type of ROM from this junction when I boot back to TWRP and I did Advance Wipe most of it except external sd card thinking that I may be able to install fresh TWRP but my Recovery TWRP is residing in phone storage resulting in No more TWRP recovery software. next thing I did was I connect phone to PC and ran adb fastboot tool to detect device and managed to detect device in recovery mode and I make decision to Locked back the bootloader and did just that and Locked bootloader is Succes and it also Erased everything during the process.
To cut short the story after Locked back bootloader only Bootloader mode is accessible and when I connect to PC and enable Recovery mode (Black screen) and EDL mode (Black screen) from Windows PC Device Manager COM port able to see Qualcomm 9008 for this 2 mode.
I must admit after few days of trying to resolve this Stuck Bootloader issue I almost give up.
Then I remember this Woodo magic by jcadduno which recommends XM flashtool version 2016.08.30.0 but unable to flash after trying few version Xiaomi flashtool and the very latest and I mean from Xiaomi Flashtool webpage http://xiaomiflashtool.com/
version 20170425 that break the ice and finally able to load A2017U ROM because this US ROM my phone No Network detected.
From here onwards I unlocked bootloader and install back TWRP (Installation of TWRP via Axon7toolkit) because of Network issue since I got TWRP I install back A2017 ROM but still Not satisfied because Chinese ROM certain Apps having issue because of Google services and I chance upon this Conversion A2017 to A2017U ROM (Hybrid ROM caused ROM is US and Modem from Chinese Modem)
that I'm stay put right now and my phone now is A2017U model.
I hope this experience can help others with similar Stuck bootloader and those who wish to convert A2017 to A2017U ROM.
below is the link that I described Woodo magic.
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
Straight forward Axon7toolkit, please don't use Chrome browser cause Chrome will Automatically Delete it after complete download for my case I used Microsoft Edge.
https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
below is the link to Hybrid ROM for A2017U
https://androidfilehost.com/?fid=457095661767154458 by Michael Warner After flash install No verity patch for the bootloader.
Cheers.
I am stuck in a position where I can restore my nandroid backups but get Error 7
when trying to reinstall any Rom on a2017u I was able to fix the unlocked bootloop
by the EDL method. The Rom's are the same as the backups. I think I tried to role back to B29 Causing the bootloop) and have had problems ever since.
Should I try flashing A2017Uv1.1.0B32_Bootstack_by_DrakenFX since the Rooms are all B32?
The B15 and B19 Nandroid's still Restore fine.
Hello all,
i don't get onto forums very often but i thought this was a nice one to add to. i've rooted a few motorolas, a few ztes, a cat; i've also bricked those ztes, cat & a few samsungs. i'm dealing with two Axon7U's; one is factory MM-b29, the other is N-b35.
while screwing around with TWRP, i bricked the b35 (the b29 has been bricked for a month at this time) after i had it almost perfected. by perfected i mean a custom recovery & root user access fully acquired. with DrakenFX's {YOURS; thanks so much. i'm learning to get along with linux} extensive files created to save people from themselves i was able to unbrick the b35. albeit its CELLULAR DATA became unhinged; that's something i could've lived with except it was a loaner and had NO CAMERA! it's camera (along with the ability to push both volume buttons at once for say EDL mode...) was damaged having been beaten across a steering wheel several times. so with my newfound unbricking superpowers i decided to take another crack at the b29. managed to get it unbricked but couldn't get it setup with both TWRP & SuperSU without losing one, the other or, both. at times it didn't even boot up. i was doing pretty much everything cited above for reasons 'why'. best way to learn is by trial & error (if one can afford it).
the b29 is rooted right at this moment; i'm working on it as soon as i leave this posting. i used Axon7_EDL_Tool. i used Axon7root. i used MiFlash. i used Fastboot. I used ADB App Controller software too. back & forth i fought for three days mostly due to downloading glitches and i prevailed. i manipulated a stock OTA full system update.zip by happenstance and it Auto_Updated over itself. in other words it already had the same ROM installed. i don't know what it tested to realize it needed to update to what it already had. it didn't have CELLULAR DATA either. just like the b35, it broke somehow while flashing TWRP or SuperSU. funny thing is it still wanted to update that same ROM after it did. while perusing the system update setting(s) i noticed it had downloaded N-b15 and it wanted to update b29 AGAIN! i opted for the Nougat update. it did alright and appears to have fixed it's CELLULAR DATA too. i haven't looked at it since but i'm confident i can gain root user access with a minimal amount of effort.
The main problem i've had with dealing with bricked devices is the age of the file downloads. most of them are simply GONE!, expired links and whatnot. if i'd had a clear path say from a custom recovery and rooted boot image of my factory version or the path that leads to it, i'd have been fixed up long ago. i've found partial 'paths' if you will that almost get me there but no quite all the way. flashing images & zips through fastboot are different from their counterparts entered through TWRP or Emergency Download Mode which of course are both different too. three different ways to get into one's phone makes it almost impossible to keep them perfected.
i'm not sure i did what i'm supposed to regarding this thread. Thank you DrakenFX for your time & knowledge; you've saved my old Axon7!
Hello all update;
b35 Nougat phone is retired. b29 managed to update itself to b35 7.1.1. however, its CELLULAR DATA is still broken. i haven't managed to figure out how or where it's broken so i cannot fix it.
what i'm trying to do now is flash Magisk instead of SuperSU and using a TWRP version 3.0.3-1. heck i've used all of TWRP's versions in my efforts to reacquire CELLULAR DATA.
crazy part is the phone knows its CELLULAR DATA carrier and freely displays all of its hookup info. this is very frustrating.
Hi,
1. If somebody experience this issue with lack of netwrok after Nougat full Rom update, like:
https://forum.xda-developers.com/showpost.php?p=71063185&postcount=121
than follow this fix from another thread:
https://forum.xda-developers.com/showpost.php?p=71054990&postcount=1456
for me it all seems to work fine now.
2. If somebody has issues with MiFlash, I think it is actually better to do the flash within first 5-10, after that it gives strange errors. If so, restrt EDL and press flash on MiFlash a bit faster .
Regards
I failed to boot nougat using these steps:
Boot to edl.
Flashed using miflash full b15 file and then b15 twrp file.
Flashed in twrp a2017 N modem.
Then it gets stuck at 5 secs screen and phone just reboots back to edl. Am i doing it wrong?
However it boots to nougat if only flashing just the b15 full.
Hi,
I had stock B13 Chinese. I MiFlahed fastboot_unlock packge,
did fastboot oem unlock,
MiFlashed B15 twrp,
copied NON-HLOS.bin file from Chinese modem(link above) into extracted B15 Full package folder(which replaced exsiting file in there) ,
reset dalvik etc.from twrp,
flashed B15 full which included already new modem file,
I let it boot finally till the end into standard mode.
This way I don't even have twrp now and all works fine.
Regards
RubiCom said:
Hi,
I had stock B13 Chinese. I MiFlahed fastboot_unlock packge,
did fastboot oem unlock,
MiFlashed B15 twrp,
copied NON-HLOS.bin file from Chinese modem(link above) into extracted B15 Full package folder(which replaced exsiting file in there) ,
reset dalvik etc.from twrp,
flashed B15 full which included already new modem file,
I let it boot finally till the end into standard mode.
This way I don't even have twrp now and all works fine.
Regards
Click to expand...
Click to collapse
Hi, what you mean you don't have twrp? Is it possible to install it somehow again? Is it possible to install SuperSU then? I'm asking this because I want to install A2017U B15 firmware (with OTA support) on A2017 (Chinese model with B13, stock recovery and locked bootloader) and just want to be sure in everything before I start Many thanks!
Wuchko said:
Hi, what you mean you don't have twrp? Is it possible to install it somehow again? Is it possible to install SuperSU then? I'm asking this because I want to install A2017U B15 firmware (with OTA support) on A2017 (Chinese model with B13, stock recovery and locked bootloader) and just want to be sure in everything before I start Many thanks!
Click to expand...
Click to collapse
Hi,
If you MiFlash B15 Full package it overwrites recovery partition...it is a full package after all. If you want TWRP on your nougat after that you need to Miflsh the B15 TWRP package. However inside the TWRP package, there is also modem driver file which you need to first replace with the new modem file, same as with B15 FULL package.
It is al soooo simple. I had some issues with MiFlash initially, as I read somewhere to "keep the vol up down, power fo 5 sec, release, wait 5seconds and than flash"
However I had near 100% success rate when I did press the flash button around 2-5 seconds after booting into EDL mode. Once you do oem unlock, the process is simple as burning ISO image on a CD
I have it now without that last step. It is unlocked, but without TWRP. I did however MiFlashed TWRP yesterday and it did work fine than as well. I don't however think I need TWRP anymore. I did Dalvik etc. reset during upgrading to Nougat... and that's all I needed it for. Maybe I'm wrong and I will MiFlash it again some day, but honestly, this was first time I flashed any Android phone as I come from Nokia- Windows Phone and all I wanted is working Daydream, Netflix VR for my long business flights. It works now. The rest I might need I will install from play store.
It does have that message about unlocked bootloader when you boot the phone, but it does not bother me and I read somewhere that it is better not to relock he phone.
How do I even know if it's OTA capable? When I checked updates, it says your phone is up to date.
Regards
Ok, now is everything much more clear to me, thank you!
Please help fellow china version users... @RubiCom
I have flashed b15 and the updated modem for china but my signal is still unusable. It keeps restarting the sim and when I go to sim settings, "com.android.phone" crashes. Some other settings related to calls/sim also crashes.
my sim is working fine when I'm on LOS. I really just want to use stock system since audio isn't fully fixed with LOS.
BTW, i'm already BL unlocked since b13. Do I still have to flash b15 twrp? I mean I could just fastboot flash twrp after installing full b15. Is there something special miflashing the b15 twrp package?
otaconremo said:
Please help fellow china version users... @RubiCom
I have flashed b15 and the updated modem for china but my signal is still unusable. It keeps restarting the sim and when I go to sim settings, "com.android.phone" crashes. Some other settings related to calls/sim also crashes.
my sim is working fine when I'm on LOS. I really just want to use stock system since audio isn't fully fixed with LOS.
BTW, i'm already BL unlocked since b13. Do I still have to flash b15 twrp? I mean I could just fastboot flash twrp after installing full b15. Is there something special miflashing the b15 twrp package?
Click to expand...
Click to collapse
I follow all the steps in original thread and after all everything works (at least for me) . But, it was a little bit complicated to make it work
So, first after unlocking I installed B15 TWRP, then entered into TWRP and deleted cache, dalvik, etc.. After that I put my phone into EDL again and flashed B15 original (I didn't boot phone to OS between flashing ROM's at all). But, on boot B15 original I still had some chinese symbols and I couldn't finish setup (phone stuck at google account setup). So, I repeated this three steps (installation of B15 TWRP, wiping everything in TWRP and installation of B15 original) again. This time I've got "android encrypted" or some similar message on boot B15 original(??!!), but after reboot everything was completely normal (except message that bootloader is unlocked, which is normal). I don't have TWRP, but 2G/3G/4G signal is great on both SIM's without lose and I have official updates. Comparing with chinese MM, this Nougat is far more better and faster, like I have a new phone
Wuchko said:
I follow all the steps in original thread and after all everything works (at least for me) . But, it was a little bit complicated to make it work
So, first after unlocking I installed B15 TWRP, then entered into TWRP and deleted cache, dalvik, etc.. After that I put my phone into EDL again and flashed B15 original (I didn't boot phone to OS between flashing ROM's at all). But, on boot B15 original I still had some chinese symbols and I couldn't finish setup (phone stuck at google account setup). So, I repeated this three steps (installation of B15 TWRP, wiping everything in TWRP and installation of B15 original) again. This time I've got "android encrypted" or some similar message on boot B15 original(??!!), but after reboot everything was completely normal (except message that bootloader is unlocked, which is normal). I don't have TWRP, but 2G/3G/4G signal is great on both SIM's without lose and I have official updates. Comparing with chinese MM, this Nougat is far more better and faster, like I have a new phone
Click to expand...
Click to collapse
I figured out what's wrong my my setup but still I can't find a way to fix this.
It seems that when I use my original sim cards (2 sims with the same provider), they both get disconnected every second.
When I put another sim from another provider, it does work but still my original sim doesn't get signal. even when changing slots.
I'm really confused how to make them work together.
otaconremo said:
I figured out what's wrong my my setup but still I can't find a way to fix this.
It seems that when I use my original sim cards (2 sims with the same provider), they both get disconnected every second.
When I put another sim from another provider, it does work but still my original sim doesn't get signal. even when changing slots.
I'm really confused how to make them work together.
Click to expand...
Click to collapse
That's weird. I'm also using SIM's from same providers, but without any problems.. Don't know what to tell, maybe you can try install B15 TWRP and wipe everything, then install B15 original and try again.. First time I also had some weird problems...
Wuchko said:
That's weird. I'm also using SIM's from same providers, but without any problems.. Don't know what to tell, maybe you can try install B15 TWRP and wipe everything, then install B15 original and try again.. First time I also had some weird problems...
Click to expand...
Click to collapse
this is actually wierd. I had this problem my my sims. And I had flashed this many times already trying out different methods including miflash and even stock flashable zips from draken. all yields to the same results.
Do you have any idea where to tweak carrier settings from system files? i tried *#*#4636*#*# but still fails.
Unfortunately I don't know it. I guess I had plenty of luck flashing these ROM's, considering how many people have problems..
Hi, I met some problems with my Nova plus mla-al10.
In short, the phone cannot boot and I need help with getting the offical emui5.0 dload upgrade package. (probably)
Below is the whole story:
1. The phone is unlocked.
2. Upgraded emui4 180 to emui5 in the emui4 system. The system indicated the target version is emui5 352. After updated, my version turned into NRD 90M test-keys without many huawei custom apps. ( I think it's because of the lack of data-update package, but it's too late now)
3. I tried to solve the version problem and I flashed the phone through fastboot with RECOVERY, BOOT, SYSTEM & CUST extracted from the downloded update packages. ( First 358, later I tried several other versions, same failing)
4. Then I cannot boot my phone. Just enter erecovery after 2nd reboot, and I cannot get the Rom downloaded through erecovery. Error reported.
5. Then I tried the dload update mode with a certain emui4 dload rom which I can only got from the internet for the MLA version. I cannot make sure what the ROM version was, like b122 or b133, emui4. I failed during update in the official recovery. 5%, 45% ,several times.
6. So I tried to use the twrp and both lineage and asop rom from #Henkate. Thank you #Henkate, the phone booted again. The system worked fine, except for one problem: When I use the China mobile(TD-LTE) and China unicom(WCDMA/LTE), I cannot dial out or dial in ( busy line). The sms and data(internet) worked fine. The signal is good. The sim card seemed to be successfully registered. China telecom seems worked fine(FDD-LTE) with dialing, sms and network. By the way, the china telecom simcard is the first card I used in the first lineage's first boot. I just found it abnormal with the problem above recent days.
7. Then I flashed the asop from #Henkate after wiping the system, cache and data. The same problem.
8. Now I cannot get where the problem is. I guess maybe the baseband software got wrong, so I wanted to flash the modem.img into the phone. The only way I think possible is to flash the dload package with version above 358 (or 360 which I also flashed through fastboot)through the huawei official recovery. The question is where I can get the package and is it the right thing to do? If not, how can I get back to the offical EMUI or other roms functioning normally?
Please help!
Thank you in advance!
Hello all
I installed the latest T585XXU4CRJ8 Oreo 8.1 update over Nougat 7 on the SM-T585. (BTU / UK)
Everything went well using Odin and the Oreo stock rom from the Updato website.
Cleared the cache and factory reset from recovery mode as normal practice. Booted up ok.
The problem is the device doesn't recognise the network sim card anymore (worked perfectly on Marshmallow & Nougat).
I've tried factory reset a few times, no difference.
Removed and reinserted the sim, even tried another sim.
Having checked 'about tablet > software details' , carrier is unknown and the IMEI has dissapeared !
I've tried to reinstall Nougat 7 and Marshmallow 6 back on the SM-T585 and Odin fails every time.
Tried 2 computers and 3 different usb cables.
Even trying to reinstall Oreo 8.1 again Odin fails!
Theres no frp lock activated, and the oem unlock tab is checked, usb debugging enabled too.
I've read somewhere Samsung have done something to Oreos BootLoader file to stop people downgrading back to earlier software.
I know its early days, but if anyone can offer any solutions, it'd be appreciated.:good:
How to change the BL file version, so i can reinstall earlier stock roms back?
The Oreo update seems more hassle than its worth and I didnt expect the sim card to be unrecognised once updated, let alone being faced with the puzzle of how to downgrade the software.
Thanks for reading. :good:
I think the problem was I used all four files (AP, BL,CP & CSC) from the Netherlands rom and that's whats screwed the device up!
As in no SIM card acknowledgement. I ran the IMEI number off the rear casing through a blacklist checking site and it came back clean.
After many attempts trying every Odin program variant possible and even tried mixing and matching files from different stock roms ( MM 6.0.1 , N7 and Oreo 8.1). To try and get the network carrier file installed, Odin refused to install anything.
https://desktop.firmware.mobi/device:754/firmware:1660
https://download.chainfire.eu/1069/CF-Root/CF-Auto-Root/CF-Auto-Root-gtaxllte-gtaxlltexx-smt585.zip
https://twrp.me/samsung/samsunggalaxytaba101wifi2016.html
Tried the above routes to root to no avail, but Magisk worked by patching the boot.img file (which worked ok). Then tried Odin to install TWRP recovery, again from the site above, nothing but blue and fuzzy lines on the boot screen. The device wouldn't boot into the OS, had to go straight to download mode. Prior to that, I even installed the TWRP manager apk and connected to wifi to flash the TWRP.img from inside the OS environment and the same happened again with all variants of TWRP! Wouldn't boot, properly, no screen visuals, but lines......
Surely someone else on here has the same device (BTU UK) SM T585 that has a working TWRP recovery?
After many hours, I couldn't get Odin to play ball , so the only option left was to try the route of root, twrp recovery then installing a custom rom from twrp.
(https://forum.xda-developers.com/ga...-ultra-lean-rom-galaxy-tab-10-1-2016-t3467942)
But it's a no go as TWRP wouldn't install properly, I'm totally miffed by the damage the software has done.
Surely just reflashing the CP file should have reinstated the network facility, but it hasn't.
The last resort is for me to wait until Samsung actually release the UK version of Oreo 8.1 and see if I can get the sim card working again.
Moral of the story is wait until a UK version of the update is released, and even then you have to question is it worth it, if Samsung are making bootloader files so no downgrades are possible, nor allowing any modifications.
Hopefully this info may help others out who are thinking of upgrading or having similar issues.
Cheers for reading
tsam19 said:
I think the problem was I used all four files (AP, BL,CP & CSC) from the Netherlands rom and that's whats screwed the device up!
As in no SIM card acknowledgement. I ran the IMEI number off the rear casing through a blacklist checking site and it came back clean.
After many attempts trying every Odin program variant possible and even tried mixing and matching files from different stock roms ( MM 6.0.1 , N7 and Oreo 8.1). To try and get the network carrier file installed, Odin refused to install anything.
https://desktop.firmware.mobi/device:754/firmware:1660
https://download.chainfire.eu/1069/CF-Root/CF-Auto-Root/CF-Auto-Root-gtaxllte-gtaxlltexx-smt585.zip
https://twrp.me/samsung/samsunggalaxytaba101wifi2016.html
Tried the above routes to root to no avail, but Magisk worked by patching the boot.img file (which worked ok). Then tried Odin to install TWRP recovery, again from the site above, nothing but blue and fuzzy lines on the boot screen. The device wouldn't boot into the OS, had to go straight to download mode. Prior to that, I even installed the TWRP manager apk and connected to wifi to flash the TWRP.img from inside the OS environment and the same happened again with all variants of TWRP! Wouldn't boot, properly, no screen visuals, but lines......
Surely someone else on here has the same device (BTU UK) SM T585 that has a working TWRP recovery?
After many hours, I couldn't get Odin to play ball , so the only option left was to try the route of root, twrp recovery then installing a custom rom from twrp.
(https://forum.xda-developers.com/ga...-ultra-lean-rom-galaxy-tab-10-1-2016-t3467942)
But it's a no go as TWRP wouldn't install properly, I'm totally miffed by the damage the software has done.
Surely just reflashing the CP file should have reinstated the network facility, but it hasn't.
The last resort is for me to wait until Samsung actually release the UK version of Oreo 8.1 and see if I can get the sim card working again.
Moral of the story is wait until a UK version of the update is released, and even then you have to question is it worth it, if Samsung are making bootloader files so no downgrades are possible, nor allowing any modifications.
Hopefully this info may help others out who are thinking of upgrading or having similar issues.
Cheers for reading
Click to expand...
Click to collapse
I had the same problem, went from Lineage 14.1 to Oreo stock rom (the flashable one you can find on this site, i flashed also the Bootloader/modem file in the thread). No imei, no baseband. Returned back to lineage and got back imei and baseband, but after my screen was going to sleep (after the regular 1 min) I had only black screen and vertical red lines. I flashed then Resurrection Remix 6.2, Lineage 15, Lineage 16, always the same problem. Then I used Odin and the original firmware of Nougat from SamMobile, at the first attempt i flashed only the AP file. I turned to have the same problem, but this time the lines were white. I flashed all the 4 files again with Odin, problem solved and back to Lineage 14.1 (the only custom rom were everything works)
Domenico F.
What version of TWRP have you installed for the T585 and from what site?
Also what root method did you use?
I have tried all available and all seem corrupt i.e don't install properly, no proper boot up with onscreen options. Just fuzzy lines.
Again root i've tried many, but don't work with this Oreo 8.1., even Magisk is problematic.
I think its pretty sad of Samsung sending out poor quality updates for us to use. Their heading the same way as Apple and the way they control customers.
If I could go back to a custom MM or Nougat, I would. But TWRP / ROOT are an issue. i.e no TWRP no custom rom!
If anyones thinking of updating and reading this topic, stay clear of the Oreo 8.1 update for the SM T585. Once installed theres no turning back.....so it seems
Thanks for replying.
tsam19 said:
Domenico F.
What version of TWRP have you installed for the T585 and from what site?
Also what root method did you use?
I have tried all available and all seem corrupt i.e don't install properly, no proper boot up with onscreen options. Just fuzzy lines.
Again root i've tried many, but don't work with this Oreo 8.1., even Magisk is problematic.
I think its pretty sad of Samsung sending out poor quality updates for us to use. Their heading the same way as Apple and the way they control customers.
If I could go back to a custom MM or Nougat, I would. But TWRP / ROOT are an issue. i.e no TWRP no custom rom!
If anyones thinking of updating and reading this topic, stay clear of the Oreo 8.1 update for the SM T585. Once installed theres no turning back.....so it seems
Thanks for replying.
Click to expand...
Click to collapse
just flash the nougat firmware from SamMobile. You have to flash all the 4 files in the zip you are going to download. AP, CSC, etc. Once you have your tablet completely stock you can install again TWRP and flash whatever CUSTOM rom you want.
I easily rooted the phone with odin flashing only the TWRP in AP box (twrp taken from this post https://forum.xda-developers.com/showpost.php?p=78145080&postcount=160) avoid the auto-reboot. You have to put the tab in DL mode, connect it to pc, start odin flash the twrp in AP file e unselect Auto-reboot. As soon as the process is done you have to log in recovery mode at the first boot with home + power + vol up and flash dm-verity. I rooted with Magisk without any problem just flashing the v17.3. Now i' m back to nougat (from Oreo) and i can install whatever custom rom i want. But honestly the only one fully working is Lineage 14.1. Resurrection remix 6.2 has problem with camera and gps don't lock. Same for Oreo version. Tried Pie, same problem.
Domenico F
Thanks for the info.
I tried to install MM 6.01 & Nougat 7 stock rom and they wouldn't install, no matter what I did. ( see Odin pictures )
The last chance was to try Oreo 8.1 again and I did manage to reflash the 'Netherlands stock Oreo 8.1 rom' (after 10 hours!) using all four files (AP,BL,CP,CSC).
I then reset the device a couple of times via stock recovery. Took the OEM lock off, theres no FRP lock either. Enabled developer mode > debug mode (all the usual setting changes prior to rooting / twrp install).
At this point the imei and sim card network ARE recognised and work on the device as normal.
HOWEVER I found once I rooted by any genuine means > Magisk v16 (patched boot img taken from stock rom) and also the CF gtaxlltex sm t585 auto root method.
And when the device booted back up, the 'imei and sim card' WERE NOT usable, nor recognised, no network...........I also noticed BusyBox wouldn't install at all, message about integrity of root.
Adaway and Lucky Patcher recognised root.
I also then tried installing TWRP 3.0.2.0 -3.2.3.0 from many locations and again, none of them worked at all. Just blue lines, fuzzy screen etc. On some occasions Odin wouldn't even process the files.
I include pictures of the files I used.
Its evident to me that I can use the device normally i.e sim card , make calls, data etc if I don't attempt to install root / twrp recovery.
So no root , no twrp , then no custom rom usable or installable. It sounds like Samsung are out to stop custom software on their products.
If the Netherlands stock rom 'BL' (boot loader) file is encrypted with this new binary v3 or v4 to stop OS modifications. I wouldn't recommend using it when flashing the new Oreo 8.1 rom or future new releases.
The best way is to just use the AP file ONLY and overlap Nougat 7 or MM 6. And because you've kept your original BL from earlier stock roms, it may be possible to downgrade back to MM or Nougat if need be.
Once the latest new Oreo / Pie 'BL files' are used in the Odin flashing process, it causes big problems.
Hopefully, maybe someone smart enough can find away to decipher these new BL files and offer a replacement method. which will allow software downgrades and modifications
tsam19 said:
Domenico F
Thanks for the info.
I tried to install MM 6.01 & Nougat 7 stock rom and they wouldn't install, no matter what I did. ( see Odin pictures )
The last chance was to try Oreo 8.1 again and I did manage to reflash the 'Netherlands stock Oreo 8.1 rom' (after 10 hours!) using all four files (AP,BL,CP,CSC).
I then reset the device a couple of times via stock recovery. Took the OEM lock off, theres no FRP lock either. Enabled developer mode > debug mode (all the usual setting changes prior to rooting / twrp install).
At this point the imei and sim card network ARE recognised and work on the device as normal.
HOWEVER I found once I rooted by any genuine means > Magisk v16 (patched boot img taken from stock rom) and also the CF gtaxlltex sm t585 auto root method.
And when the device booted back up, the 'imei and sim card' WERE NOT usable, nor recognised, no network...........I also noticed BusyBox wouldn't install at all, message about integrity of root.
Adaway and Lucky Patcher recognised root.
I also then tried installing TWRP 3.0.2.0 -3.2.3.0 from many locations and again, none of them worked at all. Just blue lines, fuzzy screen etc. On some occasions Odin wouldn't even process the files.
I include pictures of the files I used.
Its evident to me that I can use the device normally i.e sim card , make calls, data etc if I don't attempt to install root / twrp recovery.
So no root , no twrp , then no custom rom usable or installable. It sounds like Samsung are out to stop custom software on their products.
If the Netherlands stock rom 'BL' (boot loader) file is encrypted with this new binary v3 or v4 to stop OS modifications. I wouldn't recommend using it when flashing the new Oreo 8.1 rom or future new releases.
The best way is to just use the AP file ONLY and overlap Nougat 7 or MM 6. And because you've kept your original BL from earlier stock roms, it may be possible to downgrade back to MM or Nougat if need be.
Once the latest new Oreo / Pie 'BL files' are used in the Odin flashing process, it causes big problems.
Hopefully, maybe someone smart enough can find away to decipher these new BL files and offer a replacement method. which will allow software downgrades and modifications
Click to expand...
Click to collapse
Honestly i think this run for Oreo it's not really worth. I said you what I did and now i have no problems. I'm not in hurry to use Oreo (as stock rom). I think Lineage 14.1 is the most stable and fastest rom i tried till now, and most of all everything is working. I think i'll give a try via Odin to the official stock rom when it will be available for download (i live in Germany) but sadly I don't use most of the Samsung bloatware installed by default.
WRP Oreo 8.1 on Galaxy Tab 10.1 (T585)
Then I've tried
twrp_3.2.3-1_sm-t585_29918 which gives only stripes when booting into recovery
Do I have to flash the stock boot/recovery before flashing this one,
or this is broken, as well.
Many thanks for a hint,
Helmut
Hope this helps.
So, as I was trying to search for my Galaxy Tab A6 (SM-T585) for Deodexed Stock ROM, I stumbled upon this thread https://forum.xda-developers.com/galaxy-tab-a/themes/mod-twrp-odin-t3650215 just follow the instructions to fully flash Oreo. By the way when flashing Root, I would recommend Magisk Beta https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
it does not damage the IMEI at all(Thread here, read the comment:https: //forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445) . The TWRP, I think we should leave it be, don't flash an update for the TWRP.
Thanks. Hope this helps.
MiaMOTo SU # said:
By the way when flashing Root, I would recommend Magisk Beta https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
it does not damage the IMEI at all
Click to expand...
Click to collapse
Neither does a custom recovery, so not sure what your point is?
I mean if your having problems using MAGISK use the beta version
Hi
I fixed my oneplus 5 using MSMdownload tool. It put my phone on Android 7.1.1 with July 1st, 2017 security Patch and Oxygen OS 4.5.8, I have exhausted all the option to upgrade it to latest Android but it won't update. Every time I check for update it will show that it is up to date. I have also tried "local Upgrade" option but it shows installation failed.
Any work around this would be highly appreciated
Thanks
Aman
@lucider14 Just curious why you used the MSMDownloadTool from OxygenOS 4.5.8 and not the one for OxygenOS 9.0.11? You most likely won't see OTAs for Android 7 as it is now 4 Android Versions behind as of this week. Android 9.0.11 was the last official fully released OTA, OxygenOS 10.0.0 Hotfix is last official OTA OnePlus has released into the wild.
My phone waa bricked so had to use it. Please let me know if there is any workaround for this to update.
@lucider14 The workarounds I would try are:
Opt 1: Upgrade via zip file in Stock Recovery
Step 1: Download latest OTA from https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Step 2: Copy zip file to root of Phone storage
Step 3: Reboot into Recovery
Step 4: Install
Opt 2: Use Newer MSMDownloadTool:
Step 1: Download newest tool from here https://forum.xda-developers.com/oneplus-5/how-to/op5-collection-unbrick-tools-t3898870
Step 2: Reboot phone into EDL
Step 3: Run newer MSMDownloadTool
card13;83478941 [user=11104643 said:
@lucider14[/user] The workarounds I would try are:
Opt 1: Upgrade via zip file in Stock Recovery
Step 1: Download latest OTA from https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Step 2: Copy zip file to root of Phone storage
Step 3: Reboot into Recovery
Step 4: Install
Opt 2: Use Newer MSMDownloadTool:
Step 1: Download newest tool from here https://forum.xda-developers.com/oneplus-5/how-to/op5-collection-unbrick-tools-t3898870
Step 2: Reboot phone into EDL
Step 3: Run newer MSMDownloadTool
Click to expand...
Click to collapse
@lucider14 OOS 4.5.8 is pre-treble. You can't jump directly to Android 9 or 10. One of the OOS updates before Android 9 set up treble on our phones. I don remember exactly which one. You're best to use Opt 2 above, it will be easier.
Cheers!?
lucider14 said:
Hi
I fixed my oneplus 5 using MSMdownload tool. It put my phone on Android 7.1.1 with July 1st, 2017 security Patch and Oxygen OS 4.5.8, I have exhausted all the option to upgrade it to latest Android but it won't update. Every time I check for update it will show that it is up to date. I have also tried "local Upgrade" option but it shows installation failed.
Any work around this would be highly appreciated
Thanks
Aman
Click to expand...
Click to collapse
First,flash it 9.0.11 build and then OxygenOS 10.0.0 Hotfix..
And with https://play.google.com/store/apps/details?id=com.arjanvlek.oxygenupdater
I've had a similar problem and I thought I broke my phone, got pretty scared can't buy a new phone but need a newer android for my apps to work.
I came from freedom OS on android 7 so I never had the project treble on my phone and tried to flash new factory images, as a result, no newer TWRP recovery worked and I was unable to boot into anything other than the bootloader. I had the same error with Error 7, from what I can understand this is from a screwed up or non-existing "vendor" partition which says stuff like "this is a OnePlus 5" for newer factory images to install (factory image told me I didn't have a OP5), this never existed in android 7 or OOS 4.X.X. ScRuFFy7 is correct, the vender partition was created in OOS 5.1.4 (or OTA 037) and only when android is booting up, this took like 10 mins on mine. Once this vendor partition is correctly created you can flash newer TWRP recovery (I flashed 3.4.0) and newer factory images, like OOS 9.0.11 then to version 10. The built-in updater and stock recovery can update to the newer versions with the flashable zip files. For whatever reason OnePlus don't size the partitions in their zips so they make small changes from one version to the next so skipping specfic versions throws up errors in the future.
Screw it, I should document what I did in case I mess up my phone in the future and maybe be helpful to someone else in need, especially in this messed up and depressing time of the plague. But anyway this is what I did to get my phone back, I should point out I have no idea what I'm doing. Meaning I'm a N00b.
NOTE: this process Wipes all the data from the phone, so I hope you have backups right now.
Will need ADB, you can install This on windows, it's super easy and works thanks to mauronofrio. You can get the all in one tool too from here it's pretty handy and can format and decrypt from the bootloader, from mauronofrio? I think? This guy is pretty good. I got all old firmware from Here thanks to Some_Random_Username for the life line since OnePlus won't provide the old Zips anymore.
1) Boot to TWRP recovery if you have it installed (VOL DOWN + POWER). If not Boot to Bootloader (VOL UP + POWER) and flash TWRP Recovery. You can use TWRP 3.1.1 This one works on OOS 4.X firmware without giving me a Black Screen.
1a) To Flash the Recovery you can use the all in one tool to flash it or open up command prompt and use the Fastboot Flash [insert recovery file name here .img] command to flash it, you can find the FastBoot Flashing Method in the middle of this page for instructions.
2) Format Data. The Format Data button in TWRP recovery not the swipe to factory reset, because we're going back to scratch.
3) Flash OTA_006 (OOS 4.5.2) original firmware from the link above (says ota_006 in the middle of the loong file name)
4) Boot into android and use System Update in settings and stock recovery it just flashed to flash OTA_020 (OOS 4.5.15) by clicking on the cogwheel in the corner and choosing Local Update. [probably skippable I just wanted to make sure it works]
5) Boot into android again and install OTA_27 (OOS 5.0) with System Update again.
6) If it doesn't boot, go to Bootloader and flash TWRP. Once in the recovery and you go to install and if you find all the folders have random numbers and letters for names then the storage in encrypted.
7) Format to get rid of encryption (random name folders) then reboot to Recovery and Flash OTA_27 again and let it start fresh on OOS 5.0 to make sure it's still booting and working.
8) Once booted Flash OTA_037 (OOS 5.1.4) wait for vendor partition to be created (took 10 mins on my OP5), reboot to TWRP and format if folders are encrypted and reflash OTA_037 if needed.
Once booted into android this is the point where you should have the Vendor Partition already created by the factory image, you can go back into TWRP (flash TWRP if needed) and under Mount be able to see, mount/unmount a Vendor partition without errors. This should solve the Error 7 problem with factory images. A newer version of TWRP Recovery should work now, I installed 3.4.0 from mauronofrio Here. 3.4.0 works with android 10.0 so I was glad.
9) Boot android again and flash OTA_038 (OOS 5.1.5) just to make sure with stock recovery. [Probably skippable but I was a Paranoid Android at this point, just to make sure it still works]
10) Boot to android again and install OTA_042 (OOS 9.0.0) with System Update to keep making sure it works. [Again, I was Paranoid. Probably Skippable]
11) Boot to android again and install OTA_054 (OOS9.0.11) as last Android 9 update to have things set up ok.
12) Boot into Android again and install the latest android 10 from OnePlus (OTA_068) with System Update and the Stock Recovery, this is Android 10.0.0 and OOS 10.0.0. Things should work fine at this point but I doubt the check for update will get new oneplus updates. As of Sep 25, 2020 it is up to date. Technically.
I should add something else I discovered after. I found a flashable zip file from one of the lineage OS posts of a oneplus5_vendor_5.1.5.zip Here. You might be able to just use that to create the Vendor partition then just Flash one of the OOS 5.X Firmwares and go from there, I've not tried it so I'm not 100% sure but it's a possibility?
Hope this is helpful to someone at some point in time. for troubleshooting at least. Honestly really glad I have a working phone right now.