[HOWTO]Root Your Nook With Your Android Phone - Nook Color Android Development

So as many of you know, to root the Nook Color (NC) you need all of the following:
1) An external sdcard (micro sdcard to be exact--shorthand uSd)
2) An uSd reader/writer
Now many of you should have uSD's lying around like I do. And many of you should have Android phones also (I mean, you're in the xda forums...is that so hard to presume?). Now what a lot of you might lack (like me) is an uSD card reader. Being the cheap person you (and I) are, you decide to look for other ways to root the NC without having to buy an uSD reader.
My Solution: Use your android phone!
Android is based off of linux and if you paid attention, there are instructions on how to flash the Auto Nooter image with linux.
So how's it done you might ask? Heres the procedure (Make sure you thank johnnyb138, he knew all along how to do this, I'm just writting it up!)
Note: This method requires ADB to be set up and the phone to be rooted also.
1) Put in uSD into phone
2) Go to Setting->SD and Phone Storage->Unmount External SD
3) Format External SD (This will wipe everything in it)
4) Mount the External SD
5) Go to Settings->Applications->Development->USB debugging (make sure its checked)
6) Now open up your terminal/command prompt and type in "adb devices" to check if ADB recognizes your phone. If not please refer to a thread/website that will guide you in the right direction
7)Now is a good time to copy the rooting img of choice: type in the following to the terminal "adb push (Location of rooting img on computer) /sdcard/*name of rooting img*"
8)a)now type in the following: "adb shell" |Now unlock the phone and make sure the screen is on when you type in the next command|
8)b)Type in: "su" |Now look at the phone and click on allow|
*Tricky Part* Once again thank johnnyb138 for this
9) type in: cd /dev/block
10) type in: ls
This command is going to list everything that is connected to the motherboard on the phone, including the external sd card.
Now you have to find which of these blocks is the one that corresponds with the external sd card. it should start with mmcblk and then end with a # eg: mmcblk1
11) Now check which mmcblk is the external sd by typing "fdisk -l mmcblk#"Try each one out.
This command will tell you the size of the drive. So if you have an 8gb sd in the phone and mmcblk2 is is 8gb in size. Bingo you got it. Watch out though cause you might have a card that is the same size as the internal memory/internal sd card. In that case, post a pic of the command prompt/terminal and we will tell you which one is the correct one
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
*Tricky Part done*
12)now that you figured out the correct block the rest is easy: dd if= (Location of rooting img eg:/sdcard/auto-nooter-2.12.25.img) of=/dev/block/mmcblk# (you figured out in step 11 which was the right #)
13) Done! Just take out the sdcard. Make sure you don't mount it before you do take it out (ie: don't unplug the usb until you took out the card!)
Well i tried to keep this as simple as possible. It really is not hard to do, its just a little hard to comprehend if you never touched a terminal/command prompt or if you never used linux. If you have any suggestions as to make this more clearer please don't hesitate!
Credit List:
johnnyb138 <- Just give him a good pat on the back!

You may get better feedback in the nook dev forum than in general. But hopefully this can work!

Thank you! I will ask the mod to move this thread.

SprintFun said:
You may get better feedback in the nook dev forum than in general. But hopefully this can work!
Click to expand...
Click to collapse
I actually did this to root my nook color. I did method two and it worked great.
I had originally tried to just do the dd command directly on my linux box with the sd card mounted but it would not work. The card would write and have all of the data on it, but the nook would not boot it. Only when I opened ADB on the linux machine and ran all of the commands directly on the android device was I able to get the nook to boot it and it worked flawlessly!

johnnyb138 said:
I actually did this to root my nook color. I did method two and it worked great.
Click to expand...
Click to collapse
That's awesome. At least we have a confirmation. Now can you tell me what img did you use? I tried auto nooter 12.15, 12.18 and 12.25 and my nook never took them. Im getting tired of trying to get it to take but I won't give up until it works

