I am having issues with the casual install. I have tried the latest builds but I couldnt get them to connect. Any help would be great. It pretty much errors out without doing anything after the Heimdall script. It appears to be rooted but I dont know what all is supposed to be done when Heimdall runs. Any help would be great. New user to this sight, I'm a noob to this but not electronics and programming.
david_d_gates said:
I am having issues with the casual install. I have tried the latest builds but I couldnt get them to connect. Any help would be great. It pretty much errors out without doing anything after the Heimdall script. It appears to be rooted but I dont know what all is supposed to be done when Heimdall runs. Any help would be great. New user to this sight, I'm a noob to this but not electronics and programming.
Click to expand...
Click to collapse
Make sure you have all anti virus/security software disabled including Microsoft Security essentials/windows defender. That and driver problems are the two main culprits for issues using CASUAL.
Once you have done that, reopen CASUAL and try it again. If it fails, post your paste bin log link. Don't paste your log here, just the link. Without the log its difficult to see what's going on
Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Related
ive gone through all the steps and i even installed adb and all that... is it suppose to be in the same folder as the apkmanager ?... please help i just needa get the correct .xml to edit.
p.s. my device connected perfectly on the adb commands....
Code:
The program adb is missing or is not in your PATH,
please install it or fix your PATH variable
The program sox is missing or is not in your PATH,
please install it or fix your PATH variable
An attempt to help
Try reading over raziel23x 's wonderful thread here -->http://forum.xda-developers.com/showthread.php?t=1227179 Which may help with your problem. If after thoroughly reading over the thread, and you still can't solve your issue then provide a bit more in depth information about the issue you are having, and I will try to help you out as much as I can, since I have been playing around with APK Manager 5.0.1 recently. As for what is obvious, make sure your PATH environment variables are set properly, do a search in the forums, and you can find excellent documentation on how to do this. If you can't find it, then post back here, and I'll find it and post the link for you. Also, if your using an older version of APK Manager then you should give APK Manager 5.0.1 a try, or if your using another manager. I'm still learning some things as well, so go ahead and post back here, and I'll try to help, as helping you may help me to better understand things as well.
MOD EDIT : As requested by OP, I'm closing this thread.
Everyone can continue the rooting related discussions on the other thread linked here. Full root for Nook Tablet. [11/20/11] [Yes this is a permanent root!].
All,
Here is a "one click" script to root your Nook Tablet AND install gapps (Market) all in one shot. It also includes the latest superuser binary and apk (automatically installed). MAD PROPS to Indirect for being the first to get root on the NT. This script builds off of his (and others) work to make it a bit easier.
I need people to test this. That being said, RUN THIS AT YOUR OWN RISK. It may work perfectly, or it may explode your Nook. You've been warned!
1. Download and extract the zip file located at https://rapidshare.com/files/3156164791/NT-One-Click-Root-by-anlog.zip (PLEASE MIRROR THE FILE FOR ME SO YOU DON'T KILL MY DROPBOX ACCOUNT).
2. Factory reset your Nook Tablet (just do it).
3. Run Windows 7 (32-bit or 64-bit). Sorry Mac and Linux, but that's not my arena.
4. Enable USB debugging and sideloading on your Nook (download an APK and try to install it with package manager. Hit settings and set the options). YOU MUST uncheck "auto mount USB" or debugging won't activate. There are also two checkboxes for debugging and staying awake - make sure both are set. DO NOT REBOOT your Nook once you enable these settings.
5. Plug in your Nook and point Windows to search for the drivers in the usb_drivers directory from the etracted file. The driver has been modified to work with the Nook Tablet and you don't need to mess with any adb.ini stuff. It's ready to go.
6. Once the driver loads, make sure you have a device called "ADB Composite Device" (or something similar) in Device Manager. As long as you don't have an item called "Nook Tablet" with an exclamation point, you're good. Once you are plugged in, check the status bar on your Nook and make sure USB debugging is enabled (there will be a little robot indicator).
7. This step is optional, since it is run at the beginning of the script, but you can open a command prompt AS ADMINISTRATOR and go to the folder where you extracted your files and run "adb devices". It should list your Nook serial number. If it doesn't, start over.
8. Run a command prompt as Administrator and then run the NookTabRoot.bat file to root your tablet and install gapps. Your tablet will automatically restart once the script finishes.
This script is ALPHA and probably won't work, but that's why I need people to test. If anyone finds a way to make it better, please feel free to modify it (as long as you credit me and Indirect).
Good luck!
MIRROR 1 - http://dl.dropbox.com/u/7364988/NT-One-Click-Root-by-anlog.zip
Thanks a lot, this is going to be quite helpful.
anlog, can you please remove the rooting script from yours as it will make it harder for me to provide support if they are in your thread as well. Im happy the gapps is there but I really don't want aanyone to be missed when they need help.
Note: Seriously not trying to be a **** but this is the early stages of rooting and I would HATE for someones system to be completely screwed and I don't know they need help.
P.S.: Just link to the original root thread saying you must have rooted before you proceed with this script.
After that, I'll happily help you work on this script and offer support for this as well.
Indirect said:
anlog, can you please remove the rooting script from yours as it will make it harder for me to provide support if they are in your thread as well. Im happy the gapps is there but I really don't want aanyone to be missed when they need help.
Note: Seriously not trying to be a **** but this is the early stages of rooting and I would HATE for someones system to be completely screwed and I don't know they need help.
P.S.: Just link to the original root thread saying you must have rooted before you proceed with this script.
After that, I'll happily help you work on this script and offer support for this as well.
Click to expand...
Click to collapse
Your root method is not easy enough for the average user, which is why I've posted this.
I'm not removing anything. It's up to the community to decide if they want to try my script or not. I will host it and setup my own mirrors if I have to.
conundrum768 said:
Thanks a lot, this is going to be quite helpful.
[Mirror removed in light of Indirect's post below]
Click to expand...
Click to collapse
Sorry to see you cave in so easily...
I'm not being disrespectful but my script really isn't too complicated. I was working on rewriting the thread anyway I just haven't gotten the time yet until now. I've been out all day.
This early in the process, it is great having multiple ways to achieve root.
Can't you each add a disclaimer in your package "If you use this method to root, don't use any other method without doing a full factory reset first" or whatever words would be appropriate?
Mostly - don't get ticked at each other.
It's not a multiple way, it's verbatim my script with his added to it.
This is not a glory or recognition thing. This is something that I think will greatly help the community of average users with little to no experience with things like ADB or Unix commands.
Many every day users are discovering XDA and it can be very difficult for them to navigate through the forums and find what they are looking for. My goal is to make it really easy.
The script will not blow up your Nook. The worst thing that can happen is that it just doesn't work.
Not sure what else to say, but this "only one user is allowed to help people root" nonsense doesn't work for me, nor the rest of the community. Sorry Indirect. If it helps, I've credited you at the beginning of my script.
OK - then I would say don't include an early version of a root script except by reference... Let the original author handle the bugs and enhancements.
I dont see a problem with useing each others method as long as the appropriate credit is given when you use someone else's work in your own.
Indirect said:
It's not a multiple way, it's verbatim my script with his added to it.
Click to expand...
Click to collapse
You mean your script with a bunch of STANDARD adb commands in it? Not exactly rocket science. Did you write zergrush? No, but you used it (and credited them accordingly).
"Your script" <-- I atleast want people to ask permission before blindly taking my work in the first place. I didn't say this is released under public domain for anyone to use, I would like you to ask before. Use it, whatever but seriously, It kind of upsets me that you didn't bother checking with me if it was alright to atleast use my script. If anyone wants support, come to this thread if you use it. I am not able to help you as I did not develop the addition to this.
Indirect said:
"Your script" <-- I atleast want people to ask permission before blindly taking my work in the first place. I didn't say this is released under public domain for anyone to use, I would like you to ask before. Use it, whatever but seriously, It kind of upsets me that you didn't bother checking with me if it was alright to atleast use my script. If anyone wants support, come to this thread if you use it. I am not able to help you as I did not develop the addition to this.
Click to expand...
Click to collapse
YOUR SCRIPT IS A BUNCH OF STANDARD ADB COMMANDS. That means that 100% of all other ADB scripts out there use elements from the script you pieced together from other scripts.
Get over it. You obivously only care about recognition. My only goal is to help other people.
anlog, you have clearly not seen any of my other work. I'm not in it for recognition, I need to know if something goes wrong at all and if so, what caused it. That's it.
Indirect said:
I'm not in it for recognition
Click to expand...
Click to collapse
Then stop telling people to remove their work and instead write a better/faster/easier version.
Enjoy this script anlog, I appreciate your help finding the driver fix and be sure to reference me in your thread as well for proper credits. Enjoy your evening, I'm no longer debating about this as it's stupid. I think we can both agree on that.
And before you think I'm just being a ****, I wrote a script for the evo shift that was ridiculously advanced for the job JUST to make it so people can't screw it up.
http://forum.xda-developers.com/showthread.php?t=1277793 <-- read about it there.
okay, so not to get in the middle of anything, I will say I've successfully rooted my nook tablet with the original method. didn't have any luck installing the android market (and getting it running).
as such, I've done a factory restore and have downloaded the script here.
as someone who is fairly computer literate, but is VERY new to rooting (short of 1 click root), I will take the shortest path possible. no loss of credit to indirect. please guys, all your work is recognized.
will report back shortly.
Indirect said:
Enjoy this script anlog, I appreciate your help finding the driver fix and be sure to reference me in your thread as well for proper credits. Enjoy your evening, I'm no longer debating about this as it's stupid. I think we can both agree on that.
And before you think I'm just being a ****, I wrote a script for the evo shift that was ridiculously advanced for the job JUST to make it so people can't screw it up.
http://forum.xda-developers.com/showthread.php?t=1277793 <-- read about it there.
Click to expand...
Click to collapse
Dude we need people like you to build off other's work. We both agree that if there is a super easy way to root and get Market, more people will buy the NT. From the second I started this thread you were credited in the first line of my script. I will also credit you in the beginning of this thread. I am NOT about stealing other people's work. Your work here is GREATLY appreciated!
anlog said:
Dude we need people like you to build off other's work. We both agree that if there is a super easy way to root and get Market, more people will buy the NT. From the second I started this thread you were credited in the first line of my script. I will also credit you in the beginning of this thread. I am NOT about stealing other people's work. Your work here is GREATLY appreciated!
Click to expand...
Click to collapse
Sorry for getting annoyed and worked up but I already had to play "Dueling Batch Scripts" in the evo shift section when mine was CLEARLY superior to the other ones by far because I was still developing it. :| So again, my apologies for losing my head but don't wait too long for my REAL script to be thrown together sometime tonight and blow yours out of the water.
I'm trying to root my phone using the Lelus method. As far as I know, I'm following the instructions to the letter. When I get to the actual flashing step, using the ICS T-mobile rom, I get the same "Scheduled Server Maintenance" error that Kevev reported in the guide thread on the development forum. Apparently, he was able to successfully flash, but I don't see any information there as to how he got around the error. I have tried repeatedly and always come up with the same result. Since I can't post yet in a development forum, I have to ask the question here. I must be doing something wrong, but I don't have a clue. I ask your indulgence, and would appreciate any help you can give me.
bearymore said:
I'm trying to root my phone using the Lelus method. As far as I know, I'm following the instructions to the letter. When I get to the actual flashing step, using the ICS T-mobile rom, I get the same "Scheduled Server Maintenance" error that Kevev reported in the guide thread on the development forum. Apparently, he was able to successfully flash, but I don't see any information there as to how he got around the error. I have tried repeatedly and always come up with the same result. Since I can't post yet in a development forum, I have to ask the question here. I must be doing something wrong, but I don't have a clue. I ask your indulgence, and would appreciate any help you can give me.
Click to expand...
Click to collapse
Do you have shttp in C:? C:/shttp/shttp.exe. It must be exatct this way. I have this problem too....
Rixx666 said:
Do you have shttp in C:? C:/shttp/shttp.exe. It must be exatct this way. I have this problem too....
Click to expand...
Click to collapse
I have it nested several directories deep. Did you get it to work when you put it in C? I'll give it a try.
bearymore said:
I have it nested several directories deep. Did you get it to work when you put it in C? I'll give it a try.
Click to expand...
Click to collapse
You get such hiccups if you dont follow the simple instruction first. Many people have habit to extract/save everything on desktop. C drive means C root location of C drive. And you must be logged in as "ADMINISTRATOR USER" on windows 7/8 to avoid access/permission issues.
cmahendra said:
You get such hiccups if you dont follow the simple instruction first. Many people have habit to extract/save everything on desktop. C drive means C root location of C drive. And you must be logged in as "ADMINISTRATOR USER" on windows 7/8 to avoid access/permission issues.
Click to expand...
Click to collapse
I'm used to Linux rather than Windows and when possible I put things in a user's home directory rather than the root directory. Since all that the instructions said was C drive, I interpreted that to mean anywhere on the C drive, not the root directory. Now that I put the program in the root directory, everything worked perfectly.
Thanks for your guide!
I just rooted my p769. I had a few hiccups.
Line 5a says optional, but really it's a necessary step if you've never done it once. If you've edited your HOSTS file and are running shttp, then it's not gonna be able to download/update what it needs to. Close shttp and rem out the lines in HOSTS until it updates, the continue as normal.
shttp has to be extracted in C:\
Mine ran from desktop but the 127.0.0.0:9002 test for the girls picture was file not found, look at shttp dialog window and you see it couldn't find the file because it wasn't where it expected it..
Also did you forget to right click and edit UpTestEX_mod2_marwin.exe compatibility tab if you're running win7/8 like it says to?
Once I set it all up according to the image in the thread and clicked "Normal web upgrade test" it gave me an error box. Saying to setup Tool > B2C Client Setup.
After that it was easy sailing. Well other than the fact that some of the KDZ/bin files were either missing, deleted or dropbox blocked the account for excessive use..
I am using motochopper to root but when I do, instead of the expected "Allow App to do whatever" to your phone message I am receiving the "Detection Information: To protect your device, it is recommended you reboot. <Reboot Now> < Reboot later>" message.
The solution for this appears to either Freeze or remove the System/Apps/ KNOXAgent.apk, KNOXAgent.odex, KNOXStore.apk, KNOXStore.odex files along with data/data/com.sec.knox.seandroid.
1) I don't seem to have a com.sec.knox.seandroid file.
2) all of the Knox files are read only to me.
I have followed what I am seeing to be the proper steps before hand. droidviews.com/2013/how-to-root-verizon-galaxy-s4-sch-i545-and-install-cwm-recovery-on-it/
Any help would be appreciated. Feel free to call me names if this in a dozen other threads (though I have looked!), just please provide a link
kewlguy53403 said:
I am using motochopper to root but when I do, instead of the expected "Allow App to do whatever" to your phone message I am receiving the "Detection Information: To protect your device, it is recommended you reboot. <Reboot Now> < Reboot later>" message.
The solution for this appears to either Freeze or remove the System/Apps/ KNOXAgent.apk, KNOXAgent.odex, KNOXStore.apk, KNOXStore.odex files along with data/data/com.sec.knox.seandroid.
1) I don't seem to have a com.sec.knox.seandroid file.
2) all of the Knox files are read only to me.
I have followed what I am seeing to be the proper steps before hand. droidviews.com/2013/how-to-root-verizon-galaxy-s4-sch-i545-and-install-cwm-recovery-on-it/
Any help would be appreciated. Feel free to call me names if this in a dozen other threads (though I have looked!), just please provide a link
Click to expand...
Click to collapse
Give this one a try.
http://forum.xda-developers.com/showthread.php?t=2290798
DarkMenace said:
Give this one a try.
http://forum.xda-developers.com/showthread.php?t=2290798
Click to expand...
Click to collapse
Turns out my driver may not have been 'nice'. I downloaded it from Samsung but once I installed the Kies and followed the steps it worked! Now to find some ROMS. In the past I used CWM but they haven't updated yet for the S4 (officially) so I tried twrp to back everything up.
Thanks for your help!
Please read forum rules before posting
Questions and help issues go in Q&A and Help sections
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Hello all!
Getting the attached error when attempting to use Android Flash Tool to go back to the latest public on a Pixel 6.
I've used the tool successfully ever since it first came out. This error first reared its ugly head in February and since then I can't get it to work.
Related to the bugginess of platform-tools v34?
I've tried Windows, Mac, Linux, Chromebook using Chrome, Firefox, and Edge. Multiple Google accounts. All the same error.
Can anyone suggest who at Google could fix this? The Google One chat-support folks have been useless, as usual. Or anyone have any ideas for workarounds?
Thanks,
--abhinav
abhinavk said:
Hello all!
Getting the attached error when attempting to use Android Flash Tool to go back to the latest public on a Pixel 6.
I've used the tool successfully ever since it first came out. This error first reared its ugly head in February and since then I can't get it to work.
Related to the bugginess of platform-tools v34?
I've tried Windows, Mac, Linux, Chromebook using Chrome, Firefox, and Edge. Multiple Google accounts. All the same error.
Can anyone suggest who at Google could fix this? The Google One chat-support folks have been useless, as usual. Or anyone have any ideas for workarounds?
Thanks,
--abhinav
Click to expand...
Click to collapse
Hello and good morning, @abhinavk
Prior to your next posting please read the guidances that are stuck on top of every forum like
[Read Before Posting]QUESTIONS DO NOT BELONG IN GENERAL
Hello Everybody, In order to attempt to keep this forum neat and tidy the moderation team is asking you to post your questions into the Questions and Answers (Q&A) forum and not into the General section. You can find the Q&A forum by clicking...
forum.xda-developers.com
and the others. I've moved your thread to Android Q&A.
Thanks for your cooperation!
Regards
Oswald Boelcke
Senior Moderator
Look inside here:
Integrating Google Sign-In into your web app | Authentication | Google for Developers
developers.google.com
xXx yYy said:
Look inside here:
Integrating Google Sign-In into your web app | Authentication | Google for Developers
developers.google.com
Click to expand...
Click to collapse
Thank you. I did see that actually. But since I'm a user and not the developer, I was puzzled as to how I could work around the error. I couldn't find that answer in the help page. What do you think?
Got the same error, entering on the flash tool in incognito mode solved the issue.
Probably some corrupted cookie.
mundano said:
Got the same error, entering on the flash tool in incognito mode salved the issue.
Probably some corrupted cookie.
Click to expand...
Click to collapse
Thank you for that - i tried it on my end in Edge and Chrome but sadly no luck.
You're probably right - I'll keep trying.
Hopefully a workaround comes up soon
But its definitely something with the PC/browser being used.
Yesterday I was reverting from A14 beta to A13, and faced the same issue. Terrier to reboot the PC, searched for solutions online, and nothing worked.
But I tried in incognito mode and the error gone away, but got a new error about lack of space. So I assumed that was something corrupted on the temp files, so I deleted all temp files and cookies and after that it all worked like a charm, without entering incognito mode and without any sort of error.