LEX727 EUI Version 5.8.018S Windows 10 Driver Issue - LeEco Le Pro3 Questions & Answers

Got the phone from Amazon a few weeks ago and have tried to do an OTA update since it only had 5.8.018S on it; however when I try to an OTA update it says I have the latest version. So I was thinking about pushing the newest update from my Windows 10 computer, but it says it's not recognize. I've played with USB debugging off / on and switched from MTP and PTP modes with no luck. Anyone have a clue whats going on with it, so I try the latest OTA or other ROMs?

LeEco is going bankrupt and has shut down US operations along with OTA servers, the only way it's going to get an update is if you ROM it with a compatible ROM from here.

So I need to updates to be able to unlock the bootloader? I can not find 5.8.19S anywhere - any ideas where to snag it?

giveituplouie said:
So I need to updates to be able to unlock the bootloader? I can not find 5.8.19S anywhere - any ideas where to snag it?
Click to expand...
Click to collapse
Having the same problem, just found this:
https://forum.xda-developers.com/showpost.php?p=73593519&postcount=7
and somebody, who tried:
https://forum.xda-developers.com/showpost.php?p=74147818&postcount=23
Have you got another solution?
Edit:
It worked for me, i´m on 5.8.019s now!

Here's what I found for the stock ROM's. Also figured out what was going on for doing a local update. When I changed the name to update.zip and got it to the phone it would be listed as update.zip.zip. Through Astro Manager on and renamed back to update.zip.
https://forum.xda-developers.com/le-pro3/how-to/how-to-date-leeco-le-pro3-root-twrp-100-t3668918

Here is the links that Edward Keefe is sharing from his Google Drive:
5.8.19S https://drive.google.com/open?id=0B2EAg2WU3OwpejROS3piZG43SVU
5.8.20S https://drive.google.com/open?id=0B2EAg2WU3OwpVC1WcUxERmpRLXM
5.8.21S https://drive.google.com/open?id=0B2EAg2WU3OwpS21QTEplYnE4Vlk
I have tested all three of these on 3 Lex727 phones with zero issues.

18s can be unlocked with the same procedure as 19s...

Related

Need Instructions to avoid almost bricking again

