Database Users

[REF] READ IN 1ST : Rooting your Acer Liquid

Well, it seems that a lot of people get their liquid (semi) "bricked" by trying to root their device, mainly by installing Superboot.
So here is an how-to root your Liquid, whatever is your rom.
You don't need Superboot anymore, Superboot was useful before, but now it's USELESS
To root your device, just install MALEZ RECOVERY, and from the recovery menu, you will be able to check the root status of your rom (Enabled / Disabled / Unknown), and of course ROOT your current rom with it.
So, just follow the instructions from here : http://code.google.com/p/acer-liquid-malez-recovery/wiki/howToInstall to get MalezRecovery, and you shouldn't get a "Black Screen" after rooting your device.
Hope this will help some of you

Thank you very much but i cant go past fastboot when flashing it.
my current version is OS_Acer_1.100.39.EMEA.GEN1_A21E_A. should i downgrade first then flash malez. but if i update will malez recovery be deleted?

yyet respond?ee
B
KBEscalona said:
Thank you very much but i cant go past fastboot when flashing it.
my current version is OS_Acer_1.100.39.EMEA.GEN1_A21E_A. should i downgrade first then flash malez. but if i update will malez recovery be deleted?
Click to expand...
Click to collapse
Up..up..
)

KBEscalona said:
Thank you very much but i cant go past fastboot when flashing it.
my current version is OS_Acer_1.100.39.EMEA.GEN1_A21E_A. should i downgrade first then flash malez. but if i update will malez recovery be deleted?
Click to expand...
Click to collapse
Yes any change in firmware re-installs stock recovery.
Malez has 3 different ways to install the recovery on his Google Code site, did none of them work?
If not, try this- http://android.modaco.com/content/a...-superboot-768-880-920-998mhz-recovery-other/

the megaupload link is currently unavailable. does anyone have a mirror? please post

Malez recovery still not compatible with Acer Liquid E Ferrari
Any other way to root?

You don't need to do the whole thing. What you have to do is downloading a App named "Unverisal Androot 1.6.2 B5"
After install, run it, root it. take you 1 second to root you Liquid

