So I took the plunge and tried to root a Nook 8GB today. So far I have done the following: (1) created the CWM microsd card; (2) copied the latest CM10 and Gapps roms to another microsd card.
I used thes Ray Waldo instructions for creating the cwm card:
root-nook-tablet-with-cwm-sdcard
So, I am having a problem with getting the Nook to load the CWM microsd card. It just won't start when the microsd card is in. As soon as I pull out the microsd, it starts without any problems.
I tried formatting the CWM microsd card and copying CWM again, but it hasn't changed anything.
I have a Nook 16GB. Should I try the card out on that Nook?
A couple of issues that I noticed through the process:
(1) CWM file is supposed to contain 4 files? However, part C., step 7 says "Copy all 5 items in the “CWM” folder (from item B.3 above) to the window of the new SDCard" Is this just a typo? Or is there a missing file?
(2) In Part C, step 4, after the flags have been selected, there is supposed to be a green checkmark. I see a check mark grayed out. It never goes green. (Click on the green checkmark (in the upper section of the GParted window) to execute & allow GParted to complete the action)
(3) Its not really clear to me how I am supposed to boot the nook so that it will boot off the microsd card. I understand that I am not supposed to insert the card while the nook is on because the nook will mount and write data. I have seen a couple of different versions for booting: (1) just insert the card, press power, and let it boot; or (2) hold down the power button and the N button, let go when the N on the screen goes away, and then let it boot
Sources:
thedustyblog
/2012/02/how-to-root-your-nook-tablet/
Step 4 reads: Turn your NOOK Tablet on. Put in the ROOT microSD card you created in Step 3 into the NOOK Tablet. Turn the Tablet off. When it’s completely off, hold the power button and the N button at the same time. Keep holding it. This is the N button: You should see the usual NOOK boot screen with the grey N in the middle of the screen. Keep holding the power and N button. When that grey N flashes off the screen you can let go. The NOOK Tablet should be off again because you were holding the power button. Turn the NOOK Tablet on. After a moment you should see a white screen with a cardboard box on it. When it finishes you’ll see a screen that says CWM-based Recovery.
Not having gotten any feedback, I decided to go for it and tried it on my 16GB nook tablet. Worked like a charm. Not a single speedbump. Maybe there is something wrong with the 8GB nook. I tried different sd cards, etc. No luck on the 8GB device.
Related
Last night my touchscreen went down and since I am a noob I have no idea what to do. Went through some threads briefly, but need to head out for work and was wondering if anyone here knows what I can do. The touchscreen and the frame buttons are all down.
Does anyone have any ideas?
Also, this gtab has not been modded in any way.
You may have to remove the bottom and press the soft reset button.
How do you take the bottom off? Will that void the warranty?
Talked to Viewsonic and they said if the screen is not working then there is basically nothing they can do. Returning it is really the only option, be it to the store or them.
Asked about a reset and they said I could take the back off and the battery, but that it would void the warranty.
Any more ideas?
99 % sure this will fix your problem
Here is a link to a post that I think will solve your problem.
Viewsonic told me there was no fix for the screen problem but this process fixed
the same problem on my G Tablet. Viewsonic told me to send in for repair.
This fixed my screen and I did not have to open the tablet.
Let me know if you have questions about this.
When you boot this up to do the calibration, place the G Tablet flat on a table and once you turn it on, don't touch the Tablet or the Screen until after it boots.
Go back and remove the file once you have completed calibration.
You may need to have or go buy a micro SD card if you do this from sd2. Mine cost about $12.00 at Office Max.
Read this thread: http://forum.xda-developers.com/showthread.php?t=882577
Try This
This is a cut and paste from page 7 of the link I gave you in my message above.
Here is another way to do this.
1. put microsd card in Gtab
2. open ES File Manager
3. open your sdcard2 folder
4. hit menu button on tablet
5. select add new from menu option
6. select new file
7. type in "calibration.ini" with out quotes in file name.
8. reboot and enjoy new touchscreen sensitivity.
Or if your screen won't respond at all (like mine was), put your Micro SD card in its carrier and put it in an SD card reader port on your PC.
Use notepad to create an empty file called calibration.ini (make sure Windows does not add the .txt extension to your file) and save it to the root directory of the SD card.
Power down and pop the SD card into SD card2 slot on the G Tablet (behind the door on the side).
Power up the G Tablet and don't touch the Tablet or Screen again until after it boots. Power back down and pop the SD card out and remove the file or rename it.
Your screen (and almost everyone else with the same problem) should now work.
If the G Tablet finds an empty calibration.ini file in the root directory of the SD2 card, it automatically runs its calibration. Once you run the calibration you need to delete the file or rename it so it does not run again.
You do not want it to recalibrate everytime you turn on the G Tablet because as you handle the screen during boot up it could mess up your screen calibration. That is why you must not touch the screen while doing this calibration.
Good Luck, I hope this solves your problem. Also, thanks to everyone who helped me when mine did this same thing.
Did you ever get the touch screen working?
Just curious, did you ever get your touch screen working?
I put my 32 GB microSD card through a ****load of tests on my desktop to ensure it works (http://www.iozone.org/ FYI, increase to like 30 GB and let it run all night on your desktop). It passed with flying colors, not one skip. I did this because Newegg reported a bunch of QA issues with the 32 GB microSD cards. I wanted to ensure my Wintech card was working flawlessly. It was in my PC.
When I got it in my HTC Arrive WP7, upon the first few videos syncing to the device, Zune reported that my device has stopped responding. It did this a few times after connecting and disconnecting. It even reported a write error at one point. Bad sign...
Then, as I was using the phone, it seem to have 'delays' from starting applications. "delays" from accepting things I click on, before taking action. "Delays" when hitting the back or start button. All of these delays showing a "black screen" for like a full second. Nothing like the rock-solid smoothness I experienced with the phone stock. Something was a miss, and that annoyed me enought o investigate. Reminded me of my HTC Android device (oh *snap*).
What I ended up doing was doing another hard reset, but still had the issues - even before the syncing. There is another option to do a hard reset at the initial bootup. So that's what I was attempting, and here is where I found Calculate CRC Checksum!
Inline Pictures are from this thread
1. With the device powered off: Press the power button and quickly press-n-hold both VOL UP and DOWN volume keys. You will be prompted with a white screen and writing.
2. Go ahead and press VOL DOWN to restore to factory defaults.
3. Let it cycle and press-n-hold VOL UP and DOWN again to get back. Back at the white screen again, press VolUp this time.
This forces a Calculate CRC Checksum to begin. This takes like 30s or a minute or something. Wait until it is done, it will tell you witha benign message of some sort.
EDIT: Turns out, I still have issues with random reboots.
After a lot of research, I've found that you cannot get the fastest "Class 10" kind of cards. That actually ends up hurting you because manufacturers end up sacrificing random access times in order to get the faster read/write.
With our WP7, it's all about how fast you can find the data - not how fast you can read the data.
I've now ordered a Sandisk 32 GB Class 4, as sandisk seems to be the gold standard - and the OEM card is a Sandish 16 GB Class 4.
I'm experiencing exactly the same issues with an SD-Card from Toshiba (Class 4).
Please let us know if it works with the SanDisk Card.
JoelWP7 said:
I'm experiencing exactly the same issues with an SD-Card from Toshiba (Class 4).
Please let us know if it works with the SanDisk Card.
Click to expand...
Click to collapse
I will let you know!
A few years back I purchased a Flytouch II / Superpad. Installed several custom roms and had no issues. It sat in my parts box for a while and I figured I drag it out and see what I could use it for.
Initially it booted fine (running Tim6...I think) once it was up and running it started lagging and would not respond (Screen got too hot and it stopped seeing my touches)
One of the icons on the screen was a shutdown script pre-loaded. Apparently it had pressed this, the script popped up and I tried to hit close before it shutdown, The script closed and after a little more playing I shut it off by holding the power button down, then sliding the power off slider that came up.
The next day I went to power it up and it just freezes on the android logo screen. No bootanimation, nothing.
Since I'm not shy about taking stuff apart it carefully took it apart and removed the internal sd card (4gb) and made a backup of it using dd. I then loaded an sdcard v4 image I found online, it still just hangs at the green android screen.
Also tried several "brick fixes" here on xda.
If I boot it without an sdcard it says "No Card in Machine!!!" so I think the systems is ok hardware wise.
Any ideas of other steps to take?
Got it figured out. Feel kind of silly.
Just needed to format both cards to fat32 and add the two files from tim6a back to the external card. It booted, reflashed and away it went.
Phew, thought I was going to have to rig up a touchscreen for my computer
One of the first things I did on buying my new Galaxy Tab 2 7" (GT-P3100, Wi-Fi and 3G; Spanish market "PHE" identifier, came with ICS 4.0.3, no updates available either through Kies nor OTA) was to encrypt the Device. It worked.
Then I rooted the device with CF-Auto-Root, which had the side effect of performing a factory reset, and as I understand it from a brief conversation with the author of (the excellent!) CF-Auto-Root this was an expected side-effect of the device having been encrypted at the time of applying CF-Auto-Root.
So, the Tab 2 is back to un-encrypted.
Here are the details:
Android 4.0.3
Baseband version 3.0.8-CL448962-user [email protected] #1
Build number IML74K.P3100XWALD2
But now I'm trying to encrypt again (either/both the SD Card and the Device itself) and I'm having no success at all.
On trying to encrypt the SD card, each time it always returns "SD Card Encryption Error" within a few seconds. (And indeed thereafter I always get a Notification about "SD card encryption error" any time the SD card is mounted by the device). If I go back to Settings -> Security -> Encrypt SD card and select to decrypt the card (even though it's not really encrypted), then I can access the SD Card again - no damage was done (and no encryption either).
If I try to encrypt the Device, I get the black background with the large green outline android, and ... nothing. The green android on the black background just stays there. After the normal screen timeout, the screen goes completely blank; I tap the power button, get the usual unlock screen, unlock it, see the green android again ... and, nothing. If I rotate the tablet, the android rotates. If I tap the power switch, I get the silent/ flightmode/ reboot/ turnoff menu. But nothing will get me back to the normal user interface, and it never finishes encrypting (I really think it never starts).
Eventually (after more than a couple of hours) I give up, tap the power switch and select to reboot, and it comes back up fine, but not encrypted.
One of my main reasons for getting the newer device was to have encryption :-/
Is Encryption (Device, and SD Card) supported/ functional when CF-Auto-Root is in use on a Samsung Galaxy Tab 2 (Android 4.0.3)?
How do I get encryption to work, for both the Device and the SD Card?
Is there a way to get more detailed logging (the Tab is rooted, and I have command line access) and/or to command the encryption from the command line, to see what's really happening?
Thanks!
Hm, I tried encrypting only NEW files on the SD Card now, and that seems to work.
I stored a new file on the SD Card, unmounted the card from the Tab, put the card in a card reader on a desktop computer, and indeed the contents of that file are just "data", not readable. Back in the Tab, the contents are the picture which I'd saved to the card.
But still attempting to encrypt the existing files on the SD Card fails. And still attempting to encrypt the device does nothing (green android appears, but no % complete ever displays, etc, just as I posted before).
One step further with the external SD Card; I copied off all of the data, formatted the card, and then was able to fully encrypt it (and copy back my data).
But the Device itself, I still can't encrypt at all - just the same as before.
No ideas? None? Nobody? Please....?
Thanks,
-Jay
Bump?
sigh
Try the same thing with the device itself.
Do a factory reset.
Not once,twice.
I know u lose all data.
But try it.
And do this without android to start.
Keep press power+vol up.
Get into menu and do factory reset,wipe dalwik...all.
Hope this help.
libove said:
If I try to encrypt the Device, I get the black background with the large green outline android, and ... nothing. The green android on the black background just stays there. After the normal screen timeout, the screen goes completely blank; I tap the power button, get the usual unlock screen, unlock it, see the green android again ... and, nothing. If I rotate the tablet, the android rotates. If I tap the power switch, I get the silent/ flightmode/ reboot/ turnoff menu. But nothing will get me back to the normal user interface, and it never finishes encrypting (I really think it never starts).
Eventually (after more than a couple of hours) I give up, tap the power switch and select to reboot, and it comes back up fine, but not encrypted.
Thanks!
Click to expand...
Click to collapse
Did u solve the problem?
i have the same problem
MasterBrush said:
Did u solve the problem?
i have the same problem
Click to expand...
Click to collapse
This was over a year ago, and I don't even use the device anymore. Sorry, can't help.
I've since then tried a ZTE "Skate Pro" (the Movistar Spain branding of the "Blade III"). Piece of Sh*t phone. Support encryption natively under Android 4.0.4, but if you do encrypt the phone, the performance of the touch screen becomes unreliable, frequently so bad that swiping (including Swyping) actions don't work right, and you end up less moving things on the screen and more, effectively, tapping things you absolutely did not intended to tap. I discarded the ZTE Skate Pro/ Blade III.
Then I tried a Haier W708, dirt cheap; not a powerhouse, but satisfatory.
And a Nexus 5 which kicks *ss all over the place.
I can't help any more with this thread, and any results in this thread would not longer help me, so I'm dropping off the thread now.
Best of luck to all.
Hello everyone!
Yesterday I powered off my Moto G3 and plugged it in to charge. After a few minutes I heard a short vibration, which normally means that the phone powered on by itself and is booting. I then checked the screen; I had to put in the PIN for my SIM card, but afterwards there was no pattern I had to draw in order to unlock the phone (I had one set up before!). After unlocking the screen I can see a blue screen with "Welcome" at the top, a choice of language and a yellow arrow ("next") button in the middle and "Emergency" call button at the bottom. And in the top right hand corner are the usual signal strength and battery icons.
When I press the yellow button, I'm asked to connect to a Wi-Fi network. I haven't proceeded beyond that point, as I don't want to mess up my phone even further. Basically it looks like my Moto G3 returned to factory settings and wants me to set it up for first use.
I then tried to reboot the phone a few times. I always get the standard Motorola "stitching" animation and get booted into the described screen. I also went into recovery mode, but almost every single option booted me into the blue screen and one time I got the "No command" screen. But maybe I did something wrong; I'm certainly no expert when it comes to using the bootloader.
Having described all of that, my questions are: is it possible for the phone to have reverted itself to factory settings? If yes - why and how? I have an SD card with a lot of photos, documents and application data that is very important to me. Is it still possible to retrieve the data that was saved on the device?
I would very much appreciate any help with this problem!
Thank you,
Meletel
You can copy the contents of the SDCARD while in TWRP.
1. Put MicroSD card and copy the contents of Internal Storage to microsd though TWRP File manager
2. Connect your phone to your computer by USB Cable while in TWRP and you can access your phone through MTP