Related
-------------------------------------------------------------------------------------------------INTRODUCTION------------------------------------------------------------------------------------------------
Hello. I got my new LeTv phone about six months ago. Model x600 of course. When I saw that I had to upload a system with Polish language, I took care of the BB72 system. All is ok, but I do not like the EUI overlay. I will now describe all the errors that I encountered with this phone and how to fix them :fingers-crossed:
·Invalid IMEI·
Invalid IMEI this is the worst thing that I could meet. With the problem, measure up to now. This is also related to the NVRam problem. This problem is removed by IMEI and does not read the card. The phone is useless, but it can be fixed. However, after each subsequent change of the system for a new one, we will have to do the same thing again.
How to FIX?
1. Download ToolHero app and install (Google play will recognize this as a virus)
/Link\ https://m.apkpure.com/toolhero/com.mobileuncle.toolhero
2. We start and go to the tab · IMEI · and · IMEI RESCUE ·
3. Click ·START RESCUE·
4. Reset phone
·Brick·
I will not be explaining what brick is because everyone knows it. However, I know how to fix it. There are several ways to do this
-1- Find firmware scatter
http://www.androidbrick.com/download/letv-x600-unbrick-rom-scatter-file-sp-flash-tool-mtk-drivers/
SpFlashTool
https://spflashtool.com
Instruction
https://youtu.be/hRRv_jDIwGk
This is for LeTv 1S, but we do exactly the same as it is shown with our files
·AOSP·
Aosp is my favorite system for this phone, but I had no idea why KernelAuditore and AccuBattery showed me the battery capacity of only 1000mAh. The battery has disappeared and you will not do anything about it
However, if it does not bother you, I give a link to it and to TWRP created by BB72
-AOSP-
https://www.google.pl/amp/s/forum.x...rom-letv-x600-ultimate-aosp-rom-t3217135/amp/
-TWRP-
https://mega.nz/#!ZsgXACoY!Wuf44tHaF57bx-23YbfFL-sfV2jQk38rvgjfo16Nd_A
·ROM from LeTv 1S·
One of the XDA users has provided us with 5 ROMs transferred from LeTv 1s. These are CM, AIPS, LIOS, RR, MAOS. Unfortunately, when I installed them, it was crashing just like the BB72
-FIX-
1. Go to TWRP
2. Go to MOUNT
3. UNMOUNT ALL
4. And now you can flash (I don't testing on BB72 rom)
/LINK ROM\ https://www.google.pl/amp/s/forum.x...l/rom-letv-x600-cm13-based-roms-t3589050/amp/
If I learn something more, I will definitely update this Post so that you can fix your mistakes. Report them in the comments and I will look for how to fix them
-FIX ERROR 7-
1. Download on your devices TWRP BB72 (POINT AOSP, WATCH UP)
2. Go to TWRP
3. Flash TWRP BB72
4. Restart recovery
5. Go to mount
6. Unmount all
7. Go to wipe
8. Wipe cache, devil, system and data
9. Flash system
Enjoy
·NVRam·
-FIX-
1. Root phone
·Flash supersu zip
https://www.google.pl/amp/s/forum.x...2016-09-01supersu-v2-78-release-t3452703/amp/
2. Download ES EXPLORER from Play Store
https://play.google.com/store/apps/details?id=com.estrongs.android.pop
3. Turn on ROOT EXPLORER
4. Go to "/"data"nvram"APCFG"APRDEB"
5. Download and replace old WIFI and WIFI_CUSTOM
https://forum.xda-developers.com/attachment.php?attachmentid=2707382&d=1398400409
6. Restart phone
Done
·XPosed·
1. Download xposed installer
https://xposed-installer.en.uptodown.com/android
2. Click install or update
3. Wait and done
!!!DON'T WORKING ON AOSP!!!
-No Fix Bug-
1. Bluetooth
2. MIUI Cellular data
3. IR app
Error 7
I got this error with all the roms ERROR 7 with all https://forum.xda-developers.com/android/general/rom-letv-x600-cm13-based-roms-t3589050
- I need mount because I edit the scipt....?
Thanks
Nexu4K said:
-----------------------INTRODUCTION---------------------------
Hello. I got my new LeTv phone about six months ago. Model x600 of course. When I saw that I had to upload a system with Polish language, I took care of the BB72 system. All is ok, but I do not like the EUI overlay. I will now describe all the errors that I encountered with this phone and how to fix them :fingers-crossed:
·Invalid IMEI·
Invalid IMEI this is the worst thing that I could meet. With the problem, measure up to now. This is also related to the NVRam problem. This problem is removed by IMEI and does not read the card. The phone is useless, but it can be fixed. However, after each subsequent change of the system for a new one, we will have to do the same thing again.
How to FIX?
1. Download ToolHero app and install (Google play will recognize this as a virus)
/Link\ https://m.apkpure.com/toolhero/com.mobileuncle.toolhero
2. We start and go to the tab · IMEI · and · IMEI RESCUE ·
3. Click ·START RESCUE·
4. Reset phone
·Brick·
I will not be explaining what brick is because everyone knows it. However, I know how to fix it. There are several ways to do this
-1- Find firmware scatter
http://www.androidbrick.com/download/letv-x600-unbrick-rom-scatter-file-sp-flash-tool-mtk-drivers/
SpFlashTool
https://spflashtool.com
Instruction
https://youtu.be/hRRv_jDIwGk
This is for LeTv 1S, but we do exactly the same as it is shown with our files
·AOSP·
Aosp is my favorite system for this phone, but I had no idea why KernelAuditore and AccuBattery showed me the battery capacity of only 1000mAh. The battery has disappeared and you will not do anything about it
However, if it does not bother you, I give a link to it and to TWRP created by BB72
-AOSP-
https://www.google.pl/amp/s/forum.x...rom-letv-x600-ultimate-aosp-rom-t3217135/amp/
-TWRP-
https://mega.nz/#!ZsgXACoY!Wuf44tHaF57bx-23YbfFL-sfV2jQk38rvgjfo16Nd_A
·ROM from LeTv 1S·
One of the XDA users has provided us with 4 ROMs transferred from LeTv 1s. These are CM, AIPS, LIOS, RR, MAOS. Unfortunately, when I installed them, it was crashing just like the BB72
-FIX-
1. Go to TWRP
2. Select MOUNT
3. UNMOUNT SYSTEM
4. And now you can flash (I don't testing on BB72 rom)
/LINK ROM\ https://www.google.pl/amp/s/forum.x...l/rom-letv-x600-cm13-based-roms-t3589050/amp/
If I learn something more, I will definitely update this Post so that you can fix your mistakes. Report them in the comments and I will look for how to fix them
-No Fix Bug-
1. Bluetooth
2. MIUI Cellular data
3. IR app
Click to expand...
Click to collapse
Exactly the same problem I had with my LeTv. Today I fixed it and I am flying on LineageOS. I would recommend. However, TWRP can also be used. I recommend you to upload this TWRP what I have. I gave them in point AOSP.
1. Download TWRP BB72 on your phone
2. Go to recovery
3. Flash TWRP BB72
4. Restart Revovery
5. Go to Mount
6. Unmount all
7. Clear system, data, cache, devile cache
8. Flash rom
Good Luck (first boot is long)
It's really nice to see something fresh on xda in 2018 for our beloved LeTV X600!
Many thanks for this thread, Nexu4K, and for me especially the nvram fix pointer. It solved my otherwise lingering problem with that fake nvram WiFi entry.
In the meantime, my own daily driver for a while now has been the LineageOS 13 ROM. Other than the "Double-tap-to-wake-screen" feature not working on it, everything else I've tried works, and the ROM for me is smooth as silk.
My wish for this device, World, is to have a smooth LineageOS 14 ROM and beyond or similar on it already...
........
P34c3
.....
...
duwdu said:
RE:
Click to expand...
Click to collapse
Thank you for such a nice comment. I noticed that people bypass LeTv x600 so I decided to do something that will help everyone in one thread. On the other hand, on the double tap, I do not know what to do because it does not work at all. Roms do not count AOSP have been transferred from LeTv 1s and that option works there. Apparently the LeTv x600 does not have AMOLED screen allowing such tricks because no applications even support it. I SEARCH
In the options I also found an google OEM blockade known as FRP. However, I do not know if it works exactly, / and I do not want to lose a phone right now so I leave it to check
Nice. I will need to try this out. Any suggestion on how to root? I looked at some threads but all the links are dead.banyone has new links?
You don't need to do all this. Simply put the phone to default situation with stock recovery and stock rom formatting all partition different from system
Hi guys... Can anyone help me
My phone does not switch on anymore
I wanted a clean install so i flashed this mod 28S in my X600
Should be official one, after having a not official one. BB72
1523514973_FULL_X600_X600-CN-OP-ABXCNOP5902803181S-5.9.0
After installation done successfully.
with TWRP 3.0 at the end of the page was
Wipe cache e dalvik (what i pressed)
i went back then
Reboot
System
and was last time i saw my phone switch on
It switched off and didn't awake anymore
Neither in Recovery mode.
Nothing
If i charge it, the charging light gets on
It had 52% batter at the end of installation
the computer detects a device but not the phone or memory. just the sound of something connecte.
Can someone help me
Thanks
Did you solve your problem? You may need to flash rom with so flash tool.
Hello,
I've bricked my X600 (32 GB) by flashing unbrick ROM from
http://www.androidbrick.com/download/letv-x600-unbrick-rom-scatter-file-sp-flash-tool-mtk-drivers/
Now phone can only be flashed with SP Flash Tool. But when I flash with the unbrick ROM at above, nothing will be changed.
I also have another X600 32GB version fully working. If I backup all partitions of second X600's SD card and restore them bricked X600 with SP Flash Tool, can I unbrick the bricked X600?
nvm
Hello fairly new here, I found a post relating to Android sensors breaking during the upgrade to Android 10 and I also have all of my sensors broken currently.
A post on the Pixel 3 forum has the solution: https://forum.xda-developers.com/pixel-3-xl/how-to/android-10-sensors-bug-t3964904
Does anyone have working sensors that would be willing to provide their persist.img for me to dd and fix my sensors?
If there are any other solutions I'd appreciate it!
jkent900 said:
Hello fairly new here, I found a post relating to Android sensors breaking during the upgrade to Android 10 and I also have all of my sensors broken currently.
A post on the Pixel 3 forum has the solution: https://forum.xda-developers.com/pixel-3-xl/how-to/android-10-sensors-bug-t3964904
Does anyone have working sensors that would be willing to provide their persist.img for me to dd and fix my sensors?
If there are any other solutions I'd appreciate it!
Click to expand...
Click to collapse
Are you talking about broken sensors on the 7/Pro?
TheKnux said:
Are you talking about broken sensors on the 7/Pro?
Click to expand...
Click to collapse
Correct. I was having issues with broken sensors.
I had saved my original boot/EFS/modem files in TWRP. Restoring them also restored my sensors. Caution as it also made it so my sim would not connect so I went back and did the unbrick/edl msm tool and now everything is back up and working!
if your sensors are broken after android 10 it has nothing to do with persist partition
the persist partition is never written, so if its broken its a problem with android 10 not reading persist properly.
wait for the fix instead of messing with partitions you cant restore if you break it.
jkent900 said:
Correct. I was having issues with broken sensors.
I had saved my original boot/EFS/modem files in TWRP. Restoring them also restored my sensors. Caution as it also made it so my sim would not connect so I went back and did the unbrick/edl msm tool and now everything is back up and working!
Click to expand...
Click to collapse
I had a similar problem with broken sensors when I tried updating (I rolled back to Pie for now)
That thread is in regards to TWRP saving logs to /persist causing the tiny partition to fill.
I would recommend using a terminal emulation app with the 'df' command and look for persist in the results. My persist partition is only 15% utilised and doesn't contain any twrps files or a cache folder (as the Pixel guys are seeing), so I presume that our problem is something different.
If you're adamant about trying to flash it anyway, you can find the images and commands here...but I wouldn't recommend it if you don't absolutely know what you're doing:
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
(fyi... if you use the flash-all.bat included in that thread, it will wipe your storage if you don't edit out the -w flag)
Yeah I had used that tool to rollback to pie. I think that might have been where my problems started.
Using the msm tool I believe my phone is completely back to stock and currently just have twrp/magisk and going to wait until either the official Android 10 or maybe the next beta. Dark mode is the biggest feature I'm looking forward to.
Hmm I have a bit of a similar problem but not in this scenario.
Had Oxygen OS 10, all was good.
Flashed OOS 9 (prerequisite for Havoc OS 2.9 based on Android Pie).
Then I discovered no sensor works anymore in Havoc OS (also with sensor test app).
> adb shell
> su -
> mount | grep persist --> found sda2
> df -kh ---> have just 15% used on it
I flashed a persist just out of curiosity if it brings any benefit (files are the same after).
Sensors still do not work.
Is using MSM tool the only way to bring my sensors back?
I'm a bit reluctant to have to restore all my data again and lose half a day but if it's the only way...then I will proceed.
Hi all, I was freaking around on the OnePlus 7 Pro's forum, when I read this guide:
https://forum.xda-developers.com/showpost.php?p=79603954&postcount=4
Anyone tried?
Is anyone interested to do some tests?
I'ts possible to backup /data partition, enable F2FS and restore /data backup then?
to avoid losing all data and configure the phone from scratch.
Any ideas?
Thanks in the advance!
P.S.: Kirisakura Kernel works perfectly on my OnePlus 7, give it a try! For your information, I'm running OOS 10 beta 3.
Hello I'm also open beta 3 I passed in f2fs without problem I noticed a small difference but works without problem with the kernel stock.
I flashed the Kirisakura kernel all work fine.
I have now test all. I have the Persist image over the, Orange Fox recovery and also with code over the TWRP recovery. I also test flash over fastboot and edl mode. (for edl mode my account don't have the premission to flash.....)
Only the gyro and accelerated was fixed by flash the persist image over the recovery.
So i have a broken promoxity and Brigthness Sensor.
Is there a way that ones can give me a Orange Fox backup of his Persist image?
My device ist the 3/32 Gigabyte Version when it is important.
Thanks for help :fingers-crossed:
No Man can help me?
Why don't you try testing if your proximity sensor is working or not with cpuz
I have tested and they don't work. On CPUZ not listed.
hmm even if it's broken it should still show in Cpuz.
Maybe try testing with other ROM
You have the same device? When yes can you backup for me the persist image? I have flash more than one time the original rom over miui flash tool
I have attached the backup. One more thing when I checked your attached image, I see that your accelerometer is of other name (or brand) and mine is BMI... Something. I request you to make backup of your current persist and I also want to say maybe your phone might not boot (maybe, I hope not). It's risky but give it a try. Good Luck!
A big thanks for it. The sensor will work after your backup. But than the other sensor goes down. Gyroskope and Accelerometer :silly:
Witch Version of redmi note 6 pro you have? My is 3/32 Gigabyte Version.
After flash the latest persist image from us all other works and promoxity goes down and light :silly:
I will test for flash the persist over twrp with the flash code after your backup. Hope this work or i must search for a user like you with right Version.
For now very big thanks now i know it is not damaged and i can awake the sensors.
My new list after your backup flash
Here is a list of my Sensor. When anyone have the same is it possible to give me a backup of his persist image over Orange Fox recovery?
Promoxity Sensor:
stk3x1x alsprx
Sensortek
Brightness:
stk3x1x alsprx
Sensortek
Gyroscope:
ICM20607
IvenSense
Magnetometer:
AK09918
AKM
Accelerometer:
ICM20607
IvenSense
Mine is 4/64 version but I think it should have been compatible with yours. Maybe different revision or something
---------- Post added at 08:34 AM ---------- Previous post was at 07:48 AM ----------
Anyways bro
It seems that flash tool ignors flashing persist so
Try this method take your persist.img if you have from fastboot ROM file and do as below:
1) Start the twrp with Vol + and power button
2) Advanced -> Terminal.
3) Execute these lines.
a) simg2img /sdcard/persist.img /sdcard/persist_EXT4.img - Converts de image from sparse to raw.
b) dd if=/sdcard/persist_EXT4.img of=/dev/block/bootdevice/by-name/persist - Flashes the persist block with new persist image.
4) Reboot to system.
Credits - 4pda
That i have test. Simg2img don't work. Direkt over "dd if=" flash works also like Flash over Orange Fox. But the same result that the both sensor not work.
A big thanks for your answer and help.
Do tell us if you find any solution. It will help us all
I will make it. The easy way when other with same sensor give me a backup like you.
Hey bro I found this video on YouTube I recommend you to watch this
Thanks. This solution i have also tried no work for me.
I have now fix the issue
I have make a guide to fix it :
https://forum.xda-developers.com/redmi-note-6-pro/how-to/guide-repair-persist-image-sensor-crash-t4082147
HumanBoy23 said:
I have attached the backup. One more thing when I checked your attached image, I see that your accelerometer is of other name (or brand) and mine is BMI... Something. I request you to make backup of your current persist and I also want to say maybe your phone might not boot (maybe, I hope not). It's risky but give it a try. Good Luck!
Click to expand...
Click to collapse
Hi Bro i would like to talk about this personally, i have used your backup file for recovery some curropted file in my device actually it did worked well, but there is a problem which is solved by you only.
pls help me in this......!
vamsimec14 said:
Hi Bro i would like to talk about this personally, i have used your backup file for recovery some curropted file in my device actually it did worked well, but there is a problem which is solved by you only.
pls help me in this......!
Click to expand...
Click to collapse
What you want to do?
Hello.
I have a question. At this point, I have xiaomi.eu stable with miui 12 installed and want to install the stock system (version miui 11.0.6.0) and in MiFlash there is an error: Antirollback is enabled or similar. I have bootloader unlocked. Asking how to get back to stock miui?
i had this problem and the "weird" solution i googled worked fro me...
put the folder you extracted from .tgz file in the desktop and name it a short word without spaces then select that folder from MiFlash then refresh and finally flash