Nubia Z17 Mini S V2.17 and GApps working? - ZTE Nubia Z17 Questions & Answers

Hello,
I wanted to ask if somebody can confirm if the new Mini S update is working with existing Gapps?
Thanks!

I don't have this device

TheWeeezel said:
Hello,
I wanted to ask if somebody can confirm if the new Mini S update is working with existing Gapps?
Thanks!
Click to expand...
Click to collapse
I received my Z17 mini S with International Firmware EN, with gapps . Android 7.1.1 , Nubia UI 5.17.6.20 , Firmware NX589J_ENCommon_V1.01 . Works Perfect, love this phone
wwwDOTup-4everDOTcom/27gya085krcw Firmware Download
How to:
1. transfer to the phone.
2. go to Settings -> System upgrade -> Local update.
3. Choose from Local -> point the file -> install now.
4. the phone should reboot twice.

diogoasisti said:
I received my Z17 mini S with International Firmware EN, with gapps . Android 7.1.1 , Nubia UI 5.17.6.20 , Firmware NX589J_ENCommon_V1.01 . Works Perfect, love this phone
wwwDOTup-4everDOTcom/27gya085krcw Firmware Download
How to:
1. transfer to the phone.
2. go to Settings -> System upgrade -> Local update.
3. Choose from Local -> point the file -> install now.
4. the phone should reboot twice.
Click to expand...
Click to collapse
I did that now im stuck in the setup assistant. wont connect to wifi or network even tough both is there. tried many thing just wont connect and wont let me get rid of the assistent... does anybody have an idea? i can get into stock recovery and wipe data but nothing helps. since i cant get into the phone i cant setup debuging so i cant flash or root anymore... would apreciate some tips!
regards

TheWeeezel said:
I did that now im stuck in the setup assistant. wont connect to wifi or network even tough both is there. tried many thing just wont connect and wont let me get rid of the assistent... does anybody have an idea? i can get into stock recovery and wipe data but nothing helps. since i cant get into the phone i cant setup debuging so i cant flash or root anymore... would apreciate some tips!
regards
Click to expand...
Click to collapse
I got this problem too before.
you will need a OTG Cable type C, with this you need to put a chinese version firmware V2.17 LAST shareDOTweiyunDOTcom/5oybMyt
Put in a usb key an flash into recovery. this will solve this problem. if you want come back to stock, flash again a stock version without clear cache/dalvin.

diogoasisti said:
I got this problem too before.
you will need a OTG Cable type C, with this you need to put a chinese version firmware V2.17 LAST shareDOTweiyunDOTcom/5oybMyt
Put in a usb key an flash into recovery. this will solve this problem. if you want come back to stock, flash again a stock version without clear cache/dalvin.
Click to expand...
Click to collapse
Hey can you upload the rom again because it gives me an error after 1% of the installation. Maybe the file is corrupt somehow. It says install package failure. And in the boot process it says siganture verification failed. error 21. footer is wrong
I put the rom you provided onto my usb otg stick and tried to flash it. after a wipe it still doesnt work and if i flash the us version provided earlier in the post above its still not able to go trough the initial setup wizard.

TheWeeezel said:
Hey can you upload the rom again because it gives me an error after 1% of the installation. Maybe the file is corrupt somehow. It says install package failure. And in the boot process it says siganture verification failed. error 21. footer is wrong
I put the rom you provided onto my usb otg stick and tried to flash it. after a wipe it still doesnt work and if i flash the us version provided earlier in the post above its still not able to go trough the initial setup wizard.
Click to expand...
Click to collapse
The better way to install a stock rom ( v 1.01 ) is :
1 - Install a CN version 2.17, NOT install Gapps
2 - After setup initial setup, put rom V 1.01 in storage and reboot to twp recovery.
3 - Install stock rom, wipe dalvin/cache, root and reboot.
4 - If in initial setup, you get freezed in wifi settings, come to twp recovery and wipe data, ( not format data ),wipe dalvin/cache, root again, and reboot.
5 - In you got freeze in initial setup settings when it ask you to put a name, after setup a date/time, you click next without put a name, and you must be good to finish setup and enjoy the phone.
Stock Firmware
up-4everDOTcom/27gya085krcw
v 2.17 Firmware
shareDOTweiyuDOTcom/5oybMyt

diogoasisti said:
The better way to install a stock rom ( v 1.01 ) is :
1 - Install a CN version 2.17, NOT install Gapps
2 - After setup initial setup, put rom V 1.01 in storage and reboot to twp recovery.
3 - Install stock rom, wipe dalvin/cache, root and reboot.
4 - If in initial setup, you get freezed in wifi settings, come to twp recovery and wipe data, ( not format data ),wipe dalvin/cache, root again, and reboot.
5 - In you got freeze in initial setup settings when it ask you to put a name, after setup a date/time, you click next without put a name, and you must be good to finish setup and enjoy the phone.
Stock Firmware
up-4everDOTcom/27gya085krcw
v 2.17 Firmware
shareDOTweiyuDOTcom/5oybMyt
Click to expand...
Click to collapse
Okay so i did that and everything seems to be working fine until i open the sms app which immediatly closes down again. also when i try to go into language and input and disable text correction it immediatly closes down did you ever encounter this issue? thanks for your help so far!

