Related
1，unlocked bootload，https://www.gizdev.com/lg-g5-h850-twrp-3-0-rooting-guide/
2，install rec for h850 ，http://thunderztech.com/root-lg-g5-on-android-7-0-nougat-with-twrp-recovery/
3，into rec and flash LG-H85010E-Flashable.Bootloader.zip from autoprime,http://forum.xda-developers.com/lg-g5/development/stock-h850-10e-eu-rom-flashable-zips-t3448273
4,lg up flash 6.0.1 kdz,http://forum.xda-developers.com/lg-g5/development/stock-h850-10e-eu-rom-flashable-zips-t3448273
5,wipe you device by keep volume- always and power,when look lg logo,press power again and keep it ,then press yes,yes
you have downgrade to 6.0.1
xjqlfq said:
1，unlocked bootload，https://www.gizdev.com/lg-g5-h850-twrp-3-0-rooting-guide/
2，install rec for h850 ，http://thunderztech.com/root-lg-g5-on-android-7-0-nougat-with-twrp-recovery/
3，into rec and flash LG-H85010E-Flashable.COMPLETE.zip from autoprime,http://forum.xda-developers.com/lg-g5/development/stock-h850-10e-eu-rom-flashable-zips-t3448273
4,lg up flash 6.0.1 kdz,http://forum.xda-developers.com/lg-g5/development/stock-h850-10e-eu-rom-flashable-zips-t3448273
5,wipe you device by keep volume- always and power,when look lg logo,press power again and keep it ,then press yes,yes
you have downgrade to 6.0.1
Click to expand...
Click to collapse
good info.
I can make it even easier... instead of downloading my 10E COMPLETE ZIP
Just download/flash my 10E BOOTLOADER ZIP. It'll make LGUP work again with M KDZs and the BOOTLOADER ZIP is much smaller!
autoprime said:
good info.
I can make it even easier... instead of downloading my 10E COMPLETE ZIP
Just download/flash my 10E BOOTLOADER ZIP. It'll make LGUP work again with M KDZs and the BOOTLOADER ZIP is much smaller!
Click to expand...
Click to collapse
thanks，get it
autoprime said:
good info.
I can make it even easier... instead of downloading my 10E COMPLETE ZIP
Just download/flash my 10E BOOTLOADER ZIP. It'll make LGUP work again with M KDZs and the BOOTLOADER ZIP is much smaller!
Click to expand...
Click to collapse
I had several problems with this procedure (coming from V20a):
1. After flashing 10C BOOTLOADER ZIP via TWRP, LGUP was not able to detect my device type anymore, but this worked with previous bootloader. Why?
2. Flashing the 10C COMPLETE ZIP did result in a loss of TWRP (although recovery.img is not part if complete ZIP). Why?
3. Flashing the 10E COMPLETE ZIP caused FCs and a bootloop Reset in system recovery did help to get the device up again.
After that LGUP did find again my H850 and upgrade option works now with M KDZs (which did not work under Nougat). But the refurbish option is still not working and says "not supported".
fuxi222 said:
I had several problems with this procedure (coming from V20a):
1. After flashing 10C BOOTLOADER ZIP via TWRP, LGUP was not able to detect my device type anymore, but this worked with previous bootloader. Why?
2. Flashing the 10C COMPLETE ZIP did result in a loss of TWRP (although recovery.img is not part if complete ZIP). Why?
3. Flashing the 10E COMPLETE ZIP caused FCs and a bootloop Reset in system recovery did help to get the device up again.
After that LGUP did find again my H850 and upgrade option works now with M KDZs (which did not work under Nougat). But the refurbish option is still not working and says "not supported".
Click to expand...
Click to collapse
1. I suggested 10E not 10C.. not sure why LGUP 1.14 + UPPERCUT wouldn't see it. But UPPERCUT is geared towards recent devices on recent software. It's possible 10C is too old to fall under the UPPERCUT 1.0.0.0 umbrella.. and you're always welcome to use the older LGUP methods instead.
2. You will always lose TWRP if you boot into Android without patching the boot.img or flashing supersu zip first. The stock system.img has a patch in it which always tries to replace the recovery partition with stock recovery.. and zips like supersu stop such things from happening. The procedure is to flash twrp.. boot into twrp.. flash supersu. flashing twrp then booting into android = no more twrp. this is standard android stuff for awhile now.
3. The refurbish option isn't needed and I've already explained in the UPPERCUT thread that refurbish is not supported. All refurbish option does is force the phone to run a factory reset after KDZ finishes... the user can just run a factory reset manually after the flash to achieve the exact same end result.
autoprime said:
1. I suggested 10E not 10C.. not sure why LGUP 1.14 + UPPERCUT wouldn't see it. But UPPERCUT is geared towards recent devices on recent software. It's possible 10C is too old to fall under the UPPERCUT 1.0.0.0 umbrella.. and you're always welcome to use the older LGUP methods instead.
2. You will always lose TWRP if you boot into Android without patching the boot.img or flashing supersu zip first. The stock system.img has a patch in it which always tries to replace the recovery partition with stock recovery.. and zips like supersu stop such things from happening. The procedure is to flash twrp.. boot into twrp.. flash supersu. flashing twrp then booting into android = no more twrp. this is standard android stuff for awhile now.
3. The refurbish option isn't needed and I've already explained in the UPPERCUT thread that refurbish is not supported. All refurbish option does is force the phone to run a factory reset after KDZ finishes... the user can just run a factory reset manually after the flash to achieve the exact same end result.
Click to expand...
Click to collapse
At first: Big thanks for your quick response!!!
to 1.: The reason for 10C instead of 10E is simple: you do not have a KDZ file for 10E on your codefire drive (only a ZIP), but for 10C the KDZ was available. And the links to LG server were not working yesterday for me.
I read Uppercut the first time now and will give it a try today in the evening (German time). :fingers-crossed:
to 2.: Understood. Thank you! :good:
to 3.: Then how can I get rid of the 3 error messages on start-up related to NT-code ("Can't find matched cust for NT-code" + "OP name for Buyer-code...")? I understood, that refurbish will flash new cust partition and this will solve the problem. I see cust.img also on your drive, but it is not inluded in the COMPLETE ZIPs. Would it help to flash this?
Or can LG Bridge help in this case? It does refuse to flash my phone, maybe because of the bootloader unlock?!
I read so many threads yesterday, but nothing solved this issue... :crying::crying:
fuxi222 said:
to 3.: Then how can I get rid of the 3 error messages on start-up related to NT-code ("Can't find matched cust for NT-code" + "OP name for Buyer-code...")? I understood, that refurbish will flash new cust partition and this will solve the problem. I see cust.img also on your drive, but it is not inluded in the COMPLETE ZIPs. Would it help to flash this?
Or can LG Bridge help in this case? It does refuse to flash my phone, maybe because of the bootloader unlock?!
I read so many threads yesterday, but nothing solved this issue... :crying::crying:
Click to expand...
Click to collapse
cust should be getting flashed regardless of selecting refurbish or not as far as I know.. but perhaps I'm wrong.
if you have root/twrp just zero out the cust partition or simply delete the files inside the cust folder using a file explorer app... and the error msg should go away on next reboot.
this is in the FAQ/Q&A section in the OP of all my stock threads for H850.
if you're on M and must flash a KDZ with refurb option... just use the old LGUP methods. but if you're sticking with TWRP there's not really any need to flash any KDZ.. you can flash whatever in TWRP instead.
autoprime said:
cust should be getting flashed regardless of selecting refurbish or not as far as I know.. but perhaps I'm wrong.
if you have root/twrp just zero out the cust partition or simply delete the files inside the cust folder using a file explorer app... and the error msg should go away on next reboot.
this is in the FAQ/Q&A section in the OP of all my stock threads for H850.
if you're on M and must flash a KDZ with refurb option... just use the old LGUP methods. but if you're sticking with TWRP there's not really any need to flash any KDZ.. you can flash whatever in TWRP instead.
Click to expand...
Click to collapse
"and the error msg should go away on next reboot." I get 3 error messages related to this. Will I get rid of all of them?
"old LGUP methods" means tool version 1.11 instead of 1.14? So use version 1.11 for MM and 1.14 for N?!
Unfortunately, refurbish does not work even under MM for me regardless if I use version 1.11 or 1.14.
BTW: The old version 1.11 asks my each time I trigger the refurbish process to "Input new NT code" (the new version does not behave like this). Is my problem maybe caused by this or can this be used to input a working string there?
fuxi222 said:
"and the error msg should go away on next reboot." I get 3 error messages related to this. Will I get rid of all of them?
"old LGUP methods" means tool version 1.11 instead of 1.14? So use version 1.11 for MM and 1.14 for N?!
Unfortunately, refurbish does not work even under MM for me regardless if I use version 1.11 or 1.14.
BTW: The old version 1.11 asks my each time I trigger the refurbish process to "Input new NT code" (the new version does not behave like this). Is my problem maybe caused by this or can this be used to input a working string there?
Click to expand...
Click to collapse
i dont have an H850 so idk.. but any time ive had someone zero cust theyve said errors have gone away. so if they dont for you.. you must be special. try it and find out... then report back. if it doesnt work... ¯\_(ツ)_/¯
old lgup methods = 1.11 + dll msi installer, yes. but i see no reason to use 1.11 simply for refurbish option. most people should be able to use LGUP 1.14 + UPPERCUT for most situations on G4/G5/V20.
i dont know abotu the NT code stuff with LGUP.. again.. I dont have a H850. but if you have TWRP then there's really no need to be messing with LGUP at all unless you want to be 100% stock/unrooted with no TWRP. just zero cust or try flashing the cust.img that's in the folder.
I cant help any more on this NTCode subject without a device that uses it. good luck.
autoprime said:
good info.
I can make it even easier... instead of downloading my 10E COMPLETE ZIP
Just download/flash my 10E BOOTLOADER ZIP. It'll make LGUP work again with M KDZs and the BOOTLOADER ZIP is much smaller!
Click to expand...
Click to collapse
Only if someone is on the same point: For me, it is only working to flash the COMPLETE ZIP! When I flash bootloader only, LGUP does not detect the model type of my device anymore (detected type is "Unknown"). I have tried it now for 2 times with similar results...
BTW: I used this method to get rid of the annoying NT code issue: http://forum.xda-developers.com/showpost.php?p=66957161&postcount=4
@autoprime Can't we just flash 10E with the refubrish option? Somehow I'm unable to get into recovery with the button combination after downgrading and updating again, even though I'm doing it properly and I was able to do it before.
EDIT: So refubrish stopped working now too. Dang. I installed the recovery through Dirty Cow, flashed the bootstack and went back to 10E, but I still don't have a recovery. ;_;
Ok, I've tried everything and button combination for recovery still doesn't work, so think if you really wanna risk being unable to easily factory reset your phone.
autoprime said:
1. I suggested 10E not 10C.. not sure why LGUP 1.14 + UPPERCUT wouldn't see it. But UPPERCUT is geared towards recent devices on recent software. It's possible 10C is too old to fall under the UPPERCUT 1.0.0.0 umbrella.. and you're always welcome to use the older LGUP methods instead.
2. You will always lose TWRP if you boot into Android without patching the boot.img or flashing supersu zip first. The stock system.img has a patch in it which always tries to replace the recovery partition with stock recovery.. and zips like supersu stop such things from happening. The procedure is to flash twrp.. boot into twrp.. flash supersu. flashing twrp then booting into android = no more twrp. this is standard android stuff for awhile now.
3. The refurbish option isn't needed and I've already explained in the UPPERCUT thread that refurbish is not supported. All refurbish option does is force the phone to run a factory reset after KDZ finishes... the user can just run a factory reset manually after the flash to achieve the exact same end result.
Click to expand...
Click to collapse
Well I am trying to flash stock EE rom, which I have the KDZ for.
I am flashing via upgrade, and all that happens is when the phone boots it is unstable, phone app crashing etc.
All settings still intact, no myee app, app from open EU rom still exists, very very strange.
Is it possible to convert a KDZ to a twrp flashable zip as twrp seems far easier.
I suspect if I used refurbish it would fix this issue as upgrade seems to not be clearing everything.
chrcol said:
Well I am trying to flash stock EE rom, which I have the KDZ for.
I am flashing via upgrade, and all that happens is when the phone boots it is unstable, phone app crashing etc.
All settings still intact, no myee app, app from open EU rom still exists, very very strange.
Is it possible to convert a KDZ to a twrp flashable zip as twrp seems far easier.
I suspect if I used refurbish it would fix this issue as upgrade seems to not be clearing everything.
Click to expand...
Click to collapse
Did u try what I suggested in other thread? Wipe internal storage before first boot, reboot recovery afterwards before booting system; are u clean flashing? Are you trying to restore any data at all besides things like messages and call logs?
Going from an openEU.kdz to a branded .Kdz would definitely require a Twrp data format and a recovery reboot, perhaps do all this b4 using LGUP with kdz.
Yes it is possible to make a .zip from a kdz, but it's not a simple process and there is no EE branded 20a.zip
Autoprime already stated that refurbish option can be used if you use LGUP v1.11 instead of latest 1.14 but don't forget the .DLL file. Also all refurbish does is wipe data and internal storage; which can be done via TWRP using the method I mentioned above. Try what I mentioned and then reflash kdz;forget about any data besides text messages just take the extra 30min to resetup device from scratch.
What version of LGUP are you using? Can u give more info be more descriptive about what's happening?
it is resolved now but I was just trying to get it in a good state to return the phone to EE.
Doing a factory reset in twrp didnt work, but what did work is I did a reset from in the rom, and after the reboot it was properly reset.
What was odd is when I wiped system and data manually in twrp that also didnt work.
I think I forgot to check if I completely wiped the internal storage, photos etc. As I was rushing to get the phone to be sent back. But the description for the reset option in android says it does wipe all personal data so hopefully that did it.
How can I downgrade LS992?
İs this possible for lg g5 H860?
For H850 just download H85010i_00_OPEN_EU_OP_0923.kdz flash it with LGUP 1.4(uppercut) after it's finished reset the phone then just flash android 6 firmware that you like.
i have h850 ,
current firmware is v20a updated via fota
no root , no bootloader unlock ,,, compleatlly stock phone
i want to downgreade to any 6.0.1 firmware without losing data (if possible)
if not, what to check and what steps to do without tripping on cust ot drk or modem or .... issues ?
pleas advice me ....
LGUP corrupts whenever i hit Start, but it works just fine with N kdz (mine is 20a). I have tried to flash bootloader but still ended up with the same outcome.
Lucky patcher does not work on nougat. Application not installed. playstore error 504
autoprime said:
good info.
I can make it even easier... instead of downloading my 10E COMPLETE ZIP
Just download/flash my 10E BOOTLOADER ZIP. It'll make LGUP work again with M KDZs and the BOOTLOADER ZIP is much smaller!
Click to expand...
Click to collapse
I rooted H850 following autoprime's LG G5 H850 Bootloader Unlock instruction with autoprime's modded "Minimal ADB and Fastboot" {[ 1.) selecting port 41 in device manager (maybe was not necessary) and 2.) pushing TWRP twrp-3.1.1-0-h850.img 3.)booted into recovery (Using 2 hands.. use one hand/finger to press/hold volume down.. and use the other hand for the power button. Press n hold both buttons.) 4. flashing SuperSU (UPDATE-SuperSU-v2.82-20170528234214.zip) ]}.
Installed 20a with lgup because for a strange (windows 10 folder administrator permission) reason nether UPPERCUT_1.0.0.0.exe nether LGFlashTool.exe worked properly).
Unfortunatly I installed [ROM] [Nougat 7.0] Fulmics ROM 3.3 ◦ v20D ◦ H850 but, because the very big LACK of xposed framework on nougat, I had too much difficulties to patch correctly the core jar with lucky patcher getting a lot of error "app not installed the package appears to be corrupt" and other play store error 504 app not installed.
So I decided to downgrade and leave from any Nougat 7.0 based rom in order to move on Marshmallow 6.0. In particular I used TWRP to wipe everything and flash [STOCK][M] H850 10E OPEN EU ROM autoprime's 10E COMPLETE ZIP then Supersu then framework.
On android this time I skipped google registration and LG software updates with data and wifi OFF.
Then I activated USB debug in developer section
Then I followed these step in that really precise order:
a) installed super su again with twrp (want to be sure to have got ROOT);
b) configure Super Su setting in android to activate pseudo PRO option then uncheck the "separation mount space" in order to share .init;
c) configure Super Su setting giving permission always without asking and also during in boot (to everybody);
d) installed xposed-v87-sdk23-arm64.zip in TWRP
e) installed lucky patcher and using it to unistall every LG apps;
f) activate for the very first time wify in order to update immidiately lucky patcher (update available in lucky patcher settings) than download patch update;
g) installed xposed apk (in android obviosly because I refer to apk pattern) and run it following app procedure for a correct detection of framework then activate Lucky patcher module in xposed apk then reboot to permit lucky patcher using framework;
h) installed busybox (after the check I choose the "smart install").
i) and now I enjoy the freedom that I haven't got in Nougat to test some application before buying them, just to be sure to not waste money for fake apk like voice pro or other expensive one that fools me before so many times. :good:
Update: G5 H850 Genisys Theme 1.3 v10e MM is a great choice for stability and battery life.
Hey Guys,
I just bought the s8 yesterday and realised I did not have the OEM unlock and tried flashing the rom from the guide posted here but it didn't flash via odin because downgrading is not possible. I found the date trick on xda's portal and that worked for me and I flashed TWRP by odin.
I allowed system modifications and wiped all data and install no-verity-opt as well as magisk for root. Phone booted up fine and everything was working, I wanted to go to twrp to just check if it was working and it returned with Only official released binaries are allowed to be flashed and well the phone is soft bricked. I was wondering is there any other way other than restoring stock firmware via odin to fix this?
OEM lock shows off in download mode still, I am waiting for the sammobile firmware (5 more hours lol) to download and just wanted to know this time around, is there a fix that I am missing or a step that I missed out so that I could reboot and twrp stays as well as the phone doesn't get soft bricked as this is my daily driver
ItsmYarD said:
Hey Guys,
I just bought the s8 yesterday and realised I did not have the OEM unlock and tried flashing the rom from the guide posted here but it didn't flash via odin because downgrading is not possible. I found the date trick on xda's portal and that worked for me and I flashed TWRP by odin.
I allowed system modifications and wiped all data and install no-verity-opt as well as magisk for root. Phone booted up fine and everything was working, I wanted to go to twrp to just check if it was working and it returned with Only official released binaries are allowed to be flashed and well the phone is soft bricked. I was wondering is there any other way other than restoring stock firmware via odin to fix this?
OEM lock shows off in download mode still, I am waiting for the sammobile firmware (5 more hours lol) to download and just wanted to know this time around, is there a fix that I am missing or a step that I missed out so that I could reboot and twrp stays as well as the phone doesn't get soft bricked as this is my daily driver
Click to expand...
Click to collapse
Install rmm by pass after root before reboot. This will keep oem unlocked.
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
I have the h910 which is unlocked (i put a tmobile simcard in initially, which is actually prepaid).. i tried the ota check for updates to get it beyond android 7, it says no update available. I had wifi enabled and connected.
I figured the issue is that its a tmobile prepaid issue, since i guess technically the phone is att branded.
So i took my galaxy s8 att sim card and put it in, waited till connected.
Once connected after about 30 mins i tried again, still no updates available?
So i'm at a loss on the OTA portion.
Is there a way to get that working?
If not, which method should i use to force it on, so far i started following the steps on this page:
https://www.getdroidtips.com/lg-v20-android-8-0-oreo/
Which is really only android 8.0 not 8.1.
(I also tried check for updates from the lg bridge, but it throws an error even with mtp enabled on usb).
Thanks in advance
update, i tried the 20F firmware on that page which says us99620f, but i got an invalid kdz message when i tried LGUP to flash it.
LGup says H91010m for the version.
Question on the process for oreo
I have the recovery twrp-3.2.3-0-h910.img installed.
I folllowed the steps and installed:
H910_20h_Oreo_full_rooted.zip and added zips for H910_v1.0-mk2000.zip and what i thought i needed, SR5-SuperSU-v2.78-SR5-20161130091551.zip but now realize supersu is outdated, so at this point only mk2000 is on there.
The phone appears to be up to date and on oreo. Initially the free root checker seemed to say it wasnt rooted, but on second run it show it is.
I tried to run magisk manager but it says unfortunately magisk manager has stopped.(edit possibly related to the fact i didnt add any magisk 17.2 as a zip to flash, actually unsure where this file is located? can i do this now after the fact or does it matter)?
So at this point i think i missed something, maybe not fully rooted?
Questions are: does it matter if its not rooted? Will certain oreo features not work? Or, is this some isolated issue with just the manager not wanting to run?
The OS shows 8.0.0 (so i guess not 8.1), software version h91020h *i also tried to do volume up plus power did the factory wipe, but the twrp menu no longer appears, it just formats things back to stock 8.0 welcome
markm75 said:
Question on the process for oreo
H910_20h_Oreo_full_rooted.zip and added zips for H910_v1.0-mk2000.zip and what i thought i needed, SR5-SuperSU-v2.78-SR5-20161130091551.zip but now realize supersu is outdated, so at this point only mk2000 is on there.
Click to expand...
Click to collapse
The system is pre-rooted but as they said, you can still flash the Magisk image.
markm75 said:
I tried to run magisk manager but it says unfortunately magisk manager has stopped.(edit possibly related to the fact i didnt add any magisk 17.2 as a zip to flash, actually unsure where this file is located? can i do this now after the fact or does it matter)?
So at this point i think i missed something, maybe not fully rooted?
Click to expand...
Click to collapse
As for me, I installed Magisk from the image I downloaded here magiskmanager[.]com
The OS shows 8.0.0 (so i guess not 8.1), software version h91020h *i also tried to do volume up plus power did the factory wipe, but the twrp menu no longer appears, it just formats things back to stock 8.0 welcome
Click to expand...
Click to collapse
In order to get the TWRP back, you'll have to boot in fastboot mode through ADB (adb reboot bootloader) or volume down + plug to PC)
Then you can install the latest version of TWRP on fastboot mode: fastboot flash recovery twrp_image_file_name.img
So I converted my US997 to an H873 to mess around with stock Pie to see if I could root it somehow. I did this in the past, but the one thing I never tried was to unlock the bootloader while using the H873 firmware. I flashed my unlock.bin file and now the bootloader is unlocked again. Unfortunately, maybe due to how the H873 differs from the US997, I experienced some weird behavior. Mainly data encryption issues inside of TWRP and I had to monkey around with the fingerprint id to pass SafetyNet with Magisk. Before I really bothered doing any of this (getting Magisk to work), I mainly wanted to ditch stock and revert back to the official firmware then go back to Havoc. The only problem is, despite multiple attempts at trying to flash the stock Oreo KDZ, my phone simply wouldn't boot into Android. After it exits download mode, it goes straight to fastboot mode and refuses to boot into anything else. I used "partition dl" in LGUP to flash over the Canadian firmware, but unlike the last time I did this, nothing worked. I tried with the bootloader locked and unlocked. I thought that perhaps the KDZ I was using was corrupted, but the issue with that is that by now I've downloaded multiple KDZs from different sources. The MD5 on all of them were exactly the same despite not matching the MD5 hash provided on whatever given source I obtained them from. I attempted flashing the same exact version of firmware that I did the first time I converted and I even tried older versions. Nothing.
I'm currently running my Frankensteined US997 with Magisk. I would just flash a custom ROM while keeping the H873 partitions, but I got write errors for /system with any recovery I used. As I'm writing this, I'm wondering what would happen if I maybe flashed the KDZ again after using partition dl, though I might've already tried that. Could this be an issue with the KDZ itself (downloaded on a different PC and it still had the same MD5 as all the others), perhaps the boot.img didn't go through?
Maybe if someone has a US99721e KDZ I could try, I could rule out that being an issue. I could try using partition dl then upgrade in LGUP, but you'd think that It'd still boot after doing it over and over.
If anybody has any idea of what could be happening here, your input would be greatly appreciated.
Thanks