Hey every1, hope every1 is having a great day.
My problem is that im stuck with one room inside my tab (GT-7500) and its a CM9 ICS rom. For some strange reason i cant install it properly even though i have CWR 5.5.0.4 as listed in the installation steps. Then downloaded another rom (Infamous) and apparently i have to install another Honeycomb rom before installing this one.
Now to my question is there any other way to mount the sdcard beside the CWR?
As i can not find mount usb nor sdcard in CWR->Mount and Storge.
Thanks for the help in advance
In CWM, if you want to mount the internal /sdcard partition, select the option "mount data" in "Mount and Storage"
If you're talking about an external USB, you'll have to mount it manually via adb (if you're in CWM)
Well, ive done that. And it get recognized in the computer but does not show up in "My Computer", went to Computer Management to hopefully find it there with out any results. I also tried uninstall the driver and install it again. Thanks again mate
Oh no, it won't show in your computer as a usb drive or something similar if you are in cwm. What I understand is that you don't have a functional ROM, I mean, you can't boot into android and you need to put a new ROM in your tablet.
If that's the case, just use adb to push the ROM file. Read the answer #11 in this FAQ if you don't know what adb is: http://forum.xda-developers.com/showthread.php?t=1642009
Thanks Mate, all done thanks to you .
In case anywone is wondering heres how i did it.
First i installed ADB via a guide that i found on google (For some strange reason i cant link to the guide). Then via Terminal or Command Promt i used the command adb push Nameoftherom.zip /sdcard/Nameoftherom.zip.
Thanks again
Before yesterday when powering up my nook tablet I would get the "Installing factory Software...Do not Turn off your device" but immediately after I would get the error message "Please contact nook support." Now my nt just turns off after powering on and displaying the n screen. I have absolutely no clue what is wrong with my tablet or what steps to follow in order to fix it. I would greatly appreciate any input from the knowledgeable members here to point me in the right direction in terms of what procedures need to be followed. Thanks
Heathie89 said:
Before yesterday when powering up my nook tablet I would get the "Installing factory Software...Do not Turn off your device" but immediately after I would get the error message "Please contact nook support." Now my nt just turns off after powering on and displaying the n screen. I have absolutely no clue what is wrong with my tablet or what steps to follow in order to fix it. I would greatly appreciate any input from the knowledgeable members here to point me in the right direction in terms of what procedures need to be followed. Thanks
Click to expand...
Click to collapse
Okay! Step one, you need to make a bootable CWM card.
Get yourself a microSD card, format it, and copy the files from HERE (download, unzip to your SD card).
Power your NT completely down, plug in the card, and then plug in the USB cable.
You should boot to a "cardboard" box screen.
After that, its going to boot into CWM recovery. Now you're not going to have alot of tools on the card at this point, but you may see some errors about stuff not being able to be mounted, etc.
Once you've got that done, post back here, and also include any errors you see!
From there, we can try to figure out exactly what's gone wrong, and the best approach to fix it.
--Also! Include the information about your NT, Is it rooted? What firmware or Rom? Other than powering up, what had you done (If anything) previously before the error!
^ Thanks for your quick reply!
As I wrote in my first post I'm a complete noob when it comes to rooting or hacking any devices. I have not once tried rooting my NT. What I did do though in order to have android as an option on my tablet is buy one of those Nook2Android cards. Now I think I may have accidentally pressed Format SD card or something like that when trying to do something else. That's all that I can think of that I may have done to cause the error.
I'm going to try and make the bootable CWM card right now. I'll make sure to report back!
lag0matic,
I now have a bootable CWM card.
So when I boot into CWM I get this error:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
What needs to be done now? Thanks
Heathie89 said:
lag0matic,
I now have a bootable CWM card.
So when I boot into CWM I get this error:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
What needs to be done now? Thanks
Click to expand...
Click to collapse
Erf. Okay, you've managed to bork your partitions.
Lets hope this goes easily!
First, lets get Parted (and some other tools) on your CWM recovery card.
Download this file here then unzip them to the root of your CWM Sd card.
Then you need to get ADB up and installed.
I used This forum to get the drivers, however, I couldnt get ADB to work right off the bat.
I'll copy/paste the steps I used and helped others get ADB runnng.
First, google this application: Usbdeview
Download the appropriate one for your system.
Unplug all USB mass storage devices (USB HDD's, Card readers, Memory sticks, etc)
Run USBDeview, delete anything Google, Android, Nook, Barnes and Noble, and Mass storage.
Reboot.
Open device manager
Run the "Runmefirst" or whatever its called from the ADB directory
Plug in your NT.
Go to device manager - look for a broken driver on the tablet, and tell it to install the drivers (you may have to use "have disk" and point to the usb driver directory)
This should install the driver for your NT.
You may also need to edit a file in the .android directory, at the root of your windows username folder.
in which case, drop to a command prompt and type
echo 0x2080 > %username%\.android\adb_usb.ini
after that, switch to the directory you unziped the ADB files to (I used C:\ntroot) and try to connect to your NT by typing "adb devices"
you _should_ see something like
1234567890 Recovery
Or
000000000 Recovery
Now, once you see one of the above messages
in the same command promt window enter the follwing commands
adb shell
mount /sdcard/
cd /sdcard/
parted /dev/block/mmcblk0
you'll then get a prompt that looks like
(parted)
type "print"
and hopefully you'll see a few errors, and it will ask you to fix them, choose fix for both.
Once you get this far (Or, if you run into troubles) post again and i'll see what I can do for you!
(I have successfully un-bricked my NT, but I did it in a way I want to avoid fo you, as we want yours to run stock roms)
lag0matic said:
Erf. Okay, you've managed to bork your partitions.
Lets hope this goes easily!
First, lets get Parted (and some other tools) on your CWM recovery card.
Download this file here then unzip them to the root of your CWM Sd card.
Then you need to get ADB up and installed.
I used This forum to get the drivers, however, I couldnt get ADB to work right off the bat.
I'll copy/paste the steps I used and helped others get ADB runnng.
First, google this application: Usbdeview
Download the appropriate one for your system.
Unplug all USB mass storage devices (USB HDD's, Card readers, Memory sticks, etc)
Run USBDeview, delete anything Google, Android, Nook, Barnes and Noble, and Mass storage.
Reboot.
Open device manager
Run the "Runmefirst" or whatever its called from the ADB directory
Plug in your NT.
Go to device manager - look for a broken driver on the tablet, and tell it to install the drivers (you may have to use "have disk" and point to the usb driver directory)
This should install the driver for your NT.
You may also need to edit a file in the .android directory, at the root of your windows username folder.
in which case, drop to a command prompt and type
echo 0x2080 > %username%\.android\adb_usb.ini
after that, switch to the directory you unziped the ADB files to (I used C:\ntroot) and try to connect to your NT by typing "adb devices"
you _should_ see something like
1234567890 Recovery
Or
000000000 Recovery
Now, once you see one of the above messages
in the same command promt window enter the follwing commands
adb shell
mount /sdcard/
cd /sdcard/
parted /dev/block/mmcblk0
you'll then get a prompt that looks like
(parted)
type "print"
and hopefully you'll see a few errors, and it will ask you to fix them, choose fix for both.
Once you get this far (Or, if you run into troubles) post again and i'll see what I can do for you!
(I have successfully un-bricked my NT, but I did it in a way I want to avoid fo you, as we want yours to run stock roms)
Click to expand...
Click to collapse
So I'm currently going through the process of installing the drivers but I keep getting OMAP4430 under Other devices while Device Manager keeps refreshing.
Heathie89 said:
So I'm currently going through the process of installing the drivers but I keep getting OMAP4430 under Other devices while Device Manager keeps refreshing.
Click to expand...
Click to collapse
^ wow.... that is exactly what i got after the second time my unit barfed.
can you right click on the "omap4430" entry in the device manager and update the drivers by pointing to the folder that has the "nook drivers" folder in the adb + driver + fast zip file?
I imagine you will get a error telling you the drivers are not for this device.
Question to you, did you happen to try formatting the "internal sdcard" ?
@ Lag0matic. this is what killed my unit *dead* today. but it only occured *after* using the 2.3.7 memory managers (not rom-manager) to format the SDcard and the internal SDcard...
maxxcool7421 said:
^ wow.... that is exactly what i got after the second time my unit barfed.
can you right click on the "omap4430" entry in the device manager and update the drivers by pointing to the folder that has the "nook drivers" folder in the adb + driver + fast zip file?
I imagine you will get a error telling you the drivers are not for this device.
Question to you, did you happen to try formatting the "internal sdcard" ?
@ Lag0matic. this is what killed my unit *dead* today. but it only occured *after* using the 2.3.7 memory managers (not rom-manager) to format the SDcard and the internal SDcard...
Click to expand...
Click to collapse
The good news is I have now installed the drivers! My NT under Android Phone appears as Android Composite ADB Interface in Device Manager.
Sadly,though, after getting this far it seems adb still does not recognize my device?
After imputing "adb devices" in cmd in the directory containing the adb files what I get is:
List of devices attached
I don't know if I have missed a step or did one incorrectly.
Heathie89 said:
The good news is I have now installed the drivers! My NT under Android Phone appears as Android Composite ADB Interface in Device Manager.
Sadly,though, after getting this far it seems adb still does not recognize my device?
After imputing "adb devices" in cmd in the directory containing the adb files what I get is:
List of devices attached
I don't know if I have missed a step or did one incorrectly.
Click to expand...
Click to collapse
couple different things to try
#1
adb kill-server
adb start-server
adb devices
try this a couple times. my nook did not get hooked until i did this 2,3 times
#2 with the unit booted from cwm recovery *on the sd card*, reboot windows while leaving the device plugged in.
once back in windows try the adb devices command again.
failing that you are where i was. but at least you can get into cwm, mine ceased booting from sd entirely. heres a thought and a test. can you make the bootable-apla SD card and still use the nook via sd card only? or does it freeze up... ?
Heathie89 said:
The good news is I have now installed the drivers! My NT under Android Phone appears as Android Composite ADB Interface in Device Manager.
Sadly,though, after getting this far it seems adb still does not recognize my device?
After imputing "adb devices" in cmd in the directory containing the adb files what I get is:
List of devices attached
I don't know if I have missed a step or did one incorrectly.
Click to expand...
Click to collapse
i have had that happen a few times and the problem was that my drivers were not installing correctly. sure it appeared as android adb composite device, but it most likely installed the wrong driver for the wrong device.
this is where things get a bit complicated because you need to look for the product and vendor id's for the nook tablet and modify them correspondingly in the android_winusb.inf.
also make sure you execute the runmefirst.bat
that creates a .android folder in your user folder. that was the step i kept missing when i had your problem with the drivers... ironic right? "runmefirst" and i run it last haha...
I picked up an Archos G9/80 and immediately came here to root it. Instead I wound up installing SDE and flashing Freezenooks G9 Build8 from tis thread: http://forum.xda-developers.com/showthread.php?t=2171742
I just have one problem. I can't get Dropbear SSH II to install. I tried both from the Play store and adb installing it. I even tried the older version. The apk installs fine but it fails to install the service. They both fail during a step where it says its remounting read-only. This is interesting as I notice that the rootfs is mounted read-write by default. From adb shell I tried to force it read-only with mount -o remount,ro but it fails as the Device is busy. I'm guessing this is the same problem that the installer is encountering and since it can't remount rootfs as read-only it proceeds to remove the binaries it's copied over. I've been trying to find out where it copies them before it deletes them. I assume they would be in /system/bin but I can't ever find them there. I gets to the error step way too fast.
Does anyone have any workarounds? Could / should I "borrow" the binaries from another Android box and copy everything to the correct place?
Hi I was attempted to updating to the newest Venom X+ rom and my phone got stuck in boot loop even after some other fixes, so I wiped the phone and have TWRP v2.4.1.0 on the phone but no rom. So I am trying to ADB sideload the .zip however at around 20% it says "failed to write to protocol (no status).
Anyone know why this is? Happens on multiple ROM's.
--edit--
used
adb shell mount -t tmpfs none /sdcard
adb push ROM.zip /sdcard
Got the Zip onto the device but /system and /cache won't mount *least progress is made*
HTC MTP drivers not installing correctly, maybe related to why I can't ADP all the way
Hi everyone, I recently got a Novatech nTab II (RK3288 Chip), I think this tablet is pretty much a clone of a Pipo P1. The Tab comes rooted but does not have Google Play Store. So i flashed TWRP onto the tablet and flashed GAPPS for KK4.4.2 (Which is what comes onto the tablet), this is where it all started to fall apart LOL
The first problem was that there was a constant error of System Installer has stopped working. I went back into TWRP and renamed SystemInstaller.apk so that it did not give constant messages. Anyway, the Google Services wont connect. I decided to try and flash a RileyRom for the Pipo P1, but wanted to backup in TWRP first, I tried to backup but i got the error E: Unable to mount Internal Storage. I done some digging online and tried to format the UserData and Data partitions through TWRP but each time i got the same error E: Unable to mount Internal Storage.
Onto the next solution, i tried to format the partition using ADB but i cannot get the ADB Shell to work, it always gives 'Error: Closed'. I've tried updating the ADB, constant Restarts of PC and Tab, Stopping and starting the ADB server, switching to CWM and formatting the partitions there, using sideload in CWM, nothing seems to let me use the Shell.
I can see the device is in Sideload when i send ADB Devices through ADB, but as soon as i try ADB Shell i get the error.
I need the backup because Novatech refuse to release their firmware.
Even if i do flash the Pipo P1 ROM and it is stable i still need to format the partitions, they no longer even show when loaded into system.
Desperately need some help with this and any advice is greatly appreciated.
Thanks
Alex
PS: Also would someone help me try and identify if the Pipo P1 RileyRom1.8 will work on the Novatech nTab II they appear to use the same Tablet.
AlexDoran said:
Hi everyone, I recently got a Novatech nTab II (RK3288 Chip), I think this tablet is pretty much a clone of a Pipo P1. The Tab comes rooted but does not have Google Play Store. So i flashed TWRP onto the tablet and flashed GAPPS for KK4.4.2 (Which is what comes onto the tablet), this is where it all started to fall apart LOL
The first problem was that there was a constant error of System Installer has stopped working. I went back into TWRP and renamed SystemInstaller.apk so that it did not give constant messages. Anyway, the Google Services wont connect. I decided to try and flash a RileyRom for the Pipo P1, but wanted to backup in TWRP first, I tried to backup but i got the error E: Unable to mount Internal Storage. I done some digging online and tried to format the UserData and Data partitions through TWRP but each time i got the same error E: Unable to mount Internal Storage.
Onto the next solution, i tried to format the partition using ADB but i cannot get the ADB Shell to work, it always gives 'Error: Closed'. I've tried updating the ADB, constant Restarts of PC and Tab, Stopping and starting the ADB server, switching to CWM and formatting the partitions there, using sideload in CWM, nothing seems to let me use the Shell.
I can see the device is in Sideload when i send ADB Devices through ADB, but as soon as i try ADB Shell i get the error.
I need the backup because Novatech refuse to release their firmware.
Even if i do flash the Pipo P1 ROM and it is stable i still need to format the partitions, they no longer even show when loaded into system.
Desperately need some help with this and any advice is greatly appreciated.
Thanks
Alex
PS: Also would someone help me try and identify if the Pipo P1 RileyRom1.8 will work on the Novatech nTab II they appear to use the same Tablet.
Click to expand...
Click to collapse
OK so for anyone out there who like me could find no information on the Novatech nTab II, i got the tab working on RileyROM 1.8, when flashing i left the Loader out and it seems to boot and work ok.
I fixed the Internal Storage by mounting it to the PC then formatting.