[Q] <waiting for device> on P500 - Optimus One, P500, V General

[Q] <waiting for device> on P500 - Optimus One, P500, V General

Ok so I was trying to install a custom recovery on my P500 and when it turned on it gave me this message
fast boot mode started
udc_start
Click to expand...
Click to collapse
I plug it in it gives me
fast boot mode started
--suspend--
--reset--
--port/change--
--reset--
--port/change--
Click to expand...
Click to collapse
I tried out this method: http://forum.xda-developers.com/showthread.php?t=1088046
After keying the fastboot commands in it says <waiting for device>. Some Google hits told me that it's because I don't have latest USB drivers. I'm sure I do, but I've re-installed them just to be sure. But to no avail.
I'm still on my stock ROM (untouched), phone is rooted (duh) and this is my first attempt to install a custom recovery.
Not allowed to post on that thread ofc, my first post here. All help greatly appreciated. Thanks

Here is the Simple way ..try it
this link for latest working Rom >>
http://forum.xda-developers.com/showthread.php?t=946354
how to root >>
Enable USB debugging on your phone by going to Settings –> Applications –> Development. Check the ‘USB Debugging’ option.
Make sure you have a SD card inserted and mounted in your phone (Don’t know if it’s necessary but before proceeding further I formatted my SD card after taking a backup of the data in it. Why take a risk? Smile)
Download the GingerBreak APK from XDA Developers and get it onto your phone.
Install it by browsing to the GingerBreak APK in any file manager.
Open GingerBreak from your app drawer and press the root button.
Wait for a few minutes. If there are no problems, the device will reboot itself. (The reboot will take quite some time.)
You will see a SuperUser app in your app drawer after the reboot. Open it and see if it is working.
You now have a rooted Optimus One P500 phone.
Now install custom recovery
Follow the below steps to install custom recovery on your LG Optimus One P500.
Install Android Terminal Emulator from Android Market.
Download the file "amon_ra_recovery_installer.zip" from here or here.
Check the MD5 hash value of the downloaded ‘zip’ file. You can use HashTab to do this. Right click on the downloaded file and ensure the MD5 matches 86db8a52b01f049cadb8f097a4c5bd9e.
Extract the contents of the ‘zip’ file to the root of the SD card (Don’t extract inside any folder. For example if your SD Card is mounted on J: in Microsoft Windows then the four extracted files should be right under J:/ like J:/flash_image)
Open the terminal emulator app on your phone and type ‘su’ without the quotes. This will prompt a popup on your phone from the SuperUser app asking you whether you want to give root permissions for the terminal emulator app. Click ‘Allow’ and proceed. The shell prompt will change from the previous user shell ‘$’ to root shell ‘#’ in the emulator.
Now type in the following command and press Enter. The custom recovery will be flashed on to your phone and it will reboot into Custom Recovery.
sh /sdcard/rf.sh
Shut down your phone and boot into Recovery using the Volume Down, Home and Power switch keys. You can move through the options using the volume up/down keys. Use the Menu button to select the option.
In the recovery menu, select Backup/Restore, then select Nand backup. What this will do is backup your current ROM on your SD card, if something goes wrong while flashing the new ROM you can simply boot into recovery and restore your previous ROM.
Connect the phone to your computer and inside Recovery main menu click the option ‘USB-MS toggle’ and then ‘USB-MS Toggle SDCard’. This will unmount the SD card so that you can see it in your computer. Backup everything from your SD Card. Eject from computer and toggle USB again from recovery to mount the SD card back in phone.
Though it is not a necessity for this ROM, I would suggest partitioning your SD card to create swap and ext partitions. The ext partition will come in use if you want to install apps onto your SD card later. This is different from what you see in Froyo versions of Move to SD option. Partitioning will format your SD card, so make sure you backup your SD card as mentioned in Step 3.
Go back to the recovery menu again and select ‘Partition sdcard’. Then select ‘Partition SD’. Create a swap partition of size 0 and ext partition of size 512. Once done hit Back to go again to the ‘Partition sdcard’ menu. Convert the partition you just created to ext 3 and then ext4 using the options ‘SD:ext2 to ext3’ and ‘SD:ext3 to ext4’.
Toggle USB from recovery again. Inside the SDcard create a folder AAA and copy the ROM you downloaded in Step 1 into the folder ‘AAA’ on your SDCard. Once done, eject the SD card and toggle USB again to mount the SD Card in the phone again.
Go to the Wipe option in the recovery menu and wipe userdata, /data, /sd-ext, /sdcard/.android_secure, /cache, ‘Dalvik-cache’
Then go to the Flash Zip option in the recovery menu and select the zip file you copied in Step 6.
Sit back and relax while the zip is flashed. Once recovery shows that flashing is complete, reboot phone from recovery. The first boot will take quite some time.
Enjoy Gingerbread 2.3 on your LG Optimus One P500.