Acer Ferrari Root
Hi guys, really i'm tired and NEED HELP :
Ans here's below latest things I've tried to root my mobile :
- SuperOneClickv1.9
SuperOneClick v1.9.0.0
Checking drivers...
Killing ADB Server...
OK
Starting ADB Server...
OK
Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Getting OS Version...
OK
Pushing psneuter...
1972 KB/s (585731 bytes in 0.290s)
OK
chmod psneuter...
OK
Running psneuter...
ROOTED
Pushing busybox...
1768 KB/s (1062992 bytes in 0.587s)
OK
chmod busybox...
OK
Getting mount path...
rootfs / rootfs ro 0 0
FAILED
- MalezRecovery_0.6.1_FULL (this one installed successfully but when i turn off my mobile and start it in recovery mode it's starting normally just a flash for a moment for recovery on screen but then OS starts normally as nothing happened.
- UniversalAndroot-1.6.2-beta5
getting can't root and then force close or report.
- z4root.1.3.0
program close while still under process and then then force close or report.

[GUIDE] D857 to D858HK - G3 Dual SIM with Google Apps!

First of all, I have to officially thank user kalunlee for his help in this. He pulled the files from the chinese forums, and in there you have to either register or pay for the links. Without his help there would be no guide.
XDA is open for everyone, on those Chinese forums they keep their resources well hidden, but they don't bother thanking the people here on XDA for their work (rooting tools maybe?), and they even get credits for the tools taken from here! --rant over--
Let's start now. This guide is for all user of D857 or D858 wanting the Google Apps on their phones without messing around with rooting and custom recoveries, but want to keep the phone in a stock condition. Model D858HK is the only Dual Sim officially supporting the GApps, the goal of this guide is transforming a D857/D858 into an HK model.
Istructions:
Enable USB debugging on your device: menu > settings > developer options.
Install Stump Root and root the phone. Install SuperSU immediately after reboot and run it.
Install Build Prop Editor apk (I used Build Prop Editor from joeykrim, the other one didn't work), edit ro.product.model=LG-D857 to ro.product.model=LG-D858HK.
Install LG Driver.
Install LGFlashTool, overwrite the megalock.dll with the provided one.
Turn off phone, hold the volume up key and plug into the computer (DOWNLOAD MODE).
Let the LG driver install for your phone.
Go to device manager in Windows Control Panel, change LGE Mobile USB Serial Port to com41
Open LGFlashTool select the right TOT file and dll (use BOARD DL)
Go to Port settings set LIMO Port to COM101 tick port 1 only on the right (Basically first 3 items ticked)
Click Start
Remove the cable for 5 seconds and reconnect, the flash will start
Flash
Done
Now you have a D858HK instead of D857.
If you get a port error at the starting of the flash disconnect the phone, remove LG drivers, reinstall them again, change the port to com41, and without rebooting launch again the flashtool.
If you get a Windows error, remove any antivirus you have!!
If at the end of the flashing procedure the phone boots into the miniOS, then pull out the battery and enter into the recovery and do a factory reset. Reboot. When in miniOS again, press the power button and tap on normal boot!
Links:
ALL-IN-ONE TRANSFORMATION PACKAGE (thanks to ikol-77):
https://drive.google.com/folderview?id=0Bxv0rM0SdxuFbnpWUTFyaFVqVGc&usp=sharing
TOT File (D858HK v10d)
http://pan.baidu.com/share/init?shareid=1792523609&uk=2841005147&third=15
password 3uwc
Alternate link (magnet): magnet:?xt=urn:btih:8643A5C8F6F5B12...nce&tr=udp://tracker.publicbt.com:80/announce
DLL
https://mega.co.nz/#!VEhTzJxQ!v44-bnc1zhapsTDvT8UZOaiyMmKGBqg2FL9PKjrwPPc
password g6qa
Alternate Link with Blindfolded XML for Flashtool (magnet): magnet:?xt=urn:btih:6D5F4E34FF96E10...=udp://tracker.openbittorrent.com:80/announce
Build Prop Editor v1.17
https://mega.co.nz/#!MF5xnYIQ!vyvNmlhYQBfy7MpfZ27C8wiPQKe6JY4U7AfPOUNny4U
LG Driver v3.12.3
https://mega.co.nz/#!0IpVzb4I!lgvQsTAmKD-1J3yV-WRqWfJLuiVwhwuL0q3ObNjSEK0
LG FlashTool v1.8.6.527
https://mega.co.nz/#!VBJh0bQa!0Tx15V0sfxd98mYpFxsp-h8RPDVhMCeQ6e0nNc6M9YY
Alternate Link (magnet): magnet:?xt=urn:btih:2037B01DADF1D36...nce&tr=udp://tracker.publicbt.com:80/announce
Stump Root v1.2.0
https://mega.co.nz/#!QRpQEKQI!UYXXJiJK3Ql-nO9ecyM6YdQJwtz_Px1-sYezZ9wGLs0
SuperSU v2.14
https://mega.co.nz/#!wFAGhYqA!T2gxEyS8CuTsibtrUX9YsEKTJZaXYUAkq1dQM2628YM
IMPORTANT: For those of you with not working links or different issues during the procedure, please have a look at the findings of reb00tz (again, thanks buddy!):
http://forum.xda-developers.com/showpost.php?p=56542760&postcount=80
For those of you needing to root, here is my guide, just follow it without installing the GApps, it's useless now!
http://forum.xda-developers.com/showpost.php?p=55587140&postcount=2
Yes, after transforming the phone into a D858HK, you'll be able to install any OTA update that will be pushed to you. It's not like the G2, no more OTAs after this guide, you will have to manually install the update.
DO NOT INSTALL v10c on the D857, it's impossible to root at the moment. If you do, the only way to go is the downgrade. I will set up a new guide soon if I'll be able to do that on mine (learn the hard way :crying: ) Look for D857v10a TOT. Downgrade to v10a, root, then follow this guide to transform to a D858HK.
Will edit with more detailed instructions soon. STAY TUNED!
--------D858HK v10f--------
Edit: Thanks to member biu40288 on gfan, here is the newest v10f D858HK:
http://pan.baidu.com/s/1o6kIAFo
Password: fx5e
Alternate Link (magnet): magnet:?xt=urn:btih:D0B7D6F43FDC136...=udp://tracker.openbittorrent.com:80/announce
WARNING: v10f no root! None of the root methods work (PurpleDrake, IoRoot, StumpRoot, Tow3lRoot)!
If you need to go back to v10a of D857, here are the links thanks to ikol-77:
v10a TOT:
https://mega.co.nz/#!plghkBKB!LgO_qOhVoyfM27kYkjeormM9kS3YnlbkYd4M_6unVUU
Password: lgbbs
LOLLIPOP D858HK v20d: http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW1D8X8F22TWAAB9BD3F765/D858HK20d_00.kdz
Video-Guide for flashing the LG G3:
http://lgg3root.com/lg-g3-root/how-to-unrootunbrick-lg-g3/

Thanks a lot for this great information.
However, MEGA asks for an decryption key ... can't download atm.
A doppo

The question is: can we do this for all variants? Like vs985/D851 to D855
Sent from my VS985 4G using XDA Free mobile app

I just flashed mine, everything seems OK, just at the end LG Flash Tool showed "Waiting for reset 120 sec", phone restarted and setup screen showed up.
Then LG Flash Tool showed error message "download failed" and "USB port open fail", but phone works well. Any idea why this happened?

Don't try to flash other LG G3 to this version. It only works for D857 or D858 to D858HK. These are the dual sim version and all have the same hardware.
Not sure what happened to the links but you can try the links in the original post
http://forum.xda-developers.com/lg-g3/help/d857-gapps-t2882412/page3
You can ignore the fail message at the end, it happened to one of the phones that I flashed too.

DomFel said:
Yes, after transforming the phone into a D858HK, you'll be able to install any OTA update that will be pushed to you.
Click to expand...
Click to collapse
That's not actually accurate. OTA on D858HK are IMEI based, so even the D857 (or mainland D858) is flashed into D858HK, it won't receive any OTA notification still,as your IMEI will be designated to D857.
I'm not exactly sure if there s any way to side load the OTA without root/flash Tot, I hope someone will find a way when new OTA files are available for this.

kingcedz said:
That's not actually accurate. OTA on D858HK are IMEI based, so even the D857 (or mainland D858) is flashed into D858HK, it won't receive any OTA notification still,as your IMEI will be designated to D857.
I'm not exactly sure if there s any way to side load the OTA without root/flash Tot, I hope someone will find a way when new OTA files are available for this.
Click to expand...
Click to collapse
You're partially correct. OTAs are theoretically IMEI based, but it has to match the installed firmware and firmware keys of the device, in this case you'll have 858HK keys, thus 858HK OTA.
On the G2 I changed firmware successfully twice to change the region (thus enabling few needed LTE bands), and it got two OTAs for that region, not for the original one.
Time will tell BTW!

Hi ! you mean by firmware installed 4G frequencies can change?

freejess said:
Hi ! you mean by firmware installed 4G frequencies can change?
Click to expand...
Click to collapse
That's what happened with the G2. Couldn't get 4G in the UAE with Open EUR firmware. Switched to UAE firmware and got LTE!

Ah! This is great news. Maybe I'll get one of Australia will have plenty of 800mhz LTE as I was certifed seller ...

freejess said:
Ah! This is great news. Maybe I'll get one of Australia will have plenty of 800mhz LTE as I was certifed seller ...
Click to expand...
Click to collapse
Be careful, you can't flash a D855 firmware into a D857/858/859 phone! You'll brick it!!

DomFel said:
Be careful, you can't flash a D855 firmware into a D857/858/859 phone! You'll brick it!!
Click to expand...
Click to collapse
Hi there. Hoping you or maybe others from this thread could help me.. working on this document to list which root methods work on each device.
We do not get much input/feedback from D857/8/9 users and it would be nice to know if anyone could help me fill in the blanks for those devices.
Does D857/8/9 work with ioroot? if so which software versions? (10A? 10B? for example..)
Does D857/8/9 work with towelroot? if so which software versions?
Does D857/8/9 work with purpledrake root? if so which software versions?
Does D857/8/9 work with stump root? if so which software versions?
And I see you have mentioned that D855 firmware will brick a D857/8/9? Is this confirmed? It cannot be fixed if someone does this?
Do D857/8/9 users have a working TWRP from BUMP! yet? Im curious if the D855 version of TWRP would work for you
D857/8/9 users.. please keep me posted so we can make sure you dont get left out

autoprime said:
Hi there. Hoping you or maybe others from this thread could help me.. working on this document to list which root methods work on each device.
We do not get much input/feedback from D857/8/9 users and it would be nice to know if anyone could help me fill in the blanks for those devices.
Does D857/8/9 work with ioroot? if so which software versions? (10A? 10B? for example..)
Does D857/8/9 work with towelroot? if so which software versions?
Does D857/8/9 work with purpledrake root? if so which software versions?
Does D857/8/9 work with stump root? if so which software versions?
And I see you have mentioned that D855 firmware will brick a D857/8/9? Is this confirmed? It cannot be fixed if someone does this?
Do D857/8/9 users have a working TWRP from BUMP! yet? Im curious if the D855 version of TWRP would work for you
D857/8/9 users.. please keep me posted so we can make sure you dont get left out
Click to expand...
Click to collapse
D857 works with Stumproot with version v10a and v10b only. v10c fixed the vulnerability.
D857 doesn't work with towelroot (tested v10b and v10c).
D857 doesn't work at all, it says -unsupported-.
D857 doesn't work with ioroot (tested v10b and v10c).
D857 will be bricked by flashing D855 firmware. Probably a recovery would be possibile accessing the firmware download mode, but I am not brave (stupid) enough to do it, since D855 doesn't support dual sim mode.
TWRP doesn't work on D857, after a reboot the recovery won't be accessible anymore, it will only work once. Be careful, when installing a custom recovery the original one will be gone forever, unless you restore with LG Support Tool. TWRP doesn't fully support D857, thus it probably installs the recovery on wrong memory addresses, and it is not bootable for a second or third time, but only once.
The only way to access the custom recovery is to install it again.
Personally I had to downgrade from v10c to v10b to be able to root and change firmware to D858HK in order to have GApps natively. v10c on D857 is unrootable.
The difference between D857/8/9 is customization: D857 is the international version, /8 and /9 are for China Mobile and Statecom. D858HK is the Hong Kong international version of the G3 Dual Sim that includes the GApps, all other firmware don't, since they are for the chinese market, which Google abandoned.
Haven't personally tested Stumproot on D858HK v10d yet.

DomFel said:
D857 works with Stumproot with version v10a and v10b only. v10c fixed the vulnerability.
D857 doesn't work with towelroot (tested v10b and v10c).
D857 doesn't work at all, it says -unsupported-.
D857 doesn't work with ioroot (tested v10b and v10c).
D857 will be bricked by flashing D855 firmware. Probably a recovery would be possibile accessing the firmware download mode, but I am not brave (stupid) enough to do it, since D855 doesn't support dual sim mode.
TWRP doesn't work on D857, after a reboot the recovery won't be accessible anymore, it will only work once. Be careful, when installing a custom recovery the original one will be gone forever, unless you restore with LG Support Tool. TWRP doesn't fully support D857, thus it probably installs the recovery on wrong memory addresses, and it is not bootable for a second or third time, but only once.
The only way to access the custom recovery is to install it again.
Personally I had to downgrade from v10c to v10b to be able to root and change firmware to D858HK in order to have GApps natively. v10c on D857 is unrootable.
The difference between D857/8/9 is customization: D857 is the international version, /8 and /9 are for China Mobile and Statecom. D858HK is the Hong Kong international version of the G3 Dual Sim that includes the GApps, all other firmware don't, since they are for the chinese market, which Google abandoned.
Haven't personally tested Stumproot on D858HK v10d yet.
Click to expand...
Click to collapse
thank you for your response.
are you 100% sure PurpleDrake doesn't work? D855 10L has patched Stump but no one has patched PurpleDrake yet... unless it never worked to begin with.
does the following command work for you?
Code:
adb reboot --bnr_recovery
and did u try the purpledrake at this thread? because there are 2.. one is for D851 only.. this one is for all - http://forum.xda-developers.com/lg-g3/development/root-root-lg-g3-easily-purpledrake-lite-t2821000
check the manual commands in the first post if the script does not work. I want to confirm and be 110% sure purpledrake does not work on the D857/8/9.. that would make the D857/8/9 the ONLY g3 that does not have root yet.
also.. you mentioned D857 for ioroot/towelroot/purpledrake.. etc... what about the D858 and D858HK and D859? same results for all phones? or only for D857?
and for TWRP.. did you use the fastboot twrp method? do not use fastboot boot method. or did you try the Bump twrp? u tried the twrp-2.8.0.0_d855-signed.img file here? http://forum.xda-developers.com/lg-...mp-unlock-lg-g3-twrp-d852-d852g-f400-t2900614
http://downloads.codefi.re/thecubed/lg_g3/bump/twrp-2.8.0.0_d855-signed.img
Code:
[SIZE="1"]adb push twrp-2.8.0.0_d855-signed.img /sdcard/
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/twrp-2.8.0.0_d855-signed.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
reboot recovery[/SIZE]
that does not work? if that does not work I will make a proper TWRP for D857 D858 and D859 devices. I will need a boot.img from D858HK if possible please.
and can any D857, D858 or D859 users PM/Message me their IMEIso that I can use LG's website to look up KDZ files and download them myself.
If you want.. you can change or leave off the last 3 digits of the IMEI so that I dont know your exact IMEI for security.

autoprime said:
thank you for your response.
are you 100% sure PurpleDrake doesn't work? D855 10L has patched Stump but no one has patched PurpleDrake yet... unless it never worked to begin with.
does the following command work for you?
Code:
adb reboot --bnr_recovery
and did u try the purpledrake at this thread? because there are 2.. one is for D851 only.. this one is for all - http://forum.xda-developers.com/lg-g3/development/root-root-lg-g3-easily-purpledrake-lite-t2821000
check the manual commands in the first post if the script does not work. I want to confirm and be 110% sure purpledrake does not work on the D857/8/9.. that would make the D857/8/9 the ONLY g3 that does not have root yet.
also.. you mentioned D857 for ioroot/towelroot/purpledrake.. etc... what about the D858 and D858HK and D859? same results for all phones? or only for D857?
and for TWRP.. did you use the fastboot twrp method? do not use fastboot boot method. or did you try the Bump twrp? u tried the twrp-2.8.0.0_d855-signed.img file here? http://forum.xda-developers.com/lg-...mp-unlock-lg-g3-twrp-d852-d852g-f400-t2900614
http://downloads.codefi.re/thecubed/lg_g3/bump/twrp-2.8.0.0_d855-signed.img
Code:
[SIZE="1"]adb push twrp-2.8.0.0_d855-signed.img /sdcard/
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/twrp-2.8.0.0_d855-signed.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
reboot recovery[/SIZE]
that does not work? if that does not work I will make a proper TWRP for D857 D858 and D859 devices. I will need a boot.img from D858HK if possible please.
and can any D857, D858 or D859 users PM/Message me their IMEIso that I can use LG's website to look up KDZ files and download them myself.
If you want.. you can change or leave off the last 3 digits of the IMEI so that I dont know your exact IMEI for security.
Click to expand...
Click to collapse
Unfortunately that command didn't work on D857 v10c, and the .bat gave unsupported model. Trust me I tried everything to root before I downgraded, I was desperate to gain root on v10c!!
This is the link for v10c for D857:
http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW040906432109876543213/D85710c_00.kdz
Unfortunately I couldn't find any other kdz (I got that link from my IMEI). The dual sims are mainly for the Chinese market, and they don't share any kdz on the Chinese forums, because many of them ask for money for the download of TOT files.
Please send me the instructions to extract the boot.IMG! I will also re-post the link on Mega later on for the 858HK tot file.

DomFel said:
Unfortunately that command didn't work on D857 v10c, and the .bat gave unsupported model. Trust me I tried everything to root before I downgraded, I was desperate to gain root on v10c!!
This is the link for v10c for D857:
http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW040906432109876543213/D85710c_00.kdz
Unfortunately I couldn't find any other kdz (I got that link from my IMEI). The dual sims are mainly for the Chinese market, and they don't share any kdz on the Chinese forums, because many of them ask for money for the download of TOT files.
Please send me the instructions to extract the boot.IMG! I will also re-post the link on Mega later on for the 858HK tot file.
Click to expand...
Click to collapse
ok.
which firmware are you running now? D857? 10c? rooted?
you need root.. and then you would do these commands... then upload the boot.img to me.
so I guess you need to be on 10B and use stump to root.
Code:
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/boot.img
exit
exit
adb pull /sdcard/boot.img
the above commands will open adb shell, gain root, backup your boot.img to internal sdcard, exit rooted adb shell, exit adb shell, pull boot.img off internal sdcard into the folder on your computer where you are running adb.
OR
if you do not want to root the phone but still pull the files.. see my thread here: http://forum.xda-developers.com/lg-g3/development/psa-stop-taking-ota-updates-update-t2909412
under the "Download Updates" section are steps for how to extract KDZ. you can extract boot.img from kdz that way.
the only way to have a rooted D857 10C would be to have 10B.. root it with stump.. install TWRP (D857/8/9 version I need to make).. then update to 10C manually by flashing the system.img, boot.img and modem.img in TWRP.
I have an easy method to flash the system/boot/modem images in my thread as well: http://forum.xda-developers.com/lg-g3/development/psa-stop-taking-ota-updates-update-t2909412
under the "Manual Updating" section I have some flashable "Flash2" zips that do all the work for you once you have the system/boot/modem images on your internal sdcard. no need to make new flashable zips.
If anyone has the boot.img for D858 or D858HK that would be good too.

DomFel said:
You're partially correct. OTAs are theoretically IMEI based, but it has to match the installed firmware and firmware keys of the device, in this case you'll have 858HK keys, thus 858HK OTA.
On the G2 I changed firmware successfully twice to change the region (thus enabling few needed LTE bands), and it got two OTAs for that region, not for the original one.
Time will tell BTW!
Click to expand...
Click to collapse
FYI, I had it flashed with 10C and it didn't receive OTA to 10D, had to do a manual refresh of the whole 10D tot.
I've seen Chinese users reporting the same as well.
That's why i m convinced conversion this way won't receive OTA.
In any case, i have both the D857 converted D858HK, and the local stock D858HK, will be able to verify that once new OTA is pushed out.
all else apart, it's the best version of the android phone by a country mile.

kingcedz said:
FYI, I had it flashed with 10C and it didn't receive OTA to 10D, had to do a manual refresh of the whole 10D tot.
I've seen Chinese users reporting the same as well.
That's why i m convinced conversion this way won't receive OTA.
In any case, i have both the D857 converted D858HK, and the local stock D858HK, will be able to verify that once new OTA is pushed out.
all else apart, it's the best version of the android phone by a country mile.
Click to expand...
Click to collapse
I think you are right. Today I flashed a D855 of a friend of mine in order to change the region. Unfortunately the region didn't change, even by using a TOT file. Under software version it's still AME region and not EUR. Editing the build.prop and reflashing/restoring didn't work neither.
I think LG has hardcoded the region in the hardware, not on the software side anymore!

Hi all,
I'm a user of D858hk, recently i have updated my device through LGMobile Support to D858hk v10f, and the stump root effect is waived...
I try to reroot through stump / purpledrake / towelroot , but eventually can't be success.
Hence, I try to flash the stock d858hk v10d rom here, i have several questions suffer during the thread here.
1. Do i need to modify the build.prop file as my device is D858hk
2. I can't get the dll file from the above links
TOT File and DLL: http://pan.baidu.com/share/init?shar...05147&third=15
DLL http://pan.baidu.com/share/init?shar...05147&third=15
Both links contain a zip file which only include a .tot file inside.
3. I have followed all the steps as stated above, but during "Click Start->Remove the cable for 5 seconds and reconnect, the flash will start-> it show error message "Download Fail - Can't change to download mode", i'm sure i have done "Turn off phone, hold the volume up key and plug into the computer (DOWNLOAD MODE)."
Hope anyone can help and suggest what mistake i have made.
thanks.

Does anyone have a D858HK recovery file? I've accidentally written it with the wrong recovery img (D855's) and when I try to boot recovery it goes to fastboot mode... but on normal operation there aren't any side effects yet.
Greatly appreciate it if any of you can post the recovery's img!
---------- Post added at 02:24 PM ---------- Previous post was at 02:16 PM ----------
cmko said:
Hi all,
I'm a user of D858hk, recently i have updated my device through LGMobile Support to D858hk v10f, and the stump root effect is waived...
I try to reroot through stump / purpledrake / towelroot , but eventually can't be success.
Hence, I try to flash the stock d858hk v10d rom here, i have several questions suffer during the thread here.
1. Do i need to modify the build.prop file as my device is D858hk
2. I can't get the dll file from the above links
TOT File and DLL: http://pan.baidu.com/share/init?shar...05147&third=15
DLL http://pan.baidu.com/share/init?shar...05147&third=15
Both links contain a zip file which only include a .tot file inside.
3. I have followed all the steps as stated above, but during "Click Start->Remove the cable for 5 seconds and reconnect, the flash will start-> it show error message "Download Fail - Can't change to download mode", i'm sure i have done "Turn off phone, hold the volume up key and plug into the computer (DOWNLOAD MODE)."
Hope anyone can help and suggest what mistake i have made.
thanks.
Click to expand...
Click to collapse
1) no, as your device is already D858HK, no need.
2) Here's a link for you to obtain the DLL: https://mega.co.nz/#!YNx2DCSZ!ok0oaK5o7Xu0QeorfnH5gfkEDra9RyoFfhnCkXXIJNE
3) try it after using the right DLL file.