Hi guys. I very narrowly (somehow) managed to recover from almost bricking my phone.
I successfully S-Off'd my phone, and previously successfully installed TWRP. I tried to install this ROM:
https://forum.xda-developers.com/ve...m-perfumewl-m60-dev-edition-unlocked-t3442969
When I tried the to flash the ZIP for firmware and for the ROM, the firmware wouldn't install. I tried some other stuff and basically almost bricked my phone. Some how got it to suddenly start being able to use the htc_fastboot commands (????????) and was able to start installing the zip for stock... but it ran an error, I ran it again and it froze... then I forced my phone to reboot and somehow I'm back to having a stock system. No clue what I did.
My question is, can I take a software update on my phone normally (to 7.0) , and then install just that ROM? Or so I need to flash the firmware separately with a command line command? I just don't want to give myself another heart attack tonight. Current firmware version is 1.82.605.6, not rooted, don't believe my recovery is TWRP right now (but I know how to install that one).
I'm just looking for root access and the ability to remove pre-installed Verizon crap (VZW Messager, My Verizon, etc). Thanks guys.
CritKlepka said:
Hi guys. I very narrowly (somehow) managed to recover from almost bricking my phone.
I successfully S-Off'd my phone, and previously successfully installed TWRP. I tried to install this ROM:
https://forum.xda-developers.com/ve...m-perfumewl-m60-dev-edition-unlocked-t3442969
When I tried the to flash the ZIP for firmware and for the ROM, the firmware wouldn't install. I tried some other stuff and basically almost bricked my phone. Some how got it to suddenly start being able to use the htc_fastboot commands (????????) and was able to start installing the zip for stock... but it ran an error, I ran it again and it froze... then I forced my phone to reboot and somehow I'm back to having a stock system. No clue what I did.
My question is, can I take a software update on my phone normally (to 7.0) , and then install just that ROM? Or so I need to flash the firmware separately with a command line command? I just don't want to give myself another heart attack tonight. Current firmware version is 1.82.605.6, not rooted, don't believe my recovery is TWRP right now (but I know how to install that one).
I'm just looking for root access and the ability to remove pre-installed Verizon crap (VZW Messager, My Verizon, etc). Thanks guys.
Click to expand...
Click to collapse
I recommend you install this one instead:
https://forum.xda-developers.com/ve...m-1-85-605-9-aroma-root-root-debloat-t3529732
Follow instructions in OP...or:
1)fastboot flash FW w/o Boot w/ TWRP (htc_fastboot oem rebootRUU, fastboot flash zip...)
2)htc_fastboot reboot-bootloader
3) Finally, go into recovery-- backup and flash ROM (choose root w/ Magisk and debloat)
Thanks, I figured out why it wasn't working before. Used official TWRP, thats why it wasn't working. Wouldn't have thought that'd made that much of a difference.
New problem though; something I really would like to use the Google versions of contacts and dialers. Trying to flash those just made my phone app unusable. So I turned to LineageOS but it REFUSES to boot. Hangs on their little vertical line with a moving circle. Found out AOSP roms don't like VZW firmware? Flashed global firmware, updated through WiFi as much as possible, and then ran into issues with radio, even though I flashed the VZW one. So I reverted those changes, am going through with what you said above to have a working phone (after not having one all day), but any advice on getting Google dialer and contacts? I'd like to use LineageOS but I couldn't get it work at all.
CritKlepka said:
Thanks, I figured out why it wasn't working before. Used official TWRP, thats why it wasn't working. Wouldn't have thought that'd made that much of a difference.
New problem though; something I really would like to use the Google versions of contacts and dialers. Trying to flash those just made my phone app unusable. So I turned to LineageOS but it REFUSES to boot. Hangs on their little vertical line with a moving circle. Found out AOSP roms don't like VZW firmware? Flashed global firmware, updated through WiFi as much as possible, and then ran into issues with radio, even though I flashed the VZW one. So I reverted those changes, am going through with what you said above to have a working phone (after not having one all day), but any advice on getting Google dialer and contacts? I'd like to use LineageOS but I couldn't get it work at all.
Click to expand...
Click to collapse
You've got to read OPs, search threads, etc. Some ROMs work w/ our phone, and some do not. Check out the latest versions of ice and leedroid. Your most likely want to grab the SVN versions is the official versions may not yet support Verizon N firmware
Antny6 said:
You've got to read OPs, search threads, etc. Some ROMs work w/ our phone, and some do not. Check out the latest versions of ice and leedroid. Your most likely want to grab the SVN versions is the official versions may not yet support Verizon N firmware
Click to expand...
Click to collapse
I have been doing a lot of searching, but I've found so many different, conflicting sources of information. For example, one website told me to install LineageOS, was to be on latest Verizon OTA and just normally flash it; that obviously didn't work.
So from what I can see, our choices are Viper, Ice, LeeDroid, NuSense and the one you linked. I'm going to try out LeeDroid... out of curiousity, is there any reason, for example, LeeDroid or Ice haven't posted in this Verizon section with links to their ROMs?
*Edit Two* Dialer wouldn't work out of the "box" so to speak, so I had to go to Phone settings at the bottom, there is a menu called Calling Accounts. Had to go there and tap Receive Incoming Calls... why is that disabled in the first place..? But that seems to be an issue going even as far back as the Nexus 5. But that's how you find the option in the HTC 10 for anyone who comes across this issue too...
Not sure why your having issues with the flashing. Are you doing a full wipe? Not just factory reset. Going from stock to lineage requires a complete format of internal SD card. On the stock roms, most will ask if you are still on marshmallow firmware & are working fine. Again, we need more info on what firmware version your on, version of twrp& how your wiping your device. Most AOSP roms work, but no advanced calling
LOS ROMs will work without issue IF you have flashed the US unlocked firmware at some point in time. This is the only information that we have found from a VzW device with LOS booting and VzW device without. We started a thread awhile ago and is the only known method we currently know of to get LOS booting. Also works for Sprint users.
https://forum.xda-developers.com/verizon-htc-10/how-to/how-to-cm-booting-vzw-vzw-firmware-t3500900

Recovery bricked after Nougat update?