@ above completely unrelated to his problem.
Sent from my LG Optimus One P500 using XDA App

Appreciate your post but it has nothing to do with query sadly.
I was doing what you've mentioned in the installing recovery section when things went wrong.
I run Win7 x64 btw.

istoner said:
Some Google hits told me that it's because I don't have latest USB drivers. I'm sure I do, but I've re-installed them just to be sure. But to no avail.
Click to expand...
Click to collapse
That is correct - drivers issue.
1/ Add DEVMGR_SHOW_NONPRESENT_DEVICES to your environment on Windows and set the value to 1. (In Advanced system settings, Google if you do not know how.) Log off and log back on.
2/ Run devmgmt.msc
3/ There, View - Show hidden devices
4/ Go thru it and uninstall everything Android-related (for starters, ADB Interface and stuff under it, Disk drives, Modems, Ports (COM and LPT), USB controllers - might not be complete list above)
5/ Reboot the PC.
6/ Install the latest drivers for your phone.
7/ If it worked, once you have plugged in the phone stuck in fastboot mode, in device manager you should see Fastboot interface (Google USB ID) in ADB Interface section.

Thanks, trying that out now.

doktornator,
Thanks a bunch. It was an issue with the drivers, I tried your method a few times with little success. Then I let Windows find the drivers (out of all the things), and that worked. Relieved and slightly embarrassed that Windows could what I couldn't

Good that it works now. Fingers crossed to unbrick your phone soon.

Oh it's unbricked and ready to go again lol.

Hi, I am on Windows XP with the exact same problem.
Have tried the B2CApp for driver updates with no luck. Tried windows automatic driver installation,again no luck.
Anything else that I could try on a Win XP machine?

UPDATE:
I have fixed the issue. Got the drivers mentioned in this thread:
Anyone else stuck with Windows XP not recognizing the device even after the B2CApp installation, try these drivers:
http://android.modaco.com/topic/324744-waiting-for-devicefastboot/#

hi guys
Same issue here...and I've had all of the above problems (missing dll, the "waiting for device" due to the absence of proper drivers, etc) . I was able to solve everything up to step 2 of the procedure, i.e., when I type "fastboot flash recovery recovery.img" I get the error message: "cannot load recovery.img".
I tried with both the .img files extracted from the CWM link and AmonRA (thinderg). Any ideas? What am I doing wrong? This is going for hours now and I'm getting desperate!

droidao said:
hi guys
Same issue here...and I've had all of the above problems (missing dll, the "waiting for device" due to the absence of proper drivers, etc) . I was able to solve everything up to step 2 of the procedure, i.e., when I type "fastboot flash recovery recovery.img" I get the error message: "cannot load recovery.img".
I tried with both the .img files extracted from the CWM link and AmonRA (thinderg). Any ideas? What am I doing wrong? This is going for hours now and I'm getting desperate!
Click to expand...
Click to collapse
is the name of the .img file recovery.img?
the command is really fastboot flash recovery (name of file).img

Yes it is...Actually I tried both ways (renaming and keeping the original name)! But I've finally figured it out!!! Here was the problem: when I installed android sdk I added the paths of the required directories (tools and platform-tools) to the system variable section so I could launch tools without writing the path all the time...However, because desperate times call for desperate (and often silly) measures, I decided to type the command cd "name-of-directory" anyway and that...made the trick.
This community is indeed great...I'm going to distribute some "thankyous" now!

I had the same problem with Win7, Updating the drivers from the device manager of w7 worked for me. Hope it helps.
Ps: will take around 15 mins updating.

Related

Update USB Drivers?

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...

Please help my nook ?

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

Complete noob here! Help for bricked 16GB NT

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...

Hisense Soundtab MA-327

