Database Users

[GUIDE] How to root your ZTE Android device

This method doesn't rely on any root exploits & will work with any Android version on the ZTE Blade (and all variants). It should work on any phone with an unlocked bootloader (all zte android devices are sold with unlocked bootloaders).
Software needed:
adb (windows/linux/mac versions available as part of the android sdk - http://developer.android.com/sdk/index.html You will find adb in the tools directory.)
fastboot (windows/linux/mac versions available here: http://koushikdutta.blurryfox.com/G1/ )
windows drivers for the phone (if you use windows: http://support.zte.com.cn/support/news/NewsDetail.aspx?newsId=1000442 )
ClockworkMod (http://clockworkmod.com/rommanager - download zte blade clockwork recovery image)
SuperUser ( http://androidsu.com/superuser/ Download Eclair/Froyo/Gingerbread/Honeycomb (2.1 – 3.2) version) - Alternatively you can use any rooted custom rom
If your phone is running Android 2.1, then it is probably a 'gen1' device, search for "Mr Pigfish" on Android market if you're unsure. Gen1 blades will need an older version of clockworkmod, 3.0.1.4 - http://download.clockworkmod.com/recoveries/recovery-clockwork-3.0.1.4-blade.img
Method:
Download/install adb & fastboot. Install drivers for the phone if needed (on Windows).
Plug your phone into your pc using the usb cable, mount usb storage, then copy the Superuser or custom rom zip onto it & unmount usb storage.
Make sure that usb debugging is enabled on your phone, there should be an icon in the status bar, you can enable it in settings (settings -> applications -> development -> usb debugging).
Open a command terminal window & change to the directory that you downloaded recovery-clockwork-[version]-blade.img to. Type...
Code:
adb reboot bootloader
This will make the phone reboot, wait for the android logo (or custom splash screen) on the phone then type...
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-blade.img
fastboot reboot
You have just installed ClockworkMod recovery. Your phone will reboot back into android, when it has done that turn it off, then turn it on with the vol- button held to start clockworkmod. Use vol+/- to navigate, home button to select an option, back button to go back. You should create a backup now before you flash anything, when that backup is complete use 'install zip from sdcard' to either install superuser to root your stock rom, or install a custom rom. If you're installing a custom rom then you'll need to wipe data/factory reset too (you will lose all data). reboot, you're done.

I'm not sure if this is the right section for the thread, it'd probably be better in blade general. I forgot that newbies can't reply here.
Anyway, for those that can reply, can you suggest any improvements? I'll find links for adb, fastboot & windows drivers later.

Everything is clear except where to find adb and fastboot for noob users... (like me).
I did a little search and found out that adb is installed with the Android SDK... so, i installed it, installed the android platform-tools package, the usb driver but i am stuck with fastboot...
There is no fastboot in the Android SDK installation directory... and i can't find it on the web... so, i can't install clockworkmod recovery and i'm stuck...
Can u help me plz ?

Yeah, as I said, I'm still looking for links. you get fastboot when you compile android from source, but that is a bit of a long & complicated way.
Here is a pre-compiled version of fastboot for windows, linux & macos http://koushikdutta.blurryfox.com/G1/
adb works without the sdk too, I'll see if I can find links for that.
The windows driver is on zte's site somewhere, but that's a pain to find anything on. I'm not sure if the Google driver works. I don't even run windows, so if anybody can help write that part...

Probably best to for XP use the exe driver installer (Thats in the pcsuite.iso in the official 2.3.5 rom)
Windows 7 just works (gets drivers from windows update).
Does the superboot apk deal with changing default.prop (to allow adb remount etc).
If not could do that (use the same thing the CM7 universal converter uses to split the boot.img).

unrandomsam said:
Probably best to for XP use the exe driver installer (Thats in the pcsuite.iso in the official 2.3.5 rom)
Windows 7 just works (gets drivers from windows update).
Click to expand...
Click to collapse
Not everybody is running the official 2.3.5 rom, it's probably a tiny fraction of users. 2.1 roms don't have the driver iso. I found the drivers & updated the first post. The drivers on the phone should work fine, if you are running an unmodified 2.2 or 2.3 stock rom, just plug the phone in & it should mount a driver cd image over usb to install the drivers.
Does the superboot apk deal with changing default.prop (to allow adb remount etc).
Click to expand...
Click to collapse
It's superuser, it's a clockworkmod zip file & no, it doesn't change default.prop. It installs superuser & su.
If not could do that (use the same thing the CM7 universal converter uses to split the boot.img).
Click to expand...
Click to collapse
Tell ChainsDD, it isn't my software, I just wrote a quick idiot's guide.

Hi wbaw....
nice to see you posting helpful stuff here....
Can I ask what is perhaps a silly question, about the rooting process for ZTE devices, without relying on root exploits?
How is this different, or better, than using the z4Root modified by kallt_kaffe App, which I have linked (MoDaCo).
Is it just the use of the exploit, or is there another reason?
I have used it on my OSF/Blade, and never lost root or had any other problem, AFAIK.
Also, I see you are not showing your previous GEN1/Gen2 all-in-one TPT for GSF any more...is it available any more for ppl who may want to try it?
Thanks in advance

The exploit that z4root uses doesn't work on newer versions of Android (2.2.2 & above), ZTE are selling some phones with these newer versions of Android.
If z4root works for you, then that's fine, there's nothing wrong with it. It just doesn't work for everybody.
If you are using a version of Android that z4root (or other root exploits) do work on, then you should update Android asap. Otherwise a malicious app could use the same exploit to take over your phone. Root exploits themselves aren't bad (as long as you're doing it to your own device, or with permission of the owner) - the fact that root exploits work is bad & a sign that you need to update the software asap.
GSF has it's own thread. You can get the same effect by using the gen1 to gen2 tpt & then installing gsf. It is buggy & old, I think there is a nasty remote root exploit out there for 2.3.4 too. Just use CyanogenMod, it's much better, less buggy, more secure, they keep up with the latest Android fixes & it has more customisation options.

Thank you for the explanation...I will go ahead and do what you have advised.
I am just continuing to use good old Swedish Spring RLS5, which I think was kallt_kaffe (Cold Coffee) also......GEN 2 thanks to your Gen 1>Gen 2 TPT.
I think t is 2.2.
If I want to proceed to permanently root as you describe, should I use z4root to unroot first?
I will probably move to CyanogenMod, so I should use your exploit-free root instructions first.
BTW, I will be sad to move on from SS, as it does seem to be as near a perfect fit as I have found for the Blade.
I did put on GSF ,some time ago, and to be very honest, I just lasted a night with it, then restored the SS Nandroid.......it didn't feel at all as satisfactory a UI experience as SS.
Perhaps it was me, you know, you get used to an old pair of sneakers, etc.
As you said, it was and is always beta...it was an early version!!!
Thanks again, and keep up the good work in these calm(er) waters

Custom roms are already rooted. You don't need to root a custom rom, you just install it with clockworkmod.
If you already have a custom rom installed then you don't need any of this guide, you've already got clockworkmod. All this guide does is tell you how to install clockworkmod.
This is for people with phones on a stock rom who want to be able to install clockworkmod to root their stock rom or install a custom rom.
You shouldn't still be using Android 2.2 because the root exploit in z4root works on it, therefore other more malicious apps could use a similar exploit without asking you first.

Hi..... does this work on any Android phone?
I have in mind the new Samsung W i 8150.
Getting one for Xmas.... AFAIK
Sent from my ZTE-BLADE using Tapatalk

It should work on some other android phones, but they'll need adb & an unlocked bootloader, so it wont work with every phone. It should work on any ZTE android phone or tablet (except maybe the tureis?).

Hi!I have a Zte Blade with 2.3.5 OS. I tried to root my phone using this tutorial, but when i write : "fastboot flash recovery recovery-clockwork-5.0.2.0-blade.img" in Comand Prompt program, i get this message : "error: cannot load : recovery-clockwork-5.0.2.0-blade.img".
Can anyone help me, please?
Thanks!

stanangel said:
Hi!I have a Zte Blade with 2.3.5 OS. I tried to root my phone using this tutorial, but when i write : "fastboot flash recovery recovery-clockwork-5.0.2.0-blade.img" in Comand Prompt program, i get this message : "error: cannot load : recovery-clockwork-5.0.2.0-blade.img".
Can anyone help me, please?
Thanks!
Click to expand...
Click to collapse
You need to download clockwork recovery & be in the directory that you downloaded it to, to run that command.

Thank you!It works. Now, can I put Cyanogenmod 7.1 on 2.3.5 OS with this root and clocworckmod ?

stanangel said:
Thank you!It works. Now, can I put Cyanogenmod 7.1 on 2.3.5 OS with this root and clocworckmod ?
Click to expand...
Click to collapse
You can put clockworkmod on, but cm7 might not work without a bit of fixing, it is designed for 2.2 blades, zte's 2.3.5 has a different radio firmware.
Is this a 2.3.5 blade? where did you buy it?

Well, first time i had 2.1 update-1.After that I updated the version to 2.2 Boygues (or something like this) and then i found on this forum the official image.bin (2.3.5) and I decided to update.But now, i want to try CM.

stanangel said:
Well, first time i had 2.1 update-1.After that I updated the version to 2.2 Boygues (or something like this) and then i found on this forum the official image.bin (2.3.5) and I decided to update.But now, i want to try CM.
Click to expand...
Click to collapse
I see, you'll need to use another image.bin to go back to 'gen2' - the zte froyo radio firmware. Otherwise you wont get any phone signal, 3g or gps on CM7 because the 2.3.5 image.bin that you installed contained new radio firmware.
You don't need to root it first, you can install clockworkmod with a gen2 radio firmware using a custom image.bin like this one that http://www.mediafire.com/?jb4crw3em2m4r4x Amphoras made.
The 2.3.5 image.bin contained another new version of the radio firmware, which isn't compatible with CM7.

Uhuuu, it works.Thank you a lot! CM7.1 is awsome.This forum is awsome.

Hey I cant acess adb after doing adb reboot bootloader. When I come to the chinese letter I cant do nothing. So i cant fastboot flash recovery recovery-xxx.img.
What im i doing wrong?

Need Help, can't save files to root dir, can't save rom

So I got this Tablet a few days ago and wanted to get root. It came with the 3.2 update already installed so I read around and saw I needed to downgrade the os, root, flash recovery, then flash a rom via recovery.
I plan to install this rom:
http://forum.xda-developers.com/showthread.php?t=1290318
It is basically stock acer 3.2 with root. Which is all I really want.
I followed method 2 here:
http://forum.xda-developers.com/showthread.php?t=1276227
After booting and installing the unstable version to be able to get root, then I did the adb push for cwm and itsmagic. Wasn't sure what to do after this so I rebooted. (I tried downloading the acer recovery installer but my market would not let me type anything in with all the force closes)
So after reboot I am unable to get adb to show it as a listed device and everytime I try to copy the rom over I need I get an error "Cannot copy *filename* The device has either stopped responding or has been disconnected"
In frustration I figured I didn't get cwm installed properly so I downloaded the apk from the web and installed it via dropbox. It let me apply it and actually boot into recovery.
I powered off and tried getting back in but my pc still fails to see the device listed in adb or save files to it via the basic windows file explorer.
I'm currently letting the update install itself (I flashed back the original recovery via acer recovery installer) don't know if this will fix it.
If anyone can help, it would be much appreciated.
Update:
It upgraded me to 3.1 but I still can't save anything to my tab (atleast the fc's are gone). It doesn't list anything on my tab just shows 0 files. Not sure how to get this fixed.
Update:
I did a factory reset. Now it detects it and I'm able to save the rom to it. I did the root, and flashed cwm thru acer recovery installer. (avoiding adb entirely). However when I'm in there now it says "E:Can’t mount /sdcard". Read some folks are throwing it on a usb drive and flashing it that way.(BTW I put the rom zip on the root file directory, not on the external SD). Will update if it works or not.
*RESOLVED*
Got it working. It installed off the USB thumb drive just fine. Was able to install the 3.2 root Rom mentioned earlier. Everything is working as it should. Able to read and write to and from the device now. Showing superuser in my apps. Now to start removing the crap Acer put on there
This is just in case anyone runs into the same problem. Took a few hrs but its working nice
Basically I suggest this if you wish to just install the the 3.2 stock rom via cwm
1.) Since the unstable flash doesn't clear your data, download and install everything you will need first. ex: Acer Recovery Installer, Iconia Root. Put the rom on the root drive and/or a thumb drive.
2) Flash the downgrade.
3) Run the Iconia Root tool.
4) Run the Acer recovery installer (since you'll have root now) and reboot to recovery
5) Flash the rom. If it doesn't detect it try it on a usb thumb drive. Done

