Related
Hello guys,
OTA update failed on my hero and I can't do anything right now. I understood from other topics that it's possible to use goldenimage card formatted on one android to use it on another. I don't have GC right now and I'd like to 4 question:
1. Did anybody try to use goldencard on hboot 007?
2. Did anybody try to boot GC (which was created on another phone), on hero?
3. What SD Cards did you use [Stock SanDisk[2GB] or others [Names please]?
4. If second question is true, there is a way to create an image for goldenCard and by thus it'll help to newbies like me to survive first flash. Might anybody who uses linux or winhex may help?
Available SD rippers: WinHEX [Windows] and Linux [HexDump].
Thanks in advance,
MrBora
Download this file: ftp://xda:[email protected]_2.73.405.5_WWE_release_signed_NoDriver.exe
Run it. Once you see the ROM update utility GUI, search c:\users (windows 7) or c:\documents and settings (other versions) for a file called rom.zip.
Rename this file HEROIMG.zip and get it onto your SD card.
I think it's HEROIMG.zip. It might be HEROIMAGE.zip. I'm doing this from memory but I'm pretty sure it's HEROIMG.zip.
Power on the Hero holding the VOLUME DOWN button. It should scan the file and then ask you if you want to update. Say yes. This will restore you back to factory and should be able to go from there.
I tried that and I got incorrect CID
If i'm doing it through Windows i'm getting hero 131 customer ID error
thx
Thats because you need to keep trying the goldcard method..Ihad to make the goldcard 3 or 4 times before it worked,used the standard card that same with the Hero (sandisk)
guys it worked with KingSton 2GB image. I succesfully installed stable image, but i can't now to use fastboot for rooting. Write failed. Is there a way to downgrade hboot? no need. with flashapp it works like a charm.
in any case i'll create an image for goldcard
why cant i get the driod to boot upon my hd2
seidel6969 said:
why cant i get the driod to boot upon my hd2
Click to expand...
Click to collapse
Don't know. Give us some more information:
Witch rom
witch radio
Witch Android build
what did you do, what do you see!?
We are able to help you if you give us some more details.
PS you need to have minimum Radio 2.08 on your device fore be able to run Android.
um im not sure im not that good with phones how do i find the rom the raidio stuff
Q; Witch Rom/Radio version do I have?
Go to your setting tab > Info about your device > Software Info > You can see your Rom/radio version there.
rom is 2.12.531.1(90963)wwe
radio is 2.10.50.26
seidel6969 said:
rom is 2.12.531.1(90963)wwe
radio is 2.10.50.26
Click to expand...
Click to collapse
Based on the info I know/see it seems your device software is compatible with Android. So try this:
1. Format your SDCard with FAT32 (backup your data first) (what kind of card do you use? (size) (some users mention to have troubles on 16GB SD cards))
2. Copy your android to your SD card (read the installation guide of the chef, not all Android Builds runs from /Storage Card/Android)
3. Run CLRCAD.exe and then Haret.exe.
4. Be patient, it will take a few minutes at the first boot.
5. if you complete the setup process reboot and then you can do what ever you want.
Normally this must work.
how do i format my sd card to what you said how do i back up my data and its a 16 gb
seidel6969 said:
how do i format my sd card to what you said how do i back up my data and its a 16 gb
Click to expand...
Click to collapse
First of all get start on a other SD, to much peoples have problems with that.
Format SD: (tittle is deferent but it is the same way)
Backup date? copy it to your PC
Attention if you have a software like Navigation software on your device there are mostly a protection key placed on your device (anti piracy) so don't format your SD, you will loose your installation key!
when i tryto boot it it tells me the job control is turned off
seidel6969 said:
when i tryto boot it it tells me the job control is turned off
Click to expand...
Click to collapse
Did you tray what I have mention! I mean install it on a other SD!?
Make sure the SD card is format.
Ow PS; witch build do you use!?
Give me the link pleas.
http://www.multiupload.com/UDBG8J4TMG
This is meant to be a basic guide to installing and maintaining Android (SD CARD/RAM) on your HD2
NOTE: This guide is not meant for NAND versions of Android installation !!
I want to thank all the XDA forum developers who have made it possible to put Android on the HD2. This is my attempt to make a simple guide for what can be confusing and somewhat scary process (It certainly felt like that to me!!).
For detailed information guide and FAQ please read this thread by mskip
For clear explanation of how things work in Android on HD2 these two threads have excellent detailed information:
http://forum.xda-developers.com/showthread.php?t=813434
http://forum.xda-developers.com/showthread.php?t=790095
Click to expand...
Click to collapse
Before you start you need this Info
Windows ROM version > All Ship ROMs are compatible
Radio Version > Radio needs to be 2.08.50.xx or more (x.xx.51.xx are not compatible)
SPL
Click to expand...
Click to collapse
How to get the Info
For items 1,2 in WinMo look under Settings>About Phone>Software information
This info is also displayed on the bottom left corner (the numbers after the alphabets R,D,G) of your initial boot up white screen with green HTC logo
For item 3 >> Turn phone off > Press and hold Volume down button >briefly press release power button >SPL version is displayed on bootloader screen (Red/Green/White)
Click to expand...
Click to collapse
For those with Radio > 2.08.50.xx you can install Android >> GO TO STEP B
Click to expand...
Click to collapse
For those with Radio < 2.08.xx.xx you cannot install Android without upgrading your Radio (Flashing a new Radio) >> GO TO STEP A then STEP B
Click to expand...
Click to collapse
STEP A (Flashing a new Radio)
If you do not have a compatible Radio version follow the steps below:
Upgrading to the newest HTC stock ROM: This process will upgrade your Radio version anyway (The latest 3.14 ROM has Radio version 2.14.50.4 which is compatible with Android installation): LINK HERE
If you don't want to / or can't upgrade to the latest HTC stock ROM you are going to have a slightly more complicated way
If SPL is 2.10.xxxx or below then use HSPL method. Click here
If SPL is more than 2.10.xxxx you have 2 choices (since HSPL does not work)
Use SSPL method click here
Downgrade your SPL and then use HSPL method click here
Note:
>>Please check the radio version recommended by the Android Build maker>>
>> Click here if you want to download Radio versions
Click to expand...
Click to collapse
STEP B (Installing Android)
If your Radio is compatible (>2.08.50.xx) then here is how to install Android on your HD2
1) Micro SDHC card
Should be atleast 4 Gb, Class 2/4/6/8/10
Formatted clean with 32 or 64 Kb cluster size
2) Install automatic boot loader on WinMo :
This allows you to choose between booting into Windows or Android on start up. From 2nd Android bootup onwards these programs will make it easier to load Windows/Android at startup and you can even specify autoboot into Android if you wish.
Download this as a cab file and install in the phone memory (not in SD card)
Android Loader v6.0 Final for HD2
Exceller bootloader
You can of course manually always boot up Android anytime from Windows File Explorer by running CLRCAD and then HaRET files included in the Android build (see below).
3) Android Build :
Download your chosen Android build on your computer.
Extract / Unzip the folder on the computer
Now copy into the Root of your SD card.
Folder should be labelled "Android"
Once copied into SD card you will see 2 files: CLRCAD.exe and HaRET.exe which have to be run to boot into Android.
There will also be other folders / files (Android Apps, initrd.gz, system.ext2, rootfs.img, zimage, startup.txt, ts-calibration) please leave them as they are.
There are many choices in builds available, such as - MDJ, Darkstone, MIUI,. Please search the forum to look at the different features. I can't advise you on what clothes to buy. The same reasoning applies to advising on Android builds, you have to find out what is right for you...Try the build, if you dont like it, just go for another build..copy and paste your new android folder over the old one and its done.....
4) Data.img :
Your build may have a ready-made one included in the build folder or available to download separately. Size of data image is upto you, 256Mb/512Mb/1Gb (or more). This determines the Size of your Android operating system space for settings and downloaded apps etc. Bigger size allows you to keep more apps etc.
>> At start up if you have a ready-made data.img file, booting up in Android is much faster (5-10 min). (You can choose the image size yourself with this option)
>> If you boot up without a ready-made data.img (Clean Install), then this is created by Android system at first bootup which takes longer (up to 30 min) Here the system will choose its own set default image size depending on startup commands in the build. Its not easy to change this size once its created (although it is possible)
5) First Android Boot
Once you have reached this step you are all set. It really is that simple!
These steps are performed with the phone booted in WinMo
Charge your phone to 100%. This ensures proper battery calibration.
In your File Explorer open the Android folder on the SD card
Run CLRCAD - Nothing seems to happens - This is normal. !!!
Run HARET - Small pop up window with grey progress bar appears with message HaRET LINUX BOOTING - You should then see some text lines in the top left corner of the screen and then a Splashscreen (blank screen with a HTC logo) Please be patient and allow time for the initial bootup.
If Android loads successfully, then (depending on your build )another Splashscreen will appear and then the Lockscreen for Android is launched.
Set up your phone for first use as per onscreen instructions and let all account finish syncing before doing anything else
Click to expand...
Click to collapse
Once you are up and running here are some of my own tips to maintain your system.
1) Always back up of your data.img file on to your pc/mac (weekly)
This is better done in WinMo. This will mean that you can always have a failsafe arrangement for troubleshooting.
2) Troubleshooting (If you start getting data corruption errors or force closes .
> Make another Clean Install of the build -Boot into Android- Reboot in WinMo - Connect to Computer - Copy backedup data.img file into the New (compatible) Android folder.
DONE! you are back where you started. All apps, settings, contacts,emails, messages are saved as they were at the time of backup.
You can also use a backup programme like Titanium Pro. This is useful when going over to a completely different chef build as you cannot (usually) take your old data.img file across.
3) Changing kernels
Follow instructions on the relevant thread.
For MDJ / Hastarin Kernels the following steps work
Boot up in windows - copy 'zimage' and 'Root' folder (which has modules) from the new kernel and paste into your /Android folder on SD card (i.e replace zimage of old kernel).-
Boot up android - check for successful upgrade under Settings>About phone>Software>Kernel ... the new kernel should be listed.
On boot up android will copy the contents of the /Android/Root folder to the relevant place.
If upgrade is successful then while in Android use a File explorer (with root permissions) to delete the 'Root' folder within Android folder, as this is no longer needed.
Note: Some kernels require the Modules (wifi,bt,lights etc) to be copied manually using Root File explorer while booted in Android. Please check the relevant posts for correct steps.
4) Upgrading Android Builds
I always do a clean install i.e let the Android build its own data.img with a clean formatted SD card.
Once this is done then copy your old backed up data.img and overwrite the newly created data.img to get all your info and settings as they were.
Caution: data.img is usually not compatible across different chef builds and its best to start a clean install if you are going to use a completely different build altogether. You can get you settings back by using a backup programme such as Titanium. Google sync will get your Contacts and Calendar back anyway if you have synced it previously to Gmail account.
5) Improving Battery Life
Having read through a lot of forums and trying out various techniques here are tips that have worked for me.
Charge your phone in WinMo to 100% (Green LED) While still connected to charger boot to Android and wait for the LED to go green. Then disconnect from charger.
Autoboot before launching into windows/sense fully, I use Exceller autoboot in 3 sec.
Rebooting Android 2-3 times after initial install and letting it 'settle' for a 1-2 days
Turn off any functions not required e.g BT, WiFi, GPS, Autosync
Turn down screen brightness to minimum
Use a battery current widget to monitor drain
Conditioning of battery: Boot into windows when battery is @ 5%, Discharge the battery fully and let the phone turn off> charge fully to green LED while phone off >> Boot up in Android and continue charging till LED green>> One cycle every 2 weeks
Recalibration: In Android with File explorer (e.g ES Explorer), Choose settings, enable root access and then in Root delete ... /data/system/batterystats.bin . This should be done when 100% charged, Now disable root access in file explorer and close, Run the battery down fully and follow the step above...
Fully conditioned battery should show about 4.2 - 4.3 V charge at 100% (Free app Battery Indicator)
Dataswitch (free app) allows switching mobile data when phone is not in use such as during night time etc
I keep Airplane mode in windows as default before first boot in Android (Not sure if this really helps)
For me greatest battery drain seems to be when i am in area of poor phone signal> switching to 2G helps using Dataswitch app
Things that don't work:
Task killers are not really very useful according to Hastarin
For more detailed information regarding battery life issues have a look at this post
Click to expand...
Click to collapse
Have fun and enjoy your HD2 with Android
"Radio Version > Radio needs to be 2.08.50.xx or more"
more correct
Noob question
Hi!
ive done all this last summer, and it all works fine.
but i wonder if android will work if you have the original WM6.5 insted of Chucky, and other costum ROM?
i mean, the customs are really ugly, and i never use them on dual boot - but i would use WM6.5 if i had the original one, with sense and everything.
the dual boot would be more useful. now i only use android.
Proz00 said:
"Radio Version > Radio needs to be 2.08.50.xx or more"
more correct
Click to expand...
Click to collapse
Updated, Thanks for that.
loni90 said:
Hi!
ive done all this last summer, and it all works fine.
but i wonder if android will work if you have the original WM6.5 insted of Chucky, and other costum ROM?
i mean, the customs are really ugly, and i never use them on dual boot - but i would use WM6.5 if i had the original one, with sense and everything.
the dual boot would be more useful. now i only use android.
Click to expand...
Click to collapse
I agree with you on that. The stock ROM work fine (check my sig) and to be honest I tried the custom ROMs but felt more comfortable with the Stock ROM. It means less messing around with your phone!
Its most important however that your Radio is compatible though. If its not then there is no choice but to Flash a new Radio ROM.
Seems to be well explained, thanks
What is the advantage of letting the Android build create its own data.img first and then overwriting it with your previous data.img?
Ahh i just told mate at work copy android to sd card run cllr then haret.
Worked fine lol
omershahab said:
What is the advantage of letting the Android build create its own data.img first and then overwriting it with your previous data.img?
Click to expand...
Click to collapse
This only applies for Upgrading and not a New install. For a new install its always better to let the system create a data image or use the 'empty' image supplied with the build. Most builds have codes to create a default size image. If thats not to your liking then you can choose a supplied image of desired size and do the first boot up...
For upgrading purposes this method has advantages
1) it ensures a clean trouble free installation first time (makes sense to avoid any conflicts with the old data image on boot up.)
2) If there are any problems with the build then at least you can identify them before you transfer the old data image.
solid.snake said:
Seems to be well explained, thanks
Click to expand...
Click to collapse
Your welcome
Difficult to express how easier you made this process for me, with all info provided.
In my name, and the name of all the rest,that will use this thread to start with Android on HD2...... txs
Updated
updated info on maintanence and battery life
despy1989 said:
updated info on maintanence and battery life
Click to expand...
Click to collapse
I just added a link to your thread in my signature if you don't mind. Hoping it will provide easy access for all users
KrewsialNL said:
I just added a link to your thread in my signature if you don't mind. Hoping it will provide easy access for all users
Click to expand...
Click to collapse
Not at all Reminds me I have to do the same on my signature too
Hey, would doing this void my warranty/contract insurance?
Im on virgin media UK, if that helps.
Thanks for the great tutorial anyway
Unless u install a HSPL my understanding is that there is no reason to void your warranty. But I m no expert in these matters. Having said that my old hd2 touchscreen was freezing and I had hspl on it but managed to reinstall the original SPL back and returned it to virgin and this one is the replacement..they didn't complain ..
Sent from my HTC HD2 using XDA App
I have radio 2.07.51,22_2 and spl 1.42
Does that mean the only way I can do this is the HSPL method?
Great guide m8 good job well explained, but I dont know if this helps anyone but I always un-mount my SD card before a reboot or shutdown, on some builds it can reduce corruption to your data image (ie cedesmiths builds)
JR
@ samdeath . Have u considered upgrading your HTC stock ROM? The new 3.14 ROM also upgrades ur radio. In that case there is no messing with HSPL. The other option is SSPL which does not change ur original SPL.
@ JR . In theory if u umnount the SD Card in Android, it only delinks the the SD card portion outside of your data image? If u umnount the whole SD card then android would crash.
Sent from my HTC HD2 using XDA App
I cant upgrade the stock rom, there isnt a virgin media rom on the htc website, and the normal one says my device is not eligible for it. However, ive installed HSPl now, and followed all the steps, changed the radio to 2.15 etc, However now ive just "installed" android for the first time and its been on the htc spash screen for like an hour. I did not use a data file, is this normal?
Using froyo hd v4.6 btw
I've seen a number of requests for this functionality and recently it became necessary for one user who had a disabled Home Key to clear cache and data without the use of ClockworkMod. I have reserached two methods to address this issue. These instructions require some familiarity of android, computer and tablet terminology and usage. Feel free to ask for clarifications in comments. Here we go...
Method I - Stock Recovery Command File
Technical: Stock Recovery command file can be used to perform a few additional functions as well as to alter the path to update files. These commands will execute with all privileges available to recovery mode.
Advantages: Very easy to use. Very little technical knowledge required. No third party software is required for use.
Prerequisites: You will need a MicroSD card formatted FAT32 and a method for transferring files from your computer to the MicroSD.
Usage:
1) Prepare a text file named "command" (no file extension) with one of the following commands on a single line. The wipe data command will wipe both data and cache. Wipe cache will wipe cache only.
--wipe_data
--wipe_cache
2) Place the file in a folder named "recovery" in the root directory of your MicroSD card.
3) From a powered down state, insert the MicroSD card into your tablet and boot into recovery by powering it on while holding down the Volume Up key.
4) Allow the command to execute completely then the tablet should reboot (this may not occur automatically depending on firmware installed).
Method II - Updater Script
Technical: The attached "Updater Scripts" perform delete commands (recursively if necessary) on the named directory or file(s). The directories are mounted automatically by the system before the script executes but it could be easily revised to include that step if necessary. The partitioning, formatting and directory structure are left untouched. Only files are deleted.
Advantages: No third party software is necessary for execution. Relatively easy to modify for more surgical precision (i.e. leaving installed apps but clearing possibly corrupted system data). Included example: "Clear Battery Stats"
Prerequisites: You will need a MicroSD card formatted FAT32 and a method for transferring files from your computer to the MicroSD.
Usage:
1) Download the attached archive (ClearData.zip) to your computer.
2) Extract the files to your computer. You should then have a folder named "recovery" (which contains a file named "command") and an additional archive named "update.zip"
3) Place the recovery folder and the update.zip in the root directory of the MicroSD card.
4) From a powered down state, insert the MicroSD card into your tablet and boot into recovery by powering it on while holding down the Volume Up key.
5) Allow the script to execute completely then reboot the tablet (this may occur automatically depending on firmware installed).
This will become handy someday.
Thanks for sharing your knowledge.
You're welcome. One quick note... the new stock recovery adds a menu simiilar to ClockworkMod. These methods will still work since the recovery folder/command file are checked first but it really isn't as necessary any more.
Need Help
Tried both methods above but either way I get to the viewsonic splash with the message "Booting recovery kernel image" in the upper left and it just stays there, stuck there, I left it for a long time to see and it never leaves that screen.
Any ideas?
Me too
I can't get into clockworkmod either. My machine is running faster. I almost hate to mess it more.
lrgche said:
Tried both methods above but either way I get to the viewsonic splash with the message "Booting recovery kernel image" in the upper left and it just stays there, stuck there, I left it for a long time to see and it never leaves that screen.
Any ideas?
Click to expand...
Click to collapse
That's an indication that you may have more serious problems. nvflash will be required. http://forum.xda-developers.com/showthread.php?t=861950
Once done you will likely need to install ClockworkMod and repartition your internal storage.
Loukoebel said:
I can't get into clockworkmod either. My machine is running faster. I almost hate to mess it more.
Click to expand...
Click to collapse
If your tablet boots properly but you can't get into CWM then it probably isn't installed properly (or at all). http://forum.xda-developers.com/showthread.php?t=865245
Keep in mind that CWM is NOT compatible with all ROMs. Make sure the developer for your chosen ROM recommends it before installing it.
Does your method in opening post have to be run from external micro sdcard?
Both methods are performed with an external MicroSD card. They will work from internal also but it is a little more difficult to get the files in place if your tablet is not booting properly.
K J Rad said:
Both methods are performed with an external MicroSD card. They will work from internal also but it is a little more difficult to get the files in place if your tablet is not booting properly.
Click to expand...
Click to collapse
so your method is a simple way to replace one of the main uses of Clockword MOD?--Plus you stay stock more or less.
That is correct. Method II can also be modified to be less intrusive (leave user apps installed) or embedded into update scripts to perform a wipe during new ROM installs.
K J Rad said:
That is correct. Method II can also be modified to be less intrusive (leave user apps installed) or embedded into update scripts to perform a wipe during new ROM installs.
Click to expand...
Click to collapse
Wipe data does what--remove the apps installed?
And the partitions?
Your post is very interesting. It implies that you have a knowledge of the g-tabs partition structure. I have played with Linux off and on for the last 10+ years. When I began, I used Slackware and when you set it up you had to manually create partition tables using fdisk. You were only required to create two - the data partition and a swap partition but it was often recommended that you create several others - one to contain the home directory to prevent users from using all the disk space (in the days of small disks) for example. It appears that there are a lot of partition on the g-tab. Up to now, I have used various wiping tools like clockwork or calkulins wipe all on faith. I would really like to know what all the partitions are and what is in them. I have used terminal to get to the root folder and tried to do an fdisk to display the partitions but try as I might everything remains hidden. It would seem that a script like yours could be adapted to do many things but I would certainly want to understand the structure a little better before I did anything. I have searched and been unable to find that information. Can you point a way for the curious to learn more about the partition structure on the g-tab?
Wish I had a direction I could point you in. What I've found so far has mostly been stumbled upon while looking for something else. What I can tell you is this...
1) When using fdisk in Android you must specify the device to look at. Try something like: fdisk /dev/block/mccblk3 That should list the current partitions as defined by CWM or whatever was used originally.
2) Within one of those partitions in the list generated above are sub-partitions holding the bootloader, system, data, etc partitions. You can see how they're described in the .cfg files in the nvflash restores that are lying about.
lsu205 said:
Wipe data does what--remove the apps installed?
Click to expand...
Click to collapse
Removes user apps and their associated data as well as system related data and settings.
K J Rad - any idea if the partition size can be set with these methods (2048 & 0) in case I can't get clockwork installed?
CodeNamePapa said:
K J Rad - any idea if the partition size can be set with these methods (2048 & 0) in case I can't get clockwork installed?
Click to expand...
Click to collapse
I'm looking for a solution to that problem. Unfortunately these methods still require the ability to get into recovery mode which likely won't work if you're having trouble getting CWM installed.
If, however, you can get into recovery... then it is theoretically possible to create a script that would accomplish that. As soon as I have one I'll be adding it to the mix ;-)
Edit: I've found something I think will work. Will do some testing tonight. It will still require access to recovery.
I wasn't sure if you saw my other post but I am seeing no partition 0 when I NVFlash with a verifypartition.
http://forum.xda-developers.com/showpost.php?p=13059520&postcount=57
I haven't yet but I will. Let's try to keep this thread on topic. Thanks.
More thoughts:
because I went w/ cyan7 is it possible i have a "bad" kernel and that the stock bekit-1105 or the roebeet-3588 files are crashing w/ the kernel in place already?
I know custom ROMs can have a custom kernel applied separately, but I have no idea whether cyan7 loads it's own kernel...
I have yet to try the nvflash_gtablet_46 version, as I see the img files w/in are different from the original 1105 .zip
Also:
read on another thread that part 2 and part 3 aren't loading for other users when doing nvflash - I did notice that it pauses, runs some stuff, then starts loading part 4 through to the last part, then success. - do part 2 and 3 run for you?
edit: I see a 4349 downgrade.zip in another thread for those who got the OTA update but want to go back to stock 3588 prior to jumping off somewhere else - I can't expect that would help me as I can't do squat w/ recovery yet, but could that possibly "reset" any bad kernel problems? - again, I'm just thinking out loud.
This is well outside the scope of this thread but I find some of what you mention interesting so I'll address it and then end any further off topic discussions.
I did not build nor have I ever used Cyan7 so I have no basis for an opinion on the matter other than this... Each ROM comes with a kernel installed so if properly done an nvflash should overwrite any "bad" kernel.
Part2 and Part3 do indeed load, they are just displayed differently than the other Parts. Just minutes ago I flashed down from Mountain Laurel (4349 based with the new bootloader and recovery) with absolutely no trouble. I can, and have, read back those partitions after an nvflash to prove that point.
The 4349 downgrade will only work for you if recovery is working. Having never used it I don't know that it would "reset" the kernel but any subsequent flashing of a new ROM image would.
I am working on a stock recovery solution for partitioning but it isn't likely to help anyone who is stuck in an APX loop. I do have some ideas on what might help for that condition but I haven't been able to get my hands on one for testing and trying to help people here is like being a consulting mechanic for a car repair that's in someone else's shop having work done on it that you're not being told about.
I'll be happy to address any further comments or questions regarding your specific issue in an appropriate thread or via PM. Thanks.
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