[STOCK][ROOT] Step-by-Step EASY ROOT whit DUALRECOVERY in your Lollipop 14.5.A.0.270

MOD EDIT by @gregbradley
Also, users should be aware that Kingo root sends your IMEI to an unknown IP address in china during the root process, you have been warned. For more information read the whole OP here
Step-by-Step EASY ROOT whit DUALRECOVERY in your Lollipop 14.5.A.0.270
This was tested in my Z1C whit unlocked bootloader running stock 14.5.A.0.270, if you chose to try it in a locked bootloader, do it at your how risk!
Before starting, read the post to the end to see if you can manage to do this steps by your self!
This isn't for everyone, and it my not work on everyone, but if it helps you great... If not try another solution. THIS IS THE SOLUTION THAT WORKED FOR ME!
WARNING: "I am not responsible for bricked devices, dead SD cards, and any kind of problems in your little life of yours. YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you."
1. Download Z1C-lockeddualrecovery2.8.18-RELEASE.installer.zip from "[Z1 Compact][TWRP][PhilZ Touch][CWM] XZDualRecovery" or go to NUT link site that you can find here.
Unzipped to your computer... and save-it for later.
2. Download [BETA][2015.04.28] SuperSU v2.49, from Chainfire from here, and put it on your Internal Storage.
3. Download the attached "KingRoot replacement.zip" and place the mrw folder in you internal storage.
4. Uninstall or deactivate any boot your antivirus in your computer (for step 9) and in your device.
5. Download and Install Terminal Emulator app from the PlayStore.
6. Download and Install the attached version of KingRoot (that you can find in this post). This version was the only one that I tried that root 14.5.A.0.270 Rom (DO NOT REBOOT YOUR DEVICE)
7. Open Terminal emulator and type :
"Su"
Allow root permission
Type:
"sh /sdcard/mrw/root.sh"
Update su binary normal, but in the end DO NOT REBOOT YOUR DEVICE
8. Go to Settings and turn USB Debugging on... (If you dont now how to do this... Go to Settings-About phone-click seven times in "build number"-go back-"developer option"- turn it on!!!)
9. Go to your computer and connect your phone.
unzip the file that you download it in Step 1, and press install.
Chose the SuperSu Option
When asked, allow debugging in your phone and also root access.
10. In the end of the the installation process THE PHONE WILL REEBOT and in the star sony screen, press multiple times the volume down to enter TWRP recovery.
Now install the SuperSU v2.49 Beta zip file that you downloaded in step 2.
11. Reboot your device and now you have permanent root and dual recovery... It was not so hard, was it???
Give Thanks to NUT and Chainfire, that without their work, this was not possible.

