Database Info

Can't get rootacces: error opening recovery_img

Little n00b quistion,
Just made a HTCgoldcard and installed RC7.
And want to flash JFv1.3, but got this error:
Installing from sdcard
Finding update package
Opening update package
Vertifying update package
E:No signiture ( 385 files )
E:Vertifycation failed
installation abborted
What to do?

http://forum.xda-developers.com/showthread.php?t=442480
So, put the new recovery image in /system, and after that update to hard spl. After that it's easy to update to new (you can even use JF updater from the market)
You can also use this step-by-step manual:
http://www.multigesture.net/articles/t-mobile-g1-downgrade-rc30rc8-rooting-update-tutorial/
Also, don't use JF1.3, but get JF1.4x
(Hoi Marcel!)

Oke tried this :
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd sdcard
flash_image recovery recovery.img
Click to expand...
Click to collapse
But can't open recovery_img

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?

problem chown/mod flashing AOSP over HTC Desire

Hello, I have a problem when I try to flash the AOSP compiled for the HTC Desire,
I'm using the recovery ClockworkMod 2.5.0.7
and when I flash the update.zip I get the following error:
E: Can't chown/mod /system/keyspa.sh
(No such file or directory)
E:Failure at line 14:
set_perm 0 0 06755 SYSTEM:keyspa.sh
Installation aborted
somebody know what's happening?
Thanks in advance..

Check whether the below link helps u..
http://forum.xda-developers.com/showthread.php?t=530900

Hey, thanks for the response, but I already check it.
But I dont perceive any solution from there.

now the problem is the update-script / updater-script
I think the problem is the update-script. Well I try replacing the update-script by a updater-script from customized roms like Oxygen1.04 or CyanogenMod 6. But when I try to apply the update.zip I get the following error:
can't open /dev/tty0: No such file or directory
So I'm using the ClockworkMod recovery 2.5.0.7, and I don't know if that recovery can work with "updater-script" or just update-script.
Hope anybody can help me

how can I generate the update-binary for my updater-script
I figured that maybe the problem is because I dont have a udpate-binary file next to my updater-script.
someone can told how can I generate this file?
Thanks in advance..

Attempted to use Terminal Emulator "Not Found"

I have followed the instructions online precisely, I had gotten the list of apps (.apk/.odex).
However when I actually try to delete them:
rm/system/app/MediaHub.apk
I receive a line that repeats that line but with a " : not found " after the apk
What am I missing?

GreenAce92 said:
I have followed the instructions online precisely, I had gotten the list of apps (.apk/.odex).
However when I actually try to delete them:
rm/system/app/MediaHub.apk
I receive a line that repeats that line but with a " : not found " after the apk
What am I missing?
Click to expand...
Click to collapse
Are you rooted? Do you have super user access?

Yes sir I am.
In fact I have just loaded the stock samsung rom (by accident) if you'll excuse me, I need to load the rom that I wanted.
Thanks for the help.
Just a random question why do they say to use the computer when install the modded 3e recovery? It's unnecessary in fact I could figure out how to access the location of /system/bin through my pc.
Anyways wish me luck.

Also another question
I'm having troubles mounting as a read write file
I first type in su
I agree
Then I proceed to enter
mount -o remount, rw -t yaffs2 dev/block/mtdblk3 /system
that seems to go through
Usage: mount [-r] [-w] etc...
I'm trying to delete apps
rm /system/app/appname.apk or .odex
what is my deal?

Broken symlinks in the /system

Hello everybody, first time asking here.
Problem is with endless booting, sometimes it restarts back to TWRP.
After disabling MTP in TWRP and adb shell I see:
$ adb shell
linker: error reading config file "/system/etc/ld.config.txt" for "/sbin/busybox" (will use default configuration): error reading file "/system/etc/ld.config.txt": Too many symbolic links
encountered
WARNING: linker: error reading config file "/system/etc/ld.config.txt" for "/sbin/busybox" (will use default configuration): error reading file "/system/etc/ld.config.txt": Too many symbol
ic links encountered
Click to expand...
Click to collapse
So I look deeper and found
~ # ls -all /system/etc
linker: error reading config file "/system/etc/ld.config.txt" for "/sbin/busybox" (will use default configuration): error reading file "/system/etc/ld.config.txt": Too many symbolic links
encountered
WARNING: linker: error reading config file "/system/etc/ld.config.txt" for "/sbin/busybox" (will use default configuration): error reading file "/system/etc/ld.config.txt": Too many symbol
ic links encountered
lrw-r--r-- 1 root root 11 Jan 1 2009 /system/etc -> /system/etc
Click to expand...
Click to collapse
Seems that the symlink is broken and points to itself. Is it true? I found more symlinks like that:
bin -> /system/bin
product -> /system/product
system_ext -> /system/system_ext
vendor -> /system/vendor
Click to expand...
Click to collapse
so I am not sure whether this is broken system issue or something else. At least in Linux I would consider it broken but AndroidOS is not so familiar for me.
I have A3 (2016) [a3xltee] with unofficial 18.1 but the problem was also on the previous official 17.1 - I upgraded to see whether it fix the [rpbem. I did it before I found the issue with symlinks.
Any advice?
The phone itself has issues, was swimming with me in the pool, and it life is expecting to end but I would like at least to run it to sync all data and export to new phone.
BTW, those are all ld.config.txt files I found with find
~ # find . -name ld.config.txt
linker: error reading config file "/system/etc/ld.config.txt" for "/sbin/busybox" (will use default configuration): error reading file "/system/etc/ld.config.txt": Too many symbolic links
encountered
WARNING: linker: error reading config file "/system/etc/ld.config.txt" for "/sbin/busybox" (will use default configuration): error reading file "/system/etc/ld.config.txt": Too many symbol
ic links encountered
./system/system/apex/com.android.conscrypt/etc/ld.config.txt
./system/system/apex/com.android.media.swcodec/etc/ld.config.txt
./system/system/apex/com.android.art.release/etc/ld.config.txt
Click to expand...
Click to collapse

_rl said:
Hello everybody, first time asking here.
Problem is with endless booting, sometimes it restarts back to TWRP.
After disabling MTP in TWRP and adb shell I see:
So I look deeper and found
Seems that the symlink is broken and points to itself. Is it true? I found more symlinks like that:
so I am not sure whether this is broken system issue or something else. At least in Linux I would consider it broken but AndroidOS is not so familiar for me.
I have A3 (2016) [a3xltee] with unofficial 18.1 but the problem was also on the previous official 17.1 - I upgraded to see whether it fix the [rpbem. I did it before I found the issue with symlinks.
Any advice?
The phone itself has issues, was swimming with me in the pool, and it life is expecting to end but I would like at least to run it to sync all data and export to new phone.
BTW, those are all ld.config.txt files I found with find
Click to expand...
Click to collapse
If it went swimming with you, it is more likely that the hardware is damaged, not the software.

It was like two years ago. Was dried out by a technician. Was working fine since then. And all problems started yesterday. Could be that hardware was degradated over the time (corrosion)
But I was able to push the problem further.
I wiped out system and installed unofficial 18.1, now the /system is OK but still is endless booting.
Current other problem is with:
$ adb shell
error: exec '/system/bin/sh' failed: No such file or directory
Click to expand...
Click to collapse
Of course file exists. I tried to browse for similar cases ut none of the proposed solutions was working for me.