First excuse me for opening an other thread like this, i think i have read all other threats regarding my problem, but none have the same situation
My Huawei M3 Wifi (BTV-W09) seems semi bricked after installation of Nougat Update.
The Installation (Force Install with dload) gave me an error and also while boot i got the error message: "Your device has failed verification and may not work properly."
I have the option to press "Powerbutton" and the device will boot up. I checked the Version and it showed android 7 + EMUI 5. The only problem was that almost every system app was missing, like keyboard, calendar etc. (playstore was there)
So i tried to do the rollback with:
HUAWEI MediaPad M3 8 Rollback Package%28BTV-W09 %2CC900B300%2C EMUI5.0%2BAndroid7.0 rollback to EMUI4.1%2BAndroid 6.0%29
The Installtion (force update) gets stuck at 5% and after like 3-5 minutes the tablet will boot up showing the same boot error that can be skipped with pressing powerbutton. I checked sytem and it still showed "android 7 + EMUI 5" but built : BTV-W09C900B300
I think this is the one i "need" to be able to install the "HUAWEI MediaPad M3 8 Firmware %28BTV-W09 %2CC100B006%2C EMUI4.1%2BAndroid 6.0%29"
Problem is regardless which "update.app" i try to force install will get stuck at 5% and give me same error. I have ADB/Fastboot installed and tried some different things like flashing/unbricking it with "Huawei Multitool" where you can extract like boot.img or recovery.img and try to flash it.
Also getting an error. I can access eRecovery witout problems, the option to fix it by itself by wifi doesn`t work. I can´t access "normal" recovery and i think there is the problem (may got bricked while flashing Nougat?) I think its recovery problem, cause when i boot it up to the "half-installed" Android and go into setting "hard-reset" option i know it would boot up intoi recovery and would erease everything, while bootup it shows error "reset failed".
In fastbootmode i see bootloader: unlocked FRM: unlocked
I tried to install TWRP recovery with adb but get error: adb remote command not allowed
I downloaded like 15 different Android Versions 6+7 Emui 4.1+5 to try with force update but none worked, may i have to flash special version of recovery first?
I just want a normal version of android 6 or 7 i dont mind but at the moment with half working 7 "without" systemapps its a hardtime.
I hope someone can help me.
This isnt my first android device and im not a total noob i unlocked bootloader and flashed kernels on many other phones but with the W-09 where i did nothing special i dont get why "recovery got broken"
Thanks in advance
You haven't read other threads too well: more times people reported that the bootloader got locked after an update still declaring itself unlocked!
Second thing you have not found: the Nougat update consist of 2 packages and the second must be installed from TWRP.
nicolap8 said:
You haven't read other threads too well: more times people reported that the bootloader got locked after an update still declaring itself unlocked!
Second thing you have not found: the Nougat update consist of 2 packages and the second must be installed from TWRP.
Click to expand...
Click to collapse
thanks for your anwser, i read that so i also tried unlocking it "again" and it quotet it is also unlocked in adb. I also know that there are 2 packages. That you need TWRP i didnt know thanks so i am a bit smater now. I think i ll try "relock" and unlock it again might be the right way, thanks for the tip.
kivi90 said:
I think i ll try "relock" and unlock it again might be the right way, thanks for the tip.
Click to expand...
Click to collapse
This is nonsense. Unlock, install the right TWRP then install the second zip package.
nicolap8 said:
This is nonsense. Unlock, install the right TWRP then install the second zip package.
Click to expand...
Click to collapse
i cant unlock cause i dont have the code, on the huawei page i try do make an account and get the code by providing the necessary information.
I just uploaded a picture, i choose "before EMUI5" cause this is the only option i can choose "tablets". --> i choose "tablet wifi" , enter product model "BTV-W09" then the serialnumber i can see in setting: 28D6R17316XXXXXX but then i have the problem to input product id, it say i can get it through "Dialer" app (which i dont have in wifi model ) or the calculator. Problem is in my damaged installation there is no huawei calc, other calcs from store dont work (read that problem in other threats) I tried many apps from appstore to get a product ID but huawei site keeps saying wrong product ID =/
With the program DC Unlocker i am able to see a MEID i dont know if its the right one, i tried my luck with the Product ID Generator from Huawei but it doenst work. (device not supported)
It's very strange that it says bootloader unlocked if you have never unlocked...
And was very stupid to try to installl a beta release without before unlocking and taking a backup.
Exhange your device for a Nokia 3110!
nicolap8 said:
It's very strange that it says bootloader unlocked if you have never unlocked...
And was very stupid to try to installl a beta release without before unlocking and taking a backup.
Exhange your device for a Nokia 3110!
Click to expand...
Click to collapse
yeah at this device i never touched bootloader, i didnt think it would become such a big deal , i didnt want unlocked bootloader or other recovery just newest android. Never had any problems with the "force update function" to come back to stock. I tried DC Unlocker but cant get further cause device need to get into manufature mode (thorugh dialer or calculator which i both dont have) i hope maybe i find one more way.
Did you ever find a fix
Did you ever find a way to fix this. I'm in the same situation. I even did a VPN on my router to give me a Hong Kong address for erecovery and that still didn't work. I have the exact same product. Like you I tried to various attempts to download a new recovery, but nothing works. Nice hardware, but some of the worst software/firmware I have ever dealt with since starting with the first release of Android on the HTC Hero.
kivi90 said:
yeah at this device i never touched bootloader, i didnt think it would become such a big deal , i didnt want unlocked bootloader or other recovery just newest android. Never had any problems with the "force update function" to come back to stock. I tried DC Unlocker but cant get further cause device need to get into manufature mode (thorugh dialer or calculator which i both dont have) i hope maybe i find one more way.
Click to expand...
Click to collapse
I had mostly the same problem. I rolled back to 4.1 using the rollback and the actual 4.1 update.app. I think that puts you on C100 if I remember right. Tablet I have is C128 (USA) but no problem for this step. Get the Product ID from the calculator. Allow OEM unlock in the settings, then unlock it using the unlock code. Email yourself the unlock code because who knows if their website will even be functional next time. Alternatively you can extract the stock calculator from the update_data_usa.zip or whatever and try to use DC with 5.0. That second update zip does not install properly via the dload method, so a bunch of stock apps don't get installed. You can kind of hack it and flash it via TWRP but I didn't do it that way.
Or...you can use firmware finder to force an OTA from 4.1 right up to 5.0 (350), then take that last partial OTA to 351 after as well. The way to do that is via DNS in firmware finder. Find the Full OTA in firmware finder you want, send it to the updater by changing your DNS the way it tells you to, and when it does the OTA, everything will be properly installed basically the official way. Good as new. Flash TWRP to recovery2 and replace the erecovery. Keep the stock recovery as is. Install magisk. Golden.
---------- Post added at 03:36 AM ---------- Previous post was at 03:26 AM ----------
kivi90 said:
So i tried to do the rollback with:
HUAWEI MediaPad M3 8 Rollback Package%28BTV-W09 %2CC900B300%2C EMUI5.0%2BAndroid7.0 rollback to EMUI4.1%2BAndroid 6.0%29
The Installtion (force update) gets stuck at 5% and after like 3-5 minutes the tablet will boot up showing the same boot error that can be skipped with pressing powerbutton. I checked sytem and it still showed "android 7 + EMUI 5" but built : BTV-W09C900B300
I think this is the one i "need" to be able to install the "HUAWEI MediaPad M3 8 Firmware %28BTV-W09 %2CC100B006%2C EMUI4.1%2BAndroid 6.0%29"
Problem is regardless which "update.app" i try to force install will get stuck at 5% and give me same error.
Click to expand...
Click to collapse
Also, as far as the rollback, you need to do the first one (the C900 which is just a compatibility fix to allow rollback, previously used by beta testers I believe). Then you need to do the second one, the C100. If it is getting stuck, try downloading it again and be sure you don't have anything else in the /dload directory on either internal or the sd card. I had one on both at one point so maybe that happened to you. The C900 should be very quick but the C100 will slowly progress after 5% all the way around in several minutes.
When you get to updating back to 5.0, you can choose whichever region you want as long as it is a full OTA. C128 is USA and that's what I bought so that's what I picked. That gets you back in the right OTA update channel after that.
Hi guys,
I started as a novice and have learnt the hard way.
Has anyone tried rollback to EMUI 4.1 EU version on a US device (W09) and are there any problems I should be aware of?
I have had the exact same problem shared in this thread and have gone through the pain of finding a solution. My last resort is to rollback to 4.1 and restart the whole process.
@deV14nt: you suggested that when updating back to EMUI 5.0, I can choose the region even if my EMUI4.1 is EU version. How does this work?
Thanks in advance for your help.

Bluetooth issues - how to solve them?

My new A2017G B08 has no problem finding and connecting with my old LG G2 - but when trying to connect it with my trusty Bluetooth speaker, the Axon doesn't even see it. And while I can find the Axon within just 1-2 seconds from my PC with a BT-Stick, the other way around the Axon doesn't see the PC.
I can life with not finding the PC, but what can I do to make it work with the speaker? The G2 has no issues with that either so the speaker's bluetooth does work.
Go into settings/location and ensure high accuracy is selected. It can improve bluetooth scanning.
RobboW said:
Go into settings/location and ensure high accuracy is selected. It can improve bluetooth scanning.
Click to expand...
Click to collapse
That didn't help. Still, the speaker does not show up when searching for devices.
had the same issue ! b09 fixed it
Mine was fine on B04 and B08 and is still fine on B09 but I don't use any old BT speakers, most devices are fairly new. The car stereo is probably the oldest. It dates back to 2010 with a 2012 firmware update on the BT module.
caesar170988 said:
had the same issue ! b09 fixed it
Click to expand...
Click to collapse
Well, B08 is the latest version I'm getting via OTA update. I guess if nobody else comes up with a solution/tips that might work there's nothing I can do but wait for (hopefully) an Android 8 update that has the issue fixed for my device
Eiion said:
Well, B08 is the latest version I'm getting via OTA update. I guess if nobody else comes up with a solution/tips that might work there's nothing I can do but wait for (hopefully) an Android 8 update that has the issue fixed for my device
Click to expand...
Click to collapse
Don't rely on OTAs... If your bootloader is locked just go to the download center, download the B09 zip, put it in the internal storage and go to the Updates tab, it should appear there
Yeah, if I waited for an OTA my phone would still be on Marshmallow. They had problems with OTA and stopped doing them and advised to do SD updates so you have to download. Could be that a SD update may fix it.
Even then, the latest on the Australian web site is B04. I got B08 from Germany and B09 from Switzerland. It's an international ROM. I don't download from anywhere but ZTE websites.
We rely on other XDA members finding the updates and posting here that it's available.
RobboW said:
Yeah, if I waited for an OTA my phone would still be on Marshmallow. They had problems with OTA and stopped doing them and advised to do SD updates so you have to download. Could be that a SD update may fix it.
Even then, the latest on the Australian web site is B04. I got B08 from Germany and B09 from Switzerland. It's an international ROM. I don't download from anywhere but ZTE websites.
We rely on other XDA members finding the updates and posting here that it's available.
Click to expand...
Click to collapse
The download center is basically all of those but unpacked and uploaded to androidfilehost. And all of that is made by @raystef66 . It's not like you're downloading them from some shady Russian torrent website
RobboW said:
Yeah, if I waited for an OTA my phone would still be on Marshmallow. They had problems with OTA and stopped doing them and advised to do SD updates so you have to download. Could be that a SD update may fix it. [...]
Click to expand...
Click to collapse
Choose an username... said:
The download center is basically all of those but unpacked and uploaded to androidfilehost. And all of that is made by @raystef66 . It's not like you're downloading them from some shady Russian torrent website [...]
Click to expand...
Click to collapse
Guys, I have no idea how to do that and although I did root my G2 I'm not feeling very comfortable updating to anything but the official version for my German Axon 7. Meaning, if updating to the swiss version I'm pretty sure I'd lose my warranty.
Also, I'd need a very basic step by step instruction without too many technical terms (and a link to where to get the file) to feel save enough to do it. It's just that I cannot afford another phone should something go wrong.
So, I'd totally be interested in doing an update to a new firmware version since that might possibly indeed fix my problem (and possibly 1-2 others I have with the phone) - but I'm scared to brick it/lose warranty. Any thoughts on that?
EDIT: I've just checked the ZTE website for downloads and I'm a bit confused... version B10 was Android 6 and version B08 is Android 7.1? So... version B09 is older than mine? Is that what you were suggesting, going back to an older version? Can I even update backwards? Usually devices say something like "The software installed on your device is already the newest version" or something along those lines whenever trying to install a previous software version.
EDIT 2: Found "AXON 7(ZTE A2017G )SD card software package(344070B1405ZTE A2017GV1.2.0B09)N Version" on the ZTE website - but what does "N version" mean? Mine says on its back "ZTE A2017G".
Eiion said:
Guys, I have no idea how to do that and although I did root my G2 I'm not feeling very comfortable updating to anything but the official version for my German Axon 7. Meaning, if updating to the swiss version I'm pretty sure I'd lose my warranty.
Also, I'd need a very basic step by step instruction without too many technical terms (and a link to where to get the file) to feel save enough to do it. It's just that I cannot afford another phone should something go wrong.
So, I'd totally be interested in doing an update to a new firmware version since that might possibly indeed fix my problem (and possibly 1-2 others I have with the phone) - but I'm scared to brick it/lose warranty. Any thoughts on that?
EDIT: I've just checked the ZTE website for downloads and I'm a bit confused... version B10 was Android 6 and version B08 is Android 7.1? So... version B09 is older than mine? Is that what you were suggesting, going back to an older version? Can I even update backwards? Usually devices say something like "The software installed on your device is already the newest version" or something along those lines whenever trying to install a previous software version.
EDIT 2: Found "AXON 7(ZTE A2017G )SD card software package(344070B1405ZTE A2017GV1.2.0B09)N Version" on the ZTE website - but what does "N version" mean? Mine says on its back "ZTE A2017G".
Click to expand...
Click to collapse
You're confusing everything... That is not swiss, it's international. The only thing that COULD void your warranty is unlocking the bootloader, and in some cases people have been able to still claim hardware warranty on their phones by saying that they have not touched the hardware. Also, ZTE provides those updates.
If something happens (it would be basically your fault, such as trying to update with 10% battery or updating with an A2017 or A2017U package) and your phone stops working, just call ZTE and claim warranty. Their update method failed, etc. etc. Although it is borderline impossible to mess up your phone with the stock update method... I think it even tells you that you can't update with less than X% of battery.
The updates are as follows: A2017GV1.0.0B01 to B11 was Marshmallow, and then came A2017GV1.2.0B01 to B09 which is Nougat. I have thought many times that it would have been a lot better if they called them, say, M11 and N09. But this is what we have.
It's not hard at all: Go to the Guides section, there you will find Raystef66's download center. Download the file called A2017G-N-B09 (??), NOT the one under "TWRP flashable Bootstack/Stocksystem images". Those won't work.
After it gets downloaded, connect your phone to the PC. allow MTP transfer from the phone. "Internal Storage" should appear as a folder. If you have an SD card it will appear as another folder beside that on your PC. Open Internal storage. Now that is called the root of the internal storage, where all the folders are located. Just take the zip and throw it there, outside of all the folders (outside of DCIM, Android, and all those).
Then go to the phone, Settings, Update, and select the update.
@RobboW @Choose an username... (thank you very much for writing down all the information on updating the phone!)
Ok, so I did the update directly downloaded from their website. The update worked - indeed though, as somebody else has mentioned elsewhere, the phone now seems slightly slower to react to inputs when scrolling/tapping through the menu. Anyways, that's besides the point.
I tried connecting to the speaker, but still, it does not show up when searching for devices. Interestingly though I tried to make a new connection from my old phone (where I had deleted the connection) and the G2 now also can't find it (although it worked fine when the connection was already set up).
I'm back to trying to get one or the other device connected again. If nothing works, I guess I'm screwed then.
Eiion said:
@[email protected] an username...
Ok, so I did the update directly downloaded from their website - followed their PDF instruction for Update via SD. The update worked - indeed though, as somebody else has mentioned elsewhere, the phone seems slightly slower to react to inputs when scrolling/tapping through the menu. Anyways, that's besides the point.
I tried connecting to the speaker, but still, it does not show up when searching for devices. Interestingly though I tried to make a new connection from my old phone (where I had deleted the connection) and the G2 now also can't find it (although it worked fine when the connection was already set up).
I'm back to trying to get one or the other device connected again. If nothing works, I guess I'm screwed then.
Click to expand...
Click to collapse
Can you find the speaker with your PC?
Did you actually go into the PC's bluetooth settings to allow it to be visible?
Choose an username... said:
Can you find the speaker with your PC?
Did you actually go into the PC's bluetooth settings to allow it to be visible?
Click to expand...
Click to collapse
Sure, I did that when trying to connect it to the PC.
Anyways, I was trying 10-15 more minutes and don't ask me how or why... I did nothing different from all the times before but I finally was able to find the speaker on the Axon 7 and set up the connection. After that I wanted to connect the Axon 7 to the G2 - and while the G2 found the A7 within a second, the A7 did not see the G2. And after that I also tried to connect the G2 again with the speaker which worked as well.
So, all that's left is connecting the PC to the BT speaker - but I guess that's no topic for this forum.
So, thank you guys for your contribution, without I might have given up a few days ago already. Now I made it and have an updated phone. :good:
Eiion said:
Sure, I did that when trying to connect it to the PC.
Anyways, I was trying 10-15 more minutes and don't ask me how or why... I did nothing different from all the times before but I finally was able to find the speaker on the Axon 7 and set up the connection. After that I wanted to connect the Axon 7 to the G2 - and while the G2 found the A7 within a second, the A7 did not see the G2. After I also tried to connect the G2 again with the speaker and that worked as well.
So, all that's left is connecting the PC to the BT speaker - but I guess that's no topic for this forum.
So, thanks for you guys for your contribution, without I might have given up a few days ago already. Now I made it and have an updated phone. :good:
Click to expand...
Click to collapse
Semi-updated... you on B08?
The latest security patch is Dec. 1 and it's on B09. Just informing if you decide to update again
Choose an username... said:
Semi-updated... you on B08?
The latest security patch is Dec. 1 and it's on B09. Just informing if you decide to update again
Click to expand...
Click to collapse
As I had mentioned I was on B08 before the update. I'm on B09 now.
Good stuff, my next suggestion was going to be if you have an option to reset the speaker. No need now.
Sometimes you could get stuck with too many pairings. It's good to delete un-needed pairings on the phone but on a speaker you generally can only reset.
RobboW said:
Good stuff, my next suggestion was going to be if you have an option to reset the speaker. No need now.
Sometimes you could get stuck with too many pairings. It's good to delete un-needed pairings on the phone but on a speaker you generally can only reset.
Click to expand...
Click to collapse
Yeah, I thought of that too and searched the manual for it - but didn't find anything. Then I tried several button press combinations while on or while turning it on... you know, sometimes they simply don't put every function in the manual. But nothing seemed to do it. Or maybe it did - how would I know, it has no display.
But anyways, it works and that's all that matters
@ Eiion,
Have you fixed your phone's problem? I experience the same problem, so have you try other different PC and Bluetooth?
Delete all synced devices in bluetooth list. Then try to sync your device. Seems to work for me.

KB2007 On KB2005 Android 12

I have spent the better part of the evening trying to figure out what is wrong with the full update package for Android 12 for NA/Global. This is the one way out of the many I tried, that reliably worked for the KB2007 T-Mobile USA device to get it to running Android 12 without issues on the North American/Global firmware.
This ideally is for those of us that have a KB2007 that used the MSM Tool conversion to the EU firmware. Using Local Update does not fully convert to the NA/Global, even when using a full update package, which leaves the device with issues. For some reason, when updating to the KB2005 Android 12 using the full firmware image, you lose the second SIM slot, which just makes it worse. After plenty of flashes to figure this out. I have figured out a complicated mess of a way to do so.
I tried going to a couple of the full updates before Android 12 from the EU and still had issues after the update to Android 12 with performance. That is why I decided upon this longer method. Update using the full KB2005 image to Android 12. Easiest place to get it is from Oxygen Updater. Install it via Local Update. Download the rollback app, install it, and download the rollback package to flash through the rollback app. Rolling back to KB2005 using the downgrade image returns dual-SIM to the KB2007. That will have wiped your device so proceed through the setup until finished. Download Oxygen Updater again, download the stable KB2005 Android 12 incremental update through the System Updater, install it, and you should be as close what a KB2007 can get to a KB2005. I tried the full package update but that always disables dual-SIM after updating to Android 12, whether you do a factory reset before the flash and after or not.
Having an MSM Took to directly convert the KB2007 to KB2005 might have made this somewhat easier.
Sadly, it didn't survive a reboot. SIM 2 is still shown, but disabled. There is no way to enable it that I have found, but at least it is reading the info from the SIM 2. Does anyone know of a way to force the toggle for SIM 2?
dang i was coming here to see if anyone was able to do this and or had issues doing so. looks like if we are on an unloced tmo version phone we might be stuck with oos11 till things get figured out if they do. bummer. i really wish i had not waited when they put them on sale and got the normal 8t vs this tmo version those were sold out by the time i saw the sale though. just like i still cant figure out how to get vowifi / wifi calling working on this ive tried everything i could find online and nothing works to add those settings back
oddly im on the latest version of oos11 on the kb2007 converted and i can see sim 1 and 2 but sim 2 is greyed out. i actually was trying to get that working on oos11 and for me it does not work. did you have it working on 11?
Same problem with 12 here. We accidentally updated to 12 via the OTA update and it not only gave us the same symptom (SIM 2 visible, but disabled), but it also screwed up internet connectivity on SIM 1. Calls and text still seemed to work, but internet only via WiFi.
I spent last night and a good chunk of today troubleshooting it, and finally just went back to fully operational latest version of 11 via MSM and local update. It would be nice to be on the latest version, but browsing through the OnePlus forums, it looks like 12 is still a hot mess anyway.
bummer hopefully someone will figure it out sooner or later. i really dont want to go back to the tmobile rom in order to update
I just talked to OnePlus support center and they confirmed unlocked version will not be stock again Once they will finish selling T-Mobile version webpage will be cleaned from any 8T info. I really want to get unlocked for 399. and now only way to get this go for KB2000 CN version that sill stocked. The price for T-Mobile version is good 349 but based on conversion mess I don't want go for that. Also I am sure TM will stop on OOS11 and will not rollout OOS12 ever.
i agree ^^ any updates from anyone on this? any type of workarounds? this sucks i wish i would just went with the one off amazon instead of directly through oneplus now. we have three here we love the phone but i am not sure we will ever be able to upgrade now.
bigfry said:
Same problem with 12 here. We accidentally updated to 12 via the OTA update and it not only gave us the same symptom (SIM 2 visible, but disabled), but it also screwed up internet connectivity on SIM 1. Calls and text still seemed to work, but internet only via WiFi.
I spent last night and a good chunk of today troubleshooting it, and finally just went back to fully operational latest version of 11 via MSM and local update. It would be nice to be on the latest version, but browsing through the OnePlus forums, it looks like 12 is still a hot mess anyway.
Click to expand...
Click to collapse
Can you check the about page after upgraded to OOS12 is this sill showing wrong picture and missing some info?
bigfry said:
Same problem with 12 here. We accidentally updated to 12 via the OTA update and it not only gave us the same symptom (SIM 2 visible, but disabled), but it also screwed up internet connectivity on SIM 1. Calls and text still seemed to work, but internet only via WiFi.
I spent last night and a good chunk of today troubleshooting it, and finally just went back to fully operational latest version of 11 via MSM and local update. It would be nice to be on the latest version, but browsing through the OnePlus forums, it looks like 12 is still a hot mess anyway.
Click to expand...
Click to collapse
I have the same issue you had with the network on mobile data. I downloaded oos 11 and used magisk to install os11 to keep root , however I still have data isdue on the mobile network. Fine on wifi. Any suggestions?
you may want to try to use the msm tool to go back. or try the posted downgrade tool. i personally used the msm tool to go back to stock then re upgraded to latest 11. i hope i dont get hit with it myself. this was on my daughters phone.
Thanks for sharing this instruction!
So basically:
0) Oxygen Updater can be used to download the full/incremental OOS 11/12 kb2005 images mentioned below. (Probably also need to use MSM tool to rebrand as EU version before all these?)
1) System Update - Local Update to install OOS 12 kb2005 (full);
2) "Rollback app" to OOS 11 (rollback);
3) Regular system update to OOS 12 (incremental).
It seems pretty reasonable. Would you instruct more on what "rollback app/package" you use? This is the closest I found online: https://www.droidwin.com/downgrade-oneplus-8-pro-8t-to-oxygenos-11-android-11/ but please correct me if it is not the right one.
Does this method still work now? Do you have dual-sim dual volte/wifi calling working?
jllll said:
Thanks for sharing this instruction!
So basically:
0) Oxygen Updater can be used to download the full/incremental OOS 11/12 kb2005 images mentioned below. (Probably also need to use MSM tool to rebrand as EU version before all these?)
1) System Update - Local Update to install OOS 12 kb2005 (full);
2) "Rollback app" to OOS 11 (rollback);
3) Regular system update to OOS 12 (incremental).
It seems pretty reasonable. Would you instruct more on what "rollback app/package" you use? This is the closest I found online: https://www.droidwin.com/downgrade-oneplus-8-pro-8t-to-oxygenos-11-android-11/ but please correct me if it is not the right one.
Does this method still work now? Do you have dual-sim dual volte/wifi calling working?
Click to expand...
Click to collapse
I just tried this method and dual sim is not working.
alphahere said:
I just tried this method and dual sim is not working.
Click to expand...
Click to collapse
Thanks. I can't even get rollback app working so I gave up. Dual sim immediately after MSM again. Then I just did regular system update to the latest OOS software. Probably just switch to pixel next year.
I can fix this issue but for this i need
Unpack repack rom which is not possible
I try all kitchens but not workable if anyone can help me to unpack repack rom then i can fix it i even got the problem spot
Just need to test it now
If anyone able to do this just tell and i can fix it
But make sure don't mention payload dumper
I need extract whole rom sys ven prod etc
jllll said:
Thanks. I can't even get rollback app working so I gave up. Dual sim immediately after MSM again. Then I just did regular system update to the latest OOS software. Probably just switch to pixel next year.
Click to expand...
Click to collapse
Concur - Oneplus needs dual sim in the US. The carriers have blocked this for years but that wall in falling. Almost all the flagship and some midrange phones have e-sim and physical sim. So dual sim is here to stay. Oneplus needs to get on board the train.
I have this some issue after upgrading to Android 12. Is there any way to roll-back to Android 11, WITHOUT losing data and needing to wipe? And would it then allow the dual-sim to be working again?
Also, has anyone else tried the above method and had success with having a dual-sim Android 12 using the T-mobile KB2007?
raven911 said:
Also, has anyone else tried the above method and had success with having a dual-sim Android 12 using the T-mobile KB2007?
Click to expand...
Click to collapse
I can fix but need to unpack repack rom
If anyone can guide me tu unpack
System_ext
System
Vendor
Product odm then I'll make fix rom for this
Can build for samsung but in this I'm stuck with dynamic partitions
Mr Hassan said:
I can fix but need to unpack repack rom
If anyone can guide me tu unpack
System_ext
System
Vendor
Product odm then I'll make fix rom for this
Can build for samsung but in this I'm stuck with dynamic partitions
Click to expand...
Click to collapse
If you unpack / repack, then will we lose SafetyNet and Widevine?
raven911 said:
If you unpack / repack, then will we lose SafetyNet and Widevine?
Click to expand...
Click to collapse
Ofcourse not its not rooting process
Even i can do with rooted device but if have fully rw access

Device not starting/black screen after stock-ROM flash via Odin

Hello, everyone,
I tried to install LineageOS on my S10 Plus yesterday. That worked so far, but I found that it didn't have a decent camera app and the Samsung Watch wasn't that easy to connect either. So I thought I'd just go back to the Stock ROM again. I then downloaded the latest stock firmware according to this guide and installed it with Odin. The installation also runs through, after the installation the mobile phone starts and after the start screen there is an Android man with the signature "Erasing". After a few seconds, the device turns off and stays black. Even if I put it on the charger or try to restart it, nothing happens. I keep getting into download mode and recovery, but that's about it. Multiple reinstallations and resets via the recovery didn't help - the phone just won't start.
I used the CSC_... and not the HOME_CSC_... at the firmware is the right one for my phone.
Is there any way I can salvage the device? I'm afraid that something in the memory is defective now, which has nothing to do with the flashing itself. Do you have any ideas?
Many thanks!
tefracky said:
Hello, everyone,
I tried to install LineageOS on my S10 Plus yesterday. That worked so far, but I found that it didn't have a decent camera app and the Samsung Watch wasn't that easy to connect either. So I thought I'd just go back to the Stock ROM again. I then downloaded the latest stock firmware according to this guide and installed it with Odin. The installation also runs through, after the installation the mobile phone starts and after the start screen there is an Android man with the signature "Erasing". After a few seconds, the device turns off and stays black. Even if I put it on the charger or try to restart it, nothing happens. I keep getting into download mode and recovery, but that's about it. Multiple reinstallations and resets via the recovery didn't help - the phone just won't start.
I used the CSC_... and not the HOME_CSC_... at the firmware is the right one for my phone.
Is there any way I can salvage the device? I'm afraid that something in the memory is defective now, which has nothing to do with the flashing itself. Do you have any ideas?
Many thanks!
Click to expand...
Click to collapse
same thing happened to me today. but I flashed my s10e the bootloader and modem file of android 9 from twrp, the phone did not boot up and I loaded the stock rom again, then when I open it, it's the same as yours, I really need urgent help.
Releases · corsicanu/9820-bootloaders_and_modems
Contribute to corsicanu/9820-bootloaders_and_modems development by creating an account on GitHub.
github.com
EDİT: Anyway, I solved the problem, I flashed the bootloader and modem file that is suitable for my current version from the same site with twrp and the phone turned on. maybe you can solve it by flashing the bootloader and modem file suitable for the current version. try if you want
Thanks a lot, this worked!
tefracky said:
Thanks a lot, this worked!
Click to expand...
Click to collapse
I'm glad it worked.
I was very afraid that the phone died, what did you do for 5 days in this state?
Now I have a question in my mind: When Samsung releases an update in the future, will the bootloader and modem files be updated when we update it with odin? won't it be updated? After that, do we will always update manually as twrp? do you have any idea?
Well, I simply didn't use a mobile phone in these days. It was a very "interesting" experience, but not a huge problem. I sometimes opened WhatsApp as Windows App (interestingly, which works without phone).
I don't know, what happens at a Samsung Update, but until Android 13, I will not update (so probatly never). In our German forum (www.android-hilfe.de), a pre rooted and debloated "Stock"-Firmware is provided, but I can't install it, since my Bootloader is too new (V15 instead V14 for the ROM). When it is possible, I will install this firmware. If you are interested, here is the link: https://www.android-hilfe.de/forum/...3-2022-stock-rom-v2-0-pre-rooted.1000713.html
tefracky said:
Well, I simply didn't use a mobile phone in these days. It was a very "interesting" experience, but not a huge problem. I sometimes opened WhatsApp as Windows App (interestingly, which works without phone).
I don't know, what happens at a Samsung Update, but until Android 13, I will not update (so probatly never). In our German forum (www.android-hilfe.de), a pre rooted and debloated "Stock"-Firmware is provided, but I can't install it, since my Bootloader is too new (V15 instead V14 for the ROM). When it is possible, I will install this firmware. If you are interested, here is the link: https://www.android-hilfe.de/forum/...3-2022-stock-rom-v2-0-pre-rooted.1000713.html
Click to expand...
Click to collapse
thanks, if i'm going to use stock rom i prefer to root it myself

Categories

Resources