Hello,
I rooted my Hisense Sountab MA-327 and changed some issues in the builds.prop (before I backup-ed this file first). There was no result for what I was doing after a successful restart, so I copied the backup file back to the system folder. After I restart the device, the system hangs in the boot. I tried to login with ADB to see whats went wrong, but I can can not find a good USB driver for this device. Can some please help me? The device is no useless.
- Is there a good USB driver for the Hisense SoundTab MA-327?
- What do I need the get in the system (ADB tools)?
- Or ... is there a flash/firmware for the Hisense Soundtab MA-327 somewhere available?
I really hope some can help me out.
Thanks in advance
Hans

kameraad759 said:
Hello,
I rooted my Hisense Sountab MA-327 and changed some issues in the builds.prop (before I backup-ed this file first). There was no result for what I was doing after a successful restart, so I copied the backup file back to the system folder. After I restart the device, the system hangs in the boot. I tried to login with ADB to see whats went wrong, but I can can not find a good USB driver for this device. Can some please help me? The device is no useless.
- Is there a good USB driver for the Hisense SoundTab MA-327?
- What do I need the get in the system (ADB tools)?
- Or ... is there a flash/firmware for the Hisense Soundtab MA-327 somewhere available?
I really hope some can help me out.
Thanks in advance
Hans
Click to expand...
Click to collapse
Some please!

What I understood:
You are stuck in a bootloop because you edited the build.prop file, luckily, you made a backup and you know what adb is, and, hopefully, you know how to use it.
How do we solve it?
Well, I need some more information, can you boot into recovery or boot into fastboot mode? If you can, we can make your backup build.prop file active and if that doesn't work, we can just reflash stock ROM, everything will be wiped if you flash stock ROM though.

