Related
I am having a rather challenging issue. I moved from branch 1.1 and Vegan GE-7.0.0.0 RC1 to 1.2 NVflash 20110508 CWM5504 and flashed the TeamDRH-AOSP-Preview-1F-LDPI. So the issue is that I cannot write to, wipe, reformat or partition my internal sdcard. I had to flash the ICS ROM from my external sdcard and reboot system, but the screen locks on the TeamDRH title graphic page after loading all of the apps. I tried different releases of CWM55XX, but no difference.
Running CWM, I have re-partitioned to 4096/0, then 2048/0, formatted/cleared/wiped every partition, run the keycheck and tried pretty much every function CW has but nothing can touch the files on the drive!
I can get into APX and CWM. I can mount the USB port and view the internal drive. I can move, add and delete files and windows explorer shows that each action is completed. I renamed the old Update.zip to Update-Old.zip and it changes in explorer. But as soon as I unmount USB the changes are lost. When I go into CWM and try to install the zips, the only zip files showing are the update.zip and Vegan…zip. I tried to go back to Vegan, but it boot loops.
I tried rr5678’s G-Tablet Format utility that completely erases all traces of anything in the G-Tablet's ROM storage space. It showed all of the steps as completed. I got the red letter message at power on, immediately flashed the 1.2 NVflash/CWM and it functioned perfectly. But, still, no change or effect on the old files on the internal sdcard.
At this point, after way too many hours researching, reading and rereading, it may be that either I have a corrupt config file, (which is beyond my limited expertise to determine) or a bad microdrive.
I would appreciate any thoughts or ideas on resolving this. I want my GTab back!!! (It would be extra nice to have ICS, as well!)
Cheers,
Geary
galyons said:
Running CWM, I have re-partitioned to 4096/0, then 2048/0, formatted/cleared/wiped every partition, run the keycheck and tried pretty much every function CW has but nothing can touch the files on the drive!
Click to expand...
Click to collapse
This is a known problem that sometimes develops on some gTabs with a non-standard kind (compared to the majority of gTabs) of internal SD card.
There is no known "fix" for the problem. There is a workaround on page 5 of that thread, though.
But, first, I'd like you to get me the output of a dmesg command and then run through a set of tests (see posts #88 and #66) and get me their exact output.
Ok, I will read enough to see if i can figure out how to get the test results. Gonna take me a couple of days. Thank you for the guidance!
Cheers,
Geary
Well, I downloaded the Knoppix image, burned a bootable CD, booted Knoppix, hassled through getting connected to the internet, reread the threads and gave it a "go". Got buried in abd...dmesg and bailed. I would love to provide all of the diagnostic messages, but quite honestly, do not want to invest more time to become marginally able to do so.
So...RMA and boxed off to US Merchants. Hopefully you can discover a fix, rather than a work around for this issue. But the work around is infinitely better than an ever boot looping tablet!!
Thanks again for your help to me and others!!
Cheers,
Geary
Okay, this thread is going to have A TON of info. I recommend that if you are new to Android you read this thread and any questions you have I will attempt to answer to the best of my knowledge or I'm sure someone else will.
It is, in my opinion, imperative that you understand the material of this post prior to playing around with your new Android device. Much of this topic is general purpose, i.e. it could apply to any Android device but I will be making specific references for the Nook Tablet.
Root: The Android OS is a linux based OS. Thus "root access" is a term that signifies full access to the file system of the OS. Consider root access similar to "administrative privileges" on Windows. An even more extreme analogy may be if you were to buy a Windows computer and find that you only had access to "My Documents;" the Android equivalent would be buying a device like the Nook Tablet (or pretty much any other android device) and not having root access.
Root for the Nook Tablet: We have various methods for rooting the Nook Tablet. The best method, IMO, is the sdcard method found here. This method will allow you to create an external microSD card that allows you to boot into a custom recovery (more on this later) and run a script which will get you "root access."
Why do I want root?: Root access allows you to do things you otherwise would not be able to do. Installing google apps is probably the biggest reason, but other reasons include making certain modifications to the device to allow you to do more "stuff." Another big reason is to install indirect's app which will allow you to flash (fancy word for install) a custom recovery to the internal memory of the Nook. He even has an app that will allow you to unroot the device and restore it to stock (I believe as of this post the unroot app only supports the 16GB model).
Custom Recovery? What's that?: A custom recovery is, IMO, the number 1 priority when tinkering with Android. The first instance of a custom recovery you may encounter is the one I mentioned previously, the sdcard version. I actually have a card that I keep imaged with the custom recovery (Clockworkmod Recovery) ready to go should I ever need it.
Within Clockworkmod Recovery or any other custom recovery, you will be able to do a few things: install zip files, make a backup of your current OS (and restore said backups), wipe data/cache. The key here, as with a lot of this stuff, is DO NOT START SELECTING THINGS YOU DO NOT FULLY UNDERSTAND. For some reason a lot of users have a habit of wiping system and other things within CWM thus resulting in broken partitions and other issues. Follow directions. If you are unsure of something, ask a question.
Custom ROM: ROM stands for Read Only Memory. It is the operating system of Android that is on your device. The stock ROM that comes with the device, a modified version of Android by B&N is very restricting. Getting root access on this rom will open up many options for users. However, as Android is open source, we have the ability to create custom ROMs that provide even more freedom and a "pure" Android experience.
These ROMs almost always come "rooted" as well. What I mean by this is that a developer could create a ROM that does not allow the user root access. In fact, the newest policy of Cyanogenmod (a very popular and hard working ROM development team) is that ROMs will no longer come "rooted" by default. Users will have to toggle root access in settings.
Custom roms are flashed (installed) via a custom recovery like Clockworkmod Recovery. Basically, if you have CWM on your external sdcard or flashed internally, you can store the ROM zip file on your internal memory (or the external card should you choose), boot into recovery, flash the ROM and voila you will be ready to boot into a new OS (you should probably wipe data/cache as well if its a new ROM). I must stress here that it is IMPERATIVE that you make a backup of your current OS prior to installing a new ROM. This way, you can restore your previous setup should you not like the new one or if there are any issues with the new one.
Boot from sdcard? Yes we are quite lucky with the Nook such that we can boot from the external sdcard. I have already mentioned booting into CWM from sdcard but we even have the benefit of booting into a custom ROM (CM7 only currently) from external sdcard. What this means is that you leave the internal OS completely intact. This would thus allow "dual booting" i.e. you can boot into internal or boot from external.
Back to stock: Getting back to stock is incredibly easy with the Nook Tablet. I've done it myself a few times on two devices for various reasons. Many people are afraid to root or flash custom ROMs because it voids the warranty. While true, if you are able to return the device to stock conditions, B&N has no way of knowing that the device has been tinkered with and thus the Warranty remains intact.
To wrap this up, I must stress how important it is that you read, read, read and read more when doing this stuff. Follow directions to the T. Ask questions if you aren't sure about something. I know this is a long post as well but I can't stress how important it is that users understand the information I have put forth here when rooting and/or flashing custom ROMs.
Also, if someone wants to add benefits to why rooting the stock OS is useful please feel free to do so (I admittedly have little experience with the B&N stock OS and thus am not 100% positive of the benefits of rooting the B&N stock OS).
Reserved.
The Download link for the Cyanogen Mod 7 Final Image is down?
I would like to download the latest Cyanogen Mod 7 Final Image, so I found this webpage containing the latest version of this Image =
http://forum.xda-developers.com/showthread.php?t=1481826
and tried to download the SD card for the Nook Tablet..
BUT the link to the SD Card for the Nook Tablet appears to be dead..at the very least, it's not working properly.
Please, can someone direct me to a proper link to download the correct Cyanogen Mod 7 Final Image for the 16 gig Nook Tablet ?
Thanks!
I'd check/ask in the thread for that rom.
I tried to make a similiar comment on that thread, however; I recieved a notice that since I was new here, I'm not allowed to post a comment on that development thread.
That is why I'm making a similiar request on this thread.
All I'm attempting to do at this point is simply download the correct Cyanogen Mod 7 Final Image, so, I'm requesting help in that regard.
Thanks again~
um, i have a request. could you please post your questions in the 'Q&A' section.
http://forum.xda-developers.com/forumdisplay.php?f=1508
thx.
.
now having 'asked nice' for that... i have another link. imho, @succulent has a better version of the cm7 internal for 16GB. it is here.
http://iamafanof.wordpress.com/2012/06/12/cm7-2-rc1-build-20120612/#more-739
thank you, "old fart"..
Please, accept my apologies for posting on an incorrect thread.. I honestly thought that I was posting on a thread that might be able to help.
Also, thank you for posting a webpage that contains the correct Cyanogen Mod 7 Image. In regard to this better Build of the Cyanogen Mod 7 for the Nook Tablet..I admit that I'm a real noobie, I'm simply asking because I don't know.
Is the Cyanogen Mod 7 Image in the Mediafire Folder listed on that webpage ?
If so, I've opened that Mediafire folder ..this folder contains a long list of various files.. which is the correct file that I should download, and write to my sd card ?
Thank you much for your help in answering my questions~
Please take it to another thread~
GENERAL CONDUCT REQUEST
@sinatrafan:
please refrain from using CAPS to get your point across, I'm sure people with be able to read a few sentances and respond without you needing to e-yell. Another suggestion, as a new member, maybe read some of the forum guidelines to better understand how we operate. In general, ask as many questions as you'd like, but do not expect an answer every time or on your time table, just hope that you get what you're looking for. Don't forget to search for yourself, I'm sure you could have found current links, just as the link was provided to you, I'm sure they foud that link by searching. Also, you'll likely receive better help if you are polite. Thank you.
I went to that link for you, here's the direct link for both (assuming the newest is the one to get).
ROM > http://www.mediafire.com/download.php?5gw47zw4xx108gc
GAPPS > http://goo.im/gapps/gapps-gb-20110828-signed.zip
@OP and other senior members:
please don't flame people with less than 10 posts, they're new here, remember when you were new? Just try to answer questions and be helpful, or don't post. If somebody is out of line, report the post and I'll get to it soonish. Thank you.
Installing/Flashing CWM on Rooted 1.4.0 NT w/ Blocked OTA Updates
Gents,
I stepped away from the world of the Nook Tablet over the last 5-6 months in order to focus on other Android devices.
Last time I was involved with the NT, I rooted my son's NT with Indirect's 'Full Root (v1.4.0) w/ Blocked OTAs w/ ZergRush exploit' Thread.
From what it seems, there have been a few changes, including obtaining root access for NT's that have 1.4.1+ through the SDCard boot method.
Quick question:
I want to load a custom recovery on my son's NT, such as Xionia or CWM. The root via SDCard method includes this as part of the overall root method.
Is there a preferred way that I can install/flash custom recovery on my son's NT, knowing that I have a rooted 1.4.0 NT Blocked OTA updates?
Just curious.
Thank you,
BJ.
Anyone?
b1ggjoe said:
Is there a preferred way that I can install/flash custom recovery on my son's NT, knowing that I have a rooted 1.4.0 NT Blocked OTA updates?
Click to expand...
Click to collapse
I have a preference for the internal method. Plug in things are sometimes troublesome for me.
LOL! Well that's not exactly what I was asking however. As I stated, I currently have a rooted Nook Tablet (1.4.0) with Blocked OTA Updates (I used the original method from November 2011).
I am not interested in loading any kind of Custom ROMs at this time, but I do wish to add CWM or some other kind of custom recovery to my son's Nook Tablet.
Is there a recommended method to do this, without going through a re-rooting process with the 'Boot from SDCard method'?
Thanks,
BJ.
Anyone?
Nook RecoveryFlasher.apk
Search on Nook Recovery Flasher.apk and see if that app will meet your need. I believe it was created by Indirect.
Aaah ok will do. Thank you!!!!
Nook won't boot with CWM on card
Guys, am I the only one having this problem or are there others?
I've read and clearly understand the procedure to root my Nook Tablet. The problem is that no matter what I do, any time an SD card with a bootable CWM is inserted, the Nook simply refuses to start. Removing the card or for that matter replacing it with any other card that does NOT have a bootable CWM fixes the problem. It'll even boot and run the pseudo-root ROM that runs off the SDCard without actually rooting the tablet.
I've tested this with many cards and with several different ways to prepare it, and the end result is always the same regardless of what mode the Nook is in. I'm thinking that if somehow I'm not preparing the card correctly, then wouldn't the tablet simply boot up normally as it does with any other card that has no bootable CWM in it?
Since I bought my tablet at about the end of August 2012, I'm thinking B&N put something in the stock ROM to detect any other recovery and stop cold if that's what it finds. I say this because the problem is only with bootable recoveries, any bootable non-recovery works OK.
Any ideas??
humb11 said:
Guys, am I the only one having this problem or are there others?
I've read and clearly understand the procedure to root my Nook Tablet. The problem is that no matter what I do, any time an SD card with a bootable CWM is inserted, the Nook simply refuses to start. Removing the card or for that matter replacing it with any other card that does NOT have a bootable CWM fixes the problem. It'll even boot and run the pseudo-root ROM that runs off the SDCard without actually rooting the tablet.
I've tested this with many cards and with several different ways to prepare it, and the end result is always the same regardless of what mode the Nook is in. I'm thinking that if somehow I'm not preparing the card correctly, then wouldn't the tablet simply boot up normally as it does with any other card that has no bootable CWM in it?
Since I bought my tablet at about the end of August 2012, I'm thinking B&N put something in the stock ROM to detect any other recovery and stop cold if that's what it finds. I say this because the problem is only with bootable recoveries, any bootable non-recovery works OK.
Any ideas??
Click to expand...
Click to collapse
Try powering off, inserting your bootable SD card in the tablet, then plugging the B&N USB cable into your tablet. Some tablets (and there doesn't seem to be any rhyme or reason to it) will only boot from the external card if they detect the USB cable.
Saludos,
Steve
Post to Q&A and someone will sort you out.
The OP mentioned that he only dual boot bootable Cyanogenmod image is CM7. Is there a reason why CM10 is not possible? It seems the N2A people are advertising that capability on their website. I would like to be able to do that myself if possible.
Hi! So I'm wondering if anyone know if there is\have been any development for
the Tizzbird Stick N1 (M\G) ?
We have this Android-stick in stock at my store, but I'm not sure if I'm going to get it or not yet. Depends the development, as I'd really like to see the capabilities for it. I believe it's a lowbrand tho. so I might be out of luck.
Anyone know anything?
I searched the forums, and did a google search. Didnt find much.
regards,
Dag M.
Hi there!
I own one of those, and there are a handful of (german-speaking) people activly posting in this forum http://forum.tizzbird-tv.de/ about the Tizzbird N1. - The problem with that forum is that they heavily censor it - as soon as anyone posts info on how to "get in", or if someone asks uncomfortable questions - those posts gets deleted.
They sell it really cheap for 30€ (not all the time, but twice for one day @ redcoon) and although the Wifi-Chip (or the drivers for it) are really crappy, the media player part is really nice.
update: I've did a little research, and here is a little list of relevant links about the tizzbird n1:
==== Marketing Product Pages ====
http://valueplus.co.kr/english/product/product_player_n1.html
http://www.tizzbird.com/eng/index.php?mm_code=719&sm_code=755
http://tizzbird-tv.de/tizzbird/tizzbird-n1.html
==== Official Firmware ====
http://www.tizzbird.com/eng/index.php?mm_code=726&sm_code=727&board_search_head_word=stick+n1
http://download.tizzbird-tv.de/TizzBird_N1G_update_GMS_V3_20_13072719.tzbird
==== German Support Forum (posting info about root-access prohibited) ====
http://forum.tizzbird-tv.de/viewforum.php?f=11
==== GPL-Code for Tizzbird N10, N20 & N30 - but not for N1? ====
http://www.tizzbird.com/eng/index.php?mm_code=752&sm_code=754
==== Kernel Sources ? ====
http://www.cnx-software.com/2012/03...k-n1-android-ics-hdmiusb-dongle-media-player/
http://www.cnx-software.com/2012/07...hips-tcc8925-mini-pcs-cx-01-z900-tizzbird-n1/
https://github.com/cnxsoft/telechips-linux
Yeah, the pretend to be "community friendly and supportive" but once you actually start digging in, they get quite agressive and boot you out.
Anyways, I got a N1 a couple of days myself now (snagged it for 30 bucks at another RedCoon sale ) and I am surprised.
Got it pretty much only to tinker around with it and this thing suits more perfectly for that than I imagined.
Esp. that fact they used a simple SD card as "internal flash storage" - my guess is because a simple SD is cheaper than an actual eMMC flash chip, but it's so cool on so many levels for us.
I already found out how to replace the 4GB SD with a bigger one (have a 16GB in mine ATM).
I'll post some more details about it here later, got a few things I want to test and/or prepare first (thinking of some "easy to use cloning script"), but long story short:
You need to copy the bootloader to the very end (last few blocks) of the SD you want to use.
Once the BL is at the proper place it already boots from the new SD again, to be sure everything is as it's supposed to be one should apply an update via USB (I'm not 100% sure about a possible pointer to the BL that needs to be corrected, which the update does).
After that the partition information has to be edited to make the userdata partition larger and you're done.
thanks for the info HellcatDroid!
It would be great if you could elaborate on how to put the bootloader at the end of the sd-card.
Also I would love to get info how to get root into the stock firmware, that crippled down root-firmware that they allow to exist in the official tizzbird forum doesn't really satisfy my needs
I did it via a hex editor, but it should be doable with a few "dd" commands as well - that's one of the things I still want to try, find the propper dd params to copy the BL over.
If you dumped the original SD into a file using dd, at the very end of the image file you will find the bootloader and the very last block of the SD is a "header" telling the bootrom of the N1 a few things about it, so it can properly locate and load it.
So what you got to do is to copy those last ~230k from the image to the end of the new SD card.
As said, I'll try to write a small shell script that does it.
The rooting is even more easy (Stonecold would kill me if he'd read this, lol):
For when running on Linux (no can do on Windows, as Windows doesn't know the ext4 FS):
Since you got the SD in your PC anyways already, just mount partition 2 (e.g. if the SD is sdc on your PC, mount /dev/sdc2).
That is the partition where the Android system is sitting on.
Then just copy over the files needed for root to where they need to go, chown/chmod them properly, unmount and done
I used the "update-supersu.zip" I had for my Nexus7 to grab the required files.
But I'm planning to make a simple rooting script as well.
So if all goes as planned it'll come down to
- insert original SD
- run script 1
- insert new SD
- run script 2
- to root run script 3
brilliant! I would love to see those scripts
way easier than start tinkering with that stuff myself
One thing I wonder about - over at the official forum you said that a simple dd copy didn't work - is that if the target sd-card is bigger or also for an sd-card of equals size? because with equal size simple dd copy of the sd-card should still work, even if some things need so be exactly at the end.
Yup, just a dd didn't work because the new SD card was larger and the bootloader ended up being somewhere in the middle of the card instead of at the end.
While your thought of "dd to equal size cards" is totally correct, it might still fail due to the fact every card is not 100% exact same size counting down to last byte.
There ususally is a tiny size difference (a few bytes to kbytes) between cards, even if they are supposed to be same, so the bootloader might end up truncated or not exactely at the end.
If, however, the size of the cards is 100% the same, down to the last byte, then yes, a simple dd clone would work.
HellcatDroid said:
... There ususally is a tiny size difference (a few bytes to kbytes) between cards, even if they are supposed to be same, so the bootloader might end up truncated or not exactely at the end. ...
Click to expand...
Click to collapse
Oh! Didn't know that. I thought same marketing size means not the same size they write on the box, but at least the same size between those that are marketed with the same GB numbers on their stickers.
OK, here we go, I slapped together a few scripts for prepping a new (and larger) SD card to work in the N1 and while having the SD in the PC to aplly some root.
* hints at attachment of this post
The scripts might still have problems and not work on any Linux out there, but it's a start.
If there's more people interested and joining in on this I might continue but for now I got what I wanted - more storage and root.
Hi
I think I destroyed my MiniSC cand! The N1 is dead. I tried to insert the card in a linux and gparted did not see anything. What can I do?
thank you for your help
somade said:
Hi
I think I destroyed my MiniSC cand! The N1 is dead. I tried to insert the card in a linux and gparted did not see anything. What can I do?
thank you for your help
Click to expand...
Click to collapse
Could you post how you got there? what did you do to the sd-card that destroyed it?
Hi.
If you got a dump from a working state of the SD you can just dd it back onto the card.
If you don't, it can still be recovered but might need bit more work.
Two options:
find someone who gives you a dump of their card and use the write-card script from my above post to write it to your SD.
Problem with this: a working dump contains copyrighted code, like the bootloader, it technically it's "not OK" to share it
we come up with another script that only contains an "empty" image (i.e. only partitioning information) and that takes the bootloader and recovery from the official update and gets the card into a state that it boots into recovery and lets you install a working system using the official update from USB (option in the recovery menu)
Option 2 would be nicer, IMO.
I'll try to make up said script
Thank you for your immediate answer!.
Actually I dont know what has happened, maybe the sharp instrument I used to remove the plastic cover scratch it...But now when I put it in a card reader the led of the reader switch off and the card is heated!!!. And also when I put it in the N1 the blue led turns off!.
So I bought a new empty micro Sd .
Waiting for your script to partition the new card and then boot in recovery mode and install a firmware....
Because I am not expert to linux please give me a lot of details how to do this.
Thanks again!
HellcatDroid said:
we come up with another script that only contains an "empty" image (i.e. only partitioning information) and that takes the bootloader and recovery from the official update and gets the card into a state that it boots into recovery and lets you install a working system using the official update from USB (option in the recovery menu
Click to expand...
Click to collapse
Do you think the bootloader is even part of the offical updates? wouldn't it be "best practice" to leave the bootloader partition alone as long as possible (and normally firmware updates don't need to change the bootloader)
update: something else I've just found, those might be kernel sources for our Tizzbird N1:
http://www.cnx-software.com/2012/07...hips-tcc8925-mini-pcs-cx-01-z900-tizzbird-n1/
-->
https://github.com/cnxsoft/telechips-linux
Yep, the bootloader is in the update - at least in the 3.20 one.
And yes, usually the bootloader shouldn't be touched because that's usually the one thing that can "perma-brick" Android devices.
However, sometimes the manufacturer updates it (fixing bugs, adding functionality) - on my Nexus7 they updated the bootloader on pretty much every update and also Samsung updates their bootloaders every now and then (and every single update flashes the current one).
Last, not least, on the N1 the bootloader isn't on a partition but at unpartitioned space at the very last blocks of the SD (=> reason for a simple dd to a larger card not booting).
Ohyay at the possible kernel sources!
It'd be so cool if that's really sources able to build a kernel for the N1 with - I think we might be able to even get custom recovery (CWM and the likes) on the N1 if those sources work
OK, while trying to recreate a working SD card w/o using a dump of a working one I found out a few more things - some of them still need figuring out if we wanna do it properly.
There seem to be TWO bootloaders!
A stage1 bootloader of ~1kB size located at the third and second last block of the SD. If it's missing the N1 can't boot and it looks like ARM code (haven't tried to disassamble it yet), I assume the bootrom loads and executes that piece of code which in turn parses the header (see below) and load/starts the stage2 bootloader (the one also found in the FW update).
The very last block of the SD is a "header block" with some information beeing parsed either by the bootrom or (more likely) the stage1 bootloader.
The headerblock contains (among numerous other unkown data) the size of the ("stage2") bootloader (the one that then actually loads and boots the Linux kernel of the Android OS, this is also the one contained in the FW update) and the usable size of the SD card! (everything works fine though if the SD size is wrong and a proper FW update updates the header during writing of the bootloader and also sets the correct size).
Also, the headerblock has a checksum of which I have no clue on how it is generated.
All that is just educated guesses and might be totally off, but for now it looks like it's not too far off.
So, for now we can assume the following boot sequence:
Boot-ROM
-> loads stage1 bootloader from fixed position "SDsize - 3 blocks" (1 block = 512bytes)
stage1 bootloader at fixed position on SD
-> checks checksum of headerblock (?), gets size of stage2 bootloader from headerblock, locates stage2 bootloader based on it's size and loads/executes it
stage2 bootloader on variable position on SD
-> base initialisation of hardware
-> checks for recovery trigger (the red button on the remote control) and boots kernel from partition 6 if trigger present
-> boots kernel from partition 1 if recovery was not triggered
-> enters fastboot mode when booting the kernel fails
Kernel
-> loads base drivers and boots up the system
you're brilliant Hellcat!
And did you also find both bootloader stages inside the firmware updates?
Another question that came to my mind while reading your post (fastboot..)
Is there a way to use the Tizzbird as USB-slave? So to make use of adb and fastboot and such stuff? Okey adb could also be used via network I guess..
somade said:
Hi
I think I destroyed my MiniSC cand! The N1 is dead. I tried to insert the card in a linux and gparted did not see anything. What can I do?
thank you for your help
Click to expand...
Click to collapse
Somade, do you have a linux running on your pc? If no, download and get a knoppix running. and then contact me via pm. I have the original n1 image so no problem to recover the n1.
sebastian.heyn said:
Somade, do you have a linux running on your pc? If no, download and get a knoppix running. and then contact me via pm. I have the original n1 image so no problem to recover the n1.
Click to expand...
Click to collapse
Welcome to our rouge and non-censored Tizzbird N1 forum Sebastian!
I wonder if you found us here, if the German Tizzbird support also already knows about us
update: I just remembered, I've sent you the link as PM over in the official forums, thats how you landed here.
Sharing your sd-card image might be a copyright violation, and if you're profile name is strongly linked to you're real identity you should definitly be cautious with such things on public forums...
kaefert said:
And did you also find both bootloader stages inside the firmware updates?
Click to expand...
Click to collapse
Nope, unfortunately the stage1 bootloader is not in the update :-/
kaefert said:
Is there a way to use the Tizzbird as USB-slave? So to make use of adb and fastboot and such stuff? Okey adb could also be used via network I guess..
Click to expand...
Click to collapse
Yeah, it works, even officially XD
Go to the TizzBird settings -> "System Settings" -> "Advanced Settings"
It has an option "OTG Mode" there, set it to "Debug".
If you have your N1 connected to your PC via the micro-USB port (and hence your PC powering the N1!) you can use ADB and fastboot just as usual
I have not yet tried if that option is persistant, i.e. it survives a power loss.
When booting the kernel fails it should fall back to fastboot mode, so flashing a new kernel w/o pulling the SD should be possible - need to test this a bit more, though.
What works is, if you're rooted and and you fire the command "reboot bootloader" from a root shell, that gets you into fastboot mode no matter what (given you applied above mentioned setting first).
But needing a running system to get into fastboot mode kinda defeats the purpose of it - this aint Ouya which is a total fail when it comes to fastboot XD
---------- Post added at 09:26 AM ---------- Previous post was at 09:05 AM ----------
kaefert said:
I wonder if you found us here, if the German Tizzbird support also already knows about us
Click to expand...
Click to collapse
Eventually they will, I'd say.
And I'd love to see their faces when they do XD
I hope someone can help me. I have a 16gb nook tablet that I rooted using the method described here http://liliputing.com/2012/03/how-to-dual-boot-cyanogenmod-7-nook-tablet-os-with-a-microsd-card.html over a year ago and I've never had an issue until last weekend. My daughter was playing a game and the nook started acting up. The touch screen became unresponsive and the screen started to flash. I let the Nook charge overnight and when I turned it on the next day the screen became stuck at the white Nook welcome screen. After 20 minutes I tried the holding down power and N button to see if I could get it to restart, but unfortunately that may have made it worse. Now my Nook won't start at all. I've read many many threads here on how to fix it, but I am not tech savvy in the slightest. The first thing I tried was Rays method http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/ but instead of getting the green checkmark I got the red X and the "nook is shutting down" message. I tried so many things that I cannot remember them all but I do know that one of the methods I tried I got this message.
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 that I tried to use the method described here http://forum.xda-developers.com/showpost.php?p=24995518&postcount=1 and I did make the booktable cwm-sd and I went to lavero.burgos' thread to download the mmcblk files, but they weren't there.
Also I don't understand what adb is but I'm desperate, when I found the thread that explained it and tried to download the ADB + Fastboot + Drivers.zip that was in said thread (I'm sorry I can't remember which thread it was) the zip file didn't work.
I'm really sorry for posting yet another, "please help my nook is borked" thread but after all the reading I've done this past week the only thing I've become is very confused and frustrated. Thank you in advance to anyone who can help.
Notice on the link you posted
Ray Waldo; said:
If this procedure fails, try one of these:
Celtic has a possible solution on XDA here: http://forum.xda-developers.com/showthread.php?t=1513583
Succulent has more info on his Github page: https://github.com/succulent/acclaim_recovery_sdcard.
Click to expand...
Click to collapse
I can see how you got lost. There aren’t really any detailed instructions there.
I got the following zip from 2nd link
Flash the zip with CWM then try the bn_142_factory_recovery.zip SD card again and you should get a green checkmark this time.
udownwitopp said:
Notice on the link you posted
I can see how you got lost. There aren’t really any detailed instructions there.
I got the following zip from 2nd link
Flash the zip with CWM then try the bn_142_factory_recovery.zip SD card again and you should get a green checkmark this time.
Click to expand...
Click to collapse
Thank you for your reply. I will try this tonight and hopefully it will work.
Well I tried, and I hate asking but how exactly does someone add a zip file to an sd card after an image has been flashed to it? I've tried numerous times with sd cards of various sizes and I'm pretty sure I should have been able to do this with a 16gb card, but every time I try to drag and drop the flashstock zip over onto the card it says that there is no room available. Now I have been doing a lot of reading on here and I'm pretty sure I did not set the card up right, I did format it correctly with the sdformatter program, but I'm guessing I have to do something with the partitions on the card. I am not familiar with the programs because I've never had cause to use them before so I am not entirely sure how to do that. I tried following the directions found here http://forum.xda-developers.com/showpost.php?p=24995518&postcount=1 but I couldn't figure out how to enable boot, and lba flags. I realize that this has probably all been answered already, but again, there programs are so foreign to me that I'm not even sure what to look up first. Thank you again for any help that any one can give me.
evm22 said:
Well I tried, and I hate asking but how exactly does someone add a zip file to an sd card after an image has been flashed to it? I've tried numerous times with sd cards of various sizes and I'm pretty sure I should have been able to do this with a 16gb card, but every time I try to drag and drop the flashstock zip over onto the card it says that there is no room available. Now I have been doing a lot of reading on here and I'm pretty sure I did not set the card up right, I did format it correctly with the sdformatter program, but I'm guessing I have to do something with the partitions on the card. I am not familiar with the programs because I've never had cause to use them before so I am not entirely sure how to do that. I tried following the directions found here http://forum.xda-developers.com/showpost.php?p=24995518&postcount=1 but I couldn't figure out how to enable boot, and lba flags. I realize that this has probably all been answered already, but again, there programs are so foreign to me that I'm not even sure what to look up first. Thank you again for any help that any one can give me.
Click to expand...
Click to collapse
I'll try to explain the process for you. "The Red X" is a very common issue that people have with their devices. It's usually caused by digging into something that you don't fully understand. It's VERY important to understand the process of flashing custom ROMs because it could screw up your tablet, delete ROM partitions and such.
The first issue you need to attend to is "The Red X." First download the bn_142_factory_recovery.zip from the ray waldo site found here:
http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
Unzip the zip file and you should have a repart.img. Use win32diskimager to write this to an SD card. Once it's done writing, put the SD card in your device and it should boot from SD card and flash stock B&N 1.4.2 to your nook (if you have problems booting from SD card plug in the USB to your computer).
If you still get "The Red X" during this process please use the following method:
http://forum.xda-developers.com/showthread.php?t=1513583
If you have further problems please post or PM me. Once you have the issue fixed I HIGHLY recommend using the SDC version. It's a lot easier than the Internal Version and will prevent mistakes from happening.
Thank you for responding. I retried the method described on Ray's site, but sadly it's still a no go. I have downloaded the parted binary and I know how to get it onto the sd card, but what I don't know is how to ADB into my device. I'm not even sure I understand what ADB is.
evm22 said:
Thank you for responding. I retried the method described on Ray's site, but sadly it's still a no go. I have downloaded the parted binary and I know how to get it onto the sd card, but what I don't know is how to ADB into my device. I'm not even sure I understand what ADB is.
Click to expand...
Click to collapse
I'm not extremely knowledgeable with the ADB tool, but it's setting up your computer so you can write commands into your command prompt that will execute actions on your device. The link for setting it up is here:
http://forum.xda-developers.com/showthread.php?t=1474956
Once you get it set up just follow the rest of the directions in the parted binary post.
datallboy said:
I'm not extremely knowledgeable with the ADB tool, but it's setting up your computer so you can write commands into your command prompt that will execute actions on your device. The link for setting it up is here:
http://forum.xda-developers.com/showthread.php?t=1474956
Once you get it set up just follow the rest of the directions in the parted binary post.
Click to expand...
Click to collapse
Thank you for a link to the post with a working zip file for adb, I've downloaded and I've tried to follow the video, but unfortunately my laptop will not read my nook at all. Every time I connect it with a usb my device manager tries to find it, but it blinks, makes an error sound and I see
OMAP4330 under other devices. I' did a search for that error and came across this thread, but again the instructions call for installing an apk on the nook and since I can't get mine to turn on, it's a no go
evm22 said:
Thank you for a link to the post with a working zip file for adb, I've downloaded and I've tried to follow the video, but unfortunately my laptop will not read my nook at all. Every time I connect it with a usb my device manager tries to find it, but it blinks, makes an error sound and I see
OMAP4330 under other devices. I' did a search for that error and came across this thread, but again the instructions call for installing an apk on the nook and since I can't get mine to turn on, it's a no go
Click to expand...
Click to collapse
There is a possibility you could have deleted some partitions important to the nook then. Have you tried making an sdc version of cm10 to see if it could boot at all? You could see if you still have the device information to backup, recreate the partitions and flash back to stock.
Use this to make a bootable cm10 card:
http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/
Just write the image file to an SD card and put it in your nook. It will boot into cm10. Once there go into your file manager and turn on root access. Go to your root drive/ROM/devconf to access all your device information. Make a backup of all them. There is a picture of my devices root drive. If you do not have the various partitions you will have to recreate them. There is a method on the Nook General Thread for doing this named "Unbrick Internal Partitions On NT" or something similar. You can use that recreate the internal partitions essential for your nook.
If you deleted the ROM partition with the Nook's product information you may be out of luck. The serial number and Mac address are the most essential, and can be found on your device hardware. The SN is under the SD slot (if readable) and Mac address is located inside your device. Not sure where I've never opened my nook to look, but probably on the WiFi chip.
Slight chance you may be able to fix it with this information and the rest of the device information you can use from a different nook since it doesn't have to do with internet and registration. There may be a way to fix that, but I don't know of any.
Best of luck. If you have problems just post a reply or send me an email.
I can get the Nook to turn on with the bootable cm10 card in it. I get the cyanoboot screen and see the boot menu, but honestly I don't know where to go from there. I think it's time for me to try and find someone who understands all of the programs involved in trying to fix this because I know I'm going to end up making things worse, if that's even possible. Thank you for trying to help me though. I do appreciate it
evm22 said:
I can get the Nook to turn on with the bootable cm10 card in it. I get the cyanoboot screen and see the boot menu, but honestly I don't know where to go from there. I think it's time for me to try and find someone who understands all of the programs involved in trying to fix this because I know I'm going to end up making things worse, if that's even possible. Thank you for trying to help me though. I do appreciate it
Click to expand...
Click to collapse
Hello! Did you ever figure out how to resurrect your Nook? I had trouble signing in Gmail and wanted to just unbrick and have the plain Nook again. I've been struggling getting the device to boot from the sd card with the repart imaged. I'm trying to get back to the ClockworkMod recovery screen but I can't at that moment. Someone suggested that I "flash" the B&N zip to the card but I'm trying to figure out how to do that.
Would love help!
You have never seen me here, though I have been lurking for quite a while. I don't know that much about how Android works and usually leave everything up the pros. Recently, as in 1 1/2 hours ago, I tried to flash CM 11 through 4EXT. Well... it failed. I was stuck at the HTC loading screen and couldn't access the internal storage. I dug around the internet for a while and, while I did find some work arounds to fix it, they were lengthy and didn't work on Windows 8.1. So, being the impulsive person I am, I attempted something extremely stupid to hopefully solve my issue... and it worked! So, here goes:
1) Boot in 4EXT (not sure if it works on other recoveries)
2) Press the USB storage button
3) On your computer, open up explorer and find where the device is connected (there should be two partitions, D: and E:\)
4) One of the two will have files while the other one just shows a device (for me, it was E:\). Right click, hit properties, then format it. Yes, your read that right: Format it.
5) Reboot your phone into recovery. You should now have access to the internal SD card.
Nice helpful first post. Next time I get stuck like that I'll have to try. It beats the heck out of reinstalling.