tytdfn said:
So as many of you know, to root the Nook Color (NC) you need all of the following:
1) An external sdcard (micro sdcard to be exact--shorthand uSd)
2) An uSd reader/writer
Now many of you should have uSD's lying around like I do. And many of you should have Android phones also (I mean, you're in the xda forums...is that so hard to presume?). Now what a lot of you might lack (like me) is an uSD card reader. Being the cheap person you (and I) are, you decide to look for other ways to root the NC without having to buy an uSD reader.
My Solution: Use your android phone!
Android is based off of linux and if you paid attention, there are instructions on how to flash the Auto Nooter image with linux.
So how's it done you might ask? Well here's the deal. See that [WIP] up there in the title of the thread? It stands for Work In Progress. I have succesfully (at least thats what i think) flashed the SD with multiple images but for some reason the nook won't take it. Hence it's a [WIP] because I cannot confirmed if it worked because of my lack of sd card reader.
So now I request some help. Please take the time to answer the following questions:
1) after the image is succesfully flashed, can you tell me what the contents are? and what amount of the sd is free and what amount is there in total
See picture in the bottom of what the result of my flash is.
Now for the procedure to flash the sd with the phone.
Pre Procedure:
1) Put in uSD into phone
2) Go to Setting->SD and Phone Storage->Unmount External SD
3) Format External SD (This will wipe everything in it)
4) Mount the External SD
Method 1: (Easiest) (Windows)
5) Now set the phone to act as USB storage when plugged into a computer (Varies with phone)
6) Now go to My Computer
7) You should see the card, Now just open up Win image or what ever you're using and flash the card
8) Eject the phone from the computer (Varies with phone)
9) Viola! A uSD ready to root your NC (hopefully)
Method 2: (Medium) (Windows/Linux) (ADB required to interact with phone)
5) Go to Settings->Applications->Development->USB debugging (make sure its checked)
6) Now open up your terminal/command prompt and type in "adb devices" to check if ADB recognizes your phone. If not please refer to a thread/website that will guide you in the right direction
7)Now is a good time to copy the rooting img of choice adb push (Location of rooting img) /sdcard/*name of rooting img*
8)now type in the following:
a) adb shell
b) mount
9) Here you will see all the mounted partitions. Find where your external sd card is mounted. it should start with /dev/block (for example[refer to the picture below]: mine is mounted at /dev/block/vold/179:9)
10) Now (on your phone) go to Settings->SD card and Phone Storage->Unmount External SD
11) dd if= /sdcard/*name of rooting img* of=(Mount Point) eg:/dev/block/vold/179:9
Method 3: Hardest (I don't know if root(on phone) is required for this will check tomorrow I'm very tired now (it's 1 AM here))
5) Go to the market and download the Terminal Emulator app.
6) Copy the rooting img to the sdcard of the phone
7) Open the Terminal Emulator and type in:
a) mount
8) Here you will see all the mounted partitions. Find where your external sd card is mounted. it should start with /dev/block (for example[refer to the picture below]: mine is mounted at /dev/block/vold/179:9)
9) Now (on your phone) go to Settings->SD card and Phone Storage->Unmount External SD
10) Open the Terminal Emulator and type in:
a) dd if= /sdcard/*name of rooting img* of=(Mount Point) eg:/dev/block/vold/179:9
Thats all i have to say about that....I will clean this up tomorro and hopefully shed some light on this subject. Maybe we can expand the number of rooted NC's by working together
Click to expand...
Click to collapse
From your image it looks like you may be mounting the partition of the drive rather than the actual raw drive. In my scenario, the locations of the actual sd drive was /dev/block/mmcblk1 . In the attached image I ran the commands for the internal drive, which was located at /dev/block/mmcblk0 since my external was not around. I verified which was which orignally by running
Code:
fdisk -l /mmc/block/mmcblk0
to print out the partition data of the drive. Thankfully, my external drive and my internal drive were of different sizes so each one was easy to identify.
Once you know which drive you are writing to (be sure!!!) change this line to match correctly:
Code:
dd if= /sdcard/*name of rooting img* of=(Mount Point) eg:/dev/block/mmcblk1
Hope this helps.

tytdfn said:
That's awesome. At least we have a confirmation. Now can you tell me what img did you use? I tried auto nooter 12.15, 12.18 and 12.25 and my nook never took them. Im getting tired of trying to get it to take but I won't give up until it works
Click to expand...
Click to collapse
I used 12.25 and it worked great, see my above post for a slight modification to what you did for method two that I picked up on.

Also, root is required on the phone to run both the fdisk command I listed and the dd command to write the image to the sdcard from the phone. So, it will be required for any of the above methods regardless.

johnnyb138 said:
From your image it looks like you may be mounting the partition of the drive rather than the actual raw drive. In my scenario, the locations of the actual sd drive was /dev/block/mmcblk1 . In the attached image I ran the commands for the internal drive, which was located at /dev/block/mmcblk0 since my external was not around.
Click to expand...
Click to collapse
Ahh i see now that would make more sense. I was wondering why it was mounted on /dev/vold but initially i brushed it off because in the Galaxy S lines there are a lot of leaked firmwares and thus lots of hacked ways to get around bugs, for example, sdcards not mounting.
And yes i realized this morning root was needed to dd. It's a habit to type in su as the first command right after i adb shell XD. Im trying it out now. The sd successfully flashed and im waiting for the NC. Will update in a bit.
UPDATE: Lol Omg shame!!!!! found the card at mmcblk1p1 flashed it and tried it again but alas that again was the partition...dd-ing again. The actual drive is at mmcblk1

So does method 1 not work and you have to use 2 or 3?

Bobb_o said:
So does method 1 not work and you have to use 2 or 3?
Click to expand...
Click to collapse
Im gonna write up a new method right now.

tytdfn said:
Im gonna write up a new method right now.
Click to expand...
Click to collapse
Just wanted to let you know I tried rooting with method one and it worked fine.
I have an Incredible (Rooted with custom ROM) and used Win32Image

Bobb_o said:
Just wanted to let you know I tried rooting with method one and it worked fine.
I have an Incredible (Rooted with custom ROM) and used Win32Image
Click to expand...
Click to collapse
Ok so now i will put that method back into the first post. I thought it wouldn't work but i was wrong.
Sent from my LogicPD Zoom2 using XDA App

Help...I used a 16GB microSD card on this and after that now it's only read as 39MB...how can I revert that?

lazinase said:
Help...I used a 16GB microSD card on this and after that now it's only read as 39MB...how can I revert that?
Click to expand...
Click to collapse
Format the SD card. I used my Incredible to do it.

I tried your method on using my Nexus one, unfortunately no luck.

I used windows mobile OS from my HD2 as a sdCard reader and rooted my nook color successfully. Just simply plug in and select USB Storage mode.
I wouldn't try it with HD2 running Android though...might not work.

christiankk said:
I tried your method on using my Nexus one, unfortunately no luck.
Click to expand...
Click to collapse
Where was you external sdcard mounted?

tytdfn said:
Where was you external sdcard mounted?
Click to expand...
Click to collapse
In the phone - /dev/block/mmcblk0 (free from memory)
I downloaded the image to /sdcard, extracted it on the phone and executed the 'dd' command.
Switched off the NC, plugged in the uSD card and plugged in the USB cable.
The color on the cable changes once, but the screen on the NC remains black.
Am I getting the wrong end of the stick here somehow?
PS: Thanks for your help and for posting this guide.

christiankk said:
In the phone - /dev/block/mmcblk0 (free from memory)
I downloaded the image to /sdcard, extracted it on the phone and executed the 'dd' command.
Switched off the NC, plugged in the uSD card and plugged in the USB cable.
The color on the cable changes once, but the screen on the NC remains black.
Am I getting the wrong end of the stick here somehow?
PS: Thanks for your help and for posting this guide.
Click to expand...
Click to collapse
Ok sorry for replying so late but yeah you're doing it right. the screen should be black instead of the "touch the future of something blah blah". Just leave it there for like 5 min and come back. If it doesn't work take of the sdcard or else the NC will try to boot it again

Related

[Q] bricked and can't access internal sd storage

Joining the ranks of the "what was he thinking" Had TNT4.0 lite running fine. tried to upgrade to: GtabComb_b3.1_bl1.2 hung on 3 birds. A post said "go to cwm and partition the internal sd" ...fool that I am, I did. So now it hangs on booting and there's no update.zip on the internal sd to use to restore 'cause it all got wiped by the partition. Soooo managed to get the drivers (including NVIDIA boot recovery) so that NVIDIA Harmony shows as a device on my win7 notebook, but NVIDIA's "d:" drive, while listed, is grayed out and not available.
Back to CWM tried formatting and partitioning (ignorantly screwed with the sector and swap sizes) the internal SD card, mounting and unmounting (never shows and storage space, just mount/unmount) with no access from my pc to get some recovery files on it. HELP PLEASE-
1.suggestions to get access to the internal sd card and what files to put there
2.possible to get cwm 2.5.1.1 to see either the external sd or usb as location for update.zip file
3. proper settings for the internal sd card (sector size,swap size)
4 place to get my head examined
sesteinberg said:
Had TNT4.0 lite running fine. tried to upgrade to: GtabComb_b3.1_bl1.2 hung on 3 birds.
Click to expand...
Click to collapse
So you were on a 1.1 bootloader and you decided to jump to a 1.2 bootloader-based ROM (when that ROM has a perfectly good 1.1 bootloader-based version)?
First things first: Are you able to boot into ClockworkMod?
If yes, then you can copy any files you want to either sdcard, internal or external, using adb.
To copy files to the internal SD card:
Code:
C:\some\path\platform-tools> adb shell mount /dev/block/mmcblk3p1 /sdcard
C:\some\path\platform-tools> adb push c:\some\path\file.zip /sdcard/xyz.zip
C:\some\path\platform-tools> adb shell umount /sdcard
To copy files to the external SD card:
Code:
C:\some\path\platform-tools> adb shell mount [B]/dev/block/mmcblk2p1[/B] /sdcard
C:\some\path\platform-tools> adb push c:\some\path\file.zip /sdcard/xyz.zip
C:\some\path\platform-tools> adb shell umount /sdcard
If the "adb shell mount /sdcard" at the beginning complains about /sdcard already being mounted, just unmount the sdcard as shown in the last step, then start over again.
If you have inadvertently loaded a 1.2 bootloader, downgrade to 1.1 by following the steps given here.
After this, remove any external SD cards you may have so that there is no confusion when you format the SD card, then:
1. Reflash clockworkmod if needed, then boot into CWM.
2. Repartition internal SD card again with 2048 MB for /data and 0 for swap (no swap) and the rest for /sdcard.
3. Do a "wipe data/factory reset".
4. Use adb push to copy the GtabComb_b3.1_bl1.1.zip file onto the internal SD card using the commands above.
5. Install this zip file using CWM.
thank you very much for your help- i'm not experienced enough to know how to run adb...see below and thanks again
So you were on a 1.1 bootloader and you decided to jump to a 1.2 bootloader-based ROM (when that ROM has a perfectly good 1.1 bootloader-based version)? ***yes- saw a post that said that if the opening screen showed the slide lock, that bootloader was 1.2...go figure****
First things first: Are you able to boot into ClockworkMod? *yes**
If yes, then you can copy any files you want to either sdcard, internal or external, using adb. **can you help me understand how to do this- downloaded the java sdk; and the android sdk, but haven't been able to find out how to use them to move the files to the internal sd card....haven't figured out how to use adb***
To copy files to the internal SD card: ***I'm sorry, i don't understand the steps to do this...been looking on line so as not to bug you****
Code:
C:\some\path\platform-tools> adb shell mount /dev/block/mmcblk3p1 /sdcard
C:\some\path\platform-tools> adb push c:\some\path\file.zip /sdcard/xyz.zip
C:\some\path\platform-tools> adb shell umount /sdcard
To copy files to the external SD card:
Code:
C:\some\path\platform-tools> adb shell mount /dev/block/mmcblk2p1 /sdcard
C:\some\path\platform-tools> adb push c:\some\path\file.zip /sdcard/xyz.zip
C:\some\path\platform-tools> adb shell umount /sdcard
If the "adb shell mount /sdcard" at the beginning complains about /sdcard already being mounted, just unmount the sdcard as shown in the last step, then start over again.
If you have inadvertently loaded a 1.2 bootloader, downgrade to 1.1 by following the steps given here. ***how would I know this?***
After this, remove any external SD cards you may have so that there is no confusion when you format the SD card, then:
1. Reflash clockworkmod if needed, then boot into CWM.
2. Repartition internal SD card again with 2048 MB for /data and 0 for swap (no swap) and the rest for /sdcard. **done***
3. Do a "wipe data/factory reset". **done***
4. Use adb push to copy the GtabComb_b3.1_bl1.1.zip file onto the internal SD card using the commands above. **same problem as above**
5. Install this zip file using CWM.
sesteinberg said:
***yes- saw a post that said that if the opening screen showed the slide lock, that bootloader was 1.2...go figure****
Click to expand...
Click to collapse
OK, this is very important. In your first post, you said you, "Had TNT4.0 lite running fine." TnT Lite 4.0 is a 1.1-based custom firmware. Which is why I thought you were on a 1.1 based firmware. Are you in fact running ViewSonic's new stock firmware with the TapNTap UI?
***how would I know this?***
Click to expand...
Click to collapse
Read this thread. As the first post there says:
So, to check which branch you are on if you are on STOCK: Go to Settings -- About Tablet -- Tapu UI Version. If your firmware starts with "1.1", then you are on the 1.1 (old) branch. If your firmware starts with "1.2", then you are on the 1.2 (new) branch. Also an obvious difference between the two is that the 1.2 branch adds a lockscreen to the tablet.
Click to expand...
Click to collapse
TnT Lite is very close to stock, so you can, I think, still go to Settings > About Tablet > TapUI Version and check the firmware version which indicates the bootloader being used.
If, however, you find out that you do, in fact, have a 1.2 bootloader, then just flash the file you originally used: GtabComb_b3.1_bl1.2.zip. By reformatting the internal SD card and doing a factory reset, you've done all that's needed to prepare for a new ROM install.
**can you help me understand how to do this- downloaded the java sdk; and the android sdk, but haven't been able to find out how to use them to move the files to the internal sd card....haven't figured out how to use adb***
Click to expand...
Click to collapse
To set up adb on Windows, see this thread.
For quick one-shot use, follow the instructions here, and just replace the "adb" in the commands I gave with "sudo ./adb".
***Bought the tablet early this year, rooted it and installed a new rom tnt lite v 4.1.1 or 4.2.1 (i'm travelling and don't have the download--not viewsonic stock); I looked at the settings before this fiasco and did not see a 1.1 or 1.2 (because it was not longer stock?)- that's why I relied on the opening screen with the slide lock to (falsely?) conclude it was 1.2.
***on start-up the tablet loops at 3 birds--so I can no longer get to g-tab settings; I can reliably get to ClockworkMod Recovery v2.5.1.1-bekit-0.8- I did use it to "reset" the internal sd by partitioning it and using 2048mb and 0 for swap-no messages to suggest the internal sd was faulty**
***when I first flashed GtabComb_b3.1_bl1.2- it hung at 3 birds but I was able to revert to the tnt 4xxx by using CWM to select it on the internal SD card; when I flashed GtabComb_b3.1_bl1.2 the second time it hung again I found a posting on line that suggested re-partitioning the internal SD card which of course did not resolve the problem and took away my CWM restore possibilities***
***i've just finished downloading Knoppix with the hope of using it to run Adb to get access to the internal SD card---I do have NVIDIA Harmony as a "device" in win7-but the "d:" drive on it is grayed out and not browsable ***
this help you help me?
thanks again
sesteinberg said:
***Bought the tablet early this year, rooted it and installed a new rom tnt lite v 4.1.1 or 4.2.1 (i'm travelling and don't have the download--not viewsonic stock);
...
I can reliably get to ClockworkMod Recovery v2.5.1.1-bekit-0.8
Click to expand...
Click to collapse
The fact that you remember installing TnT Lite 4.x and also have CWM v2.5.1.1-bekit-0.8 working strongly suggests to me that your bootloader is 1.1.
I do have NVIDIA Harmony as a "device" in win7-but the "d:" drive on it is grayed out and not browsable ***
Click to expand...
Click to collapse
It might not show up as a USB disk, but, you should still be able to use adb on Windows. I'm not a Windows user--don't even have it on my PC--but, try this:
In CWM, select "mounts and storage", then "mount USB storage". See if the external SD card shows up as a drive on Windows.
EDIT:
If you don't have an external SD card, you can make the internal SD card's VFAT partition appear as a drive on Windows/Linux by using these adb commands:
1. Create a new file called fstab.txt with these contents:
Code:
/dev/block/mtdblock4 /cache yaffs2 rw
/dev/block/mmcblk3p2 /data ext3 rw
/dev/block/mtdblock3 /system yaffs2 rw
/dev/block/mmcblk3p1 /sdcard vfat rw
/dev/block/mmcblk2p2 /sd-ext auto rw
2. Copy this fstab.txt onto the gTablet using adb:
Code:
C:\> adb push C:\some\path\fstab.txt [B]/etc/fstab[/B]
3. On gTablet, create a symbolic link (it's like a shortcut) from /dev/block/mmcblk3p1 to /dev/block/mmcblk2p1, which is what CWM is trying to mount:
Code:
C:\> adb shell ln -sf /dev/block/mmcblk3p1 /dev/block/mmcblk2p1
4. Back in the CWM main menu, select "mounts and storage", then "mount USB storage".
I am having a similar issue with my G Tablet.
After farting around with it the other day I lost track of what I was doing and now at start up it just sits with the three birds image and does nothing.
When I try to boot into recovery I get:
"Detect a recovery key pressed"
followed by
"Booting recovery kernel image"
Then it just sits there.
So I searched all over for solutions and found the nvflash threads. I downloaded all the files needed but my PC's just won't detect the tablet and therefore I can't install the drivers for it.
I have two Win 7 machines, on 32 and on 64 . Both do the same.
What should I be doing next ? Any ideas ?
tried the various mounting options- internal sd mounts but makes no difference in terms of being visible on my PC; external sd (with memory card inserted) gives an error message; usb storage mount- no apparent effect
burning knopp disk now- and will try to get adb to allow commuication with tab...any tricks?
Frogbone said:
I downloaded all the files needed but my PC's just won't detect the tablet and therefore I can't install the drivers for it.
Click to expand...
Click to collapse
Is the USB cable OK?
What should I be doing next ? Any ideas?
Click to expand...
Click to collapse
Google "Viewsonic GTablet For Dummies" and follow the Code RED instructions there.
sesteinberg said:
tried the various mounting options- internal sd mounts but makes no difference in terms of being visible on my PC;
Click to expand...
Click to collapse
Did you try the adb push ... method? That should've worked without mounting anything.
external sd (with memory card inserted) gives an error message; usb storage mount- no apparent effect
Click to expand...
Click to collapse
That's no good. Need exact steps/commands tried and exact error messages returned.
burning knopp disk now- and will try to get adb to allow commuication with tab...any tricks?
Click to expand...
Click to collapse
If all else fails, Google "Viewsonic GTablet For Dummies" and follow the Code RED instructions on that site.
rajeevvp said:
Google "Viewsonic GTablet For Dummies" and follow the Code RED instructions there.
Click to expand...
Click to collapse
This ^^^^
I must have missed the Power plus Volume- to get to APX mode in all of the other procedures I read.
Thanks for pointing out this great site !!
Frogbone said:
Thanks for pointing out this great site !!
Click to expand...
Click to collapse
It is the distilled wisdom of the xda-developers gTablet forum in one place.
Consider making a donation to keep that site up.
Back home and at this again- went to "Dummies" "code red"
downloaded the USB driver (had done this previously through SDK tools) and while I don't get any error messages when connecting the g-tablet; Device manager shows only a "Android Debug Bridge Interface" working ok and drive up to date. below is from the code red instructions:
Using your PC, download the driver for USB connector here (clicky). Alternate source driver for USB connector. ***done***
Unzip the SystemUSB.zip file and place the folder "Flash USB driver" somewhere easy for you to find. I suggest your desktop. ***done***
Turn on your gtab by pressing the power button and volume less (-) button simultaneously and hold. Your screen will turn on with the 3 viewsonic birds and then it will turn black. Looks like it is off, but I promise you it is on in APX mode. ***As I mentioned before, I have CWM which reliably starts on holding the power button and the volume (-) button- I was able to get to a state (using the "menu" key) where the device is clearly on- black screen, but backlighting obvious.... is this APX mode?***
Do not click here.
Connect your gtab to your computer via usb. Your computer will say driver install unsucessful. ****doesn't happen...did before I installed the USB driver from the SDK****
Right click on Computer icon --> Properties --> Device Manager (left side) --> right click APX and choose upgrade driver. ***I see the Android Debug Bridge (working properly) but no APX; updated this driver with the USB driver recommended in code red- shows up to date, but still no APX reference*** Navigate to where you put the USB driver folder and select the folder. Your computer should now recognize the gtab in APX mode. ***I have no idea if this has occurred. In device manager it is listed as a "Portable device" drive d...but drive d isn't accessible....any way to confirm that the gtablet is in APX mode and that I've got the correct driver on my PC---again, no error on initial connection.
I downloaded NVFLash with CWM for 1.1 (the boot loader it seems most likely I had)- unzipped and ran it under the conditions above....ran nvflash_gtablet.bat (with CWM) --I get: "NVflash started" then "unknown device found" then "press enter to continue:" pressing "enter" closes the dos window but no activity on the pc and none on the tablet. If I run NVflash at the three birds screen on the tablet I get NVflash started and then "USB device not found" which I guess makes sense. Do I have the wrong USB driver on my PC? Am I not getting into APX mode on the tablet? Are the instruction different when Cwm is already installed -- should I have used the NVflash without CWM? thanks as ever.
The gTablet has 3 distinct modes of operation:
1. The normal mode.
Press the power button when the tablet is switched off and this is where you land. In this mode the gTab bootloader loads the linux kernel (which the firmware supplies) and this then runs the firmware you installed. This mode is where you will spend most of your time.
2. Recovery mode.
You enter this mode by first pressing the Volume [+] key, then while this key is pressed, pushing the power button. Keep the Volume [+] key depressed until you see a "Detect a recovery key pressed/Booting recovery kernel image" message.
Recovery mode will take you either into the stock recovery or into ClockworkMod recovery. This mode exists so that you can a) fix problems with your firmware, or b) install things like the firmware itself using a safe kernel, a mini-filesystem image and the CWM Recovery program.
3. APX mode.
You enter this mode by first pressing the Volume [-] key, then while this key is pressed, pushing the power button. Keep the Volume [-] key depressed until you see the blank screen right after the 3 birds boot logo has flashed by.
This is a very low-level mode which lets you recover from a "soft-brick". You should get into this mode only if CWM Recovery can't be used to fix your problems (and 90% of problems can be fixed within CWM with a bit of thinking).
In Linux you can tell which mode you're in by issuing a lsusb command:
Here's the gTab in APX mode (Volume [-] and Power):
Code:
$ [B]lsusb[/B]
Bus 002 Device 011: ID 0955:[B]7820[/B] NVidia Corp.
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 046d:c03d Logitech, Inc. M-BT96a Pilot Optical Mouse
Bus 001 Device 003: ID 0d49:7410 Maxtor Mobile Hard Disk Drive (1TB)
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Here's the other mode (both regular and recovery modes report the same device ID):
Code:
$ [B]lsusb[/B]
Bus 002 Device 013: ID 0955:[B]7100[/B] NVidia Corp.
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 046d:c03d Logitech, Inc. M-BT96a Pilot Optical Mouse
Bus 001 Device 003: ID 0d49:7410 Maxtor Mobile Hard Disk Drive (1TB)
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
From your last message it looks like you're going into Recovery mode rather than APX mode. I don't want to state the obvious here, but... look at the top of the tablet and see which key is the Volume [-] key and which is Volume [+]; then press the correct key. Many other users have made this same mistake.
BTW, did you try pushing the files you need to use (the 1.2 to 1.1 bootloader downgrade zip file and the GtabComb ROM install zip file) using adb on Linux, then installing the files after the push?
sesteinberg,
If you can get your G Tablet in APX Mode and connectect to your PC, then the steps I went through to restore a G Tablet may help you.
Guide - Restore G Tablet after a failed Recovery Mode update
djab67
THANK YOU - your description of the two modes was key- with vol- plus power the tablet showed up in windows device manager as USB recovery mode (rather than APX) BUT, in this mode the tablet was recognized by NVFlash and restored. THANK you again for your time and patience.
I am currently showing: Android 0s version 2.2 Tap UI version 1.1-3588 Kernal 2.6.32.9-00000-10.8.2-dirty [email protected] #16
Could you recommend a Rom? Will I need to root it before installing? (yes I recognize this as bootloader 1.1) worth going to android 3.0?
appreciate your expertise
Glad we could help you.
You wanted to try out GtabComb before. Beta 3.3 came out yesterday and it works pretty well--all considering. Try it out. Make sure you get the 1.1 bootloader version.
Copy the file onto the SD card, boot into CWM (Volume + and Power), then do a "wipe data / factory reset" from the menu first, and finally, install the GtabComb zip file. Note that it will take some time for the first boot--about 5 - 7 minutes--so don't panic if nothing seems to happen.
rajeevvp said:
Glad we could help you.
You wanted to try out GtabComb before. Beta 3.3 came out yesterday and it works pretty well--all considering. Try it out. Make sure you get the 1.1 bootloader version.
Copy the file onto the SD card, boot into CWM (Volume + and Power), then do a "wipe data / factory reset" from the menu first, and finally, install the GtabComb zip file. Note that it will take some time for the first boot--about 5 - 7 minutes--so don't panic if nothing seems to happen.
Click to expand...
Click to collapse
thx- does this support Flash 10.3 for Youtube and other flash video?
thank you again..
sesteinberg said:
thx- does this support Flash 10.3 for Youtube and other flash video?
Click to expand...
Click to collapse
The Flash version installed in 10.3 and flash does work. YouTube works for sure; don't know about other video sharing sites.

[Q] 1.4.3 root help

ive done every root method and still nothing can someone help
Quote:
Originally Posted by Indirect
...
1. Setup SDCard
Using a new SDCard (not one you have info stored on) make a new MSDOS partition table and add a 50 MB FAT32 partition as the first primary partition. Then make sure you enable to boot and lda flags.
Any SDCARD larger than 50 MB should work but I used an extra 2GB laying around. You can add other partitions to the card if you want, but it is not necessary to allocate the entire card. Any added partitions would need to be manually mounted on your Nook anyway.
I used GParted on my Ubuntu machine to do this but any formating tool should work.
2. Copy Files onto SDCard
You can grab the files I used here:
http://www.mediafire.com/?dr6bqau194389te
Just UnZip the files directly to the root of the boot partition you created above (make sure flashing_boot.img, u-boot.bin, and boot.img are on the root not the folder SDCARD)
3. Insert SDCARD into NT
Now, with your NT powered off, eject the SDCARD you just created from your computer and insert it into the tablet. Then just turn it on and VOLA! You should now be in CWM!
Symptoms:
With the SDcard (from above) inserted and the NT powered on, the NT shows a black screen for about 3 minutes, and then boots the internal memory.
Removing MLO from the SDcard causes normal NT internal memory booting, so clearly the NT boot process is looking at the correct place on the SDcard (note that the MLO for 1.4.0 and 1.4.1 are identical).
So, unless I am doing something really stupid, there's something different between the two NTs I've owned. Note that "bauwks" had a problem booting from the SDcard, unless he had the USB cable connected, but others have not seen that symptom.
I rooted my NT 16GB by following this post and it worked well:
http://forum.xda-developers.com/showthread.php?t=1798439
Penguin101 said:
I rooted my NT 16GB by following this post and it worked well:
http://forum.xda-developers.com/showthread.php?t=1798439
Click to expand...
Click to collapse
thamks for the rely but ive tried that already
So you wrote all the files you unzipped from the download to the sdcsrd, inserted the SD into your Nook and rebooted...do you get the box when you reboot?
Just checking, you're holding down both the power button and "n" button when powering on the tablet?
NikkieL
Sent from my Barnes & Noble Nook Tablet using xda premium
This is too complicated, really.
Just got a used NT16. Previous owner factory restored. Downloaded img file from:
[SD Root] Make 16 or 8GB Nook Tablet Root SD Cards by Albert Wertz [SDNT16or8gbV4.7]
No instructions on how to mount image to SD card for Mac (it says just google it...)
Google did not turn up a clear result.
So I finally Googled the right query: how to burn an ISO on a USB drive on Mac OS X
And in turn gave me this - how to mount the image:
"Directly from the Ubuntu download page (my formatting):
Download the desired file
Open the Terminal (in /Applications/Utilities/ or query Terminal in Spotlight)
Convert the .iso file to .img using the convert option of hdiutil (e.g., hdiutil convert -format UDRW -o ~/path/to/target.img ~/path/to/ubuntu.iso)
Note: OS X tends to put the .dmg ending on the output file automatically. Remove the .dmg extension as necessary, mv ~/path/to/target.img{.dmg,}
Run diskutil list to get the current list of devices
Insert your flash media
Run diskutil list again and determine the device node assigned to your flash media (e.g. /dev/disk2)
Run diskutil unmountDisk /dev/diskN (replace N with the disk number from the last command; in the previous example, N would be 2)
Execute sudo dd if=/path/to/downloaded.img of=/dev/rdiskN bs=1m (replace /path/to/downloaded.img with the path where the image file is located; for example, ./ubuntu.img or ./ubuntu.dmg).
Using /dev/rdisk instead of /dev/disk may be faster.
If you see the error dd: Invalid number '1m', you are using GNU dd. Use the same command but replace bs=1m with bs=1M.
If you see the error dd: /dev/diskN: Resource busy, make sure the disk is not in use. Start the 'Disk Utility.app' and unmount (don't eject) the drive.
Run diskutil eject /dev/diskN and remove your flash media when the command completes
Restart your Mac and press Alt while the Mac is restarting to choose the USB stick"
So.........
I followed the instructions to a tee. I am using a 128 MB SanDisk micro SD card.
I inserted the card in my Nook and powered it off. Put the USB cable in and after many minutes the Nook turned on. All it did was power on like normal. Once, I removed the SD card while nothing was happening (waiting for boot). Intermittently (as a result?), I was unable to turn Nook on at all, thinking it was bricked. So, I tried the SD card again, and again after several minutes it turned on. Have removed the card now and Nook works like normal again.
So, I have a 16GB Nook Tablet with 1.4.3 and would like to root it AND flash Android which may require who knows how many sd cards and various recovery modules. I would like to say I love learning how to do all of this, except these instructions are always written by developers FOR developers. Perfect example is the Bishop of Technology. One page leads to another and then another. There is no definitive answer to be found on his site. My favorite part is where he says "now take out the boot card and insert ("vague") custom ROM. And then says, now you might want to backup (using CWM). This is all on the page for installing Jellybean on 1.4.3. The whole page is a mish-mash of vagueness and redirection. That is why I tried installing directly from XDA instead.
But, like I said, I was unsuccessful. And I'm not willing to risk trial and error or spend another four hours digging around trying to find the meaning of every instruction. How hard is it to go into a bit more detail and include links every time appropriate. (insert custom ROM - this is vague and no link is shown for downloading the custom ROM.)
Should I get a 2GB sd card so I can install 142 (500MB) first?
Maybe rdisk was to fast and corrupted the image?
Maybe try this. http://forum.xda-developers.com/showthread.php?t=1494367
Sent from my Barnes & Noble Nook Tablet using Tapatalk

[Q] SD card and internal storage not mounting after running CWMR. What to do?

First off, I am very new to the world of ROMs/modding, so I apologize in advance if anything that follows misuses any terms or fails to provide proper information. Please let me know if you need me to clarify anything.
I have an Atrix 4G with AT&T running the stock 2.3.6 build 4.5.141. In light of Motorola's recent abandonment, I took it upon myself to load the stable version of CM7 onto my phone until enough of the bugs in CM10 had been worked out. I lurked XDA for a while until I got up the courage to root my phone and unlock my bootloader, at which I was successful (thanks, guys!), but I ran into a problem when I tried to use ClockworkMod Recovery to flash the ROM. After what seemed like a successful installation, I got caught in a boot loop, and had to boot to recovery mode.
Here's where I did the stupid thing: while in recovery mode, I tried several different options that I did not fully understand and somehow ended up getting it to boot back to the stock OS restored to what appear to be more or less factory settings. That's good, right? Well, now neither my phone's internal storage nor the external SD card will show up in my phone. I guess they aren't mounting? In Settings>Storage, the option to mount the SD card is grayed out and the internal storage listing is nowhere to be seen. Obviously this keeps me from accessing my recovery data, if it's even still there. My wifi also seems to not be working, displaying "error" whenever I try to turn it on in Settings.
The weird thing is that my phone's OS seems to be working fine otherwise. I can't access any file storage, but I can install apps to the app storage partition and use them just fine, as long as they don't require internal or SD storage. I am honestly confounded and I cannot find anything that resembles a solution to this problem. I am done messing with things I don't understand, so I am asking for help.
Help?
No idea what you did, but I'd say you somehow managed to bork both your storages. The easiest way to fix this is to go to CWM and format both internal and external storages. The downsize to this is obviously that you will definitely lose everything stored there. A more complicated approach would be to connect the phone to the computer and run some filesystem scanning/fixing/repairing tools and hope for the best. As for the external SD card, it would be even better if you could pull it out and put it into a card reader and connect it to the computer that way.
ravilov said:
No idea what you did, but I'd say you somehow managed to bork both your storages. The easiest way to fix this is to go to CWM and format both internal and external storages. The downsize to this is obviously that you will definitely lose everything stored there. A more complicated approach would be to connect the phone to the computer and run some filesystem scanning/fixing/repairing tools and hope for the best. As for the external SD card, it would be even better if you could pull it out and put it into a card reader and connect it to the computer that way.
Click to expand...
Click to collapse
Thank you for your reply.
I followed your advice and attempted to format /sdcard and /emmc (I believe that's internal storage) in recovery mode. I got a mount error when I tried the /sdcard, but /emmc format appeared to be successful. I then rebooted the phone, but the conditions are still the same. No internal or external SD storage. I will try to get a card reader for the micro SD card to look at it on my computer, but I am alarmed that I can't get access to my internal storage even after formatting it.
What kind of filesystem tools would I need to use while plugged into a computer? What could I do if the storages aren't mounting? Am I completely screwed?
Not sure about your phone but on my galaxy s, emmc is the external storage and sdcard is the internal.
Sent from my GT-I9000 using xda premium
NIMBAH said:
Not sure about your phone but on my galaxy s, emmc is the external storage and sdcard is the internal.
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
Oh dear. That would mean that what I can't mount is actually the internal storage. Is there any way to remedy that?
Connect the phone to the computer (enable USB transfer mode on the phone if needed) and run some windows built-in tools like scandisk, chkdsk, format...
Just one caveat - if you decide to format, make sure you select FAT32, NOT exFAT, NTFS...
ravilov said:
Connect the phone to the computer (enable USB transfer mode on the phone if needed) and run some windows built-in tools like scandisk, chkdsk, format...
Just one caveat - if you decide to format, make sure you select FAT32, NOT exFAT, NTFS...
Click to expand...
Click to collapse
Alright, I tried to connect like you said, making sure to enable USB mass storage mode. However, while the PC acknowledges that something is plugged in (installs drivers), neither storage is showing up as a drive when I try to access them with Windows Explorer. I can't do anything to them if they don't show up, or can I?
I did order a microSD card reader to try to connect the external drive to the computer that way. It should arrive sometime tomorrow. I'm thinking that if I can get the computer to read it that way that maybe I can format it so that the phone will finally be able to mount it again. Not sure what to do about the internal storage (or the broken wifi) after that, but I suspect that if I manage to flash a different ROM from external storage that I'll be able to recover that functionality? Or am I mistaken?
Hard to say. You sure have it tough there.
Try this - when the phone is connected and transfer mode selected, right click My Computer, select Manage, then go to Computer Management > Storage > Disk Management and see if anything appears there. If not... then I'm out of ideas I'm afraid.
ravilov said:
Hard to say. You sure have it tough there.
Try this - when the phone is connected and transfer mode selected, right click My Computer, select Manage, then go to Computer Management > Storage > Disk Management and see if anything appears there. If not... then I'm out of ideas I'm afraid.
Click to expand...
Click to collapse
I did what you said, and this was the result:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm not sure if that counts as nothing or not.
boohoo_sadface said:
I did what you said, and this was the result:
I'm not sure if that counts as nothing or not.
Click to expand...
Click to collapse
could you do a chkdsk of the drives?
open start, type cmd, right click and open as admin,
then type chkdsk L: (I think, resolution of screenshot is not that good)
then chkdsk F:
see if any errors pop up
jorno88 said:
could you do a chkdsk of the drives?
open start, type cmd, right click and open as admin,
then type chkdsk L: (I think, resolution of screenshot is not that good)
then chkdsk F:
see if any errors pop up
Click to expand...
Click to collapse
It's E, not L. Sorry about the resolution.
For both chkdsk commands, the message "Cannot open volume for direct access" was returned.
OK well, at least something. It's a little worrisome that it says "no media" even for internal storage.
Not sure if you had the external SD card inserted at that point, if you did, try the same thing but take the SD card out of the phone.
Also try right-clicking on one or the other, see what it offers - if you get something like "create volume" or similar, might try that.
Is it correct that one of the drives shown has about 1.46 GB (i assume your microsd) and the other has 14.37 GB?
that would seem strange to me because my internal accessible memory is only 10.71 GB, seems like system partition or something is considered with it. Maybe you have a problem with your partition table...
jorno88 said:
Is it correct that one of the drives shown has about 1.46 GB (i assume your microsd) and the other has 14.37 GB?
that would seem strange to me because my internal accessible memory is only 10.71 GB, seems like system partition or something is considered with it. Maybe you have a problem with your partition table...
Click to expand...
Click to collapse
Those are actually partitions of the PC's hard disk (C).
My internal storage should be ~8GB and the external one is a 32GB microSD card. Those would be the E and F removable drives that show up as having no media attached.
ravilov said:
OK well, at least something. It's a little worrisome that it says "no media" even for internal storage.
Not sure if you had the external SD card inserted at that point, if you did, try the same thing but take the SD card out of the phone.
Also try right-clicking on one or the other, see what it offers - if you get something like "create volume" or similar, might try that.
Click to expand...
Click to collapse
I tried again with microSD removed, and the results were exactly the same, even down to both E & F volumes both being displayed in Disk Management when the phone is connected. Chkdsk commands in the command prompt for both of these volumes also returned the exact same error message as before.
boohoo_sadface said:
I tried again with microSD removed, and the results were exactly the same, even down to both E & F volumes both being displayed in Disk Management when the phone is connected. Chkdsk commands in the command prompt for both of these volumes also returned the exact same error message as before.
Click to expand...
Click to collapse
I see.
Any potentially useful options on right-click on either?
Also try booting into fastboot and do moto-fastboot erase emmc and see what happens. (Hope you have moto-fastboot installed and ready.)
the error message for chkdsk seems to be related to another program installed on your pc, check here if it is one of these programs. If all this doesn't work (or you're tired of fiddling and trying to get back your data) you can try formatting them through cmd (FORMAT E: /FS:FAT32 and FORMAT F: /FS:FAT32)
if it all works you can use a program called recuva to try get some data back afterwards.
ravilov said:
I see.
Any potentially useful options on right-click on either?
Also try booting into fastboot and do moto-fastboot erase emmc and see what happens. (Hope you have moto-fastboot installed and ready.)
Click to expand...
Click to collapse
Here is the result:
jorno88 said:
the error message for chkdsk seems to be related to another program installed on your pc, check here if it is one of these programs. If all this doesn't work (or you're tired of fiddling and trying to get back your data) you can try formatting them through cmd (FORMAT E: /FS:FAT32 and FORMAT F: /FS:FAT32)
if it all works you can use a program called recuva to try get some data back afterwards.
Click to expand...
Click to collapse
I tried the format command, and here was the result:
So same result as before, did you look in the list of those programs? Else you can try to go into safemode with your pc and do the chkdsk or/and format command from in there.
Might be easier than uninstalling programs

[Q] Phone doesn't mount SD-Card, but I can mount it in the recovery mode

Hi,
When the (HTC Desire) phone is powered up it is unable to mount the SD card, and I am unable to have it mounted from the "Settings > SD card & Storage" menu. Having said that, the micro SD card can be accessed from a computer (when plugged in directly to the computer, i.e. no issue with the card), and moreover, when I am in the recovery mode, I can have it mounted and browse it. By the way, the card could be accessed from the phone until I downgraded the O/S, and managed to have it rooted.
When the phone is running normally, and connected to the USB port of a laptop, the laptop does recognize a device connected (can even do ADB), but I believe because the SD card is not mounted, the phone does not offer the option to make the card appear as a disk drive for computer access.
I am running the original (RUU, Telstra) Android 2.2 (2.26.841.2) on a HTC desire, after I had it "S-OFF'ed". After reloading the original 2.2, I had it rooted.
The micro SD card is a 2GB one, with approx 1.5GB formatted as FAT16 (contains typical file and photos), and 0.5 GB as EXT3 (contains nothing at the moment).
HBoot: 6.93.1002
S-Off (thanks to Revolutionary)
Recovery mode: ClockworkMod v5.0.2.0 (I manually loaded it)
I have searched online for solutions, and have not been able to have it fixed. Others seem to have different issues to that of mine. Usually, they cannot mount the SD-card at all (not even from recovery), or their SD card just needed to be reformatted. I think I have indicated that these do not appear to be relevant to my issue at all. I have also tried "Fastboot oem enableqxdm 0", and it made no difference.
I look forward to your kind responses and feedback.
Thank you for your attention.
desiremhtc said:
Hi,
When the (HTC Desire) phone is powered up it is unable to mount the SD card, and I am unable to have it mounted from the "Settings > SD card & Storage" menu. Having said that, the micro SD card can be accessed from a computer (when plugged in directly to the computer, i.e. no issue with the card), and moreover, when I am in the recovery mode, I can have it mounted and browse it. By the way, the card could be accessed from the phone until I downgraded the O/S, and managed to have it rooted.
When the phone is running normally, and connected to the USB port of a laptop, the laptop does recognize a device connected (can even do ADB), but I believe because the SD card is not mounted, the phone does not offer the option to make the card appear as a disk drive for computer access.
I am running the original (RUU, Telstra) Android 2.2 (2.26.841.2) on a HTC desire, after I had it "S-OFF'ed". After reloading the original 2.2, I had it rooted.
The micro SD card is a 2GB one, with approx 1.5GB formatted as FAT16 (contains typical file and photos), and 0.5 GB as EXT3 (contains nothing at the moment).
HBoot: 6.93.1002
S-Off (thanks to Revolutionary)
Recovery mode: ClockworkMod v5.0.2.0 (I manually loaded it)
I have searched online for solutions, and have not been able to have it fixed. Others seem to have different issues to that of mine. Usually, they cannot mount the SD-card at all (not even from recovery), or their SD card just needed to be reformatted. I think I have indicated that these do not appear to be relevant to my issue at all. I have also tried "Fastboot oem enableqxdm 0", and it made no difference.
I look forward to your kind responses and feedback.
Thank you for your attention.
Click to expand...
Click to collapse
Welcome to the forum.
I had the same problem once. The solution is very simple but annoying: Many Android phones are unable to mount SD cards formatted with tools like MiniTool Partition Wizard. Reformat the SD card using CWM (ClockWorkMod) recovery and everything will be fine.
Good luck.
It worked
nik10 said:
Welcome to the forum.
I had the same problem once. The solution is very simple but annoying: Many Android phones are unable to mount SD cards formatted with tools like MiniTool Partition Wizard. Reformat the SD card using CWM (ClockWorkMod) recovery and everything will be fine.
Good luck.
Click to expand...
Click to collapse
Dear friend,
Thank you so much for your simple tip. It worked! I felt so dumb for not trying it out myself. I guess I was tired of trying things without considering moving my data back and forth. Once more thank you.
AW: [Q] Phone doesn't mount SD-Card, but I can mount it in the recovery mode
desiremhtc said:
Dear friend,
Thank you so much for your simple tip. It worked! I felt so dumb for not trying it out myself. I guess I was tired of trying things without considering moving my data back and forth. Once more thank you.
Click to expand...
Click to collapse
Well, this IS annoying. I had the same problems and copied my data three times (~ 12 GB). So I can understand that.
Good evening,
I have also the same prroblem.
Is there any manual - instructions that I could follow in order to solve the issue with the CWM?
Thanks in advance.

[Q] Bricked?

I may have messed up the flash steps when I was trying to flash SuperNexus from Froyo? So I did the following first:
Make a Nandroid backup
Then I put those two files on the phone with the following adb commands:
adb push SuperNexus-2.0-vibrantmtd-BUILD4-update2.zip /sdcard/
adb push gapps-jb-20130301-signed.zip /sdcard/
After that I did
Do a Wipe/Factory Reset
Now I'm lost at the following step:
Flash SuperNexus ROM
On the CWM recovery interface, now when I select
install zip from sdcard
and then
choose zip from sdcard
I can't find the sdcard directory from the long list of directories such as Android, DCIM, data, external_sd, voodo, etc.! Where is sdcard?
Is it because the Nandroid backup didn't back up those two files (SuperNexus and gapps) because I did them backwards?
Now the screen only shows an open trash can with the Android logo, and it does not response? Is the phone bricked??? What can I do now?
Someone, please help!
When you click choose zip from sd card that takes you to your sd card and every folder contained in it. I usually just download ROMS with my phone and it puts them in the download folder. So when I "choose zip from sd card", then everything is in the folder "download". Next time either download with your phone or connect to your pc and put the files in a folder you will remember, example : sdcard/download. If you have pushed with adb then it might not be in a folder at all, I'm really not familiar with adb, maybe they were put in a folder named adb? I'm not familiar with the screen you speak of either, but it sounds like you have soft bricked your phone. Go back to stock with this guide http://rootzwiki.com/topic/605-guid...nja-apps-everything/page__p__11106#entry11106 if you are indeed soft bricked.
Sent from my SGH-T959 using Tapatalk 2
mj56gt said:
I may have messed up the flash steps when I was trying to flash SuperNexus from Froyo? So I did the following first:
Then I put those two files on the phone with the following adb commands:
adb push SuperNexus-2.0-vibrantmtd-BUILD4-update2.zip /sdcard/
adb push gapps-jb-20130301-signed.zip /sdcard/
Click to expand...
Click to collapse
Just plug in you usb select mass storage and copy it in the main memory(where Android, DCIM, data, external_sd, voodo exist ) not in the External memory.... the other procedure rather than adb pushing was correct... this will be fine.:good:. try again and let us know if you passed well..... for being more sure put out your mini sd card from phone.....
mistermish2000 said:
Just plug in you usb select mass storage and copy it in the main memory(where Android, DCIM, data, external_sd, voodo exist ) not in the External memory.... the other procedure rather than adb pushing was correct... this will be fine.:good:. try again and let us know if you passed well..... for being more sure put out your mini sd card from phone.....
Click to expand...
Click to collapse
Thank both of you for the kind suggestions!
It was quite scary for me since this was the first time I encountered such a scenario. After the soft brick, I managed to boot the phone into download mode many times, but the computer would not be able to detect the phone! Then accidentally I booted it into recovery mode, and the computer somehow recognized it. So I decided to just push the .zip files again with adb, After that everything went smoothly.
Now I'm fully enjoying JB!
glad you figured it out somehow... get used to it it will become easy to you when you do this again and again cause this phone can't be brick-able.. :highfive:

Categories

Resources