TheWeeezel said:
Okay so i did that and everything seems to be working fine until i open the sms app which immediatly closes down again. also when i try to go into language and input and disable text correction it immediatly closes down did you ever encounter this issue? thanks for your help so far!
Click to expand...
Click to collapse
So, this problem of sms app, you need to do a factory reset in accessibility settings, and root again, and after its all ok

diogoasisti said:
The better way to install a stock rom ( v 1.01 ) is :
1 - Install a CN version 2.17, NOT install Gapps
2 - After setup initial setup, put rom V 1.01 in storage and reboot to twp recovery.
3 - Install stock rom, wipe dalvin/cache, root and reboot.
4 - If in initial setup, you get freezed in wifi settings, come to twp recovery and wipe data, ( not format data ),wipe dalvin/cache, root again, and reboot.
5 - In you got freeze in initial setup settings when it ask you to put a name, after setup a date/time, you click next without put a name, and you must be good to finish setup and enjoy the phone.
Stock Firmware
up-4everDOTcom/27gya085krcw
v 2.17 Firmware
shareDOTweiyuDOTcom/5oybMyt
Click to expand...
Click to collapse
Is it worthy to switch from 2.17 (or 2.16 in my case) to the EN ROM 1.01? Does it have the same problems with Google Play Store? (the apps do not update immediately and they can take days!)
Someone told me (not sure if he's right) that in the MWC in Barcelona Nubia presented ROM NX589J_ENCommon_V1.02 and also that now it's available the V.104 where NFC and headphones are working (I assume before this version they didn't).
Does anyone know where we can download these ROMs? Could anyone provide more information? Thanks

logosfp said:
Is it worthy to switch from 2.17 (or 2.16 in my case) to the EN ROM 1.01? Does it have the same problems with Google Play Store? (the apps do not update immediately and they can take days!)
Someone told me (not sure if he's right) that in the MWC in Barcelona Nubia presented ROM NX589J_ENCommon_V1.02 and also that now it's available the V.104 where NFC and headphones are working (I assume before this version they didn't).
Does anyone know where we can download these ROMs? Could anyone provide more information? Thanks
Click to expand...
Click to collapse
It must work, from 2.16 to 1.01. No Gapps problem, notifications work( badge number not work ). Headphone not work, nfc not tested, I don't use this. I would like to know to where get this 1.04 rom, didn't find too

Thanks for your answer @diogoasisti
diogoasisti said:
The better way to install a stock rom ( v 1.01 ) is :
1 - Install a CN version 2.17, NOT install Gapps
2 - After setup initial setup, put rom V 1.01 in storage and reboot to twp recovery.
3 - Install stock rom, wipe dalvin/cache, root and reboot.
4 - If in initial setup, you get freezed in wifi settings, come to twp recovery and wipe data, ( not format data ),wipe dalvin/cache, root again, and reboot.
5 - In you got freeze in initial setup settings when it ask you to put a name, after setup a date/time, you click next without put a name, and you must be good to finish setup and enjoy the phone.
Stock Firmware
up-4everDOTcom/27gya085krcw
v 2.17 Firmware
shareDOTweiyuDOTcom/5oybMyt
Click to expand...
Click to collapse
When I try to download the Stock Firmware that you linked some times ago, in the download page it says is version 1.04:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is this true? I assume you didn't upload this ROM but just want to confirm.

logosfp said:
Thanks for your answer @diogoasisti
When I try to download the Stock Firmware that you linked some times ago, in the download page it says is version 1.04:
Is this true? I assume you didn't upload this ROM but just want to confirm.
Click to expand...
Click to collapse
Ow sorry, i understood now, this file was not uploaded for me, the name is incorrect, just it. It's a 1.01 version. So, there is no 1.04 version.

Related

[rom] [android 5.0.2] [lollipop] [cm12 unofficial] galaxy s3 alpha sc-03e ntt docomo

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
初期化した際、キーボードは表示されません。(設定→言語・入力でハードウェアをONすることで使えます)
2. When connected to USB, it takes a long time to display all files when connected.
USB経由でケータイがパソコンと接続した際、ストレージ内のファイルの読み込みのは長い時間がががります。
また、一部のファイルは表示されません。
3. baseband unknown
ベースバンド不明
amakuramio said:
Thank you.
2015/03/10 bugs:
1. keyboard on boot
初期化した際、キーボードは表示されません。(設定→言語・入力でハードウェアをONすることで使えます)
2. When connected to USB, it takes a long time to display all files when connected.
USB経由でケータイがパソコンと接続した際、ストレージ内のファイルの読み込みのは長い時間がががります。
また、一部のファイルは表示されません。
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

[Q] USB Debugging Issue on Redmi 4G LTE

Hello developers
This is to bring to your notice that i have Redmi 4G with me. I am not able to connect it to my laptop via USB
My Laptop Configutration:
OS - WIn 8.1 [x64]
HDD - 1TB
I have CM-11 on my Redmi 4G, fully rooted and even the "Developer options are enabled on the phone.
Despite that I am not able to connect the phone through my laptop.
I have tried the following two threads by far, but none worked for me :
http://en.miui.com/thread-34384-1-1.html
and this as well :
http://en.miui.com/thread-78249-1-1.html
I did endless search on XDA-Forum, MiUi forum, Google but none as in nothing worked.
Here are few screenshots I am attaching just for your reference purpose:
Laptop Screenshots​
My Laptop's Device Manager:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When I try installing or updating HM NOTE 4G (LTE) drivers , I get this error :
When I enable the Tethering options , I get this screen ( P.S -> Its different from screenshot-1)
CellPhone Screenshots​
My Developer Options screen:
Notification Drawer Screenshot:
USB Computer Connection Screenshot:
Now, can somebody please tell me where am I doing it wrong. This problem repeats itself every now and troubles me.
Can the developers tell me as to what is wrong. ? ??
PLEASE HELP me Developers.
Response eagerly awaited.
Thanks & regards.
Dude, do you really think that Windows install/update driver ever worked since win 2000? Also 100%working solution is drivermax/drp.su
sm_94 said:
Dude, do you really think that Windows install/update driver ever worked since win 2000? Also 100%working solution is drivermax/drp.su
Click to expand...
Click to collapse
Bro it always did worked for me almost 99.99% cases, and secondly i have tried doing all this well in advance. I tried almost 3-4 such softwares(simialar to drivermax/drp.su)
to check as to any update for my device driver, but nothing works. . !
Any other solution is more than welcome.
Thanks & regards.
Do u have legal copy of Windows?
sm_94 said:
Do u have legal copy of Windows?
Click to expand...
Click to collapse
Yes brother its a genuine copy of Windows 8.1 [x64] OS.
That's probably the reason why it was working most of the time tho, switch to Ubuntu and gg problem slowed.
sm_94 said:
That's probably the reason why it was working most of the time tho, switch to Ubuntu and gg problem slowed.
Click to expand...
Click to collapse
Bro just due to one driver issue, you are telling me to shift my OS completely. That is something that would consume a lot of time . Tell me something for this OS only please.
Thanks & regards.
Hmm how about livecd boot?
sm_94 said:
Hmm how about livecd boot?
Click to expand...
Click to collapse
That might come handy. let me give it a try.
Will inform you shortly in an hour at max.
Blah, I've forgotten about it, download philz touch cwm and there is Pico adb with drivers for redmi integrated into it ;p
sm_94 said:
Blah, I've forgotten about it, download philz touch cwm and there is Pico adb with drivers for redmi integrated into it ;p
Click to expand...
Click to collapse
Brother , I already have PhilZ touch recovery installed on my Redmi 4G. . .
Please explain this part though -> and there is Pico adb with drivers for redmi integrated into it
Didn't get this part of your reply.
Thanks & regards.
I own a Note 4g and had the exact same problem (although with miui installed, not cm). Whas this problem present since you first installed cm?
From the middle of nowhere to the center of everywhere...
chandoliasnikos said:
I own a Note 4g and had the exact same problem (although with miui installed, not cm). Whas this problem present since you first installed cm?
From the middle of nowhere to the center of everywhere...
Click to expand...
Click to collapse
Brother, I faced this issue on both the CM-11 ( currently installed on my phone) and when I was initially on MiUi v6.4.2.0[KHIMICB] , the issue was on that ROM too.
Doesn't understand why such happens frequently with me.
Highly pissed off.
Regards.
I have miui and not cm. This problem occured about a month after using the phone, so I got suspicions that the phone itself was responsible for this. Particularly I used to "dirty" flash each miui developer rom in the top of the previous, and just do a wipe cache and wipe dalvik cache before. So I decided to move to a miui stable version with clean install. Did a full wipe, cleaned everything and installed rom. After that everything worked just fine with every windows pc and laptop I've tried.
From the middle of nowhere to the center of everywhere...
chandoliasnikos said:
I have miui and not cm. This problem occured about a month after using the phone, so I got suspicions that the phone itself was responsible for this. Particularly I used to "dirty" flash each miui developer rom in the top of the previous, and just do a wipe cache and wipe dalvik cache before. So I decided to move to a miui stable version with clean install. Did a full wipe, cleaned everything and installed rom. After that everything worked just fine with every windows pc and laptop I've tried.
From the middle of nowhere to the center of everywhere...
Click to expand...
Click to collapse
I understand this brother. Though i never developed any ROM or such thing myself, but i have been tinkering with almost every device i ever got my hands laid on.
Its in my habit to do a full clean swipe of everything be it system wipe, cache, dalvik cache basically everything which a developer says to do before installing a new ROM on the device.
I have been doing it from the start, but still got this issue.
I did a clean install [twice] of MiUi ROM[Stable] but still this issue came in like every 10-20 days. So , recently i have switched to a custom ROM , CM-11 as i mentioned.
For now i am using an alternate to transfer content between the two devices, and waiting for someone from the developers end to help me out.
Lets see when do i get a stable solution for this never-ending issue.
Regards.
chandoliasnikos said:
I have miui and not cm. This problem occured about a month after using the phone, so I got suspicions that the phone itself was responsible for this. Particularly I used to "dirty" flash each miui developer rom in the top of the previous, and just do a wipe cache and wipe dalvik cache before. So I decided to move to a miui stable version with clean install. Did a full wipe, cleaned everything and installed rom. After that everything worked just fine with every windows pc and laptop I've tried.
From the middle of nowhere to the center of everywhere...
Click to expand...
Click to collapse
I understand this brother. Though i never developed any ROM or such thing myself, but i have been tinkering with almost every device i ever got my hands laid on.
Its in my habit to do a full clean swipe of everything be it system wipe, cache, dalvik cache basically everything which a developer says to do before installing a new ROM on the device.
I have been doing it from the start, but still got this issue.
I did a clean install [twice] of MiUi ROM[Stable] but still this issue came in like every 10-20 days. So , recently i have switched to a custom ROM , CM-11 as i mentioned.
For now i am using an alternate to transfer content between the two devices, and waiting for someone from the developers end to help me out.
Lets see when do i get a stable solution for this never-ending issue.
Regards.
for Developer Option Enable
MIUI 5
1. Go To "Settings > About Phone > Android version."
2. Tap "Android version" until developer mode appears.
MIUI 6
1. Go To "Settings > About Phone > MIUI version."
2. Tap "MIUI version" until developer mode appears.
after that, you can check your device is attached to your window via adb command
To enable USB try *#*#717717#*#* and it'll not connect as regular USB but visible under debugging mode.
type the same command on your phone it will [I]disable[/I] USB and once disabled - now it will appear in your my computer and visible as USB drive.

How to install Custom ROM CM 12.1 Lollipop 5.1.1 with Phillz Recovery and Root i9192

Hi, everyone I have recently did Custom ROM CM 12.1 Lollipop 5.1.1 on my Samsung Galaxy S4 Mini I9192. So for complete steps how to do it, Follow the Steps -
Strictly for I9192 Devices
Be noticed that it will void your warranty and your device may get brick during process. Also keep your battery fully charged before doing anything. I am just showing you things to do, in any odd situation YOU ARE RESPONSIBLE for damage.
For all the steps below use genuine USB cable comes with your device.
Start By Installing Phillz Recovery on your device. Here it is how
Download philz_touch_6.48.4-serranodsub_AndroidTunado.tar and Odin
When your phone is full charged, turn it off.
Enter Download Mode by pressing HOME + VOLUME DOWN + POWER KEY.
When download screen will appear open Odin and connect your phone to computer with USB Cable.
You will see your device detected as "COM:*". In Odin, do not change any checkbox settings and click PDA or AP (whatever available) and choose Phillz recovery "philz_touch_6.48.4-serranodsub_AndroidTunado.tar" file.
After choosing file, click Start Button to begin downloading in phone.
Your phone will reboot automatically and Phillz Recovery willl be succesfully installed.
So we are done with custom recovery. Next step is to install CM 12.1 . Again charge your battery if you lose any during Phillz Recovery. For download CM 12.1 and Gapps follow this post - http://forum.xda-developers.com/galaxy-s4-mini/development/rom-cyanogenmod-12-0-s4-mini-duos-gt-t2950526 (Big thanks to @k2wl).
After downloading, paste both .zip files to SDCARD. I recommend to paste both in internal and external memory in case.
Before installing ROM must do a backup of your device, install Nandroid or Titanium Backup from Google Play and get a full backup of your system and data. You need almost 4GB of space in external SDCARD to do so. Don't miss the backup as it will be only way to get you back on working phone if any failure occur. (Copy on computer as well to get secured)
So we are ready to install CM 12.1 yay! (Unlpug USB Cable if connected)
Boot your device into Recovery Mode by pressing HOME + VOLUME UP + LOCK BUTTON
From there wipe the system and clear cache: “wipe data factory reset”, “wipe cache partition” and “wipe dalvick cache”.
From main menu of recovery select “install zip from SD card” and “choose zip from SD card”.
Pick the cm-12.1-20XXXXXX-UNOFFICIAL-serranodsdd.zip file from SDCARD and install it.
When completed, DON'T EXIT/REBOOT, press again install zip from SD Card and choose gapps zip and install it.
When done Reboot your device.
There it come cynogenmod icon on bootup of your OS. Congrats CM 12.1 is installed. You can go to setttings and see version 5.1.1 of android working!
Don't forget to follow changelog of ROM for new nightly infos: http://www.cmxlog.com/12.1/serrano3gxx/#next_build
So follow rest if you want SuperUser in your device. Please note if you don't want superuser and yet Root access you have inbuilt in ROM at Settings >Developer Options > Root. Only follow below if you want SuperUser Application to have control over root access.
Download SuperSU-v2.46.zip file (from attachments) and put in your SD Card.
Again bootup in recovery mode HOME + VOLUME UP + LOCK
Choose "Install Zip from SD Card" and choose SuperSU-v2.46.zip
Install the package
When done reboot the device and you have SuperUser installed
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Enjoy CM 12.1 with phillz recovery and ROOTED. Keep in mind its just a tutorial. I take no responsibility of ROM or softwares attached. For your info, everything went perfect for me on my I9192. Let me know how your experience went!
Special Thanks to
@k2wl
and everyone who contributed in zip files.
hi, thanks for the post.
even for me, everything went perfect with the installation.
any further updates with your user experience, so far? hows the battery backup ?
ROM Performance as CM12.1 Nightly 3 July
ROM is almost stable and you may not have any trouble with general usage. Calling, Messaging, Wifi, Bluetooth, Radio almost everything is working. Camera quality is same as on stock and with same upto Full HD Recording. UI is more faster (thanks to no bloatware) and new settings for many new lollipop features and developer options. Battery life is same as stock (Falls to 20% after 3h 52min Screen Uptime with moderate usage with games and music playback). I haven't find any difference in battery yet using for 10 days. What I find is needed to improve or buggy are following
Random Force Closes - Few Apps (not all) get closed automatically. I often use a music player (debug version as I am developing it) which automatically closes after some time. (Maybe force close only for debug or non play-store apps, not sure, let me know about your experience) (Seems solved in newer update)
Games are not as fast as Stock Samsung - Heavy games like Asphalt 8 loses frames which is not with stock ROM. Sometimes Clash of Clans too behave a little laggy (once in hundred times).
Earpiece Speaker - I don't know if their is problem in my network provider or phone but 1 in 10 calls I can't hear anything what other person is speaking while connecting headphones give response and normal sound of caller. Tell me if it's same with you or I got problem at connection ?!?!?! Really annoying. (Most probably working 100% in new update as told by @roshanu)
Issues are being detected by @k2wl and improvement is going on everyday. You can upgrade to newer ROM when any comes out.
This post may get outdated anytime when ROM will be improved. To know what are changes in new nightlies, follow ROM Download Link > Changelog
Tell me what are new issues or if any old issues get resolved. Thanks everyone
Thanks to @roshanu for reminding of this post.
I am on July 10 version, installed using CWM recovery. Been two days now. Pretty basic use: no gaming no music.
ROM is stable so far, no force closes.
+1 on the light sensor.
Haven't had any problem with the earpiece speaker.
It seems root access was getting disabled on reboot, not sure. Also there was no SU app after the installation.
So I enabled the root for apps and adb through developer options, then installed the SU app through Play. Working fine now.
Will update new findings, if any...
Do you know if 4G LTE can be enabled on our phone i9192, or even future possibility ??
roshanu said:
I am on July 10 version, installed using CWM recovery. Been two days now. Pretty basic use: no gaming no music.
ROM is stable so far, no force closes.
+1 on the light sensor.
Haven't had any problem with the earpiece speaker.
It seems root access was getting disabled on reboot, not sure. Also there was no SU app after the installation.
So I enabled the root for apps and adb through developer options, then installed the SU app through Play. Working fine now.
Will update new findings, if any...
Do you know if 4G LTE can be enabled on our phone i9192, or even future possibility ??
Click to expand...
Click to collapse
It's good that developers are working on ROM and issues are solved pretty fast. For SU app you have to flash the SU zip file (in attachments) in download mode (by pressing [Volume Down] + [Home] + [Lock]). And sadly 4G LTE depends on chipset and hardware, not on software, so it can never be more than HSPA+ in any update. Do post any issues or any new improvement, it may help developers

All Z1 bugs

Hi All,
I have bought about 20 Z1 devices from my company (customers returned and Service Dept. cannot fix them)
I open all of them (LCD, Battery, Mainboard) then play LEGO game
After that, half of them can work Only some have problem like:
- SIM not work
- WiFi not work
- Fingerprint not work
- Home not work
- LCD have some yellow area
After working with them and having a look at all topics in this sub, I make a note about some common ZUK Z1 bugs that may help anyone have same issue with me
1. Battery issue
- Phone work normally but sometimes auto reboot
- Phone show incorrect % battery
It's time to think about replacing a new one, I have bought from China with about 7$ (including ship fee to Vietnam)
You can buy battery like origin or D.Seven name like me
2. Fingerprint/Home key
- If home key cannot work then your key may be dead
- If home key still work, only fingerprint not work, update below file via TWRP (I already test on 7.x, with stock ROM, I have finger, but update to Nuclear 7.x, it dissapeared then I update 7x below file and it's OK)
-- Android 6.x: https://www.androidfilehost.com/?fid=24533103863141329 (https://forum.xda-developers.com/zuk-z1/development/mod-restored-fingerprint-touch-t3262388)
-- Android 7.x: https://www.androidfilehost.com/?fid=745425885120705241 (https://forum.xda-developers.com/zuk-z1/help/fingerprint-menu-disappeared-t3411565)
3. WiFi/Bluetooth
If you cannot turn on WiFi/Bluetooth (WiFi MAC address starts with 02:00:00:00:00:00) then they can be dead
I've read a topic about this but I forgot link
4. Bootloop
- I have 2 devices with bootloop issue
- I use QFIL to flash China ROM then it can pass bootloop (https://www.androidfilehost.com/?fid=24052804347826528)
- Dev. option of this ROM does not have Update Cyanogen recovery option so I cannot flash TWRP via flash then I use QFIL to flash
- After that I can flash cm-13.0-20160416-NIGHTLY-ham.zip (6.x) but flash CM14 or higher will have bootloop issue again
- You can follow this link to download flash tool, driver, guide changing Chinese language to English,... http://www.tech-and-dev.com/2016/06...ing-to-marshmallow-zui-lenovo-zuk-z1.html?m=1
Update:
- Both above device can update to 7 with ZUI 2.5 https://www.androidfilehost.com/?fid=457095661767156988
- One of them can flash NucleaRom-V2.1.5-OFFICIAL[7.1.2]-ham-20170716-2114 https://www.androidfilehost.com/?fid=889764386195916500 (this is one of the best ROM that I've known
5. Flash NucleaROM 7x, lost accelerometer and fingerprint (use stock ROM, both sensors work normally but update to NucleaROM 7.x will lost both of them)
Up to 6.x then 7.x
Another case
- Flash China ROM first by QFIL: https://www.androidfilehost.com/?fid=24052804347826528
- Flash TWRP
- Flash ZUI 2.5 by TWRP: https://www.androidfilehost.com/?fid=457095661767156988
- Flash NucleaROM 7.x (lastest is 2.1.9 https://androidfilehost.com/?fid=961840155545588772)
6. FRP pass (Require last Google account after reset/flash)
Too many steps but can pass (if you cannot turn dev. options, you can pass this step)
https://m.youtube.com/watch?v=3tMoleAMkoU&t=182s
I still have issues that need to find. Pls help if you already in that case
Not detect SIM (I also heard this issue on XDA)
Update: One device can detect SIM2 after flash 7.1.2 but after few hour it cannot??? so strange)
Cannot flash CM14 or higher ROM with some devices
Update: 1/2 devices with bootloop can flash higher ROM by flash ZUI 2.5 first
Useful links:
- Stock ROM flash by QFIL (Lenovo ZUK Z1 team send to Vietnam for testing and I'm responsible for this task): https://drive.google.com/open?id=0B6VA9wVCZsgXWnZmYVN6c3RHWXM
- Lenovo Zuk Z1 ROMs, Kernels, Tools, Guides: https://forum.xda-developers.com/zuk-z1/general/index-lenovo-zuk-z1-t3384098
- Android Device Partitions and Basic Working: https://forum.xda-developers.com/android/general/info-android-device-partitions-basic-t3586565
- ALL IN ONE tool (Drivers|Unlock|TWRP|Factory Image|Stock Recovery) Win/Linux: https://forum.xda-developers.com/zuk-z1/orig-development/tool-toolzukz1eng0-0-3-mauronofrio-t3332563
Some images about my work
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Zuk Z1 Charging troubles
Whenever I disconnect my charger after charging my phone, the phone starts getting momentarily charging without even connecting the charger. Please reply and help.
Aashutosh1 said:
Whenever I disconnect my charger after charging my phone, the phone starts getting momentarily charging without even connecting the charger. Please reply and help.
Click to expand...
Click to collapse
You use stock ROM?
Did you try reset factory?
Currently using Lineage 14.1 (Nightlies). But the problem was there when I was using stock rom. Problem is still not solved after flashing lineage 14.1
Aashutosh1 said:
Currently using Lineage 14.1 (Nightlies). But the problem was there when I was using stock rom. Problem is still not solved after flashing lineage 14.1
Click to expand...
Click to collapse
What is your stock ROM version?
Below is stock ROM that Lenovo ZUK Z1 team send to Vietnam for testing and using for mass production (I'm responsible for testing)
You can try flashing it with QFIL and hope that your issue will be fixed (if not, I'm afraid it's HW issue)
Google Drive link: https://drive.google.com/open?id=0B6VA9wVCZsgXWnZmYVN6c3RHWXM
Flash NucleaROM 7x, lost accelerometer and fingerprint
use stock ROM, both sensors work normally but update to NucleaROM 7.x will lost both of them
Stock ROM
Flash from 5.x to 7.x
Solution
- Flash China ROM first by QFIL: https://www.androidfilehost.com/?fid=24052804347826528
- Flash TWRP
- Flash ZUI 2.5 by TWRP: https://www.androidfilehost.com/?fid=457095661767156988
- Flash NucleaROM 7.x (lastest is 2.1.9 https://androidfilehost.com/?fid=961840155545588772)
My home button works when i press it (not tap) but can't detect fingerprint. Suggest a solution. It started after flashing RR rom 2 months ago.
Dhruvshelke588 said:
My home button works when i press it (not tap) but can't detect fingerprint. Suggest a solution. It started after flashing RR rom 2 months ago.
Click to expand...
Click to collapse
What is RR mean?
You can flash 6.x or 7.x firmware in item 2 above (depend on which version that you are using) then you can have fingerprint back
ducnv said:
What is RR mean?
You can flash 6.x or 7.x firmware in item 2 above (depend on which version that you are using) then you can have fingerprint back
Click to expand...
Click to collapse
I did flashed that but it didn't work. RR means resurrection remix rom.
Dhruvshelke588 said:
I did flashed that but it didn't work. RR means resurrection remix rom.
Click to expand...
Click to collapse
You can try flash stock ROM first by QFIL https://drive.google.com/open?id=0B6VA9wVCZsgXWnZmYVN6c3RHWXM to check if your issue is OK or not
After that:
- Flash TWRP
- Flash 6.x ROM
- Flash 7.x ROM
I did the above steps.
In stock rom when I chose fingerprint it automatically completes it and when I try to do it second time it just keeps on vibrating till I switched it off.
Then I flashed cm13 rom (6.0.1) and fingerprint option is not present. Now I flashed nuclearom (7.1.2) and again no option.
Dhruvshelke588 said:
I did the above steps.
In stock rom when I chose fingerprint it automatically completes it and when I try to do it second time it just keeps on vibrating till I switched it off.
Then I flashed cm13 rom (6.0.1) and fingerprint option is not present. Now I flashed nuclearom (7.1.2) and again no option.
Click to expand...
Click to collapse
I think your fingerprint is error, I have some case same as yours
ducnv said:
I think your fingerprint is error, I have some case same as yours
Click to expand...
Click to collapse
Tried all your methods but no change. Maybe this is just a hardware problem.
My ZUK Z1 is stuck in endless bootloop and no recovery mode
ducnv said:
Hi All,
I have bought about 20 Z1 devices from my company (customers returned and Service Dept. cannot fix them)
I open all of them (LCD, Battery, Mainboard) then play LEGO game
After that, half of them can work Only some have problem like:
- SIM not work
- WiFi not work
- Fingerprint not work
- Home not work
- LCD have some yellow area
After working with them and having a look at all topics in this sub, I make a note about some common ZUK Z1 bugs that may help anyone have same issue with me
1. Battery issue
- Phone work normally but sometimes auto reboot
- Phone show incorrect % battery
It's time to think about replacing a new one, I have bought from China with about 7$ (including ship fee to Vietnam)
You can buy battery like origin or D.Seven name like me
2. Fingerprint/Home key
- If home key cannot work then your key may be dead
- If home key still work, only fingerprint not work, update below file via TWRP (I already test on 7.x, with stock ROM, I have finger, but update to Nuclear 7.x, it dissapeared then I update 7x below file and it's OK)
-- Android 6.x: https://www.androidfilehost.com/?fid=24533103863141329 (https://forum.xda-developers.com/zuk-z1/development/mod-restored-fingerprint-touch-t3262388)
-- Android 7.x: https://www.androidfilehost.com/?fid=745425885120705241 (https://forum.xda-developers.com/zuk-z1/help/fingerprint-menu-disappeared-t3411565)
3. WiFi/Bluetooth
If you cannot turn on WiFi/Bluetooth (WiFi MAC address starts with 02:00:00:00:00:00) then they can be dead
I've read a topic about this but I forgot link
4. Bootloop
- I have 2 devices with bootloop issue
- I use QFIL to flash China ROM then it can pass bootloop (https://www.androidfilehost.com/?fid=24052804347826528)
- Dev. option of this ROM does not have Update Cyanogen recovery option so I cannot flash TWRP via flash then I use QFIL to flash
- After that I can flash cm-13.0-20160416-NIGHTLY-ham.zip (6.x) but flash CM14 or higher will have bootloop issue again
- You can follow this link to download flash tool, driver, guide changing Chinese language to English,... http://www.tech-and-dev.com/2016/06...ing-to-marshmallow-zui-lenovo-zuk-z1.html?m=1
Update:
- Both above device can update to 7 with ZUI 2.5 https://www.androidfilehost.com/?fid=457095661767156988
- One of them can flash NucleaRom-V2.1.5-OFFICIAL[7.1.2]-ham-20170716-2114 https://www.androidfilehost.com/?fid=889764386195916500 (this is one of the best ROM that I've known
5. Flash NucleaROM 7x, lost accelerometer and fingerprint (use stock ROM, both sensors work normally but update to NucleaROM 7.x will lost both of them)
Up to 6.x then 7.x
Another case
- Flash China ROM first by QFIL: https://www.androidfilehost.com/?fid=24052804347826528
- Flash TWRP
- Flash ZUI 2.5 by TWRP: https://www.androidfilehost.com/?fid=457095661767156988
- Flash NucleaROM 7.x (lastest is 2.1.9 https://androidfilehost.com/?fid=961840155545588772)
6. FRP pass (Require last Google account after reset/flash)
Too many steps but can pass (if you cannot turn dev. options, you can pass this step)
https://m.youtube.com/watch?v=3tMoleAMkoU&t=182s
I still have issues that need to find. Pls help if you already in that case
Not detect SIM (I also heard this issue on XDA)
Update: One device can detect SIM2 after flash 7.1.2 but after few hour it cannot??? so strange)
Cannot flash CM14 or higher ROM with some devices
Update: 1/2 devices with bootloop can flash higher ROM by flash ZUI 2.5 first
Useful links:
- Stock ROM flash by QFIL (Lenovo ZUK Z1 team send to Vietnam for testing and I'm responsible for this task): https://drive.google.com/open?id=0B6VA9wVCZsgXWnZmYVN6c3RHWXM
- Lenovo Zuk Z1 ROMs, Kernels, Tools, Guides: https://forum.xda-developers.com/zuk-z1/general/index-lenovo-zuk-z1-t3384098
- Android Device Partitions and Basic Working: https://forum.xda-developers.com/android/general/info-android-device-partitions-basic-t3586565
- ALL IN ONE tool (Drivers|Unlock|TWRP|Factory Image|Stock Recovery) Win/Linux: https://forum.xda-developers.com/zuk-z1/orig-development/tool-toolzukz1eng0-0-3-mauronofrio-t3332563
Some images about my work
Click to expand...
Click to collapse
I have a ZUK Z1. I had been using it since march 2017 on nuclear rom with Radioactive kernel. ONe day suddenly it entered a bootloop. It shows the ZUK and android logo, Radioactive kernel logo and then restarts. I can't power off the phone, I cant go to recovery mode or the fastboot mode. Please help me!
parallax_909 said:
I have a ZUK Z1. I had been using it since march 2017 on nuclear rom with Radioactive kernel. ONe day suddenly it entered a bootloop. It shows the ZUK and android logo, Radioactive kernel logo and then restarts. I can't power off the phone, I cant go to recovery mode or the fastboot mode. Please help me!
Click to expand...
Click to collapse
Have a look at the existing threats https://forum.xda-developers.com/zuk-z1/help/zuk-z1-hard-bricked-t3669863/page with possible solutions. There are others on Q&A section too:good:
Same problem even after trying all the steps.
strongst said:
Have a look at the existing threats https://forum.xda-developers.com/zuk-z1/help/zuk-z1-hard-bricked-t3669863/page with possible solutions. There are others on Q&A section too:good:
Click to expand...
Click to collapse
Hey there. I have tried all the threads with similar problems posted on them. None of the solutions seems to work for me. Still in Bootloop. If i somehow enter recover or manage to boot into fastboot, even that reboots in a few seconds. Please help .

It is possible to install stock rom using TWRP/fastboot on WAS-LX1?

REALLY BAD ENGLISH
So im totall newbie,and i had some issues with snapchat,so i unrooted my phone,and then clear snapchat cache,and login again - it worked. But i had to install Magisk again usign TWRP,but i had only old magisk update on pc (my pc didnt have internet connection this time,some problems with ISP) so i used my friend phone as a internet provider.Then i flash magisk to phone,everything works,but youtube videos have error,i dont hear any sounds,and playing gallery videos makes gallery crash,camera app close and open itself after launch. So i decided to make hardreset. By a mistake i launch TWRP,but i tought that wipe is nearly same. I forgot to uncheck somethings,and then i click "wipe" button. After i launched my phone, i didnt see setup of new clear system,but a cloack,my mobile network operator name, and wifi,battery status - just a normal "login" screen.
I unlocked screen and i see black color - just whole screen was black. I restarted phone, and same thing happened. I decided to flash stock rom,and here we are - where problems started to show up.
1.Questions Where i can download stock rom for Huawei P10 lite Dual Sim Poland WAS-LX1,and how to install it using TWRP?
Do i need to use stock recovery if i want stock rom? Becasue When i will remove TWRP and add stock recovery,i cant use adb - which is probably very usefull huh?
I would ask about much more but i just have to go to job,i will back soon.
Please help!
In short, the answer is YES!
But in practice, I personally do NOT recommend it because I tested it and had problems during installation.
You need to know what is the exact model (WAS-LX1 or WAS-LX1A or other) and region on your phone!
If you want to try here is how:
- You need Twrp P10 Lite by KingOfMezi : https://mega.nz/#!WFYWEJjJ!HZGsY4WKdbYGr6M8VEeztDCzQe6UN020ro6f_g6V8FY
- Install TWRP
- Download Stock ROM based on your region and phone model: https://forum.xda-developers.com/p1...pilation-firmware-flasheables-huawei-t3736754
- Go to TWRP -> Wipe -> Advanced Wipe and check:
-> Davilk / Art Cache
->Cache
->Data
->Internal Storage
->System
->Vendor
->Product
- Wipe selected partitions
- Go to Install menu and install your ZIP
I have received these problems several times:
-> Keep in mind that you will most likely get errors during installation (99.99% ;p)
-> First boot may NOT happed or last forever
-> Second boot may says "Data partition coruped" and go to eRecovery, Low Level Format or similar error, etc.
-> Third or Fourth boot may be successful
So I DO NOT recommend flashing these Stok ROMs!
Here is what I recommend:
Your phone is Dual SIM WAS-LX1, region C432, right?
Download this: http://androidhost.ru/JT
In the root directory of your SD Card create a folder "dload"
Put the file UPDATE.APP and folder WAS-L21_hw_eu (contains the file update_WAS-L21_hw_eu.app) inside your dload folder
Must be:
"\dload\UPDATE.APP"
and
"\dload\WAS-L21_hw_eu\update_WAS-L21_hw_eu.app"
- Turn OFF you phone
- Put the SDcard in your phone
- Press and hold all 3 buttons Vol+ and Vol- and Power until you see EMUI update menu
- After successful upgrade you will have STOCK Rom WAS-LX1C432B182
Warning:
Bootloader will be LOCKED (you need to unlock it again if you need)
you will have STOCK RECOVERY (if you want TWRP you have to flash it again)
It's very very easy to do it
I have a question - i use my sister phone to put files from your link into sdcard,but wheen i move update.app to dload folder - it simply disapear
and does it work if i have twrp,becasue many people say that if u dont have stock recovery your method wont work.
Thanks for any replies!
Perhaps something is wrong! I don't know why these files disappear, try another SDcard. During installation TWRP will be replaced with Stock recovery and your Bootloader will be locked.
Videos:
https://www.youtube.com/watch?v=AokzzNYTFnE
or
https://www.youtube.com/watch?v=0vDgDXePAR4
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It worked. Thank You!
problems
Hello . I have a problem with my WAS-LX1. I unlocked the bootloader. I installed the TWRP red version from KingOfMezi. I wipe all the data exactly as in the video. I flashed Elemental V2. I chose the LX1 smell and the rest just like in the movie. I get the OK message. After my restart my phone restarts again, and after the second restart I go into android, I choose the wifi network and after about 1 minute it restarts again. After another minute restart. And so to the end. Right now I have the original WAS-LX1C432B204 software on it. can somebody help me please. :crying:
armaghejohn said:
Hello . I have a problem with my WAS-LX1. I unlocked the bootloader. I installed the TWRP red version from KingOfMezi. I wipe all the data exactly as in the video. I flashed Elemental V2. I chose the LX1 smell and the rest just like in the movie. I get the OK message. After my restart my phone restarts again, and after the second restart I go into android, I choose the wifi network and after about 1 minute it restarts again. After another minute restart. And so to the end. Right now I have the original WAS-LX1C432B204 software on it. can somebody help me please. :crying:
Click to expand...
Click to collapse
cant tell if there is something like "bump" on this site,but i will BUMP just for you. Im real newbie,so i wont help you.you should create new thread on this forum i think. Good Luck!

Categories

Resources