Permission Denied installing Blackrose - HTC Incredible S

I used revolutionary to get S-OFF on my Incredible S. I'm trying to install blackrose. It gives the following "permission denied" error.
Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
1765 KB/s (1048576 bytes in 0.580s)
/dev/block/mmcblk0p18: cannot open for write: Permission denied
< waiting for device >
erasing 'cache'...
OKAY [ 0.217s]
finished. total time: 0.218s
Any help would be appreciated.

quark020 said:
I used revolutionary to get S-OFF on my Incredible S. I'm trying to install blackrose. It gives the following "permission denied" error.
Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
1765 KB/s (1048576 bytes in 0.580s)
/dev/block/mmcblk0p18: cannot open for write: Permission denied
< waiting for device >
erasing 'cache'...
OKAY [ 0.217s]
finished. total time: 0.218s
Any help would be appreciated.
Click to expand...
Click to collapse
Are you rooted?

Sorry.. it was not. my bad.

Hey folks, sorry to dig up an old post, but I'm running into the same issue.
I've got hboot 6.13.1002 s-off with radio 3805.04.03.27_M. Using Revolutionary.
I've got CWM and superuser on, used Titanium backup, and installed busybox.
Doesn't this mean I'm rooted? Or am I missing some pretty obvious things here...

TheMegosh said:
Hey folks, sorry to dig up an old post, but I'm running into the same issue.
I've got hboot 6.13.1002 s-off with radio 3805.04.03.27_M. Using Revolutionary.
I've got CWM and superuser on, used Titanium backup, and installed busybox.
Doesn't this mean I'm rooted? Or am I missing some pretty obvious things here...
Click to expand...
Click to collapse
of course you are rooted and you are not missing anything.
but try root check app from play store

TheMegosh said:
Hey folks, sorry to dig up an old post, but I'm running into the same issue.
I've got hboot 6.13.1002 s-off with radio 3805.04.03.27_M. Using Revolutionary.
I've got CWM and superuser on, used Titanium backup, and installed busybox.
Doesn't this mean I'm rooted? Or am I missing some pretty obvious things here...
Click to expand...
Click to collapse
Theoretically yes, practically maybe.
Run this app https://play.google.com/store/apps/details?id=eu.thedarken.rootvalidator and all your question will be answered...

Surajkumar said:
of course you are rooted and you are not missing anything.
Click to expand...
Click to collapse
Using Root Validator, everything is green, "Your device is successfully rooted".
Well... I was getting permission errors, opened recovery, reformatted the phone, cleared cache, restarted. Then blackrose installer worked!
The installer seemed to have worked, though I got an error at the end. Restarting my phone, reformatting, formatting cache, shows the phone is still on hboot 6.13 and not blackrose...?
-------------------------------
| Incredible S BlackRose 120602 |
| Made by Lecahel(XDA-dla5244) |
| Dok-Do belongs to KOREA |
-------------------------------
Do at your own risk
Your INS(USB Debugging ON) should be connected to PC
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
* Waiting for device... *
* Installing BlackRose *
2645 KB/s (1116332 bytes in 0.412s)
2515 KB/s (1048576 bytes in 0.407s)
586 KB/s (2402 bytes in 0.004s)
2048+0 records in
2048+0 records out
1048576 bytes (1.0MB) copied, 0.212922 seconds, 4.7MB/s
* Failed to verify blackrose image *
0 KB/s (2 bytes in 0.005s)
Click to expand...
Click to collapse
EDIT: Installed cyanogen 7.1, Blackrose install worked flawlessly. I guess it was the stock GB rom that was causing issues. Flashing ICS now.

Related

[Q] pls help pls some error occured when rooting with super one click

SuperOneClick v1.8.0.0
Checking drivers...
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Getting OS Version...
2.1-update1
OK
Pushing psneuter...
1078 KB/s (585731 bytes in 0.530s)
OK
chmod psneuter...
OK
Running psneuter...
OK
***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***
Killing ADB Server...
* server not running *
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running psneuter...
ROOTED
Pushing busybox...
1056 KB/s (1062992 bytes in 0.983s)
OK
chmod busybox...
OK
Getting mount path...
rootfs / rootfs ro 0 0
FAILED
tell me what is this ?? is my phone rooted ? but i think no help pls
Try the newest version of SuperOneClick at http://forum.xda-developers.com/showthread.php?t=803682
Make sure .NET Framework v2.0 or above is installed on your PC if you're on windows.
Make sure that Android drivers for your phone are properly installed.
Make sure you run SuperOneClick as administrator.
And yes use the latest version.