I always put my ROMS on an external microSD. That is the only thing I use my SD card for, and as far as I can tell is always the recommended place to store your ROMS for updating. In the root of the microSD card.
Glad to hear you got it working though.

[Q] Stuck in TWRP, Tried everything i could find about it!

So this is my story,
I had a stock rom lg g2 d802 phone working, but didnt had a micro sim yet so i decided to flash a nice rom (http://forum.xda-developers.com/showthread.php?t=2505682). So i followed everythin as described, but then... when i finishd flashing the rom i noticed that nothing has changed in the lg. it was still the same with everything on it as before.
So my stupid brains decided to make a Wipe! in TWRP (the one where you need to type yes to continue) and after that reflash the rom i wanted. So i did just that, resulting >>> a clean sweap on my phone, everything was gone, even the rom i put on the sd card.
Not that big a deal, i just use ADB and push it on my phone, (did just that) and in TWRP i installed the rom, everything goes as supposed to. But when the reboot promt comes and i reboot to System, im getting back to TWRP.
I tried to flash the following
1. A backup i made of the phone (no result)
2. flash rayglobe (http://forum.xda-developers.com/showthread.php?t=2493209, no result)
3. flash the previous rom (no result)
at step 2 tho (rayglobe) when i flash it, i get the installer and work my way trough it, when i reboot my phone it gets back to TWRP (offcourse) but then i notice changes, like i put my ray.zip in /sdcard/ and its gone (cant see it) but i can still press the space where it was before, and it will display the pressing-animation, but wont do anything else.
i also restored my /boot folder with the one in /boot (phone side) thought it might help. no result
Then i moved on to the LG mobile support tool and put the phone in download mode (firmware update) the tool recognizes the phone but it gets stuck at step 2 (the download part) and the text in the tool isnt updated (displays chekking pc status) while in the download part. around 14 sec in from starting the upgrade in the tool. so this has no result 2.
i have tried drivers from:
google android
google sdk manager
lg android driver
lg united mobile driver
universal adb driver
with some i cant do adb and with some i can, also with some i cant do sideloader and with some i can.
but with all i cant do fastboot.
as of now i have 4 "boots" i can get into
1. recovery (TWRP)
2. download (firmware update)
3. reset factory settings
4. hardware key settings (to use buttons as phonecall helpers )
summary:
i can boot into TWRP and flash/instal/backup but with no result
what i want?????
I WANT MY STUPID BRAINS REMOVED, also i want to get back to stock or any rom that works (pref stock, got backup via TWRP) asap.
how do i manage this?
so feel free to to help me out here

going to c captain america, will be back in a while, please please please help me out

4.4.2 (KOT49H) update fails on rooted device

Received the update today but it failed to install. I'm running the stock rom KRT16S. My Nexus 10 is rooted and my recovery is TWRP 2.6.3.1. I have added nothing else to this rom except a few apps from the google play store. I wanted to try again but couldn't find where the OTA is stored. It wasn't in the /cache/fota folder. So I downloaded a flashable zip from the net. But this update file failed to install also. I've seen a few others have success installing the update. I just don't know what's preventing me from updating. I welcome your suggestions. Thanks.

Same here on my Nex5.
It seems, that some custom zips changed my stock (rooted) rom in this way that I am not able to install the 4.4.2 update.
I got similar issue on my Nex4 in the past, I could help me out by flashing full rom (rooted) deodexed, but where can I find the full rom of 4.4.2 for my Nex5 now?
Anybody can give me a clue?
Thank u very much.
Greetz from Germany.. Fred
Lexus One said:
Received the update today but it failed to install. I'm running the stock rom KRT16S. My Nexus 10 is rooted and my recovery is TWRP 2.6.3.1. I have added nothing else to this rom except a few apps from the google play store. I wanted to try again but couldn't find where the OTA is stored. It wasn't in the /cache/fota folder. So I downloaded a flashable zip from the net. But this update file failed to install also. I've seen a few others have success installing the update. I just don't know what's preventing me from updating. I welcome your suggestions. Thanks.
Click to expand...
Click to collapse

amplifier1980 said:
Same here on my Nex5.
It seems, that some custom zips changed my stock (rooted) rom in this way that I am not able to install the 4.4.2 update.
I got similar issue on my Nex4 in the past, I could help me out by flashing full rom (rooted) deodexed, but where can I find the full rom of 4.4.2 for my Nex5 now?
Anybody can give me a clue?
Thank u very much.
Greetz from Germany.. Fred
Click to expand...
Click to collapse
Hi Fred, and greetz from Ohio. I'm not aware of anything in the 4.4.2 flavor right now for the Nex10. I'm not sure about the Nex5. I think we're just going to have to wait. But I'd like to have the same thing. A lean & clean deodexed stock rooted 4.4.2 rom with a few performance tweaks. Like the old "Cleanrom" by scrosler. As for right now, did you try an ADB Sideload update to 4.4.2 using Wug's Toolkit? http://www.wugfresh.com/faqs/how-to-update-ota-not-working/

Lexus One said:
Hi Fred, and greetz from Ohio. I'm not aware of anything in the 4.4.2 flavor right now for the Nex10. I'm not sure about the Nex5. I think we're just going to have to wait. But I'd like to have the same thing. A lean & clean deodexed stock rooted 4.4.2 rom with a few performance tweaks. Like the old "Cleanrom" by scrosler. As for right now, did you try an ADB Sideload update to 4.4.2 using Wug's Toolkit?
Click to expand...
Click to collapse
Hi. Meanwhile i found a thread in nexus5 Android development area which contains both deodexed and odexed stock rooted full rom . so i just flashed odexed Version over my 4.4... Now i am on 4.4.2 finally... And still rooted..
Thank u anyway..
Greetz, fred

Lexus One said:
Received the update today but it failed to install. I'm running the stock rom KRT16S. My Nexus 10 is rooted and my recovery is TWRP 2.6.3.1. I have added nothing else to this rom except a few apps from the google play store. I wanted to try again but couldn't find where the OTA is stored. It wasn't in the /cache/fota folder. So I downloaded a flashable zip from the net. But this update file failed to install also. I've seen a few others have success installing the update. I just don't know what's preventing me from updating. I welcome your suggestions. Thanks.
Click to expand...
Click to collapse
Hi,
You can try performing a full unroot in the SuperSU app if it still doesn't work... I had to adb sideload mine to work, don't know how it works with toolkit, but you have to first set your tablet to receive it. As you are on TWRP you simply go to advanced and select adb sideload, then try using the tool, or following the instructions on it to do so .
You cannot install a OTA zip like a Custom ROM zip, they are a little bit different hehe.
Hope this helps,
~Lord
PS.: This will work for N5 too.

I somehow got the idea that rooted Nexus devices with a custom recovery could handle OTA's without trashing the recovery. I guess I expected that I would lose root. I think I'm just going to wait for someone to put together a "CleanROM" based on 4.4.2 or newer. I've been waiting for a rom like this since I bought my Nex10 anyway. I don't think I'll suffer too much running on 4.4 until then.
Thanks to those who contributed, I'll remember your suggestions. Especially if I end up waiting a long time for a 4.4.2 based Cleanrom.
Update: Thanks to Wug's toolkit. I'm now running 4.4.2..

I should ask for a sticky for this but these instruction will work EVERY TIME if you are running either custom recovery or Root.
You will need the latest adb/fastboot from google, you can either install the SDK or download any of the many smaller adb/fastboot and libs for your os
You will need STOCK 4.4/4.3/4.2 recovery depending on what version of android you are currently on. Download the factory image from here. Open the zip within the package and pull out recovery.img and rename it stockrecovery.img
Copy your custom recovery to the adb folder name it twrp.zip or short name for whatever you are using I am using twrp.
You will need the correct OTA you are seeking to apply - rename it to something short simple and obvious - for this example I will use otaupdate.zip
If you wish to root get the latest patch (I believe its up to 1.75 now) and copy it to the adb/fastboot folder.
BACKUP YOUR DEVICE FIRST AND COPY IT TO YOUR PC
If you are already Rooted:
If you are using SuperSU - go to the application options and completely unroot and reboot if needed
BACKUP YOUR DEVICE FIRST AND COPY IT TO YOUR PC
If not rooted start here:
I am assuming most of you are Windows users. Open your file explorer and open the ADB folder.
On the left hand folder where ADB is located press shift and right click the ADB folder and select "Open command window from here". This will open a command prompt window for you to run all your adb/fastboot commands from. This is the same folder where you copied your recoveries and updates to.
BACKUP YOUR DEVICE FIRST AND COPY IT TO YOUR PC
Copy your custom recovery and stock recovery to your adb folder
Copy and rename the OTA to the adb folder
Copy your root.zip patch to the /sdcard downloads folder (if you wish root)
>adb reboot bootloader
>fastboot flash recovery stockrecovery.img
>fastboot reboot-bootloader
Go into recovery and wait till dead droid appears
Press power and Volume Up at same time to go into the stock recovery menu
Using the volume buttons move and down the blue list of options and select: Apply update from ADB
You will now have orange text at the bottom of the screen - follow the instructions to side load by typing >adb sideload otaupdate.zip in your command prompt window
Wait and watch the progress, at this point you should see the ota processing steps of which there a few and will vary depending on the package. When its complete there will be a "install complete" or similar message
Reboot and let the update complete the system optimizations and go in validate your device is working and the version is what you wanted
>adb reboot bootloader
>fastboot flash twrp.zip
>fastboot reboot-recovery
Using your newly installed custom recovery you can now apply zips/root etc
Reboot as needed and update root if using older .zip to current binaries and enjoy your updated device.
And yes you only need to backup once prior to starting but many people skip that step -DON'T BE ONE OF THOSE PEOPLE.
Hopefully I've not missed a bit.
You can also use these same instructions if you're stuck in boot loop or applied a patch without first replacing stock or unrooting - just boot to bootloader using fastboot and replace recovery and apply the patches. This will usually work just fine and prevent much heart ache on your part.

finally custom rom for lg g3 d858hk

hey guys i found custom ROM for d858hk version which is here
http://bbs.gfan.com/android-7892224-1-1.html
can be translated through Google but we need someone to explain to us in details.

I might able to help, I can read Chinese
let me know if you want any explanations.
it's based on lollipop 20d
- v1.0 LED not working, and this v2.0 fixed the problem
- rooted, superSU v2.46
- once you flashed the ROM, no need to flash the ROOT again
- busybox is in the system and no app not there
- works on D857 858 and 858HK
- it's a LIGHT version, there are functions that are deleted, like weather widget for example
- including deleted app inside the ROM, and could recover yourself
- app can write data to external SD card
- split view works for 3rd party app
- smart cover function removed, user can download the "deleted app" and put back into the system to get it working
deleted apps
http://pan.baidu.com/s/1mg86X6o
HOW TO FLASH
FOR D858HK
1. ROOT
2. install TWRP 2.8.1.0
3 Reboot to TWRP 2.8.1.0 and upgrade it to 2.8.5.1
4. Flash ROM using this newest TWRP
D857 and D858
1. ROOT
2. download build.prop.zip, extract, using ES explorer to replace the one in "system" folder
3 flash D858HK 's TOT (http://bbs.gfan.com/android-7502599-1-1.html)
4.install TWRP 2.8.1.0
5. Reboot to TWRP 2.8.1.0 and upgrade it to 2.8.5.1
6. Flash ROM using this newest TWRP
Do "double wipe" after flashing the ROM, otherwise might have FC messages

Thanks alot i think this will help ...will try it now

but can we install twrp when in lollipop as i am now on lollipop
any ideas?

maybe these
http://bbs.gfan.com/android-7677473-1-1.html
one click Recovery installation
need to be rooted
1. extract files to computer
2 connect phone
3 turn on usb debugging
4. run Recovery.bat
---------------------------------------
old temp way, didn't say if it works on L or only KK
http://bbs.gfan.com/android-7727191-1-1.html

So...can any of you fluent Chinese speakers/readers help with the actual downloading of the ROM? It seems the rom is available at http://pan.baidu.com/s/1mg86X6o, but I get a little overloaded and can't figure out how to download from there. It seems to want me to log in, but I can't figure out if there's a non-login download ability lurking somewhere?

Do you have some screenshoots ?

Two things. First, I had the wrong link before. Correct one is: http://pan.baidu.com/s/1sjoKe4l. Second, I realized the reason is that the zip file is over 1GB and they force you to a "download butler". So the login thing is related to copying that file into your (QQ, for example) account and then you could download the file from there.

If anyone with a D858HK is interested, I was able to install this custom rom on my phone without any problems. I followed steps elsewhere to root (the one click version) and install TWRP. The rom is basically a slim version of the standard lollipop rom. If you end up deciding to install this, be aware that the Google Contact Sync app is not included within the rom and you'll need to also download the "deleted apps" zip file mentioned in the same post (link in OP). In the "deleted apps" zip, you'll want to grab the Gooogle Contact Sync apk and install that ... otherwise you can't get your contacts copied to the new rom. There were a bunch of other apks, but this one the only one so far that seemed like it shouldn't have been removed from the rom.
FYI, here are the version details of the rom:
Android version: 5.0.1
Baseband version: MPSS.DI.3.0.c6.2-00011-M8974AAAAANAZM-1
Kernel version: 3.4.0
Build number: (some chinese)1121561(more chinese)
Software version: D858HK20d-HKG-XX

So in total its not worth installing it? But anyway, thanks for your report!

silencer1979 said:
So in total its not worth installing it? But anyway, thanks for your report!
Click to expand...
Click to collapse
I guess that depends on how easy it is to remove LG's bloatware and whether or not you need all/any of it. I personally didn't care for it anyway. But yeah, other than that, nothing special about the rom.

There were a bunch of other apks, but this one the only one so far that seemed like it shouldn't have been removed from the rom.

i believe there's a thread somewhere in this forum (http://bbs.gfan.com/forum-1508-type-10913.html) regarding d858 MIUI, could someone confirm? Thanks

Edit

twrp flashh from MM
has anyone successfully flashed TWRP from an MM rom i tried it and i got bricked and i cant seem to find one for MM only for LP

Lg g3 d858hk
Hey, did you install? There is a problem or not? All programs worked fluently?

xdax1 said:
let me know if you want any explanations.
it's based on lollipop 20d
- v1.0 LED not working, and this v2.0 fixed the problem
- rooted, superSU v2.46
- once you flashed the ROM, no need to flash the ROOT again
- busybox is in the system and no app not there
- works on D857 858 and 858HK
- it's a LIGHT version, there are functions that are deleted, like weather widget for example
- including deleted app inside the ROM, and could recover yourself
- app can write data to external SD card
- split view works for 3rd party app
- smart cover function removed, user can download the "deleted app" and put back into the system to get it working
deleted apps
http://pan.baidu.com/s/1mg86X6o
HOW TO FLASH
FOR D858HK
1. ROOT
2. install TWRP 2.8.1.0
3 Reboot to TWRP 2.8.1.0 and upgrade it to 2.8.5.1
4. Flash ROM using this newest TWRP
D857 and D858
1. ROOT
2. download build.prop.zip, extract, using ES explorer to replace the one in "system" folder
3 flash D858HK 's TOT (http://bbs.gfan.com/android-7502599-1-1.html)
4.install TWRP 2.8.1.0
5. Reboot to TWRP 2.8.1.0 and upgrade it to 2.8.5.1
6. Flash ROM using this newest TWRP
Do "double wipe" after flashing the ROM, otherwise might have FC messages
Click to expand...
Click to collapse
My LG-D858HK phone hard bricked:
What happened/how I hard bricked the phone. I'd already rooted the phone with Marshmallow and then tried to flash phone TWRP by (mistakenly) using https://play.google.com/store/apps/details?id=b007.autorecd858hk when it hard bricked the phone. Now, the phone screen is black/blank and blue/red LED light flashing.
In addition, my PC doesn't recognise phone when plugged into USB port/s. Pop-up on PC screen says; “The last USB device you connected to this computer malfunctioned and windows do not recognize it.” And in Device Manager, I see a ‘yellow triangle’ next to LGE Platform Android Composite USB Device Driver.
I tried different methods to go into download mode and I’m not sure if any worked. Because, obviously, I can’t see anything on the phone screen to carry out procedures to fix phone in download mode. Moreover, I’m not even sure if the phone goes into download mode apart from a sound made from PC and the pop-up straight after.
PC always recognised phone when plugged into USB port/s before it was hard bricked.