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.
Related
This is a MIUI GB 2.3.xx rom ported from stock ZCPK9(China version) rom with miui patchrom.
---FLASH AT YOUR OWN RISK---
I'm now busy preparing for college entrance exam so I won't (perhaps) continue develop before I get into college
Not working:
GPS(Don't know why)
Not perfect:
Theme
DownloadProviderUI
SideKick
ClockPackage
Default language is Chinese.
App2SD(Cause reboot every time when you switch an App between SD and internal memory but actually it has operated successfully)
Ugly statusbar transparent.
Not proted now(All using stock one):
MIUI Settings
MIUI Camera
MIUI SoundRecorder
MIUI SuperUser
MIUI FileManager
MIUI Browser
MIUI Gallery3D
(And some other MIUI apps)
Features:
All MIUI features except that mentioned above (plus that I forgot and not find).
GUI installer by Aroma.
Optional Ad-hoc patch, Gapps, no keyboard light patch, USA keyboard patch.
Something wonderful:
Press home at lock screen to turn on torch.
Press home + back at same time to take screenshot.
Press menu + volum up to turn background light max(temporary).
Thanks to:
Myself , MIUI team and friends at XDA and Sdapk.
How to install:
1. Make sure you have rj's or Entropy512's installed. This rom does not contain kernel.
2. Download rom and place in your sdcard.
3. Reboot into recovery.
4. Wipe /data as well as anything else if you are first install this rom.IMPORTANT!
5. Choose install zip and this will start Aroma Installer.
6. Choose any patch you like in Aroma Installer and finish install it.
7. You will reboot automatically.
8. Be patient while first boot up.
9. Congratulations!
Screenshots:
Change log:
Code:
MIUI.2.3.xx.Noisyfox.01b
Fixed FC when headset plug in
Add USA keyboard patch
MIUI.2.3.xx.Noisyfox.01a
Fixed Settings Fail After Wipe /data
MIUI.2.3.xx.Noisyfox.01
Initial Release
Download:
https://github.com/Noisyfox/patchrom_GalaxyPlayer5.0/downloads
Develop:
If you are interested in this project, you can get fully source code from here:
https://github.com/Noisyfox/patchrom_GalaxyPlayer5.0
Hey how do we change it back to English in this ROM? And what do you mean by "Theme" is not working perfect? It is working partly or are there any bugs!
Thanks
Rom is perfect for me , but slow .
I have INTL device , which kernel is better for me Rumirand's or your patched kernel?
anil_kilic said:
Rom is perfect for me , but slow .
I have INTL device , which kernel is better for me Rumirand's or your patched kernel?
Click to expand...
Click to collapse
rj's is better.
pmdisawesome said:
Hey how do we change it back to English in this ROM? And what do you mean by "Theme" is not working perfect? It is working partly or are there any bugs!
Thanks
Click to expand...
Click to collapse
It works partly.
This is sweet, good job!!
I followed instructions to the letter. Seemed to flash fine but it is now sitting at the black Samsung screen screen for about 20 minutes. How long has it taken for 1st boot? Tried re-flashing, clearing cache, etc.
change your kernel to rj's kernel and flash again.
rj's kernel says it is for International SGP not US. My SGP is US so I am not sure if this kernel will work.
tsg2513 said:
rj's kernel says it is for International SGP not US. My SGP is US so I am not sure if this kernel will work.
Click to expand...
Click to collapse
Dont install . rj's kernel is for only INTL devices . Sorry i think your device is INTL and replied.
could you make a port for the 4 inch sgp?
I have the same problem as tsg2513, it sits at the Samsung logo and does nothing. I have a USA SGP5.0 and I flashed entropy's kernel right before I flashed the MIUI.
mrjaredbeta said:
I have the same problem as tsg2513, it sits at the Samsung logo and does nothing. I have a USA SGP5.0 and I flashed entropy's kernel right before I flashed the MIUI.
Click to expand...
Click to collapse
figured it out. i have a USA device as well and had the same issue. It was also strange as to why the flashing process only took like 5 seconds....
i flashed rj's kernel (so my buttons stopped working) then i restarted recovery just so the changes get applied. then i proceeded to flash miui. just make sure in the install options you selection USA keyboard patch and the install process should take much longer (that means its working) and bam.
EDIT: ok so the buttons light up but they still don't work. after booting to miui and sat at the homescreen for a minute or two, reboot and flash entropy's kernel.
raishiro said:
figured it out. i have a USA device as well and had the same issue. It was also strange as to why the flashing process only took like 5 seconds....
i flashed rj's kernel (so my buttons stopped working) then i restarted recovery just so the changes get applied. then i proceeded to flash miui. just make sure in the install options you selection USA keyboard patch and the install process should take much longer (that means its working) and bam.
EDIT: ok so the buttons light up but they still don't work. after booting to miui and sat at the homescreen for a minute or two, reboot and flash entropy's kernel.
Click to expand...
Click to collapse
Are you saying that after you re-flashed entropy's kernel the buttons work? Also, have you checked to see if the GPS works?
i flashed entropy's kernel after miui successfully boot up in order to get my buttons to work again, so yes
raishiro said:
i flashed entropy's kernel after miui successfully boot up in order to get my buttons to work again, so yes
Click to expand...
Click to collapse
Great! Can you please check if GPS works?
Google Maps works, just cant get a lock on Navigation. also, just discovered that the launcher restarts whenever you try to turn on usb storage with your cable plugged in...preventing you from accessing your files on your computer
raishiro said:
Google Maps works, just cant get a lock on Navigation. also, just discovered that the launcher restarts whenever you try to turn on usb storage with your cable plugged in...preventing you from accessing your files on your computer
Click to expand...
Click to collapse
Yeah, I just flashed it a little while ago. Everything looks really good expect for a few small problems (as you mention) which I can live with but I really need the GPS to work to consider this my dailer driver. Here's to hoping someone can get it fixed.
tsg2513 said:
Yeah, I just flashed it a little while ago. Everything looks really good expect for a few small problems (as you mention) which I can live with but I really need the GPS to work to consider this my dailer driver. Here's to hoping someone can get it fixed.
Click to expand...
Click to collapse
Anyone know how to get the GPS working?
So after a couple of hours searching the web, it may be that the GPS problem is inherent in MIUI 2.3.
Hello XDA! I have been a keen follower of this forum for long, but this is my first post, 'cause well... this is the first time I pretty stuck at something.
I have a Xperia Mini Pro (SK17i) and I have been using it for quite a while, around 2 years I presume. I have rooted and unlocked the bootloader by the end of the first year, and have been trying out several custom roms, until stopping at CM10.1 of LegacyXperia. (the amazing creation of Mike for our 2011-line of devices!) However, as of a month back, my touchscreen kinda broke - it wouldn't respond along with the capacitive buttons. I tried the methods mentioned in the general section, but no avail - it simply wouldn't work at all. There's a thin small strip that appears around the screen during pulling out the hardware keyboard, and I guess that somewhat suggests that the touchscreen is invalid by hardware means.
However, that's merely a background to the problem I'm facing. Recently, after the launch of CM11, I thought of giving it a swing, seeing how I have been an avid-fan of the pure look of CM. I tried flashing the kernel using flashtool and start the phone, but the only thing that takes place is just a vibration and a black screen. The screen remains black for like ever, until I pull out the battery. I tried flashing the kernel thrice, and the same problem persisted all through. I reverted back to the stock ICS then and it worked like a charm, and the same goes for FXP CM10 and the last CM10.1 I used... there's no problem whatsoever, save for the broken touchscreen.
Any suggestion one might give about my problem? Thanks a ton for reading out everything!
psychoticdemon said:
Hello XDA! I have been a keen follower of this forum for long, but this is my first post, 'cause well... this is the first time I pretty stuck at something.
I have a Xperia Mini Pro (SK17i) and I have been using it for quite a while, around 2 years I presume. I have rooted and unlocked the bootloader by the end of the first year, and have been trying out several custom roms, until stopping at CM10.1 of LegacyXperia. (the amazing creation of Mike for our 2011-line of devices!) However, as of a month back, my touchscreen kinda broke - it wouldn't respond along with the capacitive buttons. I tried the methods mentioned in the general section, but no avail - it simply wouldn't work at all. There's a thin small strip that appears around the screen during pulling out the hardware keyboard, and I guess that somewhat suggests that the touchscreen is invalid by hardware means.
However, that's merely a background to the problem I'm facing. Recently, after the launch of CM11, I thought of giving it a swing, seeing how I have been an avid-fan of the pure look of CM. I tried flashing the kernel using flashtool and start the phone, but the only thing that takes place is just a vibration and a black screen. The screen remains black for like ever, until I pull out the battery. I tried flashing the kernel thrice, and the same problem persisted all through. I reverted back to the stock ICS then and it worked like a charm, and the same goes for FXP CM10 and the last CM10.1 I used... there's no problem whatsoever, save for the broken touchscreen.
Any suggestion one might give about my problem? Thanks a ton for reading out everything!
Click to expand...
Click to collapse
The kernel is incompatible with your phone.
Care to explain a little more? I have flashed the kernel provided within the rom zip itself (as suggested time and time again), and I have double checked its for the correct device - i.e. mango.
psychoticdemon said:
Care to explain a little more? I have flashed the kernel provided within the rom zip itself (as suggested time and time again), and I have double checked its for the correct device - i.e. mango.
Click to expand...
Click to collapse
kernel is for mango??unofficial port right...can you provide the rom link once.....??
http://forum.xda-developers.com/showthread.php?t=2545367
This is the one - LegacyXperia CM11 by mikeioannina.
psychoticdemon said:
http://forum.xda-developers.com/showthread.php?t=2545367
This is the one - LegacyXperia CM11 by mikeioannina.
Click to expand...
Click to collapse
yeah i though so...was going through the post...did you try this..
1.1 (optional): If the device is not booting, reboot to bootloader again and run:
fastboot erase system
fastboot erase userdata
As the rom requires a new partition table and maybe system and userdata is conflicting...
Dark Wraith said:
yeah i though so...was going through the post...did you try this..
1.1 (optional): If the device is not booting, reboot to bootloader again and run:
fastboot erase system
fastboot erase userdata
As the rom requires a new partition table and maybe system and userdata is conflicting...
Click to expand...
Click to collapse
Thanks a lot for pointing it out, mate! Usually the roms I tried didn't require such a thing, but this might be it. I'll provide feedback if the steps works.
I tried the steps advised, but the problem seems to still persist to some extent. The capacitive lights are lit and the screen is lit as well (as could be understood from the viewing angles - it's brighter and powered up). Nothing seems to appear on the screen though - no boot logo or anything - and trying to enter recovery fails as well (through power + vol up shortcut). I have tried it twice already, kept the phone switched on for five minutes or so, but no avail. I had to pull battery out every time to shut down the device. Anyone have any other advice?
psychoticdemon said:
I tried the steps advised, but the problem seems to still persist to some extent. The capacitive lights are lit and the screen is lit as well (as could be understood from the viewing angles - it's brighter and powered up). Nothing seems to appear on the screen though - no boot logo or anything - and trying to enter recovery fails as well (through power + vol up shortcut). I have tried it twice already, kept the phone switched on for five minutes or so, but no avail. I had to pull battery out every time to shut down the device. Anyone have any other advice?
Click to expand...
Click to collapse
try this.....Have the stock ICS 4.1.B.0.587 full ftf flashed (doesn't matter if you have flashed it in the past or if you flash it before installing cm11.0, it will work both ways)
then see if device powers up...
once it does...go for the next steps........
Dark Wraith said:
try this.....Have the stock ICS 4.1.B.0.587 full ftf flashed (doesn't matter if you have flashed it in the past or if you flash it before installing cm11.0, it will work both ways)
then see if device powers up...
once it does...go for the next steps........
Click to expand...
Click to collapse
Thanks for the quick response, but I tried that too. Unfortunately, the problem still seems to persist.
psychoticdemon said:
Thanks for the quick response, but I tried that too. Unfortunately, the problem still seems to persist.
Click to expand...
Click to collapse
I wonder if its a hardware related issue...you said in your op that there is some problem with your screen and capacitive buttons...Got any friend with sk17i???? I had one before it was stolen......Every other rom apart from CM11 is working right..Is there any other Kitkat based ROM for sk17i..if its there you may try that out and see if you have the same problem...otherwise..wait for a kitkat based rom to come up and try before flashing this...Try one more time from scratch...flash stock ICS 4.1.B.0.587 full ftf..reboot....once its working...fastboot flash boot.img...then better to fastboot erase system and fastboot erase userdata and then before it boots enter recovery and wipe data cache everything...flash update.zip..wipe cache,data,dalvik cache again...and boot..if it doesnt boot up then there is no option but to wait..
Dark Wraith said:
I wonder if its a hardware related issue...you said in your op that there is some problem with your screen and capacitive buttons...Got any friend with sk17i???? I had one before it was stolen......Every other rom apart from CM11 is working right..Is there any other Kitkat based ROM for sk17i..if its there you may try that out and see if you have the same problem...otherwise..wait for a kitkat based rom to come up and try before flashing this...Try one more time from scratch...flash stock ICS 4.1.B.0.587 full ftf..reboot....once its working...fastboot flash boot.img...then better to fastboot erase system and fastboot erase userdata and then before it boots enter recovery and wipe data cache everything...flash update.zip..wipe cache,data,dalvik cache again...and boot..if it doesnt boot up then there is no option but to wait..
Click to expand...
Click to collapse
Exactly. That's the whole reason why I posed this thread - to know if it was a hardware related problem right off the bat, or there was really something that I was doing wrong. I'll rather leave this one open to see if anyone have any other opinion about the matter. I really want to see what Kitkat looks like seeing how it's not available for my current device. (Micromax A210)
Also, about trying out other 4.4 roms... I guess I can try that route. But seeing how this problem is induced by the kernel itself and every other rom out there is mainly based off the LX 3.4 kernel, I doubt if that will work. I'll try the option anyway and see if it works.
psychoticdemon said:
Exactly. That's the whole reason why I posed this thread - to know if it was a hardware related problem right off the bat, or there was really something that I was doing wrong. I'll rather leave this one open to see if anyone have any other opinion about the matter. I really want to see what Kitkat looks like seeing how it's not available for my current device. (Micromax A210)
Also, about trying out other 4.4 roms... I guess I can try that route. But seeing how this problem is induced by the kernel itself and every other rom out there is mainly based off the LX 3.4 kernel, I doubt if that will work. I'll try the option anyway and see if it works.
Click to expand...
Click to collapse
Yeah.....waiting for other roms wont work.....cz they are all based on 3.4.x kernel.......Umm can you check your baseband after flashing full ftf...baseband should be : 8x55A-AAABQOAZM-203028G-77..every other rom based on 3.4.x kernel works right???...btw if you want to see how it looks just download a kitkat launcher from playstore....
Yes, the baseband is .77 after flashing the ICS 4.1.0.B.587. I used 3.4.x kernel with CM10.1, but never really tried CM10.2 to that extent. Maybe I'll try downloading that and see if it works... or even the EOL CM10.1.
And sure, the launcher would give in the feel, but I want the full experience possible really.
Hi, I'm sorry for my bad English, I'm with 1 Moto And first generation that after being looped I was able to unblock and install TWP, and put the Lolipop Rom 5.1, installed without errors, but when I started the android, I set it up and then when I restarted it Device it enters that white screen that appears that the bootloader was unlocked and falls straight into TWRP, does not start Android at all, could they help me? thanks
Nikakz said:
Hi, I'm sorry for my bad English, I'm with 1 Moto And first generation that after being looped I was able to unblock and install TWP, and put the Lolipop Rom 5.1, installed without errors, but when I started the android, I set it up and then when I restarted it Device it enters that white screen that appears that the bootloader was unlocked and falls straight into TWRP, does not start Android at all, could they help me? thanks
Click to expand...
Click to collapse
1. Flash stock lollipop
2. Reboot bootloader
3. Volume up select, Normal powerup
Rajendran Rasa said:
1. Flash stock lollipop
2. Reboot bootloader
3. Volume up select, Normal powerup
Click to expand...
Click to collapse
Guy
Ok, thanks I'll try
Nikakz said:
Guy
Ok, thanks I'll try
Click to expand...
Click to collapse
I tried, accept the installation of Rom, but it is on the screen of the logo starting and it does not leave, I do not know what to do to work.
Nikakz said:
I tried, accept the installation of Rom, but it is on the screen of the logo starting and it does not leave, I do not know what to do to work.
Click to expand...
Click to collapse
Sometimes a new flash takes nearly half an hour to boot. I faced once.. Did u wait for sometime?
vyshak.sk said:
Sometimes a new flash takes nearly half an hour to boot. I faced once.. Did u wait for sometime?
Click to expand...
Click to collapse
Yes, I waited more than 24 hours and nothing and no other flash I tried installs only this one and does not leave the startup logo, very strange this device, I needed a solution.
Nikakz said:
Yes, I waited more than 24 hours and nothing and no other flash I tried installs only this one and does not leave the startup logo, very strange this device, I needed a solution.
Click to expand...
Click to collapse
Flash latest twrp 3.x. You can find it from official lineage os thread under original development section.
Then flash any stable marshmallow custom rom.
_sushan_ said:
Flash latest twrp 3.x. You can find it from official lineage os thread under original development section.
Then flash any stable marshmallow custom rom.
Click to expand...
Click to collapse
Hello everyone, I put a CM13 and she accepted the installation and updated the TWRP also, I put the gaps, I did everything, Android starts, but continues with the problem of falling straight into recovery and going to TWRP and something else when I can do it Start it is not with network signal, recohece the chip, but does not give network signal. I do not know what to do with this device anymore. Could you try to install lolipop on it? Which version could I put? Would it be because of being in 6? I installed this rom cm-13.0-20161022-NIGHTLY-condor only installed it right. thanks
Nikakz said:
Hello everyone, I put a CM13 and she accepted the installation and updated the TWRP also, I put the gaps, I did everything, Android starts, but continues with the problem of falling straight into recovery and going to TWRP and something else when I can do it Start it is not with network signal, recohece the chip, but does not give network signal. I do not know what to do with this device anymore. Could you try to install lolipop on it? Which version could I put? Would it be because of being in 6? I installed this rom cm-13.0-20161022-NIGHTLY-condor only installed it right. thanks
Click to expand...
Click to collapse
Looks like you are using a very old cm 13 build.
Try this one. https://www.androidfilehost.com/?fid=385035244224413102
This is cm 13 snapshot build by @Andersonmends.
Clean install is recommended ie wipe cache data internal and then flash this with pico gapps
Nikakz said:
Hello everyone, I put a CM13 and she accepted the installation and updated the TWRP also, I put the gaps, I did everything, Android starts, but continues with the problem of falling straight into recovery and going to TWRP and something else when I can do it Start it is not with network signal, recohece the chip, but does not give network signal. I do not know what to do with this device anymore. Could you try to install lolipop on it? Which version could I put? Would it be because of being in 6? I installed this rom cm-13.0-20161022-NIGHTLY-condor only installed it right. thanks
Click to expand...
Click to collapse
You flashed latest twrp inside old twrp recovery itself?right?
Rajendran Rasa said:
You flashed latest twrp inside old twrp recovery itself?right?
Click to expand...
Click to collapse
Yes. Out the problem now with the network signal that is not picking up, it recognizes the chip, but it is without signal.
Nikakz said:
Yes. Out the problem now with the network signal that is not picking up, it recognizes the chip, but it is without signal.
Click to expand...
Click to collapse
Flash radio files. Google it for ur device.
_sushan_ said:
Looks like you are using a very old cm 13 build.
Try this one. https://www.androidfilehost.com/?fid=385035244224413102
This is cm 13 snapshot build by @Andersonmends.
Clean install is recommended ie wipe cache data internal and then flash this with pico gapps
Click to expand...
Click to collapse
Hello everyone, I installed Rom CM that the forum colleague indicated and the gapps and installed, everything went well in the installation and initialized Android, was very good in relation to the previous problems, nor know how to thank you. Just when I call it goes to the screen of the fastboot direct and I do not know how to make it not happen, but at least when the motorola logo appears it starts Android. I only notice a certain oscillation in the signal of the network of the operator and I did not find any file to download and to solve this problem of the signal of the network (or radio as you say) if they know where under some that can be installed for that Rom I thank you. I'll leave it for now and see if it's fixing. Thank you very much, ah, I would like to know if I should install the CM updates that appear on the device, it was so good that I'm afraid to accept it and thunder to give it a problem. Another thing he had TV, how to install this Rom? thanks
Hello everyone, I installed Rom CM that the forum colleague indicated and the gapps and installed, everything went well in the installation and initialized Android, was very good in relation to the previous problems, nor know how to thank you. Just when I call it goes to the screen of the fastboot direct and I do not know how to make it not happen, but at least when the motorola logo appears it starts Android. I only notice a certain oscillation in the signal of the network of the operator and I did not find any file to download and to solve this problem of the signal of the network (or radio as you say) if they know where under some that can be installed for that Rom I thank you. I'll leave it for now and see if it's fixing. Thank you very much, ah, I would like to know if I should install the CM updates that appear on the device, it was so good that I'm afraid to accept it and thunder to give it a problem. Another thing he had TV, how to install this Rom? thanks
Nikakz said:
Hello everyone, I installed Rom CM that the forum colleague indicated and the gapps and installed, everything went well in the installation and initialized Android, was very good in relation to the previous problems, nor know how to thank you. Just when I call it goes to the screen of the fastboot direct and I do not know how to make it not happen, but at least when the motorola logo appears it starts Android. I only notice a certain oscillation in the signal of the network of the operator and I did not find any file to download and to solve this problem of the signal of the network (or radio as you say) if they know where under some that can be installed for that Rom I thank you. I'll leave it for now and see if it's fixing. Thank you very much, ah, I would like to know if I should install the CM updates that appear on the device, it was so good that I'm afraid to accept it and thunder to give it a problem. Another thing he had TV, how to install this Rom? thanks
Click to expand...
Click to collapse
You can try flashing radio files.
Find one for your device from this thread : https://forum.xda-developers.com/moto-e/development/rom-stock-motorola-lollipop-rom-t3167111
I m not sure why ur device is rebooting in fastboot. Generally the most common cause for reboot in moto e is faulty lock button. But that jst reboots the phone. You can try using the phone without pressing the lock button. Use volume key wake up option and double tap to status bar to lock.
Also did you wipe cache data internal before flashing ?
And regarding the updates it depends on you. The updates you are for sering are for cm 14 / lineage os. I personally believe that nougat is still not stable enough and features are still missing hence i advised you for mashmallow roms. But if you want to try u can visit the various threads in android development and android development sections and will find nougat roms.
For installing / flashing instructions read guides in general section.
_sushan_ said:
You can try flashing radio files.
Find one for your device from this thread : https://forum.xda-developers.com/moto-e/development/rom-stock-motorola-lollipop-rom-t3167111
I m not sure why ur device is rebooting in fastboot. Generally the most common cause for reboot in moto e is faulty lock button. But that jst reboots the phone. You can try using the phone without pressing the lock button. Use volume key wake up option and double tap to status bar to lock.
Also did you wipe cache data internal before flashing ?
And regarding the updates it depends on you. The updates you are for sering are for cm 14 / lineage os. I personally believe that nougat is still not stable enough and features are still missing hence i advised you for mashmallow roms. But if you want to try u can visit the various threads in android development and android development sections and will find nougat roms.
For installing / flashing instructions read guides in general section.
Click to expand...
Click to collapse
Okay, thank you, it stabilized the signal from the network operator. I will leave as is and will not make updates at the moment. I just want to know how to make the TV function work. Thanks everyone for the help and I do not know how to mark a topic as closed in the forum.
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
Are their any projects related to the Oukitel K9 phone? I purchased one and use it on the AT&T network here in the USA.
The phone is decent but the built in Android is very generic and buggy.
I would love to unlock the potential of this phone with a custom ROM.
Let me know if this isn't the right place to ask and point me in the right direction!
Lannie
No custom roms at this time, why bother when you can custom Android 9 using Magisk , Xposed and Substratum. Although having a Lineage 17 would be nice.
I ask because the Android on this phone is so buggy and lacking features. I don't see how the options you gave will add features I need. They might as I'm new to these apps and don't know much about them.
lschafroth2 said:
I ask because the Android on this phone is so buggy and lacking features. I don't see how the options you gave will add features I need. They might as I'm new to these apps and don't know much about them.
Click to expand...
Click to collapse
If you private message me I cannot get to the messages here. If I click on messages it takes me to the register or reset password every time. I have no way to read them.
At this point it's useless to try since the mediatek drivers no longer work on Windows 10. Not a single guide on installing on Windows 10 64 bit work anymore. If anyone knows how to get the Oukitel drivers to work, let me know. No amount of driver sign or advanced boot works. Every time I plug in the phone it says the previous device malfunctioned.
It worked once and I have never connected the phone since. Will not work.
lschafroth2 said:
At this point it's useless to try since the mediatek drivers no longer work on Windows 10. Not a single guide on installing on Windows 10 64 bit work anymore. If anyone knows how to get the Oukitel drivers to work, let me know. No amount of driver sign or advanced boot works. Every time I plug in the phone it says the previous device malfunctioned.
It worked once and I have never connected the phone since. Will not work.
Click to expand...
Click to collapse
This might seem obvious, but could never get my PC (Windows10 64bit) to even recognize my Oukitel K9 until I (out of desperation, and to try to prove a point to someone) reinstalled Minimal ADB & Fastboot 1.4.3 from here:
https://androidmtk.com/download-minimal-adb-and-fastboot-tool
It's the same thing I had previously installed, and I didn't expect it to suddenly/miraculously start working, but it did.
I'll pm you.
lschafroth2 said:
Are their any projects related to the Oukitel K9 phone? I purchased one and use it on the AT&T network here in the USA.
The phone is decent but the built in Android is very generic and buggy.
I would love to unlock the potential of this phone with a custom ROM.
Let me know if this isn't the right place to ask and point me in the right direction!
Lannie
Click to expand...
Click to collapse
Best rom floss october edition with buildprop tweaks transformed this phone into next level. Thanks to phherguson
nation888888 said:
Best rom floss october edition with buildprop tweaks transformed this phone into next level. Thanks to phherguson
Click to expand...
Click to collapse
Thanks, but I sold this phone and went to a Pixel 4 XL. I needed something reliable and InTune refused to work on the old Oukitel.
Has anyone worked out ramdisk partition for Magisk?
Discovery,
Thanks to Phh has developed the perfect ROM for the Oukitel K9. Strangely I have had to try many ROMs to find the perfect one. The Lineage ROM; I had GPS issues, the Recent app button not working, and signal loss. Wanted the latest OS and this one is the winner below.
https://github.com/phhusson/treble_experimentations/releases/download/v400.e/system-squeak-arm64-ab-vndklite-gapps-secure.img.xz
Llevo un par de semanas probando la rom y no funciona el detector de huellas,se puede mejorar?hay alguna rom(Android 12) mas estable y que todo funcione?,gracias
MOD Edit: I've been testing the rom for a couple of weeks and the fingerprint sensor doesn't work, can it be improved? Is there a more stable rom (Android 12) that makes everything work? Thanks
Try the updated version https://github.com/phhusson/treble_experimentations/releases/tag/v402
Should resolve the fingerprint issue. I have also tried the AOSP 12.1 v410 and the result is the phone goes into a boot loop. Not sure why when the previous version installs so easily. I have built a custom TWRP 3.6.1 and will be trying it soon. The reason why we need to update; that the TWRP 3.3.1 version is limited and could be the reason why there are install issues with some GSIs out there. The encryption keeps reactivating even if I use scripts, flash no verify-verity. Hopefully, this will work. I'm enjoying the new version too much to start again I will keep you posted.
This one is supreme V411 and distracts me away from my Note 20 Ultra. https://github.com/phhusson/treble_experimentations/releases/tag/v411 .Works well with the Oukitel K9, recommend to use swapram module for boosting memory 4gb to 8gb. Searching for a working TWRP 3.6.
nation888888 said:
This one is supreme V411 and distracts me away from my Note 20 Ultra. https://github.com/phhusson/treble_experimentations/releases/tag/v411 .Works well with the Oukitel K9, recommend to use swapram module for boosting memory 4gb to 8gb. Searching for a working TWRP 3.6.
Click to expand...
Click to collapse
Have you found better rom for k9? I've used several gsi images but system is very laggy. Yet to find a good fast custom rom for k9.
[email protected]@ said:
Have you found better rom for k9? I've used several gsi images but system is very laggy. Yet to find a good fast custom rom for k9.
Click to expand...
Click to collapse
I found this one is the best;
https://www.mediafire.com/file/74b5bgfu0vsjcvg/CherishOS_A13-arm64-bgS-slim_20221121.img.xz/file
nation888888 said:
I found this one is the best;
https://www.mediafire.com/file/74b5bgfu0vsjcvg/CherishOS_A13-arm64-bgS-slim_20221121.img.xz/file
Click to expand...
Click to collapse
Thanks a lot. I will give it a try!
nation888888 said:
I found this one is the best;
https://www.mediafire.com/file/74b5bgfu0vsjcvg/CherishOS_A13-arm64-bgS-slim_20221121.img.xz/file
Click to expand...
Click to collapse
I've flashed this one and found it is as laggy as CrDroid. I thought it might be due to not wiping data before flashing. Decided to reboot to recovery to wipe data. And.. phone stuck at twrp logo. No go further. Do you have any better TWRP than mine 3.3.1?
Try using the "Yet another Kernel Tweaker" module in Magisk. Through all my searches I could only find the TWRP 3.3.1. Tried building using kitchen but failed. Sometimes the TWRP will take up to 5 to 10 minutes, remember it is trying to decrypt. If it takes longer then SPflash, assuming done correctly with vbmeta. After the initial install the updates and synchronization starts processing. This causes a slow-down. I thought the same. Leave the device for a day to update and synchronize then should be faster.
nation888888 said:
Try using the "Yet another Kernel Tweaker" module in Magisk. Through all my searches I could only find the TWRP 3.3.1. Tried building using kitchen but failed. Sometimes the TWRP will take up to 5 to 10 minutes, remember it is trying to decrypt. If it takes longer then SPflash, assuming done correctly with vbmeta. After the initial install the updates and synchronization starts processing. This causes a slow-down. I thought the same. Leave the device for a day to update and synchronize then should be faster.
Click to expand...
Click to collapse
TWRP logo is for hours here.
Now I can't even enter fastboot after I've chosen reboot to recovery from cherishos power menu.
I hit volup+pwr and boot menu doesn't even show up. Tried 20+ times already.
I'm stuck. The last hope is to wait for it to discharge on twrp logo and try my luck with fastboot menu again.
Otherwise I have no idea. Now I question myself why on Earth I would even try to better something that works at least average ))))
nation888888 said:
Try using the "Yet another Kernel Tweaker" module in Magisk. Through all my searches I could only find the TWRP 3.3.1. Tried building using kitchen but failed. Sometimes the TWRP will take up to 5 to 10 minutes, remember it is trying to decrypt. If it takes longer then SPflash, assuming done correctly with vbmeta. After the initial install the updates and synchronization starts processing. This causes a slow-down. I thought the same. Leave the device for a day to update and synchronize then should be faster.
Click to expand...
Click to collapse
I've managed to revive it. But still on cherishos and few other A13 roms screen is flickering. Have you got something like that?