Database Info

Simple guide to flash android on Nand

12/08/2010 Updated with fix permission
TO ALL PEOPLE:
PLEASE STOP POSTING IN THIS TOPIC ABOUT "THIS PART DOESN'T WORK ECC ECC" WRITE IN THE TOPIC OF THE RELEASE (KERNEL OR SYSTEM), PLEASE LOOK IN THIS THREAD FOR WORKING SETUPS AND TRICKS, AND SEARCH ON THE FORUM BEFORE POSTING!
This method erase all data on your system and you can brick you phone so do it carefully.
Main problem: screen
For polaris there are 3 type of screen. Usually pola100 (the old one) use panel 1, and pola 200 (09 edition) has panel 3 but ... not always works...
The best mode to test is try to install and after double reboot you have black screen change panel type.
What you need:
phone (with hardspl installed)
sd card (1 Gb or more)
time
python
Update guide: http://sourceforge.net/apps/trac/androidhtc/wiki/HowToInstallWithAtoolsNand
important said:
if you have black screen:
reset the device and edit the pannel (E)
with onother type (1,2,3) and retry.
Click to expand...
Click to collapse
For androidinstall.tar e nbh look in this thread for working setups. (Choose Eclair or Froyo, Donut as problems with new kernel)
You can flash back windows (using your preferred method), if you need, but it's a shame!

Reserved by me

good
nice going l1q1d.
Make this also sticky.
can you add how to change panel 1 to 3 or vice versa?
There are som nbh file that only come out as panel 3

can you add how to change panel 1 to 3 or vice versa?
There are som nbh file that only come out as panel 3
Click to expand...
Click to collapse
You just Download NBH Editor and select the NBH with panel 3.
Then you will see that you can choose from whatever panel you would like, save and copy on SD

sorry for my english.
good guide.
I installed everything ok android
now if I wanted to update the radio?
ho installato android tutto ok
ora se volessi aggiornare la RADIO ?

Download radio update.
rename it to POLAIMG.nbh and put in sd
start with camera button pressed
push power button when asked
restart
you have successfully update the radio

ok. perfect.
tanks : )

HTC Polaris 100 - doesn't flash
I followed you instructions exactly as you wrote them. BUt it doesn't work.
When I power on the device with camera button pressed I see the 3 color boot screen- but that is it. At this point the screen says "Loading" and nothing else happens.
What am I doing wrong?
I have been using the Haret version of Froyo and think it is great, but wanted to go the NAND route. I am hoping it will perform better.
Thanks for your help

Re-download the nbh and retry, maybe is corrupted..

