Related
After installing MedroM I got this problem and couldn't connect to google account and every google app would crash if I tried to log in, so I flashed b161 and I still have this problem, even after numerous factory resets, has this ever happened to anyone ?
Yes, it is happening to other guys around here...
In fact is happening to all who flash B160/B161 firmware...
Is not possible to flash any firmware previously to B160/B161.
Workaround is to unlock bootloader, flash twrp, root it, reflash oeminfo for your device,
and after that you can flash another firmware again.
gtdaniel said:
Yes, it is happening to other guys around here...
In fact is happening to all who flash B160/B161 firmware...
Is not possible to flash any firmware previously to B160/B161.
Workaround is to unlock bootloader, flash twrp, root it, reflash oeminfo for your device,
and after that you can flash another firmware again.
Click to expand...
Click to collapse
i'm in the same situation, i tried to do what you've said, but twrp says that the installation failed. how can I have play store working again? please help, this situation is driving me crazy!
i'm on c900 b161.
I had the same issue. I did a clean flash of the new 161 update and that made my device a C900. I have a Eurpoean model (T-Mobile Germany).
After 2 days of trying different stuff, here's what gave me a functional device with TWRP and Root back:
-Back up any data you want to keep, obviously.
-Reflash stock ROM (put UPDATE.APP on your dload/ folder on the separate SD card, then boot into the update function by turning the phone off and then holding Vol+, Vol-, Power. Just wait until it's finished.
-Unlock Bootloader again
-Download the Toolkit: http://forum.xda-developers.com/huawei-p9lite/development/europe-vns-l31-toolkit-bootloader-t3432873
-Flash TWRP through the toolkit
-Boot TWRP and root
-In Android, enable ADB
-In the Toolkit, go to Dual Sim>Individual and select the appropriate custom.bin and oeminfo.img from the thread of the toolkit. For my European one it was L31 SS C432. Press flash and grant Root permissions on your phone.
-Turn off your phone and flash the stock ROM again like in step 1.
-If you want root, you need to unlock the Bootloader again, flash TWRP and then root it from there.
DON'T WIPE ANYTHING IN TWRP OR YOU WILL HAVE TO START ALL OVER AGAIN!
Don't ask me how I know.
Hope this saves someone from wasting their time with this nonsense like I have.
No need to touch the oem stuff, just extract the boot.img and system.img and flash through adb, for dat you need bootloader unlocked and fastboot drivers then you can downgrade firmware and fix your sign problem or just wait for a new firmware
raffabraz said:
No need to touch the oem stuff, just extract the boot.img and system.img and flash through adb, for dat you need bootloader unlocked and fastboot drivers then you can downgrade firmware and fix your sign problem or just wait for a new firmware
Click to expand...
Click to collapse
That would be much simpler, I didn't consider that. Would you mind writing up a guide?
I've had the same issue and have resolved it pretty easily,
i did the following steps ;
- download both medrom versions
- do full factory reset
- install medrom v1
- do all settings of google etc
- reboot recovery and install v2
- wipe dalvik and reboot
-- all works now except for the forceclose on facebook
ps : this answer is also in the thread ( not as extended as this but it's there )
Edit : some other apps are Force closing to, my guess is that there's a shared resource of some kind that's corrupted or something..
sirlex said:
I've had the same issue and have resolved it pretty easily,
i did the following steps ;
- download both medrom versions
- do full factory reset
- install medrom v1
- do all settings of google etc
- reboot recovery and install v2
- wipe dalvik and reboot
-- all works now except for the forceclose on facebook
ps : this answer is also in the thread ( not as extended as this but it's there )
Edit : some other apps are Force closing to, my guess is that there's a shared resource of some kind that's corrupted or something..
Click to expand...
Click to collapse
Force closing is caused by the oeminfo in my experience. Can you check in the "About Phone" section which build number your phone currently has? Should be something along the lines of "VNS-L31C432B161" where C432 indicates the region code.
since I am Running MEDROM v2 it shows just that. However , I do know it is based on b161
HeavyHDx said:
I had the same issue. I did a clean flash of the new 161 update and that made my device a C900. I have a Eurpoean model (T-Mobile Germany).
After 2 days of trying different stuff, here's what gave me a functional device with TWRP and Root back:
-Back up any data you want to keep, obviously.
-Reflash stock ROM (put UPDATE.APP on your dload/ folder on the separate SD card, then boot into the update function by turning the phone off and then holding Vol+, Vol-, Power. Just wait until it's finished.
-Unlock Bootloader again
-Download the Toolkit: http://forum.xda-developers.com/huawei-p9lite/development/europe-vns-l31-toolkit-bootloader-t3432873
-Flash TWRP through the toolkit
-Boot TWRP and root
-In Android, enable ADB
-In the Toolkit, go to Dual Sim>Individual and select the appropriate custom.bin and oeminfo.img from the thread of the toolkit. For my European one it was L31 SS C432. Press flash and grant Root permissions on your phone.
-Turn off your phone and flash the stock ROM again like in step 1.
-If you want root, you need to unlock the Bootloader again, flash TWRP and then root it from there.
DON'T WIPE ANYTHING IN TWRP OR YOU WILL HAVE TO START ALL OVER AGAIN!
Don't ask me how I know.
Hope this saves someone from wasting their time with this nonsense like I have.
Click to expand...
Click to collapse
Thank you so much , you saved my phone !!
Fllashing stock rom again isnt necessary , just flash the oeminfo, reboot, they will tell you an encryption password, so you have to do a factory reset AND DONE !
simo255 said:
Thank you so much , you saved my phone !!
it doesn't need to reflash stock rom again, just flash the oeminfo, reboot, they will tell you an encryption password, so you have to do a factory reset AND DONE !
Click to expand...
Click to collapse
Interesting, when I tried to do a factory reset after that screen, it always failed.
HeavyHDx said:
Interesting, when I tried to do a factory reset after that screen, it always failed.
Click to expand...
Click to collapse
You have to flash the stock recovery to do a Factory reset
medRom v2 fix
Hi all.
I think i found solution for Google login issue.
I use European VNS-L21-C432B161 dual sim phone with lattest rom.
I flashed medRom v2 with full wipes.
Ofcourse i Can not log in Google Services.
Today i download 3 Google apk files. Installed and it works.
Sorry. I cant post ling on XDA now.im newbie
Link in My profils.
There is instruction how i do:
1. Installed Gmail apk and login.
2. Installed Android System Web Wiev apk.
3. Installed Google Play Service apk
Proof: in My profils description in Youtube
Download Files: watch in YOUTUBE description.
Hope helps for someone.
Could someone provide me the correct oeminfo and custom.bin for a European/German model? C432? The images inlcuded in the toolkit don't work for me, it still crashes or can't communicate with the google server
Deddline said:
Hi all.
I think i found solution for Google login issue.
I use European VNS-L21-C432B161 dual sim phone with lattest rom.
I flashed medRom v2 with full wipes.
Ofcourse i Can not log in Google Services.
Today i download 3 Google apk files. Installed and it works.
Sorry. I cant post ling on XDA now.im newbie
Link in My profils.
There is instruction how i do:
1. Installed Gmail apk and login.
2. Installed Android System Web Wiev apk.
3. Installed Google Play Service apk
Proof: in My profils description in Youtube
Download Files: watch in YOUTUBE description.
Hope helps for someone.
Click to expand...
Click to collapse
Installing Android System Web View apk from apkmirror solved the problem for me (arm + x86 package). Thank you
HeavyHDx said:
I had the same issue. I did a clean flash of the new 161 update and that made my device a C900. I have a Eurpoean model (T-Mobile Germany).
Click to expand...
Click to collapse
I got my P9 Lite from Congstar in Germany. I didn't knew, that the device would be branded by Telekom. I flashed the B161 and couldn't connect to any google account. Thankfully updating the webview apk via apk mirror solved this problem. But this leaves me with 2 questions and maybe you could answer these...?
1) Do you know which stock rom would work the best with my device (VNS-L31 without the possibility to use two sim cards ) and where I could download this stock rom.
2) Is the B161 supposed to work fine after solving this issue or are there other problems with it?
I would be really happy if someone of you could help me. :good:
MartinMo said:
1) Do you know which stock rom would work the best with my device (VNS-L31 without the possibility to use two sim cards ) and where I could download this stock rom.
2) Is the B161 supposed to work fine after solving this issue or are there other problems with it?
Click to expand...
Click to collapse
1) The best stock ROM would either be, well, the stock ROM, or the Revolution ROM.
2) I've had some strange behavior with Relay for Reddit and frequent crashes of WhatsApp when sending messages. Right now I'm on Lineage OS 14.1 and it's really great. Camera's a bit slow, but otherwise I love it. I missed stock Android.
HeavyHDx said:
1) The best stock ROM would either be, well, the stock ROM, or the Revolution ROM.
Click to expand...
Click to collapse
Isn't Nougat still a beta...? I'm looking for a stable stock version of EMUI...
HeavyHDx said:
2) I've had some strange behavior with Relay for Reddit and frequent crashes of WhatsApp when sending messages. Right now I'm on Lineage OS 14.1 and it's really great. Camera's a bit slow, but otherwise I love it. I missed stock Android.
Click to expand...
Click to collapse
Thank you, tomorrow I'll test if Whatsapp working fine or not, that's important for me. Is Lineage 14.1 the most stable Lineage version?
Nougat is still in beta, yes. The full version is expected to come out within the next few weeks.
14.1 refers to the Android version which is 7.1.1. They adopted CyanogenMod's naming scheme. You'll still need to update LineageOS to get bugfixes and such. The dev releases a new update every 2 or 3 days, just check their website periodically.
Deddline said:
Hi all.
I think i found solution for Google login issue.
I use European VNS-L21-C432B161 dual sim phone with lattest rom.
I flashed medRom v2 with full wipes.
Ofcourse i Can not log in Google Services.
Today i download 3 Google apk files. Installed and it works.
Sorry. I cant post ling on XDA now.im newbie
Link in My profils.
There is instruction how i do:
1. Installed Gmail apk and login.
2. Installed Android System Web Wiev apk.
3. Installed Google Play Service apk
Proof: in My profils description in Youtube
Download Files: watch in YOUTUBE description.
Hope helps for someone.
Click to expand...
Click to collapse
Installed Android System Web Viev .apk did the trick for me, too. muchos gracias.
Just a little suprise - Xiaomi released an global ROM for our beloved device!
Get more Info here
http://en.miui.com/thread-526390-1-1.html (announcment, recovery and fastboot image)
and here
http://en.miui.com/download-317.html#471 (recovery / update image)
With that global ROM regular OTA updates should be no problem anymore
This is an fastboot ROM? Exist an global ROM for twrp recovery?
vergilbt said:
This is an fastboot ROM? Exist an global ROM for twrp recovery?
Click to expand...
Click to collapse
Second link
Gesendet von meinem Xiaomi Mi MIX
hey guys i have a locked bootloader, how can i flash? tried all method
long.nguyen said:
hey guys i have a locked bootloader, how can i flash? tried all method
Click to expand...
Click to collapse
request to have the bootloader unlocked then.
I assume we'll have to manually install google apps. I'm updating it via the updater app and seeing if that'll work even tho I've got twrp .
Is it better flashing with Recovery or Fastboot?
Why the Full ROM size is 1,5 GB and the Fastboot is 1,7 GB?
Ninja1400 said:
Is it better flashing with Recovery or Fastboot?
Why the Full ROM size is 1,5 GB and the Fastboot is 1,7 GB?
Click to expand...
Click to collapse
I was able to use the updater app to install the recovery rom no problem. very smooth.
But now my work application doesn't work because something to do w/ work profile not supported maybe.
Hi.If you flash fastboot rom do u loose the TWRP recovery
Yes I lost twrp.
But the bootloader remains unlocked.Are u able to flash twrp and root again?
Can someone tell me if I'll be able to get OTA updates if I install this global rom? Thanks
nizaamh said:
But the bootloader remains unlocked.Are u able to flash twrp and root again?
Click to expand...
Click to collapse
I think you should be able to. When I used the MIUI Updater app, it rebooted into TWRP to auto-install the Global firmware with no issues on the touchscreen. But it's possible to think that twrp may need to be updated to be used w/ Global like it did in RC1 or RC2.
samanbabah said:
Can someone tell me if I'll be able to get OTA updates if I install this global rom? Thanks
Click to expand...
Click to collapse
It would make sense to do it this way. Once you have global, any new global updates would be updated via the MIUI Updater OTA.
Thanks.And how do I find the rom.No FC or random reboot issues.Google app fc's
Flashed using MI flash tool and relocked boot loader so I could have android pay. Did a factory reset after flash and have had no problems so far. Stable clean rom. Had issues with flash tool that resolved when I out all the files in a folder at the root (I put them in c:\rom). Flash tool didn't like a long nested folder name (sip aid the name was too long)
TGUY25 said:
Flashed using MI flash tool and relocked boot loader so I could have android pay. Did a factory reset after flash and have had no problems so far. Stable clean rom. Had issues with flash tool that resolved when I out all the files in a folder at the root (I put them in c:\rom). Flash tool didn't like a long nested folder name (sip aid the name was too long)
Click to expand...
Click to collapse
So does Android Pay works?
Yes once you lock the boot loader. Safety net helper comes up green and I can add my card. You do have to update play services after ROM install as it's been updates since the rom was built. After your first reboot after installing new rom you will get a notification to update play services
Guys try open Google map and click on timeline. Mine says cannot clnnect
long.nguyen said:
Guys try open Google map and click on timeline. Mine says cannot clnnect
Click to expand...
Click to collapse
Mine works fine. I had other issues w/ google but I ended up resetting the phone to factory and everything runs as expected without major issues.
The Global Rom still has the
1. wallpaper carousel issue if using 3rd party launcher
2. cannot search for bluetooth devices for the Xiaomi auto unlock feature, the google option can add the devices, but it doesn't unlock the screen
3. google map feature does not work w/ a dual app that I use.
Can someone install football manager mobile 2017 and test? I have force crash. And ps I purchased on play store
Hey All, just got a MIX so I'm a newbie and apologies if my question has been covered extensively in a past thread.
The rom that came with my mix was xiaomi.eu. I used the Recovery Method to flash the Official Global Rom. However, when I did I didn't loose any data AT ALL.........it took a while for the recovery flash to go through (like 5-10 minutes), but then my phone just rebooted and all my apps, wallpaper, etc were there.
I checked, and the current MIUI Version is MIUI Global 8.2 Stable 8.2.1.0 (MAHMIDL).
Also, I tried to use Android Pay, got the error message, downloaded and ran the CTS app, and still failed. Does this mean I should get my bootloader unlocked (already submitted request) and fast flash and relock the bootloader??
The final steps to Remove "Vendor ROM" that does not have the Update Option in Settings Or Unbrick Le Max 2 or simply Update Le Max 2 to latest EUI.
NOTE: This method should address the following weird problems:
1. Le Max 2 TWRP Seeing 0MB in Internal Storage. Unable to access the ROM Storage
2. Encrypt Option Greyed Out In Settings-->Fingerprint and Security
2. Update Option missing in Settings.
3. Fingerprint Sensor not working... If it still gives trouble... Calibrate the FP Sensor in its settings. Or register the same fingerprint multiple times.
This method should work on ALL versions of Le Max 2 including X820 X829 X821
Before starting... Remove ALL USB peripherals that might interfere with the process. Use USB Ports on the PC/Laptop... DO NOT use USB Hubs... Even if the phone appears dead... Connect it Power Outlet and let it charge for an hour.
1. Download the latest Stable EUI... from LeEco Website Directly .
2. Download the FlashOne v1.9 And Service ROM From HERE.
UPDATE: FlashOne v2.0 has been released! Here's the LINK.. It is a bit more advanced and offers the ability to format User Data for a Cleaner Flash
3. Download Qualcomm Drivers
4. Put Le Max 2 in EDL (Emergency Download Mode) by pressing Volume +, Volume - and Power Button Simultaneously. For those having difficulty..... Here are few tips.
Connect the Phone to PC. If the phone is Switched/Powered On... Then Power Off the phone and Switch Back On with the Key Combinations.
OR
If the Phone is Switched Off... Then Use the Key Combination to put the phone in EDL Mode..
In either case..... the PC will make a sound of Disconnection and Reconnection of an USB peripheral. AND you will see Qualcomm QDLoader 9008 Driver Installation. To verify the same... go to Device Manager in Win 7 / Win 10 and Under Ports (Com & LPT)... you should see Qualcomm HS-USB QDLoader 9008 (COMXX).. The XX corresponds to a particular COM Port. Remember this port.
5. Once the Le Max 2 is in Qualcomm QDLoader 9008 EDL Mode... Start the FlashOne Software.
6. Choose “Qualcomm – flash dead phone” from the drop down menu next to “Flash type”.
7. Click “Refresh button” next to “Select Device”. Here your Le Max 2 will show up but in COM Number (ComXX)
8. Browse for our Qfil/service ROM by clicking “Select File”.... You can technically select the Latest EUI ROM... But it is safer with Service ROM. DO NOT Unzip the ROM File.
9. After everything is set up under “Settings”, Press “Flash” button.
10. Installation can take anywhere between 10 to 20 minutes. Have Patience.
There are chances that the Flashing might fail. In case it does... Simply put the phone in EDL Mode again... and restart the procedure.
11. After the FlashOne confirms successful flash... Wait for 15 - 20 seconds. Then Power On the phone by pressing the Power Button for at least 60 seconds. Do Not Panic due to the long press.. Press it until the phone vibrates.
12. The Le Max 2 should be in Developer Version of EUI with an unlocked Bootloader and STOCK recovery.
13. The Developer ROM has the “Format Virtual SD card” setting in Settings Menu--> Backup/Reset--> Factory Reset.. Use the setting to get back the 50+GB
[You can also use the option Format Data in TWRP Recovery instead and the partition will 64GB correctly instead of 10 GB initially. Read ahead for the procedure]
14. Once you have a working Le Max 2... there are two directions:
Install Latest Stable EUI ROM... with Update Option
OR Install TWRP Recovery / ROOT / Custom ROM
15. a. For those who wish to install Stock ROM... Simply rename it to "update" (DO NOT Add .zip... Else the file will look like update.zip.zip) and place the update.zip file in ROOT of the phone. Thereafter Switch Off the Phone... Enter Recovery by pressing Volume + and Power Button... Choose Update System AND the other setting to Clear All Data. Your Le Max 2 should update without any error.
15. b. For those who want TWRP and ROOT:
* Download the latest TWRP (For Le Max 2) and SuperSU from their respective websites. Download and Install ADB and Fastboot From HERE.
* Copy the SuperSU Zip File to the ROOT of the Phone.
* Unzip and Rename the TWRP recovery to Recovery (The file should be Recovery.img.... NOT Recovery.img.img)
* Put the Le Max 2 into Fastboot Mode By Pressing Volume - and Power Button
* Go to the ADB Install Folder and Press Shift & Right Click to get & select “Open command window here“. Confirm Fastboot is working by Entering Command: Fastboot Devices.. You should see a random string of letters followed by the word Fastboot. If you do not see the same..... the installation didn't complete successfully.
* In the Command Window.. Type: fastboot flash recovery recovery.img
* Enter the following Command: fastboot boot recovery.img
* Once the Phone has entered the Recovery... Flash the SuperSU Zip file and you will have ROOT capabilities.
* Take FULL Backup of your device and then install ANY Custom ROM.
Do let me know your results.
[Update]: There's a simple method you could try to get the Update Option Back in Le Max 2 Phone that arrived with Vendor ROM... Using the default File Manager Tap on the Update.zip file and select Upgrade Option. This will force the phone to Update using the ROM file. This method is for people who could not update through the Stock Recovery and received Errors.
After QFil/flashone my lemax2 still bootloops. I've tried flashing other roms via recovery but it reboots mid installation.
Any advice?
Try Another QFil / Service ROM
Yisheng said:
After QFil/flashone my lemax2 still bootloops. I've tried flashing other roms via recovery but it reboots mid installation.
Any advice?
Click to expand...
Click to collapse
My advice is try another Qfil. These files are quite large and hence the one you downloaded might have some corruption.
Try THIS File
Hi, the link to the Leeco website is down...is there any alternative for downloading the latest stable EUI?
I downloaded the 23s from another website, renamed "update" but when I try to update via recovery it fails, cause: corrupted.
Any suggestion on this?
Thanks a lot in advance
ermonnezza said:
Hi, the link to the Leeco website is down...is there any alternative for downloading the latest stable EUI?
I downloaded the 23s from another website, renamed "update" but when I try to update via recovery it fails, cause: corrupted.
Any suggestion on this?
Thanks a lot in advance
Click to expand...
Click to collapse
You may try to use twrp to flash it, you downloaded version is a twrp backup version...
Thanks for the suggestion but I'm trying to get back to stock for other phone issues... So I wanted to avoid to install twrp, if possible.
Any link to a stock rom that can be updated via stock recovery?
You know I just going to blame Android 7.0 Nougat any chance we can have a CyanogenMod 13 6.01 based foxfi friendly ROM ?
ermonnezza said:
Thanks for the suggestion but I'm trying to get back to stock for other phone issues... So I wanted to avoid to install twrp, if possible.
Any link to a stock rom that can be updated via stock recovery?
Click to expand...
Click to collapse
I used the 23s from this link: https://bbs.le.com/zt/eui/le_max2.html
I flashed it from an indian rom. It will change your bootloader to chinese, though (not really an issue). And your recovery too, I guess (don't panic, it's bilingual). It will also update /firmware, and that should help with many issues.
However, there's no need to flash TWRP in order to use it: you can just boot it ( fastboot boot TWRPname.img).
At the last step, my indian rom is not getting flashed. Saying corrupted!!. Yesterday I updated with the same (rom) file from the system updater when I did not root the device.
"[Update]: There's a simple method you could try to get the Update Option Back in Le Max 2 Phone that arrived with Vendor ROM... Using the default File Manager Tap on the Update.zip file and select Upgrade Option. This will force the phone to Update using the ROM file. This method is for people who could not update through the Stock Recovery and received Errors."
Following these steps got the same error.
Edit: I am pretty much sure the developer chinese rom has the issue. It does not let you update with the Indian rom. Pretty bad.
Did anyone succeed to flash the indian rom the phone came with, or any indian rom from these chinese developer rom?
---------- Post added at 03:52 AM ---------- Previous post was at 03:15 AM ----------
BTW, the indian latest stock rom 5.8.019s can not be download from anywhere now. Can you give me a link that works now?
deltasata said:
At the last step, my indian rom is not getting flashed. Saying corrupted!!. Yesterday I updated with the same (rom) file from the system updater when I did not root the device.
"[Update]: There's a simple method you could try to get the Update Option Back in Le Max 2 Phone that arrived with Vendor ROM... Using the default File Manager Tap on the Update.zip file and select Upgrade Option. This will force the phone to Update using the ROM file. This method is for people who could not update through the Stock Recovery and received Errors."
Following these steps got the same error.
Edit: I am pretty much sure the developer chinese rom has the issue. It does not let you update with the Indian rom. Pretty bad.
Did anyone succeed to flash the indian rom the phone came with, or any indian rom from these chinese developer rom?
---------- Post added at 03:52 AM ---------- Previous post was at 03:15 AM ----------
BTW, the indian latest stock rom 5.8.019s can not be download from anywhere now. Can you give me a link that works now?
Click to expand...
Click to collapse
It is the link of stock Indian eui 5.8.019s
https://drive.google.com/file/d/0BymbvUDXUaNlTjN6X0g1ME1helk/view?usp=drivesdk
Akashsundar said:
It is the link of stock Indian eui 5.8.019s
https://drive.google.com/file/d/0BymbvUDXUaNlTjN6X0g1ME1helk/view?usp=drivesdk
Click to expand...
Click to collapse
Yes
Akashsundar said:
It is the link of stock Indian eui 5.8.019s
https://drive.google.com/file/d/0BymbvUDXUaNlTjN6X0g1ME1helk/view?usp=drivesdk
Click to expand...
Click to collapse
Thanks a lot
Have any one flash this ROM
If there is any bugs reply here I will prepare fix for it
Hello...
Where can I find the original rom for le max 2 x820 with no system update please
thanks .
http://g3.letv.cn/218/24/9/letv-hdt...1S-5.9.020S.zip?b=123456&platid=5&splatid=500
Is 23S whit recovery stock.
Ok so I did as said in your post, but big problem for me : My screen is not split in two and both side are reversed.... I tried install roms goind thought twrp the problem is the same, and doing the manipulation all over again trough flashone doesn't solve my problem either. I really need someone's help on this one please.
x820 64g 6g
---------- Post added at 04:23 PM ---------- Previous post was at 04:22 PM ----------
Akashsundar said:
Have any one flash this ROM
If there is any bugs reply here I will prepare fix for it
Click to expand...
Click to collapse
I do have problem (see the post right above). Any Ideas?
Ok so, I did as shown in the topic : https://forum.xda-developers.com/le-max-2/help/flash-eui-rom-fastboot-t3525831
download twrp (The one I know didn't had the touchscreen issue)
boot from twrp (wish I had know about it before!)
upload zip file to /sdcard ( here's the catch, while in TWRP in don't have access to adb, the phone doesn't connect to pc or I don't know even I mount it, could be me. So i just put the archive at the root of the phone before booting to twrp from adb)
install rom
reboot
And ... it's ****ING WORKING!*
Really big thanks to ThE_MarD for his help!
HI, i hv the same problem likes yours with split screen.
Possible to share the steps how you manage to solved it.
Update:
Hi, I just managed to resolved it.
Download the given recovery 19S and save it on a USB drive.
Run twrp and press button wipe as our screen is reversed.
Then look for the file at external drive USB.
Just install it and once it is done..... the screen will return to normal
deltasata said:
At the last step, my indian rom is not getting flashed. Saying corrupted!!. Yesterday I updated with the same (rom) file from the system updater when I did not root the device.
"[Update]: There's a simple method you could try to get the Update Option Back in Le Max 2 Phone that arrived with Vendor ROM... Using the default File Manager Tap on the Update.zip file and select Upgrade Option. This will force the phone to Update using the ROM file. This method is for people who could not update through the Stock Recovery and received Errors."
Following these steps got the same error.
Edit: I am pretty much sure the developer chinese rom has the issue. It does not let you update with the Indian rom. Pretty bad.
Did anyone succeed to flash the indian rom the phone came with, or any indian rom from these chinese developer rom?
Click to expand...
Click to collapse
Hi.
Yes. After "QFIL", i also didn't update my device from DEV ROM with any Stock ROM (Indian or Chinese versions) by "upgrade.zip" without get the "corrupted file" error. So by TWRP, i installed 16S Indian Stock ROM -- TWRP informed that i have "no OS installed" but i proceeded and restarted from TRWP. It initialized the new ROM, and after the first setup, i restarted the device to complete any system operations after the first boot, and i updated the device with the Indian 19S with the EUI updater ( tapped "upgrade.zip" file). The device now have the stock recovery and boot in english (not chinese), and the EUI in all languages available on "India 19S Stock ROM".
Stock ROMS:
Le Max 2 All Official Stock Firmware links
Best regards.
NextGear said:
Hi.
Yes. After "QFIL", i also didn't update my device from DEV ROM with any Stock ROM (Indian or Chinese versions) by "upgrade.zip" without get the "corrupted file" error. So by TWRP, i installed 16S Indian Stock ROM -- TWRP informed that i have "no OS installed" but i proceeded and restarted from TRWP. It initialized the new ROM, and after the first setup, i restarted the device to complete any system operations after the first boot, and i updated the device with the Indian 19S with the EUI updater ( tapped "upgrade.zip" file). The device now have the stock recovery and boot in english (not chinese), and the EUI in all languages available on "India 19S Stock ROM".
Stock ROMS:
Le Max 2 All Official Stock Firmware links
Best regards.
Click to expand...
Click to collapse
Hey bro, I have the same problem. What twrp you used? When I try to install 16s indian twrp gives an error "Patching system image..." for too much long time, so it stop to install it.
This is totally CLEAN and Typically ENGLISH (OFFICIAL) version that means no chinees APPS no issue.
Donot forget to make a backup before starting.
Steps to Follow: (FOR TWRP installed user)
1. Download 20s OTA file from here.
2. Download 21s OTA file from here. (Donot Download this ZIP file as i got an OTA update of 21S after installing 20s)
3. Goto TWRP recovery.
4. Formate everything. (Cashe, Delvik, Sysytem,Data)
5. Flash the 20s Rom (Provided in STEP 1)
6. After Installing and setting up phone, You are ready to GO BACK to official stock recovery.
Steps to Follow: (FOR already on stock recovery users)
7. Download the 21s recovery (provided in step # 2)
8. change the name to update.zip
9. put it into the root folder.
10. Goto stock updater and slect MANUAL UPDATE from 3dots on top.
11. This is will install the recovery 21s.
12. DONE
Note: you can not install 21s directly on custom recovery as it will give error 7
Can you 1. correct typos 2. move this to https://forum.xda-developers.com/le-2/how-to
Thank you
Thread cleaned up.
If you find some rule violation, please report it.
Also this is not a thread to bring up your personal vendettas. Add the annoying member to your ignore list and move on. No need to use foul language.
Consider this as the first and final warning. If this is repeated any further, there will be action taken against your accounts.
Hope I made myself very clear.
Regards
Vatsal,
Forum Moderator.
I didn't understand, is 26s version available for x522 because it is mentioned in the name of this thread?
zogu said:
I didn't understand, is 26s version available for x522 because it is mentioned in the name of this thread?
Click to expand...
Click to collapse
26s removed
as the provider stopped me to share it. correction in heading done.
Found link on Google's cache of https://forum.xda-developers.com/le-2/how-to/le-s3-20s-21sofficial-ota-lock-t3634079.
But this file update.zip was for s2_india, not for s2_na
Is newer version for usa market available?
zogu said:
Found link on Google's cache of https://forum.xda-developers.com/le-2/how-to/le-s3-20s-21sofficial-ota-lock-t3634079.
But this file update.zip was for s2_india, not for s2_na
Is newer version for usa market available?
Click to expand...
Click to collapse
As I already mentioned that I have tested these file on my x522(S3) before upload.
Nd x52x series means x520/522/526
Download 20s flash it you will receive 21s automatically
zogu said:
I didn't understand, is 26s version available for x522 because it is mentioned in the name of this thread?
Click to expand...
Click to collapse
Original 26s is available in Chinese only. You can flash it via twrp than root nd remove all Chinese app.
Chinese twrp ?
edan lkr said:
Chinese twrp ?
Click to expand...
Click to collapse
Yes.
Sooooo I have a slight problem.
I have TWRP and stock ROM. Sort of. Xtreme Addiction ROM, only one that would work and not give the error"This is an s2 not s2_na_Xxxx" so I Flashed that, and uninstalled root, now in TWRP it doesn't show my internal storage so I can't flash this ROM, and ask for a password. So I tried using the 3dot option from settings and it won't work either, it'll just boot to TWRP and nothing happens. I'm really not looking forward to deleting everything... AGAIN but I will if I have to.
Is there an update for the Le s3 x522 that can be installed though the phone update app? I am still running stock recovery and don't want to change it but it seems the OTA updates not working
Christhepenguin said:
Sooooo I have a slight problem.
I have TWRP and stock ROM. Sort of. Xtreme Addiction ROM, only one that would work and not give the error"This is an s2 not s2_na_Xxxx" so I Flashed that, and uninstalled root, now in TWRP it doesn't show my internal storage so I can't flash this ROM, and ask for a password. So I tried using the 3dot option from settings and it won't work either, it'll just boot to TWRP and nothing happens. I'm really not looking forward to deleting everything... AGAIN but I will if I have to.
Click to expand...
Click to collapse
I think we might be having the same problem...
My X527 came with 16s as the stock ROM.
Upgraded to 19s with TWRP which gives me the system update option as well as OTA (which says I'm running the latest version).
I want to update to 21s and use the system update method..
Phone starts to load the new update (renamed to "update.zip") progress bar at the bottom of the screen while all of this takes place.
Phone reboots into password screen for TWRP, swipe to continue, then select system reboot and once it's back up and running it is still on 19s...?
Did you get your update resolved?
gtd2000 said:
I think we might be having the same problem...
My X527 came with 16s as the stock ROM.
Upgraded to 19s with TWRP which gives me the system update option as well as OTA (which says I'm running the latest version).
I want to update to 21s and use the system update method..
Phone starts to load the new update (renamed to "update.zip") progress bar at the bottom of the screen while all of this takes place.
Phone reboots into password screen for TWRP, swipe to continue, then select system reboot and once it's back up and running it is still on 19s...?
Did you get your update resolved?
Click to expand...
Click to collapse
I did, I used this website. https://www.google.com/amp/s/forum....factory-image-5-8-020s-directly-t3527790/amp/
Downloaded Chinese TWRP from there. As well as that ROM, if you have the 21s update file, I'm sure you can get it working with that TWRP. Hopefully it works for you.
Christhepenguin said:
I did, I used this website. https://www.google.com/amp/s/forum....factory-image-5-8-020s-directly-t3527790/amp/
Downloaded Chinese TWRP from there. As well as that ROM, if you have the 21s update file, I'm sure you can get it working with that TWRP. Hopefully it works for you.
Click to expand...
Click to collapse
What worked for me was replacing TWRP with the factory recovery and I'm good to go.
There was talk of an official update (beyond 21s) in December but so for, no sign of that...
gtd2000 said:
What worked for me was replacing TWRP with the factory recovery and I'm good to go.
There was talk of an official update (beyond 21s) in December but so for, no sign of that...
Click to expand...
Click to collapse
Interesting, replacing stock Recovery didn't work for me when I did it, and yeah. It's most likely not coming soon due to financial issues LeEco has.
Christhepenguin said:
Interesting, replacing stock Recovery didn't work for me when I did it, and yeah. It's most likely not coming soon due to financial issues LeEco has.
Click to expand...
Click to collapse
I note that this says it's the ROM for the S3.
I'm using the X527 which is the S2 with the Snapdragon chip (now listed as X526 after installing 21s), did you perhaps flash the incorrect ROM?
I had continual problems upgrading from 19s with TWRP - it would go through the whole process and then reboot to 19s..
Even after the replacement of the stock recovery, the first ROM I downloaded (21s) was not accepted. Had to download another one for it to finally work.
Could be a bad download?
Contact
How did you contact leeco and get this. I need all future updates. My phone is rooted and I am unable to completely unroot it and get OTAs.
---------- Post added at 02:59 AM ---------- Previous post was at 02:52 AM ----------
rodogg88 said:
Is there an update for the Le s3 x522 that can be installed though the phone update app? I am still running stock recovery and don't want to change it but it seems the OTA updates not working
Click to expand...
Click to collapse
If you don't have TWRP or anything installed, it should work fine if you put the 20s update in the root folder (the folder with the android and download folders). Then just go to system update, press menu, press local update, go through prompts and it should update automatically. Then just repeat the process for the 21s update. If you have twrp installed, I'm pretty sure the chinese ydss version doesn't allow OTA installs. This update requires stock recovery installed because it updates through the recovery. You can find stock recovery images on google (search le s3 stock recovery and click skyneel) or, someone might have posted a recovery image on the le 2 forum. Plz reply if it doesn't work, it worked for me tho.
Is there any bugs? If yes please list. Thank you
does it work for le s3 X626 mtk?
if not, please guide me as I see that this forum support Le S3.
thanks.
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