Fire OS 5.0.0 Help? - Fire HD 6 and 7 Q&A, Help & Troubleshooting

Hello, I have a Fire HD6 Running Fire OS 5.0.0. I am trying to use the file for 5.2.2u2 to update. When I go to settings>>device options>>system updates>>check now, it says there are no updates. If I put the file at /sdcard using a computer and turn on airplane mode, I can hit the update button and it looks like it is going to update, but when it reboots, it says i am still on 5.0.0. ADB works, but adb reboot recovery just boots normally. I had TWRP until I updated to 5.0.0. I really need help. Thanks in advance.

See if you can push file to /cache. It should upgrade from there. If you are (or once were) rooted, first reverse any pm commands you did to block OTA (pm enable com.amazon.dcp and/or pm enable com.amazon.otaverifier). If commands fail, use gatesjr Debloater tool (from here on xda) to make sure packages are enabled. Since the upgrade will break root anyway, you may be able to get OTA upgrade by turning on wifi and doing "check now."

DoLooper said:
See if you can push file to /cache. It should upgrade from there. If you are (or once were) rooted, first reverse any pm commands you did to block OTA (pm enable com.amazon.dcp and/or pm enable com.amazon.otaverifier). If commands fail, use gatesjr Debloater tool (from here on xda) to make sure packages are enabled. Since the upgrade will break root anyway, you may be able to get OTA upgrade by turning on wifi and doing "check now."
Click to expand...
Click to collapse
Is there any way to get TWRP and Root at 5.2.2u2 and get play store, or am I doomed to have an unrooted device forever? Will update in a few minutes about things you said to try.
Update: adb push 5.2.2u2file /cache results in permission denied. Trying to enable packages via adb also results in permission denied. Debloater says no packages are blocked. I would really appreciate it if I could get root and playstore on this thing. Thanks in advance.

Well, since you're unrooted without recovery you may have to go the replacement route. But first see if @bibikalka has an alternative.

Related

ATT 2.3.6 OTA failed