Reserved:
A word of advice.
If your device gets stuck or die, reinstall your firmware whit the original sony flash tool, that you can find and download in sony's support site.

You should also mention that the Kingroot app may share Your phone's unique information such as IMEI with some servers. Also, in step 7 You assume the phone is rooted, but till step 6 all that is done is downloading and installing the app, nothing is done by opening the app, which might confuse some users.

Since all other thing i wrote here were deleted i will delete this also.

Jovica007 said:
When i enter sh/sdcard/mrw/root.sh it just says this "not found" but i have paste it to root of my internal memory and when i saw that isnt working paste it to external memory, but no luck.... Some help would be appreciated.
Click to expand...
Click to collapse
its: "sh /sdcard/mrw/root.sh"
you must leave a space between sh and /
Another thins... this is my solution that i decided to share... If you don't like it, don't try it or don't use it... it works for me.
If it helps anyone, great!
Is also possible that doesn't work for everyone... so... like it says in the OP... do it at your own risk.
Criticize is easy... posting solutions is harder!

I have try kingroot on fw 283 telecom de, and not worked.

can somebody confirm this to work on Locked bootloader?
this phone is my daily driver and i dont want to brick it

Only tested on generic .270 whit unlocked bootloader

LukeHorizon said:
can somebody confirm this to work on Locked bootloader?
this phone is my daily driver and i dont want to brick it
Click to expand...
Click to collapse
You can follow guide from My signature. It is tried and tested on locked bootloader.

KingRoot.apk worked on my Z1C with .270 kernel, with locked bootloader. Should work on .283 as well. Followed a different tutorial though, probably taken from this one. Dunno which from which

Can you post your tutorial?
Gesendet von meinem D5503 mit Tapatalk

Thread cleaned
Do not argue in the open forum. This is a guide, follow it, or do not follow it. Suggest improvements if you see any, but do not argue in it.

i flashed the stable SuperSu zip and now my device is bootlooping ... recovery is installed, so what do

LukeHorizon said:
i flashed the stable SuperSu zip and now my device is bootlooping ... recovery is installed, so what do
Click to expand...
Click to collapse
Press volume down during booting, it should enter in recovery

paolo-red1 said:
Press volume down during booting, it should enter in recovery
Click to expand...
Click to collapse
well, i entered Recovery and installed a prerooted rom not the way i wanted it but at least i got working root on a working phone so lets see about xposed

