Related
I remember all the work to get the original temp root to be 'sticky' way back when. I am having trouble finding out exactly what was going on that required extra work to get it to be truly sticky. We are trying to get at least sticky temp root on the HTC Vivid for att. Zerg works to get us temp root, but after a little bit the su binary is lost/overwritten/vanishes. IS this what happened to the 3d and sensation? If so, can you tell me how you fixed it?
Yes, PM agrabren ask him what he did. He was a big dev in that project
Sent from my Warm HTC EVO 3D using Tapatalk... Get in the 3rd dimension!
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums
Moving to Q&A
Androidious said:
Yes, PM agrabren ask him what he did. He was a big dev in that project
Sent from my Warm HTC EVO 3D using Tapatalk... Get in the 3rd dimension!
Click to expand...
Click to collapse
I have. No reply. Prob busy.
Sorry bout the post location.
Sent from my HTC PH39100 using xda premium
On the Evo3D HTC left something in the ramdisk that would allow for everything under /vendor/ to be retained, so su was placed under /vender/bin/su and then symlinked to /system/xbin/su and /system/bin/su. Not all root apps were able to find it but for the most part it worked pretty well
gtkansan said:
I remember all the work to get the original temp root to be 'sticky' way back when. I am having trouble finding out exactly what was going on that required extra work to get it to be truly sticky. We are trying to get at least sticky temp root on the HTC Vivid for att. Zerg works to get us temp root, but after a little bit the su binary is lost/overwritten/vanishes. IS this what happened to the 3d and sensation? If so, can you tell me how you fixed it?
Click to expand...
Click to collapse
xHausx said:
On the Evo3D HTC left something in the ramdisk that would allow for everything under /vendor/ to be retained, so su was placed under /vender/bin/su and then symlinked to /system/xbin/su and /system/bin/su. Not all root apps were able to find it but for the most part it worked pretty well
Click to expand...
Click to collapse
Keep in mind, all this is regarding a temporary root. Permanent root should be stored in /system/bin/su or /system/xbin/su .. but if we can't get permanent root, having a *sticky* temporary root is the next best thing and we're a bit more flexible with the standards.
The main two variables in this situation are going to be, memory write protection on which partitions, plus having a good location to store the su binary.
xHausx is correct regarding the EVO 3D. Without looking or being familar with this specific method, I know from the Samsung Moment and Epic, we generally stored the su binary outside of system. Best location seems to be in a tmpfs/ramfs partition as the system doesn't seem hard coded to explore/change/modify tmpfs/ramfs partitions. Unfortunately, a tmpfs/ramfs partition is lost on each boot, but as is the nature of a temporary root, i.e. running the exploit on each boot to gain root access.
If you had any links to threads regarding the root process for this device, would be interesting to follow! Hope that helps!
joeykrim said:
Keep in mind, all this is regarding a temporary root. Permanent root should be stored in /system/bin/su or /system/xbin/su .. but if we can't get permanent root, having a *sticky* temporary root is the next best thing and we're a bit more flexible with the standards.
The main two variables in this situation are going to be, memory write protection on which partitions, plus having a good location to store the su binary.
xHausx is correct regarding the EVO 3D. Without looking or being familar with this specific method, I know from the Samsung Moment and Epic, we generally stored the su binary outside of system. Best location seems to be in a tmpfs/ramfs partition as the system doesn't seem hard coded to explore/change/modify tmpfs/ramfs partitions. Unfortunately, a tmpfs/ramfs partition is lost on each boot, but as is the nature of a temporary root, i.e. running the exploit on each boot to gain root access.
If you had any links to threads regarding the root process for this device, would be interesting to follow! Hope that helps!
Click to expand...
Click to collapse
All apreciated. They did use a similar method, http://forum.xda-developers.com/showthread.php?t=1345620
[TOOL] Perma-Temp-Root Solution [Mac/Linux/Windows] to get stick temp root. Now we need a bootloader exploit to get around the damn nand lock. Erg. I know EVERYONE over there would love any help or previous wisdom we could get. We've been trying to reach devs like unrevoked, unity, agraben, attn etc. But no one seems on board. I would think with the huge board level similarities between the raider/vivid and all the sensations that someone would have some experience to lend an idea or three ... Any help would be REALLY Apreciated! Thanks everyone.
Sent from my HTC PH39100 using xda premium
gtkansan said:
Now we need a bootloader exploit to get around the damn nand lock. Erg. I know EVERYONE over there would love any help or previous wisdom we could get. We've been trying to reach devs like unrevoked, unity, agraben, attn etc. But no one seems on board.
Click to expand...
Click to collapse
android exploits take a lot of work to find/test/develop/release. bootloader exploits are generally more time/labor intensive to find/test/develop/release as bootloader code is closed source compared with android code that is open sourced. in addition, bootloaders can be very specific to only a few devices, where as android is running on many devices.
bootloaders have to be reversed engineered which is a skill set not many people have.
after all that negative news, perhaps somebody with the skill set will take the time to examine this device. perhaps a previous method will work or hasn't been patched!
after reading the thread linked above, seems everybody is on the right track. hope the extra information helps. good luck!
No, I do not have a nook tablet so I can not offer any methods to bypass myself. This is just a thread where developers can talk about gaining the ability to flash roms and recoveries.
Developers, please use this thread to collaborate so we can have everyone working in the same space.
Users, please try to not post and if you do, don't make it a completely useless post like something that just says thanks and whatnot. Just use the button for that. The less clutter = more progress
edit: Someone is donating a nook tablet to me to try and bypass the bootloader! Here's hoping it doesn't get bricked.
I've got a Nook Tablet and would be more than happy to help with this. I'm available most evenings after 9PM EDT.
I've been reading alot about kexec and 2nd init. It looks like 2nd init is the way to go, due to the fact that it's already been used multiple times.
Ideally what I'd like to do is try to reverse engineer a current 2nd init to work for the nook.
The potential issue I see is, the kernel may not be new enough to run CM7.
Am I completely off base here?
chantman said:
I've got a Nook Tablet and would be more than happy to help with this. I'm available most evenings after 9PM EDT.
I've been reading alot about kexec and 2nd init. It looks like 2nd init is the way to go, due to the fact that it's already been used multiple times.
Ideally what I'd like to do is try to reverse engineer a current 2nd init to work for the nook.
The potential issue I see is, the kernel may not be new enough to run CM7.
Am I completely off base here?
Click to expand...
Click to collapse
Kernel is good enough to run CM7 (Gingerbread), but not sufficient for CM9 (ICS). Also it is not good enough for CM8 either (although the chance we see CM8 for any device is doubtful).
We need to find a way to keep a chat between developers. Add me on g+ and ill create a huddle for every dev
Sent by breaking the sound barrier
chantman said:
I've got a Nook Tablet and would be more than happy to help with this. I'm available most evenings after 9PM EDT.
I've been reading alot about kexec and 2nd init. It looks like 2nd init is the way to go, due to the fact that it's already been used multiple times.
Ideally what I'd like to do is try to reverse engineer a current 2nd init to work for the nook.
The potential issue I see is, the kernel may not be new enough to run CM7.
Am I completely off base here?
Click to expand...
Click to collapse
your pretty spot on, but i dont see cm7 being a problem, i see cm9 being a problem. with a 2nd init rom you have to build the OS around the kernel(which it is much harder than doing it the right way) and if the kernel isnt high enough or if drivers are outdated(like the nook color graphic drivers) than you can count that OS out of your list. cm7 since it is gingerbread and since gingerbread can be booted on a froyo kernel(moto droid proved that along with the droid x/2), i think it can be booted using 2nd init, ICS on the other hand needs a ICS kernel to boot and if your not using an ICS kernel than you need a custom kernel that can get ics booting properly
now i disagree with you about 2nd init being the best way to build a rom for the nook tablet, i believe kexec is the best way to go about building a rom for the nook tablet because it will allow for a custom kernel to be booted off the original kernel. from what i have read about kexec on android is that they cant get the 3g chip to get started again(but nook tablet doesnt have a 3g chip so who cares), but wifi and all the other key functions can get started up and running, so using kexec on a nook tablet seems the best logical solution to getting around the locked bootloader(but dont quote me on this cause i havent developed anything for the nook tablet yet, nor do i even own one).
---------- Post added at 11:19 PM ---------- Previous post was at 11:18 PM ----------
Indirect said:
We need to find a way to keep a chat between developers. Add me on g+ and ill create a huddle for every dev
Sent by breaking the sound barrier
Click to expand...
Click to collapse
devs use irc to chat, its easier than any forum or chat program out there
Thats true but i cant always be on irc to keep up on info.
Sent by breaking the sound barrier
Also, ill look into getting kexec once i get my nook tab
Sent by breaking the sound barrier
Indirect said:
Thats true but i cant always be on irc to keep up on info.
Sent by breaking the sound barrier
Click to expand...
Click to collapse
There are most likely complete logs available somewhere to review, or someone could make them available for you. I don't have the link on this pc, but there is a site that keeps up-to-date logs #nookcolor available
Indirect said:
Also, ill look into getting kexec once i get my nook tab
Sent by breaking the sound barrier
Click to expand...
Click to collapse
I wouldn't spend too much time on this. Assuming that android_4430BN_defconfig from B&N's kernel sources is the defconfig used to compile the running kernel, kexec will not work as it has been disabled.
it doesn't really matter if kexec has been disabled in the kernel config. we can't really hope that they would leave a gaping hole that fricking big. honestly i'm kind of annoyed at the "omg they didn't configure their kernel specifically for us to hack the crap out of the device" posts. Seriously, even if they did this, as far as i've seen we have yet to disable OTA updates, so 3 seconds of a B&N developer time would wipe out any work depending on kexec being built into the kernel.
we can after all create modules neh? my linux kernel hacking experience is very close to non-existent, but i'll be starting by getting a module to load, followed by getting the kexec tools and a kexec module loading.
so far i'm having trouble finding any literature on kexec on ARM. it all says it's x86 only, but clearly everyone from motorola to sony communities are making use of kexec on arm. anyone know of any good points to find information on kexec for arm?
I've also seen something call splboot mentioned a few times, but am having trouble googling anything useful up. anyone familiar with that tech?
I suggest posting in the motorola dev section seeing if any of them would be interested in getting kexec up and running on the nook tab or could point us where to get information on it running with an ARM architecture device.
Indirect said:
I suggest posting in the motorola dev section seeing if any of them would be interested in getting kexec up and running on the nook tab or could point us where to get information on it running with an ARM architecture device.
Click to expand...
Click to collapse
Try Kabaldan. http://forum.xda-developers.com/member.php?u=2218140
He was a great developer when I owned a Motorola Milestone. Assuming he used 2ndInit to port CM6 and CM7
http://lists.infradead.org/pipermail/kexec/2008-February/001272.html<-- kexec on an ARM processor.
I just tried something to see where it would get me and if I could learn something new.
Using ROM Manager, I have been trying to flash different recoveries to see what results I would get or what I could break (or brick). After some research I found a device also running the OMAP 4430 processor and selected it (LG Optimus 3D). When I selected reboot into recovery, I did get some new screens I have not seen before. It made me reboot again, then another screen flashed very fast and it then rebooted and was normal from there. I think it may have replaced the recovery I flashed as it was flashing something but was very fast. I will try it again and see if I can determine what is happening. But I got it's attention and probably flashed the right thing in the wrong place, or the wrong thing in the right place.
I found a guide on a site for flashing a recovery to a device using flash_image binary, and two files were mentioned and deleted which allowed hijacking of the recovery process. Out NT has those two files as well:
/system/recovery-from-boot.p (encrypted, cannot view)
/system/etc/install-recovery.sh (can view code, and points to first file)
I wonder what the possibility is to hijack the install-recovery.sh file ? Or is there yet another file in the process? Very interesting though.
Ive actually been thinking of hijacking the install recovery script
Sent by breaking the sound barrier
To ellaborate further on my previous post, I believe this is the key to how we can get a bootloader bypass for a custom recovery as they have done for the Motorola Bionic and other Motorola phones. When a reboot occurs, the bootloader looks for a certain file in a certain place, if it exists then it reboots into recovery. If not, it boots like normal. The bootstraps for the Motorola devices mimic the logwrapper binary that the bootloader looks to and allows it to go into a custom recovery instead. A very simplified explanation.
What their bootstrap does is place the recovery indicator file in the proper place (somewhere in /data) and when the bootloader finds it, it goes to the logwrapper binary, which of course has been replaced with their hijacked version.
It appears the install-recovery.sh on our NT is looking for a "recovery" indicator, and if it exists, it is telling it to go to recovery-from-boot.p
If so, this is the very process we need to hijack to allow some type of custom recovery. It doesn't get us completely around the bootloader, but it would allow a recovery mode for flashing custom ROMs, just as the Motorola guys have done. I am probably way over simplifying this, but i have researched this quite a bit the past few days and it looks like for the short term, this is the path we need to look at.
If anyone has contact with Kousch or someone familiar with the bootstrap process, I think we could be in business to get something workable here.
Here is a link to one of the Motorola bootstraps, and the contents of the /system/etc/install-recovery.sh
http://www.koushikdutta.com/2010/08/droid-x-recovery.html
#!/system/bin/sh
if ! applypatch -c IMG:/dev/block/platform/mmci-omap-hs.1/by-name/recovery:2048:70ef89e0497435e988819690aaabb35da6b7677f; then
log -t recovery "Installing new recovery image"
applypatch IMG:/dev/block/platform/mmci-omap-hs.1/by-name/boot:2850816:114706e7bbfa4c806323215a83d6ad4e9cd392f7 IMG:/dev/block/platform/mmci-omap-hs.1/by-name/recovery 532ad547febe82850924a52625132376514e3a8b 3203072 114706e7bbfa4c806323215a83d6ad4e9cd392f7:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi
Or all of this could be in place and not ever used !
---------- Post added at 02:22 PM ---------- Previous post was at 02:18 PM ----------
Indirect said:
Ive actually been thinking of hijacking the install recovery script
Sent by breaking the sound barrier
Click to expand...
Click to collapse
The Motorola bootstraps are just one .apk file ! We could probably modify the process to fit ours. But these are paid for apps on the market so we would need permission, or even better help from the developer. For testing to see if it even works I don't think it would matter, if it doesn't work or is not the fix then we move on to something else. But if it works, I don't think we can just post the fix without the developer's permission on how he wants to handle it.
Let me see what I can find out
Alright that will be great. Thanks romified.
Sent by breaking the sound barrier
FYI, I know there is a free version of the Droid 2 bootstrapper floating around somewhere (I think the developer made it available on xda). I'll see if I can find the link.
ylexot said:
FYI, I know there is a free version of the Droid 2 bootstrapper floating around somewhere (I think the developer made it available on xda). I'll see if I can find the link.
Click to expand...
Click to collapse
Yes, I have the APK and have it decompiled...just not with me. I will dig into this afternoon and see what I can determine. If I can reach Kousch (the developer) he may be interested in helping do this and making it available since the NT is fairly popular. Then we could have help with a recovery as well.
Thanks for your help though ! If you find the link that is fine, it may help others who can look into this as well.
Found the link, but I guess it's not from Kousch:
http://www.mediafire.com/?fxvlw4wl2jade0o
It's in one of the Droid X stickies over at AndroidForums.
Hi all,
First off, just want to say thanks to all of the hardworking devs out there that put a lot of time and effort into these projects. You guys are really awesome!
Secondly, I tried to post this as a reply in the developer's forum, but didn't have enough posts to qualify.
That all being said, I followed all of the instructions in Indirect's post here, but can't get the Nook Tablet to bring up recovery mode when I reboot. It just continues to load the standard B&N image. I even tried a factory reset to see if that would work, but same problem. I verified that the files on the micro-SD card match those as shown in Albert's excellent video here. The device is still running 1.4.0.
Any assistance is greatly appreciated!
No luck here either...I tried the root while watching Albert's You Tube video at the same time. I think the significant thing is that my screen displays something like:
Extracting files to SYSTEM...
Setting SYSTEM:bin/su permissions to 06755...
Creating SYSTEM:xbin/su symbolic link...
Installation Complete!
Install from sdcard complete.
Whereas the screen in the video shows:
Extracting files to SYSTEM...
Setting SYSTEM:bin/su permissions to 06755...
Creating SYSTEM:xbin/su symbolic link...
Installing GApps 29110878
For Android 2.3.5 Customized for the nook tablet
Mounting data...
Extracting files to data...
Unmounting data...
Install complete. Enjoy!
Installation Complete!
So clearly my install seems to silently abort somewhere in the middle...
Any insight or advice would be appreciated!
Removed...
~ Veronica
Sent from XDA premium using my Nook Tablet
Beatbox,
Just re-reading your post I think I got farther than you, but also got stuck on your issue earlier. If you keep the Nook plugged into the PC via the USB cable during the power on, the Nook will boot into the recovery mode - that at least was what got me past your issue.
It's not about Rooting OR recovery. It's about the fact that this method is still being worked on. Indirect has been making modifications to the various files and it is my opinion that the file used in Albert's video is NOT the same file that would be downloaded if you went and obtained it right now.
I would wait this out until Indirect writes an updated post explaining that the method is finalized.
If this is not an option the original root method works perfectly.
Land - when you say "original root method" are you talking about something that predates Albert's solution?
jearley9 said:
Land - when you say "original root method" are you talking about something that predates Albert's solution?
Click to expand...
Click to collapse
See this Thread
If you are running 1.4.1 you will need to downgrade first.
See Here
jearley9 said:
Beatbox,
Just re-reading your post I think I got farther than you, but also got stuck on your issue earlier. If you keep the Nook plugged into the PC via the USB cable during the power on, the Nook will boot into the recovery mode - that at least was what got me past your issue.
Click to expand...
Click to collapse
Cool jearley9, this did indeed work for me and I was able to load the image. Problem now is that I always end up at the normal B&N Setup screen. Were you able to get past that part?
And thanks to all the other thread participants. I know it takes time to work these things out, so no biggie. We all get a little too excited and impatient with things like these sometimes.
Thanks - looking it over now...
---------- Post added at 02:58 PM ---------- Previous post was at 02:53 PM ----------
Beat,
Does your screen match my screen or the one in Albert's video? If it matches then you and I have the same problem. If not then you have something different going on...
jearley9 said:
Thanks - looking it over now...
---------- Post added at 02:58 PM ---------- Previous post was at 02:53 PM ----------
Beat,
Does your screen match my screen or the one in Albert's video? If it matches then you and I have the same problem. If not then you have something different going on...
Click to expand...
Click to collapse
Definitely matches yours. Just didn't know if you got further than I did after rebooting.
Land Master said:
See this Thread
If you are running 1.4.1 you will need to downgrade first.
See Here
Click to expand...
Click to collapse
Just wanted to provide an update. I attempted the instructions from the original rooting thread (my nook tablet doesn't have 1.4.1 yet, so didn't need to downgrade). When I ran the batch file to root, it detected that the device was already rooted - which I quote from the script, "Is bothersome."
Okay, so i think my device is half-rooted somehow. Just can't get the new home screen that I'm seeing on all the videos. I'll keep you guys updated with my further troubleshooting attempts.
Beat, you and I are at least synchronized - I too tried the original root method, and I had the same exact problem as you describe... a message saying "already rooted". I did a system reset right before I tried the root, so I don't see how it could be "already rooted".
I just purchased my Nook yesterday. I am wondering if there are newer units (mine included) that are more resistant to being rooted?
I'm having the same issue, but I can use the search function to determine that apps WERE installed (and will execute properly). I believe that Indirect has removed ADW launcher and Homecatcher from the zip we're suppossed to drop onto the SD Card. My guess is that we're waiting for him to come up with a solution to the "Market not showing up in launcher" issue.
Can someone confirm this?
Well any other tactics I've tried have been to no avail, so I'll just be patient and wait for Indirect to address it. I'm sure he has enough on his plate without us bugging him.
Many thanks to him again for even working on something like this.
Edit:
Okay, for some reason I missed Albert Wertz's helpful Youtube comment:
Please Vote this comment up so everyone else can read it among all the others. Indirect is making some changes to the script, if you dont get adw to launch right after the first reboot from root, you may have to download it manually from the market. You can use the N button menu search function to pull up market by typing M in the search. You can launcher it from here. Until the bugs are worked out, you may only be able to install from market, sideloading may still be an issue. Indirect is fixin
Click to expand...
Click to collapse
I did this and have no problem bringing up the Android Market now. Just installed an app successfully. Not sure where it lives though. I could only seem to launch it from the Recently Downloaded icon at the bottom bar.
Edit 2:
Okay, just restarted after installing the ADW and now it prompted me to start with it. Only issue I have now is if I hit the N button, it reverts back to the original Barnes & Noble homescreen and I have to reboot to launch ADW again.
I got pretty much to the same place - I downloaded HomeCatcher but that seems to be non-functional - Looks like the Nook home screen is winning this round...
jearley9 said:
Beat, you and I are at least synchronized - I too tried the original root method, and I had the same exact problem as you describe... a message saying "already rooted". I did a system reset right before I tried the root, so I don't see how it could be "already rooted".
I just purchased my Nook yesterday. I am wondering if there are newer units (mine included) that are more resistant to being rooted?
Click to expand...
Click to collapse
To truly "reset" the system run the downgrade I linked previously EVEN IF you are on 1.4.0. After that it will be just like you took the NT out of the box. Then run the Indirect Root Batch and the "you are already rooted" should be gone. I would hope so anyway
Land,
I did the press and hold 9 times and got back to factory state.
Also, I tried Brianf21's files and I got the same problem as you. If I try to open Update.Zip from Windows it gives me "Please insert last disk of a multi-volume set...". I would guess that the zip file is malformed or incomplete, but that's just a guess...
-jearley
jearley9 said:
Land,
I did the press and hold 9 times and got back to factory state.
Also, I tried Brianf21's files and I got the same problem as you. If I try to open Update.Zip from Windows it gives me "Please insert last disk of a multi-volume set...". I would guess that the zip file is malformed or incomplete, but that's just a guess...
-jearley
Click to expand...
Click to collapse
I copied this post to the Development Thread in my recent reply to Brianf21. It is conceivable at this point that you and I are the only ones that have tried this. lol
Please put information regarding future attempts in that thread to help him troubleshoot.
Glad to see that you were able to reset. I don't believe it will be necessary again if Brian fixes the issue. To my knowledge simply entering CWM using his image had NO affect on my NT.
Land,
Sorry I can't comply with your request - the forum software won't let me post in the development area due to my "newness" - I am 53 years old and have 30 years of software/firmware development experience, but to this forum I am a "newbie"
jearley
jearley9 said:
Land,
Sorry I can't comply with your request - the forum software won't let me post in the development area due to my "newness" - I am 53 years old and have 30 years of software/firmware development experience, but to this forum I am a "newbie"
jearley
Click to expand...
Click to collapse
Alrighty then.... I don't know if I should laugh or cry. You can't even "post" in the Dev section? I wonder how many posts you need. Seems a little extreme to me but you will get there soon enough I guess.
In the meantime I'll make sure that your comments are known. Thanks!
anybody knows how to make a ROM customized and make a "update.img" to run on a un-rootable device? I know when you backup a linux image for example ubuntu, this image will run on all other PCs, the image will automatically knows the new PC's drivers and adapt everything with that, is it what happening to an android too ?
It's not clear what exactly you mean by "un-rootable" device, but one cause an Android device cannot be rooted is that it requires signed updates. This signing happens using a special private key, which only device manufacturer knows. So, answering your question, if a device is truly un-rootable, it's likely impossible to make install custom update.img (because otherwise you could just include superuser binary in that custom image, and it wouldn't be unrootable in first place ;-) ).
---------- Post added at 03:20 PM ---------- Previous post was at 03:12 PM ----------
Answering second question, no, it's not the same for Android. Most Android device use ARM processor, and in ARM world you usually need to know addresses and other characteristics of every peripheral device (RAM, display, camera, etc.) to make it work, and those are different for different devices. So, full system image made for one device most likely won't work for another device (unless they're very similar).
But there're also those "partial updates", which doesn't have complete system image, but only some components, e.g. a theme or some application. Such partial updated might be possible to install on different devices. (But if such update comes from a vendor, it is usually locked for a particular device anyway).
let me make it clear, I have a MSI tablet, I tried all rooting ways like z4, Gingerbreak v1.20 and superoneclick nothing's working for it (so it's un-rootable at least because of I couldn't find any way for that!) .
I found an official "update.img" from msi website, i upgraded the ROM to the new version, it was when i found we can make root access by editing of the "update.img".
Well, "a MSI tablet" still doesn't sound too specific ;-). I guess, you might have more specific responses if you'd write the exact model name you have (did you also try to search forum for it?).
As an example, I can tell about Nook Tablet - its boot loader is exactly locked, requiring signed updates. But folks here at XDA devels still found a hole in it and described how to get root on it and how to install custom updates for it (and are working on CyanogenMod for it). I personally bought Nook because I knew there's a great, active community behind it, so there would be custom hacks and updates for it.
"MSI Windpad Enjoy 10" it's the exact model name. unfortunately this one is not a famous model and there's no useful information for this device
Goldiecalypso,
I do not know if it will work for you.
I have an Aishuo A816 which I could not get rooted, what I did was find a ROM that was pre rooted and forced an upgrade with that. Everthing is now fine and if I change rom I can now root with superoneclick.
Keith
we are also discussing on this matter:
http://forum.xda-developers.com/showthread.php?t=1453613
we have the official ROM, but nobody's here to make it rooted.
try to rooting msi enjoy windpad
hi goldiecalypso
can you to try learning how to rooting ?and rooting the msi windpad,together?
(excuse me for my bad English)
I want to, but I have no idea how to start!
i purchased 2 nook tablets for an 8 and 11 year old. im debating whether to not root it because i think it wil be easier for them to follow interface and the only downside i see is having to pay for apps that may be free on amazon or play store. can i have some input here? is there a super easy rooted rom that a child can follow? or are there many free aps if i just keep it as an out of box nook. thanks so much guys, these are the 1st gen nook tablets not the hd
Rooting just opens up the device. You'll still have full access to the stock interface and BN app store and what have you.
You can make a really child friendly user imterface with a rooted device running an alternate launcher. That way you can make different home screen with the apps you want them to use easily accessable.
Give it a go! It's really easy to go back should you want to.
asawi said:
Rooting just opens up the device. You'll still have full access to the stock interface and BN app store and what have you.
You can make a really child friendly user imterface with a rooted device running an alternate launcher. That way you can make different home screen with the apps you want them to use easily accessable.
Give it a go! It's really easy to go back should you want to.
Click to expand...
Click to collapse
thanks i dread having to do the whole sd card ota block thing again and havent done it in about a year. is there a good video out there to walk me through step by step again for the ota block? and can someone recommend the best barest bones rom to root afterwards to make it as easy for a child to use as possible?
and i think i had trouble the last time because only a certain size sd card could be used. wasn't it just the 2 or 4 gb that worked? thanks and sorry for all the questions. just have to get this done tonight so i can fedex it to texas to get there in time for xmas.
A rooted nook is just marginally better than a stock nook in terms of access to more apps, but might be more confusing to kids since it has two coexisting interfaces. You would be better off sticking with stock or go all out android with full-fledged CM10.
I think the rooted stock NT is loads better than than the true stock. LOADS! Had the stock reader dealt better with my side loaded books I wouldn't have installed CM10 internally.
I agree that the double interface can be a bit confusing but to kids that age it shouldn't be much of a problem.
The OTA block is just a process of a few clicks from within the NT hidden settings app.
asawi said:
I think the rooted stock NT is loads better than than the true stock. LOADS! Had the stock reader dealt better with my side loaded books I wouldn't have installed CM10 internally.
I agree that the double interface can be a bit confusing but to kids that age it shouldn't be much of a problem.
The OTA block is just a process of a few clicks from within the NT hidden settings app.
Click to expand...
Click to collapse
im trying to use the same albert video http://www.youtube.com/watch?v=1zbT1Fj38nE, but the file doesnt even seem to be there anymore, and his updated video shows how to create a root v4 card. im totally confused. do you still need to block otas? and if so is there another link that shows that step by step. im ready to just send these back and forget the whole thing
No need for any video!
There are a couple of ready-made root images that are almost automatic. Burn the card, pop it in, install zip from card and you're rooted. Go to Google Play (it may show up as "market" at first and make sure you have updated version of NT Hidden settings to block OTA. It could not be much easier! If can watch a film on your DVD player you can do this without instruction video!
Brian's root (that I havetried once and really liked!): http://forum.xda-developers.com/showthread.php?t=1488035
Alberts (that I have also used several times and like as well): http://forum.xda-developers.com/showthread.php?p=21275927#post21275927
---------- Post added at 06:02 PM ---------- Previous post was at 05:39 PM ----------
And to expand a little:
1. Root the Tablet following the instructions in the root method you choose
2. Go to Google Market/Play and search for NT Hidden Settings
3. Open NT Hidden settings. Tap on "Hacks". When the prompt comes up "Allow" root access. You now get to a new menu where you can chhos Block OTA, Done!
Basic rooting instructions:
1. Download image file
2. Download imaging software if you don't already have it. (I like WinImage. I keep it in a folder and put my various image files in the same folder to make them easy to find)
3. Use your imaging software to burn a sd card. Albert's image will fit on a small card. I use a 1 GB, but I think smaller ones will do as well. Brian's image needs a larger card. I'm not sure how large, but the instructions probably tells you!
4. Boot to your sd card and follow the instructions for the method you have choosen. There are step by step instructions in both of the methods I have linked to, and probably others as well!
5. Done!
asawi said:
No need for any video!
There are a couple of ready-made root images that are almost automatic. Burn the card, pop it in, install zip from card and you're rooted. Go to Google Play (it may show up as "market" at first and make sure you have updated version of NT Hidden settings to block OTA. It could not be much easier! If can watch a film on your DVD player you can do this without instruction video!
Brian's root (that I havetried once and really liked!): http://forum.xda-developers.com/showthread.php?t=1488035
Alberts (that I have also used several times and like as well): http://forum.xda-developers.com/showthread.php?p=21275927#post21275927
---------- Post added at 06:02 PM ---------- Previous post was at 05:39 PM ----------
And to expand a little:
1. Root the Tablet following the instructions in the root method you choose
2. Go to Google Market/Play and search for NT Hidden Settings
3. Open NT Hidden settings. Tap on "Hacks". When the prompt comes up "Allow" root access. You now get to a new menu where you can chhos Block OTA, Done!
Basic rooting instructions:
1. Download image file
2. Download imaging software if you don't already have it. (I like WinImage. I keep it in a folder and put my various image files in the same folder to make them easy to find)
3. Use your imaging software to burn a sd card. Albert's image will fit on a small card. I use a 1 GB, but I think smaller ones will do as well. Brian's image needs a larger card. I'm not sure how large, but the instructions probably tells you!
4. Boot to your sd card and follow the instructions for the method you have choosen. There are step by step instructions in both of the methods I have linked to, and probably others as well!
5. Done!
Click to expand...
Click to collapse
thank you so much for this help, figured it would be a slam dunk from here but when i try and unzip brians ntsdcard image file it says its corrupted and when i try and run alberts 32 diskimager it says it cant computer it. ive reinstalled and rebooted 3 times. can someone else try and open these file to se if its just my computer? dont know why it would be. or is there another work around? i heard he just sells the bootdisks. maybe thats the way to go. thanks again for all your help
I downloaded Albert's package. My virus protection alerter me, but that's probably because of the scripts that do need to be in that package, so I ignored that (I trust Albert!).
I then unzipped that into anew folder.
Inside that folder I find Wini32DiskImager, and I just open it from within that folder. (I realize I was mistaken in my previous post, This is the disk imager I prefer to use even though I've used others as well)
The program just opens in a small window. In the "choose file box" you automatically get directed to the folder you opened up from. That's why I keep my images there. Pick the one you want (you'll jut have one unless you've added)
Click "Write" when you've made sure the sd-cards drive letter is the one in the top right box.
gorelow said:
thank you so much for this help, figured it would be a slam dunk from here but when i try and unzip brians ntsdcard image file it says its corrupted and when i try and run alberts 32 diskimager it says it cant computer it. ive reinstalled and rebooted 3 times. can someone else try and open these file to se if its just my computer? dont know why it would be. or is there another work around? i heard he just sells the bootdisks. maybe thats the way to go. thanks again for all your help
Click to expand...
Click to collapse
this is the error i get the program cant start because libgcc_s dw2_dll is missing from your computer
I have now downbloaded and unszipped Brians file as well. Totally problem free!
What are you using to unzip? I use 7-zip.
By the way, I can now see that it looks like Brian's image needs a 2 GB card.
And for clairfication, you don't actually have to install Win32DiskImager. Just open it from within the folder!
---------- Post added at 08:33 PM ---------- Previous post was at 08:26 PM ----------
gorelow said:
this is the error i get the program cant start because libgcc_s dw2_dll is missing from your computer
Click to expand...
Click to collapse
Check the folder. That dll should be in the folder. It is in mine (the one I created just now). Are you really opening the program from within the folder?
The simplest and best rooting instruction I've found is one provided by liquidzoo's here.
I'd also suggest that before rooting the NT, you make a backup of your NT current software using the backup option of the same Recovery program that you will use to install the rooting mods.
If you have problem writing disk image with Win32DiskImager, you can use DiskImage_1_6_WinAll.exe instead.
---------- Post added at 04:47 PM ---------- Previous post was at 04:11 PM ----------
asawi said:
I think the rooted stock NT is loads better than than the true stock. LOADS!
...
Click to expand...
Click to collapse
We'll learn soon enough the moment the kids want some recently released game apps and find out they can't have them because they are not compatible with 2+ year-old Android Gingerbread which is what the stock ROM is based on.
gorelow said:
thanks i dread having to do the whole sd card ota block thing again and havent done it in about a year. is there a good video out there to walk me through step by step again for the ota block? and can someone recommend the best barest bones rom to root afterwards to make it as easy for a child to use as possible?
and i think i had trouble the last time because only a certain size sd card could be used. wasn't it just the 2 or 4 gb that worked? thanks and sorry for all the questions. just have to get this done tonight so i can fedex it to texas to get there in time for xmas.
Click to expand...
Click to collapse
You are getting your terminology confused as well. Asking what is the best barest bones ROM to root is incorrect.
To root means you give the nook superuser access which in turn allows you to load play store, apps, new launcher, and any SU related functions.
A ROM is a fully functioning version of android. IE: CM 7(GB), CM 9(ICS), CM 10(JB). It automatically has root access built in.
As for loading a ROM due to worrying about the kids and the interface, stock nook sucks...period. My 8 y/o has had zero issues with either cm 7 or cm10. Do yourself and them a favor and put at least CM 7 but preferably CM 10 on it.
Image files for dummies can be found at iamafanof.wordpress.com
Sent from my CM 10 SD nook tablet. Thanks devs.
gorelow said:
i purchased 2 nook tablets for an 8 and 11 year old. im debating whether to not root it because i think it wil be easier for them to follow interface and the only downside i see is having to pay for apps that may be free on amazon or play store. can i have some input here? is there a super easy rooted rom that a child can follow? or are there many free aps if i just keep it as an out of box nook. thanks so much guys, these are the 1st gen nook tablets not the hd
Click to expand...
Click to collapse
My sons are 8 and 12. Trust me, your kids won't have a bit of trouble with the CM10 interface. One of the nice extras in CM10 is that you can configure profiles to block them from getting into apps you don't want them to -- like settings, email, etc... Also, you can PIN-protect the Play Store so that they don't accidentally purchase anything.
SlowCobra96 said:
...
Image files for dummies can be found at iamafanof.wordpress.com
...
Click to expand...
Click to collapse
Since the OP will be using two NTs I'd suggest building the CM10 SD card from scratch (using the info and tools posted at http://iamafanof.wordpress.com/2012/11/11/how-to-guide-bootable-cm7cm9cm10-sdcard-for-nook-tablet/ and which I have provided a summary digest here), since there have been reports of NTs running the precooked CM10 SD image having identical MAC addresses and hence not able to concurrently access a same WiFi network (in this case the OP's household WiFi network).
I'm not saying rooted stock is as good as for example CM10. Not at all! CM 10 is awsome, and user interface is really nice!
But for a user that is intimidated by even the simple rooting process putting CM10 internally should not be even considered at this point. Thankfully the sd version of CM runs just as smooth as the internal install (at least it does from my 8GB Sandisk class 4) so that could certainly be an option as soon as the OP has figured out how to use the disk image writer! Yesterday even that was troublesome.
What I'm saying (if not straight out in my previous posts) is that rooted stock certainly is not bad! It depends on the kids and what they are used to if it will be "enough". For the kids near me (ages 4, 8,5 and 14) it certainly would! The bigger ones are girls that read a lot and apart from reading, watching Youtube videos and surfing (reading fashion blogs...) they are happy with a few cute games. Maybe if they had been boys and/or had tech savvy parents they would have asked for more, but they don't.
Either way, let's try to help the OP as well as we can!
asawi said:
I have now downbloaded and unszipped Brians file as well. Totally problem free!
What are you using to unzip? I use 7-zip.
By the way, I can now see that it looks like Brian's image needs a 2 GB card.
And for clairfication, you don't actually have to install Win32DiskImager. Just open it from within the folder!
---------- Post added at 08:33 PM ---------- Previous post was at 08:26 PM ----------
Check the folder. That dll should be in the folder. It is in mine (the one I created just now). Are you really opening the program from within the folder?
Click to expand...
Click to collapse
i think it was the winzip that was screwing me up. i used 7zip and it opened right up and i burned it onto the sd card. then after i powered off i held the n button and the N button and i was only brought to a screen that said so you want to factory reset. isnt that the way to boot up? it didnt seem to recognize the unziped ntboot file. thanks
Try to just boot up (from completely turned off) without holding any buttons. If you do need to keep the "n" pressed down at first, that's just for a few seconds and then let go. Some people need to keep the Tablet turned off and insert apowered USB cable (menaing it's coneected to the charger, not computer) to get it to boot from sd-card. No buttons pressed! I have never needed that myself, but I hear many others do.