Many people are getting what they are calling a bricked Nook tablet that won't boot or restore an OS. Often when they boot into CWM (from internal or SD) they get errors on screen, or possibly after an attempted install they show in the advanced / log
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/
failed to open/sys/class/android_usb/state: No such file or directory
This is actually an extremely common issue it seems. Basically its' quite likely you're partition map has some how been damaged.
Firstly just make sure you can't install an update or restore an old backup from SD, if that still fails and you end up straight back in CWM
All you need to do is download the parted binary HERE extract it from the archive and push it to your device or even just put it on an SD
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)
parted /dev/block/mmcblk0 print
It will most likely show up with an error and ask if you want to fix it. Just say yes and let it do its' thing.
After it completes, reboot your device and see if you still get the same errors, Attempt to install CM7 once more.
If it still doesn't work, run the parted command again then download Adams total wipe and run that. It'll reset your device back to total stock. The parted command will repair the partition table and adamoutlers software will upload all the required software to the correct places for it all to work
Hope that helps!
If you get stuck feel free to give me a shout
This is actually an extremely common issue it seems. Basically its' quite likely you're partition map has some how been damaged.
NT full brick...unable to recover.
My NT is suffering from the CM7-SD format brick problem.
I have hunted high and low for instructions on how to get ADB to work on a bricked NT. My NT is in a state where the only thing that boots on it is an SD-based CWM, but when I plug the NT into a PC, no matter what I do, CWM recovery starts up and the PC detects the unit as disk drives. ADB will NOT find the unit. I have tried on two separate Win7 machines...same problem on both.
I have also tried using Adam's total wipe fix, and while linux boot, the full wipe just hangs forever on the first step (zeroing MLO).
I am not sure I have the right USB drivers...basically, I'm using the ones I had for my long-gone Nook Color.
Can anyone offer me some help?
Thanks.
imacmill said:
My NT is suffering from the CM7-SD format brick problem.
I have hunted high and low for instructions on how to get ADB to work on a bricked NT. My NT is in a state where the only thing that boots on it is an SD-based CWM, but when I plug the NT into a PC, no matter what I do, CWM recovery starts up and the PC detects the unit as disk drives. ADB will NOT find the unit. I have tried on two separate Win7 machines...same problem on both.
I have also tried using Adam's total wipe fix, and while linux boot, the full wipe just hangs forever on the first step (zeroing MLO).
I am not sure I have the right USB drivers...basically, I'm using the ones I had for my long-gone Nook Color.
Can anyone offer me some help?
Thanks.
Click to expand...
Click to collapse
It's not actually caused by formatting SD on CM7 any more. you could happily format your SD all day, although we still recommend not formatting anything at all via the NT.
If you have CWM you should have access to ADB, the probably reason it doesn't work for you is that you need to tell your computer what the id is on the device so that it can recognise it. What operating system are you using?
CelticWebSolutions said:
It's not actually caused by formatting SD on CM7 any more. you could happily format your SD all day, although we still recommend not formatting anything at all via the NT.
If you have CWM you should have access to ADB, the probably reason it doesn't work for you is that you need to tell your computer what the id is on the device so that it can recognise it. What operating system are you using?
Click to expand...
Click to collapse
Thanks, Celtic.
I'm on Win7. I have 'adb_usb.ini' in folder:
C:\Users\<myname>\.android
And the 'ini' contains 0x2080.
More details...
CelticWebSolutions said:
It's not actually caused by formatting SD on CM7 any more. you could happily format your SD all day, although we still recommend not formatting anything at all via the NT.
If you have CWM you should have access to ADB, the probably reason it doesn't work for you is that you need to tell your computer what the id is on the device so that it can recognise it. What operating system are you using?
Click to expand...
Click to collapse
Here's a brief history, as best I can recall, of how I got where I am with my NT.
1. Installed NT CM7 about a week ago. All worked well until I noticed Kindle app misbehaving by not flipping pages on a book. I tried same book on two other android devices, and both worked fine. So...
2. In a complete act of stupidity, I went into 'Storage' on the NT, and noticing that there were 3 sections listed there (whose names escape me, but something like 'Internal SD', 'SD' and 'External SD'), I formatted all 3 (yup, dumb).
3. I shut down the NT (10 second press of power), and from there on in, tablet hung at 'N' screen. I manages to get CWM to start, using a combination of buttons I now don't recall (Power and Volume Up, perhaps?).
4. For reasons I can only describe as lunacy, I used Recovery to format everything it listed as format-able (under Mounts/Storage). From this point on, the tablet would not boot at all, not even back into CWM Recovery.
5. Thru online searching, I found an image for making a bootable CWM Recovery, which I created and used successfully to boot into recovery. I used it unsuccessfully to try to re-install CM7.
6. I then tried getting an ADB connection so I could try the various other fixes offered online, but have been completely unable to get a connection. I followed the instructions found in XDA thread ID 1424563 (sorry, I'm too junior to have link-posting permissions), but the thread assumes I can get to the NT's settings to turn on debug mode, which I can't.
7. As mentioned, I also tried Adam's full wipe/restore, but it hangs on phase one (zeroing MLO).
That's the crux of it, for what it's worth. I think my big issue right now is not being able to get ADB to work with it. If I could, I could try the partition command you gave in the OP.
Thanks for any help or ideas...
imacmill said:
Here's a brief history, as best I can recall, of how I got where I am with my NT.
1. Installed NT CM7 about a week ago. All worked well until I noticed Kindle app misbehaving by not flipping pages on a book. I tried same book on two other android devices, and both worked fine. So...
2. In a complete act of stupidity, I went into 'Storage' on the NT, and noticing that there were 3 sections listed there (whose names escape me, but something like 'Internal SD', 'SD' and 'External SD'), I formatted all 3 (yup, dumb).
3. I shut down the NT (10 second press of power), and from there on in, tablet hung at 'N' screen. I manages to get CWM to start, using a combination of buttons I now don't recall (Power and Volume Up, perhaps?).
4. For reasons I can only describe as lunacy, I used Recovery to format everything it listed as format-able (under Mounts/Storage). From this point on, the tablet would not boot at all, not even back into CWM Recovery.
5. Thru online searching, I found an image for making a bootable CWM Recovery, which I created and used successfully to boot into recovery. I used it unsuccessfully to try to re-install CM7.
6. I then tried getting an ADB connection so I could try the various other fixes offered online, but have been completely unable to get a connection. I followed the instructions found in XDA thread ID 1424563 (sorry, I'm too junior to have link-posting permissions), but the thread assumes I can get to the NT's settings to turn on debug mode, which I can't.
7. As mentioned, I also tried Adam's full wipe/restore, but it hangs on phase one (zeroing MLO).
That's the crux of it, for what it's worth. I think my big issue right now is not being able to get ADB to work with it. If I could, I could try the partition command you gave in the OP.
Thanks for any help or ideas...
Click to expand...
Click to collapse
you should have damaged the partition tables, so please make a CMW card first, and then you can use adb shell to repair the partition table.
you can refer to this thread:http://forum.xda-developers.com/showpost.php?p=22157605&postcount=25
If that older driver you have don't work, you can find a driver in this thread. (I don't know if they are the same as color or not TBH)
Use the USBDeview to rid yourself of anything aldroid related, anything Google related, and any mass storage devices. Restart PC, then plug your NT in. (This is how I had to do it...many times)
ms2003 said:
you should have damaged the partition tables, so please make a CMW card first, and then you can use adb shell to repair the partition table.
you can refer to this thread:http://forum.xda-developers.com/showpost.php?p=22157605&postcount=25
Click to expand...
Click to collapse
Thanks, ms, but as I mentioned, I am completely unable to get ADB to work. It will not find the tablet. When I plug the tablet in to my Win7 box, the installed CMW card boots the tablet into recovery, and the PC detects it as disk drives (as seen in Win7's Device Mangler).
Quick progress update...
Know-Fear said:
If that older driver you have don't work, you can find a driver in this thread. (I don't know if they are the same as color or not TBH)
Use the USBDeview to rid yourself of anything aldroid related, anything Google related, and any mass storage devices. Restart PC, then plug your NT in. (This is how I had to do it...many times)
Click to expand...
Click to collapse
The old drivers and instructions you linked to worked...ADB now finds my NT! Thanks much!
Now...
I did the 'parted' thing, and while 3 or 4 errors were reported thru the process, it stated it completed successfully. I then rebooted with my CWM Recovery SD card and attempted to re-install CM7. The installer completed quite quickly and without errors, but it did not work (as I suspected it wouldn't, given how fast it executed). I then ran 'Brick_fix.zip', and it, too, completed successfully (well, except for the ping at the end), but I was unable to install CM7. So...
I'm now on to Adam's fix (note in the OP) and I'm glad to report it's working now. It got past the first stage (zeroing MLO) and is in the middle of 'flashing factory'. Sweet!
I'll report back in the morning, hopefully with good news. Thanks so much for the help, everyone.
imacmill said:
The old drivers and instructions you linked to worked...ADB now finds my NT! Thanks much!
Now...
I did the 'parted' thing, and while 3 or 4 errors were reported thru the process, it stated it completed successfully. I then rebooted with my CWM Recovery SD card and attempted to re-install CM7. The installer completed quite quickly and without errors, but it did not work (as I suspected it wouldn't, given how fast it executed). I then ran 'Brick_fix.zip', and it, too, completed successfully (well, except for the ping at the end), but I was unable to install CM7. So...
I'm now on to Adam's fix (note in the OP) and I'm glad to report it's working now. It got past the first stage (zeroing MLO) and is in the middle of 'flashing factory'. Sweet!
I'll report back in the morning, hopefully with good news. Thanks so much for the help, everyone.
Click to expand...
Click to collapse
Sorry I didn't get back to you last night, I had already gone to bed, looks like you've already got the help you need though. If the wiping had started to work you'll be fine lesson learnt though, DO NOT FORMAT ANYTHING ON NT
Let us know it's fixed (which I'm sure it will be )
Bad news...
CelticWebSolutions said:
Sorry I didn't get back to you last night, I had already gone to bed, looks like you've already got the help you need though. If the wiping had started to work you'll be fine lesson learnt though, DO NOT FORMAT ANYTHING ON NT
Let us know it's fixed (which I'm sure it will be )
Click to expand...
Click to collapse
Well, the news is bad this morning. As someone mentioned in Adam's post, during the install, the screen went blank, so I left it for about another half an hour, then powered the device off and restarted it. All appeared OK, as the B&N firmware stated that it was clearing data, but that process froze for a long while, then a message popped up stating "Please restart your device and try again. If you encounter the same issue, contact technical support at blah, blah, blah." I restarted...same message. Over and over.
I tried the full wipe no less than 4 more times, preceding each attempt with a 'part' command, but the full wipe, for some unknown reason, stops about 60 seconds in, and pops up what appears to be a windowed 'ls -al'. I tried two different class 4 SDs in the 4 attempts...same for each.
Not feeling hopeful at this point.
---------- Post added at 04:37 PM ---------- Previous post was at 03:46 PM ----------
Here's the results from my 'part' command:
Code:
~ # parted /dev/block/mmcblk0 print
parted /dev/block/mmcblk0 print
Model: MMC SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 16.3MB 15.7MB recovery
4 16.8MB 33.6MB 16.8MB boot
5 33.6MB 83.9MB 50.3MB rom
6 83.9MB 134MB 50.3MB fat32 bootdata
7 134MB 522MB 388MB factory
8 522MB 1164MB 642MB ext4 system
9 1164MB 1611MB 447MB ext4 cache
10 1611MB 2684MB 1074MB fat32 media
11 2684MB 15.6GB 12.9GB ext4 userdata
Note the fat32 and ext4 file system designations for various directories (is directories the correct word?). On page 6 of Adam's full wipe thread, user 'howcansheslap' shows the output of his/her 'part' command, and the file system in his/her output is all blank. Perhaps not coincidentally, my full wipe process stops on processing 'bootdata', the first item listed as fat32 above, and displays the windowed 'ls' of folder 'bootdata'.
Any thoughts on the relevance of this info?
Thanks all.
---------- Post added at 05:33 PM ---------- Previous post was at 04:37 PM ----------
Turns out the full wipe *was* working. The trouble is, my impatience got the better of me. Adam's wipe process does not provide a whole lot in the way of progress feedback, and in fact, it can be 5 minutes or so before you see anything meaningful on screen. Best advice: give the process a full half hour to complete and don't assume that it's hung/stopped working just because you see virtually no progress reports. Note also that if you touch the screen anywhere during the wipe, any progress bar that may or may not have been present will probably disappear, and you won't see another one displayed for possibly several minutes.
My apologies to all for subjecting you to my own impatience, and a big thank-you for all the help.
I spoke too soon...again.
The full wipe/restore completed successfully, but now when I start the tablet, I get taken thru the B&N setup process and at the stage where it asks me to login to my B&N account, I get:
Error
Sorry we're having trouble setting up your NOOK. Please shutdown the device and try again. If the problem persist, contact Customer Support at...
Well, the problem has persisted all day. I have even done the full restore a couple of extra times. And the tech support line just keeps telling me they're unable to process my call at this time.
I am definitely able to login to my B&N account thru my PC, so I've got the credentials right.
Has anyone encountered this before?
UPDATE: I followed the instructions for bypassing registration, found here:
http://nookdevs.com/NookColor_Factory_Mode/Skip_Oobe
This allowed me to get into settings and 'erase/unregister' the device, but alas, still no joy after a reboot.
back from brick to Nook Tablet
Hi to all, i had the same problem as imacmill onlly i've idiotly erased the "SD card" the 1 gb amount.
After restarting the NT did not boot. I've entered in CWM recovery... and had the same problem (***up my partition table)
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/
after agonizing 3hrs we succeeded to repair my NT via parted with ADB.
I've attached the log from adb.
Code:
<6> boxer : boxer_spi_probe called , line 310
<6>boxer: spi setup returned : 0
<6> boxer : boxer_panel_probe called , line 129
<4>omap_smartreflex_disable_reset_volt: omap_sr struct for sr_core not found
<4>omap_smartreflex_enable: omap_sr struct for sr_core not found
<6>Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
<6>omap-hsuart.0: ttyO0 at MMIO 0x4806a000 (irq = 104) is a OMAP UART0
<6>console [ttyO0] enabled
<6>omap-hsuart.1: ttyO1 at MMIO 0x4806c000 (irq = 105) is a OMAP UART1
<6>omap-hsuart.2: ttyO2 at MMIO 0x48020000 (irq = 106) is a OMAP UART2
<6>omap-hsuart.3: ttyO3 at MMIO 0x4806e000 (irq = 102) is a OMAP UART3
<6>brd: module loaded
<6>loop: module loaded
<6>android init
<6>android_probe pdata: c0563eb8
<6>android_bind
<7>android_bind_config
<6>android_usb gadget: android_usb ready
<6>f_adb init
<6>android_register_function adb
<6>f_mass_storage init
<6>fsg_probe pdev: c0563c00, pdata: c0563ea8
<6>android_register_function usb_mass_storage
<6>android_usb gadget: Mass Storage Function, version: 2009/09/11
<6>android_usb gadget: Number of LUNs=2
<6> lun0: LUN: removable file: (no medium)
<6> lun1: LUN: removable file: (no medium)
<6>adb_bind_config
<6>input: gpio-keys as /devices/platform/gpio-keys/input/input0
<6>input: omap-keypad as /devices/platform/omap-keypad/input/input1
<6>ft5x06_init() - FT I2C Touchscreen Driver (Built Jan 11 2012 @ 09:02:56)
<6>ft5x06_probe() - FT5x06 found on I2C bus.
<7>ft5x06_reset_panel_via_gpio() - Toggling GPIO 39 to reset the Touch Panel...
<4>omap_smartreflex_disable_reset_volt: omap_sr struct for sr_core not found
<4>omap_smartreflex_enable: omap_sr struct for sr_core not found
<6>android_usb gadget: high speed config #1: android
<6>input: ft5x06-i2c as /devices/platform/i2c_omap.2/i2c-2/2-0038/input/input2
<6>ft5x06_initialize() - sysfs_create_group() succeeded.
<6>kxtf9 1-000f: WHO_AM_I = 0x01
<6>input: kxtf9_accel as /devices/virtual/input/input3
<6>using rtc device, twl_rtc, for alarms
<6>twl_rtc twl_rtc: rtc core: registered twl_rtc as rtc0
<6>i2c /dev entries driver
<6>Linux video capture interface: v2.00
<4>max17042: max17042_init ...
<4>max17042: max17042_probe ...
<4>max17042: next history save at 4294936947
<4>max17042: max17042_probe > IRQ is 225
<4>max17042 GPIO pin read 1
<4>max17042: max17042_device_power_on ...
<4>max17042: max17042_hw_init ...
<4>max17042: BATTERY Detected!
<4>config = 0x2214
<4>Valert = 0xff9b
<4>Salert = 0xff05
<4>config = 0x2214
<4>config = 0x2214
<4>shdntimer = 0x0002
<4>max17042: max17042_verify ...
<6>max17042 1-0036: Version = 0x0092
<6>max17042 1-0036: support ver. 1.0.0 enabled
<4>MAX8903: Charger registering!
<4>MAX8903: Charger Initializing...
<4>MAX8903: Request CHARGER FLT IRQ successfully!
<4>MAX8903: Charger detected at boot = 1
<4>MAX8903: USB_EVENT_VBUS: Charger=5
<6>OMAP Watchdog Timer Rev 0x00: initial timeout 60 sec
<6>cpuidle: using governor ladder
<6>cpuidle: using governor menu
<6>omap_pwm_led omap_pwm_led: OMAP PWM LED (lcd-backlight) at GP timer 11/0
<7>Registered led device: lcd-backlight
<4>[BL set power] 1
<6>logger: created 64K log 'log_main'
<6>logger: created 256K log 'log_events'
<6>logger: created 64K log 'log_radio'
<6>logger: created 64K log 'log_system'
<6>proc4430_drv_initializeModule
<6>omap-devicehandler omap-devicehandler.0: omap_devh_probe: adding devh Tesla
<6>omap-devh initialized Tesla, major: 241, base-minor: 0
<6>omap-devicehandler omap-devicehandler.1: omap_devh_probe: adding devh SysM3
<6>omap-devh initialized SysM3, major: 241, base-minor: 1
<6>omap-devicehandler omap-devicehandler.2: omap_devh_probe: adding devh AppM3
<6>omap-devh initialized AppM3, major: 241, base-minor: 2
<6>omap3epd-sound: Audio SoC init
<6>Found Board EVT 2.1-ABE support Enabled
<6>asoc: null-codec-dai <-> MultiMedia1 LP mapping ok
<6>asoc: null-codec-dai <-> MultiMedia2 mapping ok
<3>tlv320aic3100_init: Unable get gpio for CODEC POWER 101
<6>mmc0: new high speed DDR MMC card at address 0001
<6>mmcblk0: mmc0:0001 SEM16G 14.8 GiB
<6> mmcblk0: p1
<4>mmc1: host does not support reading read-only switch. assuming write-enable.
<6>mmc1: new high speed SDHC card at address b368
<6>mmcblk1: mmc1:b368 SD04G 3.66 GiB
<6> mmcblk1: p1
<1>##-tlv320aic3100_init
<6>Created the sysfs Files for Audio Driver
<4>Page 4 has 41 Coefficient Values
<4>Page 8 has 61 Coefficient Values
<4>Updated Page 8 DAC Coefficient Control Reg for Adaptive Mode
<6>asoc: tlv320aic3100-dai <-> omap-mcbsp-dai.1 mapping ok
<6>input: OMAP4_ACCLAIM_ABE Headset Jack as /devices/platform/soc-audio/sound/ca
rd0/input4
<6>ALSA device list:
<6> #0: OMAP4 Acclaim AIC3100 ABE
<6>Netfilter messages via NETLINK v0.30.
<6>nf_conntrack version 0.5.0 (14615 buckets, 58460 max)
<4>CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use
<4>nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option or
<4>sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
<6>ctnetlink v0.93: registering with nfnetlink.
<6>xt_time: kernel timezone is -0000
<6>ip_tables: (C) 2000-2006 Netfilter Core Team
<6>arp_tables: (C) 2002 David S. Miller
<6>TCP cubic registered
<6>Initializing XFRM netlink socket
<6>NET: Registered protocol family 10
<6>lo: Disabled Privacy Extensions
<6>Mobile IPv6
<6>IPv6 over IPv4 tunneling driver
<6>sit0: Disabled Privacy Extensions
<6>ip6tnl0: Disabled Privacy Extensions
<6>NET: Registered protocol family 17
<6>NET: Registered protocol family 15
<6>ThumbEE CPU extension supported.
<4>omap_hwmod: Initialize debugfs support
<3>Power Management for TI OMAP4.
<6>prcm_clear_statdep_regs: Clearing static depndencies
<3>CPUidle for CPU0 registered
<3>CPUidle for CPU1 registered
<4>sr_init: No PMIC hook to init smartreflex
<6>smartreflex smartreflex.0: omap_smartreflex_probe: SmartReflex driver initial
ized
<6>smartreflex smartreflex.1: omap_smartreflex_probe: SmartReflex driver initial
ized
<6>smartreflex smartreflex.2: omap_smartreflex_probe: SmartReflex driver initial
ized
<7>Disabling unused clock "auxclk4_src_ck"
<7>Disabling unused clock "hdq1w_fck"
<7>Disabling unused clock "gpmc_ick"
<7>Disabling unused clock "gpio4_dbclk"
<7>Disabling unused clock "efuse_ctrl_cust_fck"
<6>VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
<6> boxer : boxer_panel_enable called , line 233
<6> boxer : boxer_panel_start called , line 150
<6>regulator_init_complete: disabling VANA
<6>twl_rtc twl_rtc: setting system clock to 2012-03-02 10:59:45 UTC (1330685985)
<6>omap_vout omap_vout: : registered and initialized video device 0
<6>omap_vout omap_vout: : registered and initialized video device 1
<6>omap_vout omap_vout: : registered and initialized video device 2
<6>omap_wb: registered and initialized wb device 4 [v4l2]
<6>Freeing init memory: 212K
<3>init: cannot open '/initlogo.rle'
<3>init: Unable to open persistent property directory /data/property errno: 2
<6>enabling adb
<6> boxer : boxer_panel_suspend called , line 245
<6> boxer : boxer_panel_stop called , line 215
<3><dss_mgr_disable> disabling 2lcd
<6>adb_open
<6> boxer : boxer_panel_resume called , line 255
<6> boxer : boxer_panel_start called , line 150
<6> boxer : spi_send called , line 84
<6> boxer : spi_send called , line 84
<6> boxer : spi_send called , line 84
<6> boxer : spi_send called , line 84
<6> boxer : spi_send called , line 84
<6> boxer : spi_send called , line 84
<6> boxer : spi_send called , line 84
<6> boxer : spi_send called , line 84
<6> boxer : spi_send called , line 84
<6> boxer : spi_send called , line 84
<6> boxer : spi_send called , line 84
<6>kxtf9 1-000f: IRQ TILT [1]
<6>android_usb gadget: high speed config #1: android
<4>MAX8903: Charging is now enabled!
<4>MAX8903: USB Charging at 500 mA
<6>adb_release
<6>adb_open
<6>android_usb gadget: high speed config #1: android
<6>kxtf9 1-000f: IRQ TAP1 [1]
<6>kxtf9 1-000f: IRQ TAP1 [2]
<6>kxtf9 1-000f: IRQ TAP2 [2]
<6>kxtf9 1-000f: IRQ TAP1 [20]
<6>kxtf9 1-000f: IRQ TILT [10]
<6>kxtf9 1-000f: IRQ TILT [1]
<6>kxtf9 1-000f: IRQ TILT [10]
<6>kxtf9 1-000f: IRQ TILT [1]
<6>kxtf9 1-000f: IRQ TAP1 [1]
<6>kxtf9 1-000f: IRQ TAP1 [1]
<6>kxtf9 1-000f: IRQ TAP1 [2]
<6>adb_release
<6>adb_open
<6>android_usb gadget: high speed config #1: android
<6>adb_release
<6>adb_open
<6>android_usb gadget: high speed config #1: android
<6>kxtf9 1-000f: IRQ TAP1 [1]
<4>
<4> usb unplugged!
<6>adb_release
<4>MAX8903: USB_EVENT_NONE
<6>adb_open
<6>kxtf9 1-000f: IRQ TAP1 [1]
<4>MAX8903: Charging is now disabled!
<4>MAX8903: Charger Unplugged!
<6>kxtf9 1-000f: IRQ TAP1 [1]
<6>PC detected
<4>MAX8903: USB_EVENT_VBUS: Charger=3
<6>android_usb gadget: high speed config #1: android
<4>MAX8903: Charging is now enabled!
<4>MAX8903: USB Charging at 500 mA
<6>kxtf9 1-000f: IRQ TILT [10]
<4>
<4> usb unplugged!
<6>adb_release
<6>adb_open
<4>MAX8903: USB_EVENT_NONE
<6>kxtf9 1-000f: IRQ TAP1 [10]
<6>kxtf9 1-000f: IRQ TILT [1]
<4>MAX8903: Charging is now disabled!
<4>MAX8903: Charger Unplugged!
<6>kxtf9 1-000f: IRQ TILT [10]
<6>kxtf9 1-000f: IRQ TILT [1]
<6>kxtf9 1-000f: IRQ TILT [10]
<6>kxtf9 1-000f: IRQ TAP2 [2]
<6>kxtf9 1-000f: IRQ TILT [1]
<6>kxtf9 1-000f: IRQ TILT [8]
<6>kxtf9 1-000f: IRQ TAP2 [2]
<6>kxtf9 1-000f: IRQ TILT [1]
<6>kxtf9 1-000f: IRQ TILT [8]
<6>kxtf9 1-000f: IRQ TILT [1]
<6>kxtf9 1-000f: IRQ TAP1 [1]
<6>kxtf9 1-000f: IRQ TAP2 [1]
<6>PC detected
<4>MAX8903: USB_EVENT_VBUS: Charger=3
<6>android_usb gadget: high speed config #1: android
<4>MAX8903: Charging is now enabled!
<4>MAX8903: USB Charging at 500 mA
/sdcard # mount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mmcblk1p1 on /sdcard type vfat (rw,nodev,noatime,nodiratime,fmask=000
0,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed
,errors=remount-ro)
/sdcard # parted /dev/block/mmcblk0 print
parted /dev/block/mmcblk0 print
Warning: /dev/block/mmcblk0 contains GPT signatures, indicating that it has a
GPT table. However, it does not have a valid fake msdos partition table, as it
should. Perhaps it was corrupted -- possibly by a program that doesn't
understand GPT partition tables. Or perhaps you deleted the GPT table, and are
now using an msdos partition table. Is this a GPT partition table?
Yes/No? Yes
Yes
Yes
Error: The backup GPT table is not at the end of the disk, as it should be.
This might mean that another operating system believes the disk is smaller.
Fix, by moving the backup to the end (and removing the old backup)?
Fix/Ignore/Cancel? Yes
Yes
Yes
parted: invalid token: Yes
Fix/Ignore/Cancel? Fix
Fix
Fix
Warning: Not all of the space available to /dev/block/mmcblk0 appears to be
used, you can fix the GPT to use all of the space (an extra 569312 blocks) or
continue with the current setting?
Fix/Ignore? Fix
Fix
Fix
Model: MMC SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 16.3MB 15.7MB recovery
4 16.8MB 33.6MB 16.8MB boot
5 33.6MB 83.9MB 50.3MB fat32 rom
6 83.9MB 134MB 50.3MB fat32 bootdata
7 134MB 522MB 388MB ext4 factory
8 522MB 1164MB 642MB ext4 system
9 1164MB 1611MB 447MB ext4 cache
10 1611MB 2684MB 1074MB fat32 media
11 2684MB 15.6GB 12.9GB ext4 userdata
/sdcard #
/sdcard # reboot
reboot
Also BIG thank you for you guys, especialy to CelticWebSolutions.
Thank you guys.
Cj.
similar problem! help!
I too formatted my 1g partition, and now my nook wont boot, goes to pic of box, hangs. i try cwm from sdcard, same box, hangs. i cant see my device when i plug it in to my win 7 pc. no adb. ive rooted 3 NT's now and i cant understand what i should do next. any help?
DeltreeZero said:
I too formatted my 1g partition, and now my nook wont boot, goes to pic of box, hangs. i try cwm from sdcard, same box, hangs. i cant see my device when i plug it in to my win 7 pc. no adb. ive rooted 3 NT's now and i cant understand what i should do next. any help?
Click to expand...
Click to collapse
Sounds like its not actually booting the SD card. Try powering off completely and the put SD card in. Connect power cable and see if it boots. It could also be your SD isn't written correctly. Could be worth you downloading the latest cm7 SD image from the dev thread. See if that boots.
Sent from my Nook Tablet using Tapatalk
cwm wont run
Thanks for the reply! i have tried all combinations of power,"n", vol up, and vol down, holding not holding all combinations of buttons and also the 8 failed boot buisness, plugging in to wall outlet, plugging in to pc... no changes yet, still "n" symbol on screen, then pic of box, hang. i am downloading the latest cm7 build and downloaded the installer located
here: http://forum.xda-developers.com/showthread.php?t=1000957
per your suggestion. im now making ramen, because the download says 52 min left. I will check back soon. thanks again.
I have followed the instructions and still no boot to cm7. still "n", then pic of box, hang. darn. any ideas?
Can't ADB. PLEASE HELP.
I am having trouble with my nook tablet. It will not boot an OS, and it just hangs at CWM. I am trying the original solution posted by CelticWebSolutions, but I am very new to all of this, and I can't get my computer (windows 7) to recognize the nook as an ADB device. I have no idea what USBDeview is, or where to get it. I have also managed to kill my 2 best micro SD cards. They were 32 gb cards, and when I tried to install CM7. If possible, I would like to just get back to a factory Nook Tablet. If anyone can help me reach a solution, I would be happy to donate.
kodonnell204 said:
I am having trouble with my nook tablet. It will not boot an OS, and it just hangs at CWM. I am trying the original solution posted by CelticWebSolutions, but I am very new to all of this, and I can't get my computer (windows 7) to recognize the nook as an ADB device. I have no idea what USBDeview is, or where to get it. I have also managed to kill my 2 best micro SD cards. They were 32 gb cards, and when I tried to install CM7. If possible, I would like to just get back to a factory Nook Tablet. If anyone can help me reach a solution, I would be happy to donate.
Click to expand...
Click to collapse
Can you get into CWM?, Have you tried Adam's total wipe method?, what OS did you have when you bricked your device? What exactly have you done to it? We need more details in order to help you.
~ Veronica
Sent from XDA premium using my Nook Tablet
Related
Hello!
How do i mount my HTC hero on ubuntu?
I have tried everything i know about.
Here's some info about it!
It's connected to the machine now.
Code:
[email protected]:~# dmesg|tail
[167350.745833] VFS: Can't find a valid FAT filesystem on dev sda2.
[167350.746019] qnx4: wrong fsid in superblock.
[167392.539945] FAT: bogus number of reserved sectors
[167392.539952] VFS: Can't find a valid FAT filesystem on dev loop0.
[167392.540057] qnx4: wrong fsid in superblock.
[167429.744606] attempt to access beyond end of device
[167429.744614] loop0: rw=0, want=4, limit=2
[167429.744619] EXT3-fs: unable to read superblock
[167584.269145] FAT: bogus number of reserved sectors
[167584.269154] VFS: Can't find a valid FAT filesystem on dev loop0.
[email protected]:~# sfdisk -l
Disk /dev/sda: 19457 cylinders, 255 heads, 63 sectors/track
Warning: extended partition does not start at a cylinder boundary.
DOS and Linux will interpret the contents differently.
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System
/dev/sda1 0 - 0 0 0 Empty
/dev/sda2 * 0+ 18768- 18769- 150759362 f W95 Ext'd (LBA)
/dev/sda3 18768+ 19457- 689- 5529600 8e Linux LVM
/dev/sda4 0 - 0 0 0 Empty
/dev/sda5 3916+ 18768- 14853- 119300096 7 HPFS/NTFS
/dev/sda6 0+ 3915 3916- 31455207 83 Linux
[email protected]:~# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda6 30G 3.3G 25G 12% /
udev 438M 276K 438M 1% /dev
none 438M 0 438M 0% /dev/shm
none 438M 200K 438M 1% /var/run
none 438M 0 438M 0% /var/lock
none 438M 0 438M 0% /lib/init/rw
/dev/sda5 114G 30G 85G 26% /mnt/sda5
/dev/sda6 30G 3.3G 25G 12% /mnt/sda6
[email protected]:~#
First, you should have your data partition of your SD card formatted as FAT32.
Then connect your Hero to your PC using original USB table (you can use non-original, but not everyone of them works).
You should see notification on hero about connected USB, click on this notification and Hero will ask you if you want to connect it as storage device.
Linux should now recognize your Hero as standard USB flash drive.
This works for me.
hELLO!
How can i format my data-partition on my SD-card to FAT32?
And when i connect the hero to the machine, there is no notification on the notification bar!
sorry for bad english.
Broken USB
Hmm, it seems you have some trouble with USB since Hero does not recognize it. My dmesg looks like this, when I connect my Hero (but before I enable it as storage device):
Code:
[47693.001261] usb 6-2: new full speed USB device using uhci_hcd and address 2
[47693.130013] usb 6-2: device descriptor read/64, error -71
[47693.370011] usb 6-2: device descriptor read/64, error -71
[47693.600011] usb 6-2: new full speed USB device using uhci_hcd and address 3
[47693.730011] usb 6-2: device descriptor read/64, error -71
[47693.971260] usb 6-2: device descriptor read/64, error -71
[47694.201263] usb 6-2: new full speed USB device using uhci_hcd and address 4
[47694.621263] usb 6-2: device not accepting address 4, error -71
[47694.680042] hub 6-0:1.0: unable to enumerate USB device on port 2
[47694.961263] usb 2-4: new high speed USB device using ehci_hcd and address 3
[47695.123330] usb 2-4: configuration #1 chosen from 1 choice
[47695.526904] Initializing USB Mass Storage driver...
[47695.527144] scsi6 : SCSI emulation for USB Mass Storage devices
[47695.527234] usb-storage: device found at 3
[47695.527236] usb-storage: waiting for device to settle before scanning
[47695.527250] usbcore: registered new interface driver usb-storage
[47695.527253] USB Mass Storage support registered.
[47700.521271] usb-storage: device scan complete
[47700.523257] scsi 6:0:0:0: Direct-Access HTC Android Phone 0100 PQ: 0 ANSI: 2
[47700.523603] sd 6:0:0:0: Attached scsi generic sg3 type 0
[47700.533243] sd 6:0:0:0: [sdc] Attached SCSI removable disk
i'd try repartitioning the card, looks like a corrupted filesystem.
I don't think repartitioning will help here. /dev/sda is the disk in his computer, because /dev/sda6 is mounted as /. The dmesg output doesn't say anything about /dev/sdb, and there is not even anything about trying to connect a USB device.
My guess is either the cable is bad, or the USB socket on the computer is not connected.
Hi,
I get the same - in Windows it comes up as an unregognised device, and in linux i get
[ 1724.760062] usb 7-1: new full speed USB device using uhci_hcd and address 18
[ 1724.890058] usb 7-1: device descriptor read/64, error -71
[ 1725.130036] usb 7-1: device descriptor read/64, error -71
[ 1725.360077] usb 7-1: new full speed USB device using uhci_hcd and address 19
[ 1725.492549] usb 7-1: device descriptor read/64, error -71
[ 1725.730242] usb 7-1: device descriptor read/64, error -71
[ 1725.960394] usb 7-1: new full speed USB device using uhci_hcd and address 20
[ 1726.380063] usb 7-1: device not accepting address 20, error -71
[ 1726.500053] usb 7-1: new full speed USB device using uhci_hcd and address 21
[ 1726.920281] usb 7-1: device not accepting address 21, error -71
[ 1726.920302] hub 7-0:1.0: unable to enumerate USB device on port 1
and no option on the Hero to mount the partition. I'm open to suggestions
Try another cable and/or another USB port. E.g. the USB ports at the back of your PC are directly soldered to the mainboard, without a shoddy connector and cable in between.
Introduction
Why is UART useful? It's a debugging tool. During the boot sequence on most computers, you see a splash screen. On most computers, you can hit 'ESC' to see the diagnostics in the background and then press a key like 'F2' to jump into the BIOS and make changes. On our devices we don't have that option.
On the Nook we have U-Boot which functions as a BIOS. We press 'Space Bar' to get into the U-Boot options. UART allows you to get into the U-Boot and make changes, as well as view the logs as they are generated. See the following code block for an example output
Code:
Texas Instruments X-Loader 1.41 (Oct 21 2011 - 14:00:05)
Start not on PWRON, skipping power button check.
Starting OS Bootloader from EMMC ...
U-Boot 1.1.4-acclaim1.4_1.4.0.1029^{} (Nov 11 2011 - 12:34:20)
Load address: 0x80e80000
DRAM: 1024 MB
Using default environment
In: serial
Out: serial
Err: serial
hw_status 0x23 vbus_status 0x80
mmc read: Invalid size
mmc read: Invalid size
2 bytes read
MAX17042+UBOOT: battery type=LG
MAX17042+UBOOT: gas gauge detected (0x0000)
MAX17042_STATUS (00h) is 0x0000
MAX17042+UBOOT: BATTERY Detected!
MAX17042+UBOOT:WARM BOOT
mmc read: Invalid size
mmc read: Invalid size
40 bytes read
Valid max17042 init data is loaded into memory
0x1234
0x215b
0x00d6
0x2037
0x0000
0x0100
0x007e
0x3670
0x078f
0x0000
0x0000
0x6435
0x2f2c
0x0140
0x7d5a
0x87a4
0x1400
0x205c
0x205c
0x6046
verify if mem loaded: FullcapNom was saved as 2037
uboot verify: 1d CONFIG is 2210 ; should be 2210 & 0xFDFB
uboot verify: 2a RELAXCFG is 083b ; should be 083b
uboot verify: 29 FILTERCFG is 87a4 ; should be 87a4
uboot verify: 28 LEARNCFG is 2466 ; should be 2406 & 0xFF0F
uboot verify: 18 DesignCap is 205c ; should be 205c
uboot verify: 12 Vempty is 7d5a ; should be 7d5a
uboot verify: 25 TEMPLIM is 2305 ; should be 2305
uboot verify: 2b MiscCFG is 0810 ; should be 0810 & cc1f
uboot verify: 2c TGAIN is e3e1 ; should be e3e1
uboot verify: 2d TOFF is 290e ; should be 290e
uboot verify: 2e CGAIN is 4000 ; should be 4000
uboot verify: 2f COFF is 0000 ; should be 0000
uboot verify: 37 FCTC is 05e0 ; should be 05e0
MAX17042+UBOOT: warm config is okay
SOC 90%, booting.
Board revision PVT
mmc read: Invalid size
mmc read: Invalid size
16 bytes read
ptn 0 name='xloader' start=256 len=131072
ptn 1 name='bootloader' start=512 len=262144
ptn 2 name='recovery' start=1024 len=15728640
ptn 3 name='boot' start=32768 len=16777216
ptn 4 name='rom' start=65536 len=50331648
ptn 5 name='bootdata' start=163840 len=50331648
ptn 6 name='factory' start=262144 len=387973120
ptn 7 name='system' start=1019904 len=641728512
ptn 8 name='cache' start=2273280 len=446693376
ptn 9 name='media' start=3145728 len=1073741824
ptn 10 name='userdata' start=5242880 len=64991232
mmc read: Invalid size
1088 bytes read
BCB found, checking...
** Unable to use mmc 0:1 for fatload **
** Unable to use mmc 0:1 for fatload **
** Unable to use mmc 0:1 for fatload **
Booting into Android
mmc read: Invalid size
mmc read: Invalid size
4 bytes read
BootCnt 2
1 bytes written
Autobooting in 0 seconds, press <SPACE> to stop...
kernel @ 80088120 (2682952)
ramdisk @ 81080000 (157153)
Initrd start : 81080000 , Initrd end : 810a64c1Acclaim Board.
Starting kernel ...
Linux version 2.6.35.7 ([email protected]) (gcc version 4.4.1 (Sourcery G++ Lite 2010q1-202) ) #1 SMP PREEMPT Fri Nov 11 12:35:42 PST 2011
CPU: ARMv7 Processor [411fc093] revision 3 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: OMAP4430 ACCLAIM
Memory policy: ECC disabled, Data cache writealloc
On node 0 totalpages: 245760
free_area_init_node: node 0, pgdat c0587e00, node_mem_map c062a000
Normal zone: 1536 pages used for memmap
Normal zone: 0 pages reserved
Normal zone: 178688 pages, LIFO batch:31
HighMem zone: 512 pages used for memmap
HighMem zone: 65024 pages, LIFO batch:15
***********************
OMAP4430 ES2.3 type(HS)
id-code (6b95c02f)
Die-id (5C360006-00000001-09111715-1601D00D)
Prod-id (000DB95C-000600CC)
***********************
SRAM: Mapped pa 0x40300000 to va 0xfe400000 size: 0x100000
FIXME: omap44xx_sram_init not implemented
Reserving 33554432 bytes SDRAM for VRAM
SMC: Allocated workspace of 3M at (0x9c900000)
PERCPU: Embedded 7 pages/cpu @c0e37000 s5632 r8192 d14848 u65536
pcpu-alloc: s5632 r8192 d14848 u65536 alloc=16*4096
pcpu-alloc: [0] 0 [0] 1
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 243712
Kernel command line: androidboot.console=ttyO0 console=ttyO0,115200n8 [email protected] [email protected] init=/init rootwait vram=32M,82000000 omapfb.vram=0:[email protected]
PID hash table entries: 4096 (order: 2, 16384 bytes)
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 448MB 256MB 256MB = 960MB total
Memory: 935252k/935252k available, 47788k reserved, 262144K highmem
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
DMA : 0xffc00000 - 0xffe00000 ( 2 MB)
vmalloc : 0xf0800000 - 0xf8000000 ( 120 MB)
lowmem : 0xc0000000 - 0xf0000000 ( 768 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.init : 0xc0008000 - 0xc003d000 ( 212 kB)
.text : 0xc003d000 - 0xc053f000 (5128 kB)
.data : 0xc0540000 - 0xc05888c0 ( 291 kB)
SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
Hierarchical RCU implementation.
RCU-based detection of stalled CPUs is disabled.
Verbose stalled-CPUs detection is disabled.
You will need
In order to get started you will need some things. Here's what you will need.
Torx T5 screw driver (the star kind)
Soldering iron ( any soldering iron)
Case opener tool ( or guitar pick or something small and plastic)
30-40 AWG wire (small wires)
1.8V UART to USB converter (Like The Bus Priate)
Tweezers (Makes it easier to handle small things)
Most of the tools and parts used can be obtained at Lowes or Radio Shack
For a UART device, I recommend The Bus Pirate. The Bus Pirate is known as "The Hacker's Multi-tool" and it is useful for alot more than just UART. It is an Open-Source, Open-Hardware, community supported tool. You can get it from SeeedStudios.com for $27.15.
Instructions
There are several ways to set up UART. Here is how I set up mine.
Image 1:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Disassembly
If you have an SDCard inserted, remove it.
Remove two(2) T5 Torx screws securing the back cover to the unit
Using the Case Opener tool, pry the rear cover off the unit. It is held on by small plastic hooks. They are fairly durable and I have not broken any in several removal and installations.
Remove ten(10) T5 torx screws from the metal case which secure the front cover
Image 2:
disconnect the battery and the volume control swich connections which are accessible through holes in the metal case.
Remove the front cover using a case opener tool or your bare hands, whichever is more comfortable for you
Remove the board and LCD from the metal case
Modification
Image 3:
Locate the UART RX and TX lines on the board shown in Image2.
You can hook your UART device to this directly, RX to TX and TX to RX, or keep reading and I'll show you how I set mine up. so..
Stop here and use UART or continue on for a cleaner method
run 40 awg wire to a piece of perf-board, about 8 holes wide.
Using 20 awg wire, make a loop on the perf-board which joins two holes in two spots on the small piece of perf-board
attach the UART RX
Image 4:
Route the wires along the board and tape them down
Use epoxy to mount the perfboard. It should be mounted at a very slight downward angle. Set something under the board while it dries. This gives room for the case to close.
Reassemble the unit, Assembly is reverse of Disassembly.
Image 5:
Hook up RX, TX to your perf-board hooks and connect ground to the metal case.
Image 6:
You will now be able to talk to your UART device using
Baud: 115200
Bits: 8
Parity: None
Stop Bits: 1
Voltage: 1.8 (open drain)
For the Bus Pirate, get it working in a termianal and use the following settings:
Code:
HiZ>m
1. HiZ
2. 1-WIRE
3. UART
4. I2C
5. SPI
6. 2WIRE
7. 3WIRE
8. LCD
9. DIO
x. exit(without change)
(1)>3
Set serial port speed: (bps)
1. 300
2. 1200
3. 2400
4. 4800
5. 9600
6. 19200
7. 38400
8. 57600
9. 115200
10. BRG raw value
(1)>9
Data bits and parity:
1. 8, NONE *default
2. 8, EVEN
3. 8, ODD
4. 9, NONE
(1)>1
Stop bits:
1. 1 *default
2. 2
(1)>1
Receive polarity:
1. Idle 1 *default
2. Idle 0
(1)>1
Select output type:
1. Open drain (H=Hi-Z, L=GND)
2. Normal (H=3.3V, L=GND)
(1)>1
Ready
UART>(3)
Conclusion
For those of you helping with security bypass methods, this will surely be useful as it will tell you when a secure failure is encountered. For those of you who want to experiment with U-Boot or a cool electronics project, I'd encourage you to try this. There's not alot that can go wrong because the board is well built and fairly heat resistant and the tools/parts used in this mod are available from several sources.
I hope this was informative and/or interesting for you to read.
Thanks to pokey9000 for pointing me to the right area.
A few lines before the kernal starts loading, it has bootcnt 2. What does this mean and what happens if it is modified? Or is any modification break the secure CHAIN?
Also, what would happen if it didn't autoboot in 0 seconds and you could hit the spacebar?
Sent from my BNTV250 using Tapatalk
HMG10 said:
A few lines before the kernal starts loading, it has bootcnt 2. What does this mean and what happens if it is modified? Or is any modification break the secure CHAIN?
Sent from my BNTV250 using Tapatalk
Click to expand...
Click to collapse
That's the number of boots since the counter was reset. After 8 failed boots, the device will go into recovery and restore all firmware.
this is great! I have been looking at my arduino and my pandaII (.netMF) dev boards and my tablet for a few days now.
Glad I dont have to pull out the logic analyser and find those pins..
servergod said:
this is great! I have been looking at my arduino and my pandaII (.netMF) dev boards and my tablet for a few days now.
Glad I dont have to pull out the logic analyser and find those pins..
Click to expand...
Click to collapse
that's exactly what I did...
Adafruit's FTDI Friend should also do the trick, $10 less.
I changed up my UART connection. I feel this is much cleaner and runs less wire through the nook. This makes it into a really good development device.
This new setup is made with a piece of perf-board from Radio Shack and it's held onto the nook using double-sided tape. Here are some pictures:
The wires are routed through the crack in the back cover and run to the same points mentioned in the Original Post. The 3rd connection (middle) here is Ground. Ground is the point on the board closest to the edge and furthest from UART TX in the staggered group of pins..
I thought I'd update this... I though I'd update this after a few weeks of working with it. The external connection works very well. It is easy to remove and replace if required with just 3 solder joints if required. The external perf-board is very unobtrusive, and does not interfere with operation.
I also found a case that works well with this modification. it's called "Mini Suit" for Nook Tablet.
If you go with this method and need a case, Mini Suit will suit you.
Adam,
In picture 3 you have a diagram that shows the pinout for uart tx and rx on the nook tablet (appears to be the left two pins of the 4 in the diagram), but if you look closely at picture 4, the top wire appears to be soldered to the top right pin rather than the top left pin as show on the diagram in picture 3. Is this just an optical illusion?
Thanks Again for all you do on these forums.!
acruxksa said:
Adam,
In picture 3 you have a diagram that shows the pinout for uart tx and rx on the nook tablet (appears to be the left two pins of the 4 in the diagram), but if you look closely at picture 4, the top wire appears to be soldered to the top right pin rather than the top left pin as show on the diagram in picture 3. Is this just an optical illusion?
Thanks Again for all you do on these forums.!
Click to expand...
Click to collapse
disregard picture 4. I took alot of pictures while setting things up and I chose the ones that gave the best idea of what was going on. Thanks.
Replacement for Bus Pirate
Hi Adam
Good day to you.
I would like to setup my own Uart devices for Samsung Phone, however, not able to locate the Bus Pirate devices as mention in your thread.
but i found a USB to RS232 converter as per attach PDF file.
would you please help to check on it? is it possible to setup the UART setup use on Samsung phone?
if can kindly help to give a detail guide connection setup from PC USB to Phone.
appreciate you help.
thanks
chongns said:
Hi Adam
Good day to you.
I would like to setup my own Uart devices for Samsung Phone, however, not able to locate the Bus Pirate devices as mention in your thread.
but i found a USB to RS232 converter as per attach PDF file.
would you please help to check on it? is it possible to setup the UART setup use on Samsung phone?
if can kindly help to give a detail guide connection setup from PC USB to Phone.
appreciate you help.
thanks
Click to expand...
Click to collapse
This should really go into the Samsung forum for the phone you're trying to get to, however here is where you can buy a bus pirate.
I'm looking for some experienced eyes to scan through the partition info of a CyberNav tablet that I've mucked up by being very stupid. The CyberNav is a cheap Chinese GPS/Android tablet. It works great, or rather worked great until I very stupidly left it attached to my computer after downloading a track of my latest dirtbiking exploits. Later that evening I decided to make another Ubuntu USB startup disk... well, you can guess the rest.
At this point, the tablet will not mount the internal "sdcard" memory. It still boots, everything works, not bricked yet. When connected to USB, it will share out this external storage just fine. It just won't mount it within Android. It reports "Preparing memory device, checking for errors." Never gets past that point. I do have a backup of the original internal sdcard contents (made that when I first got the device) and anything that was important to me. Yes, I make backups, been burned too many times. I've also managed to find a factory ROM for it and I've successfully flashed that to the device. It made no difference with the problem. I've also got a root prompt via ADB shell using psneuter.
I have a copy of parted and gdisk, though I've not tried to run them yet. In other words, it's time to start figuring out what to fix in the partition tables.
I think the problem is here:
# busybox fdisk -l /dev/block/mmcblk2p6
... Device Boot Start End Blocks Id System
/dev/block/mmcblk2p6p1 1 1017 3436381 5 Extended <<<<< HERE
/dev/block/mmcblk2p6p5 1 1017 3436379 b Win95 FAT32
Does that seem right? Am I in any danger of bricking this device if I blow away the mmcblk2p6p1 partition and/or the entire mmcblk2p6? How bad do things generally have to get in these partitions before the device bricks?
What is the best/safest way to remove this partition and if I have to blow the whole mmcblk2p6 partition away will I have to manually recreate it before rebooting?
Any advice appreciated,
David...
P.S. Here is all the hopefully relevant information I've so far managed to locate:
Cybernav Mini: CPU: IMAPX200 ARM11 800MHz, also known as YFPi08, now flashed to Android 2.2-104.
# cat /proc/partitions
Code:
major minor #blocks name
179 16 3878912 mmcblk2
179 17 4096 mmcblk2p1
179 18 8192 mmcblk2p2
179 19 153600 mmcblk2p3
179 20 1 mmcblk2p4
179 21 277760 mmcblk2p5
179 22 3435072 mmcblk2p6
# busybox fdisk -l /dev/block/mmcblk2
Code:
Disk /dev/block/mmcblk2: 3972 MB, 3972005888 bytes
1 heads, 16 sectors/track, 484864 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk2p1 9 520 4096 30 Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk2p2 521 1544 8192 31 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk2p3 1545 20744 153600 83 Linux
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk2p4 20745 484864 3712960 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk2p5 20753 55472 277760 83 Linux
/dev/block/mmcblk2p6 55481 484864 3435072 b Win95 FAT32
# busybox fdisk -l /dev/block/mmcblk2p6
Code:
Disk /dev/block/mmcblk2p6: 3517 MB, 3517513728 bytes
109 heads, 62 sectors/track, 1016 cylinders
Units = cylinders of 6758 * 512 = 3460096 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk2p6p1 1 1017 3436381 5 Extended
/dev/block/mmcblk2p6p5 1 1017 3436379 b Win95 FAT32
# cat /proc/kmsg
Code:
...
<3>[ 2.295000] imapx200_iic imapx200_iic.0: iic thread TX_ABORT occur
<3>[ 2.295000] imapx200_iic imapx200_iic.0: source is 1
<3>[ 2.295000] imapx200_iic imapx200_iic.0: slave address is 1a
<4>[ 2.300000] mmc_request bus 2 cmd 5 error -110
<4>[ 2.300000] mmc_request bus 2 cmd 5 error -110
<4>[ 2.300000] set info,open device error -939392608
<4>[ 2.305000] mmc_request bus 2 cmd 5 error -110
<3>[ 2.305000] imapx200_iic imapx200_iic.0: iic thread TX_ABORT occur
<3>[ 2.305000] imapx200_iic imapx200_iic.0: source is 1
<3>[ 2.305000] imapx200_iic imapx200_iic.0: slave address is 1a
<4>[ 2.305000] mmc_request bus 2 cmd 5 error -110
<6>[ 2.330000] mmc2: new high speed SDHC card at address 0002
<6>[ 2.330000] mmcblk2: mmc2:0002 3.69 GiB
<6>[ 2.335000] mmcblk2: p1 p2 p3 p4 < p5 p6 >
<4>[ 2.400000] custom info start sector 8182
<4>[ 2.430000] i2c-imapx200 transfer timeout
...
<6>[ 4.095000] EXT4-fs (mmcblk2p3): mounted filesystem with ordered data mode
<6>[ 4.635000] EXT4-fs (mmcblk2p5): recovery complete
<6>[ 4.645000] EXT4-fs (mmcblk2p5): mounted filesystem with ordered data mode
...
<3>[ 26.285000] FAT: invalid media value (0xa5)
<6>[ 26.285000] VFS: Can't find a valid FAT filesystem on dev mmcblk2p6.
... x3 above spaced to end of log.
dmesg:
Code:
...
<6>[ 0.295000] Imap Framebuffer Driver Initialization OK!
<4>[ 0.340000] set info,open device error -939392608
<4>[ 0.440000] set info,open device error -939392608
<4>[ 0.540000] set info,open device error -939392608
<4>[ 0.640000] set info,open device error -939392608
<4>[ 0.740000] set info,open device error -939392608
<4>[ 0.845000] set info,open device error -939392608
<6>[ 0.925000] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
...
<3>[ 96.180000] FAT: invalid media value (0xa5)
<6>[ 96.180000] VFS: Can't find a valid FAT filesystem on dev mmcblk2p6.
... x2 above
adding a little info
# /data/local/tmp/parted /dev/block/mmcblk2
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk2
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print all
print all
Model: SD (sd/mmc)
Disk /dev/block/mmcblk2: 3972MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 65.5kB 4260kB 4194kB primary
2 4260kB 12.6MB 8389kB primary
3 12.6MB 170MB 157MB primary ext4
4 170MB 3972MB 3802MB extended
5 170MB 454MB 284MB logical ext4
6 454MB 3972MB 3518MB logical
But,
# /data/local/tmp/parted /dev/block/mmcblk2p6
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk2p6
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print all
print all
Error: Can't have a partition outside the disk!
(parted)
Every command I try just reports: "Error: Can't have a partition outside the disk!"
Okay, Okay, I get it. No how do I get rid of said partition?
Back at: # /data/local/tmp/parted /dev/block/mmcblk2
(parted) check 6
check 6
Error: Could not detect file system.
(parted)
dare I go: rm 6
If I just reboot at that point, what are the odds of the bootloader just recreating this partition for me? Should I recreate the partition via parted first? Something like: mkpart logical fat32 454 3972 and then format it by Windows Computer via USB mode, or (man for parted says this is discouraged) mkpartfs logical fat32 454 3972 to let it format right away?
I guess what I'm really asking is: what are the odds of bricking it if I blow this partition away? Seem low, what with it not working properly now, but I figure I should at least make an attempt at asking before I suck it up and hit the button.
Anyone?
David...
fixed:
rm 6 and mkpartfs logical fat32 454 3972 then a reboot did the trick. I've copied all the data back and set the tablet back to where it was. All done
Only took 2 weeks of head-banging, trying to figure out the Android way. Not an easy thing, what with all the fragmentation, and it pushed my Linux skills to their limit as well. By the hour, this $100 tablet is now worth an order of magnitude more but those skills should be worth it, even if the tablet isn't.
David...
Hi, I am having issues with a Huawei modem E173u-1 on my tablet Archos 101 g9 8gb
driver not found.
Can you help me, pls?
USB_ModeSwitch log from Wed Apr 09 17:50:44 PKT 2014
Raw args from udev: 1-1/1-1:1.0
Using top device dir /sys/bus/usb/devices/1-1
----------------
USB values from sysfs:
manufacturer HUAWEI
product HUAWEI Mobile
serial
----------------
bNumConfigurations is 1 - don't check for active configuration
SCSI attributes not needed, moving on
checking config: /data/data/de.draisberghof.pppwidget/app_tmp/12d1.14fe
! matched. Reading config data
devList 1:
config: TargetVendor set to 12d1
config: TargetProduct set to 1506
Driver module is "option", ID path is /sys/bus/usb-serial/drivers/option1
Logger is: /system/bin/log
Command to be run:
usb_modeswitch -I -W -D -s 20 -u -1 -b 1 -g 2 -v 12d1 -p 14fe -f $cB
Verbose debug output of usb_modeswitch and libusb follows
(Note that some USB errors are to be expected in the process)
--------------------------------
Reading long config from command line
* usb_modeswitch: handle USB devices with multiple modes
* Version 1.2.4 (C) Josua Dietze 2012
* Based on libusb0 (0.1.12 and above)
! PLEASE REPORT NEW CONFIGURATIONS !
DefaultVendor= 0x12d1
DefaultProduct= 0x14fe
TargetVendor= 0x12d1
TargetProduct= 0x1506
TargetClass= not set
TargetProductList=""
DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
QisdaMode=0
GCTMode=0
KobilMode=0
SequansMode=0
MobileActionMode=0
CiscoMode=0
MessageEndpoint= not set
MessageContent="55534243123456780000000000000011062000000100000000000000000000"
NeedResponse=0
ResponseEndpoint= not set
InquireDevice disabled
Success check enabled, max. wait time 20 seconds
System integration mode enabled
Use given bus/device number: 001/002 ...
Looking for default devices ...
bus/device number matched
searching devices, found USB ID 12d1:14fe
found matching vendor ID
found matching product ID
adding device
Found device in default mode, class or configuration (1)
Skipping the check for the current configuration
Using interface number 0
Using endpoints 0x01 (out) and 0x81 (in)
USB description data (for identification)
-------------------------
Manufacturer: HUAWEI
Product: HUAWEI Mobile
Serial No.: not provided
-------------------------
Looking for active driver ...
OK, driver found; name unknown, limitation of libusb1
OK, driver "unkown" detached
Setting up communication with interface 0
Using endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
OK, message successfully sent
Resetting response endpoint 0x81
Could not reset endpoint (probably harmless): -34
Resetting message endpoint 0x01
Could not reset endpoint (probably harmless): -6
Device is gone, skipping any further commands
Bus/dev search active, referring success check to wrapper. Bye.
ok:busdev
--------------------------------
(end of usb_modeswitch output)
Checking success of mode switch for max. 20 seconds ...
Waiting for device file system (1 sec.) ...
Waiting for device file system (2 sec.) ...
Waiting for device file system (3 sec.) ...
Waiting for device file system (4 sec.) ...
Waiting for device file system (5 sec.) ...
Waiting for device file system (6 sec.) ...
Waiting for device file system (7 sec.) ...
Reading attributes ...
Mode switch has completed
Mode switching was successful, found 12d1:1506 (HUAWEI: HUAWEI Mobile)
Device class of first interface is ff
Now checking for bound driver ...
No driver has bound to interface 0 yet
Module loader is /sbin/insmod
Trying to find and install main driver module "option"
Trying to find module "option"
Loading support module /lib/modules/usb_wwan.ko
Error: insmod: cannot insert '/lib/modules/usb_wwan.ko': Invalid module format (-1): Exec
format error
Loading main driver module "option"
Error: insmod: cannot insert '/lib/modules/option.ko': Invalid module format (-1): Exec
format error
Falling back to "usbserial"
Module "usb_serial" not found, can't do more here
Driver binding seems to have failed
All done, exiting
please answer!!!
i'm solved the problem by replacing the nucleus
Hey guys,
Currently i`m digging into this matter. So here's the concept:
[HU] - one of the back USB's
|
[USB Hub] - powered form an external power supply (external 5V)
| |
U1 U2 - (32GB USB Drives)
A.) Current behaviour
- only the first inserted USB drive get's mounted under /mnt/usb_storage2
- the second usb drive is recognised by the kernel and does not get mounted by the system (not assigned to any "drive letter" so to speak(i think)).
B.) Current investigations:
B.1 ) by unpacking the boot.img - fstab.rk30board.bootmode.*
Code:
/devices/platform/usb20_otg/usb /mnt/usb_storage vfat defaults voldmanaged=usb_storage:auto
/devices/platform/usb20_host/usb /mnt/usb_storage2 vfat defaults voldmanaged=usb_storage2:auto
B.2) by unpacking the boot.img - init.rk30board.rc
Code:
[13] export THIRD_VOLUME_STORAGE /mnt/usb_storage
[14] mkdir /mnt/usb_storage 0000 system system
[15] export THIRD_VOLUME_STORAGE2 /mnt/usb_storage2
[16] mkdir /mnt/usb_storage2 0000 system system
On the Application Side, for example MTCAPKInstall_source/com/hct/apkinstall/DevListAdapter.java
Code:
} else if (path.equals("/mnt/usb_storage")) {
holder.Image.setImageResource(R.drawable.usbhost);
holder.ImageName.setText(this.mContext.getString(R.string.usb1));
} else if (path.equals("/mnt/usb_storage2")) {
holder.Image.setImageResource(R.drawable.usbhost);
holder.ImageName.setText(this.mContext.getString(R.string.usb2));
This can be solved easily by creating a for, or by duplication each else if (the copy/paste way )
I need to do some more tests... i`m also interested for your opinions/experience with this (What have you tested, What worked, What did not work, Why is not working, etc..)
So cheers to everyone and keep you posted
So far i rulled out the usb driver, internal hub.. It has something to do with the block creation and vold...
Will dig more tomorrow(i hope)
okey, so baseline the issue is related to VOLD
VOLD does not generate the block device for the new devices... i`m not 100% sure that VOLD handles the block device generation
for the time being i managed to mount 3 separate partitions from the same USB storage -> by doing this i ruled out the kernel itself, the irq assignment, etc..
I need to dig deeper into VOLD and to see exactly what is the process for generating the block device eg (/dev/block/vold/8:X)
from this point it would be nice to exchange some experience with someone that really know how things work on Android, i`m an iOS user, and the HU is my first Android System
I can't help as haven't gone down the road of digging to deep into kernels and Roms due to other commitments..
But just want to offer words of encouragement as you are working towards a good course..
I don't use a mobile modem and so at the moment that spare usbport is doing nothing. Would be nice to load it up with a spare USB drive I have around here .
That then brings up the powering up thread which the boys have already sorted..
So once you crack this and get a kernel mode going we are good to go..
Sent from my SM-G900I using Tapatalk
I tried to have a look in the binary code of vold shipped with the firmware, but friday was short... I'll continue my work next week
Keep you guys posted
In the past i did some test with a 4 Port USB hub. I connected several USB sticks and a 350 gb harddisk. They were not recognised by rootexplorer or android itself, but ESF file Explorer did recognised all of the devices.
Another strange thing is that when i connect a USB RTL dab+ dongle on the First USB Port on my hui and the harddisk on the other usb port my GPS is not working propperly.
well i`m 100% sure that the hub is not the issue, because:
<<1'st usb drive>>
<6>[ 1757.992589] usb 2-1.3: new high speed USB device number 30 using usb20_host
<6>[ 1758.093203] usb 2-1.3: New USB device found, idVendor=0781, idProduct=5204
<6>[ 1758.093230] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
<6>[ 1758.093282] usb 2-1.3: Product: Cruzer Crossfire
<6>[ 1758.093303] usb 2-1.3: Manufacturer: SanDisk Corporation
<6>[ 1758.093322] usb 2-1.3: SerialNumber: 000016A29874531B
<4>[ 1758.094142] --mtc usb storage 2-1.3 0781 5204
<6>[ 1758.094989] scsi11 : usb-storage 2-1.3:1.0
<5>[ 1759.092957] scsi 11:0:0:0: Direct-Access SanDisk Cruzer 4.05 PQ: 0 ANSI: 2
<5>[ 1759.094087] sd 11:0:0:0: [sda] 16055949 512-byte logical blocks: (8.22 GB/7.65 GiB)
<5>[ 1759.094577] sd 11:0:0:0: [sda] Write Protect is off
<7>[ 1759.094601] sd 11:0:0:0: [sda] Mode Sense: 03 00 00 00
<3>[ 1759.095072] sd 11:0:0:0: [sda] No Caching mode page present
<3>[ 1759.095095] sd 11:0:0:0: [sda] Assuming drive cache: write through
<3>[ 1759.098162] sd 11:0:0:0: [sda] No Caching mode page present
<3>[ 1759.098183] sd 11:0:0:0: [sda] Assuming drive cache: write through
<6>[ 1759.100316] sda: sda1
<3>[ 1759.104583] sd 11:0:0:0: [sda] No Caching mode page present
<3>[ 1759.104621] sd 11:0:0:0: [sda] Assuming drive cache: write through
<5>[ 1759.104663] sd 11:0:0:0: [sda] Attached SCSI removable disk
<7>[ 1759.846560] SELinux: initialized (dev sda1, type vfat), uses genfs_contexts
<<2'nd usb drive>>
<6>[ 1956.392593] usb 2-1.2: new high speed USB device number 31 using usb20_host
<6>[ 1956.493577] usb 2-1.2: New USB device found, idVendor=0951, idProduct=1666
<6>[ 1956.493616] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
<6>[ 1956.493647] usb 2-1.2: Product: DataTraveler 3.0
<6>[ 1956.493666] usb 2-1.2: Manufacturer: Kingston
<6>[ 1956.493683] usb 2-1.2: SerialNumber: 60A44C425294BE10A9820D20
<4>[ 1956.494632] --mtc usb storage 2-1.2 0951 1666
<4>[ 1960.190620] ~ arm_rev_16bits err0 0
the GUI applications are dependent of Device Block Assignment, as you can clearly see, kernel recognises both USB Storage devices, but only the first is assigned with a block device.
okey, so i had a chance to check with IDA the vold binary from our units... seems that vold binary is custom than from other rom's
i will do some tests on the unit itself with a modified version of vold to see what happens
Later Edit,
vold has nothing to do with the block assignment ... on the front USB port also known by the unit : usb20_otg works like a charm... i added 4 USB Drivers each one named accordingly -> sda, sdb, etc.. i managed to mount them manually -> success
On the rear USB also known by the unit usb20_hub it still does not work, VOLD was stopped and removed during tests
clearly things do not add up.. and VOLD so far seems to be ok..
i ran out of ideas
i'm not a developer, but if you find a solution for that problem, you'll be a hero. hope you have finally the idea that will be the right one