Accidentally hit do not install when on root page
what do i do?
I reinstalled TWRP yesterday and updated 5.2.0 to 5.2.2 and it went off without a hitch. Thank you! Here's some minor feedback:Update3: time to update the instructions for 5.2.2.
Update2: siegesoldier has captured the FireOS 5.2.2 (Lollipop), and pretty much blazed the entire trail (go give him lots of thanks!) http://xdaforums.com/fire-hd/general/lolipop-ota-capture-t3141810
HDXposed: I didn't need this to fix play store (but we all resort to whatever works.) I fixed it by renaming /system/etc/hosts file to hostsBAK and rebooting. (I'm going to activate Adaway, which may reverse the fix, but so far so good.) Maybe you can add this to the HDXposed fix. Personally, I'm a little leary of throwing HDX xposed modules at our device, but as said, must confirm my fix lasts for the long haulFireOS 5.2.2 is based on Lollipop 5.1, so you will need Xposed for 5.1, and also GAPPS don't work right away, and need to have HDXposed module enabled.
I didn't skip factory reset and have a question: This didn't wipe data and I don't understand why. (Same thing happened when i updated 4.5.4 to lollipop). All my "personal" dirs are still in /data, and settings like ES FE favorites, are active again after reinstalling the app. Can you tell me why? I thought wipe data meant, uh, wipe dataFor lazy ones I recommend skipping factory reset in Step 1) below if you already have 5.2.0.
. . .
To update to 5.2.2 from 5.2.0, you need to boot into TWRP, and in order to achieve this, you flash 4.5.3 bootloaders and TWRP as in here :
http://xdaforums.com/showpost.php?p=62011272&postcount=2 [only step 1) is necessary]
1) boot into TWRP, and, in a single session (!!!!!)
do factory reset (skip if you already have 5.2.0 ?),
I reinstalled TWRP yesterday and updated 5.2.0 to 5.2.2 and it went off without a hitch. Thank you! Here's some minor feedback:
HDXposed: I didn't need this to fix play store (but we all resort to whatever works.) I fixed it by renaming /system/etc/hosts file to hostsBAK and rebooting. (I'm going to activate Adaway, which may reverse the fix, but so far so good.) Maybe you can add this to the HDXposed fix. Personally, I'm a little leary of throwing HDX xposed modules at our device, but as said, must confirm my fix lasts for the long haul
I didn't skip factory reset and have a question: This didn't wipe data and I don't understand why. (Same thing happened when i updated 4.5.4 to lollipop). All my "personal" dirs are still in /data, and settings like ES FE favorites, are active again after reinstalling the app. Can you tell me why? I thought wipe data meant, uh, wipe data
Thanks again :good:
Update3: time to update the instructions for 5.2.2.
The 5.2.0 writing is hidden, click below:
#################################################
5.2.0
Update : Quite a few successful reports of this procedure working well, so do pay attention, but don't let your hands shake too much as do this
This is a blueprint for a reasonably safe journey to rooted Lollipop. The key is to flash 5.2.0 recovery right after flashing 5.2.0 stock, this way there is an option to recover if something goes wrong.
Disclaimer : most of the info is compiled from other threads. Myself, I have tested flashing the attached 5.2.0 stock recovery zip from TWRP, it works fine.
Big credit here hawkazn for blazing the trail, and getting to a working rooted Lollipop first, then dumping the stock recovery:
http://xdaforums.com/showpost.php?p=62009468&postcount=75
0) I assume you have TWRP installed and working, which means you've followed the guide to step 3) only, [and skip all the steps after 3) , since nobody is going to care, no extra credit here!]:
http://xdaforums.com/fire-hd/general/root-v2-0-fireos-4-5-4-gapps-t3150613
1) boot into TWRP, and, in a single session (!!!!!)
do factory reset,
flash the 5.2.0 update from this post (the official 5.2.0 zip will work just fine):
http://xdaforums.com/fire-hd/general/lolipop-ota-capture-t3141810
flash the attached 5.2.0_stock_recovery_only.zip
flash Xposed for Lollipop, and GAPPS (see the note below for details)
and finally, when TWRP asks you to install root, say "yes"
Thanks to Remolten, there is a very detailed write up regarding all of this:
http://xdaforums.com/showpost.php?p=62018692&postcount=6
Note that this is the last time you see TWRP (unless you do what I recommend in post #2), so take the opportunity to flash other stuff such as Xposed, thanks to siegesoldier for pointing this out:
http://xdaforums.com/showpost.php?p=62021411&postcount=13
Update:GAPPS can be flashed safely at this step as well (and should be flashed here!!!), 2 reports have confirmed this:
http://xdaforums.com/showpost.php?p=62208098&postcount=16
http://xdaforums.com/showpost.php?p=62296848&postcount=47
Let's pause for a second and realize what we did here - we've put full stock 5.2.0, added root, and, most importantly, overwrote TWRP with 5.2.0 stock recovery.
2) reboot to recovery, you should see stock 5.2.0 recovery (this is just to see if it works, for troubleshooting, but otherwise a meaningless step from the update perspective ...)
3) reboot to 5.2.0 OS, and hopefully, it works. Install SuperSu to manage root requests.
4) if step 3) fails, you get into working 5.2.0 recovery by pressing "Pwr & Vol+". At this point you sideload 4.5.3 stock, and go back to step 0). Come back here and ask questions (and thank me again for being able to recover so easily !!! )
GAPPS can also be installed via the JMZ tool (not recommended, and skip if you flashed GAPPS via TWRP), there are reports that everything works just fine:
http://xdaforums.com/fire-hd/orig-development/tool-jmz-fire-hd-7-tool-gapps-disable-t3113655
The next post discusses how to get into TWRP temporarily with 5.2.0 installed, and come back to 5.2.0
#################################################
Update2: siegesoldier has captured the FireOS 5.2.2 (Lollipop), and pretty much blazed the entire trail (go give him lots of thanks!)
http://xdaforums.com/fire-hd/general/lolipop-ota-capture-t3141810
FireOS 5.2.2 is based on Lollipop 5.1, so you will need Xposed for 5.1, and also GAPPS don't work right away, and need to have HDXposed module enabled. Update: a simpler way to fix GAPPS is suggested by DoLooper (without HDXposed):
http://xdaforums.com/showpost.php?p=62446653&postcount=64
For lazy ones I recommend skipping factory reset in Step 1) below if you already have 5.2.0.
0) I assume you have TWRP installed and working (if coming from 4.5.x):
http://xdaforums.com/fire-hd/general/root-v2-0-fireos-4-5-4-gapps-t3150613
To update to 5.2.2 from 5.2.0, you need to boot into TWRP, and in order to achieve this, you flash 4.5.3 bootloaders and TWRP as in here :
http://xdaforums.com/showpost.php?p=62011272&postcount=2
[only step 1) is necessary]
A report of a successful update from 5.2.0 to 5.2.2 has been posted by DoLooper, so this trail has been blazed!
1) boot into TWRP, and, in a single session (!!!!!)
do factory reset (skip if you already have 5.2.0 ?),
flash the 5.2.2 update from this thread:
http://xdaforums.com/fire-hd/general/lolipop-ota-capture-t3141810
flash the attached 5.2.0_stock_recovery_only.zip
flash Xposed for Lollipop 5.1
http://xdaforums.com/xposed/super-alpha-posted-permission-xposed-t3072979
flash Pico GAPPS for 5.1
http://www.androidrootz.com/2015/03/download-android-51x-lollipop-pa-gapps.html
2) reboot to recovery, you should see stock 5.2.0 recovery (this is just to see if it works, for troubleshooting, but otherwise a meaningless step from the update perspective ...)
3) reboot to 5.2.2 OS, and hopefully, it works. Install SuperSu to manage root requests.
4) if step 3) fails, you get into working 5.2.0 recovery by pressing "Pwr & Vol+". At this point you sideload 4.5.3 stock, and go back to step 0). Come back here and ask questions (and thank me again for being able to recover so easily !!! )
The next post discusses how to get into TWRP temporarily with 5.2.2 installed, and come back to 5.2.2
Please Use up to date gapps from tk: http://xdaforums.com/android/software/tk-gapps-t3116347
Cause these gapps you linked are not up to date!
b) what is your actual concern? GAPPS tend to update themselves all the time, so whatever you flash into /system, it will fairly soon become obsolete anyway because the update will download fresher versions
and
a) is there any point in quoting the entire guide?
I reinstalled TWRP yesterday and updated 5.2.0 to 5.2.2 and it went off without a hitch. Thank you! Here's some minor feedback:
HDXposed: I didn't need this to fix play store (but we all resort to whatever works.) I fixed it by renaming /system/etc/hosts file to hostsBAK and rebooting. (I'm going to activate Adaway, which may reverse the fix, but so far so good.) Maybe you can add this to the HDXposed fix. Personally, I'm a little leary of throwing HDX xposed modules at our device, but as said, must confirm my fix lasts for the long haul
I didn't skip factory reset and have a question: This didn't wipe data and I don't understand why. (Same thing happened when i updated 4.5.4 to lollipop). All my "personal" dirs are still in /data, and settings like ES FE favorites, are active again after reinstalling the app. Can you tell me why? I thought wipe data meant, uh, wipe data
Thanks again :good:
Sorry. Better get out your red pencil again, I spoke too soon. Play store has stopped opening. After trying long time to reinvent @siegesoldier's wheel, I am going to resort to HDXposed.Also, I've added the reference on the "hosts" file trick to the guide!
I agree (for what that's worth!) Also was wondering whether we should be flashing 5.2.2 recovery.I am now thinking that in post #2 I should probably update 5.2.0 bootloaders to 5.2.2, since these are different Lollipop versions. So, just in case
Thanks for this bro! I can confirm this process works, and I will show the steps I took here (clarification for people who want to do this).
1. I started on 4.5.4 + Root + TWRP with adb installed on my Mac
2. I connected fire to computer, and did (in terminal window)
adb backup -apk -shared -all ~/Downloads
to save my data before factory reset (this should work on Mac + Linux).
3. Rebooted to TWRP
4. Performed a Factory Reset (the default one under Wipe on TWRP)
5. Installed the 5.2.0 bin file with adb sideload
6. Installed 5.20 stock recovery with adb sideload
7. Went to Reboot page and chose reboot recovery
8. TWRP will prompt you to install root, do it
9. It will then reboot into stock Amazon recovery, choose to reboot your system
10. Mine took forever, but it finally booted into 5.2.0
11. If you're plugged into the computer, it gives you the option to enable usb debugging, do this
12. I completed the setup process
13. Downloaded SupersSU from here on computer
14. Used
adb install -r supersu.apk
(or whatever your's is named)
15. Check you have root by running
adb shell
su
16. You should have root installed!
17. Now run
adb restore backup.ab
which will restore your data (apps)
18. SKIP UNLESS YOU HAD XPOSED INSTALLED If you had Xposed installed, it is not compatible now, so uninstall all of your modules (if you want to save space). I believe the problem with Xposed is that we need to change a build.prop sdk/api value, but that's something for us to figure out later.
19. Install jmz fire tools from here
20. Run it and choose install Gapps, your device will reboot
21. Sucess!!! Lollipop + Root + Gapps
Anyways, good luck to everyone I hope this helps someone in the future!
---------- Post added at 10:33 AM ---------- Previous post was at 10:32 AM ----------
I fixed this by running
adb install -r eu.chainfire.supersu.apk
or whatever your supersu file is named.
Install HDXposed. It's not going to work without it atmI completed all steps and succeeded. My fire 6 was rooted with lollipop OS and gapps
I was happy when google play could work. However, after I signed in google account, it immediately crashed.
I've tried doing "force stop" and opening again but it still does not work.:crying:
:crying::crying:
can anybody help me please? thanks
plus, I installed lollipop 5.1 (fire 5.2.2), but it shows "fireOS 5.0" in setting. I dont know what was wrong?
Yes, play store seems not to be working on latest lollipop. The update at top of this post seems to be the only fix.I was happy when google play could work. However, after I signed in google account, it immediately crashed.
That's how it displays. If build date is July 20, you've got 5.2.2.plus, I installed lollipop 5.1 (fire 5.2.2), but it shows "fireOS 5.0" in setting. I dont know what was wrong?
Solid info here, thanks again for finding the fix!!!
Sorry. Better get out your red pencil again, I spoke too soon. Play store has stopped opening. After trying long time to reinvent @siegesoldier's wheel, I am going to resort to HDXposed.
I agree (for what that's worth!) Also was wondering whether we should be flashing 5.2.2 recovery.
Hi, I'm unable to install 5.2.2 over 4.5.3/4.5.4 rooted with TWRP. The flash process is stopped to "Patching system image unconditionally..." and the only way to exit is forcing with power button and in this case TWRP is unable anymore to mount /system, so I have to install 5.2.0 recovery and sideload 4.5.3 to unbrick the device. Any solution? Very thanks
In TWRP you should try to format /system as ext3, then format as ext4. Then try the 5.2.2 update again. If it fails, don't reinstall 4.5.3, but come back here with questions. You will still have TWRP working, so that's good enough.
Updating partition details...
...done
Full SELinux support is present.
MTP Enabled
Installing '/sdcard/Fire5.2.2/update-kindle-devpreview_ariel-20.5.2.2_user_522041550.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Patching system image unconditionally...
Formatting /system with ext3/ext4 solved the mount error but 5.2.2 still fails to install. Here the log:
adb shell
su
exit
exit
3a1f3cd1ef405eaeec719eaeb41ab791 /dev/block/mmcblk0p3
d605e31a180652c65d6957b58d2d8501 /dev/block/mmcblk0p5
305a5546ff8960b51cd573b59a05cde6 /dev/block/mmcblk0p7
C:\Program Files\Minimal ADB and Fastboot>adb devices
List of devices attached
0000000000000XXX device
C:\Program Files\Minimal ADB and Fastboot>adb shell
shell@ariel:/ $ su
su
root@ariel:/ # cd /sdcard/gscript
cd /sdcard/gscript
root@ariel:/sdcard/gscript # ls
ls
453_key_images.zip
453_tee1.img
453_twrp.img
453_uboot.img
root@ariel:/sdcard/gscript # dd if=453_tee1.img of=/dev/block/mmcblk0p3
dd if=453_tee1.img of=/dev/block/mmcblk0p3
6364+1 records in
6364+1 records out
3258876 bytes transferred in 0.543 secs (6001613 bytes/sec)
root@ariel:/sdcard/gscript # dd if=453_uboot.img of=/dev/block/mmcblk0p5
dd if=453_uboot.img of=/dev/block/mmcblk0p5
414+1 records in
414+1 records out
212116 bytes transferred in 0.041 secs (5173560 bytes/sec)
root@ariel:/sdcard/gscript # dd if=453_twrp.img of=/dev/block/mmcblk0p7
dd if=453_twrp.img of=/dev/block/mmcblk0p7
14004+0 records in
14004+0 records out
7170048 bytes transferred in 1.103 secs (6500496 bytes/sec)
root@ariel:/sdcard/gscript # exit
exit
shell@ariel:/ $ exit
exit
C:\Program Files\Minimal ADB and Fastboot>adb reboot recovery
Yahoo! I'm either almost there or am no longer rooted. adb shell, su doesn't return #-sign, but I can "cd" and "ls" all around /system. SuperSU installer says I'm "not fully rooted," but if you press Play (store) Amazon wants to open appstore of course, and no TWRP. Tried adb install, which failed:
Desktop>adb install eu.chainfire.supersu.apkGuess I'm partially rooted? Need some reassurance because had a little trouble flashing (which I won't explain unless I must) . Anyway, I have 5.2.0 recovery and if superuser is as expected, I'll go for post 2 (i think)! Thanks!
3017 KB/s (5904943 bytes in 1.911s)
pkg: /data/local/tmp/eu.chainfire.supersu.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
Managed to get the upgrade from reading the last thread, but no TWRP. Thanks!!
This happened to me as well... the su binary was in /system/xbin but wasn't working, and the app said I had to flash or install from the Play Store. I copied the Superuser.apk to /sdcard and installed it device side, worked fine.
This happened to me as well... the su binary was in /system/xbin but wasn't working, and the app said I had to flash or install from the Play Store. I copied the Superuser.apk to /sdcard and installed it device side, worked fine.Yahoo! I'm either almost there or am no longer rooted. adb shell, su doesn't return #-sign, but I can "cd" and "ls" all around /system. SuperSU installer says I'm "not fully rooted," but if you press Play (store) Amazon wants to open appstore of course, and no TWRP. Tried adb install, which failed:
Desktop>adb install eu.chainfire.supersu.apkGuess I'm partially rooted? Need some reassurance because had a little trouble flashing (which I won't explain unless I must) . Anyway, I have 5.2.0 recovery and if superuser is as expected, I'll go for post 2 (i think)! Thanks!
3017 KB/s (5904943 bytes in 1.911s)
pkg: /data/local/tmp/eu.chainfire.supersu.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]