So I bricked my Kinde Fire HDX by changing the build.prop and not fixing permissions. I have adb access but no root (I don't know why :S). Would a factory reset work? If not, how can I get to fix the build.prop or replace it with the old one? thank very much, I've been a couple hours looking for solution but I couldn't find any.
No, a factory reset would only break it further. It would remove your adb access and not fix anything. What makes you think you lost root? Have you tried "adb shell" then "su"?
Sent from my Amazon Tate using Tapatalk
r3pwn said:
No, a factory reset would only break it further. It would remove your adb access and not fix anything. What makes you think you lost root? Have you tried "adb shell" then "su"?
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
I used the HDX ToolKit v0.92 to check the root access, and it said "Please grant root on your device"
I've also tried "adb shell", and then "su", but it just returns "su" again. I am new with adb commands so I don't really know what it should show.
Thank you very much for your help
May I ask what version you were on before you bricked?
Sent from my Amazon Tate using Tapatalk
14.3.2.3.2, last update I think.
?
peter_b93 said:
14.3.2.3.2, last update I think.
Click to expand...
Click to collapse
Fixed?
jimyv said:
Fixed?
Click to expand...
Click to collapse
Nope, I couldn't find any way to get root acces again. But nevermind, my new kindle fire will be here in two days. I am surprised how well amazon costumer service works. Even though I bought my kindle in the US and now I am in Spain (not going back), they called me from the US for free, and they are paying all the shipping costs and sending it by priority shipping.
I am still interested if anyone knows how to fix it, just for fun
well
peter_b93 said:
Nope, I couldn't find any way to get root acces again. But nevermind, my new kindle fire will be here in two days. I am surprised how well amazon costumer service works. Even though I bought my kindle in the US and now I am in Spain (not going back), they called me from the US for free, and they are paying all the shipping costs and sending it by priority shipping.
I am still interested if anyone knows how to fix it, just for fun
Click to expand...
Click to collapse
It sounds like to me that you still root access you just were not mounted RW in other words it would not boot up completely so you could hit allow to the adb Shell. So you will have to mount system rw manually Try last 3 pages of this thread http://forum.xda-developers.com/showthread.php?t=2588608. He can fix you most likely if you can comprehend and follow directions.. or if ur understanding adb is fair you'll be able to probably extract your repair from the thread as is.
jimyv said:
It sounds like to me that you still root access you just were not mounted RW in other words it would not boot up completely so you could hit allow to the adb Shell. So you will have to mount system rw manually Try last 3 pages of this thread http://forum.xda-developers.com/showthread.php?t=2588608. He can fix you most likely if you can comprehend and follow directions.. or if ur understanding adb is fair you'll be able to probably extract your repair from the thread as is.
Click to expand...
Click to collapse
I've tried what it is said in the other thread. However, the problem there is that the guy cannot get his device to be recognized.
I've tried this:
adb root
adb shell
su
mount -o rw,remount /system *****- if this fails, try: mount -o remount /system
chmod 644 /system/build.prop
chown root.root /system/build.prop
reboot
But adb root gives me this error:
adbd cannot run as root in production builds
On the other hand if I skip the "adb root" step I cannot go further than "su" since I don't get the "[email protected]:/ #" line.
well
peter_b93 said:
I've tried what it is said in the other thread. However, the problem there is that the guy cannot get his device to be recognized.
I've tried this:
adb root
adb shell
su
mount -o rw,remount /system *****- if this fails, try: mount -o remount /system
chmod 644 /system/build.prop
chown root.root /system/build.prop
reboot
But adb root gives me this error:
adbd cannot run as root in production builds
On the other hand if I skip the "adb root" step I cannot go further than "su" since I don't get the "[email protected]:/ #" line.
Click to expand...
Click to collapse
Well since you do have ADB connectivity why can't you hook a bruting utility and push root ? Romaster_3.4.3.7593_Setup use as describe back in the roll back thread and the rooting thread 4 the new yes I kno wat is in chinese but this is the 1 that you must use sent you cannot install the apk install software plugin your tablet look at the upper right corner you will see an gear icon tap that then second row down second icon over "root"
jimyv said:
Well since you do have ADB connectivity why can't you hook a bruting utility and push root ? Romaster_3.4.3.7593_Setup use as describe back in the roll back thread and the rooting thread 4 the new yes I kno wat is in chinese but this is the 1 that you must use sent you cannot install the apk install software plugin your tablet look at the upper right corner you will see an gear icon tap that then second row down second icon over "root"
Click to expand...
Click to collapse
FIXED!!!!!
The chinese software worked! Thank you very much! As I first rooted with towelroot I wasn't aware that it was possible to root without booting into android! I think I won't edit the build.prop again lol.
peter_b93 said:
FIXED!!!!!
The chinese software worked! Thank you very much! As I first rooted with towelroot I wasn't aware that it was possible to root without booting into android! I think I won't edit the build.prop again lol.
Click to expand...
Click to collapse
Ok now use this http://forum.xda-developers.com/showthread.php?t=2532818 and uninstall romanager from pc...and reboot... And BTW modifying your build prop is alot easier useing build prop editing app. It takes care of permissions anyway as long as you entrys are correct..
jimyv said:
Ok now use this http://forum.xda-developers.com/showthread.php?t=2532818 and uninstall romanager from pc...and reboot... And BTW modifying your build prop is alot easier useing build prop editing app. It takes care of permissions anyway as long as you entrys are correct..
Click to expand...
Click to collapse
Good call on RomMaster. I have no idea what it is doing since I haven't had any time to look at it, but I'd figured it was an app like TR. At any rate, nicely done. :good:
sweet
GSLEON3 said:
Good call on RomMaster. I have no idea what it is doing since I haven't had any time to look at it, but I'd figured it was an app like TR. At any rate, nicely done. :good:
Click to expand...
Click to collapse
I'm not sure either that's why when I used it I was on a blacklisted unit and I kept the PC and the tablet and airplane mode at all times. Until I was certain I got all the files off of both before I let them go to Wi-Fi Chinese files that is.. But one thing I was very curious about is if you open that tool up the Chinese tool that is an you go to the same page you would hit the anchor to root to your device just below that it says fastboot I'm wondering if they have a fastboot working for also too bad nobody here know Chinese..
Related
hey guys i need some help plz!!!
i had rooted my asus prime.......and my bootloader was still locked, after i rooted my device i also had rootkeeper to protect it incase i update.....to make a long story short, i was so anxious when jelly bean was released i wasnt thinking so i proceeded without temp unroot first before i did the update......so after everything completed i went to restore my root access and it was gone..........was so pissed off, so now from every research i did it says that there is no current root options for the prime jelly bean, anybody knows how to get it back or a way to root again.....im willing to downgrade if i can to get back my root access. please help!!!
You can't downgrade without using the ASUS unlocker tool. Yeah, I know... shocked me too....
There isnt a working root method working as of yet if you are certain you have lost root access.
Some people report having partial root and even having some apps that still retained root. If none of that applies to you then your screwed with the rest of us.
hx4700 Killer said:
You can't downgrade without using the ASUS unlocker tool. Yeah, I know... shocked me too....
There isnt a working root method working as of yet if you are certain you have lost root access.
Some people report having partial root and even having some apps that still retained root. If none of that applies to you then your screwed with the rest of us.
Click to expand...
Click to collapse
yea thanks for replying tho, as far as the partial root goes.....im not sure if im that lucky and i checked system/bin there is no su file and also when i enter adb shell command then su i got the $ sign instead of the #.........but i still have superuser app !
weakenfalls said:
yea thanks for replying tho, as far as the partial root goes.....im not sure if im that lucky and i checked system/bin there is no su file and also when i enter adb shell command then su i got the $ sign instead of the #.........but i still have superuser app !
Click to expand...
Click to collapse
If you don't get # you don't have root.
I actually had an SU in xbin but it wasnt owned by root.
hx4700 Killer said:
If you don't get # you don't have root.
I actually had an SU in xbin but it wasnt owned by root.
Click to expand...
Click to collapse
I get # in ADB but not using Terminal Emulator. What does this mean?
Restorer said:
I get # in ADB but not using Terminal Emulator. What does this mean?
Click to expand...
Click to collapse
Hmmm I will have to try in ADB and see what happens.
If your prompt changes to # in ADB then that means you should have root access. With that you can restore full root properly to your device. You may be one of the lucky ones that just needs to uninstall and reinstall Superuser.
hx4700 Killer said:
If your prompt changes to # in ADB then that means you should have root access. With that you can restore full root properly to your device. You may be one of the lucky ones that just needs to uninstall and reinstall Superuser.
Click to expand...
Click to collapse
Well it did give me hope when I saw that but I can't get past stage 11 in this guide . I just cannot get ADB to mount /system as RW . Also entering su in Terminal Emulator gets "permission denied" and Superuser itself "fails" at updating binary.
Restorer said:
Well it did give me hope when I saw that but I can't get past stage 11 in this guide . I just cannot get ADB to mount /system as RW . Also entering su in Terminal Emulator gets "permission denied" and Superuser itself "fails" at updating binary.
Click to expand...
Click to collapse
What is the error when you issue the remount command? if I type remount I get: "remount: not found"
There is also an executeable that came with one of the 10000 root packages I have tried called fsrw. Pushing it to /data/local/tmp with ADB then running it via the adb shell out of that path should try to perform the remount.
If you are getting "operation denied" then you don't really have root =/
hx4700 Killer said:
What is the error when you issue the remount command? if I type remount I get: "remount: not found"
There is also an executeable that came with one of the 10000 root packages I have tried called fsrw. Pushing it to /data/local/tmp with ADB then running it via the adb shell out of that path should try to perform the remount.
If you are getting "operation denied" then you don't really have root =/
Click to expand...
Click to collapse
I get:
"mount: Operation not permitted" .
There you go, you are not really root
Curious that you get the # logo though. I had an SU in xbin but got no # prompt because its ownership was screwed up.
hx4700 Killer said:
There you go, you are not really root
Curious that you get the # logo though. I had an SU in xbin but got no # prompt because its ownership was screwed up.
Click to expand...
Click to collapse
Sorry, just tried again and now stage 11 is working! But then when I try 12 I get:
"r.apk of=/system/app/Superuser.apk
/data/local/tmp/Superuser.apk:cannot open for read: No such file or directory
1:[email protected]:/#"
re root jellybean
hi, to all those other rookies, i did a bit of reading and finally decided to update to JB from stock ICS .28 which was unlocked and rooted.
As i expected i lost root and have just manged to get it back, i first installed twrp for JB using fastboot method.
http://forum.xda-developers.com/showthread.php?t=1615990
then after trying [ROOT][TOOL]Debugfs automated root [09/18/2012] and SparkyRoot Apk having read this can possible restore root although not in my case, for me i uninstalled super user and re-flashed via twrp,
(version Superuser-3.2-arm-signed.zip from thread http://forum.xda-developers.com/showthread.php?t=1911024)
Then when i rebooted i noticed luckypatcher app requested SU and root access was now working
hx4700 Killer said:
There you go, you are not really root
Curious that you get the # logo though. I had an SU in xbin but got no # prompt because its ownership was screwed up.
Click to expand...
Click to collapse
Whooo! Just got my root back. I hadn't realised there are a couple of typos in the guide there and I was copying and pasting the long lines!
Big thanks to hx4700 Killer for making me wonder I must be doing something wrong :laugh:.
tomtomxp said:
hi, to all those other rookies, i did a bit of reading and finally decided to update to JB from stock ICS .28 which was unlocked and rooted.
As i expected i lost root and have just manged to get it back, i first installed twrp for JB using fastboot method.
http://forum.xda-developers.com/showthread.php?t=1615990
then after trying [ROOT][TOOL]Debugfs automated root [09/18/2012] and SparkyRoot Apk having read this can possible restore root although not in my case, for me i uninstalled super user and re-flashed via twrp,
(version Superuser-3.2-arm-signed.zip from thread http://forum.xda-developers.com/showthread.php?t=1911024)
Then when i rebooted i noticed luckypatcher app requested SU and root access was now working
Click to expand...
Click to collapse
Well.. I believe that everyone who'd not consider unlocking their tablets before the JB update would not unlock after losing root just because of the warranty, probably not because they don't know how but because about half of the forumers don't think it's worth the risk considering the hardware instabilities like the green camera module, light bleed etc.
And since you've already flashed a custom recovery you've unlocked more than just root, why not try a custom ROM based on stock JB?
Hello guys, i have a question here, i bought this tablet from Focalprice:
http://www.focalprice.com/CE0427B/Y...PX820_Dualcore_12GHz_Tablet_PC_with_WiFi.html
This tablet have the same specs of the Ippo Y88, BUT Y88 have 1.5ghz and mine have 1.2ghz, they use the SAME dualcore A5 processor, IMAPX820.
Well, i search on google, and use the tool here on XDA to find some information, but its impossible to find anything about this processor, and those tablets... I know they are simple tablets, but someone know if i can ROOT this thing using CWM and put some light ROM, or Cymod?
Thnaks for help, this forum is the best, and i love the Galaxy S3 forum!
This proc is new, or have some other name?
up
up.
too cheap to be rooted? xD
p_morales said:
up.
too cheap to be rooted? xD
Click to expand...
Click to collapse
Hehe, idk maybe this tablet is not so good, so none develop for it. ;x
p_morales said:
up.
too cheap to be rooted? xD
Click to expand...
Click to collapse
How is your answer supposed to help anybody? People buy cheap tablets for a lot of reasons, I bought this to use it for a home automation system and it's perfectly fit for this purpose.
I'm also interested in rooting it, so any information ( ROMs , ideas on how to root it or how to make a ROM dump without root, etc) would be much appreciated.
crwro said:
How is your answer supposed to help anybody? People buy cheap tablets for a lot of reasons, I bought this to use it for a home automation system and it's perfectly fit for this purpose.
I'm also interested in rooting it, so any information ( ROMs , ideas on how to root it or how to make a ROM dump without root, etc) would be much appreciated.
Click to expand...
Click to collapse
My answer helps as yours. I only wanted to say that Aldighieri is not the only person looking for a way to root it.
Maybe nobody will develop a rooting method for this kind of tablets, but there could be an existing method that works ¿isnt it? hope so.
Thanks all of u!
Calm down boys, hehe!
So, none know a way? Is impossible to root this thing? =/
Aldighieri said:
Calm down boys, hehe!
So, none know a way? Is impossible to root this thing? =/
Click to expand...
Click to collapse
If you or somebody else can provide/find the original ROM I might be able to root it. I'm not an expert but I've managed to root an "unrootable" android tv box once. I've asked the guys at focalprice for the ROM but they didn't answer my email and I don't have too much hope given their awful customer service.
Oh thanks! Ill try to find it with someone on ebay, or google, if i find it i tell you! Thanks! )
Same problem for me. Excelent tablet, bu timpossible to root. When I try (with different methods: unlockroot,z4root, superoneclick, root bin4ay, rootx...) a massage say that is rooted, but when I try to install Superuser don't work for me. Please, help!
I asked for sellers on ebay to try to find the rom with the providers, but have no awnser yet, if u can, try it too! ^^
Me too on focal price. If i know something, I will post about it. Is very a rare case...
Thanks.
Aldighieri said:
I asked for sellers on ebay to try to find the rom with the providers, but have no awnser yet, if u can, try it too! ^^
Click to expand...
Click to collapse
elefantino9 said:
Me too on focal price. If i know something, I will post about it. Is very a rare case...
Thanks.
Click to expand...
Click to collapse
Nice! Thanks!
Still no answer from focalprice on my side and I think the best chance to find the ROM is via ebay sellers. I've tried a few methods of rooting the tablet without any luck and I came to the conclusion (with my limited knowledge) that the problem is related to the file system the ROM is packed, which doesn't allow changing file permissions. I can't go further without risking bricking my tablet, but if we find the original ROM I may be able to unpack /repack it, changing the permissions in the process. It may be a long shot but it's worth a try.
Thanks everybody for your efforts!
Fast response from focalprice: a word file with how to use this tablet: on, off, mute, how listen to the music...wow!
IF you find the rom ok, but you can't use it because the recovery is not present on this tablet. If you can do somethins, please, post it.
Thanks :good:
crwro said:
Still no answer from focalprice on my side and I think the best chance to find the ROM is via ebay sellers. I've tried a few methods of rooting the tablet without any luck and I came to the conclusion (with my limited knowledge) that the problem is related to the file system the ROM is packed, which doesn't allow changing file permissions. I can't go further without risking bricking my tablet, but if we find the original ROM I may be able to unpack /repack it, changing the permissions in the process. It may be a long shot but it's worth a try.
Thanks everybody for your efforts!
Click to expand...
Click to collapse
Hello friends!
I'm completly frustated. Google is burned with my researches. I have found this video and I think that is our tablet, but this combination don't work for me. Any idea?
Thank you for the info. I've tried the method in the video and it doesn't work on my tablet either, so probably we have a different model. Even if there is no recovery mode as the guys from focalprice say, I am sure that the ROM can be updated/reinstalled somehow, via usb maybe?
I'll keep trying to make a ROM dump from my tablet and I'll post here if I succeed.
Aldighieri said:
Hello guys, i have a question here, i bought this tablet from Focalprice:
http://www.focalprice.com/CE0427B/Y...PX820_Dualcore_12GHz_Tablet_PC_with_WiFi.html
This tablet have the same specs of the Ippo Y88, BUT Y88 have 1.5ghz and mine have 1.2ghz, they use the SAME dualcore A5 processor, IMAPX820.
Well, i search on google, and use the tool here on XDA to find some information, but its impossible to find anything about this processor, and those tablets... I know they are simple tablets, but someone know if i can ROOT this thing using CWM and put some light ROM, or Cymod?
Thnaks for help, this forum is the best, and i love the Galaxy S3 forum!
Click to expand...
Click to collapse
Okay, I found a way to root it, but its on different device (Infotmic GF20). Firstly you have to enter recovery mode with adb (adb reboot recovery), then disconnect and reconnect usb cable, enter adb shell. If you have # as prompt, you can continue - it will work on your device too - if not, you have to obtain firmware from seller to root it. If you have #, type
Code:
ubiattach -m 1
busybox mount -tubifs /dev/ubi0_0 /system
Then exit adb shell, get su binaries and supersu app, and pull them to the device:
Code:
adb push su /system/xbin/
adb shell chown 0.0 /system/xbin/su
adb shell chmod 6755 /system/xbin/su
adb shell ln /system/xbin/su /system/bin/su
adb shell chown 0.0 /system/bin/su
adb shell chmod 6755 /system/bin/su
adb shell push supersu.apk /system/app/
Reboot device and it should work
OMG! Incredible!
My problem is the seller: they don't have the firmware, but I will try to understand all the process and I will try.
Thanks, thanks and thanks
lolet said:
Okay, I found a way to root it, but its on different device (Infotmic GF20). Firstly you have to enter recovery mode with adb (adb reboot recovery), then disconnect and reconnect usb cable, enter adb shell. If you have # as prompt, you can continue - it will work on your device too - if not, you have to obtain firmware from seller to root it. If you have #, type
Code:
ubiattach -m 1
busybox mount -tubifs /dev/ubi0_0 /system
Then exit adb shell, get su binaries and supersu app, and pull them to the device:
Code:
adb push su /system/xbin/
adb shell chown 0.0 /system/xbin/su
adb shell chmod 6755 /system/xbin/su
adb shell ln /system/xbin/su /system/bin/su
adb shell chown 0.0 /system/bin/su
adb shell chmod 6755 /system/bin/su
adb shell push supersu.apk /system/app/
Reboot device and it should work
Click to expand...
Click to collapse
Don't works for me. I can see the recovery (thanks), but when I unplug and plug the device, windows (xp) don't recognize the tablet. I use the Universal ADB drivers https://github.com/koush/UniversalAdbDriver, but I think that are the correct drivers. Any idea? Thanks! :good:
Here we have the solition, but I don't understand the recovery mode driver installation...
VRoot Cleanup Tool - Easily replace VRoot with SuperSU
From your Windows PC
OK everyone, here's the deal. I did the VRoot the toher day on my phone and it worked great. The problem is that it can be tricky to get the old Chinese Superuser app and SU binaries updated to SuperSU. As a result I decided to put this tool together to help update the VRoot files to SuperSU, and get rid of the old VRoot ones. What this means is that you can now clean up the Chinese Super User app and completely install SuperSU with a single click, from your Windows PC.
How to use:
Download Root Cleanup from here: https://www.dropbox.com/s/sto74q58uq4r1bj/root_cleaner.zip
Extract it to a folder on your computer.
Open the new folder and double click the clean_root.bat file.
Follow the directions.
** You will want to make sure that USB debugging is on (which it should be from VROOT) and that VRoot is closed when you run this. **
Also note I only have one phone to test with, and it worked great on the one I have. Please let me know if you have any other issues and I will try my best to help. Also, as always, not responsible for problems . <3
Edit: I just got asked via PM if this is to be run after freezing VRoot, etc. So I wanted to add here in case anyone else wondered. With this tool you do not need to freeze VRoot, delete any files, etc. My script will literally take care of everything for you. So, run VRoot and the phone will reboot. You can immediately close VRoot on your computer and run this to completely replace VRoot with SuperSU, and remove VRoot files.
This is my first time writing something like this, but so far I have a lot of people who told me it works fine. Please let me know if you have issues and Ill do my best to help! I went ahead and created this thread at the request of some people who have had good success with this on the other thread here: http://forum.xda-developers.com/showthread.php?t=2511815&page=29
Update: V4 is up - this version makes sure that ADB is accessible. Thank you @k1mu for helping me with this!
I want to ask you, why do you think the process on i9505 hangs on the line "cleaning up files" and does not automatically reboot the phone? You need to manually reboot it.
For the rest it works great!
Thank you
fabrilas said:
I want to ask you, why do you think the process on i9505 hangs on the line "cleaning up files" and does not automatically reboot the phone? You need to manually reboot it.
For the rest it works great!
Thank you
Click to expand...
Click to collapse
My guess would be these lines:
adb shell "su -c 'rm /dev/com.mgyun.shua.su'"
adb shell "su -c 'rm /dev/com.mgyun.shua.su.daemon'"
adb shell "su -c 'rm -rf /dev/com.mgyun.shua.su'"
adb shell "su -c 'rm -rf /dev/com.mgyun.shua.su.daemon'"
The issue is that I cant remember if com.mgyun.shua.su and com.mgyun.shua.su.daemon are directories or files. If you could confirm for me which they are then I will be happy to fix my tool!
Thx
Angie
it tells me that "device not found" any clues?
never mind the first statment if i put the file in the phone the run it from my computer it goes away. but I'm now going to put word for word what it tells me. "When prompted to grant root to ADB select yes. 'adb' is not recognized as an internal or external command, operable program or batch file. Once you have granted root to ADB press any key to continue... Press any key to continue . . .
but it never askes me to grant root to it it just sits there and does nothing and if i hit continue with out allowing it, it just deletes the su and unroots the phone. any clues about what I could be doing wrong
Works also with Galaxy S4 Italy Gt-i9505 :good:
ComputerBro2 said:
it tells me that "device not found" any clues?
never mind the first statment if i put the file in the phone the run it from my computer it goes away. but I'm now going to put word for word what it tells me. "When prompted to grant root to ADB select yes. 'adb' is not recognized as an internal or external command, operable program or batch file. Once you have granted root to ADB press any key to continue... Press any key to continue . . .
but it never askes me to grant root to it it just sits there and does nothing and if i hit continue with out allowing it, it just deletes the su and unroots the phone. any clues about what I could be doing wrong
Click to expand...
Click to collapse
If you are getting device not found that typically means that ADB is not able to access or find the phone. I would make sure that you close the VRoot tool as it will keep the debugging bridge tied up, and give you a device not found error. After you root you need make sure VRoot is closed before running my tool.
ComputerBro2 said:
it tells me that "device not found" any clues?
never mind the first statment if i put the file in the phone the run it from my computer it goes away. but I'm now going to put word for word what it tells me. "When prompted to grant root to ADB select yes. 'adb' is not recognized as an internal or external command, operable program or batch file. Once you have granted root to ADB press any key to continue... Press any key to continue . . .
but it never askes me to grant root to it it just sits there and does nothing and if i hit continue with out allowing it, it just deletes the su and unroots the phone. any clues about what I could be doing wrong
Click to expand...
Click to collapse
That "adb is not recognized.. " is because the batch file is not running with it's current directory in the folder where you extracted it.
@LilTechPrincess -
adding "cd %~dp0"
at the start of the clean_root.bat will ensure that it's able to find the files that it needs since that'll CD to the drive and path where the clean_root.bat was extracted.
LilTechPrincess said:
If you are getting device not found that typically means that ADB is not able to access or find the phone. I would make sure that you close the VRoot tool as it will keep the debugging bridge tied up, and give you a device not found error. After you root you need make sure VRoot is closed before running my tool.
Click to expand...
Click to collapse
okay i just needed to update my drivers witch is odd cause i just did it yesterday hmm. Anyway now it runs fine but it wont prompt me on my phone to allow root access to adb
ComputerBro2 said:
okay i just needed to update my drivers witch is odd cause i just did it yesterday hmm. Anyway now it runs fine but it wont prompt me on my phone to allow root access to adb
Click to expand...
Click to collapse
So did it fix your root to SuperSU?
Also, does anyone know how I can prompt root to ADB easier than this? Currently I am doing this to try and force the Superuser prompt:
adb shell "su -c 'touch /sdcard/invoke-root'"
If anyone knows how to do this better please let me know!
k1mu said:
That "adb is not recognized.. " is because the batch file is not running with it's current directory in the folder where you extracted it.
@LilTechPrincess -
adding "cd %~dp0"
at the start of the clean_root.bat will ensure that it's able to find the files that it needs since that'll CD to the drive and path where the clean_root.bat was extracted.
Click to expand...
Click to collapse
Thank you very much for the help! Im still a newb! haha Anyhow, I updated my tool with your suggestion.
LilTechPrincess said:
So did it fix your root to SuperSU?
Also, does anyone know how I can prompt root to ADB easier than this? Currently I am doing this to try and force the Superuser prompt:
adb shell "su -c 'touch /sdcard/invoke-root'"
If anyone knows how to do this better please let me know!
Click to expand...
Click to collapse
No the adb won't start on my phone
It say to me
rm failed for /sdcard/install-recovery.sh, No such file or directory
And now ? xD
Does it also say no device found?
Sent from my SCH-I545 using Tapatalk
Bfitz26 said:
Does it also say no device found?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
No it freze on this
rm failed for /sdcard/install-recovery.sh, No such file or directory
when i disconnect the pone say not found for 4 or 5 times and finish
---------- Post added at 08:49 PM ---------- Previous post was at 08:28 PM ----------
I tri 3 times
try to wipe all data.
Next try is to reinstall last firmware update whit odin or it trip my knox 0x0 to 0x1 ?
MexyHKR said:
It say to me
rm failed for /sdcard/install-recovery.sh, No such file or directory
And now ? xD
Click to expand...
Click to collapse
Thats not a big deal. Basically, I removed the /sdcard/install-recovery.sh from the script earlier and forgot to not try and delete a file that doesnt exist... Ill fix that! haha That doesnt hurt anything at all. Sowwy!
Ok now im freeze on Cleaning Up Files....
Your link is down
Tomsgt said:
Your link is down
Click to expand...
Click to collapse
The link has 2 hh's in the http
eklipz3 said:
The link has 2 hh's in the http
Click to expand...
Click to collapse
thanks did notice that
Finaly dont work on my GS4
PDA: I9505XXUEMJ7
MODEM: I9505XXUEMJ7
CSC: I9505ITVEMJ8
Try 2 times after full wipe and emergency firmware restore.
Freeze on Cleaning etc...
Now need to go sleep 1:06AM in italy
Good night and sorry for bad speak
I speak like a fish trying to speak Russian
I bought device from a friend and all he could tell me is that it's rooted and that OTA updates are disabled. It's 8.9 HDX, current version 14.3.2.4_user_324002120 and has Play Market and custom launcher. What are my steps to install a custom rom?
Aftermath__ said:
I bought device from a friend and all he could tell me is that it's rooted and that OTA updates are disabled. It's 8.9 HDX, current version 14.3.2.4_user_324002120 and has Play Market and custom launcher. What are my steps to install a custom rom?
Click to expand...
Click to collapse
You will need to do some homework. Instructions (at least starting points) are posted throughout this forum. Ditch the play market (especially Google play services and associated framework), custom launcher and any other non-stock mods before diving in. While most are benign others can cause problems and potentially lead to a brick. If you have no experience installing custom roms plan on considerable research as you have much to learn. If experienced be aware that Kindles are unlike most other Android devices: easy to brick and nearly impossible to recover - especially the newer HDX models. If you are eying your trusty fastboot cable or other bag of tricks be aware most will not work on an HDX.
Davey126 said:
You will need to do some homework. Instructions (at least starting points) are posted throughout this forum. Ditch the play market (especially Google play services and associated framework), custom launcher and any other non-stock mods before diving in. While most are benign others can cause problems and potentially lead to a brick. If you have no experience installing custom roms plan on considerable research as you have much to learn. If experienced be aware that Kindles are unlike most other Android devices: easy to brick and nearly impossible to recover - especially the newer HDX models. If you are eying your trusty fastboot cable or other bag of tricks be aware most will not work on an HDX.
Click to expand...
Click to collapse
Thanks, also he said something about changing device name in build.prop Is it important?
Aftermath__ said:
Thanks, also he said something about changing device name in build.prop Is it important?
Click to expand...
Click to collapse
Don't mess with build.prop (get it wrong, create a brick). For experienced users. Keep reading ...
Davey126 said:
Don't mess with build.prop (get it wrong, create a brick). For experienced users. Keep reading ...
Click to expand...
Click to collapse
Yeah, I kinda bricked it already. was following instructions and decided to reboot device, now i have black screen after "kindle fire" logo. Is this it or i have some option?
Aftermath__ said:
Yeah, I kinda bricked it already. was following instructions and decided to reboot device, now i have black screen after "kindle fire" logo. Is this it or i have some option?
Click to expand...
Click to collapse
You're done. Recovery is almost impossible.
Davey126 said:
You're done. Recovery is almost impossible.
Click to expand...
Click to collapse
Not necessarily...
@Aftermath__: Can you gain adb access?
EncryptedCurse said:
Not necessarily...
@Aftermath__: Can you gain adb access?
Click to expand...
Click to collapse
Yes. After the reboot i mentioned device was shown in device manager as "Android" and I installed Kindle driver and now it's visible in "adb devices".
Aftermath__ said:
Yes. After the reboot i mentioned device was shown in device manager as "Android" and I installed Kindle driver and now it's visible in "adb devices".
Click to expand...
Click to collapse
Great! Assuming it's just a permissions issue, just enter adb shell and try running the following commands:
Code:
su
chmod 0644 /system/build.prop
EncryptedCurse said:
Great! Assuming it's just a permissions issue, just enter adb shell and try running the following commands:
Code:
su
chmod 0644 /system/build.prop
Click to expand...
Click to collapse
I've got
Code:
[email protected]:/ $ su
su
1|[email protected]:/ $ chmod 0644 /system/build.prop
chmod 0644 /system/build.prop
Unable to chmod /system/build.prop: Read-only file system
Aftermath__ said:
I've got
Code:
[email protected]:/ $ su
su
1|[email protected]:/ $ chmod 0644 /system/build.prop
chmod 0644 /system/build.prop
Unable to chmod /system/build.prop: Read-only file system
Click to expand...
Click to collapse
Oh, right. I forgot.
Code:
su
mount -o remount,rw /system
chmod 0644 /system/build.prop
mount -o remount,ro /system
Lett me know if that works.
EncryptedCurse said:
Oh, right. I forgot.
Code:
su
mount -o remount,rw /system
chmod 0644 /system/build.prop
mount -o remount,ro /system
Lett me know if that works.
Click to expand...
Click to collapse
Code:
[email protected]:/ $ su
su
1|[email protected]:/ $ mount -o remount,rw /system
mount -o remount,rw /system
mount: Operation not permitted
255|[email protected]:/ $
I guess I lost root access after reboot.
Aftermath__ said:
Code:
[email protected]:/ $ su
su
1|[email protected]:/ $ mount -o remount,rw /system
mount -o remount,rw /system
mount: Operation not permitted
255|[email protected]:/ $
I guess I lost root access after reboot.
Click to expand...
Click to collapse
draxie has an approach to that situation with ghettoroot.
http://forum.xda-developers.com/showpost.php?p=57659692&postcount=2
EncryptedCurse said:
draxie has an approach to that situation with ghettoroot.
http://forum.xda-developers.com/showpost.php?p=57659692&postcount=2
Click to expand...
Click to collapse
It worked. Thank you so much for your help.
Aftermath__ said:
It worked. Thank you so much for your help.
Click to expand...
Click to collapse
Glad you are able to fix the problem. Props to EncryptedCurse for picking up the ball and pointing you in the right direction. Thanks also to draxie for posting a solution. Not many devices live through a soft brick. Well done.
I have issue with both manual upgrading and downgrading my .3.2.4 . After reboot grey logo is showed and it seems like it's frozen. I've waited 10 minutes and turned it off and on and it's back to the state before update. Any advice will be appreciated.
Aftermath__ said:
I have issue with both manual upgrading and downgrading my .3.2.4 . After reboot grey logo is showed and it seems like it's frozen. I've waited 10 minutes and turned it off and on and it's back to the state before update. Any advice will be appreciated.
Click to expand...
Click to collapse
Let's focus on upgrading to 3.2.5 as I believe it is the safer path (for the record, tweaking build.prop for a direct downgrade from 3.2.4 is also fine if you know what you're doing and can recover from a mistake). So you put the 3.2.5 bin obtained from here in the root ("internal storage") directory and then follow the instructions in the same post. When the device reboots to only get the grey Kindle Fire Logo. Is that correct?
Suggestions:
- be sure to reenable OTA updates if previously disabled. Keep wifi off, delete all wifi profiles and stay away from open hotspots
- make sure you have a 'clean' copy of build.prop. The contents are machine specific so I can't point you to a link. If unsure check with the previous owner to see if he modified it. Need to be real careful with this file. If the contents or permissions get messed your device can become non-responsive (a kinder way of saying 'soft brick').
- if still no luck try enabling wifi and disabling airplane mode. Some folks claim this is a necessary step (has not been my experience)
- a somewhat riskier step is performing a factory reset just prior to upgrading. Again, some posters have stated this allowed the update to proceed. However, there is a small risk of harming your device with this technique of the recovery partition is damaged and/or build.prop is messed.
From Amazon: To start the software update:
-Swipe down from the top of the screen to open Quick Settings, and then tap Settings.
-Tap Device, and then tap System Updates.
-Tap Update. Your Kindle Fire will restart during the software update. After the restart, the message "Installing system update" will appear on the screen.
I realize the above seems simplistic; you've probably done everything right. Just covering the basics before moving on.
Davey126 said:
Let's focus on upgrading to 3.2.5 as I believe it is the safer path (for the record, tweaking build.prop for a direct downgrade from 3.2.4 is also fine if you know what you're doing and can recover from a mistake). So you put the 3.2.5 bin obtained from here in the root ("internal storage") directory and then follow the instructions in the same post. When the device reboots to only get the grey Kindle Fire Logo. Is that correct?
Suggestions:
- be sure to reenable OTA updates if previously disabled. Keep wifi off, delete all wifi profiles and stay away from open hotspots
- make sure you have a 'clean' copy of build.prop. The contents are machine specific so I can't point you to a link. If unsure check with the previous owner to see if he modified it. Need to be real careful with this file. If the contents or permissions get messed your device can become non-responsive (a kinder way of saying 'soft brick').
- if still no luck try enabling wifi and disabling airplane mode. Some folks claim this is a necessary step (has not been my experience)
- a somewhat riskier step is performing a factory reset just prior to upgrading. Again, some posters have stated this allowed the update to proceed. However, there is a small risk of harming your device with this technique of the recovery partition is damaged and/or build.prop is messed.
From Amazon: To start the software update:
-Swipe down from the top of the screen to open Quick Settings, and then tap Settings.
-Tap Device, and then tap System Updates.
-Tap Update. Your Kindle Fire will restart during the software update. After the restart, the message "Installing system update" will appear on the screen.
I realize the above seems simplistic; you've probably done everything right. Just covering the basics before moving on.
Click to expand...
Click to collapse
All of the above was done, except factory reset. I started with upgrading to 3.2.5 as I followed the steps in your post. Link in this part
- download 3.2.5 here; print upgrade instructions
Click to expand...
Click to collapse
wasn't about 3.2.5 and I guess I shouldn't follow the instructions in it, but I did. I downloaded bin file from here and started update and after the reboot got stuck with grey logo. I restarted device and tried to downgrade, but got the same result. Wi-Fi is on and all of the networks are protected.
I believe build.prop is untouched and there were 5 backups in internal storage, although I think he messed with some system apps, because, and that is one of the reasons I'm doing this now, there is no working keyboard and I can't access "Keyboard Language" and "Keyboard Settings". Should I try factory reset?
Aftermath__ said:
All of the above was done, except factory reset. I started with upgrading to 3.2.5 as I followed the steps in your post. Link in this part
wasn't about 3.2.5 and I guess I shouldn't follow the instructions in it, but I did. I downloaded bin file from here and started update and after the reboot got stuck with grey logo. I restarted device and tried to downgrade, but got the same result. Wi-Fi is on and all of the networks are protected.
I believe build.prop is untouched and there were 5 backups in internal storage, although I think he messed with some system apps, because, and that is one of the reasons I'm doing this now, there is no working keyboard and I can't access "Keyboard Language" and "Keyboard Settings". Should I try factory reset?
Click to expand...
Click to collapse
Sorry about the mispointed link. I usually test those as occasionally a previous cut gets 'stuck' in the clipboard. Given where you have been and the other symptoms I would consider a factory reset. Be aware this is some risk. Not great but there. In most cases undesirable outcomes are limited to doing nothing to help/hurt the problem or device. On rare occasions you are left with a brick.
When the device comes back try the upgrade process again.
(out for a few hours; will check back later)
Davey126 said:
Sorry about the mispointed link. I usually test those as occasionally a previous cut gets 'stuck' in the clipboard. Given where you have been and the other symptoms I would consider a factory reset. Be aware this is some risk. Not great but there. In most cases undesirable outcomes are limited to doing nothing to help/hurt the problem or device. On rare occasions you are left with a brick.
When the device comes back try the upgrade process again.
(out for a few hours; will check back later)
Click to expand...
Click to collapse
I tried and i can't do factory reset because of the same issue as with the upgrade/downgrade. I guess the reason is that I flashed this recovery and I really shouldn't.
How should I go about factory resetting my rooted, HD 7" that's running a different launcher? So that it can go back to as clean as possible and be updatable and used normally without bricking/dying. I heard it's dangerous to just use the native factory reset as it can end up with bricks.
Its running on some older firmware that was rootable not long after it became possible and is running Vire Launcher instead of the typical amazon launcher. I'd like to go back to Stock somehow.
Sorry for the double post but seriously no-one knows how to go back to fully default?
Shadowshinra said:
Sorry for the double post but seriously no-one knows how to go back to fully default?
Click to expand...
Click to collapse
For stock with no root:
Run these commands to unblock OTA:
Code:
adb shell pm unblock com.amazon.dcp and
adb shell pm unblock com.amazon.otaverifier
Also, look for /system/priv-app/deviceSoftwareOTA.apk and make sure the extension is (plain) "apk"
Put OS 5.1.2 onto /sdcard (not inside a folder) and press Update now in Device settings.
For latest stock with root, follow this root guide: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950 without installing Gapps/xposed/makespace. If you're running OS 4.5.3 now you can use 5.2.0_stock_recovery_uboot.zip at step 10.
DoLooper said:
For stock with no root:
Run these commands to unblock OTA:
Code:
adb shell pm unblock com.amazon.dcp and
adb shell pm unblock com.amazon.otaverifier
Also, look for /system/priv-app/deviceSoftwareOTA.apk and make sure the extension is (plain) "apk"
Put OS 5.1.2 onto /sdcard (not inside a folder) and press Update now in Device settings.
For latest stock with root, follow this root guide: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950 without installing Gapps/xposed/makespace. If you're running OS 4.5.3 now you can use 5.2.0_stock_recovery_uboot.zip at step 10.
Click to expand...
Click to collapse
Seems simple enough, the adb commands seemingly worked but I can't seem to rename the APK_ back into APK using ES file explorer, it just says renaming progress and the bar doesn't fill up.. so I haven't done the last step yet.
Shadowshinra said:
Seems simple enough, the adb commands seemingly worked but I can't seem to rename the APK_ back into APK using ES file explorer, it just says renaming progress and the bar doesn't fill up.. so I haven't done the last step yet.
Click to expand...
Click to collapse
Try rebooting and see if it got renamed. Are you sure you're rooted and have root explorer on in es file explorer? Maybe you used JMZ's Fire Tool to block OTA? See if you have it and try that for unblocking. Or, if rooted this command might work:
Code:
adb -d shell "su -c 'mount -o remount,rw /system; cd /system/priv-app/; mv DeviceSoftwareOTA.apk_ DeviceSoftwareOTA.apk'"
If you can't get it renamed, try doing the update. Don't think it'll work, but worth a shot. If it doesn't work, you'll need to boot twrp and install 5.1.1 or 5.1.2 from there: http://forum.xda-developers.com/showpost.php?p=62011272&postcount=2
DoLooper said:
Try rebooting and see if it got renamed. Are you sure you're rooted and have root explorer on in es file explorer? Maybe you used JMZ's Fire Tool to block OTA? See if you have it and try that for unblocking. Or, if rooted this command might work:
Code:
adb -d shell "su -c 'mount -o remount,rw /system; cd /system/priv-app/; mv DeviceSoftwareOTA.apk_ DeviceSoftwareOTA.apk'"
If you can't get it renamed, try doing the update. Don't think it'll work, but worth a shot. If it doesn't work, you'll need to boot twrp and install 5.1.1 or 5.1.2 from there: http://forum.xda-developers.com/showpost.php?p=62011272&postcount=2
Click to expand...
Click to collapse
Definitely rooted, heck you yourself helped me do it a long time ago, even Root checker says i'm still rooted, I do have JMZ tool, the OTA section is gray though, reboot didn't help, will try the adb command
Edit, upon entering the command CMD appeared to hang/stall/do nothing. Not letting any other commands to be typed afterwards.
Shadowshinra said:
Edit, upon entering the command CMD appeared to hang/stall/do nothing. Not letting any other commands to be typed afterwards.
Click to expand...
Click to collapse
CTRL-C to get out. EDIT @Shadowshinra: Do you get # prompt with "adb shell" "su"?
DoLooper said:
CTRL-C to get out. EDIT @Shadowshinra: Do you get # prompt with "adb shell" "su"?
Click to expand...
Click to collapse
You mean the popup on the kindle? Now you mention it, It hasn't been popping up since I've been attempting this, so somehow I/it semi-unrooted itself despite the rootchecker saying it's fine? Or were the changed we did responsible?
Edit: Oh wait I know what you mean now, the # sign isn't there either, it's a $ so yeah It's unrooted itself somehow or I did something unknowingly, which is odd seeing as the Vire Launcher, root checker and all my apps are still working..
Edit2: Ran supersu, turned it off and on, appears to have fixed it? I was able to rename it aftar that.. it can't have been that simple lol..
Shadowshinra said:
Edit: Oh wait I know what you mean now, the # sign isn't there either, it's a $ so yeah It's unrooted itself somehow or I did something unknowingly, which is odd seeing as the Vire Launcher, root checker and all my apps are still working..
Edit2: Ran supersu, turned it off and on, appears to have fixed it? I was able to rename it aftar that.. it can't have been that simple lol..
Click to expand...
Click to collapse
Yes, there's a twilight-zone state in which root apps partially work but you can't get full superuser access until you update binaries by running superSU app. No idea how you lost su. Anyway, I trust you can update to unrooted stock 5.1.2 now.
DoLooper said:
Yes, there's a twilight-zone state in which root apps partially work but you can't get full superuser access until you update binaries by running superSU app. No idea how you lost su. Anyway, I trust you can update to unrooted stock 5.1.2 now.
Click to expand...
Click to collapse
When I tried to use that update it just says Validating update file, and seemingly loading forever, i'll edit if it ever completes, but if I turn on wifi it will try to download an update from there can that not be used instead or does that cause the bricks I've heard about?
Shadowshinra said:
When I tried to use that update it just says Validating update file, and seemingly loading forever, i'll edit if it ever completes, but if I turn on wifi it will try to download an update from there can that not be used instead or does that cause the bricks I've heard about?
Click to expand...
Click to collapse
The OTA update should be fine. I actually thought the manual method would be faster, but . . .
DoLooper said:
The OTA update should be fine. I actually thought the manual method would be faster, but . . .
Click to expand...
Click to collapse
Ah I see, however another issue has arisen, upon hitting update and it attempting to do so after a reboot, the team win recovery menu shows up instead, If I click reboot from there I'm just taken back to the dashboard on the original rooted firmware, I guess the TWRP is interfering in some manner? Also do I have to reenable the Fire Launcher and uninstall Virelauncher before all of this or will the updating process just do all of that.
Shadowshinra said:
Ah I see, however another issue has arisen, upon hitting update and it attempting to do so after a reboot, the team win recovery menu shows up instead, If I click reboot from there I'm just taken back to the dashboard on the original rooted firmware, I guess the TWRP is interfering in some manner? Also do I have to reenable the Fire Launcher and uninstall Virelauncher before all of this or will the updating process just do all of that.
Click to expand...
Click to collapse
@bibikalka, I totally forgot @Shadowshinra would have TWRP, coming from rooted OS4. Any problem with him following your steps here to restore stock? http://forum.xda-developers.com/fire-hd/general/how-to-restore-stock-fireos-t3164267 Thanks!