Related
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..
Plzzz help im stuck I want to rollback my huawei p9 lite VNS-L31 where its build number is NRD90M(test keys) to marshmallow 6.0 help don't know what to do . Plz if you can explain step by step what can i do because i'm not good in these things , My bluetooth not workng , there no calculator , no software updater , i am not able to check if got update or not and so on......, im stuck plz help
Well hey.. first download this rollback package from this link:
http://download-c1.huawei.com/download/downloadCenter?downloadId=93645&version=371484&siteCode=np
Extract and move all the files to dload folder on your external SD Card then install it with the 3 button method. If there's no dload folder then create one.
So the phone will reboot and now you can downgrade to any mm rom
Now just download this mm rom from this link:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1164/g104/v66015/f1/full/update.zip
And again extract and move the files to dload folder on your sd card.. Install with 3 button method.
Done! Everything should work now!
In case If you don't know what the 3 button method is..lol
•Power the phone off ?
•Just press and hold on POWER + VOLUME UP + VOLUME DOWN buttons
The phone will start installing the rom and that's the 3 button method ?❤
this is not working for me. it says incompatibility with current version and to download the correct version.
lennie27 said:
this is not working for me. it says incompatibility with current version and to download the correct version.
Click to expand...
Click to collapse
Man, you have to do entire procedure: unlock bootloader, install twrp for Nougat and flash oeminfo for your phone. Before that you have to put in dload folder MM firmware (B130/B131),
because after flashing oeminfo phone try to repair firmware from dload folder. If repair do not start, power off phone and power on with 3 keys combination.
Hi All,
I'm having a similar issue as lennie27 however I think I might have strayed down an incorrect path during the process of upgrading to Nougat. My device shipped with VNS-L31C16B120 with no updates available through the stock updater. I tried the Firmware Finder guides which listed options for VNS-L31C169B13x and VNS-L31C432B13x however none of these updates would work, updater would say it's incompatible with current version. I also tried manually downloading the VNS-L31C432B160 firmware and installing that with the 3 button method as well as the EngineerMenu option with the same result (found guides that stated needing to be on B160 or B161 before making the jump to Nougat). Eventually I decided to unlock the bootloader and install Nougat through TWRP and followed the obeygeekupdate-huawei-p9-lite-to-android-7-0-nougat-manually guide (can't post links ) on manually installing Nougat (stupidly never paying attention to the fact that it's a beta build guide). I've installed TWRP to the device again using the P9 Lite Toolkit v0.0.0.11 found here on XDA (used this when on MM however the upgrade seemed to restore the stock recovery) with the idea of downloading the build from the ministryofsolutions huawei-p9-lite-vns-l31-nougat-b371-update-stable-europe page and pushing that to the device instead (however now the device doesn't want to boot into recovery)
Now my only concern is, will this work? I've noticed a bit of commenting going back and forth on the ministryofsolutions site which essentially boiled down to the need for debranding the phone (apparently C19 is MTN South Africa specific and I need to debrand it and get it onto C432 Europe before mucking about with Nougat, but alas to late) which seemed to be something I should have done while on MM still. If I can find a full firmware link for VNS-L31C16B120 can I flash that through TWRP without needing to follow any prerequisite steps? So far nothing that I've tried to flash using the three button method has worked, I'd just like to get back onto an official stable firmware again.
Any advice will be appreciated
saintnite said:
Hi All,
I'm having a similar issue as lennie27 however I think I might have strayed down an incorrect path during the process of upgrading to Nougat. My device shipped with VNS-L31C16B120 with no updates available through the stock updater. I tried the Firmware Finder guides which listed options for VNS-L31C169B13x and VNS-L31C432B13x however none of these updates would work, updater would say it's incompatible with current version. I also tried manually downloading the VNS-L31C432B160 firmware and installing that with the 3 button method as well as the EngineerMenu option with the same result (found guides that stated needing to be on B160 or B161 before making the jump to Nougat). Eventually I decided to unlock the bootloader and install Nougat through TWRP and followed the obeygeekupdate-huawei-p9-lite-to-android-7-0-nougat-manually guide (can't post links ) on manually installing Nougat (stupidly never paying attention to the fact that it's a beta build guide). I've installed TWRP to the device again using the P9 Lite Toolkit v0.0.0.11 found here on XDA (used this when on MM however the upgrade seemed to restore the stock recovery) with the idea of downloading the build from the ministryofsolutions huawei-p9-lite-vns-l31-nougat-b371-update-stable-europe page and pushing that to the device instead (however now the device doesn't want to boot into recovery)
Now my only concern is, will this work? I've noticed a bit of commenting going back and forth on the ministryofsolutions site which essentially boiled down to the need for debranding the phone (apparently C19 is MTN South Africa specific and I need to debrand it and get it onto C432 Europe before mucking about with Nougat, but alas to late) which seemed to be something I should have done while on MM still. If I can find a full firmware link for VNS-L31C16B120 can I flash that through TWRP without needing to follow any prerequisite steps? So far nothing that I've tried to flash using the three button method has worked, I'd just like to get back onto an official stable firmware again.
Any advice will be appreciated
Click to expand...
Click to collapse
you need to install nougat recovery, not the one from the toolkit. then twrp will work and the device will boot.
to go back to 120 you need to install oeminfo, and then the update.app
mjz2cool said:
you need to install nougat recovery, not the one from the toolkit. then twrp will work and the device will boot.
to go back to 120 you need to install oeminfo, and then the update.app
Click to expand...
Click to collapse
Thank you for the reply, managed to come right a few hours after posting. Turned out the copy of TWRP that I had on hand was more outdated than I thought, downloaded the newest copy and that worked on the device. Additionally I managed to find a website listing just about every firmware for the phone (Including my original MTN ZA specific variant) so I downloaded that and managed to restore the phone using the three button method. Phone is back to stock now and even the unlocked bootloader nag screen is gone so I'm guessing the bootloader is locked again as well One day when I'm brave enough to attempt this again I'll look at debranding the phone and getting it onto a C432 based ROM before getting it onto Nougat again.
phone bricked
hello guys! im currently on lineage os 14.1 by meticulus, i wanna revert back to stock mm but i cant. i flashed the custom rom from mm using twrp recovery by meticulus, but now i cant even boot into erecovery! can you pls help me!:crying: DLOAD method doesnt work!
Hi
I got my self in quite a pickle here..
so advice or help is very welcomed.
I own a Huawei P10 lite,
with a software version WAS-LX1AC900B049
First off I unlocked the phone, then flashed TWRP recovery, and thus far everything was ok
I wanted to install Lineage 14.1 OS, and I failed because my version of the phone is not supported..
but during attempt installation of Lineage OS , I deleted data, system, dalvik, and cashe..
I did not make a backup!!! (major mistake, I know..)
so effectively I deleted my OS :-/ ..
but it isn’t over jet..
because I could not find a stock rom, namely WAS-LX1AC900B049 version
I thought of debranding my phone to Orange, namely WAS-LX1AC109B110 because stock roms for Orange are available on the net.
so.. using TWRP I replaced oeminfo file..
(this time making a backup of oeminfo)
but once I downloaded Orange stock rom, put it on the
sdcard in /dload folder and entered download mode on the phone, nothing happened, update failed
but.. also changing oeminfo resets the system so I guess that turned off USB debugging..
so now the TWRP is not available because of the system reset, and in the fastboot and rescue mode , adb program from Windows, does not detect device..
so..
it seems I have 3 options..
1. somehow install Orange stock rom
2. make fastboot and rescue mode to work properly so I can reinstall TWRP and go further from there
3. find original stock rom WAS-LX1AC900B049, may be it will work
by the way erecovery does not work, it conects to the wifi, starts serching, and then fails
Help please..
I unbricked the phone
for anyone interested I used adb to unlock the phone in fastboot and rescue mode..
the phone was showing me a message that it was unlocked but it was not
once unlocked previously installed TWRP booted immediately, so from there I installed Lineage 14.1 by HassanMirza01 and it works great
Happy that you fixed your problem but how did adb detected your device as you mentioned it didn't at the first place?
Planning on going back to stock and I think the same trouble would happen for me too.
oH MY GOD!
ultragorki said:
Hi
I got my self in quite a pickle here..
so advice or help is very welcomed.
I own a Huawei P10 lite,
with a software version WAS-LX1AC900B049
First off I unlocked the phone, then flashed TWRP recovery, and thus far everything was ok
I wanted to install Lineage 14.1 OS, and I failed because my version of the phone is not supported..
but during attempt installation of Lineage OS , I deleted data, system, dalvik, and cashe..
I did not make a backup!!! (major mistake, I know..)
so effectively I deleted my OS :-/ ..
but it isn’t over jet..
because I could not find a stock rom, namely WAS-LX1AC900B049 version
I thought of debranding my phone to Orange, namely WAS-LX1AC109B110 because stock roms for Orange are available on the net.
so.. using TWRP I replaced oeminfo file..
(this time making a backup of oeminfo)
but once I downloaded Orange stock rom, put it on the
sdcard in /dload folder and entered download mode on the phone, nothing happened, update failed
but.. also changing oeminfo resets the system so I guess that turned off USB debugging..
so now the TWRP is not available because of the system reset, and in the fastboot and rescue mode , adb program from Windows, does not detect device..
so..
it seems I have 3 options..
1. somehow install Orange stock rom
2. make fastboot and rescue mode to work properly so I can reinstall TWRP and go further from there
3. find original stock rom WAS-LX1AC900B049, may be it will work
by the way erecovery does not work, it conects to the wifi, starts serching, and then fails
Help please..
Click to expand...
Click to collapse
YOU DID AS EXACTELLY AS ME ...HAHAHAHAHAHAHAH and now im still tryiong to find it solutution ...have you found some?
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
Hello,
Recently a Huawei P9 lite VNS-L21 came into my hands. I experimented a bit with unofficial ROMs but eventually flashed the official back. I had flashed an earlier version, ending in 380 I believe, but because the phone attempted to upgrade to the next incremental update (say, -382) I decided to upgrade myself to the latest supported version (506). I used Firmware Finder to find the firmware and downloaded it to SD card.
Upgrade succeeded - since I had left TWRP recovery in the phone, I used the HuRUpdater which worked flawlessly.
The only small issue is that following this update, a red message is displayed on boot saying the device has failed verification.
Any way to solve this?
Sovjohn said:
Hello,
Recently a Huawei P9 lite VNS-L21 came into my hands. I experimented a bit with unofficial ROMs but eventually flashed the official back. I had flashed an earlier version, ending in 380 I believe, but because the phone attempted to upgrade to the next incremental update (say, -382) I decided to upgrade myself to the latest supported version (506). I used Firmware Finder to find the firmware and downloaded it to SD card.
Upgrade succeeded - since I had left TWRP recovery in the phone, I used the HuRUpdater which worked flawlessly.
The only small issue is that following this update, a red message is displayed on boot saying the device has failed verification.
Any way to solve this?
Click to expand...
Click to collapse
Hello,
my doubt is that you flashed a different firmware version from the one you had, thus corrupting the device's oem file. Could you post which was the latest complete firmware without this problem and the last one you downloaded and flashed? ( ex. L21CxxxB382 & LxxCxxxB506 ).
Let me know this info ...
Hi,
I went from l21c432b380 to l21c432b506 during this process. Stock OEM file was flashed before the -380 upgrade (no errors existed, the 380 upgrade followed a flash of -370).
I'm not sure why this is happening - I mean, both firmwares were from the firmware finder app... Weird, to say the least.
Sovjohn said:
Hi,
I went from l21c432b380 to l21c432b506 during this process. Stock OEM file was flashed before the -380 upgrade (no errors existed, the 380 upgrade followed a flash of -370).
I'm not sure why this is happening - I mean, both firmwares were from the firmware finder app... Weird, to say the least.
Click to expand...
Click to collapse
Yep, you used correct file but anyhow the firmware has been corrupted.
I think you have some ways to solve...
1 - if you have stock recovery, reboot into it and
download and flash the same latest firmware.
If you do not have it, you can extract (with huawei update extractor) it
(should be recovery1.img) from B506 firmware (update.zip) you already got,
then can be flashed via fastboot commands.
2 - Flash a previous or B380 firmware via HuRUpdater, then
update to latest via Firmware Finder with dns/vpn method.
3 - Repeat the whole job you done with B506 firmware. (via HuRupdater)
4 - Reboot recovery, reflash L21OEMinfo file, dual sim one, then the latest firmware again...
P.S.: method 1, 2, 4 will re-lock the bootloader, no problem if still you got the code...
Beware method 4, after you flash the oeminfo file do not shout down, reboot to bootloader
and unlock it again with the code. Device will reboot into twrp, then flash B506 firmware.
Good luck and let the community know..