Hi,
I had a look over the recovery code in the official android source, and in the cyanogen sources. And one point remains obscure to me.
It seems that in both cases, the flashing program verifies the signature of the zip archive using a public key located in /res/keys.
I use cyanogenmod and it turns out that when I reboot in recovery mode and open a console, there is no /res/keys file.
Can someone explain me where is the trick here ?
One more question. I guess that if there is a public key in the device, there must be a private key used to sign the archives. (Probably kept secret by the carriers to sign their own updates). But I read somewhere that there is some apps available to sign theses updates (something called SignAPK or so). So I guess that either the private key has leaked from the carriers, or that something in the rooting process of the G1 changed the key pair on my device.
Can someone give me more details ?
Thx
Julian
I can't answer your first part, but rooted phones use the ADP1 test keys to sign packages.
Usually the AOSP keys are used to sign zips, if you need instructions, they are here:
http://forum.xda-developers.com/showthread.php?t=471586&highlight=sign
Thank you for your answers, but it seems that I don't need any custom scripts to sign the update.zip, since there is already everything needed inside the android source tree (build/tools/releasetools).
The test-keys are located under build/target/product/security/.
But that doesn't explain why I can't see the /res/keys file when in recovery mode.
Julian
Newer version of recovery(eclair) reads the public keys from /res/keys, but with cupcake, public keys included in the source file, see install.c and keys.inc for more detail.
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!
I start with thread with a information for all users:
Haret system sucks so if you want a full working android system left windows behind you and move to the new android world flash on nand.
With this how-to you will not erase any part of your system but you do at your own risk.
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
sd card (1 Gb or more) 500 mb free
time
Update guide: http://sourceforge.net/apps/trac/androidhtc/wiki/HowToInstallWithAtoolsHaret
reserved by me
Do we have to delete/remove the install-seq.sh after installation?
Are both files (system & data) cleared with the installation script?
Thanks for the help.
install-seq.sh disable automatically after correct install.
This how-to is fir first install on disk on images so it format both data an system.
If you want to make only un update use bsg select partion and select update.
partition
I believe you should make this sticky
Don't post without reading!!!!
This method doesn't use sd partition, it create two imagedisk on sd!
working android
l1q1d said:
Don't post without reading!!!!
This method doesn't use sd partition, it create two imagedisk on sd!
Click to expand...
Click to collapse
hi there,
i made all you told here, booting..after more minutes...the logo appears...but when i press the android logo from the screen.. the touch screen dosent work..i can not start..only with buttons..and after pressing buttons..get over wizard..the phone need SIM PIN..but i can not typed.
please help
i changed BORAD PANEL in 1,2,3 and in 2,3 is black screen.
please help me
You have to disable pin code before installing.
For the screen problem look in kernel thread...
waiting for not busy
What about "waiting for not busy" - im2c error ?
The only Zimage working for my pola100 it's an old 29-04-10 Version !
I am very disperate!
Bye !
touch screen dosent work
foxct2005 said:
What about "waiting for not busy" - im2c error ?
The only Zimage working for my pola100 it's an old 29-04-10 Version !
I am very disperate!
Bye !
Click to expand...
Click to collapse
Dear All,
i tried and deactivate the PIN of sim card..read all posts from previous thread that you gave me..but nothing..
all ok..
bootin..starting..apears the logo and final...
before i need to press the screen, appears a message ''Android system stop responding..and a button FINISH"...after pressing finish, i need to press the middle of the screen on the android logo and nothing, only 2 buttons Emergency Call and Choose Language. to can press these 2 buttons, i use the buttons and i can press them..but touch screen do not working.
please all of you..the masters of this softwares..give me a solution.
thx
Try to reinstall the system...
(rename /andboot/install-seq-disabled.sh to /andboot/install-seq.sh and boot)
touch screen problem
l1q1d said:
Try to reinstall the system...
(rename /andboot/install-seq-disabled.sh to /andboot/install-seq.sh and boot)
Click to expand...
Click to collapse
hi there..
i solved the problem..i took an older Z image..and working fine
the problem is that more applications like camera..media player screen adjust don't work..
they try to run..(i mean ..in camera..i can see..but appears a messages with stop working..sorry). i don't know why..
nothing work well
and what about the contacts..how can i get them from my Sim card?
i don't know..
if you can help me will be great.
thx allot for yours assistance.
best regards.
The information from sim card are very limitated (neither pin code works) so if you want to export contact sync before starting with google and configur your google account on android.
old zimage are full of bugs and all developers install android on nand so starting android from haret has many unfixed bugs.
I've been playing around with the haret install for a week or so now, and I've found that, for me at least, it makes a huge difference which initrd.gz file I use.
The one dated 22-05-10 doesn't let me install any zImages newer than 29-04-10. After trying all sorts of combinations of base files with different dates (haret, zImage) and additions to the default.txt, changing the initrd.gz file to the one dated 20-02-10 fixed most of my problems and lets me install the most recent zImage files without a glitch.
No clue why, just that it works.
I'm running a Pola100 with the original WM6.0 ROM still on it, and radio version 1.58.25.14. Yeah, I need to upgrade to at least the official WM6.1 ROM and probably something better. But I'm a newbie at this, so I need to work up some courage first ;-)
hello,
I tried to install android on sd following your instructions, everything seems to go well until the screen where it says:
"Welcome to htc vogue Frøya
touch the android to begin "
I'll try, but the touch does not work, I tried using the d-pad, which does work, but I can only select the language and the emergency call.
zImage as I used: zImage-Frøya-15-07-10
androidinstall.tar as I used: Incubus26Jc's Super Frøya RLS11 Themed
please help me because I would switch to Android!
thanks
Try with latest kernel version on kernel (i release it yesterday)
l1q1d said:
Try with latest kernel versin on kernel (i release it yesterday)
Click to expand...
Click to collapse
where can I find it?
thanks
I tried it unsuccessfully. Boot starts regulary, always ending on repeating error, looping forever.
I can read something like:
==============
ERROR no local apt for prog ... replying anyway
...
Setting function 4 for gpio ... that I don't own
==============
Is it related to which system file ? Loader? Kernel ? Or what ?
Thanks
What did you use for your installation?
I used the files mentioned at the very beginning of this post.
Regarding zimage: zimage-24-05-10
EXPERTS ONLY!!! USE WITH CAUTION I DO NOT ACCEPT ANY RESPONSIBILITY FOR BRICKS.
I have written a tool to create blobs which can be used to flash boot/recovery images on the Transformer.
All information can be found on
http://www.opencodes.org/node/16
Let me know if you had success or problems/errors. But please do bear in mind that messing up boot or recovery and generally flashing blobs can brick your device and I cannot accept any responsibility for that!
Thanks so much for doing this, since the current effort I'm aware of to do the same thing wasn't very forthcoming on details.
Would you mind detailing what you found out in the reverse engineering? I was planning to start working on this also.
Edit: Well, since it is a script, I guess I can wait till I get home from work for details.
rothnic said:
Would you mind detailing what you found out in the reverse engineering? I was planning to start working on this also.
Click to expand...
Click to collapse
The basic idea is very simple. There is a header that is in the file (the header I have in the script is slightly longer since it e.g. contains a value which tells the bootloader that there is just one partition in the blob. That value is technically variable, but I didn't need that feature).
The crucial line is then
head="$header $partaddr $filepos $length 01 00 00 00"
whcih tells you exactly what the file looks like before the partition contents are pasted in.
$partaddr is the internal partition address of the Eee Pad, so is different depending on whether we flash boot or recovery. And those are the same in the two released Eee Pad versions (WW/US) [I did check that in the ASUS Firmware releases]. You can see in the script what they are.
$filepos is the hex address of the partition start in the blob. Again that is constant in my script as we only have one partition - it can very easily be adapted to accept multiple partitions, though I couldn't see when I would need that.
$length is the size of the partition in hex.
One thing to note is that each 4-byte hex value is reversed in the file (as in the bytes are reversed), ie the address 0x4C is actually 0x0000004C . That applies to all the values above.
I'm not entirely sure what the value '01 00 00 00' (which actually is just 0x1) represents but it is constant in all blobs for all partitions. It could be that that value is an override flag if one wanted to ignore a partition or similar, but I haven't tested that.
Edit: Well, since it is a script, I guess I can wait till I get home from work for details.
Click to expand...
Click to collapse
Yes, exactly. It's all open for people to look at.
Generally I believe that we all should collaborate and release our work as soon as we can (with appropriate cautions to avoid n00b-bricks!), to allow further progress by others. I really dislike the closed-clique nature some devs are adopting just to get the credit for something. All of this rooting is not *such* a big deal, especially since we all rely on work done by others in our efforts. So here's to open hacking
Just purchased credits to unlock my bootloader through WotanServer. I got directed to the tutorial page where I download the client and a driver, but upon running the client it stops working immediately. Just "WotanClient has stopped working" and forces me to close down. I've tried running it in different compatibility modes but to no avail. It creates a folder called 'data' and two empty subfolders 'flashes' and 'scripts' and a text log.
I know WotanServer seems legitimate, but I can't help but feel a bit cheated. I'm guessing there's something wrong with the current version and I was wondering if anyone had a link for an older version maybe? As that could possibly work. I've tried googling this but again, to no avail. I've emailed them but I thought I might get a quicker response here.
The text log contains the following:
WotanClient 3.12.0 - wotanserver link omitted [3012000]
Microsoft (build 9200), 64-bit ENG (ENG)
[APPSTART] checking version for WotanClient.exe...
Click to expand...
Click to collapse
And that's it! Thanks in advance if anyone can help me out. Sorry for any misuse of terms, it's my first time trying to install custom ROMs on my phone and this is the only get around for my carrier locked/fastboot locked Xperia Play.
Hello.
Did you ever find an answer to this? I'm having the same issue.
Thanks.
Well I found it and ran it (w/o buying it) and here's what I found...
1) You can download data3.zip from http://storage.wotanserver.com/version/data3.zip and put in the data folder
:::::::: Problem :: it crashed instantly...
2) GUESS < Add http://storage.wotanserver.com as 127.0.0.1 in C:\Windows\system32\drivers\etc\host
:::::::: Since this is a guess, it's possible it might work... However I recomend downloading the file then blocking the site.
:::::::::::: Since the site will be blocked; the program might think it's doing it while it's not; meaning; it should skip that part.
Hello everyone,
I have bought various Android TV boxes in the past, and haven't had problems getting them up and running.
I recently ordered 2 chinese models from eBay however, which are giving me nothing but grief. I apologize in advance for such a loooong post, but I am at my wits end and I am really hoping someone can help me out.
The action was for this model here:
www.ebay.com.au/itm/231275032090
It appeared to be a pretty standard model, like a Justop 4.0, but with a hard switch where the optical should be, and a cut down remote.
Firstly, the Specifications according to the auction:
1GB ddr3
4GB nand flash
Allwinner A20 dual core 1GHz CPU
On closer inspection after receiving the unit, an additional physical difference is that the reset button appears to be between the USB ports, instead of behind the AV out - not a big deal.
After powering it up, I am having huge problems with them.
Firstly though, what the software says about the hardware:
Advanced Settings/About Tablet:
Model Number : BBA22
Android Version : 4.2.2
Firmware Version : V2.0
Kernel Version : 3.4.39 [email protected] #10 Wed May 14 22:36:36 CST 2014
Build Number : BBA22-UI4-V2.0.1
And what Droid Info says about the (relevant)hardware:
Model : BBA22 (sdk-normal)
Manufacturer : unknown
Chipset : sun7i
RIL version : sw-dataonly-ril-0.5
Build Number : BBA22-UI4-V2.0.1
Build Bingerprint : softwinners/ninss/ninss4.2.2/NinssSoftware/20140521:eng/test-keys
OS Version : Jelly Bean MR1 (4.2.2)
SDK : 17
CPU Architecture : ARMv7 Processor rev 4 (v71)
Now, the BIGGEST issue these things have, is that at random points of use, it comes up with a message "Warning - System configuration is inconsistent with the production configuration, please contact your supplier, thank you!". This message will flash over and over again for anything from 30 seconds to half an hour. I half suspect it has tablet code SOMEwhere in it also, as it keeps coming up with 'touch the circle' walkthroughs for applications like avia. This might be unrelated though, I have no idea.
So anyway, I have tried doing the Justop 4.0 flash method with a SD card, however it will not turn on if there is a card in the slot. Also, when you hold the reset button down and power it up, it does not seem to go into the diagnostic mode so I can't flash it that way either. I am guessing the ONLY way I can update short of soldering in a serial port, is to use the backup/restore function.
I read through this whole thread here, but cound not fine anything to help me:
http://forum.xda-developers.com/showthread.php?t=2398632
If anyone has any ideas, please let me know, I seriously can't get anything to work. I thought maybe the 'hotspot' being enabled was causing the incinsistency problem, but I used a process killer to stop that at startup, still no luck. Doing a system reset through advanced config didn't help either, I got the error almost as soon as turning the unit back on.
I've attached pictures of the error I am getting, the top of the board, and the back if the board.
Cheers,
Smak
PS - I am yet to hear back from the seller, but if I ever do, I will post the result here...
Smakky said:
Advanced Settings/About Tablet:
Model Number : BBA22
Android Version : 4.2.2
Firmware Version : V2.0
Kernel Version : 3.4.39 [email protected] #10 Wed May 14 22:36:36 CST 2014
Build Number : BBA22-UI4-V2.0.1
Click to expand...
Click to collapse
I seem to be in a very similar situation. My device also reports as being "BBA22" but it's a different form factor and the identification on the board is "TXCZ_A20_v1.0". I tried contacting the people that made the board (Shenzhen Tianxing Chuangzhan Electronic Co.) but they refused to help. I also tried contacting the company that made the firmware images (Shenzhen NINSS Technology Ltd.) and they also refused. The supplier I bought the device from says they have the image file but they can't seem to figure out how to get it to me (they tried emailing the +200mb file then they gave up and stopped responding). The build number on my device is "BBA22-UI4-V2.0.4" so apparently there's an update available that may work on your device.
I'm pretty sure you need to flash the image using the Phoenixsuit program to make a special sdcard that you place in the device and boot from to reflash the device.
Please post your image file if you ever get it!
tisdall said:
I seem to be in a very similar situation. My device also reports as being "BBA22" but it's a different form factor and the identification on the board is "TXCZ_A20_v1.0". I tried contacting the people that made the board (Shenzhen Tianxing Chuangzhan Electronic Co.) but they refused to help. I also tried contacting the company that made the firmware images (Shenzhen NINSS Technology Ltd.) and they also refused. The supplier I bought the device from says they have the image file but they can't seem to figure out how to get it to me (they tried emailing the +200mb file then they gave up and stopped responding). The build number on my device is "BBA22-UI4-V2.0.4" so apparently there's an update available that may work on your device.
I'm pretty sure you need to flash the image using the Phoenixsuit program to make a special sdcard that you place in the device and boot from to reflash the device.
Please post your image file if you ever get it!
Click to expand...
Click to collapse
That is good to know, I might email them again now. Will let you know the outcome!
OK, so I got a reply from the seller.
I've attached the patch file and the instructions to this message, but theres a few things to note.
- Its only like 20 meg big, so it isnt a full firmware update
- The instructions talk about pressing the reset button at the start.., I don;t think this is neccesary if its rooted already
- The instructions are VERY engrish-y, basically just dump the update.zip onto a sd card, and apply the patch through the settings menu
- The default language is changed to some form of Chinese after applying, theres plenty pictorials on how to change the android language though.
- The version has been updated from BBA22-UI4-V2.0.1, to BBA22-UI4-V2.0.3 - This is still lower than the one you mentioned @ BBA22-UI4-V2.0.4
So far though, I have re-installed all my apps, and haven't seen the error.. yet. I was a little concerned it is still giving me touchpad tutorials, but mouse mode on the remote is making short work of those.
I'll just have to wait and see, I guess.
Smakky said:
OK, so I got a reply from the seller.
I've attached the patch file and the instructions to this message, but theres a few things to note.
- Its only like 20 meg big, so it isnt a full firmware update
- The instructions talk about pressing the reset button at the start.., I don;t think this is neccesary if its rooted already
- The instructions are VERY engrish-y, basically just dump the update.zip onto a sd card, and apply the patch through the settings menu
- The default language is changed to some form of Chinese after applying, theres plenty pictorials on how to change the android language though.
- The version has been updated from BBA22-UI4-V2.0.1, to BBA22-UI4-V2.0.3 - This is still lower than the one you mentioned @ BBA22-UI4-V2.0.4
So far though, I have re-installed all my apps, and haven't seen the error.. yet. I was a little concerned it is still giving me touchpad tutorials, but mouse mode on the remote is making short work of those.
I'll just have to wait and see, I guess.
Click to expand...
Click to collapse
That seems very promising for you! Unfortunately it probably won't help me at all... It sounds like it's a sort of update patch instead of a whole image. Starting the device with the reset button causes it to load the recovery partition instead of the regular partition (I'm guessing you saw a green android with a text menu with options for recovery). I full flashing would/could involve an SDcard, but I think you would have to create it with Phoenixsuit and not just copy the file contents over (it would then just boot directly from the SDcard and you wouldn't need to press the reset button).
In my case, both the regular boot partition and the recover partition are wrecked so I couldn't even try this patch if I wanted to.
Thanks for posting, though... Hopefully it helps someone else out.
tisdall said:
That seems very promising for you! Unfortunately it probably won't help me at all... It sounds like it's a sort of update patch instead of a whole image. Starting the device with the reset button causes it to load the recovery partition instead of the regular partition (I'm guessing you saw a green android with a text menu with options for recovery). I full flashing would/could involve an SDcard, but I think you would have to create it with Phoenixsuit and not just copy the file contents over (it would then just boot directly from the SDcard and you wouldn't need to press the reset button).
In my case, both the regular boot partition and the recover partition are wrecked so I couldn't even try this patch if I wanted to.
Thanks for posting, though... Hopefully it helps someone else out.
Click to expand...
Click to collapse
Hmm, is clockworkmod still a thing? I could try taking a backup of my ROM and see if that's something you can use.., only problem is I will need a bit of time. If I get a chance, I'll do it over the weekend. I will need a place to dump the image though, it will be too big to attach here, can sort that out later though.
Smakky said:
Hmm, is clockworkmod still a thing? I could try taking a backup of my ROM and see if that's something you can use.., only problem is I will need a bit of time. If I get a chance, I'll do it over the weekend. I will need a place to dump the image though, it will be too big to attach here, can sort that out later though.
Click to expand...
Click to collapse
I'd appreciate that... Your board seems to have a completely different layout, but all the same components. I'm not familiar with clockworkmod, though, so I'm not sure how that backup would work. I guess I'd need to get clockworkmod flashed on to the recovery partition first and then I could flash the backup to the NAND from there?
tisdall said:
I'd appreciate that... Your board seems to have a completely different layout, but all the same components. I'm not familiar with clockworkmod, though, so I'm not sure how that backup would work. I guess I'd need to get clockworkmod flashed on to the recovery partition first and then I could flash the backup to the NAND from there?
Click to expand...
Click to collapse
I'm not actually too sure. The last timed I used clockworkmod was for flashing a galaxy s2 phone, so I'm not even too sure if its still around or compatible with tv boxes. There will definately be SOME sort of tool though, that can take a full backup suitable for restoring. I'm about at the limit of my knowledge, so I am sort of playing by ear and going into a google-learn-try sort of cycle as I try different things. Maybe someone with more experience will stumble in here and let us know what we need to do
This is interesting... I found another device with an identical PCB board: YBKJ_A20 (I can't post links yet, but a Google search will find it) Several chips are different so the firmware would differ. It's so hard to work with these devices when no one claims credit for making a lot of these things!
What is J4?
http://dl-1.va.us.xda-developers.com/2/9/3/6/8/3/3/DSC_0207s.jpg
I was wondering what the upper left 2 pin connector is for? (the little white 2 pin plug next to the USB)
Is it SPDIF? Power input? output? Something else? I see in this picture a cable connected so i'm hoping you can tell.
Ask BBA22-V.1.50 TV BOX Model Android 4.2 Firmware
Smakky said:
OK, so I got a reply from the seller.
I've attached the patch file and the instructions to this message, but theres a few things to note.
- Its only like 20 meg big, so it isnt a full firmware update
- The instructions talk about pressing the reset button at the start.., I don;t think this is neccesary if its rooted already
- The instructions are VERY engrish-y, basically just dump the update.zip onto a sd card, and apply the patch through the settings menu
- The default language is changed to some form of Chinese after applying, theres plenty pictorials on how to change the android language though.
- The version has been updated from BBA22-UI4-V2.0.1, to BBA22-UI4-V2.0.3 - This is still lower than the one you mentioned @ BBA22-UI4-V2.0.4
So far though, I have re-installed all my apps, and haven't seen the error.. yet. I was a little concerned it is still giving me touchpad tutorials, but mouse mode on the remote is making short work of those.
I'll just have to wait and see, I guess.
Click to expand...
Click to collapse
Hello
Thank You For This Firmware But It Work For BBA22-UI4-V2.0.1, to BBA22-UI4-V2.0.3.
My Device Model is ((BBA22-V.1.50)) with Android 4.2 and I had to update it with your firmware file to fix problem black page after boot.
after update my device with your firmware, black page broblem is solved but device not work properly and it show Error message for (android.process.acore) systematically in loop!
also I can not make very actions because this error message show repeatedly.
also the default device language is china and i can not change language (error message show repeatedly)
have you original firmware for ((BBA22-V.1.50)) with Android 4.2 device???
thank you for help me...
H.SHAFAGHI said:
have you original firmware for ((BBA22-V.1.50)) with Android 4.2 device???
Click to expand...
Click to collapse
So... For everyone looking for a full firmware for this box, and stumbled upon this thread from google like I did: DESPAIR NO MORE.
I found a compatible firmware for this device (exacly as described and same board as the one OP has) It will work even if your box came preinstalled with another software version, but its the same hardware
Found it in another thread, posted by @daaviles30 Its not EXACLY the same as the one I had originally loaded but appears to work without any issue whatsoever (even the remote works), if a little bit better.
So here it is:
daaviles30 said:
A20_V20_SDK_EN_XBMC_0703-2.img*491.4 MB
*https:/ /mega.co.nz/#!XAIRiD5Q!aIb0tvvjvzUdaf11vIR7PAadeXPV8XizYJ9X2mAzpQI
RH46-update-a20.zip*582 KB
*https:/ /mega.co.nz/#!HZwTgQIT!LQGxb6R-lCIKe58RgIGROfufY-aq5PODSAq3-NPKOeo
PhoenixCard_V309
*http:/ /mega.co.nz/#F!HAIhBJyS!L_UQPNnYdPyHTD3ggnJ6OA
After flashing update and then go to the play store and download SuperSU update that and your ready to go.
---------- Post added at 03:57 PM ---------- Previous post was at 03:29 PM ----------
Titanium Backup Pro v6.1.5.3.apk*6.2 MB
*https:/ /mega.co.nz/#!vAAWRJga!vOFKlAq_25ssrG5kvwa3-oC-d0saL06YGBIWIyN2jss
You can delete all the unwanted system apps with this app.
Hope this helps Happy New Years.
Click to expand...
Click to collapse
The flashing process is exacly as described earlier in this thread. Use phoenix card to burn the img to an SD card, turn the device on with the card inserted in the slot and enjoy your restored android box.
It Working Only With Booting From Memory Card Slot...
amedeh123 said:
So... For everyone looking for a full firmware for this box, and stumbled upon this thread from google like I did: DESPAIR NO MORE.
I found a compatible firmware for this device (exacly as described and same board as the one OP has) It will work even if your box came preinstalled with another software version, but its the same hardware
Found it in another thread, posted by @daaviles30 Its not EXACLY the same as the one I had originally loaded but appears to work without any issue whatsoever (even the remote works), if a little bit better.
So here it is:
The flashing process is exacly as described earlier in this thread. Use phoenix card to burn the img to an SD card, turn the device on with the card inserted in the slot and enjoy your restored android box.
Click to expand...
Click to collapse
Hello My Friend And Thank You For Replay...
This Android is Working And is Very Good But i Can Not Install This To My Device. I Copy The IMG File To A External Memory Card (Using PhonixCard Application) and put the Memory Card To My Device And PowerOn My Device. My Device Automatically Boot From Memory Card And New Android is Appear. It Is Very Fast And Have No Errors.
Now...
HOW I CAN INSTALL THE IMG FILE TO MY DEVICE (INTERNAL MEMORY) AND BOOT MY DEVICE WITHOUT USING MEMORY CARD (FOR ALL TIMES)???
H.SHAFAGHI said:
Hello My Friend And Thank You For Replay...
This Android is Working And is Very Good But i Can Not Install This To My Device. I Copy The IMG File To A External Memory Card (Using PhonixCard Application) and put the Memory Card To My Device And PowerOn My Device. My Device Automatically Boot From Memory Card And New Android is Appear. It Is Very Fast And Have No Errors.
Now...
HOW I CAN INSTALL THE IMG FILE TO MY DEVICE (INTERNAL MEMORY) AND BOOT MY DEVICE WITHOUT USING MEMORY CARD (FOR ALL TIMES)???
Click to expand...
Click to collapse
Wow.
The Phoenixsuite makes an sdcard that flashes the internal memory. After it's finished flashing, you take the card out and it runs off of the internal NAND. That's it. It never runs the Android from the sdcard.
My device can boot from sd-card!!! I need to flash this to install your android!
tisdall said:
Wow.
The Phoenixsuite makes an sdcard that flashes the internal memory. After it's finished flashing, you take the card out and it runs off of the internal NAND. That's it. It never runs the Android from the sdcard.
Click to expand...
Click to collapse
Hello My Friend And Thank You For Replay...
1- My Device Can Boot From SD-CARD With A Bootable Memory Card! (Such As OpenSuse Linux)
2- I Use PhonixCard Application That You Send.
(PhoenixCard_V309
*http:/ /mega.co.nz/#F!HAIhBJyS!L_UQPNnYdPyHTD3ggnJ6OA
3- I Can Not Use PhonixSuit Application And I Don't Know How To Use PhonixSuit. When I Connect My Device To My Computer To Use PhonixSuit, My Computer Don't Find Any Hardware And Can Not Connect!
4- I Copy The IMG File To A SD-CARD (Using PhonixCard Application) and put the Memory Card To My Device And PowerOn My Device. My Device Automatically Boot From Memory Card And New Android is Appear. If Unplug The SD-CARD And Power On My Device, Old Android Is Appear!!! Master Android Software Is In My Device And I Need To Clear This From My Device And Install Your Android!
HOW I CAN INSTALL YOUR ANDROID TO MY DEVICE (INTERNAL MEMORY) AND BOOT MY DEVICE WITHOUT USING MEMORY CARD???
I need help!!!!
no any answer???