Hi,
Hello to everybody, I am new on this forum.
I have a Leeco Max 2.
2 weeks ago I installed Twrp with success and I installed a first rom installed. Everything was working fine.
After few days, I got a loop restart and the first welcome picture of leeco change from english to chineese.. a virus ???
Now, If don't use it after 1 or 2 minutes, it restarts. If i put it in charge, it's work without loop !
I flashed 2 different rom, to see if i's solve the problem, but no. Before each flash I formated with twrp : the cache dalvik, system, cache, data.
But still the loop.
Did any one face the same symptoms ? Any ideas how to solve the problem ?
Thanks in advance for your proposals.
Heyyo, the change in boot screen logo from English to Chinese could be if you flashes any EUI ROM be if custom or not that is based on the Chinese versions and have a Chinese boot logo in the files. If you flash an English EUI ROM splash screen or EUI ROM it will return to English.
As for the boot looping? Hmm that's unfortunate. Can you please specify which ROMs you have tried?
ThE_MarD said:
Heyyo, the change in boot screen logo from English to Chinese could be if you flashes any EUI ROM be if custom or not that is based on the Chinese versions and have a Chinese boot logo in the files. If you flash an English EUI ROM splash screen or EUI ROM it will return to English.
As for the boo,t looping? Hmm that's unfortunate. Can you please specify which ROMs you have tried?
Click to expand...
Click to collapse
--
Hi The Mard,
Regarding the boot screen logo. it doens't change any more to english .. After 2 or 3 rom flashed. does it mean something ? may be not ..
The last rom I flashed is the PixelExperience_x2-8.1.0-20180218-1114-OFFICIAL.
rodolphediet said:
--
Hi The Mard,
Regarding the boot screen logo. it doens't change any more to english .. After 2 or 3 rom flashed. does it mean something ? may be not ..
The last rom I flashed is the PixelExperience_x2-8.1.0-20180218-1114-OFFICIAL.
Click to expand...
Click to collapse
---
Nobody to help me .. please I am really bad. Thank you
rodolphediet said:
---
Nobody to help me .. please I am really bad. Thank you
Click to expand...
Click to collapse
Have you flashed a modern firmware version on your device ?
Try going on TWRP and flash 26S or 466D modem (try one first and if that doesn't work try the other):
466D Modem
26S Modem
I've had a similar problem, a few days ago I woke up and noticed my phone was boot looping.
Ive since wiped the phone, with inbuilt recovery. I then flashed twrp via adb cmd, made a back up. Was working for two days, then today constantly crashing, so I flashed my recovery via twrp, now back to bootloop.
Mine started doing this a few days ago. I've used https://forum.xda-developers.com/showthread.php?t=3492949 to try to fix mine. It didn't help initially. After doing it a few times over the last few days I'm running fine. I don't know how long it will last. So far about six hours without a reboot. I did the above process, then flashed a stock 20s US rom via TWRP and then a Lineage rom. I did this whole process a few times. The last time, I ran the unbrick process two times in a row. Not sure if that's what did the trick or not. Good luck.
Sent from my LEX829 using Tapatalk
first flash cbg or cuoco rom to overwrite chinese bootloader (maybe better fastboot version). After, flash one of the lastest modem, maybe improve stability, than try to flash another custom rom (pixel revenge, official lineage, aosip, du...the best atm). If that does not solve the reboot issue, buy another battery.
My phone has an up time of 20 hours so far after the "process" I did. That's after having an up time of an hour or so for each step I took. So, almost a day in total without a random reboot.
Sent from my LEX829 using Tapatalk
4ish days later and it's doing it again. Tine to sell it for parts.
Sent from my Ascend Mate 2 using Tapatalk
Related
Hey y'all. I originally flashed Team Spain's revolution remix rom and it was working well. I thought I would give Madsurfer's rom a try. Loaded multiple different versions of TWRP (5.8 teamspain's, and TWRP 3.0.2-1, 3.0.2-0). I've wiped the whole thing on each and flashed the zip but continue to get stuck in the "LeEco" screen. It Vibrates then just reboots. Any help would be appreciated. @madsurfer1
thats strange my friend, because I've tryed it in various situations and I manage to get it working, can you please re-download the rom and see if it happens again?
I'm afraid that mega isnt a very good place to have my rom hosted, many people are complaining
Your phone setup is the same as mine twrp 3.0.20 and did full wipe
Next time, if you want a faster reply, please use my rom thread, I promise I'll be quicker there
Hi to everyone!
I have a problem to share because I hope anyone can help me to fix it.
My OnePlus 2 with the stock ROM of OxygenOS 3.1.0 (never unlocked bootloader or installed custom roms... always with the original system) has a problem: since 2 weeks he started rebooting randomly... it may happen from 1 up to 3 times a day (in my situation). These reboots are not caused by apps I think because a lot of them happens when the phone is with screen looked and it is in my poket or on the table (on charge and withoutcharge also, is indifferent). Sometimes happened also while using it (it could be a browsing session, a photo.... it's random!).
I also noticed that before the restart the phone freezes, expecially when its screen is turned off, you can't turn it on and all gestures or phisical key (also the fingerprint) doesn't work.
I noticed the first time that the phone rebooted exactly for the fingerprint sensor, because I tryed to unlock it and it said that after reboot I need to first insert the unlock sequence.
I tried (in this oreder):
- to make a cache and data wipe from recovery (with no result);
- to make an hard reset from the recory installed into the phone (with no result);
- to make another FULL wipe and reinstall the OxygenOS from the zip installer on the official download section of the oneplus website (with no result).
Now, I beg to all of you to help me if you have any suggestion or know a fix for this problem.
Thanks in advance to all people that will help me
Hi...
U will need to upgrade to the latest oxygen os 3.5.6/3.5.6 or flash a custom ROM like cm.
In order to do that u will need to unlock bootloader and install twrp and then flash zip.
Ensure u take a nandroid backup in twrp before flashing roms
Everything can be found on google. [emoji4]
Hope it solve the problem
Sent from my ONE A2005 using Tapatalk
But the phone worked well for months... why now there is this problem? And anyway there is no update by OTA and I don't want to unlock the bootloader for an update that I have to recive by official way...
claudio.94 said:
But the phone worked well for months... why now there is this problem? And anyway there is no update by OTA and I don't want to unlock the bootloader for an update that I have to recive by official way...
Click to expand...
Click to collapse
It's probably caused by a google app running in the background.
If u can get a logcat of the the device before reboot without root would have an idea.
Sent from my ONE A2005 using Tapatalk
How can I take a logcat? and anyway I don't know when the phone will reboot... and when I discover it is too late because like I said it freezes for 10-15 seconds and I can't make anything...
Well if u are looking for ota, check out this: https://forum.xda-developers.com/oneplus-2/general/hot-fix-3-5-6-oneplus-2-official-update-t3528911
since u don't want to unlock bootloader n stuff.
Sent from my ONE A2005 using Tapatalk
Oh thanks... but why I didn't recived it by OTA?
Well idk but I think it is released in some country or not quite official yet.
Tbh I'm using custom Roms so I never checked it.
As they say, it fixed random boots and use a VPN and select Germany or Canada to download the zip via ota or can manually flash in stock recovery.
I recommend the ota it's more safe.[emoji2]
Sent from my ONE A2005 using Tapatalk
Ok... I will try it
I have the resurrection 5.8.0 installed (30 Dec build) and my phone takes about 5 minutes to boot. Initially it is stuck in the MI logo for about 4 minutes before the animation starts. I have used several ROMS and kernals and they all seem to do the same thing. I never had this issue with MIUI. Once the phone has booted, the phone is totally fine however I would prefer to identify and fix the problem. Any suggestions? I have already done a complete wipe, and tried various verions of TWRP with no joy. Thanks
I suggest you to flash the latest version of MIUI latest china dev, then from fastboot flash twrp, then clean flash rom + kernel. It takes about 30 minutes if you know what you're doing.
So basically restore then start from scratch? That did cross my mind... I will give it a go. Thanks. I will report back here.
ginohabibi said:
So basically restore then start from scratch? That did cross my mind... I will give it a go. Thanks. I will report back here.
Click to expand...
Click to collapse
Hi if you find a fix for this problem please share it with me, I tried latest china dev rom, latest global dev rom and latest global stable rom with all versions the boot time goes to 4-5 minutes...
ufoshop said:
Hi if you find a fix for this problem please share it with me, I tried latest china dev rom, latest global dev rom and latest global stable rom with all versions the boot time goes to 4-5 minutes...
Click to expand...
Click to collapse
Try method in my signature.. it should work for you
khajiit said:
Try method in my signature.. it should work for you
Click to expand...
Click to collapse
Where do i find that method?
https://forum.xda-developers.com/redmi-note-3/how-to/kate-guide-install-lineage-os-locked-t3546154
Alright, im going to try that method and i will report my results here.
Followed all the steps within your guide, but that guide didnt work and has nothing to do with our slowboot issue.
Hardware related then
ginohabibi said:
I have the resurrection 5.8.0 installed (30 Dec build) and my phone takes about 5 minutes to boot. Initially it is stuck in the MI logo for about 4 minutes before the animation starts. I have used several ROMS and kernals and they all seem to do the same thing. I never had this issue with MIUI. Once the phone has booted, the phone is totally fine however I would prefer to identify and fix the problem. Any suggestions? I have already done a complete wipe, and tried various verions of TWRP with no joy. Thanks
Click to expand...
Click to collapse
Didnt you change recently some parts of the phone? Like display/baterry and so...?
i think dat guy replaced display module
same problem here, touchscreen cant initialize on boot
4-5mins to go... all rooms.
to solve/ n - use old Santosh kernel, mm - use neon kernel, lp - elementalx
on this cores phone starts on 20-40s
and about recovery - use twrp+ 3.0.2-2 by mr_root
paladzin said:
i think dat guy replaced display module
same problem here, touchscreen cant initialize on boot
4-5mins to go... all rooms.
to solve/ n - use old Santosh kernel, mm - use neon kernel, lp - elementalx
on this cores phone starts on 20-40s
and about recovery - use twrp+ 3.0.2-2 by mr_root
Click to expand...
Click to collapse
So you say there is no solution to run the official rom without waiting 4-5 mins on boot, I have the phone from fastcardtech and maybe is a refurbished unit because they have very low prices compared to other resellers...the phone came in sealed box...
Dwnld links plzz..
Hay anybody here ...is there any other kernal for andriold n ROMs...
paladzin said:
i think dat guy replaced display module
same problem here, touchscreen cant initialize on boot
4-5mins to go... all rooms.
to solve/ n - use old Santosh kernel, mm - use neon kernel, lp - elementalx
on this cores phone starts on 20-40s
and about recovery - use twrp+ 3.0.2-2 by mr_root
Click to expand...
Click to collapse
Mine to, it 2 time I had to replace screen. I'll give a test right now and report back.
Im not using the device anymore, but i think i had to replace the screen like 3-4 times, its very fragile, even a drop from small height makes it crack. Also without case its very slippy device, but none of that matters. From the 4 displays i used, which all have been touchscreen + lcd + the frame (as i dont like to glue the display, i pay 10 dollars more and its better) had that exact same problem, which is very long waiting for the device to boot. The custom kernel solved it, but another (probably better quality) display does solve it too.
Hello everyone,
i got a Redmi Note 3 pro for a friend some while ago, since i dont wanted to stick to MIUI, i just flashed ResurrectionRemix since this was the most used costum rom back then.
My friend now suddenly has the problem that his phone just bootloops all the time. So i tried upgrade the rom to a newer version but it just keept bootlooping.
I also already tried formating the data partition as well as the storage but nothing helped so far. I even tried a few different roms but no difference there either.
But the weired thing is that i found an really old full backup (1.5 years old, only system and data) of the rom he used before and when i flash that, it just works fine.
I really dont wanna go back to that old and buggy rom so is there something else i could do to fix this problem?
Have you tried flashing a newer firmware? IIRC there's a thread that includes links to all the past and latest firmwares for kenzo.
TomTheDragon87 said:
Hello everyone,
i got a Redmi Note 3 pro for a friend some while ago, since i dont wanted to stick to MIUI, i just flashed ResurrectionRemix since this was the most used costum rom back then.
My friend now suddenly has the problem that his phone just bootloops all the time. So i tried upgrade the rom to a newer version but it just keept bootlooping.
I also already tried formating the data partition as well as the storage but nothing helped so far. I even tried a few different roms but no difference there either.
But the weired thing is that i found an really old full backup (1.5 years old, only system and data) of the rom he used before and when i flash that, it just works fine.
I really dont wanna go back to that old and buggy rom so is there something else i could do to fix this problem?
Click to expand...
Click to collapse
If u unofficially unlocked bootloader
Then U need latest miui rom bootloader. First update to latest miui 10 fastboot rom using pc. then unlock and install twrp .
Then ur custom roms will boot.
If u have unlocked ur bootloader officially using miunlock tool. then just flash latest firmware which includes emmc. This will directly update ur bootloader. Then u can flash custom roms.
Hey everyone,
I am very new to the OP7TP, comming from an HTC U11 which is.. old and very different.
Anyhow on to my problem:
When I got my new device I decided to get rooted, and then chose to use reseruction rom.
Which was a pretty nice experience, but I also wanted to see what else was being released, and Havoc came along.
I flashed Havoc according to the instructions on telegram, using fastbootd..
But when I went to boot it just kept rebooting to Bootloader mode
I restored my device using MSM, and triedagain, with the same result
But now, for the real trouble: reseruction rom does the same!
When flashing it, it will just reboot to bootloader every time.
It seems I can't flash custom roms anymore?
The stock OOS rom seems to be fastbootd and MSM flashable and boots without issue.
Has anyone encountered this before? any advice on how to proceed?
I am using the European OP7TP HD1913 with latest stable OOS 10.0.9 HD01BA
Solution:
Well I do feel silly now..
I flashed Reseruction Remix using my Desktop
Flashed Havoc (and all other attempts) using my notebook
And even tho I installed, which I thought were the correct fastboot drivers, evidently they are not..
When I tried flashing Havoc using my desktop it worked instantly..
It was just fastboot.. no errors during flashing, wiping, erasing and such... but it did something wrong..
Giblet-dono said:
Hey everyone,
I am very new to the OP7TP, comming from an HTC U11 which is.. old and very different.
Anyhow on to my problem:
When I got my new device I decided to get rooted, and then chose to use reseruction rom.
Which was a pretty nice experience, but I also wanted to see what else was being released, and Havoc came along.
I flashed Havoc according to the instructions on telegram, using fastbootd..
But when I went to boot it just kept rebooting to Bootloader mode
I restored my device using MSM, and triedagain, with the same result
But now, for the real trouble: reseruction rom does the same!
When flashing it, it will just reboot to bootloader every time.
It seems I can't flash custom roms anymore?
The stock OOS rom seems to be fastbootd and MSM flashable and boots without issue.
Has anyone encountered this before? any advice on how to proceed?
I am using the European OP7TP HD1913 with latest stable OOS 10.0.9 HD01BA
Solution:
Well I do feel silly now..
I flashed Reseruction Remix using my Desktop
Flashed Havoc (and all other attempts) using my notebook
And even tho I installed, which I thought were the correct fastboot drivers, evidently they are not..
When I tried flashing Havoc using my desktop it worked instantly..
It was just fastboot.. no errors during flashing, wiping, erasing and such... but it did something wrong..
Click to expand...
Click to collapse
Everytime I flashed havok I had to wipe data after flashing the ROM when it was in boitloop I held all buttons. Then went to recovery and wiped data then it booted fine