I hope that this thread can be pinned so that we can all be warned about serious conflicts with app updates and versions and some of the kernels and roms we have flashed. Still hoping this thread will be used for solid advice. Please contribute.
Some of these apps/versions are consistently causing problems, including near-bricks.
My first warning is for Xoomers to avoid updating to the 4.XXX version of Clockwork Recovery. This version doesn't "see" our external sdcard, and backs up to the internal sd, and also, prevents flashing from the external sdcard...if you have already updated through Clockwork Mod Rom Manager, you will need to re-flash a good recovery.
Update 6/21-- This is still a problem--do not update to Version 4.XXX of Clockwork Mod Recovery through ROM Manager. If you did, then in RM, scroll to the bottom and flash an older recovery (2.0.2.5 I think) then the newest one pinned to the top of solarnz's thread in the development section.
There have also been problems with the updated busybox and with the binaries that the updated superuser app installs.
Please, can we get more definitive statuses on these two applications?
Please use this thread and add in your own known problem apps, etc. and if possible suggest or link to solutions for others who may be ensnared in these conflicts.
Okantomi is right. This thread should be pinned. I have seen at least a dozen cries for help on Q&A from people that have fallen into these two traps.
cam30era said:
Okantomi is right. This thread should be pinned. I have seen at least a dozen cries for help on Q&A from people that have fallen into these two traps.
Click to expand...
Click to collapse
Thanks cam30era, you have been one of the people giving the warnings as well.
OK this is a shameless bump to keep the thread visible.
Oh yes, and never flash a .zip file through adb!!!
ROM manager causes so many problems. I don't see the point of it.
kev0153 said:
ROM manager causes so many problems. I don't see the point of it.
Click to expand...
Click to collapse
It's actually a very useful app in so many ways, but there should be more coordination between the developers...it seems the 4.XXX update sort of treats the Xoom like a phone with only a small internal memory and an external sd card being the only thing called sdcard.
On a tablet, however, we have a large internal sdcard (32GB on Xoom) and mounted to that is our external sdcard (this mount point is one of the reasons that Google is hesitant to OK the external SDcard on tablets--makes for an awkward file structure, I guess). This version of CWM seems to only see our internal sdcard on the root directory and treats it as the external sd.
If this explanation is wrong, those with more knowledge please correct me. I think it's helpful for people to know, in layman's terms, what's going wrong, as it can help them use logic to avoid problems in the future, but I don't want to spread mis-information!
What's wrong with the latest "Superuser" and "Busybox", though?
kcrudup said:
What's wrong with the latest "Superuser" and "Busybox", though?
Click to expand...
Click to collapse
I think these are either in conflict with the Tiamat ROM 1.0 /and or newest updates missing files (busybox). This was recorded in an ongoing discussion in development (dinomight OP) and I fell victim to updating to a conflicting busybox version. All was fine until I rebooted and stared the dreaded RSD 3 in the face. God only knows how I made it back from the edge...
okantomi said:
I think these are either in conflict with the Tiamat ROM 1.0 /and or newest updates missing files (busybox). This was recorded in an ongoing discussion in development (dinomight OP) and I fell victim to updating to a conflicting busybox version. All was fine until I rebooted and stared the dreaded RSD 3 in the face. God only knows how I made it back from the edge...
Click to expand...
Click to collapse
I installed busybox from the market too, is it safe to uninstall? I was trying to get cifs to work somehow and I ended up installing busy box. The xoom froze and I got the RSD 3 somehow. I kept smashing button combinations until it rebooted. It has been fine ever since.
Kippui said:
I installed busybox from the market too, is it safe to uninstall? I was trying to get cifs to work somehow and I ended up installing busy box. The xoom froze and I got the RSD 3 somehow. I kept smashing button combinations until it rebooted. It has been fine ever since.
Click to expand...
Click to collapse
Wow! Glad you were able to recover! I think that solarnz made a stable version and I think it's in the development section inhis recovery thread.
kcrudup said:
What's wrong with the latest "Superuser" and "Busybox", though?
Click to expand...
Click to collapse
Long story short :
The busybox wasn't compiled with run-parts. In our rom, the ramdisk used to rely on this for init.d. This has been fixed.
With superuser, the su binary appears to be incompatible. I haven't had a look at this issue yet.
solarnz said:
Long story short :
The busybox wasn't compiled with run-parts. In our rom, the ramdisk used to rely on this for init.d. This has been fixed.
With superuser, the su binary appears to be incompatible. I haven't had a look at this issue yet.
Click to expand...
Click to collapse
Thank you solarnz. So is the busybox in the market safe to install/update or do you have a link to the fixed version?
As long as you have flashed the rom update 3, you can flash busybox without worrying.
Related
Hey all. I have searched but I was unable to find a thread pertaining this issue.
Phone: Android Dev Phone 1
Running: JFv1.50 ADP1.5
What has happened is that today SU/Root seemingly stopped working. I discovered it when I bought Kosh's Screenshot app and started it up. The app requires SU permission, and therefore the "SU Request" window popped up. But it's blank. A blank black screen which eventually will run low on memory and then force close.
I then tried to open the Superuser Permission app, same result. Opened Task Manager for Root Users, same deal. Opened the Terminal Emulator and typed "su", which actually worked! I still had SU privs there. Closed the TE and decided to reboot the phone, and now I don't have SU privs in TE anymore. Everything that's non root related is still working fine.
Does anyone have an idea what's happening here? I suspect that maybe the Market Enabler app or the AdsFree apps could have something to do with it, because they're the only root related apps I have installed the last few weeks, before this problem occurred.
I'm sure a wipe would fix this glitch, but I'd prefer not to do that unless it's necessary. Plus, it would be nice to know what's causing this, so I can avoid it in the future.
Same thing has happened to me. It worked fine for Term Emu, task manager, and ad block. But I tried using an OC app and when super user popped up blank. All my previous apps still work but any new root apps I install do not work. Not sure why though and the only way I found to fix it is to wipe. Do you have your apps on the sd card? I'm using the old method haven't gotten around to trying the new method. Not sure if that is the issue or not, the old version of super user never gave me any issues.
I did a wipe, and it sorted the problem out, for some root apps. Now I'm back to the same crap again though, the SU Request window pops up but it's all black and eventually it force closes.
According JF's blog he included "a much better Superuser app, courtesy of zinx" in the 1.50 release. It's obviously what's causeing our problems, I never had an issue with the old one, but I don't know what to do about it. I don't want to go back to 1.1 or Haykuro's builds. I guess I'm stuck with a semi-crippled JFv1.50 ADP1.5 until someone with more brains than me finds and posts a proper solution.
Yeah Ive been noticing the same thing. Also the superuser list GUI is horrible. I liked how in the last one you can choose what programs you'd want to remove su access from.
andonnguyen said:
Yeah Ive been noticing the same thing. Also the superuser list GUI is horrible. I liked how in the last one you can choose what programs you'd want to remove su access from.
Click to expand...
Click to collapse
Exactly. I'm not sure what he means by "a much better Superuser app", because for a layman like myself it seems a lot worse than the old one
This is just going from bad to worse. Now I discovered I have no positioning via wifi/3G anymore. I have to start the GPS and go outside and wait for a signal to get a lock on my position, which sucks. What the hell is going on? If not even a wipe is enough I guess I'm looking at a complete reinstall, but if all this has happened once it can/will happen again. I would much prefer to find the cause of all this crap.
Ok, so I found the cause for the Assisted GPS issue at least. My Micro SD card needed repairs. I put it in a SD card adapter and plugged it in to my laptop and let Vista repair the file system (apparently there were close to 100 errors on the damn thing) and now it seems to be working again.
Edit: This might actually have fixed my issues with the superuser permissions too. Knock on wood. I'll have to get back to you on this.
I'm having this Exact issue
I am having this exact same issue on dudes build. I have tried everything from scanning to formatting the SD i have flashed back and forth from Jf1.42 to jf1.50 and then to all different dude builds and i have no clue what to do next.
I do a wipe every time i flash and the only way to get any su access is to have jf1.42 or haykuro build. Anyone Else having an issue? I have been working on this for 3 days straight now...
For me it was an SD card issue. If you have a spare card, try that instead, or if you can borrow a card from a friend, just to see if it resolves your problems.
I realize that you have repaired/formatted your SD card, but it could be something wrong with it that screws things up. Worth a try, right?
Absolutely I'm looking for one right now thanks for the quick response. I'll let you know if it works. I have a 2gb sandisk in there now, so i still have my 1gb and my girlfriends 1gb too. Her phone has no su problems at all.
I also ran across the same problem reported here, only a wipe solved it. I believe it had something to do with the Market Enabler (non-signed) app, which was the only one I installed that first showed me the dreadful empty SU screen...
Fixed It
My Problem has been fixed by formatting the sd card with the phone itself.
I copied off all my info, unmounted it from the computer, unmounted it from the phone, this gave the option to format the sd card.
Once that was done i copied all my data back and when i installed programs from my sd i have not had a single su problem since.
I was having all these same problems in JF's 1.5 build, and none of the wiping/formatting SD/trying a different SD card combinations did the trick. Then, I went into JF's blog post where he released 1.5, and someone posted there that enabling USB debugging would fix the issue. I did this, and what do you know, now my superuser permissions app works again in everything, even in unsigned apps! Maybe this is why a wipe fixed it for some people, and not for others?
n17ikh said:
Then, I went into JF's blog post where he released 1.5, and someone posted there that enabling USB debugging would fix the issue. I did this, and what do you know, now my superuser permissions app works again in everything, even in unsigned apps! Maybe this is why a wipe fixed it for some people, and not for others?
Click to expand...
Click to collapse
Not to Jesus resurrect this thread, but I had the same issue and same fix as n17ikh here on the ION build. Enabled USB debugging and su/superuser permissions started working Too bad I have to disable USB debugging in order for my car stereo to mount my G1 as a USB device, but at least I have a solution
Hope this helps anyone else who may stumble upon this.
OK, so I am trying to get GTalk back installed after flashing a new ROM (Cyanogen 4.2.15).
I have searched and there seems to be no direct answer, possibly some inferred ones but noone has been able to answer or point me in the right direction. Hell, I got nicely ignored on Cyanogen's IRC channel. So, unless you are some sort of developer, that' a pretty useless avenue to ask questions it seems.
Here's the scoop:
I reflashed the CM ROM after properly preparing my SD card to make use of Apps2SD option. Gmail works, GMaps works, no GTalk.
Yes I am aware that the Google Apps had to be separated from CMs ROM but that seems only partially true as the other apps are all there.
Since there is a link to the suite of GApps (http://kanged.net/mirror/download.php?file=gapps-ds-ERE36B-signed.zip) does anyone know if one can simply 'apply any zip' and get the GTalk functionality back? I don't care if I have to resign into Google/Gmail again, just want GTalk to work.
Phone Info:
HTC Dream/G1
Firmware 1.6
Radio 2.22.19.26i
CyanogenMod 4.2.15.1
Nandroid
Stock CM theme
8GB Class 4 MicroSD car (partitioned 4GB/4GB....yeah, it's goo big of an app partition, toying with resizing it instead of blowing it all away.)
JadedTech said:
OK, so I am trying to get GTalk back installed after flashing a new ROM (Cyanogen 4.2.15).
I have searched and there seems to be no direct answer, possibly some inferred ones but noone has been able to answer or point me in the right direction. Hell, I got nicely ignored on Cyanogen's IRC channel. So, unless you are some sort of developer, that' a pretty useless avenue to ask questions it seems.
Here's the scoop:
I reflashed the CM ROM after properly preparing my SD card to make use of Apps2SD option. Gmail works, GMaps works, no GTalk.
Yes I am aware that the Google Apps had to be separated from CMs ROM but that seems only partially true as the other apps are all there.
Since there is a link to the suite of GApps (http://kanged.net/mirror/download.php?file=gapps-ds-ERE36B-signed.zip) does anyone know if one can simply 'apply any zip' and get the GTalk functionality back? I don't care if I have to resign into Google/Gmail again, just want GTalk to work.
Phone Info:
HTC Dream/G1
Firmware 1.6
Radio 2.22.19.26i
CyanogenMod 4.2.15.1
Nandroid
Stock CM theme
8GB Class 4 MicroSD car (partitioned 4GB/4GB....yeah, it's goo big of an app partition, toying with resizing it instead of blowing it all away.)
Click to expand...
Click to collapse
you should be able to flash gapps and get it back but you can unzip that and grab gtalk and push it back using adb
supremeteam256 said:
you should be able to flash gapps and get it back but you can unzip that and grab gtalk and push it back using adb
Click to expand...
Click to collapse
When you say 'push' to you mean 'adb push' or 'adb install'. Just wanted to be clear as the install doesn't work.
"Failure [INSTALL_FAILED_OLDER_SDK]"
I get that when I tried to install. My understanding is that there is a mis-match in the adb I am using and the ROM that is on the phone. Is there a way to fix this?
If you are only using CM4 then you need to wipe, defanged base (all of the google apps), then flash CM4.
You shouldn't be flashing gapps. That is for CM5
-------------------------------------
Sent via the XDA Tapatalk App
Oh yeah dont flash gapps. That is for CM5.
-------------------------------------
Sent via the XDA Tapatalk App
And so my learning continues....
So, by copying the zip file to the SD card and choosing 'apply any zip', it seems that everyone is calling that 'flashing'?
Now here's the issue. I already flashed CM 4.2.15.1 and there was no GTalk included.
FYI, for people like me learning, a little more explanation goes a long way. Good thing I'm one of those types who knows how to use Google as opposed to the types who get pissed by people who just use terms and assumes everyone knows them....
So through my wanderings I found this link:
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod
Which led me to here
http://wiki.cyanogenmod.com/index.php/DangerSPL_and_CM_5_for_Dream
Just did a nandroid backup, about to copy stuff from SD card and then upgrade to CM 5/Gapps!
Wsh me luck!
SUCCESS! CM 5.0.7 installed!!
And GTalk works
Thanks all involved with making these things possible!
I have never had an issue, but a few people have commented recently (odd that it's mostly recent) that when they delete a file it seems to re-appear.
IF (and only if), you are having this issue, could you please post the version of Root Explorer you are using and the build you are running (and perhaps how you got your build, ie kies, ota, odin, flash).
I'm hoping this will lead to a common issue (not likely, worth a shot).
The most recent build is 2.12.4. I don't understand why there is a small number of people having issues. I've been trying to contact the developer as well and hope this thread will help him too.
Thanks.
Have you tried root manager?
I'm using Root Explorer - 2.10.2 with JI6. I updated through Odin. I do have root.
^^ nomad, not trying to sound rude:
"I have never had an issue"
"IF (and only if), you are having this issue, could you please post"
Click to expand...
Click to collapse
I had this issue with 2.12.2 and Bionix Fusion & Obsidian.
Sean what did u do to resolve it?
This is sort of ot, but Astro has decided to let me delete system apps which it never did before. I'm running fusion 1.2 stock kernel.
Don't blame me, blame my keyboard's autocorrection algorithm.
flashyp said:
Sean what did u do to resolve it?
Click to expand...
Click to collapse
didn't resolve it really, I wanted to delete some bloatware but I ended up just freezing the apps in Titanium Backup.
I contacted the developer *and got a super fast response*. Please make sure you are on the latest build. Please see his email pasted below.
Hi,
Thanks very much for your support, it’s much appreciated. I actually have a Galaxy S myself with Android 2.1 and have been running Root Explorer on it successfully for some months now. There was an issue a while back in that remounting the system partition didn’t work, but that was fixed in a recent update. Also, I’ve just updated to Froyo and rooted using Z4Root and Root Explorer is still working well. So on a rooted stock Galaxy S I know there are no problems.
So the question is, what is the difference on the phones where there’s a problem? Are there any major differences in the carrier specific versions? And are the problems only happening on custom ROMs? One person recently reported that Root Explorer didn’t recognise root on his Galaxy and I found that he was running a custom ROM and the su file was placed in a non-standard location.
Ok, something has just come to mind. When I first received my phone I was surprised to find that the system partition was mounted as R/W even before rooting. But of course you still don’t have permission to change system files. I’ve just replicated this situation by remounting system as R/W and renaming su to sux. I then closed Root Explorer and restarted it. It started in non-root mode and when I went to system it correctly reported the file system state as r/w but there was no “Mount R/O” button. I tried a delete and then a rename and the app reported these as having worked. But going out and back in showed that the changes didn’t actually work. I’m pretty sure this must be what’s happening for some people. So the question you need to ask them is whether they can see the mount button. If not then their phone isn’t rooted. Do you agree that this is the most likely scenario?
In the meantime I need to make a change to Root Explorer to properly check whether these operations worked and not mislead the user that the change happened.
Thanks for pointing this out. Galaxy S phones are probably the most popular out there at the moment. I think by fixing this issue there will be a lot more happy Root Explorer users!
Best Regards,
Colin
Click to expand...
Click to collapse
Once I pointed out that users were indeed rooted and saw the button, this is the response I received:
Well that blows my theory out of the water
The actual delete is just a simple rm command so there isn’t much that can go wrong. One possibility is a dodgy BusyBox binary. I’ve seen this cause problems for a few people but it’s very rare. If BusyBox is ok then I can only guess that the remount hasn’t worked. One question to ask is whether the remount operation appears to work. If it does nothing and the mount status stays as either r/w or r/o then this may be the problem. If this is the issue then it would be useful to see the output from a mount command. I can then push this through Root Explorer in debug mode and find out what command it’s running to perform the remount.
Click to expand...
Click to collapse
thanks for your help.
I'm running Root Explorer 2.12.2 on Obsidian v2.2 Froyo. I do see the Mount as R/W button, and I'm running BusyBox v1.17.1
I'm going to try re-installing BB, I'll post back if it fixes the issue.
Edit: WTH, it's working now. I had a dodgy BusyBox install.
Edit x2: And it's broken again. Weird.
The developer said there was an issue with old builds, why not update?
s15274n said:
The developer said there was an issue with old builds, why not update?
Click to expand...
Click to collapse
Working on that now. I don't think it's an issue with Root Explorer though because if, upon the permission failure, I simply re-install BB, RE is then able to edit files again. I need to mess around with it more to be sure, but I'll update RE in the meantime.
THIS METHOD IS NO LONGER WORKS as of update version 2.0.5 and higher.
Please visit this thread instead for the current rooting method.
Posting in this thread will get you nowhere, let it RIP.
Proof:
https://www.youtube.com/watch?v=DIaw2RZkguk
Due to the popular demand, and the questions in the last few days. The problem arise from people who were using verygreen version of root. The true is, his version of root works, but what very happens is that he decided to lock down some of the stuff, and thus making further mod become inconvenience for a lot of people. Many people don't know how to fix it. They do not know how to read and interpret the error message and fix it. In a way I think this maybe a better alternative since I believe people who looking to modify their Nook HD/HD+ or root them, what they very after at the minimum is the Google Play store and ability to install any apps they want. While this isn't gonna get you everything, it does most of what people are very after with very little fuss. The main purpose of this thread isn't to have everything working, because we are working around the limitation of what the Nook has, but rather stream line what we already have working and get it there quickly and painlessly from a scratch. So this is mainly to use after the system has been wipe/factory reset.
After I have made this post, I still got someone PM me said it doesn't work. While I'm sure that it does work, I want to be very confident about it. So, I decided to sacrifice my already good setup of my Nook HD+ and FULLY FACTORY RESET it then record this video. Let me make it clear, the file was download from the thread again, and not from my local copy. I'm baffled. I'm just not sure is there is anything easier way it can be done. Seriously just unzip and run 1 command and people still say it doesn't work. The responsibility to read the information is up to you. I don't have the capability to upload those information to your head. Since I already proved that this work, I'll not response to PM regarding this. If you have question or problem, post it on the thread.
Disclaimer:
If something gone wrong, it's all your fault. I take ZERO responsibility for what happen to your device, your life, your wife/husband, your kids, your unborn child and etc. You get the idea.
Breaking News:
It seem the latest update 2.0.5 actually break the root. So, be warned.
Preface:
I didn't discovered the original root on the Nook HD+, verygreen did Nor did I discover the ability to enable install of unknown source. Leapinlar thread has the history on that so I won't go there. But I have created some scripts to help gaining root, modify some critical setting, and adding GAPPS to the Nook HD/HD+, but they are all scattered. Leapinlar has a thread that help gather many of those information together here. Still people are still having trouble. As I stated, I believe what many people are after is just the ability to install any app they want. And this should get very close to their goal. While the end goal is probably something like a custom ROM, something like a CM10 that verygreen is developing; and I believe it will get there. It will probably take a bit more time for the installation process to be easy for people to follow. And there may be something that need to get fix when the very early beta come out. It's like in the Alpha if not pre-Alpha ATM.
While this will get a lot done for you, I still encourage people to go read the original mod threads, there maybe some useful information for you.
1. My original root thread.
2. My original GAPPS thread.
3. I encourage you to read the Nook HD+ Stock Root User Tips from LeapinLar thread, this is like a must read for anyone planning to root their Nook HD/HD+.
Pre-Requisite:
Working ADB that can see Nook HD/HD+ and the Nook HD/HD+ of course(that include enable ADB on the Nook also). If you need help getting drivers and ADB to see Nook, check out LeapinLar thread. ATM, Nook HD/HD+ have 3 firmwares version, 2.0.0, 2.0.2 and 2.0.4. When the get it online it will update automatically. So far all the mods we know of works on all 3. But this doesn't mean it will on future version. Again, LeapinLar thread will have that information as well.
Instruction:
Download these three files. allinone.zip GoogleMaps.apk and gapps-ics-system.zip
Unzip allinone.zip (don't unzip gapps-ics-system.zip)
run allinone.bat
after you got google play store, I suggest you to update it first, the run it at least once before installing Google Map by either copy it to Nook and use your favorite file manager to install or using the command
Code:
adb install GoogleMaps.apk
Post-Install: (or if you don't see the google apps)
The way apps installed via B&N store are different from other apps install via sideloading or any other app stores, and that include GAPPS as well. What this means is that all these apps won't show up on the stock Nook Launcher naturally. But other launcher will see them w/o any problem. That said, I recommend you pick another launcher from the google app store and use that instead. In order to see those extra apps from the Nook Launcher on the Apps screen, hold the volume up button while you press the "Apps" word at the top of the screen for 2-3 seconds. An "Extras" screen will pop up showing all of the sideloaded apps. Another thing is that the superuser app need one extra nudge. It need to be launch at least once manually before it start working. This only need to be done once.
IMO, while I could just point you to one of the launcher or even sideload it during the installation for you. I prefer not to do that. I very think the choice to choose one should be your own. Personal preference aside, I rather not point you to one because I don't know how safe is it to randomly point people to some random apk when it's not even the real purpose of this. I very prefer people get to the google play store on their own and get it from there. If you don't know one then ask around. Many people here have suggested ADW, Apex, Nova, Zeam. If you want to grab apk to sideload, then you can try androiddrawer, it look rather ok.
PRECAUTION:
All these mods you see the Nook HD & HD+ are workaround. They are not the holy grail. So, for example the superuser checker app won't recognize them. That doesn't mean you don't have root, you do but because it's not a traditional root thus they don't see them. A bigger concern is that because this is a workaround. And it's a workaround because we don't have full control of the Nook, any modification to the files or added files /system and its sub-directories (regardless of whether you do so manually or via app) will result in 8 boot loop followed by a full system wipe. Anything stored on the Nook internal storage will be gone. As such, we encourage you not to use such app. We know of at least SuperSU and many ad removal apps will create such event. For more information I strongly encourage you to read those threads I pointed to earlier.
Footnote:
Google Chrome browser is also not included, it's quite big and the latest version doesn't seem compatible(at least that's what I heard). And the voice search is also not working.
ORIGINAL TEXT:
Basically I'm sick of manually reinstalling everything from scratch every time it bootloop mine. Well, I guess mine bootloop more than some ppl here because I explore mine more. So, would you be interested in seeing a simple all-in-one guide? It's already done, I'm just not sure whether to make another thread or not. Meaning I'll leave those guides I made outdated and rotted. Although I just updated the GAPPS installation to be super simple. The All-in-One will basically be the same thing. You just run 1 command and get all three of them. Since I figured people who root their Nook HD/HD+ will end up want to get GAPPS anyway. If people want it, I'll put a new instruction on this thread instead. The Poll will run for 3 days, and then after the poll close, I'll consider that a majority decision. That or if a mod close this thread for duplicate.
someone0 said:
Basically I'm sick of manually reinstalling everything from scratch every time it bootloop mine. Well, I guess mine bootloop more than some ppl here because I explore mine more. So, would you be interested in seeing a simple all-in-one guide? It's already done, I'm just not sure whether to make another thread or not. Meaning I'll leave those guides I made outdated and rotted. Although I just updated the GAPPS installation to be super simple. The All-in-One will basically be the same thing. You just run 1 command and get all three of them. Since I figured people who root their Nook HD/HD+ will end up want to get GAPPS anyway. If people want it, I'll put a new instruction on this thread instead. The Poll will run for 3 days, and then after the poll close, I'll consider that a majority decision. That or if a mod close this thread for duplicate.
Click to expand...
Click to collapse
Ooooo yes please!
I have an HD and i cant get adb on it. I got a new computer too and no other android device has been install but when I try to install the drivers provide, they always have the yellow triangle and the only drivers are the BNTV400 ones. I have looked everywhere and cant get it so I can install google play store.
kvnly2 said:
Ooooo yes please!
I have an HD and i cant get adb on it. I got a new computer too and no other android device has been install but when I try to install the drivers provide, they always have the yellow triangle and the only drivers are the BNTV400 ones. I have looked everywhere and cant get it so I can install google play store.
Click to expand...
Click to collapse
If you are on Windows 7 64bit, check this post.
collect all your tips about root ,manual ota and gapps under one thread and do some editing so that people can follow step by step , and figure where the problems lie.
all in one bat file will help advanced users, but for layman, I am afraid it will cause more confusion
robertchow said:
all in one bat file will help advanced users, but for layman, I am afraid it will cause more confusion
Click to expand...
Click to collapse
Well, if it works consistently enough there will be nothing for the layperson to get confused about. Only if it leads to troubleshooting would it maybe cause problems (because the person would have no idea what steps were taken).
I say if the process can be further automated, even if it's just (hopefully) a stopgap to more thorough root and ROMs down the road, then by Glob do it!
Taosaur said:
I say if the process can be further automated, even if it's just (hopefully) a stopgap to more thorough root and ROMs down the road, then by Glob do it!
Click to expand...
Click to collapse
I'm not sure what further automated this thing could be, you only have to download few files, unzip and run ONE command to get all three things done; root+Manual OTA+GAPPS.
someone0 said:
I'm not sure what further automated this thing could be, you only have to download few files, unzip and run ONE command to get all three things done; root+Manual OTA+GAPPS.
Click to expand...
Click to collapse
Right, I'm saying go for it. Your proposal in this thread would be "further automated" than the current method where only root is automated, is what I meant.
I like the idea
Sent from Droid 4 Running Codename Android
someone0 said:
Basically I'm sick of manually reinstalling everything from scratch every time it bootloop mine. Well, I guess mine bootloop more than some ppl here because I explore mine more. So, would you be interested in seeing a simple all-in-one guide? It's already done, I'm just not sure whether to make another thread or not. Meaning I'll leave those guides I made outdated and rotted. Although I just updated the GAPPS installation to be super simple. The All-in-One will basically be the same thing. You just run 1 command and get all three of them. Since I figured people who root their Nook HD/HD+ will end up want to get GAPPS anyway. If people want it, I'll put a new instruction on this thread instead. The Poll will run for 3 days, and then after the poll close, I'll consider that a majority decision. That or if a mod close this thread for duplicate.
Click to expand...
Click to collapse
Yes please, i like that idea :good:
Yes!
I have ADB & side loading working via Mac OSX, but would love an all in one before taking on this next step as I'm not too good with Terminal commands.
Yes please! I'd love a step-by-step to root the device, manual OTA, and GApps! Although, I do still appreciate the work you have done so far, it's amazing! ;D
Thank you very much.
Sounds like a fantastic idea! Please do! And thx again for all you've done for the nook HD community!
Sent from my BNTV600 using xda premium
I have 2.04 - the installation went well. i've tried and i'm able to get launcher running but cannot get playstore running.
Ok, am I just messing this up big time or what? When I run the .bat it starts, then it says mkdir failed for /data/su, file exists. Then it tries to do every file saying "cannot stat "whatever" : No such file or directory." Over and over again. Major fail. I've rooted multiple android phones and tablets without these kinds of problems. Am I messing up something simple?
Strouperman369 said:
Ok, am I just messing this up big time or what? When I run the .bat it starts, then it says mkdir failed for /data/su, file exists. Then it tries to do every file saying "cannot stat "whatever" : No such file or directory." Over and over again. Major fail. I've rooted multiple android phones and tablets without these kinds of problems. Am I messing up something simple?
Click to expand...
Click to collapse
If you rooted once before it will give you that cannot mkdir error. You might erase and deregister using the B&N settings, then as soon as you reload and register, run the mod. Only once.
Sent from my Nook HD+ Running CM10 on SD
I've done that a few times, but I'll try again.
Thank you very much for this all-in-one. It's genius!
I've just installed it on my Dad's HD+, and it works like a charm. Damn, it's so amazing! One thing though, rookie question, and I guess I'm asking for too much, but would it be possible to redirect the "Apps" icon on the "desktop" to auto redirect to the Android app-drawer; where the Android apps are located - i.e. Play store? Sorry for the bother, and I understand I am asking for too much, so please ignore my message.
Again, thank you very much for your efforts. Works like a charm.
Did a full reset on my HD+. No longer shows the mkdir failed part, everything else still says no such file or directory.
Strouperman369 said:
Did a full reset on my HD+. No longer shows the mkdir failed part, everything else still says no such file or directory.
Click to expand...
Click to collapse
Did you download that gapps-ics-system.zip file and put it in the same folder you are running the allinone bat file from?
Sent from my Nook HD+ Running CM10 on SD
I've tried it in the same area and out, although I'm not sure if both were fresh. I'm trying yet again here in the next few minutes. I will get this. I've only owned one android device that I didn't root, and the was the Samsung Intercept. If you've ever heard of that piece of crap, you'll know why I didn't bother.
---------- Post added at 02:23 AM ---------- Previous post was at 02:02 AM ----------
Finally! I'd already had the gapps in the folder before but I guess the su file had already been created. A full wipe, followed by proper placement of the files finally worked! I would ask if it is sad to feel so good about such a simple achievement, but I don't care. It finally worked! Thanks to someone0 for the all-in-one and leapinlar for the advice.
I'm about to destroy my phone and go back to iPhone 5 because that didn't constantly make me want to destroy everything around me.
I wanted to side-load an app. I just unlocked my bootloader and rooted it and was re-installing my apps.
When I go to install an app it says that there is no more space. the file is 4.85mb and I have 12GB of storage left.
I tried:
-Re-booting
-Installing other apps (which works)
-Clearing the cache
-Downloading Trail from PlayStore (I get the same result)
NEW:
-When plugged in via USB to my PC, device doesn't show up under "Computer" [Running Windows 7 x64)
What I did:
I backed up my phone and wiped the whole thing because I was running out of time last night
Thankfully Foxnov1990 and ImbaWind's tips worked. I restored the original backup and it solved my problem. Thanks so much! Love ya guys! :victory:
AFAIK my friend and I don't have this problem with our N4 and my friends don't have this problem with their GNEX.
Btw this is a N4 forum.
ImbaWind said:
AFAIK my friend and I don't have this problem with our N4 and my friends don't have this problem with their GNEX.
Btw this is a N4 forum.
Click to expand...
Click to collapse
I'm talking about the N4... DERP
If you aren't here to answer then don't post... please leave.
Chubby_Skunk said:
I'm talking about the N4... DERP
If you aren't here to answer then don't post... please leave.
Click to expand...
Click to collapse
it's your problem you don't know how to solve, not google's.
if you're here just to unleash this anger then YOU leave.
the guy is right about what he said in the first line.
android wasn't made to piss you off, it was made to stay stock, but you rooted it.
solution? easy: 1) install a stock-like ROM or 2) unroot...
Lol you'll get a lot of constructive answers with your style of posting What have to tried so far to fix the problem? Could we get a screenshot of your storage page?
Chubby_Skunk said:
anyone have a simple answer? rather than sending me to another page where I have to read a 10,000 word essay on how to fix it...
Click to expand...
Click to collapse
That's kinda how it works here - if someone else has fixed it you read their solution! Quite a simple concept really...
However, I've never had that with my old GNex or my current N4 so I can't help you personally
desarenezitic said:
Lol you'll get a lot of constructive answers with your style of posting What have to tried so far to fix the problem? Could we get a screenshot of your storage page?
Click to expand...
Click to collapse
I tried:
-Re-booting
-Installing other apps (which works)
-Clearing the cache
People tend to complain about the OP rather than sticking to the topic at hand.. here's the pic:
Riro Zizo said:
it's your problem you don't know how to solve, not google's.
if you're here just to unleash this anger then YOU leave.
the guy is right about what he said in the first line.
android wasn't made to piss you off, it was made to stay stock, but you rooted it.
solution? easy: 1) install a stock-like ROM or 2) unroot...
Click to expand...
Click to collapse
If you are going to direct that back at me, please send me a PM instead of posting your complaints in the forum. Then we can argue all you want.
Maybe it's the app you're trying to install? Side loading indicates its not quite kosher?
Sent from my Nexus 4 using xda app-developers app
chrisrozon said:
Maybe it's the app you're trying to install? Side loading indicates its not quite kosher?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Not even. I tried to download the Trail from the PlayStore and that says the same thing too... It's like the app is just being a d**k to me lol
I think actually the answer begins on 10,001th word !
And actually I think I know how to fix this problem !
Chubby_Skunk said:
Not even. I tried to download the Trail from the PlayStore and that says the same thing too... It's like the app is just being a d**k to me lol
Click to expand...
Click to collapse
I get the attitute, but you might wanna at least try to be friendlier as we're just here to help.
But On-Topic: have you tried this?
File explorer (app)
Go to /data/app (in System (root))
Del this line
com.maxmpz.audioplayer-1.odex
I've had it before that on stock ROM (aka unlocked bootloader and rooted) which means that it's not DEodexed that some Odex files were left behind. Which means that whatever you try, as long as that file is there, you won't be able to install the app. (shouldn't happen but it's possible in rare occasions)
Hope it helped.
If it didn't help and the Odex file is not there, see if you have Lucky Patcher installed, deinstall it (it sometimes holds on to odex files), and try installing PowerAmp now. Then reinstall Lucky Patcher
Foxnov1990 said:
I get the attitute, but you might wanna at least try to be friendlier as we're just here to help.
But On-Topic: have you tried this?
File explorer (app)
Go to /data/app (in System (root))
Del this line
com.maxmpz.audioplayer-1.odex
I've had it before that on stock ROM (aka unlocked bootloader and rooted) which means that it's not DEodexed that some Odex files were left behind. Which means that whatever you try, as long as that file is there, you won't be able to install the app. (shouldn't happen but it's possible in rare occasions)
Hope it helped.
If it didn't help and the Odex file is not there, see if you have Lucky Patcher installed, deinstall it (it sometimes holds on to odex files), and try installing PowerAmp now. Then reinstall Lucky Patcher
Click to expand...
Click to collapse
Normally just delete the odex file it will works
this problem always occur after uninstalling the app and when you want to install it back, **** thing happens
ImbaWind said:
Normally just delete the odex file it will works
this problem always occur after uninstalling the app and when you want to install it back, **** thing happens
Click to expand...
Click to collapse
Honestly, I have installed and deinstalled the app more than you can possibly imagine... and I've nearly never had issues with reinstalling.
And when I did get issues it was Lucky Patching (having patched the app) that was holding on to the odex and I couldn't delete it till Lucky patcher was deinstalled.
So not sure what **** you mean but there was always an easy solution for me
Foxnov1990 said:
Honestly, I have installed and deinstalled the app more than you can possibly imagine... and I've nearly never had issues with reinstalling.
And when I did get issues it was Lucky Patching (having patched the app) that was holding on to the odex and I couldn't delete it till Lucky patcher was deinstalled.
So not sure what **** you mean but there was always an easy solution for me
Click to expand...
Click to collapse
Oh yep, always happen when I use lucky patcher to removed the app's ads !
I've run into a similar issue before.
I've had similar issues when I've removed an .apk using adb or root explorer without removing its associated .odex file.
Use root explorer and try to find an .odex file that has the same name as the package that you are having trouble installing.
There are some cache cleaning utilities in the Play store that might assist you as well.
https://play.google.com/store/apps/details?id=com.SystemCleanup.Inteks.org&hl=en
Good luck. Also, try to approach asking for help in a more mature manner in the future. You are not entitled to hack a device then complain when something unexpected happens.
-Mike
bunch of winers in here...girls keep your problems to yourself
Sent from my Nexus 4 using xda app-developers app
have you tried to flash userdata.img via msdos?
sometimes my N4 needs to erase everything cause i erase everything and im still seeing rubbish in the memory trough windows explorer!
follow this tutorial!
http://forum.xda-developers.com/showthread.php?t=2010312
Foxnov1990 said:
I get the attitute, but you might wanna at least try to be friendlier as we're just here to help.
But On-Topic: have you tried this?
File explorer (app)
Go to /data/app (in System (root))
Del this line
com.maxmpz.audioplayer-1.odex
I've had it before that on stock ROM (aka unlocked bootloader and rooted) which means that it's not DEodexed that some Odex files were left behind. Which means that whatever you try, as long as that file is there, you won't be able to install the app. (shouldn't happen but it's possible in rare occasions)
Hope it helped.
If it didn't help and the Odex file is not there, see if you have Lucky Patcher installed, deinstall it (it sometimes holds on to odex files), and try installing PowerAmp now. Then reinstall Lucky Patcher
Click to expand...
Click to collapse
Thanks for the tip! I'm going to save this for future reference. I fixed the problem though. ^^^ in OP
ImbaWind said:
Normally just delete the odex file it will works
this problem always occur after uninstalling the app and when you want to install it back, **** thing happens
Click to expand...
Click to collapse
Thanks for the help as well sir. I'm going to save this for future reference if it happens again... I fixed the problem though. ^^^ in OP