LukeHorizon said:
i flashed the stable SuperSu zip and now my device is bootlooping ... recovery is installed, so what do
Click to expand...
Click to collapse
LukeHorizon said:
well, i entered Recovery and installed a prerooted rom not the way i wanted it but at least i got working root on a working phone so lets see about xposed
Click to expand...
Click to collapse
I have removed exposed because I was having trouble with charging. I uninstalled it and no problem (this on lollipop prerooted wirh last supersu and last dual recovery)

can't get su working, where do I have to put it?
if I type su it shows: not found
if i type ./su it shows: permission denied
can anybody help me?

raxman68 said:
can't get su working, where do I have to put it?
if I type su it shows: not found
if i type ./su it shows: permission denied
can anybody help me?
Click to expand...
Click to collapse
this uses same method but is explained a bit differently. https://www.youtube.com/watch?v=n9TIS1k50po
i read both guides through couple of times and then went for it and it worked.

Hi,
I've got stuck in the step 9. I have USB debugging enabled in my phone, but adb is not seeing my device and the script is waiting with for it:
Code:
==============================================
= =
= PhilZ Touch, CWM and TWRP Dual Recovery =
= Maintained by [NUT] =
= =
= For Many Sony Xperia Devices! =
= =
==============================================
1. Installation on ROM rooted with SuperSU
2. Installation on ROM rooted with SuperUser
3. Installation on unrooted ROM using the TowelRoot method
4. Install ADB drivers to windows
5. Exit
Please choose install action.
[1,2,3,4,5]?1
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
=============================================
adb devices
List of devices attached
In step 7, you wrote to now reboot the phone, which I assume could solve my issue (reboot into fastboot mode).
Do you have any solution for this?
Thanks a lot,
Michal.
EDIT:
I've solved this problem when I changed the Sony Xperia Z1 driver to not MTP but USB composite -> then ADB driver installed as well.
How to change this: Device Manager->Portable Devices-> Z1->Update Driver->Browse my Computer->Let me pick from.. -> Change to USB composite.
Now I have dual recovery with rooted phone - thanks a lot!
Michal.

OS 5.0 + ROOT + GAPPS + Play Store VIDEO TUTORIAL

Please DO NOT use this guide anymore due to bricks. Instead use an up to date guide: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
I was debating whether to make a new thread or not but ended up doing so. First off I want to thank the people on XDA including @bibikalka , @DoLooper , and @jmz who made everything work. I'm a visual & hands-on learner so I like making these types of tutorials and I hope others who favor more visual tutorials will find them useful as well. This video guide is a combo from guides from @bibikalka (ROOT & GAPPS & OTHER) , @DoLooper (ROOT & GAPPS & OTHER) , and @jmz (TWRP).
This video tutorial explains how you can get root, GAPPS, and the Play Store on Fire OS 5.0. This video is one of the more andvanced ones and contains many steps. I take no responsibility if something happens to your device. Try to follow the video as close as you can and you sould be fine. The basic process consists of downgrading to a root vulnerable OS, rooting it and installing TWRP, then through TWRP install the new 5.0 version and then GAPPS, root, etc.
Video
www.youtube.com/watch?v=gC0nm8I3IFE
Here are the in depth steps. Follow along with video for more insight:
1.Install USB ADB drivers: https://www.youtube.com/watch?v=CyJlmTtLsIg
Download Software version 4.5.3: https://kindle-fire-updates.s3.amazonaws.com/update-kindle-20.4.5.3_user_453011120.bin
Reboot into recovery: "adb reboot recovery"
Enter sideload mode from recovery
Install v4.5.3: "adb sideload update-kindle-20.4.5.3_user_453011120.bin"
Wiipe data/ factory restet from recovery
Reboot & keep wifi off so that it does not re-update
Disable ota updates with "adb shell pm block com.amazon.dcp" and "adb shell pm block com.amazon.otaverifier"
Turn on wifi
Download kingroot from http://www.kingroot.net/ onto device
Root with app
Test root with "adb shell" and "su"
Download TWRP IMG: https://drive.google.com/file/d/0Bx_94ujbh0qobGpZcGV6aHNKT3M/view?usp=sharing
Check md5sum: 4fefd8b46ca97a2b66e4c8852d4c3396
Push recovery to device with "adb push openrecovery-twrp-2.8.6.0-ariel.img /data/local/tmp"
Go into root shell with "adb shell" and "su"
Go to /data/local/tmp/ directory: "cd /data/local/tmp/"
Install TWRP: "dd if=openrecovery-twrp-2.8.6.0-ariel.img of=/dev/block/mmcblk0p7"
Test TWRP with "adb reboot recovery"
Boot back up
Download 5.2.2 firmware: https://mega.nz/#!ZI1wTL6L!xbDNDvaJjLUWwqe8J9awAs4xNQvxreXCmZ1I6cWTLVA
Download 5.2.0 stock recovery: http://forum.xda-developers.com/attachment.php?attachmentid=3416498&d=1437711793
Download pico gapps package (Play Store etc): https://basketbuild.com/devs/TKruzze/5.1.x GApps Packages/MODULAR - Pico GApps
Download make_space zip: http://forum.xda-developers.com/attachment.php?attachmentid=3519998&d=1445918906
Move firmware, recovery, gapps, and make_space zip onto Fire internal storage
Rename 5.2.2 firmware to a .zip file instead of a .bin file so TWRP recognizes it
Reboot into TWRP: "adb reboot recovery"
STEPS 28-33 MUST BE DONE IN ONE SESSION
Do another factory reset
Flash 5.2.2 firmware
Flash 5.2.0 recovery
Flash/run make_space zip to clear up system space
Flash Pico GAPPS zip
Choose reboot into recovery from TWRP and tell TWRP that you would like to install superSU
Reboot device and wait for it to boot up (will take about ten minutes)
After booted up, disable ota updates with "adb shell", "su", "pm disable com.amazon.otaverifier", and "pm enable com.amazon.dcp"
Update SuperSU from Play Store, open it and choose to install normally
Root, GAPPS, and Play Store should all be working now
Click to expand...
Click to collapse
Notes:
Do not try to re-flash TWRP the same way you did on 4.4.3. It will not work
Click to expand...
Click to collapse
Links & Downloads:
•XDA Guide: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
•USB driver tutorial: https://www.youtube.com/watch?v=CyJlmTtLsIg
•4.5.3 software: https://kindle-fire-updates.s3.amazonaws.com/update-kindle-20.4.5.3_user_453011120.bin
•KingRoot: http://www.kingroot.net/
•TWRP image: https://drive.google.com/file/d/0Bx_94ujbh0qobGpZcGV6aHNKT3M/view?usp=sharing
•5.2.2 firmware: https://mega.nz/#!ZI1wTL6L!xbDNDvaJjLUWwqe8J9awAs4xNQvxreXCmZ1I6cWTLVA
•5.2.0 stock recovery: http://forum.xda-developers.com/attachment.php?attachmentid=3416498&d=1437711793
•pico gapps package (Play Store etc): https://basketbuild.com/devs/TKruzze/5.1.x GApps Packages/MODULAR - Pico GApps
•make_space zip: http://forum.xda-developers.com/attachment.php?attachmentid=3519998&d=1445918906
Click to expand...
Click to collapse

Detailed tutorial
Will try later today.

Thanks a lot for the video. Used it and got everything working no problems!

argrr101 said:
Thanks a lot for the video. Used it and got everything working no problems!
Click to expand...
Click to collapse
Awesome to hear. Enjoy
Sent from my KFARWI using Tapatalk