I finally gave in to the update nagging screen and tried to update.
My phone was rooted with preinstall method, nothing else.
I was on 2.3.4 (4.5.91).
I installed RootKeeper and unrooted before the update (kept root backup).
The phone downloaded the update, restarted, and I saw the Android Icon and an "unpacking" progress bar. The bar stopped about half way and the icon turned into an exclamation point. I thought I was toast....
The phone rebooted fine, everything still there. I got a message box "Update failed" once I got on my home screen. The phone is still 2.3.4. The update nagging is gone.
I have pretty rare reboots, maybe 2 a month. I am quite happy with it.
Anyone had the same issue? Should I even bother going to 2.3.6?
The only thing I am really missing on the Atrix is HDMI mirroring option with 720p or 1080p up-conversion.
How can I get the cause for the "fail"? Should I use the Moto USB method?
I wouldnt mind going to CM9 but I want the Finger Sensor, Camera etc all to work. I dont want to loose any current functionality going to CM9 and its not there yet, correct?
Thanks!
I would just stay where you are at. Unless you really want the mirroring. You seem to not mind stock so I would wait for Moto to release ICS for the Atrix. They put it on the list.
if you only rooted, did nothing else that requires root (freeze apps, put files in /system, etc) and did not unlock the bootloader, just unroot and then apply the 2.3.6. update.
Code:
1. Open Android Terminal Emulator (ADB)
2. Type in the following commands, hitting ENTER after each line of code: (after typing 'su' below, look for the Superuser request and approve it, you can only continue if you get the # prompt.
Code:
su
mount -o rw,remount /dev/block/mmcblk0p12 /system
mount -o rw,remount /dev/block/mmcblk0p17 /preinstall
rm /system/bin/su
rm /preinstall/sqlite3
rm /preinstall/dosu
rm /preinstall/Superuser.apk
rm /preinstall/su
reboot
3. Let the phone reboot fully and then go into Settings > Applications > Manage Applications > find Superuser and uninstall it just like any other app.
thx guys,
so you are saying that it failed because the unroot in rootkeeper did not do it right?
so with the manual unroot it should work? is there anyway to see why the update failed? log file or smth?
Thanks
spacev said:
thx guys,
so you are saying that it failed because the unroot in rootkeeper did not do it right?
so with the manual unroot it should work? is there anyway to see why the update failed? log file or smth?
Thanks
Click to expand...
Click to collapse
There have been posts in various 2.3.6 threads where rootkeeper did not work if you used the fastboot preinstall method.
It should work if you manually unroot as long as everything else is stock.
for seeing why the update failed, hold the Volume up and power button when the error appears and you should see some sort of error msg...never tried it myself though.
I have the same issue. I used the preinstall root as well as unroot. I have not found a way to install the update. I tried OTA (I am locked) and I also tried to install from SD.
No dice
otter9309 said:
I have the same issue. I used the preinstall root as well as unroot. I have not found a way to install the update. I tried OTA (I am locked) and I also tried to install from SD.
No dice
Click to expand...
Click to collapse
Did you undo everything that requires root access prior to applying the OTA? I usually do the following prior to an OTA (and redo once the OTA is applied):
uninstall Swype beta, restore stock Swype files (the so and apk files)
move ringtones out of /system/media
Help Needed
Hi All,
I am a newbie here and I am not sure if my question makes any sense. Couple weeks back, I bought an Atrix 4g (US version), an unlocked version (the seller told me that this phone is unlocked using AT&T code) and I am using it with Vodafone (India) sim. It works perfectly and so far I didnt face any problems with this phone. But last week, I got an alert in phone saying that software update (2.3.4.5.141) is available for AT&T users and enable wifi to download. However, I didnt download and install the update as I was not sure why is it saying the update is available only for AT&T users. Also wherever I read about this software udpate, the name 'AT&T users' come along with that.
So my doubt here is, what will happen if I, who is not an AT&T user, download and install the software update in my phone ? will it cause any issues in the phone (like getting locked again or bricking the phone)
I have not done any modification like rooting or installing custom ROM and things like that and I am using the phone as I recieved it.
Thanks in advance for your help.
-Qaddaffi

[Q] rooting thedigiland DL701Q, version 4.4.0

hi, i have a digiland tablet that i have tried rooting without success. its model is DL701Q, version 4.4.0. i have tried all of the rooting methods that i could find. from my investigation, there appears to be no specific rooting method for the version and model.
has anyone with this tablet successfully rooted it yet?
I find root genius to work on it.
wkLeon said:
I find root genius to work on it.
Click to expand...
Click to collapse
Thanks! It worked. The root program took a little while to do it, but it worked.
Failed
Root Genius rebooted the device several times, then showed failure in rooting. Nothing critical - it did not work however.
This is AFTER there was a 130MB OTA update "Wireless Update" that 'fixed some security issues' and I had already applied it wondering what it would do.
Go into About Phone and you will see Wireless Update as the second option below System Update. Hold off on applying it if you want root. As you will also lose root when applying it.
Off-the-shelf:
>adb shell
produces a $ prompt instead of a # prompt like it used to.
These devices are rootable off-the-shelf. Once the OTA has been applied, not at this time.
See also:
http://forum.xda-developers.com/chef-central/android/help-rooting-digiland-tablet-dl701q-t2960712
http://forum.xda-developers.com/android/general/digiland-dl700d-tips-tricks-t2867764
http://forum.xda-developers.com/android/general/digiland-dl700d-tablet-kit-kat-t2851783
http://forum.xda-developers.com/android/help/digiland-android-tablet-root-t2816435 (four pages)
In short, -and I read all the prior threads, so this is a summary to-date-, if you accept the update OTA, you will lose adb shell root access, and Root Genius will no longer work.
It does seem to work on the device off-the-shelf (without applying the OTA).
stock recovery and fastboot access
ndrsconschrtysvcs said:
Root Genius rebooted the device several times, then showed failure in rooting. Nothing critical - it did not work however.
This is AFTER there was a 130MB OTA update "Wireless Update" that 'fixed some security issues' and I had already applied it wondering what it would do.
Go into About Phone and you will see Wireless Update as the second option below System Update. Hold off on applying it if you want root. As you will also lose root when applying it.
Off-the-shelf:
>adb shell
produces a $ prompt instead of a # prompt like it used to.
These devices are rootable off-the-shelf. Once the OTA has been applied, not at this time.
See also:
http://forum.xda-developers.com/chef-central/android/help-rooting-digiland-tablet-dl701q-t2960712
http://forum.xda-developers.com/android/general/digiland-dl700d-tips-tricks-t2867764
http://forum.xda-developers.com/android/general/digiland-dl700d-tablet-kit-kat-t2851783
http://forum.xda-developers.com/android/help/digiland-android-tablet-root-t2816435 (four pages)
In short, -and I read all the prior threads, so this is a summary to-date-, if you accept the update OTA, you will lose adb shell root access, and Root Genius will no longer work.
It does seem to work on the device off-the-shelf (without applying the OTA).
Click to expand...
Click to collapse
Opps, meant to reply in the this thread. See my other post:
forum.xda-developers.com/showpost.php?p=57557683&postcount=35

Root DOB1, Lollipop..

http://forum.xda-developers.com/galaxy-s5/general/sm-g900f-root-android-5-0-t2963451
Soon...
Are you saying we can't root?
I personally havent ever seen that post as i just stick mainly to the tmobile board, not the unified board.
But i have root on DOB1.
Just use odin (3.07) and flash the CF-Auto-Root for the G900T ( even though the link on the CF-auto-Root website says for 4.4.2)
I just got the phone, it was updated to Lollypop, I would rather put a rom on it anyways, do I need to revert back or something? some help would be nice, I am new to this Tmobile phone.
joachim123 said:
I personally havent ever seen that post as i just stick mainly to the tmobile board, not the unified board.
But i have root on DOB1.
Just use odin (3.07) and flash the CF-Auto-Root for the G900T ( even though the link on the CF-auto-Root website says for 4.4.2)
Click to expand...
Click to collapse
That's what I thought. I usually just flash a recovery and flash super su.
I rooted my device just fine after updating to 5.0 with the cf auto root for kitkat... worked like a charm on lollipop 5.0
So does any twrp recovery .
Sent from my Tmobile S5 on Lollipop 5.0
SuperSU installed but no SU
Hi,
Just installed the DOB1 build, installed Philz recovery which worked OK and also installed the SuperSU ZIP through recovery (UPDATE-SuperSU-v1.94.zip) .
Everything seemed fine. I launched several applications (BusyBox, Titanium Backup, terminal emulation) and all of them prompted SuperSU to grant root permission and I acknowledged the permission. SuperSU app itself says that root is enabled.
BUT - it seems that even though SuperSU believes it gives root permission - it does not. The apps keeps asking (and "granted" root per the toast message) but they do not get root and keep asking for that after 30 sec. or so.
I also tried terminal emulation. At the shell prompt I've entered "su", immediately I've got the prompt to allow root, I clicked OK and the in the terminal emulation the cursor just got stuck. never got the "#" prompt for root access.
If someone was able to actually grant root access to the apps, can you please share the steps you've done that? following the posts through Philz' recovery and root did not help, I did follow the same steps I've done before upgrading to lollipop...
Thanks,
Gil.
---------- Post added at 02:30 PM ---------- Previous post was at 02:19 PM ----------
gilbnx said:
Hi,
Just installed the DOB1 build, installed Philz recovery which worked OK and also installed the SuperSU ZIP through recovery (UPDATE-SuperSU-v1.94.zip) .
Everything seemed fine. I launched several applications (BusyBox, Titanium Backup, terminal emulation) and all of them prompted SuperSU to grant root permission and I acknowledged the permission. SuperSU app itself says that root is enabled.
BUT - it seems that even though SuperSU believes it gives root permission - it does not. The apps keeps asking (and "granted" root per the toast message) but they do not get root and keep asking for that after 30 sec. or so.
I also tried terminal emulation. At the shell prompt I've entered "su", immediately I've got the prompt to allow root, I clicked OK and the in the terminal emulation the cursor just got stuck. never got the "#" prompt for root access.
If someone was able to actually grant root access to the apps, can you please share the steps you've done that? following the posts through Philz' recovery and root did not help, I did follow the same steps I've done before upgrading to lollipop...
Thanks,
Gil.
Click to expand...
Click to collapse
Sorry guys! My mistake, I didn't use cf-autoroot. I just ODIN'ed the autoroot and now all is well!
Please anyone who's taken the update (via OTA or by flashing the full DOB1 tar) and then rooted and installed custom recovery: if you've since installed custom Roms, please head over to this thread and let us know how you did it, what steps you took, etc.
http://forum.xda-developers.com/tmobile-galaxy-s5/general/warning-flashing-bootloader-modem-t3037034
Thanks much!

Panasonic DMC-CM1 Stagefright update fails

Today I received a notification about System updates on my Panasonic DMC-CM1 (5.0.2, 12.0274) and allowed the update to run. Now every time I reboot I am seeing a warning "System Updates" "Software Update Stopped, Please Try again". If I go to "About Phone" "System Updates" it says "Your phone is up-to-date" but it is still at 12.0274, it should be 12.0300.
I have also tried to install the update by downloading the .DAT file from the Panasonic website and copying it to the "Download" folder of my microSD, and updating from there. I get the same result.
Any ideas?
*bump*
Does anyone on XDA have any experience with the Panansonic CM1?
Same here. Are you rooted? — I reckoned that in my case root might be the culprit.
cybriks said:
Same here. Are you rooted? — I reckoned that in my case root might be the culprit.
Click to expand...
Click to collapse
I WAS rooted, but I unrooted with SuperSU. It makes no difference.
Exactly what I tried – to no avail.
Unrooting with SuperSU does not remove all changes done to the system...
---------- Post added at 02:31 PM ---------- Previous post was at 02:22 PM ----------
What I've tried this far:
unrooting through SuperSU -> nope
re-rooting, uninstallning xposed sdk, unrooting -> nope
re-rooting, re-enabling all services, unrooting -> nope
trying to flash the ealier update -> nope
---------- Post added at 02:46 PM ---------- Previous post was at 02:31 PM ----------
FlashFire gives me "/system/bin/app_process has unexpected content"
You have tried more than me. I tried reinstalling kingroot 4.5, rerooting then unrooting. Nope. This post on DPreview suggests that Developer setting is an issue. I've checked that, no difference for me.
Have you tried factory reset? I've not tried that yet because I haven't backed up this week.
JPCoetzee said:
You have tried more than me. I tried reinstalling kingroot 4.5, rerooting then unrooting. Nope. This post on DPreview suggests that Developer setting is an issue. I've checked that, no difference for me.
Have you tried factory reset? I've not tried that yet because I haven't backed up this week.
Click to expand...
Click to collapse
The "/system/bin/app_process has unexpected content" warning seems to be caused by changes made by Xposed. Uninstalling (by flashing the uninstaller with FlashFire) doesn't seem to do the trick, however.
cybriks said:
The "/system/bin/app_process has unexpected content" warning seems to be caused by changes made by Xposed. Uninstalling (by flashing the uninstaller with FlashFire) doesn't seem to do the trick, however.
Click to expand...
Click to collapse
The .DAT update files are zips. Maybe you could replace app_process32 with the one from 0P...0761_9274.DAT?
Have you tried factory reset?
Factory reset did not work.
However, I give you... *drumroll*... SUCCESS
Make sure you are rooted and that Xposed was properly uninstalled (by flashing the uninstaller with FlashFire)
Navigate with your file browser (I am using Solid Explorer) to /system/bin. (In the settings of Solid Explorer you have to enable display of the root folder)
Locate app_process32
Check whether you have app_process32.orig in the same folder
Change the name of app_process32 to whatever you like. Rename app_process32.orig to app_process32
Unroot.
Update system
The flashing will be done in three increments, with the device rebooting between each increment. Don't freak out, it's not a bootloop. Three circles underneath the android robot are changed to filled circles/dots, one for each increment.
After completing the flash, it took ages during the "optimizing apps"-process, but I was finally greeted with the "Update successful"-notification. The "about this phone"-section in settings now properly states version 12.0300 (though still Android 5.0.2).
Trying to acquire root was more of hit-and-miss. I had to run KingRoot several times, before it worked properly. SuperSU Me gave me different results on every run.
After the first run of KingRoot, it indicated success, but I could not to anything requiring root. SuperSU Me told me that KingRoot was not installed.
I re-ran KingRoot. Now SuperSU Me told me, that KingRoot is installed. Great. Trying to remove KingRoot, SuperSU Me stalled completely. Even KingRoot and the bloatware it installs crashed (giving system warnings). The result after this try basically was no root at all.
I re-ran KingRoot a third time, SuperSU Me works through both stages and notifies me of success. Amazing.
Running SuperSU afterwards however gives me a warning: "Another su-binary seems to be installed. Should I remove it" (or something similar, didn't jot it down).
After choosing yes, and a final reboot, everything seems to be back to normal with proper su, no KingRoot and latest version from Panasonic :good:
cybriks said:
Factory reset did not work.
However, I give you... *drumroll*... SUCCESS
Click to expand...
Click to collapse
I have never installed Xposed so I've never seen this error. Is it installed by Kingroot?
Great news, all the same!
JPCoetzee said:
I have never installed Xposed so I've never seen this error. Is it installed by Kingroot?
Great news, all the same!
Click to expand...
Click to collapse
Not that I am aware of. Take a look into the /system/bin folder and check whether you have app_process32 in differently named versions (I had app_process32 (which was a symlink) and app_process32.orig)
This didn't work for me There was an acc_process32_original and a symlink, but I think it was the SuperSU symlink. Anyway, no go. Back to the drawing board. Factory reset made no difference.
Which version of Kingroot did you use?
While having root, you could try to install FlashFire (if you haven't already). One of Chainfire's amazing tools.
Download the .dat-file to your phone and start to flash it with FlashFire. This will most certainly fail, but instead of simply rebooting upon failure, FlashFire should swiftly show you an error-message. Try to remember that and hunt down the problem by that.
You have to follow what is beeing displayed however, as FlashFire will abort the flashing and reboot just a few moments after displaying the error message.
I used KingRoot 4.65
Update: you probably wouldn't have to follow the display real-time. FlashFire should log to Internal memory > FlashFire > lastlog
cybriks said:
FlashFire should swiftly show you an error-message. Try to remember that and hunt down the problem by that.
Click to expand...
Click to collapse
Flashfire has helped me fix it! What a marvellous tool.
Ages ago I removed GCoupon - Panasonic/Lumix bloatware. Flashfire showed me that the update was failing on "/system/app/Gcoupon/Gcoupon.apk/ has unexpected contents". Gcoupon.apk was actually missing, so I replaced it with the version from the previous update file (0P0000121100000600110761_9274.dat).
I unrooted and restarted the update. After the 3 reboots and "Android is upgrading" I now have 12.0300. Using Kingroot 4.8.0 and Super-SUme I rooted on first attempt.
For my phone (without Xposed) the "app_process32 has unexpected contents error" is a red herring. When SuperSU is installed on a rooted device the app_process32 executable is replaced by a symlink to daemonsu so any update attempted on a rooted phone is bound to fail during the checking stage.
Thanks for your help!
JPCoetzee said:
Flashfire has helped me fix it! What a marvellous tool.
Click to expand...
Click to collapse
Great :good:
I tried to write a sum-up on the other thread as well: http://forum.xda-developers.com/showpost.php?p=65404103&postcount=40
Does anyone know how to get the CM1 into recovery mode? My CM1 is now in a boot loop after a failed panasonic update. The phone had been kingrooted, so that may be a contributing factor.
Anyway, I need to know how to get the phone into enter recovery mode, so I can do a reset.
Thank you.
allmankind said:
boot loop ... phone had been kingrooted, so that may be a contributing factor.
Click to expand...
Click to collapse
Something similar happened with my Sony Z3 (bootloop after kingroot on tablet with locked bootloader) and I had to reinstall the firmware using a Sony PC utility. Unfortunately Panasonic don't provide anything similar (I have asked their tech support).
If it can't be fixed using some generic PC software there is a Panasonic Service Centre here in the UK http://panasonic.dkavs.co.uk/
Thanks, but I am in Thailand. I have been in contact with Panasonic Japan, and they have refered me to Singapore. With the boot loop, it never gets to the stage where ADB can interact with the phone. But hopefully they will have something to allow either a factory reset, or a complete reloading fof the firmware.
As an aside, Japan told me the CM1 is in fact produced by the camera division (DMC-CM1 designation) and not the phone division.
After update firmware to 12.300, wifi tethering not working
DMC CM 1 Lockscreen
hello my CM1 have screenlock i dont know the pin anymore
anyone was able to make a Factory Reset with the phone?
i need some help please how to do a Factory Reset with the phone
it is show me in Windows as Android ADB Interface
or USB multimedia.
but if i use ADB SDK Manager it says Error no Devices found.
#i just need to do a factory reset. i also was trying to remove the Battery but i failed.

Kindle Fire HD 7 (4th) Root Issue (?)

I successfully rooted my HD7(4th) using Kingroot and reverted it back to 4.5.3. I disabled OTA updates via ADB (pm block com.amazon.otaverifier somethin somethin), but I am now trying to go back to stock build 5.3.6 (amz/gp/help/customer/display.html?nodeId=201596850). I cannot for the life of me figure out flashing the bin/.zip files using TWRP, PlatformTools, SuperTool, etc.
Somehow I have lost the 'update from ADB' option during recovery (only seeing 2 options now, Reboot your fire, and Reset to factory). Running bootloader doesn't do anything. Just black screen.
OTA update checker in System Updates always says Last updated failed despite turning off root, uninstalling Kingroot, unblocking OTA verifier manually in ADB, then doing factory reset, etc. Still says 4.5.3 and will not allow me to update.
Halp! Any help is appreciated. TIA.
doobius said:
I successfully rooted my HD7(4th) using Kingroot and reverted it back to 4.5.3. I disabled OTA updates via ADB (pm block com.amazon.otaverifier somethin somethin), but I am now trying to go back to stock build 5.3.6 (amz/gp/help/customer/display.html?nodeId=201596850). I cannot for the life of me figure out flashing the bin/.zip files using TWRP, PlatformTools, SuperTool, etc.
Somehow I have lost the 'update from ADB' option during recovery (only seeing 2 options now, Reboot your fire, and Reset to factory). Running bootloader doesn't do anything. Just black screen.
OTA update checker in System Updates always says Last updated failed despite turning off root, uninstalling Kingroot, unblocking OTA verifier manually in ADB, then doing factory reset, etc. Still says 4.5.3 and will not allow me to update.
Halp! Any help is appreciated. TIA.
Click to expand...
Click to collapse
If you are on 4.5.3 bootloader you can easily boot to unsigned recovery images. So install flashify and download the twrp for ariel and flash it:
https://forum.xda-developers.com/fire-hd/development/recovery-twrp-3-0-2-0-t3488768
So here you can install any zip, but when you finish, restore the correct recovery.img. For example: If you update to 5.3.6 with TWRP, then flash the 5.3.6 recovery.
But be careful of what you do, you can brick the tablet by flashing wrong bootloaders.
haha. too late. i apparently hadnt set up twrp the right way. added it, and decided to go back to the newest version OS directly from amazon without thinking. so now i am on 5.6.1, cant do anything cool, and to make it worse, opted to add supersu installer. so now i have supersu installer that i cannot remove on a locked os.
doobius said:
haha. too late. i apparently hadnt set up twrp the right way. added it, and decided to go back to the newest version OS directly from amazon without thinking. so now i am on 5.6.1, cant do anything cool, and to make it worse, opted to add supersu installer. so now i have supersu installer that i cannot remove on a locked os.
Click to expand...
Click to collapse
Wow very nice. You can use this toolbox in the next version since the dev will add support for ariel for debloat and do more things without root:
https://forum.xda-developers.com/hd8-hd10/development/official-amazon-fire-toolbox-v1-0-t3889604
thank you for the replies Rortiz2. i am going to stop tinkering and ask for advice here before i make things worse.
so with this tool, i am able to debloat, but must retain the updated OS (5.6.1)? i'm under the impression i cannot go back to anything before 5.6.1 at this point.
i can get into => Fastboot mode....can i do anything with that to reinstall a different OS and go back to 4.5.3 or something rootable? if i can undo this 5.6.1 flash i would.
or do you know if through the ADB command console i can uninstall the supersu installer? it does not allow me to install within the apps menu. i read somewhere that it is because it is considered a system program the way i installed it. i tried downloading the UPDATE-unSU-signed.zip supersu uninstaller fix, but have no way to open the zip within the kindle.
i just want to take it back to full rooted, or full oem and not some messed up thing in between.
doobius said:
thank you for the replies Rortiz2. i am going to stop tinkering and ask for advice here before i make things worse.
so with this tool, i am able to debloat, but must retain the updated OS (5.6.1)? i'm under the impression i cannot go back to anything before 5.6.1 at this point.
i can get into => Fastboot mode....can i do anything with that to reinstall a different OS and go back to 4.5.3 or something rootable? if i can undo this 5.6.1 flash i would.
or do you know if through the ADB command console i can uninstall the supersu installer? it does not allow me to install within the apps menu. i read somewhere that it is because it is considered a system program the way i installed it. i tried downloading the UPDATE-unSU-signed.zip supersu uninstaller fix, but have no way to open the zip within the kindle.
i just want to take it back to full rooted, or full oem and not some messed up thing in between.
Click to expand...
Click to collapse
Ok before trying nothing, maybe you have a chance of life and SuperSU has injected the binaries. Try installing SuperSU.apk from google and open it. If it asks for update binaries you have root and you can downgrade!
Rortiz2 said:
Ok before trying nothing, maybe you have a chance of life and SuperSU has injected the binaries. Try installing SuperSU.apk from google and open it. If it asks for update binaries you have root and you can downgrade!
Click to expand...
Click to collapse
i tried manually installing supersu.apk via adb, but when i do that, it says the install failed because it is already on the device. but it is just the installer. when i open the installer, it asks me to try and download via play, but it is no longer available, and the other option is via twrp. it downloads a file, and restarts, but nothing happens. it just starts as normal. i installed kingroot again, and it fails trying to root it since 5.6.1.
doobius said:
i tried manually installing supersu.apk via adb, but when i do that, it says the install failed because it is already on the device. but it is just the installer. when i open the installer, it asks me to try and download via play, but it is no longer available, and the other option is via twrp. it downloads a file, and restarts, but nothing happens. it just starts as normal. i installed kingroot again, and it fails trying to root it since 5.6.1.
Click to expand...
Click to collapse
Ok so try this:
Open a cmd and type:
Code:
adb shell
and then
Code:
su
what's the output of "su"?
Rortiz2 said:
Ok so try this:
Open a cmd and type:
Code:
adb shell
and then
Code:
su
what's the output of "su"?
Click to expand...
Click to collapse
PS \ADB\platform-tools_r29.0.1-windows\platform-tools> .\adb shell
[email protected]:/ $ su
1|[email protected]:/ $
this is what happens when i try to install supersu.apk manually. and the only reason i was trying to install it was so that i could remove it hah.
PS ADB\platform-tools_r29.0.1-windows\platform-tools> .\adb install supersu.apk
Performing Push Install
supersu.apk: 1 file pushed. 3.9 MB/s (6258692 bytes in 1.534s)
pkg: /data/local/tmp/supersu.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
PS ADB\platform-tools_r29.0.1-windows\platform-tools>
doobius said:
this is what happens when i try to install supersu.apk manually. and the only reason i was trying to install it was so that i could remove it hah.
PS ADB\platform-tools_r29.0.1-windows\platform-tools> .\adb install supersu.apk
Performing Push Install
supersu.apk: 1 file pushed. 3.9 MB/s (6258692 bytes in 1.534s)
pkg: /data/local/tmp/supersu.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
PS ADB\platform-tools_r29.0.1-windows\platform-tools>
Click to expand...
Click to collapse
You have the f**** root. The problem is that there's no prompt... Maybe, changing SuperSU package name helps?
Rortiz2 said:
You have the f**** root. The problem is that there's no prompt... Maybe, changing SuperSU package name helps?
Click to expand...
Click to collapse
good idea. but that failed too.
doobius said:
good idea. but that failed too.
Click to expand...
Click to collapse
So then try installing google play as in Fire 7 2015/2017.
You have two methods:
- Manual: https://forum.xda-developers.com/amazon-fire/general/how-to-install-google-play-store-fire-t3486603
- Automated tool: https://forum.xda-developers.com/amazon-fire/general/tool-amazon-fire-7-7gen-fire-os-5-6-x-t3815112
(Use install google play option).
When you logged in and setup it correctly, proceed to update supersu installer tought Play Store.
ok sir, you are on to something...
i downloaded the playstore stuff via that link you sent.
i logged in to playstore and went back to the supersu installer i already had.
i clicked play.
it took me to the same playstore suspersu program and it says it is currently unavailable.
i searched supersu and found the main updated download.
i hit open and it took me back to the installer i already have.
i went back and noticed the update option in the playstore and selected that.
it updated and is now saying that the su binary needs to be updated and is asking me to continue.
awaiting your godlike instructions.
the next screen says, "if you have a custom recovery like twrp or cwm, that can be used to (try to) install the SU binary. this is recommended for HTC devices. how would you like to install the SU binary.
normal or twrp/cwm?"
normal, right?
and now if i try the su command under adb shell, i get a popup on the kindle asking me to grant superuser request for access. are these good things?
doobius said:
and now if i try the su command under adb shell, i get a popup on the kindle asking me to grant superuser request for access. are these good things?
Click to expand...
Click to collapse
Yay!! You have root!! Now that you have root. I will recommend you to flash a working recovery.
Pinging some people that may help creating the stock recovery: @k4y0z @bibikalka
ok. what is the best method to roll back to a previous OS then? should i use that fire toolbox 5.1 and try the root process there? i just don't want to mess it up again. like i said, i either want it to look like i never touched it and go back to 100% amazon factory....or keep it rootable/rooted with an old OS and just lock the OTA updates from ever updating it.
to be honest, what i had tried to do was set it up so i could use the gps spoofer on an app. but the app doesn't like the old OS i was on. and i don't think i can do the spoofing/gps manipulation with an old OS because i don't have the ability to choose an app for fake location.
doobius said:
ok. what is the best method to roll back to a previous OS then? should i use that fire toolbox 5.1 and try the root process there? i just don't want to mess it up again. like i said, i either want it to look like i never touched it and go back to 100% amazon factory....or keep it rootable/rooted with an old OS and just lock the OTA updates from ever updating it.
to be honest, what i had tried to do was set it up so i could use the gps spoofer on an app. but the app doesn't like the old OS i was on. and i don't think i can do the spoofing/gps manipulation with an old OS because i don't have the ability to choose an app for fake location.
Click to expand...
Click to collapse
Ok. DON'T DO ANYTHING UNTIL YOU RESTORE WORKING RECOVERY.
First we need to create a working recovery image. Can you check if there's install-recovery.sh in system/etc and in system/bin please?
i dont see that, but i'm probably not looking in the right spot then. how do you suggest i check for this?

Categories

Resources