Hi RAZERZDAHACKER,
Thanks for your help. Yes I can boot into recovery/boot mode (android robot with sign and even can see the menu (Volume + Start). I tried to make an USB connection, but I can not find any driver for this device. Under XP I find a good USB driver, but then ADB want install, in Windows 7 or 10 its the opposite. And even with some not good driver, I see with the command "adb devices": No access, and then 1234567890ABCDEF. Can not find any driver. If possible its no problem to reflash stock ROM, but I do not know how to do this.
I appreciate your help.
Hans

kameraad759 said:
Hi RAZERZDAHACKER,
Thanks for your help. Yes I can boot into recovery/boot mode (android robot with sign and even can see the menu (Volume + Start). I tried to make an USB connection, but I can not find any driver for this device. Under XP I find a good USB driver, but then ADB want install, in Windows 7 or 10 its the opposite. And even with some not good driver, I see with the command "adb devices": No access, and then 1234567890ABCDEF. Can not find any driver. If possible its no problem to reflash stock ROM, but I do not know how to do this.
I appreciate your help.
Hans
Click to expand...
Click to collapse
Thanks for replying, you can boot into recovery which is probebly the most vital thing of this whole process (YaY), in recovery, there should be an option called "apply update from adb", if not, kindly name the options. When you click it, what happens in adb? From my experience you don't need drivers to acces "adb sideload" (as the feature is called).

Yes I see the option.
--------
Now send the package you want to apply
to the device with "adb sideload <filename>" ....
---------
I made the backup build.prop earlier to /sdcard on the device. Maybe that was not a good idea.
Oke whats the next step?
Hans

kameraad759 said:
Yes I see the option.
--------
Now send the package you want to apply
to the device with "adb sideload <filename>" ....
---------
I made the backup build.prop earlier to /sdcard on the device. Maybe that was not a good idea.
Oke whats the next step?
Hans
Click to expand...
Click to collapse
Oh, I thought you had it on the pc, I am not sure but can you do "adb sideload /sdcard/build.prop /system"?

RAZERZDAHACKER said:
Oh, I thought you had it on the pc, I am not sure but can you do "adb sideload /sdcard/build.prop /system"?
Click to expand...
Click to collapse
That don't work. I get the help of adb when I give the command string. Do not know how this will work with a USB connection. How should Windows and adb know when to get the input from?
when i try adb usb, it start the daemon , but then error: closed
adb devices -> 0123456789ABCDEF sideload
Oke maybe a reflash stock ROM. How does this work?
Again I appreciate all your help.
Hans

kameraad759 said:
That don't work. I get the help of adb when I give the command string. Do not know how this will work with a USB connection. How should Windows and adb know when to get the input from?
when i try adb usb, it start the daemon , but then error: closed
adb devices -> 0123456789ABCDEF sideload
Oke maybe a reflash stock ROM. How does this work?
Again I appreciate all your help.
Hans
Click to expand...
Click to collapse
You get error closed because you're in sideload, I realized that you can't move files in adb sideload. If you want to flash stock ROM, download this and move it to the adb folder and type "adb sideload nameoftheimg.img".
Hope that helps

RAZERZDAHACKER said:
You get error closed because you're in sideload, I realized that you can't move files in adb sideload. If you want to flash stock ROM, download this and move it to the adb folder and type "adb sideload nameoftheimg.img".
Hope that helps
Click to expand...
Click to collapse
I will try that of course, but the same image I previously put on SDCARD, inserted it in the bay and dis an update from external drive. Then a message came that hardware was not compatible with the update. I can not find a flash for MA-327 and (again) not for the USB driver. But I will try what you suggest.

I get the error: cannot read 'MA347ENMEG3EV02.img'
Image is 1.744.423.512 size
Hans

kameraad759 said:
I get the error: cannot read 'MA347ENMEG3EV02.img'
Image is 1.744.423.512 size
Hans
Click to expand...
Click to collapse
If you have a sdcard that is large enough for the image (minimum 4gb) you can download win32diskimager. Open win32diskimager and select the .img file. Then, connect your sdcard to your pc and format it to fat32. Then locate it on win32diskimager and write the file. This will take a very long while so please be patient. Once it's done, put it in the hisense and attempt to boot. The android "bios" will go through all the nand memory for a bootable image but since that wont work, it will proceed to check external devices (as far as I know) and once it sees the bootable sdcrad it will, hopefully boot. Once you have booted, don't eject the sdcard, conncect the hisense to your pc and install the necessary adb drivers, then, boot into recovery and hit apply update from adb. Then type adb sideload nameoftheimg.img.
Hopefully that works

Oke. But if it boot from sdcard, then it will not install the img from sdcard?? I though it would.
What are the 'necessary adb drivers'?
And when i give the command "adb sideload nameoftheimg.img, will it get the img from sdcard OR from PC?
So the image is on SDcard AND on the PC? I do not get it (sorry)

kameraad759 said:
Oke. But if it boot from sdcard, then it will not install the img from sdcard?? I though it would.
What are the 'necessary adb drivers'?
And when i give the command "adb sideload nameoftheimg.img, will it get the img from sdcard OR from PC?
So the image is on SDcard AND on the PC? I do not get it (sorry)
Click to expand...
Click to collapse
Not as far as I know, I could be wrong, it could install from it. As far as the adb driver goes this is what I meant, you manually install them. Yes, the image is on both the pc and sdcrad.

RAZERZDAHACKER said:
Not as far as I know, I could be wrong, it could install from it. As far as the adb driver goes this is what I meant, you manually install them. Yes, the image is on both the pc and sdcrad.
Click to expand...
Click to collapse
Hello (again)
It will not boot from the sd card. I formatted it FAT32, used Win32DiskManager to write the .img on it, place the sdcard in the hisense and booted it. Press ON. System will not boot on sdcard. Instead it boot from disk. I see the same logo as before, Hisense Smart. It ignores the sdcard.
Booted it in recovery mode (with inserted SDcard). ADB sideload xxx.img, gave same answer: cannot read MAxxx.img. Other option in the recovery mode like update from external image (i hoped the sdcard) does not work either (can not find any /mnt ect file).
How can I force to boot from sdcard? Is the sdcard now bootable (with win32diskmanager). I used Rockchip Create Upgrade Tool 1.43 also, but this app crash when it want to write to SDcard.
No luck with me till now. Is my device saveable at all? Why does it not see the sdcard?
Hans

kameraad759 said:
Hello (again)
It will not boot from the sd card. I formatted it FAT32, used Win32DiskManager to write the .img on it, place the sdcard in the hisense and booted it. Press ON. System will not boot on sdcard. Instead it boot from disk. I see the same logo as before, Hisense Smart. It ignores the sdcard.
Booted it in recovery mode (with inserted SDcard). ADB sideload xxx.img, gave same answer: cannot read MAxxx.img. Other option in the recovery mode like update from external image (i hoped the sdcard) does not work either (can not find any /mnt ect file).
How can I force to boot from sdcard? Is the sdcard now bootable (with win32diskmanager). I used Rockchip Create Upgrade Tool 1.43 also, but this app crash when it want to write to SDcard.
No luck with me till now. Is my device saveable at all? Why does it not see the sdcard?
Hans
Click to expand...
Click to collapse
It is saveable, can you give me the link to the .img file? The fact that it says "cannot read" might be that the image file is corrupt. Are you sure you are typing the right name? You can do adb sideload then type the first letter (if it is a big letter type it as big for example Achicken, type A, if it is aCHICKEN, type it as a) and hit tap, that will ensure you have the exact name and dont tamper with it as in add .img at the end.

RAZERZDAHACKER said:
It is saveable, can you give me the link to the .img file? The fact that it says "cannot read" might be that the image file is corrupt. Are you sure you are typing the right name? You can do adb sideload then type the first letter (if it is a big letter type it as big for example Achicken, type A, if it is aCHICKEN, type it as a) and hit tap, that will ensure you have the exact name and dont tamper with it as in add .img at the end.
Click to expand...
Click to collapse
Yes I always give first letter tap. This is what I typed
adb sideload M (and then tap) => adb sideload MA347ENMEG3EV02.img
https://docs.google.com/uc?id=0Bwr18Lh81gvJazJXTGFQTnhDSEk&export=download
Its a rar. I unzipped it with 7-zip
I tryed also adb shell. But device is unauthorized and I get eroor $ADB)VENDOR_KEYS not set (even when I deleted .android in my users dir. Do not get any permission question on device also. My hope is still a bootable SDCard and image.
Thanks

kameraad759 said:
Yes I always give first letter tap. This is what I typed
adb sideload M (and then tap) => adb sideload MA347ENMEG3EV02.img
https://docs.google.com/uc?id=0Bwr18Lh81gvJazJXTGFQTnhDSEk&export=download
Its a rar. I unzipped it with 7-zip
I tryed also adb shell. But device is unauthorized and I get eroor $ADB)VENDOR_KEYS not set (even when I deleted .android in my users dir. Do not get any permission question on device also. My hope is still a bootable SDCard and image.
Thanks
Click to expand...
Click to collapse
Might seem crazy but check this out, try with your image then his image(s). Remember, booting from an sdcrad is extremely slow, It can actually take 24hours depending on the speed fo your sdcrad so before trying this I suggest you leave it for a day.

RAZERZDAHACKER said:
Might seem crazy but check this out, try with your image then his image(s). Remember, booting from an sdcrad is extremely slow, It can actually take 24hours depending on the speed fo your sdcrad so before trying this I suggest you leave it for a day.
Click to expand...
Click to collapse
Oke, I will wait for a while. But it seems it just hangs in the normal boot.
Thanks for so far. I will report back after the weekend with hopely good news
Hans

I waited for 48hours but nothing happens. Still the screen Hisense Smart.
So it will not boot from SD card and I can not external mount with adb.
When I go in recover mode I see message:
failed to mount /mnt/external_sd (No such device)
SDCard is raw formatted. Can not browse with Windows SDCard. Maybe it should be wrotten different so I can see /mnt/external_sd
Maybe you have a good idea this week for me.
Hans

[GUIDE] [Fix] Dreamtab hangs at characters.

Symptoms
The classic symptoms of the issue are at some point the Nvidia Dreamtab will stop booting and hang at the Dreamworks characters screen and never boot any further. The frequency ranges from once a month to a year. You are able to factory reset and the issue goes away for some periodicity and then returns.
NOTE: If you recently bought a new Nvidia Dreamtab and you have this character freeze right after doing the OTA then this probably isn't the issue, I am working on a different fix for that problem in this thread. If however this solution does fix your issue I'd like to hear about it.
Background
The tablet uses the linux ext4 filesystem. The Dreamtab kernel requests a filesystem check every 20 partition mounts(typically during reboots) or when the files system is marked dirty(the tablet is hard powered off, or some other glitch). The tablet is missing the fsck binary which is the filesystem checker similar to what you might have seen in windows with chkdsk. Without this file the tablet can not check filesystem and the kernel waits indefinitely for that to happen and your tablet sits and the Dreamworks characters.
Solution
Temporarily boot to a program(TWRP) that can install the filesystem file on the tablet. To temporarily boot to TWRP the bootloader must be unlocked. The unlock procedure requires erasing all information on the tablet which isn't an issue if you are currently experiencing the problem as a factory reset was the only way to recover anyway. If you have a working tablet and want to apply this fix you should find a way to backup your files prior to attempting this. To better understand how the low level Nabi functions this should be required reading and will help better understand what you are doing. http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
Procedure
Only for Nvidia Dreamtab NV08B. Use this at your own risk, your warranty is void. You will lose all personal data on the device
Link to video Youtube video installation
1) Down load the drivers.
-- There are 3 popular options included in the link from above in the driver section of the Nabi General Information thread. Have them handy for the next step.
2) Download TWRP recovery.
-- The file is attached at bottom of post. DTTWRPinstaller300.zip
-- Note: You can automate some of the bootloader unlock and installing TWRP steps below with the install.bat file if you have a working Nabi.
3) Download the fsck patch.
-- The file is attached at bottom of post. NV08B_FSCK_PATCH.zip
4) Reboot to fastboot protocol
-- With Nabi powered off press and hold the power button and the vol + button until a small menu(bootloader menu) appears. Quickly release both buttons or the tablet will start booting normally. Using the vol- button to highlight the fastboot protocol(2nd option from top) and then press the vol+ button to select it. Note: Depending on if the drivers are installed the screen will change or stay the same.
5) Verify drivers installed or install drivers.
-- Open windows device manager. On Windows 10 type "device manager" in to the Cortana search bar. On other versions open run by pressing the "windows key" in lower left of keyboard while also pressing R key. Then type: devmgmt.msc
-- If you have "Android Device" and it's sub menu says bootloader/fastboot then you are set up. If down by "other devices" you have an unknown device then you will need to install the drivers from the selection and download you made from reading the Nabi General Information thread.
6) Unlock the bootloader
-- This step will ERASE ALL information on the tablet.
-- Unzip the DTTWRPinstaller300.zip to a location of your choosing. If you use Windows built in unzip utility make sure you check the box that says to open when unzipping is complete.
-- Hold the shift key on the keyboard while right clicking on the "files" folder. Then select "open command window here"
-- At the prompt type:
Code:
fastboot oem unlock
Note: You need to move quickly to the tablet and do the next step as there is a timeout
-- On the tablet it will ask if you want to unlock. Using the vol- key select "yes" with vol+ or pwr. If you do this properly in the command window on your computer it will tell you it is erasing the device.
7) Temporary boot TWRP
-- I can't remember if after the bootloader unlock if tablet is at fastboot, or if you have to power off the tablet and do step 4 again. I think you can just proceed.
-- At the prompt type
Code:
fastboot boot recovery.img
8) Get the patch file on the tablet
-- Option A: There are a couple options for this. Check the file explorer on your computer. If you see t8400n as a device you can just copy and paste the NV08B_FSCK_PATCH.zip to the internal storage by copy and pasting in windows. Go to step 9.
-- Option B: Insert a microSD card in your computer and copy the NV08B_FSCK_PATCH.zip to your microsd card and insert the sdcard in the tablet.
-- Option C: If the t8400n does not show up on your computer then you will need to transfer via ADB. This will require you to setup the ADB driver like you did for fastboot in step 5. Now in sub Android Device in Device Manager you should see ADB, if you don't install driver.
--Copy the NV08B_FSCK_PATCH.zip to the "files" folder where you extracted DTTWRPinstaller300.zip. It should be in a folder with adb, fastboot, AdbWinAPi, etc
-- At the command prompt type:
Code:
adb push NV08B_FSCK_PATCH.zip /sdcard
9) Install patch
-- In TWRP on tablet click the install tab. Generally you will now see the NV08B_FSCK_PATCH.zip if you picked option A or C. If not navigate to the sdcard folder. If you picked option B navigate up a folder and find external_sdcard folder and look in there.
Note: For external_sdcard it may be necessary to exit to TWRP main menu and select mount tab and make sure Micro SDcard is checked.
-- Once you have found the NV08B_FSCK_PATCH.zip from inside the install tab you can select it and then swipe to install. You should get verification it completed normally.

I know this is rather old, but I have a couple of these tablets I'm trying to get working again to give to a friend's kids, but this doesn't seem to work. Did you have to have USB debugging checked before the tablets stopped booting in order for this to work properly?
Basically I can do all the fastboot stuff without any errors, but when I try to boot to TWRP all the tablets do is pretty much rotate the screen 180° so the bootloader screen is in the opposite corner and the volume buttons no longer work until I hold power for ten seconds to power it off... Any help is greatly appreciated!

Better Mobile App

welcome