powerpoint45 said:
I was debating whether to make a new thread or not but ended up doing so. First off I want to thank the people on XDA including @bibikalka , @DoLooper , and @jmz who made everything work. I'm a visual & hands-on learner so I like making these types of tutorials and I hope others who favor more visual tutorials will find them useful as well. This video guide is a combo from guides from @bibikalka (ROOT & GAPPS & OTHER) , @DoLooper (ROOT & GAPPS & OTHER) , and @jmz (TWRP).
This video tutorial explains how you can get root, GAPPS, and the Play Store on Fire OS 5.0. This video is one of the more andvanced ones and contains many steps. I take no responsibility if something happens to your device. Try to follow the video as close as you can and you sould be fine. The basic process consists of downgrading to a root vulnerable OS, rooting it and installing TWRP, then through TWRP install the new 5.0 version and then GAPPS, root, etc.
Video
www.youtube.com/watch?v=gC0nm8I3IFE
Here are the in depth steps. Follow along with video for more insight:
Notes:
Links & Downloads:
Click to expand...
Click to collapse
Got a " E: failed to verify whole-file signature" error message when trying to sideload 4.5.3 update

2006yamahaR6 said:
Got a " E: failed to verify whole-file signature" error message when trying to sideload 4.5.3 update
Click to expand...
Click to collapse
Hmm. Maybe try redownloading the update file as it cold be corrupted. I'm really not sure about this one
@DoLooper you've got any ideas?
Sent from my KFARWI using Tapatalk

@powerpoint45 Are you using the Amazon launcher or a custom one? Has anyone tried to change the launcher using the method that worked for 4.5.3?

2006yamahaR6 said:
Got a " E: failed to verify whole-file signature" error message when trying to sideload 4.5.3 update
Click to expand...
Click to collapse
powerpoint45 said:
Hmm. Maybe try redownloading the update file as it cold be corrupted. I'm really not sure about this one
@DoLooper you've got any ideas?
Click to expand...
Click to collapse
Only that a search turns up lots of hits.

argrr101 said:
@powerpoint45 Are you using the Amazon launcher or a custom one? Has anyone tried to change the launcher using the method that worked for 4.5.3?
Click to expand...
Click to collapse
I'm using a custom one. If you have root just install your custom Launcher, go into adb shell, type "su", and then "pm disable com.amazon.firelauncher"
Sent from my SPH-L710 using Tapatalk

argrr101 said:
[MENTION=4469251]Has anyone tried to change the launcher using the method that worked for 4.5.3?
Click to expand...
Click to collapse
This is for latest OS 5.0.1 (5.2.2u2). Be sure to install custom launcher first. Need to be in SU.
pm disable com.amazon.firelauncher

Thanks, got Nova Launcher up and working.

cxm170 said:
Will try later today.
Click to expand...
Click to collapse
works like a charm
. thanks

Excellent write-up I didn't even bother watching the video... My hd6 is now working as it should!
One note - I had to register with both Amazon and Google via wifi before I could update SuperSU and disable ota updates through adb. Not sure if I did something wrong, but that's how it ended up working for me.

Hello, I have tried this tutorial but I'm unable to downgrade to 4.5.3
I get a signature verification error when sending the file; the exact error from the recovery logs is:
Code:
I: failed to verify against RSA key 0
E: failed to verify whole-file signature
The installed OS version is 5.0.1 on a Fire 5th generation.
Does anyone have a solution for this problem?

Get the same error :
E:failed to verify whole-file signature
E: signature verification failed
Installation aborted
Can smone help pls?

I followed this guide to root my fire, it worked.
http://forum.xda-developers.com/amazon-fire/development/wip-achieving-root-thread-t3238152

wasted whole day, try 3 times already, doesn't work on Fire HD6, Followed all the steps, upgraded from 4.5.5 to 5.0.1 Preview, then downgraded to 4.5.3, install KingRoot to get su, install TWRP, copy all zip packages, flash them, reboot via TWRP to install superSU and after 10 minutes it shows kindle fire OS 5.0.1, and to perform step 35, no SU access any more, can't complete step 35, such a wastage of hours and hours

george9584 said:
wasted whole day, try 3 times already, doesn't work on Fire HD6, Followed all the steps, upgraded from 4.5.5 to 5.0.1 Preview, then downgraded to 4.5.3, install KingRoot to get su, install TWRP, copy all zip packages, flash them, reboot via TWRP to install superSU and after 10 minutes it shows kindle fire OS 5.0.1, and to perform step 35, no SU access any more, can't complete step 35, such a wastage of hours and hours
Click to expand...
Click to collapse
Man I am glad I read this post... I have a Gen 4 HD6 that came with 4.5.5, and I would LOVE to get root and GAPPS and make this thing work the way it should, but these tutorials are confusing as hell...
Do we use ADB+Fastboot or do we have to install ADB from the SDK? There is NO mention of this in the video tutorials... I am confused.
Not everyone uses Linux. I am on a Windows box here at work and would love to make this happen... Can anyone shed light?

Hello,
@Team Scream, I suggest you look at Imma Wake's video "Downgrade and root Fire HD6/HD7". This one is giving you all you need to move from 4.5.5 to 5.0.1 and get root rights. It's shorter(18 steps) and rather self-explanatory. As an example, I did it today without any hiccups.
I used ADB+Fastboot (the one he made a video about), but didn't had to use any fastboot command. So don't get confused, it's just a rather simple way to get ADB up and running.
If it may be of any help, just know that I had to re setup the driver in the device manager will the tab was in sideload mode.
@powerpoint45 not forgetting ppl who made this tutorial possible, I deeply thank you for the tremendous work you've done! I will give it a shot soon hopping it goes as smoothly as the guide i mention before.
All the best,
EDIT
It all went smooth and easy.
So here is my backlog:
"Fire HD6" on "Fire OS 4.5.5"
Upgrade to 5.0.1 (dev version)
Downgrad to 4.5.3 and grant ROOT access via kingroot. (followed the 18 step tutorial made prior to this one. check his youtube videos. additionnaly I did "adb shell pm block com.amazon.dcp" not mention in the 18, but 37steps tutorial just to be safe about OTA stuff)
Catch up on this tutorial at step12. Upgraded to 5.0 + ROOT + GAPPS + Play Store
@powerpoint45, You may want to swap step 35 and 36 because by the time you reach 35, you can't "su" in "adb shell". In fact, 36 is meant to allow "su" usages as far as i can tell
Due to the above "su" issue, I was scared that during the SuperSU setup(needing Wifi and prior to OTA disable) between step 34 and 36 is that some update happen eventually transforming a piece of cake into nightmare. Is it something to be worried about for ppl following your tutorial?
Lastly, the "System Updates" panel state "Fire OS 5.0.1", but isn't "5.2.2 firmware" + "5.2.0 stock recovery" suppose to increase the OS number to 5.2.X? (that's the rookie question I suppose)
Once again, thank you very much for this great video tutorial and all the best to you stepping into it.

