Related
Installation
https://github.com/LegacyHuawei/local_manifests/wiki/Installation
Bugs
https://github.com/LegacyHuawei/local_manifests/wiki/Status
Downloads
https://basketbuild.com/devs/LegacyHuawei
Changelog
https://github.com/LegacyHuawei/local_manifests/wiki/CM11.0-changelog
If you have any bugs to report, open new issue at https://github.com/LegacyHuawei/local_manifests/issues
Readme
Use the standard Torch app wherever possible, it only enables flashlight. Other apps from Play Store are designed to use the camera interface, which means camera will use additional power.
For more RAM: Settings->Performance->Memory management.
Do not enable KSM, as video encoder/decoder stops working.
HuaweiSettings
Charge current - allows you to set custom charging current. While this actually limits the current input, it effectively decreases or increases the available current transferred to the battery. This is useful in multiple ways:
Slower, but more effective charging. Your battery will last longer.
Faster charging when connected to USB. For example, USB charging is limited to 500mA, but newer PCs allow drawing up to 800mA or even more. This can be configured via the setting.
Manual override of non-standard charger allowing to draw more than 500mA.
Magnetic sensor calibration - lets you delete previous calibration information. This is useful to recalibrate the compass (when it's inaccurate). Just tap the item & then open any compass up to recalibrate your sensor.
If the phone reboots unexpectedly, crash log is found at /data/dontpanic .
To report bugs, use this app: https://play.google.com/store/apps/details?id=com.tortel.syslog
Thank you, i'll try
wow, downloaded...
Many thanks, good job!
after installing cm11 and gapps, the phone always reboot to recovery
ggunzio said:
after installing cm11 and gapps, the phone always reboot to recovery
Click to expand...
Click to collapse
Did you do a factory reset before?
And does it show the cm logo or just boot to recovery?
Sent from my IDEOS X5 using Tapatalk
Blefish said:
Did you do a factory reset before?
And does it show the cm logo or just boot to recovery?
Sent from my IDEOS X5 using Tapatalk
Click to expand...
Click to collapse
before installing the rom, i've wiped everything, data, cache, system and dalvkit cache, reboot recovery. After installed the rom, and right after, installed the gapps. Then, in recovery, reboot system and after it show the huawei logo, it enters recovery without showing the CM logo.
EDIT: i will install ble_part stock, and them install again the B518, repartition again and try to install CM again.
Booted and installed just fine after doing Blepart and using your recovery. It's slow as molasses, probably in great part due to the fact that the display glitches are still there, but it certainly works, and it's as much KitKat as my Moto G. Something worth mentioning, your recovery has some sort (the same?) of display glitch as well in which the screen only seems to update after a couple of presses of the volume button, not immediately.
ROM and GAPPS, everything works fine.
No glitches for me.
Great job, thanks!
faekplastik3s said:
Booted and installed just fine after doing Blepart and using your recovery. It's slow as molasses, probably in great part due to the fact that the display glitches are still there, but it certainly works, and it's as much KitKat as my Moto G. Something worth mentioning, your recovery has some sort (the same?) of display glitch as well in which the screen only seems to update after a couple of presses of the volume button, not immediately.
Click to expand...
Click to collapse
Thanks.
I don't have any devices to compare it with so it feels "fast" to me. Its great to know the recovery suffers same display bugs, it confirms that its in fact kernel side problem. Though, kernel side does not have BLT enabled, which I thought would be the problem. I'll debug the registers, and see if I can find something odd. It could also be a clock hz issue, it was changed in 3.4.
Sent from my IDEOS X5 using Tapatalk
Blefish said:
Thanks.
I don't have any devices to compare it with so it feels "fast" to me. Its great to know the recovery suffers same display bugs, it confirms that its in fact kernel side problem. Though, kernel side does not have BLT enabled, which I thought would be the problem. I'll debug the registers, and see if I can find something odd. It could also be a clock hz issue, it was changed in 3.4.
Sent from my IDEOS X5 using Tapatalk
Click to expand...
Click to collapse
Well, it stutters a lot, and it's not nearly as smooth as something like Aurora or even stock Huawei ROMs, but I'm sure it's related to the display issues or another issue like that because even scrolling through the Settings app or the little animation in the notification drawer that flips into the shortcuts stutters like hell and drags around, which shouldn't be an issue for this device and wasn't a problem with other ROMs, and overclocking and other user-level optimizations do nothing to alleviate it.
I did also notice black screens when waking the device from lockscreen (digitizer still works) almost every time, requiring multiple attempts until the display finally wakes. I know you squashed this one multiple times, but here it is again.
It's a miracle for this to happen to begin with, so I can't help to be amazed seeing KitKat on this device. Thank YOU so much, Blefish.
do i need to have my phone rooted?
faekplastik3s said:
It's a miracle for this to happen to begin with, so I can't help to be amazed seeing KitKat on this device. Thank YOU so much, Blefish.
Click to expand...
Click to collapse
This. If some months ago anyone told me I'd be installing 4.4 on this device I'd tell them they were crazy.
Thanks for your amazing work, Blefish
Here its works as it should be, you are awesome blefish
Sent from my SM-T210 with rocketTab 2.1 + MK1 kernel using tapatalk v4
Finally i could get it to boot.
probably i broke something, i've installed the oficial rom and then, with 5.5.0.4 recovery wiped everything. Next installed the blepart, new recovery and its working
Good job sir
Thank you!
faekplastik3s said:
I did also notice black screens when waking the device from lockscreen (digitizer still works) almost every time, requiring multiple attempts until the display finally wakes. I know you squashed this one multiple times, but here it is again.
Click to expand...
Click to collapse
Yes, I have waking problems too.
Install everything (partition, 6 recovery, cm11 rom and gapps) and works pretty well so far.
Fantastico. :good::highfive:
lemene said:
Install everything (partition, 6 recovery, cm11 rom and gapps) and works pretty well so far.
Fantastico. :good::highfive:
Click to expand...
Click to collapse
is anyone having problems to connect to wifi networks? i cant connect
EDIT: i guess that is a problem with the wireless definition of the rom, im thinking this, because i can connect to open networks, but when i change the segurity of the wlan to wpa or wpa2, i can't connect to it.
Could you look at this @Blefish?
Im not sure if its a bug or not, maybe something is broken in wpa.supplicant
[]
I have flashed BlePart recovery, i have rebooted the recovery and i have flashed blepart 2.2 then i have flashed CVM Version 6.0.4.6. The phone rebooted and now i cant open the phone or recovery. I tried to install offical 2.3 from sd card but i coudn't. How can i recover my phone?
DISCLAIMER: YOU WILL BE FLASHING YOUR PHONE AT YOUR OWN RISK. YOU ARE SOLELY RESPONSIBLE FOR ANYTHING YOU DO TO YOUR PHONE, SO MAKE SURE YOU ARE WELL INFORMED AND WELL PREPARED BEFORE DECIDING TO FLASH OR INSTALL ANYTHING ON YOUR DEVICE.
I created this thread with the sole aim of helping the owners of the Japanese SAMSUNG GALAXY ALPHA SC-03E NTT DOCOMO to install the latest version of Android (LOLLIPOP) on their devices without much hassle. All updates will be provided in the future.
All THANKS GO TO @ma34S :good: FOR COMPILING THIS ROM FOR US WE HAVE BEEN WAITING FOR THIS FOR A LONG TIME AND FINALLY ITS HERE.
REQUIREMENTS
1. A properly functioning SAMSUNG GALAXY ALPHA SC-03E NTT DOCOMO. We don’t want to receive any feedback from users with faulty phones.
2. PERMANENT ROOT WITH SU INSTALLED
IF YOU ARE RUNNING A CUSTOM ROM 4.X AND HAVE A CUSTOM RECOVERY INSTALLED SKIP TO “THINGS TO DOWNLOAD”
If you don’t have root and you are running on the stock android 4.3 or 4.x here is a simple way to root your device. All the CF Auto Root methods I found never worked for me.
a. Firstly, you are probably on an older OS like 4.1, 4.2 or 4.3. You might loose all your data depending on your OS(I was running the 4.3 SC03EOMUBND2 and I didn’t loose anything, not sure of 4.1 and 4.2)
b. Download one of these stock rooted roms.
4.3 SC03EOMUBND2 or 4.3 SC03EOMUBNH2
c. Download Samsung drivers here and install it
d. Download Odin on your PC and open it
e. Make sure USB debugging is enabled on your phone in developer settings.
f. Hold the Power Button + Volume Down + Home at the same time. Your phone will enter Download Mode.
g. Now connect your phone to the PC via USB cable whiles Odin is opened.
h. Now in Odin click the PDA button and open the Rom that you downloaded earlier.
i. Make sure F.Reset time and Auto reboot are all ticked
j. Now click Start button and wait for it to display PASS at the top left corner. Your Phone might restart a few times.
k. After the Last restart and the Display of the Pass you should have root now with super su installed.
l. Congrates you have root.
m. If you have an NK2 rom go check this thread on how to root it.
3. FULLY CHARGED BATTERY. This is to prevent the phone from going off in the flashing process
4. A CUSTOM RECOVERY installed.
If you don’t have one download Sc03e-KK-KBC-CWM-v6.0.5.1_r2-recovery and install with Odin with same procedure.
NOTE: If you have an older CWM installed, update to this one.
THINGS TO DOWNLOAD
1. ANDROID LOLLIPOP ROM 5.0.2 CM12.0 UNOFFICIAL
2. GOOGLE APP(GAPPS)
INSTALLING THE LOLLIPOP ROM
1. Copy the downloaded files and place them in the phone memory or SD card(recommended)
2. BACKUP your current OS in the recovery menu so that you can restore it if you encounter any problems in the flashing process.
3. To Enter the recovery menu, turn off your phone completely. PRESS and HOLD the POWER button + Volume UP + HOME button at the same time . When DOCOMO is displayed leave the power button and still keep holding the other buttons.
4. In recovery, use volume buttons to navigate and Power to select. Now go to wipe data/factory reset and wipe data, then wipe cache partition , then go to advanced and wipe Dalvic cache.
5. When all is done go to install zip and install the cm-12-20150213-UNOFFICIAL-sc03e.zip first.
6. When done install the GAPPS package.
NOTE: IF YOU HAVE CWM 6.0.4.7 THE GAPPS PACKAGE WONT INSTALL.
7. Now go back and wipe data , cache partition and Dalvic cache again then reboot. Upon exiting CWM you will be asked to fix your root binaries... say yes!
8. Your phone will boot into Android L with a Cyanogen boot animation.
9. Set up you phone and make sure to update all your Google apps and viola! :good:
NOTE: You will have to enable root in developer options.. enable it by tapping build number several times
CURRENT PROBLEMS
The keyboard.. i found a fix for it.. when you try to type something and it shows the Input method icon in the notification area... just tap on it and disable Hardware keyboard.. it should work fine .
Again remember to UPDATE Google apps else smart lock won't work
If you Discover any problems apart from the ones already stated above feel free to post a reply. Double check your errors before posting the reply.
Once Again thanks to @ma34S for providing this rom for us.
Thank you.
IN [OFFICIAL] Japanese SGS III (SC-03E) Rooting, ROMs, Kernels & Guides
.
Bugs: NFC, osaifu keitai, oneseg, music player force close, keyboard not appearing at first, unstable usb connection.
.
Click to expand...
Click to collapse
osaifu keitai, oneseg
I will not fix it right now.
next, I will remove osaifu keitai, oneseg support (it caused error now)
music player force close
My device is not so. it works well.
keyboard not appearing at first,
Cyanogenmod's nightly is same (t0lte),
when they fix it , this device is fix too.
unstable usb connection
I think this is including base framework.
because my all device is same as sc03e. (sc02e,sc04e,sc01f,lgl22)
but it seemed it was in boot time only.
I think it is not big problem for normal use. don't you think so?
Thank you.
yhh.. i also didn't notice any sort of problems with the USB.. and the keyboard.. i found a fix for it.. when you try to type something and it shows the Input method icon in the notification area... just tap on it and disable Hardware keyboard.. it should work fine
and its good to remove those app too.. also is it possible to make facelock preinstalled?..
Does your faceunlock work?
Sent from my SC-03E using XDA Free mobile app
ma34S said:
Thank you.
IN [OFFICIAL] Japanese SGS III (SC-03E) Rooting, ROMs, Kernels & Guides
.
osaifu keitai, oneseg
I will not fix it right now.
next, I will remove osaifu keitai, oneseg support (it caused error now)
music player force close
My device is not so. it works well.
keyboard not appearing at first,
Cyanogenmod's nightly is same (t0lte),
when they fix it , this device is fix too.
unstable usb connection
I think this is including base framework.
because my all device is same as sc03e. (sc02e,sc04e,sc01f,lgl22)
but it seemed it was in boot time only.
I think it is not big problem for normal use. don't you think so?
Thank you.
Click to expand...
Click to collapse
MY Faceunlock is not working.. i want to know if yours is working.. How do i fix it says trusted face has stopped
donsleeq said:
MY Faceunlock is not working.. i want to know if yours is working.. How do i fix it says trusted face has stopped
Click to expand...
Click to collapse
Sorry, I never used Faceunlock. please tell me how to use it.
Thank you.
ma34s
---------- Post added at 09:14 PM ---------- Previous post was at 08:39 PM ----------
SC03E has a issue by using chrome browser.
this is able to fix (just workaround?) with below.
http://forum.xda-developers.com/showpost.php?p=57072138&postcount=1556
Thank you very much @TokedUp!!
ma34S said:
Sorry, I never used Faceunlock. please tell me how to use it.
[/MENTION]!!
Click to expand...
Click to collapse
go to settings
go to lock screen
set a pin lock or pattern lock..
if you already have a pin lock then go to smart lock in the lock screen settings.
then then go to trusted face..
when you try to set it up , it just crashes..
I try it but TV and Faceunlock did not work and the androids keyboard did not work also
Right now back to CM11 last update
poopha said:
I try it but TV and Faceunlock did not work and the androids keyboard did not work also
Right now back to CM11 last update
Click to expand...
Click to collapse
face unlock and tv wont work.. true but the keyboard is working fine .. check the post for the fix.
"The keyboard.. i found a fix for it.. when you try to type something and it shows the Input method icon in the notification area... just tap on it and disable Hardware keyboard.. it should work fine"
donsleeq said:
go to settings
go to lock screen
set a pin lock or pattern lock..
if you already have a pin lock then go to smart lock in the lock screen settings.
then then go to trusted face..
when you try to set it up , it just crashes..
Click to expand...
Click to collapse
Thank you
I found the menu.
Face unlock did not work too.
(But it seemd did not crash)
ma34S said:
Thank you
I found the menu.
Face unlock did not work too.
(But it seemd did not crash)
Click to expand...
Click to collapse
mine said trusted face had stopped..
Can you fix it please..
anyway what is felica lock and what does it do?
and can you please add onscreen buttons support
donsleeq said:
mine said trusted face had stopped..
Can you fix it please..
anyway what is felica lock and what does it do?
and can you please add onscreen buttons support
Click to expand...
Click to collapse
"felica lock" needs for Osaifu. But it does not work in Lolipop right now.
And then I removed it since cm-12-20150227-UNOFFICIAL-sc03e.
Thank you.
donsleeq said:
mine said trusted face had stopped..
Can you fix it please..
anyway what is felica lock and what does it do?
and can you please add onscreen buttons support
Click to expand...
Click to collapse
I think this is not problem in ROM .
It depend on Google service(I don't knot what effects)
I tried below:
1. Factory reset
1. install cm12 ( I installed cm-12-20150309-UNOFFICIAL-sc03e.zip)
2. install GAPPS( I installed gapps-lp-20141114-signed.zip )
---> Smart lock did not work
3. update all Google app & Google Play services by Google play
---> Smart lock start to work.
* see attachment images (my screen shot).
Thank you
ma34s
cm-12-20150309-UNOFFICIAL-sc03e
http://site.kbc-brick.org/samsung/sc03e/recovery-kernel-rom
My changes
-Fix color LED notification
CM changes
please see http://www.cmxlog.com/12/t0lte/ .
this is for t0lte , but it almost same as my build for sc03e except android_device_samsung_t0lte.
Thanks man.. I'm trying that now.
And is it possible to get on screen buttons.. I will be glad to get it.
donsleeq said:
Thanks man.. I'm trying that now.
And is it possible to get on screen buttons.. I will be glad to get it.
Click to expand...
Click to collapse
it is possible for you to enable on screen key by writing following in /system/build.prop
Code:
qemu.hw.mainkeys=0
it works in my device,
please try it
Thank you
cm-12-20150310-UNOFFICIAL-sc03e
Download:
http://site.kbc-brick.org/samsung/sc03e/recovery-kernel-rom
My changes:
-Fix GPS
CM changes:
please see http://www.cmxlog.com/12/t0lte/ .
this is for t0lte , but it almost same as my build for sc03e except android_device_samsung_t0lte.[/QUOTE]
---------- Post added at 06:59 PM ---------- Previous post was at 06:57 PM ----------
@amakuramio post at here
bugs
1. keyboard on first install
2. contents on sd card not properly displayed
Click to expand...
Click to collapse
bugs
2. contents on sd card not properly displayed
Click to expand...
Click to collapse
I don't understand what means.
Thank you.
2015/03/10 bugs:
1. keyboard on boot
初期化した際、キーボードは表示されません。（設定→言語・入力でハードウェアをＯＮすることで使えます）
2. When connected to USB, it takes a long time to display all files when connected.
ＵＳＢ経由でケータイがパソコンと接続した際、ストレージ内のファイルの読み込みのは長い時間がががります。
また、一部のファイルは表示されません。
3. baseband unknown
ベースバンド不明
amakuramio said:
Thank you.
2015/03/10 bugs:
1. keyboard on boot
初期化した際、キーボードは表示されません。（設定→言語・入力でハードウェアをＯＮすることで使えます）
2. When connected to USB, it takes a long time to display all files when connected.
ＵＳＢ経由でケータイがパソコンと接続した際、ストレージ内のファイルの読み込みのは長い時間がががります。
また、一部のファイルは表示されません。
3. baseband unknown
ベースバンド不明
Click to expand...
Click to collapse
Oh thank you, I don't say that can't understand English.
But thank you.
about 1 and 2:
I posted at #2
It will fix by Cyanogenmod maybe.
about 3:
really? my device recognize the baseband. I think no problem.
I asked to other guy on twitter.
he said that baseband is OK.
please check your operation and flash again.
thank you
(Edit 1) Found a fix already! Read post 2!!!
Hello there,
I've been having a OnePlus Two since 4 months already, and had like 2 or 3 home button not working issues.
They used to fixed by themselves after a couple of days of not working, but not this last time.
I tried already the reinstalling system (after formatting system via TWRP), clean it several times, hard reset (hold power button for more than 20 seconds), complete drain battery and fully charge it again, force stop fingerprint service, take out the tempered glass screen protector, and none of those solutions worked.
I here attach (copy the link, can't upload a video directly to this post) a video in which you can see that whenever I power on the screen (still locked), the home button works for several times, but as soon as I unlock it (pattern lock) it stops working. This makes me think that the problem is software, not hardware, but as I said before, already tried reinstalling OOS 3.0, wiping system, cache, data, internal storage, etc.
I compressed the video so it wouldnt be too big, but quality is good enough, just rise the volume so you can listen to the "vibration" that the home button produce.
Any help would be appreciated.
Sincerely,
Daniel Castro
Fix for the issue!
Forum people, I found a fix!
Ok, the solution for making the home button work again (with fingerprint sensor) is the following.
-Factory reset while in OOS 3.0
-Set up everything up and then reboot into fastboot mode
-Install OOS 2.1 via fastboot (you will need to search the forums for it)
-Set up everything up and try to set up fingerprint (it wont work)
-Copy OOS 3.0 (Beta) in the root of the phone
-Reboot into stock recovery and flash OOS 3.0 (beta)
-Factory reset it and set up everything again
-Voila!
Feel free to try this method and reply to this threat or P.M. me for any help.
Sincerely,
Daniel Castro
I have the same problem
Tomorrow i'll try your method
I've posted a questione about this issue,
I think the One plus team should find a solution to this problem that afflict many users
Also, don't forget to rotate your phone 720 degrees, counter clock wise! ? hocus pocus....
DCastro555 said:
Forum people, I found a fix!
Ok, the solution for making the home button work again (with fingerprint sensor) is the following.
-Factory reset while in OOS 3.0
-Set up everything up and then reboot into fastboot mode
-Install OOS 2.1 via fastboot (you will need to search the forums for it)
-Set up everything up and try to set up fingerprint (it wont work)
-Copy OOS 3.0 (Beta) in the root of the phone
-Reboot into stock recovery and flash OOS 3.0 (beta)
-Factory reset it and set up everything again
-Voila!
Feel free to try this method and reply to this threat or P.M. me for any help.
Sincerely,
Daniel Castro
Click to expand...
Click to collapse
Will it erase my internal storage during that fast boot step? So I can backup all my data.
Sent from my ONE A2003 using Tapatalk
these fixes are all coincidences... we need to request a definitive fix from One plus team if is a software issue.
LOL9988 said:
Will it erase my internal storage during that fast boot step? So I can backup all my data.
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
It will erase everything, make a backup before starting the process.
faustin95 said:
these fixes are all coincidences... we need to request a definitive fix from One plus team if is a software issue.
Click to expand...
Click to collapse
Most probably hardware design fault, solution would be to redesign the phone and release a fixed design, will probably not happen unless oneplus3 is the solution.
And I second that it's just coincident behind these back and forth flashing of firmwares "solving" it, almost religious. But what are people to do when oneplus is not a company that takes responsibility for they're mistakes.
pitrus- said:
Most probably hardware design fault, solution would be to redesign the phone and release a fixed design, will probably not happen unless oneplus3 is the solution.
And I second that it's just coincident behind these back and forth flashing of firmwares "solving" it, almost religious. But what are people to do when oneplus is not a company that takes responsibility for they're mistakes.
Click to expand...
Click to collapse
If it works, its worth a try . And yeah, but we are not in any OnePlus Forum, neither debating about if they are gonna do anything about their own issue, we are trying to fix what an irresponsable company wont.
can we make together an official request to one plus to give us an answer or explanation about this? a lot of users are facing this issue, it's not normal
This is my second opt I bought that this problem has happened
sorry for my english
I had also tried lot of things but home button is not responsive at all.. H2os,exodus,oxygen 2.1 ,3.0 same everywhere
---------- Post added at 04:01 AM ---------- Previous post was at 03:59 AM ----------
Error is: when i open fingerprint setting
Enrollment not working try differnt finger or try again ... Nd fingerprint autotest not starting also
i've turned to stock i've updated to oxygen 3.0 bet and the button worked again
i think rooting installing twrp and installing different roms may be the cause of this issue
faustin95 said:
i think rooting installing twrp and installing different roms may be the cause of this issue
Click to expand...
Click to collapse
Unfortunately that is not the case, it's a hardware design bug.
However you can f-k up your finger scanner by damage your persistant-partition if you flash up and down between different ROM/bootloader revisions. But it's easily fixed by flashing the image file for that partition again.
pitrus- said:
Unfortunately that is not the case, it's a hardware design bug.
Click to expand...
Click to collapse
it's a driver issue
faustin95 said:
it's a driver issue
Click to expand...
Click to collapse
50/50 moisture sensitivity and driver issue.
Home button has been working fine for a year, installed 3.0.1 today and suddenly home button only works in OOS 3.0.1. No longer works in CM 13, yet works fine in OOS 3.0.1. Definitely a driver issue.
Tried installing OOS 2.2.1, wiping, then installing Grarak's CM 13 and home button refuses to work. Wiped system, data, cache, installed OOS 3.0.1 and home button works again. Tried wiping again and installed CM 13, home button stopped working. Wiped and reinstalled OOS 3.0.1, home button works again.
Odd thing, my phone will only work with CM13 roms and OOS 2.2.0 or less for fps and home button. Nothing will fix or ever work.
For me, the home button stopped working for a short while on Graraks, then it just jumped back to life again and I haven't had any more home button blackouts after that. If it's a driver issue, it's an extremely intermittent one.
The fingerprint scanner has stopped working from time to time at lockscreen, but this is acceptable for an official hackjobb supported scanner until official sources are released ?
Need Help with this!
Hi everyone!
I have a OP 2 for more than one and a half years now and never had any issues with it(stayed stock...) until recently. I didnt update the phone to the latest version and was putting it off, and today in the afternoon when I tried to unlock my phone it said the 'Fingerprint hardware is not available' and after unlocking the phone with the pattern, it IMMEDIATELY LOCKS ITSELF BACK !!! after split second it just locks the screen while everything is working like connection, wifi, messages, notifications, etc. but due to this I cannot access anything on the phone, can't go to settings and switch to onscreen nav bar buttons, can't force stop/wipe cache the com.fingerprints.serviceext either, tried restarting it several times, downloaded the update but can't even install it because the phone just locks! I have no idea what would fix it and I am avoiding a full reset and wipe on the phone(also based on all i have read, dont think it would fix it anyways)
If anyone knows whats the problem or has dealt with it or knows someone who has, please help me out here on how to fix this and what to do. I did not root it or flash custom ROM's on it yet so literally dont know why it happened.
Thanks,
Max
Hello,
I have noticed since I have flashed the universal bootloader for LineageOS 14.1, that sometimes I am unable to perform the pull down action on the notification bar in order to open the quick settings.
Sometimes, this is fixed by locking the screen by pressing the power button and unlocking it after. This does not always work though. A more reliable way to "fix" this is to completely reboot the phone.
Can someone please advise if there's a known, more permanent, fix for this issue?
PS I went back to stock through EDL (shis should overwrite the boostack, right?), and the issue is present on stock rom too (2017G B10 7.1.1)
thanks a lot in advance!
rzarectha said:
Hello,
I have noticed since I have flashed the universal bootloader for LineageOS 14.1, that sometimes I am unable to perform the pull down action on the notification bar in order to open the quick settings.
Sometimes, this is fixed by locking the screen by pressing the power button and unlocking it after. This does not always work though. A more reliable way to "fix" this is to completely reboot the phone.
Can someone please advise if there's a known, more permanent, fix for this issue?
PS I went back to stock through EDL (shis should overwrite the boostack, right?), and the issue is present on stock rom too (2017G B10 7.1.1)
thanks a lot in advance!
Click to expand...
Click to collapse
Wait what? So you flashed the universal bootloader AFTER installing Lineage, and presumably using it?
If you installed an EDL ROM and the problem persists, it's definitely not the bootstack. are you sure there's nothing else that you installed both on stock and los?
Choose an username... said:
Wait what? So you flashed the universal bootloader AFTER installing Lineage, and presumably using it?
If you installed an EDL ROM and the problem persists, it's definitely not the bootstack. are you sure there's nothing else that you installed both on stock and los?
Click to expand...
Click to collapse
I definitely did not flash the bootloader after flashing lineage, I do not believe it's possible; my apologies if my wording was off.
As you said, it is possible that the switch to Lineage was just a coincidence.
You make a good point though, I did restore the same titanium backup apps on both ROMs. I should factory reset and see if it solves it.
cheers
rzarectha said:
I definitely did not flash the bootloader after flashing lineage, I do not believe it's possible; my apologies if my wording was off.
As you said, it is possible that the switch to Lineage was just a coincidence.
You make a good point though, I did restore the same titanium backup apps on both ROMs. I should factory reset and see if it solves it.
cheers
Click to expand...
Click to collapse
Yeah, I just didn't know what you meant. I guess it might be a root app or something. I used Material Notification Shade on stock but it had a couple of problems that i didn't figure out until some time ago (it was pretty obvious though)
And for something physical, have you fitted a screen protector lately? I had one that interfered with pull down.
Last few days I tried to use custom ROM. Volte doesn't work. I've given up on that issue now. Now problem is Miui pro.
After flashing it keeps showing boot logo ( I waited for more than 30 minutes) but the older version (7... Something) flashes without any problem.
How long should I wait to complete it's booting process( more than an hour??!!!!!)
P.s- device encryption is enabled [ but I don't think it's causing the problem cuz older version is doing fine]
http://miuiid.blogspot.in/p/rom.html?m=1
Download this and flash like normal rom.
First clear data, dv-cache, system,
Then flash this along with magisk
After flash don't clear dv-cache, not even after flashing magisk and dont change anythink in the system partition untill first boot u can also flash the magisk modules straight ahead.
This is miui id best, u get paid themes free, also volte working and it does have split screen.
Note:- don't forget to flash magisk, don't clear cache after flashing the rom and i mean anytime don't do it it will take a lot of time then.
First boot will take 15 min, dont wait for it once it gets past the boot logo and enters the bootanimation wait for 2 min then again do force reboot by long pressing the power button, do it one more time this time wait for 5 min if it opens then good or again reboot. This time it will happen.
The rom is stable and totally worth the trouble.
This process is just to reduce the first booting time.
Thanks ?
Also check this post for more information.
Link:- https://forum.xda-developers.com/xi...t/arvanasoft-miui-9-7-10-20-redmi-3s-t3694036
Thanks.
Im running Miui 9.2 global stable 9.2.2.0
Can i do dirty install? I dont wanna lose apps data
Im using stock miui global stable 9.2.2. Android 6.0
If i wanna install miui id, do i need to wipe all , as in format my handset. Or is it ok to just wipe system, cache dv? I dont wanna lose my apps data
@Trovies hi,
Just do titanium or swiftbackup search the apk in google, and u can do dirty flash but i will not recommend it.
Note :- download the premium version of the swiftbackup from the internet.
Thanks
Flash lazyflasher.zip
Sagar_zac said:
http://miuiid.blogspot.in/p/rom.html?m=1
Download this and flash like normal rom.
First clear data, dv-cache, system,
Then flash this along with magisk
After flash don't clear dv-cache, not even after flashing magisk and dont change anythink in the system partition untill first boot u can also flash the magisk modules straight ahead.
This is miui id best, u get paid themes free, also volte working and it does have split screen.
Note:- don't forget to flash magisk, don't clear cache after flashing the rom and i mean anytime don't do it it will take a lot of time then.
First boot will take 15 min, dont wait for it once it gets past the boot logo and enters the bootanimation wait for 2 min then again do force reboot by long pressing the power button, do it one more time this time wait for 5 min if it opens then good or again reboot. This time it will happen.
The rom is stable and totally worth the trouble.
This process is just to reduce the first booting time.
Thanks
Click to expand...
Click to collapse
very well explained. As per habit I was clearing both dv cache and cache and due to this rom was taking too much time to boot. But after reading your post I have made clear pretty much everything. This is the best MIUI rom I have ever used. Performance, battery life, smoothness everything is spot on. I just wish it would had double tap to wake feature and recent apps menu would had icon mode option. Audio through earphones is also low. other than that its fantastic rom.
https://forum.xda-developers.com/xi...t/arvanasoft-miui-9-7-10-20-redmi-3s-t3694036
Vinayakn73 said:
very well explained. As per habit I was clearing both dv cache and cache and due to this rom was taking too much time to boot. But after reading your post I have made clear pretty much everything. This is the best MIUI rom I have ever used. Performance, battery life, smoothness everything is spot on. I just wish it would had double tap to wake feature and recent apps menu would had icon mode option. Audio through earphones is also low. other than that its fantastic rom.
https://forum.xda-developers.com/xi...t/arvanasoft-miui-9-7-10-20-redmi-3s-t3694036
Click to expand...
Click to collapse
Well u don't get everything but the things you mentioned i don't use it. So... Good for me right. ?For the audio problem use Dolby from the magisk repo the lenovo A7000 one the others don't work. Just flash the settings zip after flashing the rom and don't clear cache
Sagar_zac said:
Well u don't get everything but the things you mentioned i don't use it. So... Good for me right. For the audio problem use Dolby from the magisk repo the lenovo A7000 one the others don't work. Just flash the settings zip after flashing the rom and don't clear cache
Click to expand...
Click to collapse
well I'm using viper4android but with it audio quality increased but volume decreased further, I think I can live up with it. After flashing settings zip I did everything as you mentioned (did not clear dvk cache or cache) but now rom is stuck on mi logo (almost 20 to 25 minutes) can I dirty flash rom again???? Or do I need to do clean install??
Vinayakn73 said:
well I'm using viper4android but with it audio quality increased but volume decreased further, I think I can live up with it. After flashing settings zip I did everything as you mentioned (did not clear dvk cache or cache) but now rom is stuck on mi logo (almost 20 to 25 minutes) can I dirty flash rom again???? Or do I need to do clean install??
Click to expand...
Click to collapse
Just do a clean flash, rom + settings zip, together like do a batch. Then no clear cache boot and do the process
Sagar_zac said:
Just do a clean flash, rom + settings zip, together like do a batch. Then no clear cache boot and do the process
Click to expand...
Click to collapse
yup I'm not noob and doing exactly as you are saying but still I'm struggling with this rom
1st attempt wipe dalvik, system, data cache - flashed rom - flashed settings zip - flashed magisk - tried to flash magisk modules (failed) - reboot without any wipe - rom didn't boot
2nd attempt - clean installed with only rom and settings zip - booted normally - went to bootloader again installed magisk - reboot system - went in bootloader again - flashed app systemizer module- rebooted successfully - went to magisk manager and added module youtube advanced - reboot stuck on mi logo
3rd attempt - reinstalled clean as described in 2nd attempt till the setup of app sytemizer on reboot - went to app systemizer module and ticked gps app- module asked to reboot boooooom stuck on mi logo
Everything I wrote above is my common practice with every miui rom but I don't know why It is not working with this rom. anyways thanks for your help I am moving to global stable as I can't live without these modules. n sorry for bad english
Vinayakn73 said:
yup I'm not noob and doing exactly as you are saying but still I'm struggling with this rom
1st attempt wipe dalvik, system, data cache - flashed rom - flashed settings zip - flashed magisk - tried to flash magisk modules (failed) - reboot without any wipe - rom didn't boot
2nd attempt - clean installed with only rom and settings zip - booted normally - went to bootloader again installed magisk - reboot system - went in bootloader again - flashed app systemizer module- rebooted successfully - went to magisk manager and added module youtube advanced - reboot stuck on mi logo
3rd attempt - reinstalled clean as described in 2nd attempt till the setup of app sytemizer on reboot - went to app systemizer module and ticked gps app- module asked to reboot boooooom stuck on mi logo
Everything I wrote above is my common practice with every miui rom but I don't know why It is not working with this rom. anyways thanks for your help I am moving to global stable as I can't live without these modules. n sorry for bad english
Click to expand...
Click to collapse
Ya i know modules can be a pain in the ass only one suggestion when ever after flashing a module if its stuck in the bootloop then just use magisk Uninstaller then again install Magisk or use magisk for recovery to remove the particular module which is causing boot loop also use root youtube valence and use universal installer it will not cause bootloop. Also use minimal module only what you need. Ok then. Also do as u discreet i am fine in this rom. And its great. ?
See my modules
I too use YouTube vanced.
Man u got to find solutions not give up and change only after a few attempts. U know how many times i got bootloop because of this rom and it's compatibility issues with the modules. After many attempts i got it. Now its the best custom miui rom ever also the dev is constant and hops to bring miui 10. Also if u have used this rom only for a few hours u can realize the difference.
Sagar_zac said:
I too use YouTube vanced.
Man u got to find solutions not give up and change only after a few attempts. U know how many times i got bootloop because of this rom and it's compatibility issues with the modules. After many attempts i got it. Now its the best custom miui rom ever also the dev is constant and hops to bring miui 10. Also if u have used this rom only for a few hours u can realize the difference.
Click to expand...
Click to collapse
yup there is no doubt this is best custom miui rom out there. But this bootloop and boot time driving me nuts. I wonder why all this problems are popping up though the rom is based on official firmware and I've never faced such problem with official roms. I will give it a try again after two days. I just hope that time it will go smooth.