Related
Long missive below, so fair warning – I have put in as much detail as I can remember to help out troubleshooting and I have read every thread on APX mode I can find both on this board and others.
I’ve gone and done it now, my GTab formerly running VEGAn-Tab 5.1.1 is stuck booting only to APX mode. So what did I do, and what have I tried?
* Immediately after purchase, I loaded ClockworkMod .8, then VEGAn 5.1.1. Absolutely no issues.
* Started looking into the various kernels, decided to try Clemsyn’s since it seemed to support VPN’s without any hassle (I don’t have any Linux experience, so to me moving module files around is a hassle). It worked great, my VPN to home worked. I successfully upgraded several times to his Version5 without any problems.
* Loaded a ton of apps, the vast majority worked just fine. I loaded App2SD, and moved most of the larger apps to the SD card. I also I think moved LauncherPro to the SD Card, which caused minor problems later.
* Inserted a 512MB USB stick. It worked. However when the GTab rebooted with it in, I received a ton of FC’s for apps loaded to the SD Card that load on startup, including LauncherPro. I can’t remember what exactly I did to fix that, I remember somehow getting the regular launcher to load, then uninstalling LauncherPro and a ton of other apps. Reloaded those but didn’t move them to the SD Card. Everything back to normal.
* Decided I wanted a boot screen other than the birds, so I made one following the instructions in that thread. Like everyone else, my graphic failed on partition 6 but worked on partition 7. No problems after that.
* Yesterday I inserted a 4GB USB stick. It didn’t work. Rather stupidly based on my earlier experience with the 512, but confident I could fix anything that broke, I rebooted the machine with the stick still inserted. As expected, a ton of FC’s, this time though the apps were not loaded on the SD Card. Not good. I also could not get into the regular launcher to uninstall things. No problem, I was planning to switch to the Gingerbread edition of VEGAn anyway. I force rebooted (held the power button down about 10 seconds).
* The GTab came back to life in APX mode. Not good, but not fatal either. I downloaded NVFlash and the Win7 x64 drivers, I had no problem connecting the GTab and my laptop. Now feeling a little better, but still annoyed.
* Read the “[STICKY][ROM] nvflash FULL restore, using bekit's original image (Instructions)” thread on recovery backward and forwards twice to make sure I understood what I was doing. Came to the conclusion that all I needed to do at this point is unzip the two files (one with NVFlash, the other with the stock images) into one subdirectory, and run the .bat file. I did that, watched NVFlash create and format about 10 subdirectories, then load the images to them. NVFlash reported success, and my GTab rebooted into stock TnT. The usual FC’s on bootup, after chasing those away, I enabled WIfi, and let it download the latest firmware – 3588. It asked to install, I said yes. It asked to reboot I said yes. It rebooted into APX mode.
* Now I am really annoyed, this isn’t supposed to happen, though I did find I think 2 guys that are stuck in APX mode, looks like one returned his, the other leaves it on a dock and does not touch it. I don’t have the dock, I don’t like the stock TnT, and since I ordered the custom carbon fiber backing sticker and the “android eating the apple” sticker and they look great on the back I am not in favor of returning it at this time.
* So I spent another couple of hours on the web reading. I read the “[UTILITY] G-Tablet Format” thread on formatting the device, I downloaded that zip file, it looks much like the regular NVFlash recovery process. Actually exactly the same, but it looks like the .img files are different and the NVFlash file is different. It ran, and said it was successful. The GTab rebooted, and said I think “Magic number mismatch”. I rebooted again, expecting to see a magic number error, which would give me the greenlight to go into NVFlash Recovery mode, but failure - right back into APX mode. I wanted to do try the format and then restore to stock process back to back, but it seems that the machine has to reboot after any NVFlash action. Right back to APX mode, NVFlash to stock worked the same as before, loaded then APX mode on reboot.
* I tried using NVFlash to stock but adding CWM .8 on partition 9. No difference, right back to APX mode, no chance to get CWM to load. I read that using a single command to push only CWM to partition 9, then while holding down the plus sign pushing the image. That actually worked, it rebooted into CWM. Everything seemed to work as expected, I could mount the system and data directories, format them, reformat the SDCard, change it’s size to 2048/0. I tried wiping the DELVIK cache, it returned an error saying a file existed but then said it was successful. I don’t remember what it said when I did that the very first time when loading VEGAn 5.1.1, so that might be the expected behavior. Either way, I rebooted and right back to APX mode.
* I read somewhere that flashing CWM to partition 10 worked. I swapped around .img files so that it was pushed to 10 instead of 9. Upon reboot, it went straight to CWM. I had the same experience as before, upon reboot after that it went to APX mode instead of back to CWM.
* I popped the back off and tried booting while shorting out the 4 pins, no change, though I could get to APX mode anyway so I wasn’t expecting a miracle. The button next to those 4 pins didn’t make a difference either.
* I tried booting while holding down the vol- button, and again with both the vol- and + being held down. Neither worked.
* I downloaded the SDK to try ADB mode. It made me download the Java DK, no problem. The SDK does not see the JDK, but I didn’t reboot the laptop, since I was still in #Tegratab (thanks BadFrog for your help). I will do that when I get home and get ADB to work, but I don’t know what to do when I get that done. ADB works, I needed to load the 32 bit version of the JDK, even though I have an x64 machine. ADB works, so I am happy. Now to see if that helps the overall problem.
* I did after booting into CWM load VEGAn Gingerbread and Clemsyn’s GB Beta 2 kernel. After next rebooting into APX mode, I pushed CWM to partition 9, and it tried booting into GB but never got past the animated GB screen. I will try that again later today with 5.1.1 and the Ver5 kernel and see if it makes any difference. I can probably live with it booting into APX mode if I can push CWM to Par9 and get it to boot back into 5.1.1 when needed. z4root didn't help either.
* So in conclusion, I am stuck in APX mode no matter what I tried. I think it is partition related, because of the problems after inserting the USB sticks, and since it will reboot after NVFlash into whatever seems to be in partition 10. In the DOS world that is easy to fix, especially when doing a system wipe and rebuild. I tried using NVFlash to say partition 10 is the boot partition, that didn’t work, NVFlash actually didn’t seem to do anything and I had to do a CTRL-C to end it.
Any suggestions, other than peel my stickers off and mail it back to Amazon.com?
* 1239CET 25 Mar 11 - Edited, I tried z4root, it didn't help my problem.
* 1345CET 25 Mar 11 - ADB now working. Win7x64 Ult.
* 1725CET 26 Mar 11 - Unit RMA'd to Amazon - I was on day 30 so off it went, the replacement just shipped so they will cross in the mail.
Bump for more visibility
Very nice detailed post - you certainly did your homework. With that in mind I don't think I have much to add.
Yes, I remember one user who would reboot into APX mode all the time. I think there was one other person who would reboot into Fastboot all the time. And I don't think those problems were ever resolved.
Question: What is the model # on your device? I want to make sure it's it's not a 320, as at least one user on this board got a 320 and not a 300 (he got it from SEARS online). A 320 is a 1GB "v2" Malata device and those nvflash files might not work with them.
Here's another suggestion before you give up. Since nvflash seems to be the problem, maybe try another nvflash such as the Adam. The Adam nvflash DOES work on the GTAB. Maybe it will "jump-start" something for you.
Adam nvflash (Windows): http://api.notionink.com/fix/windows/LCD.zip
Adam nvflash (Linux): http://api.notionink.com/fix/linux/LCD.zip
Normally I wouldn't suggest this, but you are ready to return so there's not much to lose. You can always re-flash back to 1105 bekit, before you return it. These files will alter the booloader to that of an Adam, but again you can undo with the GTAB nvflash if needed.
Yep, mine is stuck in APX mode and the only way to "boot" it is to nvflash it.
I've set it up with VEGAn 5.1.1 and another kernel and my wife uses it. It sits on the dock (charging) when she's not using it and is never turned off/rebooted. If it does go off, I just nvflash it to boot (using the --format_partition 2 command) and once it boots the bootloader and formats partition 2 it proceeds to run.
I gave up (and also since my wife is using it I can't test other methods to make it work) and will later probably get myself one of the newer tablets (Samsung or Motorola or Toshiba...who knows) and pass my fully functional Gtablet to my wife.
roebeet said:
Here's another suggestion before you give up. Since nvflash seems to be the problem, maybe try another nvflash such as the Adam. The Adam nvflash DOES work on the GTAB. Maybe it will "jump-start" something for you.
Adam nvflash (Windows): http://api.notionink.com/fix/windows/LCD.zip
Adam nvflash (Linux): http://api.notionink.com/fix/linux/LCD.zip
Normally I wouldn't suggest this, but you are ready to return so there's not much to lose. You can always re-flash back to 1105 bekit, before you return it. These files will alter the booloader to that of an Adam, but again you can undo with the GTAB nvflash if needed.
Click to expand...
Click to collapse
Good sugestion, but unfortunately the nvflash in the adam recovery rom is the same as the one in the FORMAT images (151K), it seem to be better under windows since it list partition in text, the other when asked for a list of partition output a binary files.
As for the bekit1105 I usually do (when trying other rom or tnt5) NVFLASH FORMAT IMG, THEN NVFLASH the 1105 with the partition #9 replacing the clockwork .8 alway worked for me.
If it was me I would try to re-partition under windows the flash section, I am not sure how to do it with adb but if possible I would do it there.
I also notived the unit seem to be making sure the flash is partitioned in 2 section (2GB/16GB) inside system/etc/inandop.sh maybe that would be a couple of command to run by hand in adb, I know partition of flash can be tricky at time and it may be the reason the unit is falling to apx..
Would be a good idea to extract the partition list to confirm all their size a legit too.. either way don't give up I am quite sure someone will figure out a way of those half bricked unit...
michaeljwestii said:
*
Decided I wanted a boot screen other than the birds, so I made one following the instructions in that thread. Like everyone else, my graphic failed on partition 6 but worked on partition 7. No problems after that.
Any suggestions, other than peel my stickers off and mail it back to Amazon.com?
* 1239CET 25 Mar 11 - Edited, I tried z4root, it didn't help my problem.
* 1345CET 25 Mar 11 - ADB now working. Win7x64 Ult.
Click to expand...
Click to collapse
I really think something is wrong there, the correct partition for the bmp is definitely #6 in my tablet,
however in the other recovery (nvflash_gtablet_46_2010112600.zip) in roebeet's dropbox the #6 and #7 are inverted... 16MB vs 4MB but their .cfg is correct
So if you flashed the bird on 7 it's a surprise for me that it worked...
also I am wondering did you change the size if the partition in the .cfg files prior to flashing ??? or did you simply swapped the files? I noticed a few post where people where changing the recovery partition without adjusting the size in the .cfg file...
I would really like to see the list of your partition...
sound like the geek way to ask a girl for a show
read this... http://forum.xda-developers.com/showthread.php?t=934023
your boot configuration table may be bad... so maybe another rom like roebeet suggested would help...
Actually it's bekit's dropbox.
Some of the newer gTAB's have partitions 6 and 7 reversed:
Code:
[partition]
name=BLO
id=6
type=data
allocation_policy=sequential
filesystem_type=basic
size=4194304
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=part6.img
[partition]
name=MSC
id=7
type=data
allocation_policy=sequential
filesystem_type=yaffs2
size=16777216
file_system_attribute=0
partition_attribute=0
allocation_attribute=0x10
percent_reserved=0
filename=part7.img
My first gTAB (the one I currently own) was setup this way, but one dev unit I got in December had them reversed, and bekit had one that was reversed as well. I actually flashed the 1105 bekit image and it had worked for me, at the time.
I do not think the image can be the cause of this problem (as long as the size in the cfg is correct), however I think something is wrong in the early boot process in his case...
The guy in this toshiba forum are playing quite a lot with their partition with nvflash...
http://tosh-ac100.wetpaint.com/page/Repartition+Internal+Storage
Interestingly, reading my partition 11 on my tab end with an error...
Z:\>nvflash -r --read 11 part-11.img
Nvflash started
[resume mode]
receiving file: part-11.img, expected size: 209715200 bytes
/ 209584128/209715200 bytes receiveddata receive failure NvError 0x120000
command failure: read failed
like if the partition was not the correct size by a few bytes...
Roebeet...
I was looking at the ADAM recovery and I think it may explain why some tablet are boot looping or bricked...
the file name they use for the .bct files tell us something...
LCD\harmony_a02_12Mhz_H5PS1G83EFR-S6C_333Mhz_1GB_2K8Nand_HY27UF084G2B-TP.bct
They specify their FLASH (HY27UF084G2B) number in their boot config, this is probably due to the fact that they change their IC from time to time (flash are often on high allocation so manufacture often have more than one supplier) and those change seem to be important enough that they use it as their boot config... (bct probably need to match the memory... or even configure memory speed etc)
This mean that flashing with a BCT that is not specific to the type of memory installed may be bad... but there's no proof that viewsonic had unit with different memory, unless it's one of the difference between the 300 and 320 unit you where mentioning..
Interesting. One thing about the Adam and the VEGA that I always liked is that we have at least on vendor-based nvflash config from them. Even the Viewpad10s has one. But we never got an official one for the gTablet - bekit's version is fantastic and still the defacto standard, but it's not the vendor's.
I keep wondering if the latest holdout on their stock release is because they want to deploy an nvflash version. It's not in the realm of impossibility, given that the Viewpad10s already has one. And it would certainly be a good way to give users a backout in case the update.zip fails (Viewsonic, you reading this?). A vendor-based nvflash config would be a wonderful thing, if they offered it. Well, we can hope....
michael...
Did you try in nvflash to set the boot partition ?
--setboot N
sets the boot partition to partition N
roebeet said:
Interesting. One thing about the Adam and the VEGA that I always liked is that we have at least on vendor-based nvflash config from them. Even the Viewpad10s has one. But we never got an official one for the gTablet - bekit's version is fantastic and still the defacto standard, but it's not the vendor's.
I keep wondering if the latest holdout on their stock release is because they want to deploy an nvflash version. It's not in the realm of impossibility, given that the Viewpad10s already has one. And it would certainly be a good way to give users a backout in case the update.zip fails (Viewsonic, you reading this?). A vendor-based nvflash config would be a wonderful thing, if they offered it. Well, we can hope....
Click to expand...
Click to collapse
I think it would better and safer if people would do a capture of their unit rom instead of using a generic one as a backup.
Would be nice to see one from Viewsonic as well, I hope they hear you!
P00r said:
I think it would better and safer if people would do a capture of their unit rom instead of using a generic one as a backup.
Would be nice to see one from Viewsonic as well, I hope they hear you!
I tried to locate that viewpad recovery with no sucess, ca you point me in the right direction ? tnx
Click to expand...
Click to collapse
Well, it WAS here:
http://ap.viewsonic.com/in/downloads/
But now it seems to have been pulled. Weird. Maybe check back in a day or two. I already looked at their firmware and it's very similar to the Advent Vega 1.0.9 firmware (sister devices).
I have downloaded the VEGA image restore, they left inside the utility used to create the .BCT files
the help for this utility confirm the bct is linked to the flash chips
as well as to the image (not sure which...)
Usage: buildbct [options] Configfile ImageFilename ChipName
options:
-h, --help, -? Display this message.
-d, --debug Output debugging information.
Configfile File with configuration information
ImageFilename Output image Filename
ChipName Name of the chip, currently valid --ap15
This mean using a generic bct may be risky if viewsonic have more than 1 type of hardware tablet with the same name...
Makes a lot of sense, to me. I honestly think we've been very lucky so far (most of us). Bekit and I must have the same device as his backup has never failed me. And, as you can imagine, I have flashed my device a LOT.
We don't know the hardware differences - why are some of the newer devices shipped with switched partitions? Why is it that at least one XDA user got a 320, when they paid for a 300? And if those Woot devices really are new, who's to say that the hardware inside isn't slightly different. Maybe our mods won't work on them regardless of what we do.
The other problems are that 1) Viewsonic isn't telling us and 2) we aren't keeping any metrics on this. We had this issue with the Pandigital Novel, but it was only two boards - eventually we could find ways to distinguish between the two (we called them "v1" and "v2" boards. I even opened them up and could tell that way. But, so far, we don't know if this is the case with the GTablet.
This 320 series will be interesting to watch
I do not think the order of the partition should have any impact, looking at other device they are all organised diferently, only their descriptor and file system seem to matter (YAFFS for the user accesible section) but it does show they played with it
Thanks for the comments and help
Thanks everyone for the comments and help. I checked Amazon and since I was on day 30, I did an online RMA and sent it back, so I didn't try the Adam idea. I did confirm it is not a model 320 though.
P00r - I did try the Setboot N command, pointing it at partition 10, since when I put the CWM image there it booted to it. NVFlash hung and I CTRL-C'd it after about 3 minutes.
When I swapped partition 6 & 7, I did swap the config info also, so the partition size and file system were correct per the cfg file normally.
The bad GTab and new replacement will cross in the mail, hopefully Gojimi's GB is out of experimental and into Beta by then
The whole BCT is still a mystery (to me at least). I've posted about that, and if I recall, responded to official viewsonic suggesting they provide info on that plus partition table, etc. I have yet to find any info on what the BCT actually is, but have seen from posts on wetpaint that messing with it or changing it can bork your device.
That's one of the reasons I'm still stock. Don't want to get into a situation where nvflash is the only resort.
The other reason I haven't tried to flash using nvflash is the bad blocks I mentioned awhile ago, and not being able to nvflash/read all my partitions. Figured that if it can't read all partitions, it probably won't be able to write them either .
Just ordered a 2nd Gtab from the woot deal, so I'm curious if that'll show bad blocks in dmesg, and if I'll be able to read all partitions w nvfash w the new one...
Jim
When the new tablet comes in, I'll pull the partition list and post it. Is there any other info from a bone-stock machine anyone would think is useful?
michaeljwestii said:
When the new tablet comes in, I'll pull the partition list and post it. Is there any other info from a bone-stock machine anyone would think is useful?
Click to expand...
Click to collapse
Happy to hear you cane exchange it!
Can you try extracting all the partition, I got an error on my partition 11, and I think Jim is right about the bct also used to map bad block in the flash...
I am just curious to see if this error is there on a virgin unit!
I can send you a batch files for the command
First, you need to be sure you install the sdcard version of the recovery, otherwise you won't be able to do this. (You need to goto this thread to install the sdcard version and follow instructions.
First of all, make sure your drivers are setup properly as this is a windows script to fix everything since you can only fix it from a computer. (I CANNOT EMPHASIZE THAT ENOUGH!)
Then you just download this zip, it check's md5 sum on the image before flashing so no worries, and then it flashes. It will reboot when it's finished.
I am in NO way responsible should anything happen, it was your fault for not checking the app's md5 in the first place so if this works for you, openly admit that you could have been better with handling the app's flashing. <-- Required.
I'm having a seperate thread so I can actively update this with anything that may arise since it would make my app's thread cluttered.
Read the whole thread or enjoy a broken Ntab, it's your choice.
Just wanted to say thanks for the dedication to those of us not smart enough to figure things out on our own.
Sent from my BNTV250 using Tapatalk
is this for those nt cannot use sd card recovery or 8 times boot break to restore the originally rom?
Dumb Question
Total noob question. What do you mean by drivers set up properly? I want to try this, but I do not want to screw up again, and I just want to be totally sure I understand this properly. Thanks.
Benblanko81 said:
Total noob question. What do you mean by drivers set up properly? I want to try this, but I do not want to screw up again, and I just want to be totally sure I understand this properly. Thanks.
Click to expand...
Click to collapse
Means that you must have your nook drivers installed and working, if you ever rooted then you should have your drivers working properly.
~ Veronica
Can't get this to work
I have verified that I have the proper drivers (thanks Veronica). I unzip the fix and run the batch file, but the window closes almost instantly. I am using an XP machine, because of installing the drivers when I rooted. I can not for the life of me figure why it wont run. I am booted into the sd card version of CWM. Do I need to mount it some way or just at the home CWM recovery screen. I have been looking for help without asking and bothering, but can't figure it out. Not a noob but totally confused. Any help would be appreciated. Thanks.
Oops! I managed to set the wrong error levels on it, I meant to do 0 and 1, I instead did 1 and 2. Anyway, uploading now.
Still no go.
I got the batch file to run but it does not finish. It starts the Deamon successfully, and it just stays at Deamon Started Succesfully. It has been there for about 45 minutes. Should I wait or can I kill it and start over. Thanks again.
Kill it reboot your machine and start over
Sent from XDA premium using my Nook Tablet
No Go
Thanks Veronica, but the reboot still does the same thing. I just started the Nook&Zergy and the device shows up so I know the drivers are proper, it just stays stuck in Deamon Started Successfully for the fix. I am out of ideas, I fear I have just bricked my first device. I have doing this since the G1, this is sad.
No no, just do:
adb push cwm_internal.img /sdcard/cwm_internal.img
adb shell
then type:
dd if=/sdcard/cwm_internal.img of=/dev/block/mmcblk0p3
First off great work Indirect. This is exactly what I was hoping that image creator would be used for, just working on other things and got preoccupied. I think you might have to do some explaining though.
One thing to note though is that CWM should not be used for any other then rooting your device. As it stands right now there is no reason to flash it to an internal partition, you will only risk messing something up, as it has no gains.
Overview:In the Nook Tablet world there is a locked bootloader, which requires that there be a Secure Chain from u-boot, to the recovery. With the exploit that bauwks discovered and designed, we are able to flash custom recoveries on to the device. However a recovery must be packed.
Packing Structure:There are two ways that we have been able to go about getting around the boot loader, the internal method requires that we use the second U-Boot, with a 256k buffer and then attache the recovery after the buffer.
(0-m bytes) ------> (m-256k bytes) ------> (256k-n bytes)
Bauwks ntBoot Buffer nemiths CWM
The trick is that that 256kth byte must contain the header for the CWM, and this is vital. If that is lost, or something on Bauwks didnt get flashed right, you will enter a boot loop.
FAQ:
What Is a 'broken recovery' NT?
A broken recovery Nook Tablet is one where either the NT's internal recovery structure was not writen correctly or one where the NT's internal recovery structure is missing bauwks boot.
How can I tell if I have a 'broken recovery'?
Assuming you have not messed with any other partitions if you do either the N + pwr method, or the 8 false boots, you should see it open the BN recovery. If your device constantly turns on and off after one of these two methods, then you have a broken recovery partition.
My Nook just continues to boot into the recovery whats this?
Aha now that is not a 'broken recovery' and is actually quite fixable. In the nook Tablet there are two files that relate to the booting structure, aka the selection of where to boot from. These lie on a partition called bootdata, and are named BCB and BootCnt. If you are running stock on your internal partition, just let the stock recovery run, and it will solve your problem. If you are running CWM, you will have to use the following commands,
Code:
adb shell mount -t vfat /dev/block/mmcblk0p6 /data
adb shell dd if=/dev/zero of=/data/BCB bs=1 count=1088
adb shell dd if=/dev/zero of=/data/BootCnt bs=1 count=1
adb reboot
Aaa this is confusing can't I just put the stock recovery on my NT?
Sure. Hopefully indirect will make a script soon, or I will make one tonight that will put the default recovery img back. If you are feeling lucky you can do the following while on CMW.
NOTE: I AM NOT RESPONSIBLE FOR ANY DAMAGES YOU CAUSE TO YOUR DEVICE. One false move and you will brick your device. HIGHLY UNRECOMMENDED
Code:
adb push recovery.img /data (this is the recovery from the 1.4.0 or 1.4.1 update zip)
adb dd if=/data/recovery.img /dev/block/mmcblk0p3 (THIS LINE IS [COLOR="Red"]EXTREMELY DANGEROUS[/COLOR]. It should only be done as a last resort, and you should only do it if you are willing to take full responsibility.)
Dead End.
I am going to start from the beginning. I flashed CWM using this app and the hit reboot into recovery from the app as well. Went to the cardboard box. I can reboot into CWM using the sd card method but can get no further. I have been trying the fix for two days and cant get it to work. Indirect gave me some ADB commands but I cant get ADB to work either. I have been on this for 2 days and cannot get it going. I really do not know what else to do. I am not a Noob and i know I have the proper drivers, the fix gets stuck though, and with the tablet in CWM from the sd card I just cant get ADB to work. I do not know if maybe because of usb debugging not being checked off, but again I can not boot up to Android, just to recovery from sd card. If I take out the sd card with CWM it boots to the cardboard box, then to black screen, and there it stays. I checked the thread for the app and people are still having this problem. I really do not know what to do. I have followed every instruction I have found or has been given to me, to the t, nothing.
UPDATE - I deleted the sdk and everything that had to do with Android from my pc. Reinstalled drivers using the method in the root thread that is pinned. I ran NOOK&ZURGY just to see my device appear in list of adb devices, which it did. It gave me my serial and it said recovery. I then redownloaded the sdk and did not download the Drivers from SDK manager. I am not sure but that seems to be the key here, to get rid of google drivers that can be downloaded from SDK manager. I then opened a command prompt, adb devices and bam there it was. I used the commands posted by LogLud above my post under "My nook just continues to boot into the recovery, what is this?". ADB Reboot and ****ing worked. THANKS TO INDIRECT, LOGLUD, and LAVERO.BURGOS. Your patience and help is greatly appreciated. I have never really asked for this much help before on XDA, and you guys were on the money, Thank You, Thank You, Thank You. Please PM me so that I can get you guys and girls beers. I will try to figure out how on my own anyways, but you guys deserve a contribution for taking the time out of your day to help me and others. Anyone with this issue and is having problems fixing, please post here or shoot me a PM and I will gladly give you all I can. Thank you again to all and happy flashing.
Benblanko81 said:
I am going to start from the beginning. I flashed CWM using this app and the hit reboot into recovery from the app as well. Went to the cardboard box. I can reboot into CWM using the sd card method but can get no further. I have been trying the fix for two days and cant get it to work. Indirect gave me some ADB commands but I cant get ADB to work either. I have been on this for 2 days and cannot get it going. I really do not know what else to do. I am not a Noob and i know I have the proper drivers, the fix gets stuck though, and with the tablet in CWM from the sd card I just cant get ADB to work. I do not know if maybe because of usb debugging not being checked off, but again I can not boot up to Android, just to recovery from sd card. If I take out the sd card with CWM it boots to the cardboard box, then to black screen, and there it stays. I checked the thread for the app and people are still having this problem. I really do not know what to do. I have followed every instruction I have found or has been given to me, to the t, nothing.
UPDATE - I deleted the sdk and everything that had to do with Android from my pc. Reinstalled drivers using the method in the root thread that is pinned. I ran NOOK&ZURGY just to see my device appear in list of adb devices, which it did. It gave me my serial and it said recovery. I then redownloaded the sdk and did not download the Drivers from SDK manager. I am not sure but that seems to be the key here, to get rid of google drivers that can be downloaded from SDK manager. I then opened a command prompt, adb devices and bam there it was. I used the commands posted by LogLud above my post under "My nook just continues to boot into the recovery, what is this?". ADB Reboot and ****ing worked. THANKS TO INDIRECT, LOGLUD, and LAVERO.BURGOS. Your patience and help is greatly appreciated. I have never really asked for this much help before on XDA, and you guys were on the money, Thank You, Thank You, Thank You. Please PM me so that I can get you guys and girls beers. I will try to figure out how on my own anyways, but you guys deserve a contribution for taking the time out of your day to help me and others. Anyone with this issue and is having problems fixing, please post here or shoot me a PM and I will gladly give you all I can. Thank you again to all and happy flashing.
Click to expand...
Click to collapse
Oh well you should had started your first post by saying im using SDK and you will have it fixed faster. SDK is not needed in windows, leave that for devs all the necessary stuff that you needed to root is provided in indirects permanent root thread including drivers.
Glad it worked!
~ Veronica
Please help
I used Indirects app to install CWM, it seemed to work fine, but when I tried to boot into CWM it flashes the picture of the box, then shuts off. I tried using this method to fix it, but the same thing happens.
What am I doing wrong? Please help. I'd hate to have bricked my nook.
lehite said:
I used Indirects app to install CWM, it seemed to work fine, but when I tried to boot into CWM it flashes the picture of the box, then shuts off. I tried using this method to fix it, but the same thing happens.
What am I doing wrong? Please help. I'd hate to have bricked my nook.
Click to expand...
Click to collapse
Did you try the method posted in this thread? you don't mention that , also can you boot normal if you let it or you cant? provide more info.
~ Veronica
lavero.burgos said:
Did you try the method posted in this thread? you don't mention that , also can you boot normal if you let it or you cant? provide more info.
~ Veronica
Click to expand...
Click to collapse
Sorry if I was not clear. Here is the entire process:
1. I have a rooted Nook Tablet.
2. I installed Indirect's One Click App to install CWM
3. I used that app to install CWM.
4. I attempted to boot into CWM, but it flashes the box and then shuts off
5. I came to this thread and began following the instructions to fix it, but the fist set of instructions "First, you need to be sure you install the sdcard version of the recovery, otherwise you won't be able to do this.(You need to goto this thread to install the sdcard version and follow instructions.)
6. I followed those instructions, but I still get the box image then shut down.
7. I can't boot normally or into CWM.
Let me know if you need any other information and I greatly appreciate your help.
What I really need to know is how to create the CWM sdcard on a mac. i.e. I don't have a linux machine with gparted and I can't figure out how to get something like Disk Utility to enable boot and lda flags.
Thanks!
bootable sd card with osx
Lehite, I was having the same problem, i.e. disk utility in osx couldn't do the job for me. I ended up using this method.
Download the “size agnostic” CM7 SD card installer image (v1.3 in my case), then write it to your microSD following the instructions on the before mentioned page. The writing takes a little bit without terminal telling you the progress, after 1-2 minutes it should be done.
After succesfully writing the image to your SD card copy the files from Goncezilla's SD Boot thread (here) to your SD card overwriting files if necessary and follow his further instructions.
On a reboot with the boot SD inside your nook you should get to the CWM menu after seeing the cardboard box. good luck!
I myself am also stuck at the black screen after the box and need to figure out how to get the ADB working on osx to be able to do Loglud's commands...
UPDATE: to get ADB working on osx I used this method. Since I'm not a developer I didn't download the whole SDK package from google but rather just the ADB tools from here.
I then connected the Nook to the mac while in CWM, checked if it was properly recognized but typing adb devices, and applied Loglud's adb commands. BAM! worked! Am back in android Many thanks to all for directions, especially Loglud.
Now a question to Indirect, I downloaded your package just today, while using it it verified the MD5 positively and continued flashing. Why did I get the black screen, and not the CWM?
cheers
Today I tried to flash the CyanogenMod 9 Nightly 06-30-12, coming from Build 35 of AOKP and after factory resetting and clearing Dalvik I went to install the zip and while flashing it I got a build-prop related error!
All of my NANDROIDS gave me a data error when flashing and now I am pretty f'd! I /really/ need to fix this ASAP but have no idea how.
-Samsung Galaxy Tab 10.1 Wifi-
-CWM 4-
On a second note, does anywhere know where I can get my screen replaced for cheap? I dropped my tab a few months back and the screen got MAJOR cracked, though it still does technically work (I still use the screen, it works but it's cracked is all...) and after calling Samsung and waiting for over 1 and a half hours they told me they wanted $150 to fix it, which if I recall is about half of what I payed for it anyway...
To be honest, I'd be lying if I said I was happy with Samsung over all.
I mean, bad customer support, the proprietary connection cable, and lack of official updates (along with the ugly TouchWiz that I'm not sure /who/ likes ) don't make me that happy...
Anyway, can anyone help me please?
Thanks in advance!
Update your recovery: http://droidbasement.com/db-blog/?p=2655
If you have a GT-P7510 (p4wifi), in this post are flashable zips (with your current recovery) of CWM and TWRP, in case you prefer this method: http://forum.xda-developers.com/showpost.php?p=28051448&postcount=29
After that, flash your ROM like always.
Yeah, thanks, were it so easy. I fired up ODIN multiple times, no matter what, unsuccessful. Like always, my computer would not recognize my tablet. Yes, I have the bloody Samsung drivers, yes I've tried reinstalling them (several times in the last few months), yes I've tried using different USB ports! And what? Nothing. Nothing at all. For the last few months I have not been able to transfer movies/music to my tablet via file transfer and I can't even get the stupid odin download thing to work. To be honest, I really am pissed off with this broken pile of trash. Would trade it in for a similar tablet any time.
Did you try any of the flashable zips for a new recovery?
About the USB, it sounds like a different problem, but for the file transfers, are you sure you have MTP selected? (answer #5 --> http://forum.xda-developers.com/showthread.php?t=1642009 )
If you haven't tried it yet, you could use a different computer, another OS (some Linux distro and check that adb works), change the USB cable.
I can't use a flashable zip since I can't copy files onto the tablet >.>
Also, yes, for file transfers I /do/ have MTP selected always and it doesn't work eitherway.
Essentially, I am stuck with a $300+ ugly and broken thing that I can only use as a paperweight for the huge mess I call my desk. Yay.
>Rage sidenote; Samsung, go take the money I payed for **** and shove it.
And I guess you don't have your old ROM (AOKP build 35) in your tab.
Try with adb (in recovery), but if you can't get a working USB connection (using other computers or OS), maybe there's something physically wrong with your tablet.
No, I don't. I'm stupid enough to delete the ROM zip after flashing it to save space on the tablet...
How do I do this ADB thing? I've heard of it before alot but never used it or looked into it...
Read this: for windows -> http://forum.xda-developers.com/showthread.php?t=1387527 , for Ubuntu -> http://forum.xda-developers.com/showthread.php?t=921169
After everything is installed, boot your tablet into recovery and try running in your command line application (CMD for windows):
adb devices
If it shows that a device (and ID number and the actual state, e.g. recovery) is connected, your golden!
If you have another android device, try it too, to be sure that is working.
To transfer a file the command is
adb push /path/to/file /path/in/tablet
In windows I guess is something like this:
adb push C:\path\to\file /path/in/tablet
so I'd do something like
adb push C:\ADB\CWM-5.5.0.4-p4wifi.zip mnt/sdcard/ ?
Im dling the ADB files right now
adb push C:\ADB\CWM-5.5.0.4-p4wifi.zip /mnt/sdcard/
You need the slash at the star and end of the path of the tablet.
While installing PdaNet it failed, said it couldnt connect through to the device or w/e
Also,I don't recall having ADB on when I had the tablet. I might've but I don't think I kept debugging on for the general time...
This is so frustrating >.>
I'm not sure about that error in PdaNet, I can help you with adb but I don't use Windows, so there's things I can't test.
If you didn't select ADB debugging in your ROM it doesn't matter, you're doing this from recovery.
BTW, do you have other android device?
adb seems to be working and copying, but I can't find the file in Recovery while doing choose a zip to apply!
Yes, I have an LG Optimus V on Virgin Mobile running tdm's AMAZING Quattrimus Alpha 10 on Ice Cream Sandwich/ Android 4.0.4
this is what I get
C:\Users\Mikoyan Gurevich\Desktop\LG Drivers>adb devices
List of devices attached
43C800340009517 recovery
C:\Users\Mikoyan Gurevich\Desktop\LG Drivers>adb push C:\CWM-5.5.0.4-p4wifi.zip
43C800340009517\sdcard\download
1328 KB/s (4147569 bytes in 3.048s)
C:\Users\Mikoyan Gurevich\Desktop\LG Drivers>
If you connect your phone and execute
adb devices
What's the output?
If you do the same with your tablet, what's the output?
with the tablet it's
C:\Users\Mikoyan Gurevich\Desktop\LG Drivers>adb devices
List of devices attached
43C800340009517 recovery
with my phone it doesn't wanna show up in Recovery or not.... Hmm.
Well, it shows fine, then you should be able to transfer the files
First, in your recovery, go through the steps to install some zip file, but just go as far as selecting the directory, then go back
Now in your PC try running something like this, change your path in windows:
adb push C:\CWM-5.5.0.4-p4wifi.zip /sdcard/
The in your recovery, select install and should show there. The thing is that most likely the sdcard wasn't mounted in your tab
Edit, to mount your sdcard in recovery do: mounts and storage > mount /sdcard > Go back
The do the transfer in your PC.
Hmm
While I was holding it to my gut, pushing the end of the cable into my stomach (It was the only way to get it to be recognized) I fooled around and went into download mode, hoping that on the contrary I could do that, turn it off, and when I went back into Recovery it would be there when it finally said the cable WAS connected and then I rushed to open Odin and wrote it through, and it frickin' wrote CWM v5 right on and it worked, I'll be damned!
Maple, I can not thank you enough for helping me with this, I am in great debt.
You're welcome, I'm glad it worked. Knowing how to use adb is really useful. And now you know that something is wrong with your cable.
Or in the connector pins or w/e of the tablet... The cable works fine for charging though....
You are my savior, bro.
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
This is not an Android project so I don't feel that posting it in the Android Development forum would be appropriate.
ArchLinuxARM for the manta (Samsung/Google Nexus 10) - Native Boot
Working:
Wi-Fi (with NetworkManager)
Audio (requires manual intervention)
Not Working:
Bluetooth
2D & 3D Accelerated Graphics
Installation (to a subfolder of the /data partition)
You will need a Terminal Emulator or ADB Shell to install.
This assumes that arch_manta_20141210_root.tar.gz is in the root of your internal storage (/data/media/0).
Code:
su
mkdir /data/local/arch
tar -C /data/local/arch -xpzvf /data/media/0/arch_manta_20141210_root.tar.gz
Booting
Since there is no workable multiboot solution for the Nexus 10 yet, you can take one of two routes to boot this thing:
Option 1: Flash the arch_boot.img to either the recovery or the boot partition of the internal flash chip. Due to risk of BRICKING if you flash to the wrong partition, I will not provide instructions here. I might make a flashable zip later on. Note that this removes access to Android.
Option 2: Use Fastboot to tethered boot the provided kernel from another computer where it is installed:
Code:
fastboot boot boot_arch_manta.img
Logging in
The username is "arch" and the password is "archlinux". Change the password ASAP.
For root, the username is "root" and the password is also "root". CHANGE THE PASSWORD ASAP!
You'll probably want to enable the On-Screen Keyboard (onboard) and set your Session to "MATE" up in the top right corner.
To make audio work after booting and logging in, run "fix_audio.sh" in a terminal.
Read Me
If you WIPE DATA, it will also WIPE OUT THIS PORT, all its applications, and any files you may have stored within it!
Downloads
root filesystem archive: https://drive.google.com/file/d/0B4WUjKii92l2Qkd6S3c3M2tDcTQ/view?usp=sharing
kernel for fastboot or flashing: https://drive.google.com/file/d/0B4WUjKii92l2UGhIWTlVam5vSk0/view?usp=sharing
Kernel Source: https://github.com/willcast/kernel_manta
Also available for:
Nexus 7 2013: http://forum.xda-developers.com/nex...fficial-archlinuxarm-release-n7-2013-t2969301
Galaxy S3 LTE: http://forum.xda-developers.com/gal...unofficial-port-archlinuxarm-release-t2969290
HP TouchPad: http://forum.xda-developers.com/hp-touchpad/other/unofficial-archlinuxarm-release-hp-t2969310
HTC HD2: http://forum.xda-developers.com/hd2-ubuntu/development/unofficial-archlinuxarm-htc-hd2-t2970483
Free space required?
Started with 5GB+ before downloading the 1.5 tar.gz, thought it will be enough but I'm supposed it wasn't cuz I'm getting "No space left in the device" although I still have 537MB free left.
Hmm, shouldn't do that. The archive itself is 4,060 MB uncompressed according to gzip -l.
Try booting it anyway, maybe? Also, perhaps I uploaded a truncated archive. I'll have to check.
Edit: Wait, you'd need upwards of 5.5 GB free to have both the archive and the extracted files on /data.
So, I deleted my nandroid backup and was able to install it. Actually it runs very well, I think even better than when ubuntu was being officially developed by canonical for the nexus 7. Of course it was easier to run because of the MultiRom solution, always wonder why Nexus 10 it's not supported, like Nexus 4, 5, 7 and even som non-nexus devices.
tavocabe said:
So, I deleted my nandroid backup and was able to install it. Actually it runs very well, I think even better than when ubuntu was being officially developed by canonical for the nexus 7. Of course it was easier to run because of the MultiRom solution, always wonder why Nexus 10 it's not supported, like Nexus 4, 5, 7 and even som non-nexus devices.
Click to expand...
Click to collapse
I don't know, honestly. After I'm done with the HD2 flash-image port of this, I'm looking at porting kexec hardboot from a random old Epic 4G kernel to my kernel_manta on github, because that's the only ready-made Exynos hardboot patch I can find through google. Then, we could boot this with a script similar to the Galaxy S III LTE port, and someone could theoretically port MultiROM, though that someone is probably not going to be me.
Thank you, Castwilliam! It run good , with some gitch on screen, but better than ubuntu phone devReview .
But when I run pacman -Syu ( update packages), reboot and it become blackscreen, try many taps in middle touch screen, intensity light of screen is something change. What wrong when update packages in pacman ?_?.
Is the booting option 2 temporary? Can I just turn off nexus and boot back to android? Can I unplug the nexus from PC while running linux?
I have no idea what I am doing here (and you probably dislike dealing with noobs flooding forums with questions right? :silly: )
Dri0m said:
Is the booting option 2 temporary? Can I just turn off nexus and boot back to android? Can I unplug the nexus from PC while running linux?
I have no idea what I am doing here (and you probably dislike dealing with noobs flooding forums with questions right? :silly: )
Click to expand...
Click to collapse
Yes, yes and yes
Hello,
This is awesome work! It booted properly, connected to a network, and programs run just fine. But as the tablet's pixel density is pretty high, it isn't too comfortable to use. I tried adding a new resolution using xrandr, but it throws something along the lines of "failed to get gamma size for display default". I've tried googling for it, but nothing worked. What can I do to resolve this?
Thanks,
Vedanth