user0x80 said:
Hello,
@Team Scream, I suggest you look at Imma Wake's video "Downgrade and root Fire HD6/HD7". This one is giving you all you need to move from 4.5.5 to 5.0.1 and get root rights. It's shorter(18 steps) and rather self-explanatory. As an example, I did it today without any hiccups.
I used ADB+Fastboot (the one he made a video about), but didn't had to use any fastboot command. So don't get confused, it's just a rather simple way to get ADB up and running.
If it may be of any help, just know that I had to re setup the driver in the device manager will the tab was in sideload mode.
@powerpoint45 not forgetting ppl who made this tutorial possible, I deeply thank you for the tremendous work you've done! I will give it a shot soon hopping it goes as smoothly as the guide i mention before.
All the best,
EDIT
It all went smooth and easy.
So here is my backlog:
"Fire HD6" on "Fire OS 4.5.5"
Upgrade to 5.0.1 (dev version)
Downgrad to 4.5.3 and grant ROOT access via kingroot. (followed the 18 step tutorial made prior to this one. check his youtube videos. additionnaly I did "adb shell pm block com.amazon.dcp" not mention in the 18, but 37steps tutorial just to be safe about OTA stuff)
Catch up on this tutorial at step12. Upgraded to 5.0 + ROOT + GAPPS + Play Store
@powerpoint45, You may want to swap step 35 and 36 because by the time you reach 35, you can't "su" in "adb shell". In fact, 36 is meant to allow "su" usages as far as i can tell
Due to the above "su" issue, I was scared that during the SuperSU setup(needing Wifi and prior to OTA disable) between step 34 and 36 is that some update happen eventually transforming a piece of cake into nightmare. Is it something to be worried about for ppl following your tutorial?
Lastly, the "System Updates" panel state "Fire OS 5.0.1", but isn't "5.2.2 firmware" + "5.2.0 stock recovery" suppose to increase the OS number to 5.2.X? (that's the rookie question I suppose)
Once again, thank you very much for this great video tutorial and all the best to you stepping into it.
Click to expand...
Click to collapse
Ok so first off thank you so much for taking the time to try and help, and forgive me for being needy.
In your post you mention following Imma Wake's video which I tried to do, but the very first step is a brick wall. The YouTube video which supposedly shows how to upgrade to the 5.0 Developer preview has been removed. It is no longer there, so that very crucial first step is one that I cannot take.
Next, in your post, you reference upgrading the Kindle HD6 using both the 5.0 Developer preview AND the 5.01 Developer preview which has me totally confused. I do not see any videos on Imma Wake you tube channel referencing the 5.01 Developer preview. The last thing I want to do is brick my brand new Kindle...
SO, once again, I am back here at square one, stuck. Any chance you can point me to the quick and easy method of upgrading to 5.0 Developer so I can get past that step? I have signed up on Amazon and the developer page indicates that my device will be upgraded within 48 hours, but I am sitting here with time on my hands today and really wanted to give this a shot today.
Thanks.

AFTV stick FW 5.2.1.0 Build 550145120

Hello Fire TV lovers
First to my situation. My AFTV sticks is running FW 5.2.1.0 550144920 and is rooted by Kingo Root. Even after doing an factory reset the stick stays still rooted without running again or installing the Super User app. When doing a factory reset there will be shown an screen at first start after reset with something like "optimizing system..." and runs about 3-5 minutes before the first screen is showing where you can connect the remote.
As some users got already the update for the new 5.2.1.0 build I am still waiting for it. But yesterday I believe I have found the update files in the "./cache" directory... The name is "update-montoya_montoya-550144920-to-550145120". But AFTV sticks still says theres nothing new... I have done a factory reset and the file is still in the cache directory but the update is still not installed. Any ideas?
The file is only about 5.5 mb and when extracting it there is not much more than some patches to the first 5.2.1.0 build. So it seems that this is not an full fw update but only a little patch. That maybe the reason why it is still rootable...???
Does anybody have other AFTV stick update files? Maybe any user got an full update file to newest build?
@rbox do you have some ideas what we can do with this? maybe installing an old fw by replacing the "new" file?
And does someone know if full updates are different from device to device? So not the same file for AFTV 1, AFTV 2 and AFTV stick?
Here is the files if someone is interested... --> https://www.dropbox.com/s/j3esv7xefzk35be/update-montoya_montoya-550144920-to-550145120.bin?dl=0

cuki3r3k83bln said:
Hello Fire TV lovers
First to my situation. My AFTV sticks is running FW 5.2.1.0 550144920 and is rooted by Kingo Root. Even after doing an factory reset the stick stays still rooted without running again or installing the Super User app. When doing a factory reset there will be shown an screen at first start after reset with something like "optimizing system..." and runs about 3-5 minutes before the first screen is showing where you can connect the remote.
As some users got already the update for the new 5.2.1.0 build I am still waiting for it. But yesterday I believe I have found the update files in the "./cache" directory... The name is "update-montoya_montoya-550144920-to-550145120". But AFTV sticks still says theres nothing new... I have done a factory reset and the file is still in the cache directory but the update is still not installed. Any ideas?
The file is only about 5.5 mb and when extracting it there is not much more than some patches to the first 5.2.1.0 build. So it seems that this is not an full fw update but only a little patch. That maybe the reason why it is still rootable...???
Does anybody have other AFTV stick update files? Maybe any user got an full update file to newest build?
@rbox do you have some ideas what we can do with this? maybe installing an old fw by replacing the "new" file?
And does someone know if full updates are different from device to device? So not the same file for AFTV 1, AFTV 2 and AFTV stick?
Here is the files if someone is interested... --> https://www.dropbox.com/s/j3esv7xefzk35be/update-montoya_montoya-550144920-to-550145120.bin?dl=0
Click to expand...
Click to collapse
1) Do you have updates disabled (router or through ADB)? If so enable them and try again.
2) You are rooted why not erase file from ./cache and let it downloade it again, make sure updates are enabled.
3) Is no way to install an older firmware without having recovery, rbox did not release recovery for firestick as of yet.
4) updates are different from unit to unit so do not do install anything release so far or you will brick your stick.

hmmh ok have done nothing but file was removed and everything is like was before... no update done yet...
ota updates are not disabled...

Factory reset won't get rid of root. You have to uninstall it via the SuperSU app using the 3 dots in the right hand corner to remove the keep root backups.

No need for removing root Just wondering why I recieve the update file for newer 5.2.1.0 build but it wont be installed...
If I have root or not is not really interesting for me because I use my AFTVS for BS and RetroArch only... Rooting it was just for fun and is not much usefull as long as rbox does not provide us with recovery and prerooted fw

Before installing an incremental software update, the Fire TV and Fire TV Stick check the integrity of system and recovery. On a rooted device, that integrity check fails and the update is not installed. That is why the incremental update @cuki3r3k83bln found in /cache was just sitting there and never got installed. Normally, after the integrity check fails, the device will then download a full version of the software update. The full update will include a complete copy of system and recovery so it doesn't care about the current state of the device. If installed, the full update will wipe out root (and TWRP if present).
For whatever reason, version 5.2.1.0_550144920 is not downloading the full update of 5.2.1.0_ 550145120 after the integrity check fails. I noticed the same thing happen on a rooted FIre TV 2. I got the Fire TV 2 to download the full 5.2.1.0_550145120 by downgrading to the pre-rooted 5.0.5.1 ROM. On 5.0.5.1, it did the usual download of the incremental update, then failed the integrity check, then download the full 5.2.1.0_550145120 update.
I don't know if the old Fire OS 3 process of manually upgrading/downgrading the OS still works on Fire OS 5. I haven't tried it, but you can try to downgrade to a stock full version. If you downgrade successfully, I'm sure it will then update to 5.2.1.0_550145120. Here are full updates if you want to try:
5.0.5 (537174420) Full
http://amzdigitaldownloads.edgesuit...te-kindle-montoya-54.5.3.7_user_537174420.bin
5.0.5.1 (537175520) Full
https://amzdigital-a.akamaihd.net/o...te-kindle-montoya-54.5.3.7_user_537175520.bin
Personally, I would suggest just sitting and waiting. Rbox is working on TWRP and pre-rooted ROMs for the Stick. When that's released, you'll be able to downgrade safely if you want. Or, more likely, Amazon will figure out why the Stick is not downloading the latest full update and fix it before then.
Lastly, if you connect via ADB and run the command
Code:
adb shell pm clear com.amazon.device.software.ota
it will cause the device to forget that it failed the integrity check. This will make it re-download the incremental update and redo the integrity check. I would do this once a day in hopes that Amazon fixes the issue preventing the full update from downloading.