A little help
Hi,
It's been a while since i posted but I'm trying to flash to the NAND but must be a little out of touch as I get blocked at an Error
on the micro SD card I put
\POLAIMG.NBH (renamed from POLAIMG-PANEL1-320-FROYO.NBH
in the \andboot
install-seq.sh
androidinstall.tar (which is not easy to find but I managed
I followed your guide http://forum.xda-developers.com/showthread.php?t=725604
but the bootlog.txt stops at these errors;
...
....
Script finished
sh: 0: unknown operand
mount: mounting /dev/block/mtdblock2 on /system failed: Invalid argument
mount: mounting /dev/block/mtdblock3 on /data failed: Invalid argument
mount: mounting /data/tmpcache on /cache failed: Invalid argument
mount: mounting /data/shared_prefs on /shared_prefs failed: Invalid argument
mount: mounting /data/tmpcache on /tmp failed: Invalid argument
mount: mounting /data/sysfiles/su on /system/bin/su failed: No such file or directory
mount: mounting /data/sysfiles/su on /system/xbin/su failed: No such file or directory
mount: mounting /data/sysfiles/su on /bin/su failed: Invalid argument
mount: mounting /data/sysfiles on /system/etc/ppp failed: No such file or directory
mount: mounting /data/sysfiles on /smodem failed: Invalid argument
I am doing something wrong ???
Thanks for any help
Richard

It's very strange, try another time..
(remember that install-seq disable automatically if install procedure works without problems)
there only these errors? are there any "Failed to format"?

Indeed the install-seq did get renamed ti install-seq-disable and the data.img & system.img was on the sd card....
Tried three times already...humpf..
Maybe I'll try a manual install.
I can post the dmesg if you think it helps??

If you use nand install you don't need anymore data.img and system.img ...
the install-seq install all on nand.
Post your dmesg (with a link) and i'll take a look...

Hi, at first I want to thank you for this tut and all your work It walked me through the proces of getting android on my pola100.
Just wanted to ask what I can delete from my sd card after succesful flashing. Can I delete complete folder andboot? Thx for your help

All the files, but it would be a better choice to keep all file on sd...

l1q1d said:
If you use nand install you don't need anymore data.img and system.img ...
the install-seq install all on nand.
Post your dmesg (with a link) and i'll take a look...
Click to expand...
Click to collapse
When I used your install script for the first time it tries to install system.img and data.img on the EXT2 partition.
After restart I entered the menu and selected the NAND option.
When I re-install the nbh and using your install script (for the second time) it is working.

I have the same problem as zeeos, I have "loading..." on my screen but nothing happens. I tryed many nbh...

Try to change sd card or flash from windows application...

Hey guys,
I've followed the guide exactly, performed task 29 first and ran from a clean, formatted SD card.
I'm using the latest Froyo build and have changed it to panel 1 as I have a POLA100.
The install procedure runs smoothly until it it gets to the point where I see the Warm Donut boot screen with animation, but then it stops and just shows a black screen with white cursor in the top left hand corner, doesn't go any further. Is this normal? Do I have to wait longer? I've left it for half an hour...?

Which files did you use?

[Q] difficulty reinstalling ROM

I've got a Galaxy SGH-1897 "captivate".
I've been running various kernels and ROMs for quite a while now. I'm handy with linux and adb and I can flash things with heimdall.
Whelp, I saw that CM7.1 finally had a version for my captivate, so I installed it last night with Clockwork mod recovery. All went well with the install, but the system seemed buggy, or at least I was having some problems. One was that I couldn't seem to get all my user data restored through Titanium backup like I've been able to after other installs. So, having fun and walking along, I thought, oh, well what I want to do is restore back to 2.2 and my old rom (which was "Torch 2.1 or something"). Anyway, I booted into recovery then told CWM to restore. It errored out and tried to reboot, but couldn't get past the startup screen.
So, I used the volume-up-down plug-in-usb trick to get back into download mode. Then I used heimdall to flash the overstock kernel and CWM (http://cmw.22aaf3.com/aries/sgh-i896/root/) all went well. Now, I have the issue that I can't seem to go ahead and reinstall a new (or old) ROM. If I try to do a "restore", I get the error that I can't mount /system, installation aborts. The error says "file already exists", so I'm trying to figure a way to unmount /system before trying it, but so far no luck (maybe I can flash busybox and get su and get the job done). Alternatively, I've been trying to flash CM7 again, but that installation errors out with "Status 7", and seems to be failing some assert statement.
I'd love any advice. Let me know if you need more detail or if this is in the wrong forum.
---------- Post added at 03:48 PM ---------- Previous post was at 03:19 PM ----------
Just following up with more info here.
It seems like "Status 7" happens when the software one is trying to install is intended for some other hardware. I'm trying to verify this now.
Looking at the output of my error, all of the asserts seem true. getprop("ro.product.device") == "captivate" ...
getprop keeps wanting "captivate" or "captivatemtd" or "SGH-I896" or "SGH-I897" it seems. And that's no surprise, I'm using a captivate. I'm not sure what the "mtd" part is about yet. And I'm pretty sure my device is an I897.
Now I'm trying to isolate which statements are causing assert to fail. I'm using grep and find on the update-cm-7.1.0-RC1-Captivate.signed.zip archive to try to locate some clues. Any ideas?
---------- Post added at 04:30 PM ---------- Previous post was at 03:48 PM ----------
Okay, now I'm thinking that I'm simply barking up the wrong tree with the assert statements and the Status 7 error. From what I can tell, I'm trying to install captivate software on a captivate, so maybe this error message is spurious. Especially considering the fact that other tasks such as "restore" also seem to be failing, but with a more general sort of error.
When I use clockworkmod recovery to go to "recover" then I select my latest backup point, I get to wait abit during md5 checks then:
Code:
E:Can't mount /dev/block/st19 to /system with parameters auto llw,check=no
(File exists)
Error mounting /system/!
Skipping format ...
E:Can't mount /dev/block/st19 to system with parameters auto llw,check=no
(File exists)
Can't mount /system/!
So, 'file exists' seems to mean that the /system directory is mounted when it shouldn't already be, or else the install script should unmount it before it starts but has failed there. In either case, maybe this is a permissions issue. Does the recovery OS need privileges it doesn't have? Is there some way to flash busybox/su using heimdall or adb? Does that seem like my problem?

not permissions, still no progress
Maybe I'm posting in the wrong forum ... ?
Let me know if there's some other group (irc?) which might have ideas?
So, it seems that the problem isn't permissions. At least insofar as I found in the ClockworkMod Recovery settings a selection to install su. So, that seemed to go fine, but afterwards I'm still getting "cannot mount /system/!" when I try to do a restore.
Still stumped. Looking for ideas.

Same error on SGSI
I've got the same error on my Samsung Galaxy S.
But I can't even boot the device, it freezes on the first boot screen, I've installed the cyanogenmod but, when I've tried to install the MIUI this problem appears and know, I can't do nothing.
When I try to install the cyanogenmod or the MIUI I get the following error:
assert(getprop("ro.product.device") == "galaxysb" || getprop("ro.build.product") == "galaxysb" || getprop("ro.product.board") == "galaxysb" ||
getprop("ro.product.device") == "galaxysbmtd" || getprop("ro.build.product") == "galaxysbmtd" || getprop("ro.product.board") == "galaxysbmtd" ||
getprop("ro.product.device") == "GT-I9000B" || getprop("ro.build.product") == "R8GT-I9000B00at" || getprop("ro.product.board") == "GT-I9000B"
Click to expand...
Click to collapse
If I enable the signature verification I get this error:
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
Click to expand...
Click to collapse
Did you fix your problem?
Someone else have any clue?
Thanks.

I've solved this problem I just changed a file updater-script located at /META-INF/com/google/android/ of the cyanogenmod zip file.
I've simple delete the lines that make a reference to my device.

tic-tac-toe said:
I've solved this problem I just changed a file updater-script located at /META-INF/com/google/android/ of the cyanogenmod zip file.
I've simple delete the lines that make a reference to my device.
Click to expand...
Click to collapse
how did u do that? did you just access the ROM zip file and edited it from there

[Q] Red Triangle and no root

Hi all
Have a problem with a boot loop.
First, my story:
I rooted the tablet and installed Rouge recovery using the "one click root" from here: http://forum.xda-developers.com/showthread.php?t=1689193
That worked and I installed CM9
What I didn't do was to make a back-up before I had installed CM9.
I want to give the tablet away to a young relative and install the original firmware on it and removing root.
I downloaded from ASUS the WW_epad-user-9.2.1.27.zip file which was the latest firmware for the device.
When I went to flash it however I got the following error
assert failed: write_raw_image("/tmp/blob", "staging")
E:Error in /sdcard/US_epad-user-9.2.1.11.zip
(status 7)
Installation aborted.
So I did the following fix found here (http://forum.xda-developers.com/showthread.php?t=1576937)
- download the img file
- rename it as blob file with a more simple name for example cwm_touch.blob
- open Terminal Emulator on your tablet, then:
$ su
# dd if=/"path to blobfile" of=/dev/block/mmcblk0p4 (REPLACE "path to blobfile" with the path to where you have saved the file).
Now here's the problem, I restarted the device and it goes into a boot loop, trying to access the recovery (Power + Volume) It goes to an android with a red triangle and nothing else. So I'm stuck, I can't recover and I can't access the device on my computer.
What do I do?

Wedge85 said:
Hi all
Have a problem with a boot loop.
First, my story:
I rooted the tablet and installed Rouge recovery using the "one click root" from here: http://forum.xda-developers.com/showthread.php?t=1689193
That worked and I installed CM9
What I didn't do was to make a back-up before I had installed CM9.
I want to give the tablet away to a young relative and install the original firmware on it and removing root.
I downloaded from ASUS the WW_epad-user-9.2.1.27.zip file which was the latest firmware for the device.
When I went to flash it however I got the following error
assert failed: write_raw_image("/tmp/blob", "staging")
E:Error in /sdcard/US_epad-user-9.2.1.11.zip
(status 7)
Installation aborted.
So I did the following fix found here (http://forum.xda-developers.com/showthread.php?t=1576937)
- download the img file
- rename it as blob file with a more simple name for example cwm_touch.blob
- open Terminal Emulator on your tablet, then:
$ su
# dd if=/"path to blobfile" of=/dev/block/mmcblk0p4 (REPLACE "path to blobfile" with the path to where you have saved the file).
Now here's the problem, I restarted the device and it goes into a boot loop, trying to access the recovery (Power + Volume) It goes to an android with a red triangle and nothing else. So I'm stuck, I can't recover and I can't access the device on my computer.
What do I do?
Click to expand...
Click to collapse
EDIT:
Well after banging my head on a wall for a few hours, I found a solution.
http://www.transformerforums.com/fo...t/31927-frederuco-s-guide-root-rom-tf101.html
This has allowed me to get back a recovery and I have installed CM9 back again.
I'm still stumped as to how to return the device back to stock..

Wedge85 said:
EDIT:
Well after banging my head on a wall for a few hours, I found a solution.
http://www.transformerforums.com/fo...t/31927-frederuco-s-guide-root-rom-tf101.html
This has allowed me to get back a recovery and I have installed CM9 back again.
I'm still stumped as to how to return the device back to stock..
Click to expand...
Click to collapse
Why not just put ARHD on it and remove/uninstall super user app...... will work a fair bit better but still have all the stock Asus bits. There wont (i suspect) be any more updates for our TF so ARHD would be just the ticket imo.

[Q] Sideloading stock ROM problems on ClockworkMod Recovery

Howdy -- I was given a SGH-I747 formerly on AT&T. This was a hand-me-down from a coworker that doesn't know what the prior owner actually did to the thing.
It appears that the phone boot-loops for a bit until it lands in into ClockworkMod Recovery v6.0.4.7. The CyanogenMod logo appears at initial boot.
This recovery tool seems to have no external microSD card access. I already have ADB on my Win7 machine and was able to install a driver for the S3 to allow me to sideload via command prompt.
I attempted to do this with a copy of the stock ROM without root access.
Initially I was forced to update a line on the script to bypass the invalid number of arguments roadblock, but later encountered this:
Code:
Finding update package...
Opening update package...
Installing update...
set_perm: some changes failed
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
I presume something has changed on the primary partition that it wasn't expecting, but I haven't the slightest idea where to go from here.
Thanks for the brainpower

Moderator Edit: Thread Closed at request of OP.

Please help... Acer e700 bootloop after official update!

Hello,
I was trying to update my phone(from settings>about phone) and I had no idea that I should not have done that because my phone is rooted; the downloaded update size was small around 12 megabytes as I remember and after restarting it got stuck into android system recovery <3e> (CWM), gave me that error "Installation aborted" and I can't boot into my system again. Unfortunately I haven't backed up my data and when I try to back them up using CWM it gives me this error "Write error, short write!" I tried recovering the backup file later from SD card on PC, it was damaged but I found out that it always crashes at 4 GB file size; I am using a 32 GB memory card and the size of data to be backed up is around 8 GB.
My questions are: Is there any other way to backup my files and applications data before attempting any repair methods?(My main concern) ;even if it was a physical way...
What should I do next?
This is what I have tried so far (without any luck),
- Wipe cache partition
- I tried installing Aroma file manager in CWM mode from SD card but it always gives me the error "Installation aborted".
- Connecting my phone to PC and choosing apply an update from ADB in CWM (The only way my PC can read my phone). I tried then pull, usb and reboot commands but it always gives me a message saying "error: closed". The only command that works is "adb sideload update.zip(Aroma also)" which gives me "Installation aborted" on the phone.
My mobile version is Acer_AV0K0_E39_1.024.00_EMEA_GEN2 (3 sims version)
=These lines are from the end of the log file for the first time the phone bootlooped trying to install the official update
(Unpacking new recovery...ApplyParsedPerms: chown of /system/bin/su to 0 failed: Operation not permitted
ApplyParsedPerms: chgrp of /system/bin/su to 0 failed: Operation not permitted
ApplyParsedPerms: chmod of /system/bin/su to 420 failed: Operation not permitted
ApplyParsedPerms: lsetfilecon of /system/bin/su to ubject_r:system_file:s0 failed: Operation not permitted
ApplyParsedPerms: removexattr of /system/bin/su to 0 failed: Operation not permitted
script aborted: set_metadata_recursive: some changes failed
Symlinks and permissions...
set_metadata_recursive: some changes failed
E:Error in /cache/alu/update.zip
(Status 7)
Update.zip is not correct
Installation aborted.
write result : MOTA_RESULT_FILE
write result : remove_mota_file
write result : remove_mota_file(DEFAULT_MOTA_FILE)
fw_upgrade: status = 1
fw_upgrade: fw
fw_upgrade_result_fw: dir does not exist, create it.
fw_upgrade_finish)
I hope that there is someone here who can find a solution to my problem. Thank you for your time.

Hello again,
I am about to try something but I am afraid it might crash my phone even more, so I would love to hear an expert opinion first;
I downloaded the same stock rom as the one in my phone from here (vache-android .com /hubicAcer/E700/OS%20Images/EMEA_GEN2/update_Acer_AV0K0_E39_1.024.00_EMEA_GEN2-sds.zip) and then I am planning to flash using the method in this video to preserve my data (youtube .com/watch?v=b5H6EbaCKrw),and then if this method works and the system booted I am planning to back up my data and applications using titanium back and then do a clean install.
Do you think this might work? If not, What other methods can I try to backup my data?