Related
I recently rooted my Eris and I'm unable to flash a custom recovery because I can't get the USB drivers to update with those found in the SDK files. When I try to update the drivers Windows tells me that I have the most up to date drivers installed. It's because of this I cannot see my phone in the command prompt and can't get the custom recovery to work.
Has anyone tried putting the recovery files on their SD and using a terminal emulator?
Any ideas on updating the USB drivers?
If I flashed a custom Rom (as risky as that is without a recovery) could I then use nandroid or some other recovery? Or would I still need to use SDK?
joshw0000 said:
I recently rooted my Eris and I'm unable to flash a custom recovery because I can't get the USB drivers to update with those found in the SDK files. When I try to update the drivers Windows tells me that I have the most up to date drivers installed. It's because of this I cannot see my phone in the command prompt and can't get the custom recovery to work.
Has anyone tried putting the recovery files on their SD and using a terminal emulator?
Any ideas on updating the USB drivers?
If I flashed a custom Rom (as risky as that is without a recovery) could I then use nandroid or some other recovery? Or would I still need to use SDK?
Click to expand...
Click to collapse
download htc sync that should fix ur problem , it did for me
Yes HTC sync updated mine as soon as your phone is acknowledged by HTC sync it should update your usb drivers
FYI HTC sync did NOT work for me on Windows 7. I had to do some pretty annoying stuff to stop windows from installing the regular drivers automatically. If HTC sync doesn't work I can try to help.
If HTC Sync doesn't help, try the following steps.
1. Unplug your Eris from the PC
2. Open Device Manager and delete the Android device
3. Reboot your PC
4. Once in Windows, connect your Eris
5. The drivers should load automatically, if not point it to the SDK drivers folder
Good luck!
Any more ideas
First I tried downloading HTC Sync on my laptop (running Vista) and that didn't do it. Then I deleted the drivers and tried to manually download them back with the ones in the USB folder of SDK and still it wouldn't work.
So I started over and downloaded SDK and Java to my pc (Windows 7) and tried to update the drivers with the ones found in SDK and it wouldn't let me. So I deleted the drivers, unplugged my phone, and plugged it back up. Before I could attempt to direct it to download the intended USB drivers, Windows 7 had already updated with the drivers of it's choice. I can't win for losing.
If you don't mind using one of those "Live" Linux CDs, you could install the recovery using fastboot.
No need to install anything on the PC, and no drivers are needed for Linux, no SDK, no Java, no adb; just make sure to run fastboot as root.
The downloads of fastboot and the Amon_RA recovery are small, so they will easily fit in /tmp.
bftb0
I've never used Linux but I'm willing to try. Please tell me more. Are there "how tos" for this?
When you have your phone plugges in do you have it set to "charge" or "sync"? I know all the how to's say yo have it set to charge only but the inly way my computer ever finds my phone is if it us set to sync.
-------------------------------------
Sent via the XDA Tapatalk App
I set it to charge. I was finally able to install the correct driver. I selected a Google driver from the list it gave me (which my computer did not like) then went back and updated the drivers with those found in the tools usb folder of SDK. IT FINALLY LET ME!
Now I have a new problem. I'm using the command prompt and trying to create a custom recovery. I set it to the tools directory in SDK (where the flash and recovery images are) and I'm entering the commands exactly like the "how to" instructions have them. I keep getting "adb: not found" errors.
Can anyone tell me what I'm doing wrong?
joshw0000 said:
I've never used Linux but I'm willing to try. Please tell me more. Are there "how tos" for this?
Click to expand...
Click to collapse
Well, in the long run it is probably a good idea to resolve the driver install problems you are having on your PC, because it is very useful to have "adb" around, even if you are already rooted and have the ROM of your choice installed.
But, if you would like to do this, here's an outline below. Note that the point of the "Live" CDs is that you are not installing Linux on your machine, you are just booting it directly from the CD - the OS and hard drive on your PC are untouched.
1) Download an ".iso" file from your favorite Linux distro [ 3 ] for their "live" CD. (BIG download, usually 600+ MB)
2) Burn the .iso file to a CD as a bootable CD. (Most decent CD/DVD burner programs know what an .ISO file is, but might refer to them as a disk image).
3) Boot your PC off it! (You might need to hit a key on your PC right after you power it on to go into a boot menu, or the BIOS setup to change the boot order so your PC will try to boot from the CD/DVD before it tries the hard drive).
4) Copy the fastboot [ 1 ] executable for Linux and the Amon_RA recovery image [ 2 ] to /tmp "somehow" - you could just download it using the Linux browser if your network come up automatically (wired ethernet), or you could put them onto a USB key beforehand, and plug that in after Linux has booted; it should mount automatically.
5) Then, open up a terminal window and become root. (Type either "su" or "sudo /bin/bash" - depends on the Linux distro)
6) Attach your (well-charged) phone to the phone via USB, and power it up in fastboot mode (Send+End simultaneously)
cd /tmp
chmod 755 fastboot
md5sum recovery.img (check file sig)
./fastboot devices (check to see you are connected)
./fastboot flash recovery recovery.img
Obviously, if you need to look something up on the internet, it is useful to be networked, so you can use a web browser. The Linux boot will try to autoconfigure network interfaces automatically, but this is going to be most straightforward with a wired connection (Ethernet). Alternatively, if you have another PC or laptop nearby, you could use that.
Good luck.
Edits:
[ 1 ] Find Linux version of fastboot from HTC midway down this page - md5sum 9851bb6ad29cd4b60c9ba9d011ba9efd
[ 2 ] Amon_RA's recovery is located on this XDA page - md5sum e3932991f097993602af3c7a4b61a4f8
[ 3 ] Ubuntu's Current (x32) CD for v10.04 this page
NOTE: This CD is both a "Live" CD and an Install CD. You DO NOT WANT TO INSTALL ANYTHING; you are using the "Live" CD function - see the "show me how" link under Item #3 ("Try It!") on the above linked page
[ 4 ] Various OpenSuSe 11.2 Live CDs
Thanks for the info. I was able to get my drivers installed and run a nandroid recovery. Then I think I bricked my phone:
I just ran a nandroid backup for my Eris which was at stock 2.1 w/ root. I first partitioned the sd to swap - 3072 MB, ext2 swap 3072 MB, and fat32 - remainder. Realizing this was stupid, I went back and changed the partition to swap - 0, ext2 - 512 MB, fat32 - remainder 7680 MB or 7.5 GB. I moved ext2 to ext3 and booted the phone. All my sd was cleared so I copied everything back on (I saved all sd contents to my computer prior to this). I went back to recovery and flashed Eris Lightning 3.02. Everything went successful and when it rebooted, I saw the droid guys, then the "quietly brilliant", then "Verizon" screens. It then began running the "quietly brilliant" and "verizon" screens over and over. I pulled the battery and powered up again but it's still running those two screens over and over. I booted into recovery and attached my phone to the computer. I opened command prompt, entered " sd C:\android-sdk-windows\tools" and then entered "adb devices". It reads "List of devices attached" but there are none. I attempted to add the driver back to my device but when I go to device manager and click "update driver" and point it to the tools directory in SDK, it says that "Windows could not find driver software for your device".
If I can't communicate with my phone via usb and it wont boot, how can I get it to recover?
Any suggestions would help, I'm scratching my head here. I really don't want to have to buy another phone.
joshw0000 said:
Thanks for the info. I was able to get my drivers installed and run a nandroid recovery. Then I think I bricked my phone:
I just ran a nandroid backup for my Eris which was at stock 2.1 w/ root. I first partitioned the sd to swap - 3072 MB, ext2 swap 3072 MB, and fat32 - remainder. Realizing this was stupid, I went back and changed the partition to swap - 0, ext2 - 512 MB, fat32 - remainder 7680 MB or 7.5 GB. I moved ext2 to ext3 and booted the phone. All my sd was cleared so I copied everything back on (I saved all sd contents to my computer prior to this). I went back to recovery and flashed Eris Lightning 3.02. Everything went successful and when it rebooted, I saw the droid guys, then the "quietly brilliant", then "Verizon" screens. It then began running the "quietly brilliant" and "verizon" screens over and over. I pulled the battery and powered up again but it's still running those two screens over and over. I booted into recovery and attached my phone to the computer. I opened command prompt, entered " sd C:\android-sdk-windows\tools" and then entered "adb devices". It reads "List of devices attached" but there are none. I attempted to add the driver back to my device but when I go to device manager and click "update driver" and point it to the tools directory in SDK, it says that "Windows could not find driver software for your device".
If I can't communicate with my phone via usb and it wont boot, how can I get it to recover?
Any suggestions would help, I'm scratching my head here. I really don't want to have to buy another phone.
Click to expand...
Click to collapse
First, relax and take a deep breath; everything's going to be fine.
In the recovery main menu, there is an Item called something like "MS-USB toggle" or something like that. It does not use the adb driver, it uses a standard "Mass Storage Device" USB driver already on the PC. The purpose of this function is to make the SD Card mount on the PC when the Amon_RA recovery is running.
Try that - it should work.
Then, download a conservative ROM such as Ivanmmj's Official 1.0 alpha, or Jcase's "Plain Jane", and copy it to your SD card.
After you have done that, make sure to check the MD5 sum of that .zip file on the SD card. (You should be doing this already).
Then, cleanly dismount the USB drive from the PC with the "Safely Remove Hardware" thingamabob, and toggle "off" the MS-USB toggle on the phone. Return to the main menu, wipe /data, and then flash the "conservative" ROM.
Then boot the conservative ROM just to verify everything is OK.
Next, Backup anything from the SD card that you don't already have (this step might be optional), and boot into recovery, and unpartition your SD card so that the only thing that is there is the VFAT partition.
For the moment, I'll give you some advice: f*ck A2SD. You need to gain some familarity with how the various versions of a2sd work before you start using it..
Very likely you were just stuck in a boot loop created by the re-partitioning you performed after initial configuration of a ROM that uses a2sd. Frankly, it is easy to create conditions for this, especially if you switch between ROMs that use different versions of a2sd, and/or don't understand that certain versions are not correctly backed up with Nandroid at the moment (e.g CLB).
bftb0
Go in to the start menu of your computer or laptop right click on computer and go down to properties and open it up look to the right and you will see something that says advanced system settings click that and it will open up another window for system properties.. Okay look at the bottom of that small window you will see something that says environmental variables, click that. Now you want to scroll through the system variables and find the one that says "path" you want to change that to you ";C:\android-sdk-windows\tools" and save it.. That is where your adb file or app is in your sdk tools folder, so when you open up a command prompt type in adb devices it may say something about killing daemon starting successful.. Don't worry just type it in again you should get your phones serial number thats when you know your good and you can start talking to your phone.. You can try a simple command like adb reboot and it will reboot your phone.. All else fails and you do this and your phone is responding but you can get anything to run in the command prompt type with 1 space cd then another space and then copy and paste "C:\android-sdk-windows\tools" that.. So it will look something like this
cd C:\android-sdk-windows\tools.. That should def do the trick.. Or absolute worst case scenario and you want to make it real easy and not have the fun of doing all the hard but fun work just use the "all in one root script" it will root your phone and it will also install "amon RA recoveryv1.6.2"... Hope this helps you out. LoL I know its long but yo dude I went through the same hell and I finally got everything where I want it!!!!!! Also make sure your HBOOT is under 1.49, if you have 1.49 you cant root... For example 1.46 your good...
Go in to the start menu of your computer or laptop right click on computer and go down to properties and open it up look to the right and you will see something that says advanced system settings click that and it will open up another window for system properties.. Okay look at the bottom of that small window you will see something that says environmental variables, click that. Now you want to scroll through the system variables and find the one that says "path" you want to change that to you ";C:\android-sdk-windows\tools" and save it.. That is where your adb file or app is in your sdk tools folder, so when you open up a command prompt type in adb devices it may say something about killing daemon starting successful.. Don't worry just type it in again you should get your phones serial number thats when you know your good and you can start talking to your phone.. You can try a simple command like adb reboot and it will reboot your phone.. All else fails and you do this and your phone is responding but you can get anything to run in the command prompt type with 1 space cd then another space and then copy and paste "C:\android-sdk-windows\tools" that.. So it will look something like this
cd C:\android-sdk-windows\tools.. That should def do the trick.. Or absolute worst case scenario and you want to make it real easy and not have the fun of doing all the hard but fun work just use the "all in one root script" it will root your phone and it will also install "amon RA recoveryv1.6.2"... Hope this helps you out. LoL I know its long but yo dude I went through the same hell and I finally got everything where I want it!!!!!! Also make sure your HBOOT is under 1.49, if you have 1.49 you cant root... For example 1.46 your good...
I mistakenly dropped pershoot's 10.1v kernel onto my 10.1 (P7500). Now thw screen draws garbage, and does not seem happy. I do have CWM 4.0.0.4 on it, and that does seem to work well, except that it won't mount a USB drive. ("unable to open ums lunfile" issue)
Any help would be appreciated.
adb shell mount /data
adb push NEW_KERNEL /data/media
flash new kernel and reboot.
done.
Or if you don't understand what pershoot is telling you to do. The backup that you shoulve made prior to flashing anything should work. You can select backup and restore in cwm, then advanced restore, select your backup, then just select boot
pershoot said:
adb...
done.
Click to expand...
Click to collapse
Thank you so much. In my panic, I had forgotten that the adb monitor is still running in recovery mode. I took this time to put ADB on my new Win7 machine. (been using it on my Ubuntu for kernel builds and client coding)
I'm using CM7 ALpha2, so i use 1-click CWM to recover stock recovery, and i reboot it! After that i receive endless bootloop! So i try to 8 times factory reset but it doesn't work! However it can boot into CWM from sdcard, and i flash another rom , but it still have bootloop! I try all roms i have but it still bootloop ! So Please help me !
Anyone help me please? I tried my best!
Check the checksum of the CM7_NT_Alpha12_Public1.zip on your uSD to see if it matches. Many time, the fault lies in corrupted file getting flashed. Cheap uSD reader from China can corrupt your file during transfer. I've had this experience and heard of it. Use a good uSD reader and always check the checksum.
You can shutdown your NT by holding the power button until it shut of. Re-download CM7_NT_Alpha12_Public1.zip and re-flash.
succulent said:
Check the checksum of the CM7_NT_Alpha12_Public1.zip on your uSD to see if it matches. Many time, the fault lies in corrupted file getting flashed. Cheap uSD reader from China can corrupt your file during transfer. I've had this experience and heard of it. Use a good uSD reader and always check the checksum.
You can shutdown your NT by holding the power button until it shut of. Re-download CM7_NT_Alpha12_Public1.zip and re-flash.
Click to expand...
Click to collapse
Not only CM7 Alpha2, i tried all rom in forum, none of them worked !
From recovery, do a complete data wipe (-wipe data/factory reset)
then wipe your cache (-wipe cache partition)
Install an md5 verified zip of CM7.
Wipe cache partition again. Reboot
See if that works.
During CM7 testing, the only time we encountered boot loops was from not doing a cache wipe. If you have installed numerous files, chances are stuff is getting corrupted.
Know-Fear said:
From recovery, do a complete data wipe (-wipe data/factory reset)
then wipe your cache (-wipe cache partition)
Install an md5 verified zip of CM7.
Wipe cache partition again. Reboot
See if that works.
During CM7 testing, the only time we encountered boot loops was from not doing a cache wipe. If you have installed numerous files, chances are stuff is getting corrupted.
Click to expand...
Click to collapse
It still not work , it still bootloop ! !
blackhat007 said:
It still not work , it still bootloop ! !
Click to expand...
Click to collapse
Try the cwm fix by indirect to push cwm image again back in place , you may want to do all the wipes data, cache, advanced> dalvik cache and system partition just in case but DO NOT format any other partition or you'll mess your device even more.
~ Veronica
Sent from XDA premium using my Nook Tablet
lavero.burgos said:
Try the cwm fix by indirect to push cwm image again back in place , you may want to do all the wipes data, cache, advanced> dalvik cache and system partition just in case but DO NOT format any other partition or you'll mess your device even more.
~ Veronica
Sent from XDA premium using my Nook Tablet
Click to expand...
Click to collapse
Yesterday when I tried to fixed this problem, perhaps I formated the /system and the /bootdata partition! Is this cause my problem
When you boot into CWM recovery, go to advanced and show log. Do you have any errors listed there?
failed to open /sys/class/android_usb/android0/state: no such file or directory
Sometimes if i unplug cable and press power button, the N screen appear one time and turn off after that, but if i plug into computer, it will become bootloop !
Is there any ideas, i dont want to send back for warranty because i'm in Viet Nam !
If you don't have ADB set up, go download Indirect's nook&zergy file. It has ADB included in it, and you will need to grab the drivers from that same post. Located here
Then you will need to follow the instructions Here
Once you have working ADB, and you copy the parted file to your sdcard do this: (not listed as such in Celtic's post)
adb devices (make sure you are detected)
adb shell (this will return a # prompt)
cd /sdcard
parted /dev/block/mmcblk0 print
answer yes and fix as many times as necessary. Eventually it will return a partition break down.
From there, clear cache again to be safe, then reboot
I was in the situation where my Nook would boot, showed the "cardboard box", and then blackness. I just took it to the B&N store hoping for a reformat. Instead they gave me a whole new NT. YMMV of course. Good luck!
Dobabobalina said:
I was in the situation where my Nook would bot, shoe the "cardboard box", and then blackness. I just took it to the B&N store hoping for a reformat. Instead they gave me a whole new NT. YMMV of course. Good luck!
Click to expand...
Click to collapse
I don't think he would have the same experience being in Vietnam.
Know-Fear said:
If you don't have ADB set up, go download Indirect's nook&zergy file. It has ADB included in it, and you will need to grab the drivers from that same post. Located here
Then you will need to follow the instructions Here
Once you have working ADB, and you copy the parted file to your sdcard do this: (not listed as such in Celtic's post)
adb devices (make sure you are detected)
adb shell (this will return a # prompt)
cd /sdcard
parted /dev/block/mmcblk0 print
answer yes and fix as many times as necessary. Eventually it will return a partition break down.
From there, clear cache again to be safe, then reboot
Click to expand...
Click to collapse
I do following the instruction but i don't understand how to :
"ADB into your device and run the binary with the following command (you'll need it to be the accesible path or you can just be in the directory where it is)"
I double click on adb.exe but nothing happend !
you must have adb set up and working on your computer. Plug your NT USB cable in to the PC. If you have this:
Open a command window from the folder your adb.exe is located. (assuming you are running windows, linux would have a totally different set up that you would need to research). If in windows, navigate to the folder your adb is in (if you followed the guide in Indirect's thread, it would be in your c:\NTROOT folder. Either way, once you are in that folder, hold down your shift key and right click and select the 'open a command window here option from the menu.
Once you have a command window open, type the following:
adb devices (again, to make sure you are being detected)
adb shell
cd /sdcard
parted /dev/block/mmcblk0 print
answer the prompts with yes and fix as directed.
Know-Fear said:
you must have adb set up and working on your computer. Plug your NT USB cable in to the PC. If you have this:
Open a command window from the folder your adb.exe is located. (assuming you are running windows, linux would have a totally different set up that you would need to research). If in windows, navigate to the folder your adb is in (if you followed the guide in Indirect's thread, it would be in your c:\NTROOT folder. Either way, once you are in that folder, hold down your shift key and right click and select the 'open a command window here option from the menu.
Once you have a command window open, type the following:
adb devices (again, to make sure you are being detected)
adb shell
cd /sdcard
parted /dev/block/mmcblk0 print
answer the prompts with yes and fix as directed.
Click to expand...
Click to collapse
I'm using win7 ultimate 64bit , i open but nothing happened! I open task manager and see process adb.exe ! I tried it in winxp sp3 so it didn't work too !
adb is ran from a command window. its not a GUI based program. Follow the instructions I have given you and you should be good to go.
This same error happened to me earlier this afternoon and was easily recovered from.
blackhat007 said:
I'm using win7 ultimate 64bit , i open but nothing happened! I open task manager and see process adb.exe ! I tried it in winxp sp3 so it didn't work too !
Click to expand...
Click to collapse
[HOW-TO] Use ADB tool | Android Debug Bridge
you cant just type adb devices and expect it to work unless you add adb to windows PATH, first you have to "cd" to the path where adb files are located, most likely C:\ntoot or wherever you have placed them, more specific info is in the tutorial i posted.
~ Veronica
Know-Fear said:
adb is ran from a command window. its not a GUI based program. Follow the instructions I have given you and you should be good to go.
This same error happened to me earlier this afternoon and was easily recovered from.
Click to expand...
Click to collapse
I understand and i run the command but it didn't recognize my devices !
List of devices attached
blackhat007 said:
I understand and i run the command but it didn't recognize my devices !
List of devices attached
Click to expand...
Click to collapse
if you never rooted using a pc but the sdcard method then you need to run the runmefirst.bat that will create a .Android folder with adb_usb.ini containing nook vendor's id needed by adb to recognize your device.
~ Veronica
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...
so.... I screwed up & wiped my dna. no recovery img, nothing left on it a side from recovery.
i have team win v2.5.0.0
been trying to use adb sideload to install another rom. my pc recognizes the phone & i get adb running. been trying this method:
going to "advanced" in recovery, then:
adb /kill-server
adb usb
starting up "adb sideload",
adb devices
adb sideload (romname)
every single time, it keeps saying - *failed to write data 'protocol fault (no status)' *
anyone else experience this and know how to fix it?
FIXED!!!!!!!!
--------------------------
Rather then do "sideload", I just stayed in 'Advanced' and performed:
adb /kill-server
adb usb
adb push (romname) /sdcard
it successfully copied the rom to the sdcard folder, then I was able to install the rom just fine.
Thanks mate! You just saved my day.
I had the exact same problem and couldn't get sideload to work in TWRP 2.7.0.0 on Nexus5. But simple "adb push..." worked.
this doesn't work
thank you very much, you saved my day,too.
voxigenboy said:
so.... I screwed up & wiped my dna. no recovery img, nothing left on it a side from recovery.
i have team win v2.5.0.0
been trying to use adb sideload to install another rom. my pc recognizes the phone & i get adb running. been trying this method:
going to "advanced" in recovery, then:
adb /kill-server
adb usb
starting up "adb sideload",
adb devices
adb sideload (romname)
every single time, it keeps saying - *failed to write data 'protocol fault (no status)' *
anyone else experience this and know how to fix it?
FIXED!!!!!!!!
--------------------------
Rather then do "sideload", I just stayed in 'Advanced' and performed:
adb /kill-server
adb usb
adb push (romname) /sdcard
it successfully copied the rom to the sdcard folder, then I was able to install the rom just fine.
Click to expand...
Click to collapse
Thanks man... you just saved me a ton of trouble. Tried this on the Nexus 4 and works like a charm! :good:
just wanted to say thanks!
for some odd reason, my twrp (even though its the latest for my nexus7 grouper) had the same flashing no status error)
used the kill, usb, and push commands to copy over 3 different zips (rom,kernel,gapps) and it all copied over ready to flash
thanks!
23468
seriously thanks mate! work like charm :good::good:
for me it copies the small files but my rom is 1gb plus it gives me the error 'protocol failure' can some one give me a helping hand here?
please?
Same Issue
jacktackle said:
for me it copies the small files but my rom is 1gb plus it gives me the error 'protocol failure' can some one give me a helping hand here?
please?
Click to expand...
Click to collapse
Three days and All I can do is flash a recovery. Insertcoint goes though and says it's installed but nothing but HTC Screen
voxigenboy said:
so.... I screwed up & wiped my dna. no recovery img, nothing left on it a side from recovery.
i have team win v2.5.0.0
been trying to use adb sideload to install another rom. my pc recognizes the phone & i get adb running. been trying this method:
going to "advanced" in recovery, then:
adb /kill-server
adb usb
starting up "adb sideload",
adb devices
adb sideload (romname)
every single time, it keeps saying - *failed to write data 'protocol fault (no status)' *
anyone else experience this and know how to fix it?
FIXED!!!!!!!!
--------------------------
Rather then do "sideload", I just stayed in 'Advanced' and performed:
adb /kill-server
adb usb
adb push (romname) /sdcard
it successfully copied the rom to the sdcard folder, then I was able to install the rom just fine.
Click to expand...
Click to collapse
Thanks man. You're lifesaver
Awesome, this worked for me too
HELP
I have htc one s somthing wrong happend turned the storage from 16 giga into 48 mega byts i cant get back my storage what to do please help me* i still can push roms but i cant because there is no storage what to do
mahmoud hakim said:
I have htc one s somthing wrong happend turned the storage from 16 giga into 48 mega byts i cant get back my storage what to do please help me* i still can push roms but i cant because there is no storage what to do
Click to expand...
Click to collapse
Can you ruu. Then do a factory restore. That should reset the partition
This does not work for me. Firstly, I tried installing Cyanogenmod by putting it on my internal SD card, then booting to recovery and installing the zip, and this did not work. So I tried to sideload it and got the error " * failed to write data 'protocol fault (no status)' * ". I don't know what to do. I've also tried the same with Paranoid Android but I get the same errors. Any help would be greatly appreciated.
derekokelly said:
This does not work for me. Firstly, I tried installing Cyanogenmod by putting it on my internal SD card, then booting to recovery and installing the zip, and this did not work. So I tried to sideload it and got the error " * failed to write data 'protocol fault (no status)' * ". I don't know what to do. I've also tried the same with Paranoid Android but I get the same errors. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Exact same problem I have, any suggestions?
try changing to usb 2.0, usb 3.0 sometimes not working with adb command.
much love
Thanks for saving the day voxigenboy!!! I love you man. lol
And for those that simply can't get their stupid computer to recognize the LG drivers... PDANet wins with whatever voodoo they freaking use!
Thanks for your help, rescued my evening!
voxigenboy said:
so.... I screwed up & wiped my dna. no recovery img, nothing left on it a side from recovery.
i have team win v2.5.0.0
been trying to use adb sideload to install another rom. my pc recognizes the phone & i get adb running. been trying this method:
going to "advanced" in recovery, then:
adb /kill-server
adb usb
starting up "adb sideload",
adb devices
adb sideload (romname)
every single time, it keeps saying - *failed to write data 'protocol fault (no status)' *
anyone else experience this and know how to fix it?
FIXED!!!!!!!!
--------------------------
Rather then do "sideload", I just stayed in 'Advanced' and performed:
adb /kill-server
adb usb
adb push (romname) /sdcard
it successfully copied the rom to the sdcard folder, then I was able to install the rom just fine.
Click to expand...
Click to collapse
I'm sorry, that's a bit confusing.
So are u suggesting to "sideload" by:
adb /kill-server
adb usb
starting up "adb sideload",
adb devices
adb sideload (romname)?
Waiting for your response.
Zenfone 5 a501cg (India) (WW)
Stock Recovery
This didn't work for me but I found this other way of passing the archive to my phone :
https://www.youtube.com/watch?v=Z3SpI7m7mFI