Well, I "had" an HDX at 14.3.2.6. I had the hdxposed module and I renamed the otacerts.zip to otacerts.bak. When the downgrade method came out, I named the otacerts.bak to otacerts.zip and I removed and uninstalled the HDXposed module. Then I changed the build prop to match the guides, and tried to update. I keep on getting an update fail, despite multiple reboots. I have checked to make sure that the .bin is in the root of storage, but nothing is happening. Please help me.
I put a pause in the batch, and manually copied the files to the right location, and I believe what happened is I did the build.prop and one more thing, then I accidently rebooted and its a brick.
XxD34THxX said:
Well, I "had" an HDX at 14.3.2.6. I had the hdxposed module and I renamed the otacerts.zip to otacerts.bak. When the downgrade method came out, I named the otacerts.bak to otacerts.zip and I removed and uninstalled the HDXposed module. Then I changed the build prop to match the guides, and tried to update. I keep on getting an update fail, despite multiple reboots. I have checked to make sure that the .bin is in the root of storage, but nothing is happening. Please help me.
Click to expand...
Click to collapse
Please clarify what did you plan to achieve with this and with what you need help exactly?
Is your kindle still usable (rom booting, but freeze at some point and is unusable or rom booting correctly, only update is failing)?
What recovery are you using (stock, safestrap or TWRP 2.8.x.x) and can you access it?
Your firmware was stock + rooted or some custom rom?
Please link the "guides" you worked with and if possible mark the point in which guide recommend something, but your kindle refuse(d) to continue?
XxD34THxX said:
Well, I "had" an HDX at 14.3.2.6. I had the hdxposed module and I renamed the otacerts.zip to otacerts.bak. When the downgrade method came out, I named the otacerts.bak to otacerts.zip and I removed and uninstalled the HDXposed module. Then I changed the build prop to match the guides, and tried to update. I keep on getting an update fail, despite multiple reboots. I have checked to make sure that the .bin is in the root of storage, but nothing is happening. Please help me.
Click to expand...
Click to collapse
Not sure why you needed to mess with build prop when starting from 3.2.6. According to this guide (which I have successfully used several times) it's simply a matter of dropping the renamed image in root, rebooting and allowing the 'update' to be processed naturally. What am I missing?
You're following the wrong guide...Those instructions are only for x.3.2.4 and below.
See http://forum.xda-developers.com/showpost.php?p=55759790&postcount=204.
Well.. If this is not the case..
Did you set the permissions on the build.prob? I forgot it last time and my kindle was bricked. And Warrenty was out of time. But I got a new With 4.5.2 -.-'
@Davey126 I used that guide and it says to edit build.prop
@EncryptedCurse Uhmm, chrome and firefox both don't like the rollback for my HDX... Also, do I run the bat on the kindle or on my PC? And what folder exactly...
@oOFrAnzOo Permissions were all r/w
@jeryll Only update is failing. Everything works fine. Firmware and everything is stock + towelroot and Xposed. No safestrap
you need to read carefully...
edit build.prop is only up to 3.2.4...
you way to do is the mentioned post from encryptedcurse...
before that, edit the build.prop back to what it was before...
you need to extract it first on pc, and copy the update 3.1.0bin to that folder, and run the .bat from there....
after that copy the 3.1.0 to kindle (mentioned in the how to)
if you can't get the rollback.zip, disable your antivirus for a minute and use internet explorer...
(if remeber right, there are two download buttons, the blue one was the right one...)
XxD34THxX said:
@Davey126 I used that guide and it says to edit build.prop
Click to expand...
Click to collapse
I am afraid not. You need to read more carefully. The first section (where it mentions modifying build.prop) is for versions up to 3.2.4. The section further down is for 3.2.5-3.2.6. Look for the bold red highlighted text delineating sections.
(yes, it could be more clear. Maybe blinking red. That said, volunteers post this information; I am grateful for their contributions even if it takes a couple readings to fully digest)
Now if I can start IE...
The HDX has to be in fastboot mode correct?
wait, The kindle DOES NOT need to be connected to the PC when running the batch right? Also, is the reboot for the HDX or PC?
XxD34THxX said:
wait, The kindle DOES NOT need to be connected to the PC when running the batch right? Also, is the reboot for the HDX or PC?
Click to expand...
Click to collapse
The batch file simply issues a bunch of adb commands on your behalf. So yeah, it needs to be connected. Reboot is for HDX. Make sure you understand what you are doing; you can easily 'damage' or permanently brick your device with a simple mistake.
---------- Post added at 11:35 AM ---------- Previous post was at 11:33 AM ----------
XxD34THxX said:
The HDX has to be in fastboot mode correct?
Click to expand...
Click to collapse
No...where does it say that?
Davey126 said:
The batch file simply issues a bunch of adb commands on your behalf. So yeah, it needs to be connected. Reboot is for HDX. Make sure you understand what you are doing; you can easily 'damage' or permanently brick your device with a simple mistake.
---------- Post added at 11:35 AM ---------- Previous post was at 11:33 AM ----------
No...where does it say that?
Click to expand...
Click to collapse
OK, so I installed ADB drivers... going to try this now. I'm still used to safestrap, which needed little work
Alright, I ran the batch, the .bin was in the same folder, Kindle was connected, ADB enabled in settings. I rebooted, moved .bin to the root of storage, and I get the same "Last Update Failed" Error again...
XxD34THxX said:
OK, so I installed ADB drivers... going to try this now. I'm still used to safestrap, which needed little work
Alright, I ran the batch, the .bin was in the same folder, Kindle was connected, ADB enabled in settings. I rebooted, moved .bin to the root of storage, and I get the same "Last Update Failed" Error again...
Click to expand...
Click to collapse
Did you mess with the otaupdate apk's from amazon to previously blick ota updates? That is the error you get when you try to update & it can't launch the updater app. The same error you get when disabling the OTA's & then trying to search for updates.
You may need to rename the OTA apk's ***AFTER DISABLING WIFI*** & then trying to start the process again. I think it will require a reboot to bring those services on line again, as well.
Ermmm.. The OTAcerts is a .zip... Is it supposed to be a .apk?
XxD34THxX said:
Ermmm.. The OTAcerts is a .zip... Is it supposed to be a .apk?
Click to expand...
Click to collapse
otacerts.zip is correct.
Davey126 said:
otacerts.zip is correct.
Click to expand...
Click to collapse
well, it's a .zip and located in /System/etc/Security. HDXposed is off, and I did several reboots to make sure. Then I did the batch...
XxD34THxX said:
well, it's a .zip and located in /System/etc/Security. HDXposed is off, and I did several reboots to make sure. Then I did the batch...
Click to expand...
Click to collapse
Not sure what to say. Seems something is still amiss and needs to be tracked down. Suggest you go through previous posts and validate everything. I am sure you have already done this but something must be off. Frustrating for sure...we've all been through it at some point.
Perhaps someone else has a better idea.
XxD34THxX said:
well, it's a .zip and located in /System/etc/Security. HDXposed is off, and I did several reboots to make sure. Then I did the batch...
Click to expand...
Click to collapse
Try a factory reset from within the settings.
Code:
* USE IT AT YOUR OWN RESPONSIBILITY because rewrite recovery partition.
*
* This batch file works "kindle fire hdx 8.9" ONLY
* This is not tested.
*
* If do not want rollback, Close this window.
*
* IF you want to rollback,
* Put "update-kindle-14.3.1.0_user_310079820.bin" in SAME folder,
* Push Enter key 5 times
*
* If it is requested from super su, please allow superuser.
*
Press any key to continue . . .
Press any key to continue . . .
Press any key to continue . . .
Press any key to continue . . .
Press any key to continue . . .
C:\Users\Karanbir Ahuja\Desktop\ApolloHDX\rollback89>7z.exe e update-kindle-14.3.1.0_user_310079820.bin "boot.img" "recovery/recovery-from-boot.p" "system/etc/recovery-resource.dat" "system/etc/security/otacerts.zip"
7-Zip 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-18
Processing archive: update-kindle-14.3.1.0_user_310079820.bin
file boot.img
already exists. Overwrite with
boot.img?
(Y)es / (N)o / (A)lways / (S)kip all / A(u)to rename all / (Q)uit? a
Extracting boot.img
Extracting recovery\recovery-from-boot.p
Extracting system\etc\recovery-resource.dat
Extracting system\etc\security\otacerts.zip
Everything is Ok
Files: 4
Size: 8875856
Compressed: 833418977
C:\Users\Karanbir Ahuja\Desktop\ApolloHDX\rollback89>adb shell mkdir /sdcard/recovery
mkdir failed for /sdcard/recovery, Permission denied
C:\Users\Karanbir Ahuja\Desktop\ApolloHDX\rollback89>adb push build.prop /sdcard/recovery/build.prop
failed to copy 'build.prop' to '/sdcard/recovery/build.prop': Permission denied
C:\Users\Karanbir Ahuja\Desktop\ApolloHDX\rollback89>adb push otacerts.zip /sdcard/recovery/otacerts.zip
failed to copy 'otacerts.zip' to '/sdcard/recovery/otacerts.zip': Permission denied
C:\Users\Karanbir Ahuja\Desktop\ApolloHDX\rollback89>adb push boot.img /sdcard/recovery/boot.img
failed to copy 'boot.img' to '/sdcard/recovery/boot.img': Permission denied
C:\Users\Karanbir Ahuja\Desktop\ApolloHDX\rollback89>adb push recovery-from-boot.p /sdcard/recovery/recovery-from-boot.p
failed to copy 'recovery-from-boot.p' to '/sdcard/recovery/recovery-from-boot.p': Permission denied
C:\Users\Karanbir Ahuja\Desktop\ApolloHDX\rollback89>adb push recovery-resource.dat /sdcard/recovery/recovery-resource.dat
failed to copy 'recovery-resource.dat' to '/sdcard/recovery/recovery-resource.dat': Permission denied
C:\Users\Karanbir Ahuja\Desktop\ApolloHDX\rollback89>adb push install.sh /sdcard/recovery/install.sh
failed to copy 'install.sh' to '/sdcard/recovery/install.sh': Permission denied
C:\Users\Karanbir Ahuja\Desktop\ApolloHDX\rollback89>adb shell sh -v /sdcard/recovery/install.sh
sh: /sdcard/recovery/install.sh: Permission denied
C:\Users\Karanbir Ahuja\Desktop\ApolloHDX\rollback89>pause
Press any key to continue . . .
That's the log for the batch... I added a pause at the end and a check for this. a crap ton of errors... Oh yes, I did a factory reset...
Related
NOTE: DO NOT DO THIS UNLESS YOU KNOW WHAT YOU ARE DOING, YOU CAN EASILY SCREW UP YOUR SYSTEM, AND THIS WON'T HELP YOU.
BACKUP FIRST, AND MAKE SURE YOU HAVE A SETUID SH AS ROOT SO YOU CAN RECOVER FROM BACKUPS IF NECESSARY.
First you have to re-sign framework-res.apk using testkeys. This will allow you to use testkeys for system uid packages.
Next step is to re-sign all other apks that use shared uid system.
That is: bootinfo, Fota, GoogleCheckin, GoogleSubscribedFeedsProvider, NetworkLocation, ServiceMenu, Settings, SettingsProvider, VpnServices
Next you have to re-sign all apks that use the platform key, which turns out to be the shared uid phone - these require implicit permissions from the platform like DEVICE_POWER:
TelephonyProvider, Stk, semc-backup-rachael, Phone
Finally, I think GoogleEnhancedSearch also needs it or something otherwise a settings menu will fc.
The nice part about re-signing is that you don't actually need to deodex the files.
One important thing is that in the new versions, the fota.action.DEBUG_ENTRY is actually disabled, and moreover, requires special permissions that aren't granted. This is where re-signing comes in.
Now, you need to deodex fota.apk, modify the manifest to remove permissions required for DEBUG_ENTRY, and finally, force enable the debug menu:
In com/sonyericsson/android/fota/common/fotaview/FotaDebugEntry.smali,
find "debug UI is not available!"
a few lines above, there is if-nez v0 :cond_0
change it to if-eqz v0 :cond_0
This forces it to enable the debug menu.
Now we re-smali the Fota.apk, re-sign, then push it on to the phone along with the rest of the modified packages.
Repush all the files to the phone and it's done
problem !
baksmali gives an error at fota.apk
can you post your deodex scrypt
Why is this required?
TechGuru_x10 said:
Why is this required?
Click to expand...
Click to collapse
So that you won't have to keep re-flashing the older firmware to root (and keep re-installing stuff afterwards), and it should save time in repairing your firmware if you mess system files up.
It should also allow us to upgrade to newer firmwares from the current one, so we don't have to lose all of our apps/settings when rooting our phones again with a newer firmware.
Is this right guys? Anyway, thanks and good luck!
jerpelea said:
problem !
baksmali gives an error at fota.apk
can you post your deodex scrypt
Click to expand...
Click to collapse
You need to add the classpath by deodexing everything in the framework folder and including it.
zephyrix said:
You need to add the classpath by deodexing everything in the framework folder and including it.
Click to expand...
Click to collapse
oki
will try
thanks
found my error
i was using smali1.2.2 tested with 1.2.3 and is working
jerpelea said:
oki
will try
thanks
found my error
i was using smali1.2.2 tested with 1.2.3 and is working
Click to expand...
Click to collapse
Could these steps be made into a script, to run everything at once? Or at least in sections?
Daneshm90's autodeodexer 2.3 modified by me for X10
http://hotfile.com/dl/53736770/16a1bc8/Deodexer_2_3_SE.rar.html
So eventually (with this) we can take a newer build and run this script thus allowing us to then run the files necessary for root?
what do you mean by newer builds like R2BA020
Sorry if Im being a noob but lets say I mess up a framework file and get stuck at the bootscreen. When I try to use adb to push my backup it says permission denied. Will this allow me to make the changes?
Well what I've done is use a modified adb which runs as root and replaces on boot. However, I believe you could use a setuid sh and achieve the same result.
i.e. cp /system/bin/sh /system/bin/rootsh
chmod 6755 /system/bin/rootsh
then you can push to a folder where you can normally write, and use rootsh and move it.
Great thanks, I'm going to wait until I have to try it...
Why?
init.d allows to run scripts at system startup (reboot) of Linux and Android devices. On the Sony Tablet S it is not supported on "stock" ROM. Therefore it is not possible to execute shell scripts at the boot process.
For what?
As mentioned above, primarily for startup scripts. It can be used for 'mounting ext.sdcard to int. sdcard' for example or it is also possible to integrate kernel modules or system tweaks boot time.
How?
This requires copying the files in the enclosed zip archive to the corresponding points and to change the permissions right. Firstyou must create the folder 'init.d' at '/system/etc'.
But now "Step-by-Step":
Requirements:
You need to use Root Explorer, adb or something else. I do not want to explain each step in detail. If you have not the necessary basic knowledge you should not do this because it is deeper system change, which could end with a brick or boot loop. That would not 'the end of the world', if you have previously prepared you system for this before and know what to do this case. I am not responsibility for damage or other any problems.
Everything is done at your own risk.
Step-by-Step Instructions:
1. Create in '/system/etc' a 'init.d' folder
2. Change the access rights to '777'
3. Copy the file 'sysinit' into folder '/system/bin'
4. Change the access rights to '755'
5. Copy file 'install-recovery.sh' into folder / system / etc '
6. Change the access rights to '777'
7. Copy file 'run-parts' into folder '/system/xbin'
(If 'run-parts' already existing, you can skip Step 7 and 8. In my case it was already on the Tablet S)
8. Change the access rights to '777'
9. Copy file '99test file' into folder '/system/etc/init.d'
10. Change the access rights to '777'
Now finished .... it should work !
After next reboot take a look into the folder 'data/local/tmp'. You should find a file 'init.d_log_test.txt', created by the test script. If so, everything works fine and now you can put there your own scripts under 'init.d'. Now you can delete the test script or if you like adjust it for your own tests.
Have fun with the new 'init.d' support and apologize for my weak English !!
Special thanks to DooMLord for the idea and first implementation.
Source: http://forum.xda-developers.com/show....php?t=1431134
am I missing something here, or where is the zip-file?
the link doesn't work at the bottom.
Thanx for a nice "how-to"
Seems simple and straightforward enough
Sorry for that and thank you for the hint. I was 100% sure that I enclosed the zip ... but it looks like I am getting old. ;-)
Now you should find the zip on the end of first post.
Sorry - how do you gve the 777 file permissions?
SWFlyerUK said:
Sorry - how do you gve the 777 file permissions?
Click to expand...
Click to collapse
Via the chmod unix command, or if you are using root explorer just enable read/write/execute permissions for owner, group, and others. For 755 give owner all permissions and only read/execute to group and others.
Whoops, my device is in a bootloop lol
I hope you are joking ...
@Rumball
Sorry, but you are wrong ...
755 give owner all permissions and only read/execute to group and others.
4=read
2=write
1=execute
I'm not joking, the permissions error is obviously the reason its in a bootloop then, fantastic.
What does it mean? Did you set wrong file permissions and reboots system? On all files or only on one specific? Did you changed build.prob and downloaded system update for boot loop prevention before?
obicom said:
I hope you are joking ...
@Rumball
Sorry, but you are wrong ...
755 give owner all permissions and only read/execute to group and others.
4=read
2=write
1=execute
Click to expand...
Click to collapse
Doh! Thanks
SWFlyerUK said:
I'm not joking, the permissions error is obviously the reason its in a bootloop then, fantastic.
Click to expand...
Click to collapse
Not permissions fault. Mine didn't bootloop
obicom said:
Special thanks to DooMLord for the idea and first implementation.
Click to expand...
Click to collapse
yep, DooMLord's great work.
got finished autoinstall tool for init.d as I said to you on thursday.
That sounds great ...
let us share your file ...
it makes it much easier for the other members ..
if you allow I could add it to the first post ...
with a special thx for Condi ;-)
obicom said:
That sounds great ...
let us share your file ...
it makes it much easier for the other members ..
if you allow I could add it to the first post ...
with a special thx for Condi ;-)
Click to expand...
Click to collapse
hah not important, just good to see that there are some people who are working on making our devices better and better the more of us = more of cool tab stuff
auto-install up, try it, tested so far only on one device.
I changed nothing in the build.prop.
All I did was follow the instructions to your post and change the permissions as said by the chap above.
I'm now in a boot loop. My own fault for doing it but you don't expect posted information on permissions to be incorrect...
Can't follow your comment ...
Nothing is wrong with the information regarding permissions.
I did exactly the same on my Tab and one hour ago via Teamviewer on a second one.
I am not responsible if you did something wrong. Specially if you did not follow my hint to do first all regarding "boot loop prevention"
If you have not the necessary basic knowledge you should not do this because it is deeper system change, which could end with a brick or boot loop. That would not 'the end of the world', if you have previously prepared you system for this before and know what to do this case. I am not responsibility for damage or other any problems. Everything is done at your own risk.
Click to expand...
Click to collapse
SWFlyerUK said:
I changed nothing in the build.prop.
All I did was follow the instructions to your post and change the permissions as said by the chap above.
I'm now in a boot loop. My own fault for doing it but you don't expect posted information on permissions to be incorrect...
Click to expand...
Click to collapse
I wrote in many threads about 'rescue-backdoor', why havent you made it?
I did condi ie got my ota firmware. Rolled the build.prop increment value back. But I get a verification cation error so everything was prepared.
That was the background regarding 'did you changed build.prob' and not as a reproach. I can not understand why someone try something out, without a backup or rescue strategy. Oh damn !!
-- Edit --
Rolled the build.prop increment value back
Click to expand...
Click to collapse
Does it mean now you have the original value or the lower value?
If first case , that was a fault.
SWFlyerUK said:
I did condi ie got my ota firmware. Rolled the build.prop increment value back. But I get a verification cation error so everything was prepared.
Click to expand...
Click to collapse
The key to 'rescue' is to leave modified build.prop. It fakes that you've got older firmware than zip (zip=device the same versions). Then you get in recovery, and got opportunity to reflash the same version!
[GUIDE-IMPORTANT!] "rescue-backdoor" - regarding bootloop, do it before change in sys
UPDATE: THIS IS OBSOLETE.
USE S.onyTablet.S [ALLinONE] tool
Below guide/tool use as 'description'
-------------------------------------------------------------------------
Hi guys,
We've got now ROOT. We can do a lot of things, which we couldn't do before.
But before you begin to make changes in system files, first you need to know few things.
Few users experienced "bootloop". Its brick state. There is no access to shell, no adb.
Damaged device.
How to avoid that?
Yes, there is a solution. We need to get proper update zip for our device.
We also need to fool device, that it is a newer file, than the firmware in device.
How to, step by step:
Of course, ROOT is required.
To get proper ota-update-zip for your device you have to edit /build.prop:
- easiest way is via "Root Explorer", or directly via "build.prop Editor" (in market, free),
- do not use "File Manager HD" or other filemanager, which doesn't support root operations (thx kryddan),
- always make backup of files, which you are modifying,
- change value of "ro.sony.build.incremental" to lower one to fake firmware version,
- for example on my device newest firmware has: "ro.sony.build.incremental=111201022" - decrease that value,
in my case to 111201021.
Reboot device.
OTA update notification will appear - click on "Download" button.
Wait until download finishes, but don't click "Update"!!!
I repeat - DON'T CLICK UPDATE! It will reflash firmware,
and you will have to make everything from the beginning (inc. root).
Update zip is located in /cache/ota/signed-nbx03_.......zip - make a copy to safe place - external sd and/or in pc.
Leave build.prop modified. IMPORTANT. Don't revert back changes.
To enter RECOVERY-MODE - power off device,
hold vol-down + power button.
When you want to flash your device, Sony Tablet is checking few things:
is update zip proper one - signed one,
is the update zip - for your region - SKU value,
is the update zip is newer one than firmware in device - equal and higher will not update,
only lower - thats what we're faking.
If you will revert back build.prop = update will fail,
if you will try to update with other region update zip = update fail.
So if we stay with modified build.prop = we can just enter recovery,
and update from external sd card, to our downloaded update zip
Remember, that after reflash in recovery, your build.prop will be updated back
to higher value, then to be safe you need to reapply modification!
I have tested that "rescue-backdoor" on my own device,
deleted some system framework file - of course bootloop, without adb access.
Flashed through recovery - voila, device fixed
Of course, everything what you do with your device, you are doing at your own
risk. I'm sure that in 99% cases with "rescue-backdoor" you will fix your device,
always could be that other 0,01% case.
One condition for sure = build.prop file has to be correct.
[OPTIONAL]
You can disable ota update notification - which appears on every reboot.
To do this use "Titanium Backup" app, look for "System Update" app on list,
and use "Freeze" option
Any questions, suggestions - just ask
PS. I'm thining about writing auto-script for that...
br
condi
great guide, thank you
I think an automated-script would be much appreciated
condi said:
Hi guys,
We've got now ROOT. We can do a lot of things, which we couldn't do before.
But before you begin to make changes in system files, first you need to know few things.
Few users experienced "bootloop". Its brick state. There is no access to shell, no adb.
Damaged device.
How to avoid that?
Yes, there is a solution. We need to get proper update zip for our device.
We also need to fool device, that it is a newer file, than the firmware in device.
How to, step by step:
Of course, ROOT is required.
To get proper ota-update-zip for your device you have to edit /build.prop:
- easiest way is via "Root Explorer", or directly via "build.prop Editor" (in market, free),
- always make backup of files, which you are modifying,
- change value of "ro.sony.build.incremental" to lower one to fake firmware version,
- for example on my device newest firmware has: "ro.sony.build.incremental=111201022" - decrease that value,
in my case to 111201021.
Reboot device.
OTA update notification will appear - click on "Download" button.
Wait until download finishes, but don't click "Update"!!!
I repeat - DON'T CLICK UPDATE! It will reflash firmware,
and you will have to make everything from the beginning (inc. root).
Update zip is located in /cache/ota/signed-nbx03_.......zip - make a copy to safe place - external sd and/or in pc.
Leave build.prop modified. IMPORTANT. Don't revert back changes.
When you want to flash your device, Sony Tablet is checking few things:
is update zip proper one - signed one,
is the update zip - for your region - SKU value,
is the update zip is newer one than firmware in device - equal and higher will not update,
only lower - thats what we're faking.
If you will revert back build.prop = update will fail,
if you will try to update with other region update zip = update fail.
So if we stay with modified build.prop = we can just enter recovery,
and update from external sd card, to our downloaded update zip
I have tested that "rescue-backdoor" on my own device,
deleted some system framework file - of course bootloop, without adb access.
Flashed through recovery - voila, device fixed
Of course, everything what you do with your device, you are doing at your own
risk. I'm sure that in 99% cases with "rescue-backdoor" you will fix your device,
always could be that other 0,01% case.
One condition for sure = build.prop file has to be correct.
[OPTIONAL]
You can disable ota update notification - which appears on every reboot.
To do this use "Titanium Backup" app, look for "System Update" app on list,
and use "Freeze" option
Any questions, suggestions - just ask
PS. I'm thining about writing auto-script for that...
br
condi
Click to expand...
Click to collapse
Thanks Condi! Download worked great but under my cache there is nothing. Could the file be located elsewhere?
It should be under '/cache/ota' ... nowhere else ..
Judah001 said:
Thanks Condi! Download worked great but under my cache there is nothing. Could the file be located elsewhere?
Click to expand...
Click to collapse
Be sure that ota has been download, check again /cache/ota.
If still no zip, then run 'adb shell' then:
Code:
su
find -name *signed*
or
Code:
find -name *.zip
If your ota update will be in different location, then please post it.
br
condi
condi said:
Be sure that ota has been download, check again /cache/ota.
If still no zip, then run 'adb shell' then:
Code:
su
find -name *signed*
or
Code:
find -name *.zip
If your ota update will be in different location, then please post it.
br
condi
Click to expand...
Click to collapse
ok I will try once I am home through adb. So far there is nothing under my cache folder. I am using file manager HD but it should pick up a zip file.
Thank you condi... The instructions worked perfectly!!
Judah001 said:
ok I will try once I am home through adb. So far there is nothing under my cache folder. I am using file manager HD but it should pick up a zip file.
Click to expand...
Click to collapse
Just a little tip. I'd suggest you use Root Explorer instead of File Manager HD.
You see, File Manager HD does not show the files in /cache. (mine didn't)
I tried File Manager HD on my tablet and found nothing inside /cache
But with Root Explorer I found three different directories. There among OTA.
kryddan said:
Just a little tip. I'd suggest you use Root Explorer instead of File Manager HD.
You see, File Manager HD does not show the files in /cache. (mine didn't)
I tried File Manager HD on my tablet and found nothing inside /cache
But with Root Explorer I found three different directories. There among OTA.
Click to expand...
Click to collapse
That did the trick. I used the root browser in rom tool box and copied the zip to my sd card. Thank you for the help guys.
Good advice kyddan ... same on my tab with file manager HD.
I work normally with Root Explorer or File Expert.
Both show the folders and files in /cache .. File Manager HD do not.
my ro.sony.build.incremental is 111201038
Do I have to decrease it by 1 to 111201037 ?
EDIT: nevermind. I did so. Worked.
sebarkh said:
my ro.sony.build.incremental is 111201038
Do I have to decrease it by 1 to 111201037 ?
Click to expand...
Click to collapse
Yep, exacty. And then you will get newest ota zip of 111201038 pozdro
hahahahah I just had brick... I'm working on auto-install script for "rescue-backdoor", and accidentally I've pushed empty 0bytes build.prop - after reboot - sony logo, then black screen.... and guess what...
recovery reads incremental value (which doesnt exists..) as "0" zero
so i've got lower value, and reflash done.
after reboot my tab started correctly, but.. after reboot again brick - black screen.
fortunatelly - after few min with black screen i've got adb access.
but for first - i can't get root access.. 'su' not works.
but... '/system/xbin/su' works root lets check - build.prop still empty,
remounted system as rw, pushed correct build.prop - ahhh again working !!
that was good experience hahah.
-------------edit:
i've got auto-install tool ready... need to make one more full test with my device and will publish it.
full automatic !!!!!
This is driving me crazy. why everyone is getting update message when changing the incremental value while my dumass tablet keeps saying that my system is up to date
ase3000 said:
This is driving me crazy. why everyone is getting update message when changing the incremental value while my dumass tablet keeps saying that my system is up to date
Click to expand...
Click to collapse
Just wait for automatic-tool. Its ready, but need to make final tests.
condi said:
So if we stay with modified build.prop = we can just enter recovery,
and update from external sd card, to our downloaded update zip
Click to expand...
Click to collapse
In which way we can enter to recovery??
riccardo91 said:
In which way we can enter to recovery??
Click to expand...
Click to collapse
power off, hold vol-down + power.
All done! It works well! Thanks! Avoiding bootloop it's even a good thing!
riccardo91 said:
All done! It works well! Thanks! Avoiding bootloop it's even a good thing!
Click to expand...
Click to collapse
Great Just remember one thing - after reflash in recovery, your build.prop will be updated to higher value - then to be safe you need to reapply modification!
--- my 100th post !
condi said:
Great Just remember one thing - after reflash in recovery, your build.prop will be updated to higher value - then to be safe you need to reapply modification!
--- my 100th post !
Click to expand...
Click to collapse
I bricked my XTS playuing with build.prop. Shame I didn't see this post before. For future - how can I edit build.prop in a safe way? I changed file permission then I forgot to restore default. After restart brick. Do I need to change permission to edit build.prop then do i NEED to restore proper permission back? I'm still confused with it
Hey all,
when changing my build.prop I didn't set the permissions and now I see the grey kindle logo at bootup. I'm on 13.3.2.4 and did a Towelroot before this happened.
Trying to fix the permissions I noticed I cannot change the build.prop because ADB says it is a read-only file system. The mount / remount doesnt work either.
I think what I need is a re-root via ADB (e.g. ghettoroot), as described here http://forum.xda-developers.com/kindle-fire-hdx/help/help-build-prop-edit-rooted-hdx-brick-t2973070
Sadly this also doesnt work, at the chmod 0644 /system/build.prop it still tells me read-only file system. I can only imagine it is due to the modstring being for 14.3.2.6.
Is there a way to do an ADB-only root on 13.3.2.4 (does someone have the corrent modstring) or any other way to set the right permissions on my build.prop?
Thanks in advance for your help!
------
UPDATE: UNBRICKED MY KINDLE. The ghettoroot call was correct
./ghettoroot -n -m "1337 0 0 0 4 0" /system/bin/sh
But afterwards I was still not able to change the build.prop (despite having the "#" which would indicate I have sufficient rights)
Then I used
Code:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
chmod 644 /system/build.prop
(not sure if the "su" is needed, but I will not rebrick my Kindle to find out)
which I found in HERE
What exactly do you want to mess up your build.prop for? If you want to downgrade to 3.1.0 in order to use TWRP and to unlock your bootloader you should install Safestrap v3.75 (if you haven't already) and use the rollback image provided by @ggow. Take a look at this thread (page 1 is about 3.2.5/3.2.6 users who can NOT use the rollback images).
Cl4ncy said:
What exactly do you want to mess up your build.prop for? If you want to downgrade to 3.1.0 in order to use TWRP and to unlock your bootloader you should install Safestrap v3.75 (if you haven't already) and use the rollback image provided by @ggow. Take a look at this thread (page 1 is about 3.2.5/3.2.6 users who can NOT use the rollback images).
Click to expand...
Click to collapse
Yes my plan was to downgrade to 3.1.0 in order to use TWRP and to unlock the bootloader. I wasnt aware of ggows solution and followed this thread http://forum.xda-developers.com/showthread.php?t=2782159 but used the "change build.prop with ES File Explorer instead of build prop editor". And I dont know why my root is gone (I had towelrooted it before and was able to change the build.prop file). And now I need a root to fix the build.prop.
OriginalJones said:
Yes my plan was to downgrade to 3.1.0 in order to use TWRP and to unlock the bootloader. I wasnt aware of ggows solution and followed this thread http://forum.xda-developers.com/showthread.php?t=2782159 but used the "change build.prop with ES File Explorer instead of build prop editor". And I dont know why my root is gone (I had towelrooted it before and was able to change the build.prop file). And now I need a root to fix the build.prop.
Click to expand...
Click to collapse
Did you try to re/root it with Hdx toolkit? IMHO if this can't re/root your kindle, probably nothing can...
jeryll said:
Did you try to re/root it with Hdx toolkit? IMHO if this can't re/root your kindle, probably nothing can...
Click to expand...
Click to collapse
HDX toolkit needs the tablet to be running, but I can only ADB it. That's why I'm locking for a root that is working via ADB only (like the ghettoroot described in the linked thread).
Well, I'm not exactly sure about this, but most likely @Davey126 is right:
Davey126 said:
Messing with build.prop is a bad idea on this device as you unfortunately discovered. I'm almost certain it can not be replaced via adb as the file is processed before adb access becomes available (assuming you previously enabled USB debug in FireOS).
Click to expand...
Click to collapse
OriginalJones said:
HDX toolkit needs the tablet to be running, but I can only ADB it. That's why I'm locking for a root that is working via ADB only (like the ghettoroot described in the linked thread).
Click to expand...
Click to collapse
I am sorry, I did miss that booting process is stuck at the grey logo. I always thought that you can't communicate with the hdx tablet at that point via ADB. So far what I learn from posts here is that messing with build.prop in wrong way (i.e. permissions set in wrong way) is fatal to the HDX tablet and there is no known way how to repair this...
-------THIS GUIDE IS NO LONGER NEEDED------
If your on a rootable version follow the guide and instructions to install a pre rooted Firmware, with Rbox's custom recovery.
This I supposed was good to use to have SuperSU before we had any type of recovery.
-----UPDATED V3-----NEW DOWNLOAD LINKS-----
*PLEASE READ THROUGH THE FULL GUIDE BEFORE STARTING.*
FIRE STICK Replace King/o Root with SuperSU v3.
Thanks @joojoobee666 for his suggestions on layout of the guide to try make it more understandable to folk and also to incorporate a step into the script to make it a little easier still.
First off i am not responsible for your device, if you want to wait for a custom recovery (if one is even being made) that is your choice. Ive spent 2 days trying all possible ways to accomplish this and made it as easy as i could for you.
REMEMBER GUYS, the process for this to work is root with KINGOROOT - reboot-root with KINGROOT - reboot - run the commands - uninstall KINGOROOT. Failing to follow the order of the steps could soft brick you.
Prerequisites
Fire Stick
Fire OS 5.0.5 (if your on anything other than 5.0.5 use my other guide to downgrade to 5.0.5 here:
http://forum.xda-developers.com/fire-tv/development/fire-tv-stick-downgrade-firestarter-3-2-t3399298 ) dont forget to block updates again.
An understanding that 2 separate root programs are used in this guide KINGO ROOT and KING ROOT.
Installation Procedure :
You must follow these steps exactly as they are here, any deviation from this could cause you to brick (which is undo able so dont worry too much)
If you are not already rooted you need to root with KINGO ROOT. Once rooted reboot your Fire Stick. download it from here :
https://root-apk.kingoapp.com/kingoroot-download.htm
Your now able to follow the guide after you Root with KINGO ROOT.
Procedure
1.) Download the rar file containing the scripts and APKS:
http://www.filedropper.com/firestickroot_2
http://s000.tinyupload.com/?file_id=73723140467469181970
http://www.megafileupload.com/7nfv/firestickroot.rar
2.) Extract the file pack in the rar to /sdcard on your Fire Stick, PLEASE DOUBLE CHECK THIS. YOU NEED TO HAVE THE FOLDER STRUCTURE CORRECT OR IT COULD CAUSE PROBLEMS. YOU SHOULD HAVE /SDCARD/FIRESTICKROOT/CONTENTS . Inside the firestickroot folder you will see KING ROOT, install this and open it. Grant any permissions to it and let it take over root. When its finished, reboot your Fire Stick.
3.) Open an ADB Shell connection to the device. You should now see a prompt like this:
[email protected]:/ $
4.) Run the "su" command and choose "Allow" when prompted by KINGROOT on the screen. If successful, you should now see the following in the terminal:
[email protected]:/ $ su
[email protected]:/ #
5.) Run the following command:
sh /sdcard/firestickroot/root.sh
if successful you should see something similar to this
[email protected]:/ # sh /sdcard/firestickroot/root.sh
-----------------------------------------
-----------------------------------------
---FireStick SuperSU Tool by Sconnyuk----
Thanks to Mr.W0lf for the original script
------Thanks @Chainfire for SuperSU -----
--------Swap KingRoot for SuperSU--------
-----------------------------------------
-----------------------------------------
/system/bin/am[8]: app_process: not found
/system/bin/pm[6]: app_process: not found
/system/bin/am[8]: app_process: not found
/system/bin/pm[6]: app_process: not found
rm: /system/app/Kinguser.apk: No such file or directory
/system/bin/am[8]: app_process: not found
/system/bin/pm[6]: app_process: not found
chattr: stat /system/bin/ddexe: No such file or directory
rm: /system/bin/ddexe: No such file or directory
chattr: stat /system/usr/iku/isu: No such file or directory
rm: /system/usr/iku: No such file or directory
rm: /dev/reportroot: No such file or directory
rm: /system/app/Kinguser: No such file or directory
rm: /data/data-lib/king: No such file or directory
----------------INSTALLING SU BINARIES--------------------
cp: /system/xbin/su: Text file busy
mkdir failed for /system/bin/.ext, File exists
ln: /system/bin/install-recovery.sh: File exists
cp: /system/bin/mksh: No such file or directory
pkg: /sdcard/firestickroot/superuser.apk
Success
-----------Your Welcome--------------
6.) Run the SuperSU application, go to settings and un-check Enable Superuser then re-check it.
7.) Reboot the device (either hold play and select or run "reboot" from the ADB Shell prompt)
8.) Open ADB Shell once again and run "su". This time you should see the SuperSU prompt asking to allow the ADB Shell process to run as root.
9.) Uninstall KINGOROOT
10.) If you have any reminents of KING ROOT installed uninstall them, if it wont let you uninstall, re-install KING ROOT but DONT OPEN IT! then you can uninstall it.
IF YOU RUN INTO SOFTBRICK ISSUE (stuck at fire tv logo)
Make sure you have ADB drivers properly installed in your windows pc/laptop.
connect a genuine usb lead to the firestick/pc.
download the windows version of KINGO ROOT and install it.
open KINGO ROOT on the pc with Fire Stick connected up to pc and tv.
wait for the button to pop up and click root.
if you dont see AFTV or get enable debugging in the KINGO ROOT program on pc/laptop please unplug the stick from usb and replug it back in.
if this still wont work restart the pc/laptop or try another pc/laptop.
you should after clicking root boot back up into your homescreen, if it doesnt boot back into your homescreen automatically, wait around 5 minutes and unplug usb and re-plug it again.
Thumbs up if ive helped
If anyone can make use of another app from chainfire, Flashfire, as it now will work with chainfires Su binaries installed. The app allows for backup/flash all partitions/install zips etc. Im not sure if its fully working or maybe an older version might?
Anyway ill leave that for anyone who might want to test that app out.
*IMPORTANT*
If you still cant seem to manage this, delete he associated KINGOROOTS SUPERUSER manually, then right after you have installed KINGROOT and rebooted navigate to /system/xbin and delete the file daemonsu. When the script finishes run it a second time, if you dont get chainfires SuperSU installed manually install it. This is included in the script to carry out this task but seems it wont work for everyone.
sconnyuk said:
be back soon with re-written guide v2 that is much simpler.
Click to expand...
Click to collapse
:good: i went out and bought the device for this process. was going to pull the trigger on the long complicated route. can you throw together a twrp image for us as well?
asafegous said:
:good: i went out and bought the device for this process. was going to pull the trigger on the long complicated route. can you throw together a twrp image for us as well?
Click to expand...
Click to collapse
Ive re done the guide made it much simpler, spent 2 days on it trying all ways to brick my device in the process and could not brick it no matter how hard i screwed up.
This newer guide should work 1st time if followed correctly, and you will be shot of Kingo/o Root.
Im real sorry but to make a custom recovery is a little beyond me.
sconnyuk said:
*Update*
I am not responsible for your device, if you want to wait for a custom recovery (if one is even being made) that is your choice. Ive spent 2 days trying all possible ways to accomplish this and made it as easy as i could for you.
The guide has been re done again by myself as it was far too long and although there was zero chance of bricking (with the use of Kingo Roots windows tool) ive put v2 together which is much simpler and all in a single script you will have no chance of any brick, with success the first attempt
This guide is for Fire Stick 5.0.5, you need root access with KingRoot, so if your rooted with Kingo Root please update your root app with the KingRoot apk in this pack, it will take over your Kingo Root and use King User.
Please note, you must root originally with Kingo Root, restart then Re-root with KingRoot then restart again, if not you will find that after a restart you will get unrooted.
Also be aware, if you have followed this through and still after a restart you are unrooted navigate to /root/system/xbin and delete the file daemonsu, then try again.
Download the pack here : http://s000.tinyupload.com/?file_id=02940258229221060594
Extract it in your Fire Sticks /sdcard directory.
You should have a folder in your Fire Sticks /sdcard directory called firestickroot.
Ive noticed myself that if im at the standard fire tv stick launcher sometimes king/o root fails to grant permissions so for the next step be aware and maybe have firestarter/app starter launcher loaded up.
Connect your Pc/Laptop/terminal to your fire stick and type the following commands. (grant permissions to all)
su
sh /sdcard/firestickroot/root.sh
Thats it, the script will remove KING ROOT and all associated files and install su binary and SuperSU apk.
Once you restart make sure you are using ChainFires SuperSu and uninstall Kingo Roots stuff.
Thumbs up if ive helped
Click to expand...
Click to collapse
II
@sconnyuk, could you pls add another d/l mirror? Thx
dave157 said:
@sconnyuk, could you pls add another d/l mirror? Thx
Click to expand...
Click to collapse
I certainly will when I get home later.
This is not working for me here. Here's the log:
Code:
-----------------------------------------
-----------------------------------------
---FireStick SuperSU Tool by Sconnyuk----
Thanks to Mr.W0lf for the original script
------Thanks @Chainfire for SuperSU -----
--------Swap KingRoot for SuperSU--------
-----------------------------------------
-----------------------------------------
Success
Success
rm: /system/app/Kinguser.apk: is a directory
rm: /system/app/Kinguser: No such file or directory
Failure [DELETE_FAILED_INTERNAL_ERROR]
/sdcard/firestickroot/root.sh[34]: can't create /system/xbin/daemonsu: Text file busy
rm: /data/data/com.kingroot.RushRoot: No such file or directory
rm: /data/data/com.kingroot.kinguser: No such file or directory
rm: /data/data/com.kingroot.master: No such file or directory
chattr: stat /system/bin/ddexe: No such file or directory
rm: /system/bin/ddexe: No such file or directory
chattr: stat /system/usr/iku/isu: No such file or directory
rm: /system/usr/iku: No such file or directory
rm: /dev/reportroot: No such file or directory
rm: /system/app/Kinguser: No such file or directory
rm: /data/data-lib/king: No such file or directory
----------------INSTALLING SU BINARIES--------------------
mkdir failed for /system/bin/.ext, File exists
ln: /system/bin/install-recovery.sh: File exists
cp: /system/bin/mksh: No such file or directory
pkg: /sdcard/firestickroot/superuser.apk
Failure [INSTALL_FAILED_DUPLICATE_PERMISSION perm=android.permission.ACCESS_SUPERUSER pkg=com.kingouser.com]
-----------Your Welcome--------------
I removed the com.kingouser.com package manually and was able to install the Superuser APK but when I run Superuser, it says the SU binaries are not installed. I've reinstalled KingRoot for now but this script is NOT bullet proof. I'm not sure exactly what state this is leaving me in but root seems to be working again after reinstalling KingRoot. Should I be completely removing KingoRoot BEFORE running this script? If so, the instuctions hould mention it. As of now, I'm afraid to do so for fear of bricking this thing. Any thoughts?
joojoobee666 said:
This is not working for me here. Here's the log:
Code:
-----------------------------------------
-----------------------------------------
---FireStick SuperSU Tool by Sconnyuk----
Thanks to Mr.W0lf for the original script
------Thanks @Chainfire for SuperSU -----
--------Swap KingRoot for SuperSU--------
-----------------------------------------
-----------------------------------------
Success
Success
rm: /system/app/Kinguser.apk: is a directory
rm: /system/app/Kinguser: No such file or directory
Failure [DELETE_FAILED_INTERNAL_ERROR]
/sdcard/firestickroot/root.sh[34]: can't create /system/xbin/daemonsu: Text file busy
rm: /data/data/com.kingroot.RushRoot: No such file or directory
rm: /data/data/com.kingroot.kinguser: No such file or directory
rm: /data/data/com.kingroot.master: No such file or directory
chattr: stat /system/bin/ddexe: No such file or directory
rm: /system/bin/ddexe: No such file or directory
chattr: stat /system/usr/iku/isu: No such file or directory
rm: /system/usr/iku: No such file or directory
rm: /dev/reportroot: No such file or directory
rm: /system/app/Kinguser: No such file or directory
rm: /data/data-lib/king: No such file or directory
----------------INSTALLING SU BINARIES--------------------
mkdir failed for /system/bin/.ext, File exists
ln: /system/bin/install-recovery.sh: File exists
cp: /system/bin/mksh: No such file or directory
pkg: /sdcard/firestickroot/superuser.apk
Failure [INSTALL_FAILED_DUPLICATE_PERMISSION perm=android.permission.ACCESS_SUPERUSER pkg=com.kingouser.com]
-----------Your Welcome--------------
I removed the com.kingouser.com package manually and was able to install the Superuser APK but when I run Superuser, it says the SU binaries are not installed. I've reinstalled KingRoot for now but this script is NOT bullet proof. I'm not sure exactly what state this is leaving me in but root seems to be working again after reinstalling KingRoot. Should I be completely removing KingoRoot BEFORE running this script? If so, the instuctions hould mention it. As of now, I'm afraid to do so for fear of bricking this thing. Any thoughts?
Click to expand...
Click to collapse
As the guide says if you have problems navigate to /system/xbin and delete daemonsu
First make sure you are rooted with KINGO ROOT - reboot
Second install the KING ROOT apk in the pack you downloaded and placed in /sdcard. let it take over root and should install its own King User apk. - reboot
Third step :
su
sh /sdcard/firestickroot/root.sh
The script is no way bulletproof but it works, if anyone would like to moddify it to better suit Fire Stick that would be great. As for bricking, i understand that nothing is 100 percent fail proof as in root etc but the way this script is set out ive tested it for 2 days uninstalling root re installing king/go in different combinations and could not brick my stick, i got a few restarts but that was all. The v1 guide i did had higher chance of bricking (trust me i tested the crap out of it) and everytime my stick failed to boot i plugged it into my laptop and ran either kingo or king root windows versions and it re rooted and got me back up and running, everytime.
I tried all different combinations to try brick and not be able to bring it back but always did.
The v2 guide here what your using i couldnt get my stick to brick once.
sconnyuk said:
As the guide says if you have problems navigate to /system/xbin and delete daemonsu
First make sure you are rooted with KINGO ROOT - reboot
Second install the KING ROOT apk in the pack you downloaded and placed in /sdcard. let it take over root and should install its own King User apk. - reboot
Third step :
su
sh /sdcard/firestickroot/root.sh
The script is no way bulletproof but it works, if anyone would like to moddify it to better suit Fire Stick that would be great. As for bricking, i understand that nothing is 100 percent fail proof as in root etc but the way this script is set out ive tested it for 2 days uninstalling root re installing king/go in different combinations and could not brick my stick, i got a few restarts but that was all. The v1 guide i did had higher chance of bricking (trust me i tested the crap out of it) and everytime my stick failed to boot i plugged it into my laptop and ran either kingo or king root windows versions and it re rooted and got me back up and running, everytime.
I tried all different combinations to try brick and not be able to bring it back but always did.
The v2 guide here what your using i couldnt get my stick to brick once.
Click to expand...
Click to collapse
I initially WAS rooted with Kingo, re-rooted with King and rebooted, then ran script. But it FAILED to complete so I didn't try the removal of deamonsu since it never completed. Is that going to fix the error I received when installed Superuser.apk? That error seems to be unrelated to the leftover daemonsu as it's in regards to a conflict with packages installed from KingoRoot. Review of the scripts shows that they in NO WAY remove that application (com.kingouser.com) so I imagine I will end up in the same spot....If I get there. I'm currently stuck on "fireTVstick" logo after trying to Re-Root with Kingo as you suggested. I don't think this looks very good...
joojoobee666 said:
I initially WAS rooted with Kingo, re-rooted with King and rebooted, then ran script. But it FAILED to complete so I didn't try the removal of deamonsu since it never completed. Is that going to fix the error I received when installed Superuser.apk? That error seems to be unrelated to the leftover daemonsu as it's in regards to a conflict with packages installed from KingoRoot. Review of the scripts shows that they in NO WAY remove that application (com.kingouser.com) so I imagine I will end up in the same spot....If I get there. I'm currently stuck on "fireTVstick" logo after trying to Re-Root with Kingo as you suggested. I don't think this looks very good...
Click to expand...
Click to collapse
OK, run the windows version of KingoRoot on your pc/laptop. if it fails first time unplug usb then plug it back in and it should root you and get you back up and running.
Its failing to complete because the daemonsu file is there. Delete it and the script will finish and uninstall KingRoot.
Nowhere in the guide says you must install SuperSU apk, the script does this for you. All you should be left with when it completes is KingoRoot and a newly installed SuperSU apk v2.01
sconnyuk said:
OK, run the windows version of KingoRoot on your pc/laptop. if it fails first time unplug usb then plug it back in and it should root you and get you back up and running.
Its failing to complete because the daemonsu file is there. Delete it and the script will finish and uninstall KingRoot.
Click to expand...
Click to collapse
Thanks. Will give all that a go here and let you know.:good:
joojoobee666 said:
Thanks. Will give all that a go here and let you know.:good:
Click to expand...
Click to collapse
Definitely want to know if everyone is having success, i did not make the scripts used here, i just slightly modified them and merged more instructions.
Everytime i run the script it works and if it wasnt for the fail safe of Windows Kingo Root i would not of put the guide up.
sconnyuk said:
Definitely want to know if everyone is having success, i did not make the scripts used here, i just slightly modified them and merged more instructions.
Everytime i run the script it works and if it wasnt for the fail safe of Windows Kingo Root i would not of put the guide up.
Click to expand...
Click to collapse
Hmm...I'm not having any luck with the KingoRoot windows app. It's not even getting to the point where it can fail. "Connecting...Please enable USB Debugging mode" is where it's getting stuck. If I remove the fire stick and plug it back in, nothing happens in the program. It still just sits at that screen. I can adb into it but I do not get root (of course). Should I maybe relflash the 5.0.5 update.bin I have sitting on the SD card (if possible)?
joojoobee666 said:
Hmm...I'm not having any luck with the KingoRoot windows app. It's not even getting to the point where it can fail. "Connecting...Please enable USB Debugging mode" is where it's getting stuck. If I remove the fire stick and plug it back in, nothing happens in the program. It still just sits at that screen. I can adb into it but I do not get root (of course). Should I maybe relflash the 5.0.5 update.bin I have sitting on the SD card (if possible)?
Click to expand...
Click to collapse
Just restart the KingoRoot app and plug unplug firetick and plug it back in, it will eventually detect it.
If not, run kingroot windows tool if that works then ok, if not dont close it open kingoroot up and then try, you will get it detected it happened to me a few times when i did v1 guide
sconnyuk said:
Just restart the KingoRoot app and plug unplug firetick and plug it back in, it will eventually detect it.
Click to expand...
Click to collapse
I think I've done all that over 10 times, same thing keeps happening. The one thing I have gotten twice is a window titles "Notification" that explains that I will need to allow debugging on the device for the app. Obviously, I cannot do that. It eventually goes away on its own then hangs at the aforementioned screen again. Any other suggestions?
joojoobee666 said:
I think I've done all that over 10 times, same thing keeps happening. The one thing I have gotten twice is a window titles "Notification" that explains that I will need to allow debugging on the device for the app. Obviously, I cannot do that. It eventually goes away on its own then hangs at the aforementioned screen again. Any other suggestions?
Click to expand...
Click to collapse
restart your pc/laptop try another usb port ? did you try KINGROOT windows app then if that goes ok fine, if not dont close it open KINGO ROOT windows app and try it then, like i said i had this a few times when i did the v1 guide but everytime i got it back up again.
sconnyuk said:
restart your pc/laptop try another usb port ? did you try KINGROOT windows app then if that goes ok fine, if not dont close it open KINGO ROOT windows app and try it then, like i said i had this a few times when i did the v1 guide but everytime i got it back up again.
Click to expand...
Click to collapse
I was just in the middle of installing the KingRoot app. I ran it and it said it was successful. Should I just reboot now? (side note, there is not daemonsu in /system/bin currently)
joojoobee666 said:
I was just in the middle of installing the KingRoot app. I ran it and it said it was successful. Should I just reboot now?
Click to expand...
Click to collapse
If it wont start up in a few minutes yes just unplug and plug it back in.
Like i said, i would not of put guide up if there wasnt the failsafe methods of KING/O for windows in place.
sconnyuk said:
If it wont start up in a few minutes yes just unplug and plug it back in.
Like i said, i would not of put guide up if there wasnt the failsafe methods of KING/O for windows in place.
Click to expand...
Click to collapse
That was the only reason I decided to go for it. However, It's still stuck on the fireTV Stick logo...after multiple reboots
joojoobee666 said:
That was the only reason I decided to go for it. However, It's still stuck on the fireTV Stick logo...after multiple reboots
Click to expand...
Click to collapse
Let it sit there a while, will probably go to optimising screen.
If it wont re root it with Kingo/king on pc and dont restart after, just let it sit and it should go to optimising screen.