Related
Just wondering if anyone is working on a one-click root or custom ROM (obviously, for a donation!!!) for the NC? I am going to take the time to root this weekend, but would obviously love to just DL something and flash it.
Well, one click isn't really one click. There are lots of other clicks involved, turn on computer clicks, go to download page clicks, download clicks, then load on SD card clicks or Start - Run - cmd clicks, then the closing windows clicks.
What I believe you should have been asking, without the sugarcoating of the "one-click" phrase, is: "If it isn't too much trouble, can I use your third Genie wish after you've rubbed the lamp? I'll donate, of course, not that it would matter because I can only assume one of those first two wishes was an insane amount of money"
devis said:
Well, one click isn't really one click. There are lots of other clicks involved, turn on computer clicks, go to download page clicks, download clicks, then load on SD card clicks or Start - Run - cmd clicks, then the closing windows clicks.
What I believe you should have been asking, without the sugarcoating of the "one-click" phrase, is: "If it isn't too much trouble, can I use your third Genie wish after you've rubbed the lamp? I'll donate, of course, not that it would matter because I can only assume one of those first two wishes was an insane amount of money"
Click to expand...
Click to collapse
Precisely, what you said!!!! lol. Believe me, I try...
coldbeverage said:
Precisely, what you said!!!! lol. Believe me, I try...
Click to expand...
Click to collapse
Glad you enjoyed reading it as much as I did writing it
Now... that out of the way, and in all seriousness, can I use that third wish from someone?
devis said:
Glad you enjoyed reading it as much as I did writing it
Now... that out of the way, and in all seriousness, can I use that third wish from someone?
Click to expand...
Click to collapse
I'll have more time to mess with this after this week is over. On my todo list is trying the BN kernel's video console support so we can at least write a message to the screen when Nooter is done rooting, and copying over superuser.apk and su and maybe Astro for starting out.
With the above we could have an almost-1-click root if someone could make the card writing process easier. It would be nice if we had a Linux boot CD or boot USB image that can reformat the card (check that it's a USB device first and ask the user!) to make the boot partition the whole disk automatically. Or someone could verify the rumor that HP's USB bootdisk maker formats the drive correctly.
I'm not the guy to do a 1-click root; exploits aren't my thing, but my goal is to make Nooter easy enough that we don't need to go that route.
My apologies if this has been covered....but with my eken slate, we use an update.zip file....the device automatically does a restore with this file if its present on the sd card
Until someone actually does a custom rom roll, it's unlikely that you're going to see one-click root. Since B&N decided to hide the Android menus that would allow us to side-load Apps, we have to boot from the SD image as part of the process.
I will look into making things a little easier though by adding a few items to the list of things that nooter does:
+ Install ADW and/or Zeam.
+ Install android.hardware.touchscreen.multitouch.xml to enable multi-touch on Android applications that support it.
+ Enable the installation of Non-Market Apps.
I personally took a shortcut when it came to rooting my personal Nook Color. Others may want to use this method as well.
(1) Write the nooter image to SD:
# dd if=nooter_sdcard_40mb.img of=/dev/<sdcard>
(2) Make sure that the Nook Color is powered off.
(3) Install the SD card with nooter written to it in the Nook Color
(4) Connect the Nook Color via USB to your computer. (Linux in my case). The Nook Color will power on all by its lonesome when it is connected to the USB.
(5) Wait a few minutes for nooter to do its thing. Seriously folks. Trying to time this down to seconds until you power the Nook Color off at this step is way overkill. Look at your watch. Add 5 minutes to whatever time it is. When 5 minutes have passed, you can safely go to step 6.
(6) Hold down the power button on your Nook Color for what seems like forever. You can count this one in seconds but, make sure that it has powered down. Without something on the screen, that is difficult to tell that it has powered down. I just timed it and an 8-10second continuous hold of the power button powered the Nook Color off. To be safe, lets say you hold it for 15 seconds.
(7) Remove the SD card from your Nook Color.
(8) Power your Nook Color Back on. (Hold the power button until you see the screen turn on. Duh!)
At this point, your Nook Color is should be rooted.
I then followed the instructions at nookdevs.com/NookColor_Rooting to use ADB to enable multi-touch and Non-Market Apps.
Thanks. I am just an IT lawyer who's only been at this android stuff since August so much to learn (for instance, figuring out what you wrote below.....I do try to learn and not constantly ask on here though)!!!!
johnopsec said:
Until someone actually does a custom rom roll, it's unlikely that you're going to see one-click root. Since B&N decided to hide the Android menus that would allow us to side-load Apps, we have to boot from the SD image as part of the process.
I will look into making things a little easier though by adding a few items to the list of things that nooter does:
+ Install ADW and/or Zeam.
+ Install android.hardware.touchscreen.multitouch.xml to enable multi-touch on Android applications that support it.
+ Enable the installation of Non-Market Apps.
I personally took a shortcut when it came to rooting my personal Nook Color. Others may want to use this method as well.
(1) Write the nooter image to SD:
# dd if=nooter_sdcard_40mb.img of=/dev/<sdcard>
(2) Make sure that the Nook Color is powered off.
(3) Install the SD card with nooter written to it in the Nook Color
(4) Connect the Nook Color via USB to your computer. (Linux in my case). The Nook Color will power on all by its lonesome when it is connected to the USB.
(5) Wait a few minutes for nooter to do its thing. Seriously folks. Trying to time this down to seconds until you power the Nook Color off at this step is way overkill. Look at your watch. Add 5 minutes to whatever time it is. When 5 minutes have passed, you can safely go to step 6.
(6) Hold down the power button on your Nook Color for what seems like forever. You can count this one in seconds but, make sure that it has powered down. Without something on the screen, that is difficult to tell that it has powered down. I just timed it and an 8-10second continuous hold of the power button powered the Nook Color off. To be safe, lets say you hold it for 15 seconds.
(7) Remove the SD card from your Nook Color.
(8) Power your Nook Color Back on. (Hold the power button until you see the screen turn on. Duh!)
At this point, your Nook Color is should be rooted.
I then followed the instructions at nookdevs.com/NookColor_Rooting to use ADB to enable multi-touch and Non-Market Apps.
Click to expand...
Click to collapse
coldbeverage said:
Thanks. I am just an IT lawyer who's only been at this android stuff since August so much to learn (for instance, figuring out what you wrote below.....I do try to learn and not constantly ask on here though)!!!!
Click to expand...
Click to collapse
No problem. Just so nobody is confused about anything I posted above: I take absolutely no credit for anything (especially nooter) in my post. I simply wrote down the steps I took using OTHER PEOPLES ideas and code.
Your simple instructions are pefect! The only thing I would add is for the Windows users to use WinImage on step 1.
Rooting really is easy; it is getting the ADB drivers to work properly (for us Windows users) that is the difficult step. If you can modify nooter to add the extra steps of writing the file to allow .apk installation; installing Astro or other file explorer; installing a launcher (Zeam seems to be a good choice); and maybe SlideME as a Market until the Google Market is figured out - I think the rooting process couldn't be much easier given the nature of the device!
johnopsec said:
Until someone actually does a custom rom roll, it's unlikely that you're going to see one-click root. Since B&N decided to hide the Android menus that would allow us to side-load Apps, we have to boot from the SD image as part of the process.
I will look into making things a little easier though by adding a few items to the list of things that nooter does:
+ Install ADW and/or Zeam.
+ Install android.hardware.touchscreen.multitouch.xml to enable multi-touch on Android applications that support it.
+ Enable the installation of Non-Market Apps.
I personally took a shortcut when it came to rooting my personal Nook Color. Others may want to use this method as well.
(1) Write the nooter image to SD:
# dd if=nooter_sdcard_40mb.img of=/dev/<sdcard>
(2) Make sure that the Nook Color is powered off.
(3) Install the SD card with nooter written to it in the Nook Color
(4) Connect the Nook Color via USB to your computer. (Linux in my case). The Nook Color will power on all by its lonesome when it is connected to the USB.
(5) Wait a few minutes for nooter to do its thing. Seriously folks. Trying to time this down to seconds until you power the Nook Color off at this step is way overkill. Look at your watch. Add 5 minutes to whatever time it is. When 5 minutes have passed, you can safely go to step 6.
(6) Hold down the power button on your Nook Color for what seems like forever. You can count this one in seconds but, make sure that it has powered down. Without something on the screen, that is difficult to tell that it has powered down. I just timed it and an 8-10second continuous hold of the power button powered the Nook Color off. To be safe, lets say you hold it for 15 seconds.
(7) Remove the SD card from your Nook Color.
(8) Power your Nook Color Back on. (Hold the power button until you see the screen turn on. Duh!)
At this point, your Nook Color is should be rooted.
I then followed the instructions at nookdevs.com/NookColor_Rooting to use ADB to enable multi-touch and Non-Market Apps.
Click to expand...
Click to collapse
jasoraso said:
Your simple instructions are pefect! The only thing I would add is for the Windows users to use WinImage on step 1.
Rooting really is easy; it is getting the ADB drivers to work properly (for us Windows users) that is the difficult step. If you can modify nooter to add the extra steps of writing the file to allow .apk installation; installing Astro or other file explorer; installing a launcher (Zeam seems to be a good choice); and maybe SlideME as a Market until the Google Market is figured out - I think the rooting process couldn't be much easier given the nature of the device!
Click to expand...
Click to collapse
^ This.
Thats the main reason I am holding out on rooting... That and I want to see how far it goes before the market place comes out unless an easy solution like this comes out. While I like the updates here, I am also not in a huge needs for a large phone... but still Great work so far!!!
johnopsec said:
No problem. Just so nobody is confused about anything I posted above: I take absolutely no credit for anything (especially nooter) in my post. I simply wrote down the steps I took using OTHER PEOPLES ideas and code.
Click to expand...
Click to collapse
Lol. I just meant that I try to help you guys, but I have so much to learn on actually doing the stuff you do. Everyone is sharing there stuff on here openly. All good.
I am going to try to teach myself how to use ADB. Kinda nervous though.
jasoraso said:
Your simple instructions are pefect! The only thing I would add is for the Windows users to use WinImage on step 1.
Rooting really is easy; it is getting the ADB drivers to work properly (for us Windows users) that is the difficult step. If you can modify nooter to add the extra steps of writing the file to allow .apk installation; installing Astro or other file explorer; installing a launcher (Zeam seems to be a good choice); and maybe SlideME as a Market until the Google Market is figured out - I think the rooting process couldn't be much easier given the nature of the device!
Click to expand...
Click to collapse
coldbeverage said:
I am going to try to teach myself how to use ADB. Kinda nervous though.
Click to expand...
Click to collapse
No kidding, that is whaat ij aam strugglliing with. Thhaatt and tthe stupid keyybboard!
pokey9000 said:
With the above we could have an almost-1-click root if someone could make the card writing process easier. It would be nice if we had a Linux boot CD or boot USB image that can reformat the card (check that it's a USB device first and ask the user!) to make the boot partition the whole disk automatically. Or someone could verify the rumor that HP's USB bootdisk maker formats the drive correctly.
Click to expand...
Click to collapse
I was messing around with UNetBootin, which is similar to the HP USB formatter. It is designed to take linux ISOs and format them as bootable. But I don't know what specialized format Nooter uses. I didn't get far on this front.
It seems windows users are having trouble with windows drivers needed to get USB ADB working. An alternative is to enable ADB over IP. Leaving this open persistantly is a security hole, but it may be appropriate for initial setup.
PHiZ said:
I was messing around with UNetBootin, which is similar to the HP USB formatter. It is designed to take linux ISOs and format them as bootable. But I don't know what specialized format Nooter uses. I didn't get far on this front.
It seems windows users are having trouble with windows drivers needed to get USB ADB working. An alternative is to enable ADB over IP. Leaving this open persistantly is a security hole, but it may be appropriate for initial setup.
Click to expand...
Click to collapse
Getting the OMAP to boot off of SD requires a few things:
-the OMAP wired to boot from SD
-an SD card with a specific disk geometry as reported by the partition table
-a FAT16 or 32 filesystem on the first partition
-a first and second stage bootloader (MLO and u-boot.bin) in the FAT filesystem
The hardest part of getting Nooter installed correctly is creating that special partition table, and so I released it as a raw dump of an SD formatted using that scheme to only a 40MB image. The theory I've heard is that for maximum BIOS compatibility the HP USB formatter tool generates this same sort of geometry, after which you just need to drag and drop the four Nooter files onto the drive. I haven't had a chance to try this yet though.
edit: I'll be damned, it does work! Just format using hpusbfw.exe (Google it) with "quick format" checked and "create a dos startup disk" unchecked. Then copy MLO, u-boot.bin, uImage, and uRamdisk over. That's it. Plus you wind up with a FAT32 partition that takes up your whole disk, not just 40MB.
pokey9000 said:
Getting the OMAP to boot off of SD requires a few things:
-the OMAP wired to boot from SD
-an SD card with a specific disk geometry as reported by the partition table
-a FAT16 or 32 filesystem on the first partition
-a first and second stage bootloader (MLO and u-boot.bin) in the FAT filesystem
The hardest part of getting Nooter installed correctly is creating that special partition table, and so I released it as a raw dump of an SD formatted using that scheme to only a 40MB image. The theory I've heard is that for maximum BIOS compatibility the HP USB formatter tool generates this same sort of geometry, after which you just need to drag and drop the four Nooter files onto the drive. I haven't had a chance to try this yet though.
edit: I'll be damned, it does work! Just format using hpusbfw.exe (Google it) with "quick format" checked and "create a dos startup disk" unchecked. Then copy MLO, u-boot.bin, uImage, and uRamdisk over. That's it. Plus you wind up with a FAT32 partition that takes up your whole disk, not just 40MB.
Click to expand...
Click to collapse
Sounds like we may be getting close to a custom rom....????
Is the uImage the ROM? or is it all 4 pieces
Sorry if I am misunderstanding this pokey since I am a total noob. I too have been holding out on rooting hoping for an easier solution (I do not even know how to navigate to directories in terminal) I believe you are implying that the NC can be rooted using this method and is in fact much easier to accomplish. You said that you had to copy over those 4 files once you format the card. Where can one obtain those files?
Thanks man for all your dedication and hard work!
sudermatt said:
Sounds like we may be getting close to a custom rom....????
Is the uImage the ROM? or is it all 4 pieces
Click to expand...
Click to collapse
MLO - first stage bootloader. The OMAP's built in ROM looks for this on the SD and runs it. MLO then looks for u-boot.bin and runs it if it can find it on the card. It's like the Nook's boot sector.
u-boot.bin - second stage bootloader. This is responsible for figuring out how to get Linux and the ramdisk in memory. This copy loads up uImage and uRamdisk from microsd and starts running the kernel. This is similar but not the exact same as the one on the internal flash.
uImage - The Linux kernel. This copy is built specifically for Nooter.
uRamdisk - a Linux filesystem that gets loaded into RAM. Contains the Nooter script, disk utilities for performing the root, and other bits and pieces that let you log in over USB and get a shell.
This really has nothing to do with a custom ROM, it's just an easier way to install Nooter.
th3c1am said:
Sorry if I am misunderstanding this pokey since I am a total noob. I too have been holding out on rooting hoping for an easier solution (I do not even know how to navigate to directories in terminal) I believe you are implying that the NC can be rooted using this method and is in fact much easier to accomplish. You said that you had to copy over those 4 files once you format the card. Where can one obtain those files?
Thanks man for all your dedication and hard work!
Click to expand...
Click to collapse
If you have a card with Nooter on it, you could mount it on a PC and pull all 4 files off. Using the HP utility is an easier option for people who want to root under Windows and are having trouble with the disk utilities. When I get a chance I'll post the files separately.
My kids received Nook Color readers for Christmas, and like everything, they look to Dad to optimize them.
I was going to try rooting, but a couple of things remain unclear:
- Do I have to 'auto-noot' to root the Noot, or are there other options (other tools, manual rooting, etc.)
- Should I upgrade the software to 1.0.1 prior to rooting or not?
I tried to give auto-noot for 1.0.0 a quick run, but I couldn't get the SD card to boot (and a check revealed that I had two FAT16 partitions, one with the appropriate images and the other with the files needed). I'm assuming it's because the card I have might be too slow (portal recommends Class 6 or greater, and the card I'm using is a cheapo card I got with an earlier phone that I'm not too sure of).
Thoughts? Tips?
I upgraded mine to 1.0.1 first then rooted.
What OS is on your PC?
If Windows, did you use Win32DiskImager to write the image to microSD card?
Take a look at here for different ways of rooting here http://www.nookdevs.com/Portal:NookColor#Rooting
The easiest and the way I rooted is below which I borrowed from http://blogkindle.com/2010/12/read-kindle-books-on-nook-color/
Here’s what you need to do:
1. Before rooting make sure that you’ve registered the device with B&N as it might not work after rooting.
2. Download nooter that corresponds to you Nook version. You can check your Nook version by pressing Nook button, selecting “Settings” >> “Device Info” >> “About your NOOKcolor” >> Software version:
--- for 1.0.0 – GabrialDestruir’s auto nooter 2.12.15 file 15 Dec 2010
--- for 1.0.1 – GabrialDestruir’s auto nooter 2.12.25 file 25 Dec 2010
3. Unpack the file
4. On Windows use Win32DiskImager to write the image to microSD card (please note that all data on the card will be lost). For Linux or Mac, check out NookDevs.com for detailed microSD imaging instructions.
5. Completely power off NOOKcolor by holding the power button until the screen blurs and “Power off NOOKColor” dialog appears. Select “Power Off” and wait for the device to shut down completely.
6. Turn device face down and open the microSD card container in the lower right corner. Push the card in with metal contacts facing down.
7. Connect the device to your computer via USB cable. The device will power up and book from the SD card but the screen will not turn on. This is normal.
8. After about a minute your computer show detect the new device. This means that the rooting is complete. Your Windows computer will complain about missing drivers. This is normal.
9. Disconnect the USB cable and remove the card from the reader.
10. Power cycle it by holding the power button for 20 seconds and then releasing it. The press the power button briefly to power the reader on.
11. As the reader boots you will see a red splash screen.
12. Once the reader boots, you will be prompted for you Gmail account (as usually with Android) and some initial settings. This will only happen once.
13. As you open the extras folder you will see that it now contains Android market icon and some extras (Youtube, Gmail, etc)
14. You can now start the market app and download other apps that you like. You will need to reboot the device for apps to appear on the extras page. The apps themselves can be used right away just as with usual Android apps.
I would look for the thread in the android development section for auto nook 1.01. Update the OS to 1.01, then do the nook-ing process. Its all laid out there in the opening post.
I would definitely root your nooks to get the most out of them.
I'm guessing he meant Auto-Nooter 2.12.25 (1.0.1 Only), which the thread can be found here
I was looking for a manual method because I didn't have my card reader at work yesterday, and I couldn't get the card I wrote in my Incredible to boot Auto-Noot in 1.0.0.
Oddly enough, after deciding to upgrade to 1.0.1 first, when I tried to root the second time it worked just fine. I did the second one after upgrading, also went without a hitch. Think it just makes sense to upgrade first, seeing as they're both exploitable.
giantcrazy said:
I was looking for a manual method because I didn't have my card reader at work yesterday, and I couldn't get the card I wrote in my Incredible to boot Auto-Noot in 1.0.0.
Oddly enough, after deciding to upgrade to 1.0.1 first, when I tried to root the second time it worked just fine. I did the second one after upgrading, also went without a hitch. Think it just makes sense to upgrade first, seeing as they're both exploitable.
Click to expand...
Click to collapse
How can you write an image from your Incredible? You need to use a computer to write the "image" not just the files to the sdcard, to make it bootable.
-CC
clockcycle said:
How can you write an image from your Incredible? You need to use a computer to write the "image" not just the files to the sdcard, to make it bootable.
-CC
Click to expand...
Click to collapse
I spent some time re-inventing the wheel before I realized someone had documented the method on XDA (my fault for being search lazy):
http://forum.xda-developers.com/showthread.php?t=889001
You use the Linux DD command to write the image to the SD card, which renders it with the correct partitions and files needed to complete root. I did it yesterday, and assumed that I had either too slow a card or it didn't work, until I upgraded to 1.0.1 first and it worked at first crack. Just take care to write the card with the correct device name, mmcblk1.
I used GParted on Linux to double-check after doing my fdisk, everything looked kosher to me and it worked flawlessly.
giantcrazy said:
I spent some time re-inventing the wheel before I realized someone had documented the method on XDA (my fault for being search lazy):
http://forum.xda-developers.com/showthread.php?t=889001
You use the Linux DD command to write the image to the SD card, which renders it with the correct partitions and files needed to complete root. I did it yesterday, and assumed that I had either too slow a card or it didn't work, until I upgraded to 1.0.1 first and it worked at first crack. Just take care to write the card with the correct device name, mmcblk1.
I used GParted on Linux to double-check after doing my fdisk, everything looked kosher to me and it worked flawlessly.
Click to expand...
Click to collapse
Ah, totally forgot about that.. Well glad you got it sorted.
-CC
Obviously this guide owes a huge bunch of thanks to "TheManii", "Giveen" and other folks who can't be named on this forum. I have tested this on both a Streak 7 WiFi and a Streak 7 4G. In both cases they had the Stock Honeycomb already on them. So if you are coming from some other version of Android you may wish to reconsider
1) Download the Fastboot+ADB.zip file for Clockwork Mod 5.0.2.7 from the XDA Developers thread (http://forum.xda-developers.com/showthread.php?t=1334487)
2) Download the Clockwork mod 5.0.2.7 file from the XDA Developers thread (http://forum.xda-developers.com/showthread.php?t=1334487)
3) Go into Settings->Applications and turn on "Run Applications from Unknown Sources"
4) Go to Development Settings and select "USB Debugging"
5) Unpack the Fastboot+ADB file into a directory on your computer where you can find it again
6) Attach the Streak to your PC, and copy the "Drivers.zip" file from the root directory of the Streak (/sdcard) to the same directory where you unpacked the Fastboot file
7) Turn off your Streak after you have copied this file, and disconnect it from the PC
8) Unpack the drivers.zip file and find the "Setup.MSI" file. Execute this file to install the drivers you will need
9) Put your Streak into Fastboot mode - i.e. turn it off, then turn it on by pressing the Power button while holding the Vol DOWN (-) at the same time. This can take up to 20 seconds
10) You will get some red text followed by a white line saying something about Fastboot USB downloading is active
11) Connect the streak to the PC now, and it should install an Android ADB driver. Depending on what you have already setup you may get some drivers installed successfully, and some not. In general if you've been following this guide, you'll be ok
12) Open a command line for the folder where you have fastboot and your recovery image (ClockWorkMod) - in windows navigate to the folder, and hold the shift key while right clicking
13) On the command line type the following:
fastboot -i 0x413C flash recovery recovery.img (where recovery.img is the ClockworkMod or other recovery file)
14) On the command line type the following:
fastboot -i 0x413C reboot
15) Your device should now reboot
16) To get it to reboot into CWM, turn the Streak off, and then turn it on again while holding the Power Button and Volume UP (+) at the same time. This may take up to 30 seconds
From here you would follow the normal CWM options to install just the root files (Superuser7 for one example) or install a custom ROM.
It turns out steps 9 - 15 are also a great way to fix the problem when your Streak comes up and starts asking for a Password when you never setup a password. For some reason installing one of the custom ROMS also installs a version of CWM that is not as recent as the 5 series, which can lead to issues with the signature verification (i.e. when things go "boom", Android sees the partition as encrypted rather than just "locked"). So steps 9 - 15 allow you to put in a later CWM which does a proper wipe, and you're back in business. Have to reinstall apps, but the data is left alone.
Just in case I'm not the only one who has run into this
Ok, I used this guide to modify my Dell Streak 7 wifi. After I was done my screen kept flickering and I put it back to stock thanks to AndroidOVERALL putting together a post on how to complete the restore.
I have searched about the screen flickering but didn't find a resolution. Maybe I missed it, but it seemed that others had the same issue and it was either a hardware problem, the brightness was adjusted, or auto rotate was disabled. I tried adjusting the brightness settings and many other settings but the issue was not resolved until I returned everything to stock.
I have a Dell streak 7 wifi, US version with Honeycomb.
Please point me in the right direction if this issue has been resolved and I missed it. If not any suggestions?
Did you load a custom ROM after following these steps, or did you just reboot aft getting CWM installed. Usually the flickering comes from an issue with the video driver (so can be software if a bad driver, or hardware if it's only marginally in spec).
For any one who gets to the end of the steps and now can boot in go CWM but doesn't know what to do about getting rooted.
Very very Simple.
Download Superuser7.zip
http://www.tablet-cables.com/streak/tools/root/Superuser7.zip
Have your Streak booted normally and USB cable hooked up.
Move to the internal Memory Superuser7.zip
power off device
Power back on using Vol UP & Power Button
Select 2. Software upgrade via update.pkg on SD card and press power
CWM will load.
Select install zip from sd card and power to enter.
select Choose zip from internal sd card and power.
use Vol UP to go backwards to your files and select Superuser7.zip and hit power
move down to YES - Install Superuser7.zip and hit power
thats it. its rooted.
goto ++++++++ Go Back+++++++
and reboot system now
and let it reboot.
Not necessary, but I'd suggest running Superuser and hitting the Knob icon top right (settings) and scrolling down and updating Super User.
Hope this helps someone who may not know where to get Superuser7 and what to do after following the great guide above.
thanks!
nothing sucks worse than a bad download -- happend TWICE! (dayum!)
got rewt?
Help?
I am trying to Flash superuser.zip after installing the clockwork.
But I keep getting the following screen. I do not have exterior sd card installed.
What can I do?
blastedmax said:
I am trying to Flash superuser.zip after installing the clockwork.
But I keep getting the following screen. I do not have exterior sd card installed.
What can I do?
Click to expand...
Click to collapse
It's saying that it is looking for an SD Card and not finding it, so that certainly makes sense. However, it sounds like it is looking for "update.pkg" rather than "superuser.zip", so is it possible you accidentally selected the "Update" option in CWM rather than the option to select a file?
He doesnt have clockwork mod installed, you must have CWM installed to flash zips
OK, I have a new Streak 7 t-mobile with HC 3.2. I plug it to the pc running xp sp3, and it needs drivers for MTP and Streak7. I pointed to the Fastboot+ADB folder I extracted for the Streak7 driver and it installed Android ADB Interface. Pointing there for MTP fails to find a driver. I can't get to the internal SD to get the drivers.zip because my computer won't recognize the Streak until the MTP driver is installed. After installing an MTP driver from the net, I can see the internal and external SD. I copied everything to a single folder labelled STREAK in c:\ and unplug the Streak from the pc. I put the Streak into fastboot mode (Volume - & Power), wait about 10 seconds, then plug it into the usb port. The computer see the Fastboot device and needs a driver. I point it to the STREAK folder (former Fastboot+ADB) but it didn't find a driver it liked. I tried to install manually, but there is no Android 1.0 or Android ABD Interface devices in my list. I do see Android USB Devices, but it is empty when I click on it. ANYBODY else get this, and how do I move forward? I followed the guide to the letter, and appreciate all the work & effort you guys put into making these root methods available. The Streak7 is a cool little device, but I think it will be cooler once I root it. I have rooted my Epic 4g and the wife's Evo 4g on this same computer, and I do have the Android SDK installed (even though I don't know how to use it).
OK, so I used all the same files I have here and was able to successfully get Clockwork flashed & gain root. I dunno why the xp machines don't like these files. I tried 3 other xp laptops before getting to my wife's Windows 7 laptop, which worked just as described in the very well-written guides. #MindBottling!
I cannot even find the drivers.zip in step6. WIN7x64 and a brand new tmobile streak 7. where is this thing? I looked through all the folders and subfolders.
Drivers.zip is in the main directory of the Streak. Open up ES File Manager or a similar program and you should see it. To get it to your PC, attach the Streak via USB and let it mount as external storage (default behavior I believe).
In my main directory on on my streak, using ES file explorer, i cant seem to find that file. I see acct, cache, config, d, ....etc folders, i scroll down, i see default.prop, init, init_recovery.rc, ...... var files, but i dont see drivers.zip. help I need to get honeycomb so I can use skype front facing camera, cause I understand froyo 2.2 can only use the back camera w skype.
Since this should be a common file for all SD7 units, can someone please email that file to me so i can get past step 6. [email protected]
cidand1 said:
In my main directory on on my streak, using ES file explorer, i cant seem to find that file. I see acct, cache, config, d, ....etc folders, i scroll down, i see default.prop, init, init_recovery.rc, ...... var files, but i dont see drivers.zip. help I need to get honeycomb so I can use skype front facing camera, cause I understand froyo 2.2 can only use the back camera w skype.
Click to expand...
Click to collapse
From this I gather your Streak did not ship with Honeycomb. That would explain why you didn't find the file as that is something that I gather Dell added when they changed how they shipped it later on. I am not sure what the redistribution rules are for the file, which is why I haven't posted it myself.
That said, I also can't guarantee this process will work for someone starting with Froyo. I do know there may be an issue with which version of CWM you can use in that case. As such, you may want to check one of the other guides to be sure.
EwanG said:
From this I gather your Streak did not ship with Honeycomb. That would explain why you didn't find the file as that is something that I gather Dell added when they changed how they shipped it later on. I am not sure what the redistribution rules are for the file, which is why I haven't posted it myself.
Click to expand...
Click to collapse
Explain please? Shouldn't drivers be present no matter how it's shipped? Mine came with Froyo with drivers, I OTA'd to HC and I still have them.
Ya I bought this from dell directly about 3 weeks ago. From what I have been reading on XDA, mine is definitely different. Its a tmobile streak 7.
Android 2.2.2
Kernel : 2.6.32.9
OEM ver: GLUNB1A133633
Build : 15420
Another thing I noticed is that even trying to load CWmod through fastboot, my computer does not recognize the DS7 in fastboot mode. The drivers in the fastboot+ADB zip file dont work on my computer as fastboot drivers (or maybe I should try another CPU). My cpu is an AMD 64; running win7 pro 64; i need some serious help.
I think I bricked!
Ok I followed the directions from here to root my tablet.
http://www.cesgeekbook.com/2011/12/root-dell-streak-7-with-honeycomb-32.html
All went well! Everything worked and I was rooted! did the Superuser7. Clockwork came up and installed. All went right! So I was pleased. I figured I would later than put on a ROM cause it was late. Well was going to do so and tried to go into clockwork via ROM manager. Didn't work! Kept rebooting! So I figured I would try the pother way "Press Power and +" then click to Install from SD Card to go into Clockwork. That didn't work either! Then Now it won't reboot at all! I can get into fastboot and I can get into the bootloader. But that's it! I tried to do a Factory Reset and nothing! it just stays on the Dell boot screen. Anyway to fix the problem? If so, please give me step by step directions on how to do it.
Use of ROM Manager is generally discouraged due to unknowns about how the package will work with other ROMs. It also isn't clear to me which version of CWM you were using.
If you can get into fastboot, then you should still be able to use ADB, and I would suggest trying to reinstall CWM as indicated in the first message of this thread. That way at least you should be at a known good spot for us to try and help you get a custom ROM installed.
EwanG said:
Use of ROM Manager is generally discouraged due to unknowns about how the package will work with other ROMs. It also isn't clear to me which version of CWM you were using.
If you can get into fastboot, then you should still be able to use ADB, and I would suggest trying to reinstall CWM as indicated in the first message of this thread. That way at least you should be at a known good spot for us to try and help you get a custom ROM installed.
Click to expand...
Click to collapse
Didn't know about the Rom Manager issue. I guess it's only good to use on cell phones? Anyway, I am trying again, but the problem is my laptop is now not reading the tablet when in fastboot mode. I have followed all the step again. Including reinstalling the drivers. But since it's not reading the tablet. I can not reinstall CWM. The version I installed was the one from the 1st page. It's a fairly simple thing to do. But just need to get the device to be read by my laptop.
I have contacted Dell and explained to them the problem. They did say that I can return it to get it fixed. but still kind of hoping I can do it from home.
Marvelous0ne said:
Anyway, I am trying again, but the problem is my laptop is now not reading the tablet when in fastboot mode. I have followed all the step again. Including reinstalling the drivers.
Click to expand...
Click to collapse
Not sure what you mean when you say the laptop is not reading the tablet in fastboot mode. When in fastboot it should NOT show up as attached storage. The best way to tell if it is "really" seeing the Streak 7 is in step 13 - which uses an id rather than a device name so that it should work even if the tablet isn't fully identified. If you try to perform step 13 while in fastboot, what message are you getting?
Hi, sorry if this in the wrong location, I'm new to android and just learning my way around here. Id like to root my hook hd but the first time I powered it on it automatically updated to 2.0.5.
Ive read the rooting threads and the 8 reset trick to force a complete wipe and factory reset, but how to i pass the the wifi setup screens etc (oobe?) as it will just accept the pushed upgrade again.
***edit** after finding the right search terms for google I finally found the instructions here with pictures for anyone else wishing to know how to do this
techunsupport . wordpress. com
quick summary factory reboot power + N, N, N on welcome screen do either of the following
vol up + touch bottom right of screen factory screen button appears
vol down + touch bottom left of screen enable adp button appears
on factory screen vol up + touch bottom right of screen skip OOBE button appears
thanks
You can root firmware 2.0.5 now. See this thread:
http://forum.xda-developers.com/showthread.php?t=2062613
Thanks I had read that thread but I dont have a microsd reader for the pc. Unless I missunderstood and you dont need a card for the rooting part only CM10 install?
growlley said:
Thanks I had read that thread but I dont have a microsd reader for the pc. Unless I missunderstood and you dont need a card for the rooting part only CM10 install?
Click to expand...
Click to collapse
You do need a card and a card reader. But external card readers are cheap.. some cards even come with them.
Sent from my Nook HD+ Running CM10 on SD
root
ok I have adb working correctly to side load stuff but I have been trying to follow the instructions in the thread here http://forum.xda-developers.com/showthread.php?t=1981617&page=1 to gain root.
The process is failing in clrbootcount.sh as the line that should call the hook process is comented out and I cant just copy a file over the top as it says read only file system is there any way round this?
cheers
growlley said:
ok I have adb working correctly to side load stuff but I have been trying to follow the instructions in the thread here http://forum.xda-developers.com/showthread.php?t=1981617&page=1 to gain root.
The process is failing in clrbootcount.sh as the line that should call the hook process is comented out and I cant just copy a file over the top as it says read only file system is there any way round this?
cheers
Click to expand...
Click to collapse
That is how B&N broke root on 2.0.5. The only way to get root on 2.0.5 is to use my CWM method in my HD CWM thread linked in my signature.
Sent from my Nook HD+ Running CM10 on SD
thanks for the reply, I thought it might be so i ordered a card reader. Now haver to wait for the postie.
BAH
growlley said:
thanks for the reply, I thought it might be so i ordered a card reader. Now haver to wait for the postie.
Click to expand...
Click to collapse
Just my typical luck with gadgets , card and reader arrived today nook will see card , pc dectects reader but says no media no matter what you do so cant copy flash image to it I hate f*****g pc's
help
ok I followed the clockwork mod and created a card , backed up the image and then installed the universal root and the gApps + others zip using the instructions.
The deive rebooted successfully but I am having a problem with google play, it wont let me authenticate I try and add a google account and get a white dialog box saying unfortunately, setting has stopped. This happens for both existing and new options.
Iwanted to add home 2. I had play s working before via siding loading unfortunately the pc that had adb on it went to microprocessor heaven. Any ideas?
growlley said:
ok I followed the clockwork mod and created a card , backed up the image and then installed the universal root and the gApps + others zip using the instructions.
The deive rebooted successfully but I am having a problem with google play, it wont let me authenticate I try and add a google account and get a white dialog box saying unfortunately, setting has stopped. This happens for both existing and new options.
Iwanted to add home 2. I had play s working before via siding loading unfortunately the pc that had adb on it went to microprocessor heaven. Any ideas?
Click to expand...
Click to collapse
Did you add voice search? That causes settings to crash. See my instructions under voice search in my rooting thread.
Wait, you said you side loaded Play Store before? That is the problem. You need to wipe everything and start over. Do an erase and deregister. Or go to CWM and do a wipe data/factory reset.
Sent with XDA Premium from my Nook HD+ running CM10 on SD
I've been using Nook HD+ well so far but I stupidly tried to upgrade from CM 10.2.1 to unstable release today and made it brick. It doesn't even detect sdcard and doesn't go into recovery mode even if I press power and home key together.
This is the symptom. When it boots, it shows "nook" logo and disappear right away and show "nook" again and keep looping this sequence.
Please help me to fix this.
Use Initial ovation sdcard image (cwm).
Read verygreen's post...
http://forum.xda-developers.com/showthread.php?t=2600572
You should read 'For new Installs:'
You can't jump from jellybean(cm 10.2) to kitkat(cm 11) directly..
The proper way is to flash new cwm recovery for cm11 and reboot into that recovery and then flash latest cm11 zip.
You are bootlooped because you are still using old cwm recovery which was intended to use with cm 10.1 and 10.2.
For details ..
http://forum.xda-developers.com/showthread.php?t=2600572
Extra tips.. Power on device; As soon it shows nook logo insert sd card immediately. This might work.
Thank you com35 & keshabbhattarai126,
After some struggling, I got to boot as below. I made a booting image incorrectly. When I formatted it with SDformatter again and write the booting image then I could get into the attached screen. But there is another issue.
After I wrote the booting image, the size of sd card is extremely reduced - I used 32GB but it shows just some MB left - so I cannot copy a recovery and CM image, it complains as the size is not enough. So I cannot do "Boot CWM Recovery" as attached.
How can I make a booting sd card with other images?
Download this boot image. (for cm11 EMMC)
http://nook.rootshell.ru/hd/emmc-cwm-early3.1.img.gz
Download this recovery. (for cm11)
http://nook.rootshell.ru/hd/cwm-recovery-ovation-6.zip
Download CM rom from this site. (cm-11-20141112-SNAPSHOT-M12-ovation.zip)
http://download.cyanogenmod.org/?device=ovation
Use SD Formatter.
https://www.sdcard.org/downloads/formatter_4/eula_windows/
Click 'I Accept'
Download and install.
Click 'Option' button and change this ON.
FORMAT SIZE ADJUSTMENT - ON
And format SD card.
Hi com35,
I downloaded the files you mentioned and used SDfomatter with that option, so I wrote a boot image with Win32DiskImager and just copied over a recovery image directly, finally I could get into the recovery mode. But still, CWM image cannot be copied due to space shortage, so I copied this image to another sd card and replaces with the first sd card and tried to install but Nook cannot detect a replaced sd card.
Question:
So when I write above three images to sd card, at first, I need to write a boot image with Win32DiskImager and copy the other two images diectly(copy and paste)? How can all be copied since there is no enough space once a boot image is written?
I also tried to copy CWM into the internal memory but USB driver doesn't work correctly somehow.
ejkim01 said:
...
Question:
So when I write above three images to sd card, at first, I need to write a boot image with Win32DiskImager and copy the other two images diectly(copy and paste)? How can all be copied since there is no enough space once a boot image is written?
Click to expand...
Click to collapse
You should write emmc-cwm-early3.1.img to SDcard using Win32DiskImager, then copy the 3 zip files: cwm-recovery-ovation-6.zip, CM11 ROM zip and Gapps zip (from http://wiki.cyanogenmod.org/w/Google_Apps) to the SDcard.
A slightly different way of creating the CM11 installation SDcard is outlined at http://forum.xda-developers.com/showthread.php?t=2679899.
Install boot image to SD card with Win32DiskImager.
And copy only recovery file.
Insert SD card and turn on nook.
Just install recovery file in recovery mode(SD).
Format SD card with SD Formatter. (FORMAT SIZE ADJUSTMENT - ON)
And copy rom and gapps to SD card.
Power off and insert SD card.
Boot into recovery mode(internal) with Power + n buttons.
Install rom and gapps.
And reboot.
Thank you all!
Finally I succeeded to flash CM11 on my Nook HD+, I almost dump it but you guys saved me.
One pending issue.
After I install CM11, it cannot connect to my PC, which shows USB driver problem in device manager with my Win8.1 PC.
As I googled, they say it's known issue with CM11, is this true?
Wireless copying is the only solution to move files?
Download 'usb_driver_r04-windows-B&N.zip' from this thread. (leapinlar's)
http://forum.xda-developers.com/showthread.php?p=34168454#post34168454
I don't know does it support Windows 8.1.
I think using SD card with card reader is better.
Or use cloud storage like google drive.
ejkim01 said:
Thank you all!
Finally I succeeded to flash CM11 on my Nook HD+, I almost dump it but you guys saved me.
One pending issue.
After I install CM11, it cannot connect to my PC, which shows USB driver problem in device manager with my Win8.1 PC.
As I googled, they say it's known issue with CM11, is this true?
Wireless copying is the only solution to move files?
Click to expand...
Click to collapse
Try turning off Android debugging in developer settings.
Sent from my BN NookHD+ using XDA Premium HD app
After turning off Android debugging option, "BN Nook+" was disappeared from faulty driver list but "MTP" is still there and Nook cannot connect to PC yet.
I tried with my ubuntu laptop, it has no problem at all, so I'll just use it when I need to copy files until CM fixes this issue.
Thank you all!
ejkim01 said:
...
After I install CM11, it cannot connect to my PC, which shows USB driver problem in device manager with my Win8.1 PC.
As I googled, they say it's known issue with CM11, is this true?
Wireless copying is the only solution to move files?
Click to expand...
Click to collapse
I have no problem accessing my HD+ (running CM11 M12) as a MTP device over USB from my Win 8.1 PC.
You should check to see if the MTP option on Settings->Storage->"Advanced settings" (the 3 vertical dot pulldown menu) is enabled.
---------- Post added at 08:21 PM ---------- Previous post was at 08:14 PM ----------
ejkim01 said:
After turning off Android debugging option, "BN Nook+" was disappeared from faulty driver list but "MTP" is still there and Nook cannot connect to PC yet.
I tried with my ubuntu laptop, it has no problem at all, so I'll just use it when I need to copy files until CM fixes this issue.
Thank you all!
Click to expand...
Click to collapse
To fix the "faulty driver" issue when using ADB-over-USB, see http://forum.xda-developers.com/showpost.php?p=57870838&postcount=19.
digixmax said:
I have no problem accessing my HD+ (running CM11 M12) as a MTP device over USB from my Win 8.1 PC.
You should check to see if the MTP option on Settings->Storage->"Advanced settings" (the 3 vertical dot pulldown menu) is enabled.
---------- Post added at 08:21 PM ---------- Previous post was at 08:14 PM ----------
To fix the "faulty driver" issue when using ADB-over-USB, see http://forum.xda-developers.com/showpost.php?p=57870838&postcount=19.
Click to expand...
Click to collapse
This is the symptom.
When I disable "Android debugging" in Developer options, Device manager shows no driver issue but Nook isn't shown in Windows explorer.
When I enable above, Device manager shows "BN NookHD+" and "MTP" error and cannot install usb driver even .inf value is same as the link.
ejkim01 said:
This is the symptom.
When I disable "Android debugging" in Developer options, Device manager shows no driver issue but Nook isn't shown in Windows explorer.
When I enable above, Device manager shows "BN NookHD+" and "MTP" error and cannot install usb driver even .inf value is same as the link.
Click to expand...
Click to collapse
Which USB driver package did you install/use?
You might want to double-check the hardware ID for your device (see step #5 of http://forum.xda-developers.com/showpost.php?p=42881406&postcount=1), as that's the ID to be used in the android_winusb.inf entry (it should be VID_2080&PID_0005&MI_01 as in my post, but just in case ...).
digixmax said:
Which USB driver package did you install/use?
You might want to double-check the hardware ID for your device (see step #5 of http://forum.xda-developers.com/showpost.php?p=42881406&postcount=1), as that's the ID to be used in the android_winusb.inf entry (it should be VID_2080&PID_0005&MI_01 as in my post, but just in case ...).
Click to expand...
Click to collapse
I followed your advice but it still complains as “The hash for the file is not present in the specific catalog file. The file is likely corrupt or the victim of tampering.”
So I found other solution for this:
http://www.getdriver.com/how-to/2410/make-windows-7-drivers-work-windows-8-8-1-inf-modding.html
But, it still cannot resolve my problem, my Windows 8.1 seems weird.
ejkim01 said:
I followed your advice but it still complains as “The hash for the file is not present in the specific catalog file. The file is likely corrupt or the victim of tampering.”
So I found other solution for this:
http://www.getdriver.com/how-to/2410/make-windows-7-drivers-work-windows-8-8-1-inf-modding.html
But, it still cannot resolve my problem, my Windows 8.1 seems weird.
Click to expand...
Click to collapse
FWIW, I initially used the SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.45.0 (http://downloadcenter.samsung.com/c...NG_USB_Driver_for_Mobile_Phones_v1.5.45.0.exe) and it works for all my Samsung as well as Nook tablets (MTP and/or UMS).
For ADB access for the HD+, I switched to the Universal_Naked_Driver_0.72.zip (https://www.youtube.com/watch?v=afrvSGiMAtk).
digixmax said:
FWIW, I initially used the SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.45.0 (http://downloadcenter.samsung.com/c...NG_USB_Driver_for_Mobile_Phones_v1.5.45.0.exe) and it works for all my Samsung as well as Nook tablets (MTP and/or UMS).
For ADB access for the HD+, I switched to the Universal_Naked_Driver_0.72.zip (https://www.youtube.com/watch?v=afrvSGiMAtk).
Click to expand...
Click to collapse
This doesn't work either for me.
It cannot install Samsung driver.