AFTVnews.com said:
Before installing an incremental software update, the Fire TV and Fire TV Stick check the integrity of system and recovery. On a rooted device, that integrity check fails and the update is not installed. That is why the incremental update @cuki3r3k83bln found in /cache was just sitting there and never got installed. Normally, after the integrity check fails, the device will then download a full version of the software update. The full update will include a complete copy of system and recovery so it doesn't care about the current state of the device. If installed, the full update will wipe out root (and TWRP if present).
For whatever reason, version 5.2.1.0_550144920 is not downloading the full update of 5.2.1.0_ 550145120 after the integrity check fails. I noticed the same thing happen on a rooted FIre TV 2. I got the Fire TV 2 to download the full 5.2.1.0_550145120 by downgrading to the pre-rooted 5.0.5.1 ROM. On 5.0.5.1, it did the usual download of the incremental update, then failed the integrity check, then download the full 5.2.1.0_550145120 update.
I don't know if the old Fire OS 3 process of manually upgrading/downgrading the OS still works on Fire OS 5. I haven't tried it, but you can try to downgrade to a stock full version. If you downgrade successfully, I'm sure it will then update to 5.2.1.0_550145120. Here are full updates if you want to try:
5.0.5 (537174420) Full
http://amzdigitaldownloads.edgesuit...te-kindle-montoya-54.5.3.7_user_537174420.bin
5.0.5.1 (537175520) Full
https://amzdigital-a.akamaihd.net/o...te-kindle-montoya-54.5.3.7_user_537175520.bin
Personally, I would suggest just sitting and waiting. Rbox is working on TWRP and pre-rooted ROMs for the Stick. When that's released, you'll be able to downgrade safely if you want. Or, more likely, Amazon will figure out why the Stick is not downloading the latest full update and fix it before then.
Lastly, if you connect via ADB and run the command
Code:
adb shell pm clear com.amazon.device.software.ota
it will cause the device to forget that it failed the integrity check. This will make it re-download the incremental update and redo the integrity check. I would do this once a day in hopes that Amazon fixes the issue preventing the full update from downloading.
Click to expand...
Click to collapse
Surely if you manage to downgrade a stick using the method you have mentioned you can stop it upgrading by not using the official charger (plug usb into tv etc).
If this is possible it would be quite good for many users of the stick who would like to be on 5.0.5 to then be able to use the home button click double click feature in firestarter 3.2.3 ? i know i certainly would but unsure if the method would brick the device ?

Downgrade is possible
@AFTVnews.com WOW!!! Big Thx Downgrading worked perfectly!!!
What have I done? Very simple...
1. Downloaded the 5.0.5.1 FW from AFTVnews.com link above and then followed the tutorial he has linked...
2. Renamed the filename to update.bin
3. Pushed the update.bin via adbLink from Mac to AFTV stick
4. Opened ADB Shell via adbLink on Mac and moved update.bin from "sdcard" to "cache" directory...
Code:
su
cd /sdcard
mv ./update.bin /cache/
5. Then done some more steps from AFTVnews guide...
Code:
cd /cache/recovery
echo --update_package=/cache/update.bin > command
adb reboot recovery
Few seconds after this the recovery process started and some minutes later my AFTV stick rebooted back and was running 5.0.5.1 without problems. I startet ADB Shell again and the "su" command was not working anymore so my device has been "derooted". Some minutes later I checked the update status and the stick started downloading newest 5.2.1.0 build. After rebooting and waiting some minutes everything worked fine and then I have done a factory reset and now I am using a clean and fresh 5.2.1.0 AFTV stick
So lets say: FW 5.0.2.1 can be downgraded
I don't know if this helps someone but maybe someone would like to use older versions or we could run an prerooted room without custom recovery or or or...

cuki3r3k83bln said:
@AFTVnews.com WOW!!! Big Thx Downgrading worked perfectly!!!
What have I done? Very simple...
1. Downloaded the 5.0.5.1 FW from AFTVnews.com link above and then followed the tutorial he has linked...
2. Renamed the filename to update.bin
3. Pushed the update.bin via adbLink from Mac to AFTV stick
4. Opened ADB Shell via adbLink on Mac and moved update.bin from "sdcard" to "cache" directory...
Code:
su
cd /sdcard
mv ./update.bin /cache/
5. Then done some more steps from AFTVnews guide...
Code:
cd /cache/recovery
echo --update_package=/cache/update.bin > command
adb reboot recovery
Few seconds after this the recovery process started and some minutes later my AFTV stick rebooted back and was running 5.0.5.1 without problems. I startet ADB Shell again and the "su" command was not working anymore so my device has been "derooted". Some minutes later I checked the update status and the stick started downloading newest 5.2.1.0 build. After rebooting and waiting some minutes everything worked fine and then I have done a factory reset and now I am using a clean and fresh 5.2.1.0 AFTV stick
So lets say: FW 5.0.2.1 can be downgraded
I don't know if this helps someone but maybe someone would like to use older versions or we could run an prerooted room without custom recovery or or or...
Click to expand...
Click to collapse
Awesome. I'm glad it worked out. Thanks for reporting back that downgrading still works.

Is this usable for the Fire TV Box Gen. 1 to downgrade and make it rootable?
Gesendet von meinem E6653 mit Tapatalk

Why not? Try it out... Have tried it just for fun and it worked ? Would do it for you but have the stick only

cuki3r3k83bln said:
Why not? Try it out... Have tried it just for fun and it worked �� Would do it for you but have the stick only
Click to expand...
Click to collapse
i tried the steps posted yesterday and couldnt get it to work, any chance you could post the exact steps you used ? id like to downgrade my firestick to 5.05 to get back the firestarter features. thanks

cuki3r3k83bln said:
Why not? Try it out... Have tried it just for fun and it worked ? Would do it for you but have the stick only
Click to expand...
Click to collapse
I think I first need the Firmware files ver. 5.05 for AFTV, not AFTV Stick. Can someone help me out?
Gesendet von meinem E6653 mit Tapatalk

sconnyuk Well you have to download the 5.0.5.1 from ATVnews his link, rename it to update.bin and then push it via adbfire on mac or pc (or you can use apps2fire on android devices)... I did simply that and then I did open the adb shell and simply typed what I have written... Your device has to be rooted via Kingo Root to access the cache directory... What have you done or what errors did you get?

i get
cannot stat 'update.bin : No such file or directory
after i try push update.bin to /cache
im using windows 10 64bit
---------- Post added at 08:55 PM ---------- Previous post was at 08:51 PM ----------
my stick is 5.2.1.0 rooted with super user (kingo) and trying to push the 5.0.5 file AFTVnews posted.

Hmmh did you try to use adbLink and then you simply need to select "sdcard" as destination folder for uploading it? sorry dont know how and where you uploadet your file...

I have adb drivers installed on windows pc. i have followed all steps posted by AFTVnews until i get to adb push update.bin /cache and i get the error cannot stat 'update.bin' : No such file or directory
Im now going to try adblink with your added commands and see what i get.

Ok, tried the way you did it with the adblink tool and it worked
Thanks for posting your success as i would of just gave up.
This is good to know and i guess theres alot of people who have updated from 5.0.5 and lost firestarter features who would like them back.
All my apps are intact, i did have to re-run kingoroot to get root.
I have disabled updates straight after booting to my downgraded 5.0.5 stick. (pm disable com.amazon.device.software.ota), thanks cuki3r3k83bln and AFTVnews, im sure there is alot of people who will use this info to do as i just did.

Next project is how to mount a good working NFS folder as directory into filesystem OR using external usb disk with y-otb-cable but that will be done when we got a prerooted rom because I dont trust kingoroots exploit not much

cuki3r3k83bln said:
Next project is how to mount a good working NFS folder as directory into filesystem OR using external usb disk with y-otb-cable but that will be done when we got a prerooted rom because I dont trust kingoroots exploit not much
Click to expand...
Click to collapse
Im wanting to try replacing Kingo roots SuperUser app with chainfires SuperSu.
I know a few people have tried this without success on 5.2.1.0 im wondering if its different on 5.0.5 ?
Im fairley sure that a messed up stick that wont boot because of changed su files is recoverable as i recovered my stick after deleting su files in root folder. Others have had non booting sticks from using various methods to change to SuperSu and with the way ive pointed out to them of getting it back up and running it seems they have had success also.
The way to do it is to plug the stick into a pc/laptop and run kingo roots windows tool to root it, this in turn replaces the modified su files and gets the stick back up and running.
Have you any idea on a version of Chainfires Su that could work ?