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.
Related
Hi, people...
Just wondering if there is a way out of my situation, last night I installed the latest recovery image (RA-hero-v1.5.3.1), prior to that I put the latest Villian Rom on to update, but I think I messed things up, with some of the new menus in the Recovery rom as I accidently hits a few things :-(
Messages I'm getting are on almost every option I try is : E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0 (no such file or directory)
and
E:Can't mount SDCARD:/nandroid/
If I try any other options aswell I get "Error: Run 'bart' via adb" which is no good when I get the adb messages as for some reason my windows 7 pc has stopped detecting the phone in adb mode?!
The normal Hero bootloader get's detected fine in windows, is there anything I can do here to restore the system. I think some messages flashed by saying missing image! Which don't sound good.
Any ideas on how I can fix this?
if you have access to fastboot as you say, I'm sure you could fastboot recovery (just in case there's some weird issue there), then format the SD card and restore from a nandroid backup on your PC (I hope you took a copy of the backup on a PC).
Other than that, you might need to wait on someone like kendong2 to spread his words of wisdom here, as he seems good at solving stuff like this.
lechy said:
Hi, people...
Just wondering if there is a way out of my situation, last night I installed the latest recovery image (RA-hero-v1.5.3.1), prior to that I put the latest Villian Rom on to update, but I think I messed things up, with some of the new menus in the Recovery rom as I accidently hits a few things :-(
Messages I'm getting are on almost every option I try is : E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0 (no such file or directory)
and
E:Can't mount SDCARD:/nandroid/
If I try any other options aswell I get "Error: Run 'bart' via adb" which is no good when I get the adb messages as for some reason my windows 7 pc has stopped detecting the phone in adb mode?!
The normal Hero bootloader get's detected fine in windows, is there anything I can do here to restore the system. I think some messages flashed by saying missing image! Which don't sound good.
Any ideas on how I can fix this?
Click to expand...
Click to collapse
For the phone not being detected in adb mode? what shows in device manager when its plugged in under universal serial bus?
try formatting the card using a linux live disc like gparted...
anon2122 said:
if you have access to fastboot as you say, I'm sure you could fastboot recovery (just in case there's some weird issue there), then format the SD card and restore from a nandroid backup on your PC (I hope you took a copy of the backup on a PC).
Other than that, you might need to wait on someone like kendong2 to spread his words of wisdom here, as he seems good at solving stuff like this.
Click to expand...
Click to collapse
Thanks for the advice, my heart started pounding very hard when you mentioned about the nandroid backup being backed up! Luckily, I done an SD card backup a few weeks ago and found the folder, phew.
Sorry for being a little foolish, but when you say do a fastboot recovery how is this done in the bootloader, i'll search google in the mean time. To format my sd card im going to have to get usb adapter I presume as you can't format the SD card from bootloader? Correct me if im wrong.
anarchyuk said:
For the phone not being detected in adb mode? what shows in device manager when its plugged in under universal serial bus?
try formatting the card using a linux live disc like gparted...
Click to expand...
Click to collapse
Thanks for the reply. Nothing comes up at all anymore, I can't see any changes when I plug in the device under recovery mode, and even when selecting the USB-MS mode, nothing is detected or shown on the USB devices list. However, when I first tried originally it came up with the device not recognised.
Got to get myself a SD USB adapter first to format the card.... so I'll give that a try.
Ok, got myself a USB adapter to format SD Card, i've put my backup of everying back on. I now understand about how to use the fastboot command via command prompt etc....
Where do I go from here? What commands to type etc.. I've looked at the options but cannot seem to use flashall command succesfully.
The device is listed when typing fastboot devices, so I take it that's one good thing for a start!
Again, thanks for any help with this.
Just another question does the SD card have to be formatted specially? Ie partitioned etc... perhaps this is why I can't get it mounted under the recovery options. Because I accidently done one of the partion options and from then on I had all the problems.....
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
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:
I have an iBall Slide i701 running Windows 10. So, I wanted to try RemixOS on my tablet after seeing a thread on some site. So, I downloaded the zip and tried to use the USB option but my USB was not detected at all. I tried everything like formatting the pendrive to different formats, but still no luck. Then, I tried the Hard Disk installation, but here's the problem. My tablet has 16GB of internal storage of which right now about 7GB is free (which isn't enough to repartition). But, I do have a 16GB SD Card on the tablet but it's being shown as Secure SD Storage and I am unable to create a normal bootable partition with the SD Card. So, when I try the hard disk installation option, the SD Card doesn't show up among the hard drives, instead it shows among USB. Anyways, I tried USB installation to the SD Card, but it won't boot into the USB though I have set UEFI as boot option #1 and disabled secure boot.
Please help me out!
Well i have tried everything from booting linux to win7 win 8.1 installers with and without efi installers it just doesn't boot from any flash drive. There is a lock in the bios on boot option that forces it to boot from internal and yes i also tried via its sd slot, the prob is the sd card can only be accessed after it boots up, so thats a bummer,
vistatech9895927087 said:
I have an iBall Slide i701 running Windows 10. So, I wanted to try RemixOS on my tablet after seeing a thread on some site. So, I downloaded the zip and tried to use the USB option but my USB was not detected at all. I tried everything like formatting the pendrive to different formats, but still no luck. Then, I tried the Hard Disk installation, but here's the problem. My tablet has 16GB of internal storage of which right now about 7GB is free (which isn't enough to repartition). But, I do have a 16GB SD Card on the tablet but it's being shown as Secure SD Storage and I am unable to create a normal bootable partition with the SD Card. So, when I try the hard disk installation option, the SD Card doesn't show up among the hard drives, instead it shows among USB. Anyways, I tried USB installation to the SD Card, but it won't boot into the USB though I have set UEFI as boot option #1 and disabled secure boot.
Please help me out!
Click to expand...
Click to collapse
hello, ive had similar problems with the iball marvel 6 and ive contacted iball for it and they sent me this email
With reference to your below mail, iBall compbook Marvel 6 comes with pre-installed OS 64 bit Windows 10 Home Ver. Customer cannot Upgrade or downgrade the OS through online or with any other external devices. Compbook works on tablet technology it will not support any other OS except the OS which is preinstalled in it, therefore there is no any separate drivers available for that..
i dont know if this is similar to yours but your slide also works on tablet technology so it might be the crux of the problem.
It is possible to load from USB
I had the same problem with my iball i701, during win10 upgrade it went into blank screen of death. Heres what i did.
0. Make efi shell as first boot in bios.
1. Go into efi shell, type map. It lists the drives, usb is not listed.
2. Unplug usb, type map -r
3. Plug in usb drive (my usb was win10 efi bootable drive), type map -r
4. Voila now the last entry is usb drive.
5. Type reset, press esc to go into bios. Usb is now listed in boot options.
Done.
RCA Pro10 (Digiin) RCT6103W46 10" Tablet
RK3188 CPU
JellyBean 4.4.2
Problem: Unit hangs on RCA splash screen and therefore will not boot up even after factory resets. Unit was working fine until vold.fstab was edited to change the mount point of the external SD card.
USB Debugging enabled.
adb shell accessable.
busybox accessable.
When trying to obtain su privileges, via adb shell, the shell hangs.
Can not change read only status to r/w status for internal storage and therefore can not push edited vold.fstab back into internal storage.
Have tried several rooting programs (on both Windows 10, Ubuntu 18.04.2 and Mint 19.1 Cinnamon) to obtain root/su status on the tablet with no positive results.
No fastboot option available - only recovery is available via power/volume key combinations.
No viable firmware images availble either from manufacturer or available via internet searching.
Questions:
What software (or via adb shell) would pull a complete set of recovery images from
the unit so that I could install them to an external SD card with the purpose of attempting to boot/run Android from the external SD card?
Would this even be a possible option as I would imagine there would also have to be some method of overriding the original boot sequence so that it does boot from the external SD card?
I hate to think that this unit is totally bricked without exploring all options to try and revive it (including trying to install another OS which from doing net searches doesn't look to promising).
Any input on this topic would be much appreciated...thanks!