[Q] Can't S-off !!!

I've tried all the s-off guides tu unlock my incredible s, but every time, when i try to flash the RUU, it dosen't work Someone to help me
What hboot u on?
more info u give the help u will get in return
Sent from my HTC Incredible S using xda premium
jules290496 said:
I've tried all the s-off guides tu unlock my incredible s, but every time, when i try to flash the RUU, it dosen't work Someone to help me
Click to expand...
Click to collapse
sharkman3d said:
What hboot u on?
more info u give the help u will get in return
Sent from my HTC Incredible S using xda premium
Click to expand...
Click to collapse
^^^^^^^^^^^^^^^^^^ What he said!!!!!!!! ^^^^^^^^^^^^^^^^
More information please.
Sorry I'm on 2.01.0001
What error did you get?
jules290496 said:
I've tried all the s-off guides tu unlock my incredible s, but every time, when i try to flash the RUU, it dosen't work Someone to help me
Click to expand...
Click to collapse
Even i have this problem with the new version of HBOOT. Did you try the tool given by Nonverbose?? And are you having any radio issues?
I got this in my terminal:
Waiting for device to connect
adb server is out of date. killing...
* daemon started successfully *
Device found
Is the device rooted?
y OR n:n
Waiting for device to connect
adb server is out of date. killing...
* daemon started successfully *
Device found
Pushing tacoroot
adb server is out of date. killing...
* daemon started successfully *
351 KB/s (14475 bytes in 0.040s)
Correcting permissions
adb server is out of date. killing...
* daemon started successfully *
tacoroot rebooting phone to recovery
adb server is out of date. killing...
* daemon started successfully *
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by
both Justin Case and Dan Rosenberg (Rosenberg fist). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
Rebooting into recovery, please press Volume+, Volume- and Power at the same tim
e, and reboot the system.
rm failed for /data/data/recovery/log, No such file or directory
link failed No such file or directory
Waiting for device to connect
Device found
tacoroot starting adbD as root
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by
both Justin Case and Dan Rosenberg (Rosenberg fist). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
Rebooting into root.
cannot create /data/local.prop: permission denied
Waiting for device to connect
Device found
Pushing misc_version
1006 KB/s (367096 bytes in 0.356s)
Correcting permissions
Downgrading main version
--set_version set. VERSION will be changed to: 2.00.000.0
Patching and backing up misc partition...
Error opening input file.
Do you need to create a goldcard?
y OR n:n
Undoing tacoroot (if applied)
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by
both Justin Case and Dan Rosenberg (Rosenberg fist). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
rm failed for /data/local.prop, No such file or directory
Root removed, rebooting
Waiting for device to connect
error: protocol fault (no status)
Device found
Cleaning temp files
* daemon not running. starting it now *
* daemon started successfully *
Checking version-main
< waiting for device >
version-main: 3.11.405.2
finished. total time: 0.002s
If the version-main returns 2.00.000.0 you should be
able to run the RUU downgrade. If it does not, answer n to the
unlocked bootloader prompt no matter what.
Do you have an unlocked bootloader from htcdev.com?
y OR n:y
...
(bootloader) Lock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.297s
Note: run the RUU in fastboot mode
If all steps were completed without error,
you should be ready to run the RUU downgrade
Appuyez sur une touche pour continuer...
And when i try to flash the RUU for downgrad, it say : The update utility can't update the android phone.
Try to obtain the correct rom update utility and try again ( it's translated from french)
InsertDumbNick said:
Even i have this problem with the new version of HBOOT. Did you try the tool given by Nonverbose?? And are you having any radio issues?
Click to expand...
Click to collapse
Yes, it was the first i tried...
Is the RUU you have the correct one for your region? The fact you are choosing not to make a goldcard could be having an effect.
Type this command into cmd while your phone is in fastboot mode 'fastboot oem lock'. I did that before I run the process.
Sent from my HTC Incredible S using xda premium
jules290496 said:
I got this in my terminal:
Waiting for device to connect
adb server is out of date. killing...
* daemon started successfully *
Device found
Is the device rooted?
y OR n:n
Waiting for device to connect
adb server is out of date. killing...
* daemon started successfully *
Device found
Pushing tacoroot
adb server is out of date. killing...
* daemon started successfully *
351 KB/s (14475 bytes in 0.040s)
Correcting permissions
adb server is out of date. killing...
* daemon started successfully *
tacoroot rebooting phone to recovery
adb server is out of date. killing...
* daemon started successfully *
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by
both Justin Case and Dan Rosenberg (Rosenberg fist). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
Rebooting into recovery, please press Volume+, Volume- and Power at the same tim
e, and reboot the system.
rm failed for /data/data/recovery/log, No such file or directory
link failed No such file or directory
Waiting for device to connect
Device found
tacoroot starting adbD as root
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by
both Justin Case and Dan Rosenberg (Rosenberg fist). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
Rebooting into root.
cannot create /data/local.prop: permission denied
Waiting for device to connect
Device found
Pushing misc_version
1006 KB/s (367096 bytes in 0.356s)
Correcting permissions
Downgrading main version
--set_version set. VERSION will be changed to: 2.00.000.0
Patching and backing up misc partition...
Error opening input file.
Do you need to create a goldcard?
y OR n:n
Undoing tacoroot (if applied)
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by
both Justin Case and Dan Rosenberg (Rosenberg fist). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
rm failed for /data/local.prop, No such file or directory
Root removed, rebooting
Waiting for device to connect
error: protocol fault (no status)
Device found
Cleaning temp files
* daemon not running. starting it now *
* daemon started successfully *
Checking version-main
< waiting for device >
version-main: 3.11.405.2
finished. total time: 0.002s
If the version-main returns 2.00.000.0 you should be
able to run the RUU downgrade. If it does not, answer n to the
unlocked bootloader prompt no matter what.
Do you have an unlocked bootloader from htcdev.com?
y OR n:y
...
(bootloader) Lock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.297s
Note: run the RUU in fastboot mode
If all steps were completed without error,
you should be ready to run the RUU downgrade
Appuyez sur une touche pour continuer...
And when i try to flash the RUU for downgrad, it say : The update utility can't update the android phone.
Try to obtain the correct rom update utility and try again ( it's translated from french)
Click to expand...
Click to collapse
OK, during the running of this script, when tacoroot says starting adb as root, do you see a # prompt?
From the messages, it looks like tacoroot is not getting temproot in order to update the mainver value to 2.00.0000. At the end of the script your mainver is still 3.11.405.2.
tpbklake said:
OK, during the running of this script, when tacoroot says starting adb as root, do you see a # prompt?
From the messages, it looks like tacoroot is not getting temproot in order to update the mainver value to 2.00.0000. At the end of the script your mainver is still 3.11.405.2.
Click to expand...
Click to collapse
No, i don't see any # and i tried whith and without goldcard
jules290496 said:
No, i don't see any # and i tried whith and without goldcard
Click to expand...
Click to collapse
Yeah, the whole key to the script is getting temp root access so that the mainver can be modified to 2.00.0000.
If that doesn't work, the whole goldcard and RUU thing will not work.
The best thing you could try is to open a command window and try manually typing the commands in and post the command window to help isolate the issue.
I think i will give up, thanks anyway
jules290496 said:
I think i will give up, thanks anyway
Click to expand...
Click to collapse
You have a custom recovery installed?
No, i don't now how to do it without revolutionary...
jules290496 said:
No, i don't now how to do it without revolutionary...
Click to expand...
Click to collapse
So the phone is completely stock, just unlocked bootloader?
Yes it's completely stock
jules290496 said:
Yes it's completely stock
Click to expand...
Click to collapse
Try locking the bootloader and doing a factory reset. Boot into recovery once, turn fastboot off and USB debugging on and run the newest version (3.2) of the script again.
Ok, i will try

how to enable init.d support?

im using stock 4.1.1 (rooted), i know batakang & joker support init.d but i prefer stock & want to mod it a little.
script manager does make few script's work, but cannot supercharge n stuff like that without init.d
i tried using the init.d enabler script but doesn't work & also pimp my rom uses the init.d enabler script so that doesn't work either.
so any1 have any ideas on how to enable init.d support for stock 4.1.1
I wrote a little guide and the required files in a .zip hosted on my Dropbox.
If you want an auto-mated Windows batch file to install it AND adbd insecured...
Use the Ext4 bat file.
im a little noob to do it manually so i tried the bat file method, which failed & here's the error,
Make sure your phone is NOT set to USB Mass Storage.
Make sure USB Debugging is enabled.
Make sure you are ROOTED before doing this.
Press any key to continue.
Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
4548 KB/s (145332 bytes in 0.031s)
23 KB/s (370 bytes in 0.015s)
3896 KB/s (1867568 bytes in 0.468s)
0 KB/s (37 bytes in 1.000s)
0 KB/s (138 bytes in 1.000s)
cp: /system/xbin/busybox: No such file or directory
rm failed for /system/xbin/run-parts, No such file or directory
link failed No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/run-parts: No such file or directory
Rebooting. When it shows 'remount sucessful' it means it worked.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
my Atrix HD is rooted, made sure usb debugging is on, also tried installing busybox to system/xbin but in stock JB it only installs in system/bin so tried changing the lines with xbin to bin in "InstallerForExt4Devices.bat" but still does not work.
thanks for the help but i guess this phone is not for noobs
coldfear00 said:
im a little noob to do it manually so i tried the bat file method, which failed & here's the error,
Make sure your phone is NOT set to USB Mass Storage.
Make sure USB Debugging is enabled.
Make sure you are ROOTED before doing this.
Press any key to continue.
Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
4548 KB/s (145332 bytes in 0.031s)
23 KB/s (370 bytes in 0.015s)
3896 KB/s (1867568 bytes in 0.468s)
0 KB/s (37 bytes in 1.000s)
0 KB/s (138 bytes in 1.000s)
cp: /system/xbin/busybox: No such file or directory
rm failed for /system/xbin/run-parts, No such file or directory
link failed No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/run-parts: No such file or directory
Rebooting. When it shows 'remount sucessful' it means it worked.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
my Atrix HD is rooted, made sure usb debugging is on, also tried installing busybox to system/xbin but in stock JB it only installs in system/bin so tried changing the lines with xbin to bin in "InstallerForExt4Devices.bat" but still does not work.
thanks for the help but i guess this phone is not for noobs
Click to expand...
Click to collapse
Try the busy box installer from play store.
Sent from my MotoAHD Maxx
Youngunn2008 said:
Try the busy box installer from play store.
Sent from my MotoAHD Maxx
Click to expand...
Click to collapse
i have busybox pro from Gplay also enabled adbd insecure but still no use
You need the "normal install" not the smart install
Sent from my phone.
Markyzz said:
You need the "normal install" not the smart install
Sent from my phone.
Click to expand...
Click to collapse
i always do normal install of busybox.
coldfear00 said:
i always do normal install of busybox.
Click to expand...
Click to collapse
With busy box app you can select to install it to xbin as well.
Sent from my MotoAHD Maxx
Youngunn2008 said:
With busy box app you can select to install it to xbin as well.
Sent from my MotoAHD Maxx
Click to expand...
Click to collapse
Yup. IIRC I just manually copied the files into xbin and init.d worked after that.
Sent from my phone.
Youngunn2008 said:
With busy box app you can select to install it to xbin as well.
Sent from my MotoAHD Maxx
Click to expand...
Click to collapse
when i select system/xbin installation fails, only installs in system/bin
Markyzz said:
Yup. IIRC I just manually copied the files into xbin and init.d worked after that.
Sent from my phone.
Click to expand...
Click to collapse
good for you bro, i also tried the same but no use.
im giving up on this phone, going for nexus 4
accidentally double post, sorry

[Q] MSM7227 stuck on waiting.

I was following the guide to unlock the bootloader for the Xperia X8 and have gotten here:
Code:
Getting ROOT rights.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
1540 KB/s (585731 bytes in 0.731s)
error: protocol fault (no status)
Waiting...
Removing NAND MPU restrictions via SEMC backdoor. Permanent. Require ROOT rights.
66 KB/s (3087 bytes in 0.045s)
success
Waiting ...
Getting ROOT rights.
Waiting ...
It's been stuck on waiting for at least 15 minutes. There's also no USB Debugging notification, leading me to believe that the phone is disconnected. What should I do? Should I just reconnect the phone or redo the whole process?
Never mind. Just disconnected the phone and rebooted it and restarted the program and now it works.

Amazon Fire 7-inch tablet rooting error messages

Hi, I recently updated my Amazon Fire 7" 5th Gen tablet to the latest system update & prior to this the tablet had already been rooted when it was running Android 5.0.1, but now the newer update has un-rooted the device and I am having difficulties re-rooting the device as now I am receiving some error messages in the Amazon Fire Tablet CMD Tool and I am unsure about what I have to do to resolve the issue....Below is a copy of the error messages I am receiving:
--------------------------------------------------------------------------------
[*] NOTE this will not work unless your fastboot drivers are installed
[*] see option 1 ADB Driver install.
[*] Once the screen is black and says fastboot in the corner
[*] press and key to continue the script.
--------------------------------------------------------------------------------
...
(bootloader) APPEND KERNEL CMDLINE
OKAY [ 0.016s]
finished. total time: 0.016s
resuming boot...
OKAY [ 0.000s]
finished. total time: 0.000s
--------------------------------------------------------------------------------
[*] your device is rebooting and will inject root files.
--------------------------------------------------------------------------------
remount succeeded
759 KB/s (170232 bytes in 0.218s)
61 KB/s (1976 bytes in 0.031s)
1570 KB/s (75364 bytes in 0.046s)
2984 KB/s (5904943 bytes in 1.931s)
1360 KB/s (29972 bytes in 0.021s)
mkdir failed for /system/app/SuperSU, File exists
mkdir failed for /system/bin/.ext, File exists
cp: /system/xbin/su: Operation not permitted
Unable to chmod /system/xbin/su: Operation not permitted
chcon: Could not label /system/xbin/su with ubject_r:system_file:s0: Operation not permitted
cp: /system/xbin/daemonsu: Text file busy
cp: /system/xbin/supolicy: Operation not permitted
Unable to chmod /system/xbin/supolicy: Operation not permitted
chcon: Could not label /system/xbin/supolicy with ubject_r:system_file:s0: Operation not permitted
cp: /system/bin/app_process32_original: Text file busy
--------------------------------------------------------------------------------
[*] Once the screen is black and says fastboot in the corner
[*] press and key to continue the script.
--------------------------------------------------------------------------------
...
(bootloader) APPEND KERNEL CMDLINE
OKAY [ 0.006s]
finished. total time: 0.007s
resuming boot...
OKAY [ 0.497s]
finished. total time: 0.497s
--------------------------------------------------------------------------------
[*] your device is rebooting and will finish the root process.
--------------------------------------------------------------------------------
Thanks in advance for any help and advice you can give to me.
If you have 5.1.1, the root procedure is a bit different. Start here:
http://forum.xda-developers.com/amazon-fire/help/help-thread-question-noob-friendly-t3205441
shabuboy said:
If you have 5.1.1, the root procedure is a bit different. Start here:
http://forum.xda-developers.com/amazon-fire/help/help-thread-question-noob-friendly-t3205441
Click to expand...
Click to collapse
Thank you shabuboy, I will read through the thread and see if any of the information can help me....:good:
I've read through the links enlisted and watched the tutorials but I've still not been able to root my device as I continue to get the same error message ...I wish now I had not updated to Android 5.1.1 and at this point I think I'm going to give up until the next update or so ....
If you followed the procedures for 5.1.1 and/or used the supertool and still did not work, I would attempt to disable OTAs at the least.
shabuboy said:
If you followed the procedures for 5.1.1 and/or used the supertool and still did not work, I would attempt to disable OTAs at the least.
Click to expand...
Click to collapse
Yes I have disabled the OTAs now, as well as this I also found another XDA user who's having the same problem with he's device: http://forum.xda-developers.com/hd8-hd10/help/looking-help-rooting-kindle-5th-gen-v5-t3285665 & I've contacted him to see if he has found a solution to his, hopefully he'll get back to me.
DeeKay10 said:
Yes I have disabled the OTAs now, as well as this I also found another XDA user who's having the same problem with he's device: http://forum.xda-developers.com/hd8-hd10/help/looking-help-rooting-kindle-5th-gen-v5-t3285665 & I've contacted him to see if he has found a solution to his, hopefully he'll get back to me.
Click to expand...
Click to collapse
Have your tried doing a restore with the 5.1.1 stock firmware before proceeding with the root process?
I may try this option next
I may be forced to try this option next, I'll give a feedback on the results once I've done this although I did factory restore obviously to no avail as once the update has been done it cannot be downgraded....
Good news!!!! I now have full root access/super user privileges
***UPDATE***
I now have full root access to my Amazon device, I think that some of the files that were giving the error messages were corrupted and therefore last night I re-installed/restored the android 5.1.1 firmware to the tablet and this resolved the problem …Thank you both "shabuboy & thekrakah", I much appreciate your contribution to my query and thankfully now my device is operating correctly....

Categories

Resources