Related
UPDATE (07-Jan-2017):
If your OnePlus 2's IMEI#2 = 0, (IMEI#1 is showing correct IMEI)
Because you run these commands in fastboot mode:
"fastboot erase modemst1 "
"fastboot erase modemst2 "
"fastboot erase cache"
Then,
A fix has been made into this zip file.
https://www.androidfilehost.com/?fid=529152257862693598
Kindly thank Tony.L & Crystal.Z from OnePlus OOS team.
You have to be on OOS 3.5.6 (Clean-Flashed, non-rooted, from whatever ROM you are currently on).
I had TWRP Hybrid Recovery v3.4 installed.
IMEI#2 will come back again.
Now, Remember to backup EFS using terminal method.
& DONT erase modem ever again.
mine have same problem..only IMEI2 shows "0"..my phone keep random rebooting until now
osr.arora said:
I will be really grateful, if anybody can help me recover/write IMEI#2 on my OnePlus 2.
IMEI#2 currently shows as "0", (IMEI#1 is showing correct IMEI)
I don't have a EFS backup.
Device is out of warranty.
OnePlus's L2 support team, flashed OOS v3.1.0 via Qualcomm recovery method via remote session, but still no fix.
Lastly (I think, some may consider this illegal, but I'm just trying to write the missing IMEI on my phone),
I searched for IMEI writer softwares ( WriteDualIMEI(W+G_eMMC), Read&Write_Tool_v1.3) on internet, but somehow, i couldn't make them work (Maybe incorrect Qualcomm drivers on my PC, or idk what )
*********How did this all happen*********
I read a blog, that In order to increase the download speed from the Jio SIM, preferred LTE Band should be switched (from 3 to 40).
So, I pressed *#*#4636#*#*, >> Phone Info page >> three dot menu >> select radio band >> SELECTED Band mode 40.
Immediately after that,
Vodafone Sim stopped working in any of the SIM-Slots, But Jio sim (4G) was working in both the slots.
*****
Then I ran these commands in fastboot mode:
"fastboot erase modemst1 "
"fastboot erase modemst2 "
"fastboot erase cache"
Immediately, Both the SIM slots stopped working.
*****
Then I flashed "new-modem.zip" from benschhold (https://androidfilehost.com/?fid=24407100847293158)
which makes SIM-Slot-1 work with both Vodafone & Jio,
But SIM-Slot-2 only detects the sim, but with 0 network bars i.e. "No service| Vodafone"
I would appreciate your help.
Click to expand...
Click to collapse
***************************************
lockmunk said:
mine have same problem..only IMEI2 shows "0"..my phone keep random rebooting until now
Click to expand...
Click to collapse
Lesson for you guys. The first thing to do after flashing a custom recovery is to make a complete nandroid backup..
Tunatje said:
Lesson for you guys. The first thing to do after flashing a custom recovery is to make a complete nandroid backup..
Click to expand...
Click to collapse
FYI, a full nandroid backup doesn't backup the two EFS partitions even though EFS is an option in TWRP's backup menu.
You need to manually backup the modemst1 & modemst2 partitions
Spannaa said:
FYI, a full nandroid backup doesn't backup the two EFS partitions even though EFS is an option in TWRP's backup menu.
You need to manually backup the modemst1 & modemst2 partitions
Click to expand...
Click to collapse
True. Done it myself through terminal. Forgot about the dual sim :laugh:
osr.arora said:
I will be really grateful, if anybody can help me recover/write IMEI#2 on my OnePlus 2.
IMEI#2 currently shows as "0", (IMEI#1 is showing correct IMEI)
I don't have a EFS backup.
Device is out of warranty.
OnePlus's L2 support team, flashed OOS v3.1.0 via Qualcomm recovery method via remote session, but still no fix.
Lastly (I think, some may consider this illegal, but I'm just trying to write the missing IMEI on my phone),
I searched for IMEI writer softwares ( WriteDualIMEI(W+G_eMMC), Read&Write_Tool_v1.3) on internet, but somehow, i couldn't make them work (Maybe incorrect Qualcomm drivers on my PC, or idk what )
*********How did this all happen*********
I read a blog, that In order to increase the download speed from the Jio SIM, preferred LTE Band should be switched (from 3 to 40).
So, I pressed *#*#4636#*#*, >> Phone Info page >> three dot menu >> select radio band >> SELECTED Band mode 40.
Immediately after that,
Vodafone Sim stopped working in any of the SIM-Slots, But Jio sim (4G) was working in both the slots.
*****
Then I ran these commands in fastboot mode:
"fastboot erase modemst1 "
"fastboot erase modemst2 "
"fastboot erase cache"
Immediately, Both the SIM slots stopped working.
*****
Then I flashed "new-modem.zip" from benschhold (https://androidfilehost.com/?fid=24407100847293158)
which makes SIM-Slot-1 work with both Vodafone & Jio,
But SIM-Slot-2 only detects the sim, but with 0 network bars i.e. "No service| Vodafone"
***************************************
I would appreciate your help.
Click to expand...
Click to collapse
Did you managed to get any info on that??
I also encountered the exactly same issue..
ashu01 said:
Did you managed to get any info on that??
I also encountered the exactly same issue..
Click to expand...
Click to collapse
No Fix, as of yet !
Somebody said, he flashed modem files from beanstalk Rom thread, & that fixed the missing IMEI issue.
I haven't tried it yet,
If you try it, & it fixes this problem, update me on thia thread !
Hi
Like I wrote in another thread, this is what I did to get working modem after testing out the unstable H2OS firmware
1. Ran TWRP backup of CM14 install
2. Restored OOS 3.1 OTA zip
3. Formatted modemst1 and 2 and persist partition using fastboot
4. Did factory reset and booted up OOS and powered down the phone
5. Powered up into fastboot and restored persist partition with the persist.img dump found in some thread in this forum
6. Restored back my CM14 install and now everything is working again (except for losing some configuration probably stored in the persist partition like button swapping and battery text on icon)
Best regards
pitrus- said:
Hi
Like I wrote in another thread, this is what I did to get working modem after testing out the unstable H2OS firmware
1. Ran TWRP backup of CM14 install
2. Restored OOS 3.1 OTA zip
3. Formatted modemst1 and 2 and persist partition using fastboot
4. Did factory reset and booted up OOS and powered down the phone
5. Powered up into fastboot and restored persist partition with the persist.img dump found in some thread in this forum
6. Restored back my CM14 install and now everything is working again (except for losing some configuration probably stored in the persist partition like button swapping and battery text on icon)
Best regards
Click to expand...
Click to collapse
Can u send me persist.img pls
My email is [email protected]
Would be better, if you upload persist file here.
pitrus- said:
Hi
Like I wrote in another thread, this is what I did to get working modem after testing out the unstable H2OS firmware
1. Ran TWRP backup of CM14 install
2. Restored OOS 3.1 OTA zip
3. Formatted modemst1 and 2 and persist partition using fastboot
4. Did factory reset and booted up OOS and powered down the phone
5. Powered up into fastboot and restored persist partition with the persist.img dump found in some thread in this forum
6. Restored back my CM14 install and now everything is working again (except for losing some configuration probably stored in the persist partition like button swapping and battery text on icon)
Best regards
Click to expand...
Click to collapse
We are facing missing IMEI#2 issue,
Did your steps, fix this issue ?
osr.arora said:
We are facing missing IMEI#2 issue,
Did your steps, fix this issue ?
Click to expand...
Click to collapse
Yes they did, after flashing the H20S firmware and going back to OOS firmware I was missing IMEI on both modems/incompatible modemst partitions. Formatting these and booting up OOS recreated these and after also restoring persist partition both IMEIs was reported and Cyanogenmod no longer bootlooped.
pitrus- said:
Yes they did, after flashing the H20S firmware and going back to OOS firmware I was missing IMEI on both modems/incompatible modemst partitions. Formatting these and booting up OOS recreated these and after also restoring persist partition both IMEIs was reported and Cyanogenmod no longer bootlooped.
Click to expand...
Click to collapse
Before flashing H2Os firmware,
What was your OP2 running ?
Also can you list all links to files, which helped you.
Just an hour ago, i flashed "ResurrectionRemix-6.0-OOS-2.2.1-Modem.zip" on my OnePlus 2 (running Oxygen OS 3.1.0 with TWRP) & it went into bootloop.
So now i'm downloading @Spannaa 's "Oxygen OS 2.1.1 fastboot.zip" , to make my phone working again.
osr.arora said:
We are facing missing IMEI#2 issue,
Did your steps, fix this issue ?
Click to expand...
Click to collapse
I though my phone was fine, then I noticed my swedish BankID just didn't want to work. Turns out my SIM2 has null IMEI just like yours. Tried Qualcomm restore to OOS 3.0.2 but still IMEI2:0, so it looks like trying out the H2OS 2.5 beta firmware and going back was a real killer for my phone. I get signal on both SIM cards and strangely I can call using both SIM cards even though one is showing no IMEI
Update
After analyzing the nv data of my phone, I can tell that the IMEI for SIM card 1 is there, and there does not seem to be any address register for a second IMEI so the phone must figure this out itself. For me the first IMEI ends with a 99 and second with a 81 which means a difference of -18, perhaps second IMEI is always -18 hexadecimal from the first and therefore automatically calculated and registered by the modem firmware?
@pitrus-
Do you have a European A2003 model? I remember that the difference between European and Chinese models was that the Chinese has only 1 IMEI. Maybe this H20S firmware changed your European model effectively to Chinese. FYI my IMEIs, untoutched by H2OS, differ by 8, 72 vs 64. You can check your original IMEIs from the red box that the phone shipped in, if you still have it.
To resolve this, Oneplus customer service recommends to replace the motherboard:
https://forums.oneplus.net/threads/those-who-lost-their-imei-please-read.475930/page-5#post-15427155
pryggi said:
@pitrus-
Do you have a European A2003 model? I remember that the difference between European and Chinese models was that the Chinese has only 1 IMEI. Maybe this H20S firmware changed your European model effectively to Chinese. FYI my IMEIs, untoutched by H2OS, differ by 8, 72 vs 64. You can check your original IMEIs from the red box that the phone shipped in, if you still have it.
To resolve this, Oneplus customer service recommends to replace the motherboard:
https://forums.oneplus.net/threads/those-who-lost-their-imei-please-read.475930/page-5#post-15427155
Click to expand...
Click to collapse
Yes, it's an A2003 European model. If only I had a dump of a working A2003 NV Data so I could find the difference between them. Whoever could give me this could just zap out 00550 NV Item (IMEI) so as not to share it with me. That would tell us which NV Items to change to swap between single och dual sim card modell.
@pitrus-
I have the IMEIs on my OP2 still intact, I have not flashed latest H2OS beta, nor have I used the fastboot erase/format commands. So I can analyse the /dev/block/mmcblk0p17 and /dev/block/mmcblk0p18 dd dumps. Could you tell me which tools to use, or how can I edit out my IMEIs?
Really confused, what to flash, what not to flash (to fix the IMEI issue) !!!
I restored my OP2 to OOS 2.1.1 with Qualcomm Restore Files (from OnePlus Forums) as @Spannaa 's fastboot file, didn't worked, idk why !
osr.arora said:
Really confused, what to flash, what not to flash (to fix the IMEI issue) !!!
I restored my OP2 to OOS 2.1.1 with Qualcomm Restore Files (from OnePlus Forums) as @Spannaa 's fastboot file, didn't worked, idk why !
Click to expand...
Click to collapse
It doesn't mather what you flash, our nv data is incompatible with all modems other than the unstable H2OS 2.5 one. Only solution is to wait for a OxygenOS modem that uses the same nv data structure if you like me didn't make a dump of the nv data before flashing the H2OS ROM. If you do want to go back to CM14, just flash H2OS 2.5.x and then format system, data, cache and flash latest CM14. You will still get null IMEI on second SIM slot, there's no solution for this right now. (You could also Qualcomm restore back to OxygenOS 3.1, this will give you the TZ needed by CM14).
pitrus- said:
It doesn't mather what you flash, our nv data is incompatible with all modems other than the unstable H2OS 2.5 one. Only solution is to wait for a OxygenOS modem that uses the same nv data structure if you like me didn't make a dump of the nv data before flashing the H2OS ROM. If you do want to go back to CM14, just flash H2OS 2.5.x and then format system, data, cache and flash latest CM14. You will still get null IMEI on second SIM slot, there's no solution for this right now. (You could also Qualcomm restore back to OxygenOS 3.1, this will give you the TZ needed by CM14).
Click to expand...
Click to collapse
i also used fastboot erase command..and in the same situation of showing imei2 0.
do you think the oos update will have a fix for this issue??
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 picked up a H910 the other day as it was a great price & immediately hated the AT&T bloat (plus I'm in the UK on the EE network) so I flashed US996 which was fine, the steps I did where:
Downloaded LGUP (patched)
Downloaded LG Drivers
Downloaded US99610o_01_0202.kdz
Put my phone in download mode
Selected Partition DL
Checked all partitions
Phone booted perfectly however I noticed I flashed a old version of the US996 firmware which wasn't Oreo, & I was aware that OTAs wouldn't work, so i tried flashing the update through LGUP (patched) again, this time I did:
Downloaded US99620f_00_1120.kdz
Put phone in download mode
Selected Partition DL
Then I got a error saying firmware doesn't support partition update so I checked upgrade, everything went ahead but when I booted the device it was on a blue screen with the number 2 & encryption process complete at the top, I couldn't boot the device at all past that screen
So I went back on to LGUP (patched) and this time selected refurbish & this time the device booted but immediately said settings keeps stopping and I couldn't get past it
So now I've reverted back to the US99610o_01_0202.kdz which is nougat & February 2018 patch..
What am I doing wrong?, I just wanted to be on the latest US996 firmware possible which I believe is Oreo & September patch but as I said above can't seem to do so
Any help is appreciated
I want to make it very clear I searched last night for the issue I was having and could not find it, however if this has already been discussed somewhere then I apologize but I really couldn't find where!
try upgrade mode with the oreo kdz. You don't need partition dl because the phone is already fully running us996 firmware.
Phoenix591 said:
try upgrade mode with the oreo kdz. You don't need partition dl because the phone is already fully running us996 firmware.
Click to expand...
Click to collapse
Thanks for the reply, turns out it must have been a bad .kdz file, strange because I got it from the LG firmware site, I redownloaded it just incase & this time it worked perfectly so I'm now on US996 Oreo with Nov 2018 patch
TheInfiniteAndroid said:
I picked up a H910 the other day as it was a great price & immediately hated the AT&T bloat (plus I'm in the UK on the EE network) so I flashed US996 which was fine, the steps I did where:
Downloaded LGUP (patched)
Downloaded LG Drivers
Downloaded US99610o_01_0202.kdz
Put my phone in download mode
Selected Partition DL
Checked all partitions
Phone booted perfectly however I noticed I flashed a old version of the US996 firmware which wasn't Oreo, & I was aware that OTAs wouldn't work, so i tried flashing the update through LGUP (patched) again, this time I did:
Downloaded US99620f_00_1120.kdz
Put phone in download mode
Selected Partition DL
Then I got a error saying firmware doesn't support partition update so I checked upgrade, everything went ahead but when I booted the device it was on a blue screen with the number 2 & encryption process complete at the top, I couldn't boot the device at all past that screen
So I went back on to LGUP (patched) and this time selected refurbish & this time the device booted but immediately said settings keeps stopping and I couldn't get past it
So now I've reverted back to the US99610o_01_0202.kdz which is nougat & February 2018 patch..
What am I doing wrong?, I just wanted to be on the latest US996 firmware possible which I believe is Oreo & September patch but as I said above can't seem to do so
Any help is appreciated
I want to make it very clear I searched last night for the issue I was having and could not find it, however if this has already been discussed somewhere then I apologize but I really couldn't find where!
Click to expand...
Click to collapse
Do you get any warning screen when booting up with US996 firmware on H910?
Good day!
I have a V20 Sprint right after DirtySanta. I want rooted Oreo, I live in Europe (sorry for my English) and use a local telecom operator (CDMA2000 1xEV-DO). There are many incomprehensible I did not find it on the forum.
1) Updating which firmware components increases ARB? I.e. aboot, modem etc.
2) How, having an img file or a kdz file, can I find out the ARB version?
3) Does ARB increase when flashing with any of these methods: "partition dl", "fastboot flash", kdzwriter?
4) Can someone share a Sprint V20 Oreo MODEM and SYSTEM dump?
5) Did someone try to cut the leads on motherboard @runningnak3d https://forum.xda-developers.com/t/...t-to-brick-your-phone-for-funsies-v1.3673622/ ?
6) It seems to me that the best option is to use SYSTEM (and MODEM?) from US99620f (US99620f_00_1120.kdz) . Both LS997 and US996 support CDMA2000 1xEV-DO frequency. US996 contains no bloatware. Does only vs995, us996 and ls997 support СDMA and they all have ARB 1 on Oreo?
7) How best to try:
a) Flash (Installing KDZ US996 7.0 via patched LGUP "partition dl" -> Re-installing the same KDZ via "update") LS997 7.0 to US996 7.0; then flash SYSTEM.img US996 8.0 (+ core mk2000 Oreo US996)? If there is no connection, flash MODEM.img US996 8.0?
Or
b) The same without prior full flashing to US996. Which kernel @askermk2000 and TWRP @Phoenix591 in the case of such a "Frankenstein" to use - LS or US? Which kernel is better to use in this case: LS997_v2.1, US996Santa_v2.2 or US996Santa_v2.2-BETA38? Would it make sense to flash the LS997 8.0 modem?
8) What is the best way to flash the SYSTEM and MODEM? kdzwriter, LGUP "dl partition", "fasboot flash"?
Thank you guys for your work and time!
An LS997 on Oreo is on ARB1 and therefore completely locked down and unrootable, so I don't think anyone has made any dumps from it. No idea which specific portion causes the ARB to change.
I would not recommend cross-flashing a modem unless someone else reported it to be working. You have a much higher risk of completely losing all cellular signal. Does your phone in its current state have signal reception problems?
The rootable LS997 on ARB0 is generally assumed to be stuck on Nougat for stock-based ROMs, and I haven't seen anyone try to flash any stock US996 Oreo parts, so that could be quite risky. If you really want Oreo or higher, then you should consider looking at the LineageOS-type ROMs.
For more things on the LS997, I've written up a bunch of general information in this post on the V20 Subreddit.
how to check ARB status?
nevermind, i got it back how do i confirm ARB?
xxTECRAxx said:
how to check ARB status?
nevermind, i got it back how do i confirm ARB?
Click to expand...
Click to collapse
As far as I know, only the H918 (software version H91810p or later, includes all on Oreo) and LS997 (software version LS997ZV8 or later, includes all on Oreo) have ARB enabled. So you don't have to worry about it on any other model, including the US996. Or did you actually cross-flash the US996 Oreo KDZ onto the LS997?
C D said:
As far as I know, only the H918 (software version H91810p or later, includes all on Oreo) and LS997 (software version LS997ZV8 or later, includes all on Oreo) have ARB enabled. So you don't have to worry about it on any other model, including the US996. Or did you actually cross-flash the US996 Oreo KDZ onto the LS997?
Click to expand...
Click to collapse
I did cross flash my LS997 with US996 10f kdz
xxTECRAxx said:
I did cross flash my LS997 with US996 10f kdz
Click to expand...
Click to collapse
Is it 10f or 20f (your screenshots show 20f)? It's certainly interesting to see US996 stock Oreo cross-flashed onto an old LS997 as I have never seen anyone do it before. Do things actually function normally on it?
Anyway, everything's still on ARB0, so you can downgrade any way you like. If you haven't already done so, you'll need to be on 10f in order to do the rooting procedure.
First, I made a backup of all partitions using LGUP. I flashed the unlocked LS997 with US99620f firmware in the "Partition DL" mode via patched LGUP . I have selected all sections except aboot and abootbak. Then, in fastboot mode, I flashed recovery 3.2.2-1. I`ve tried 3.3.1-1, 3.2.3-5, 3.2.3-4, but they can't do format data correctly. Then I flashed modem, modemst1 and modemst2 from the backup in fastboot mode. Then in recovery I flashed the last mk2000 kernel for Oreo - LS997_v2.1-mk2000.zip . Then magisk 19.5
P.S. I need SDMA, so I was flashing the kernel and modem from LS997. For GSM it may not be necessary.
kokos76 said:
First, I made a backup of all partitions using LGUP. I flashed the unlocked LS997 with US99620f firmware in the "Partition DL" mode via patched LGUP . I have selected all sections except aboot and abootbak. Then, in fastboot mode, I flashed recovery 3.2.2-1. I`ve tried 3.3.1-1, 3.2.3-5, 3.2.3-4, but they can't do format data correctly. Then I flashed modem, modemst1 and modemst2 from the backup in fastboot mode. Then in recovery I flashed the last mk2000 kernel for Oreo - LS997_v2.1-mk2000.zip . Then magisk 19.5
P.S. I need SDMA, so I was flashing the kernel and modem from LS997. For GSM it may not be necessary.
Click to expand...
Click to collapse
Very interesting. So all CDMA signal reception from your carrier and all root functions are working?
And did you use TWRP made for the US996 or LS997?
Any particular reason you went with Magisk 19.5 instead of a later version?
Also, there are a few more stock Oreo kernels for the LS997 that you could try (of course they've never really been tested since the regular LS997 on Oreo is unrootable):
- Phoenix591 has converted some of the mk2000 2.2 versions here
- ezzony's ezV2020 kernel also has an LS997 version here
C D said:
Is it 10f or 20f (your screenshots show 20f)? It's certainly interesting to see US996 stock Oreo cross-flashed onto an old LS997 as I have never seen anyone do it before. Do things actually function normally on it?
Anyway, everything's still on ARB0, so you can downgrade any way you like. If you haven't already done so, you'll need to be on 10f in order to do the rooting procedure.
Click to expand...
Click to collapse
it's 20f, not 10f. I had swapped toms to darn near everything on XDA but never happy with any of them. always something not working or I couldn't remove some built-in crap from so-called "stock" roms.
this last go I forget what I was trying to put on it but she stuck in the warning screen and wouldn't boot. i threw so many commands at inside fastboot mode, I am surprised it's not a paperweight. honestly, you name it, I sent it! wipe, format partition, didn't have a concern in the world, and I don't because I have a pixel 4a as the daily driver.
it should be noted, prior to this, I could never get LG Up to work as the app never recognized the phone. after fastboot mode not getting results booting into anything, I said f*ck it and put it into download mode. tiny bit of reading here and shortly after pulling the US996 20f KDZ file from LG, I had a stock RUNNING Oreo!
bro, seriously though, this Oreo runs the best that I've seen! it's smooth and fast! just a little on the heavy side. she's bloated and I need to trim the fat away. LG poisons the phone bad with all their garbage. runs like a champ though
I am extracting stock ls99720a Oreo from ls997 and will test it well before uploading it.
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