Related
From what I can tell anyway. I was working on this, and I had it working up until installing a new app from the Market. Here's the tutorial I wrote:
Code:
Note1: This process can brick your phone, and it can crash the Android OS. Please use with caution, and know that you are responsible for your own actions, not me, nor anyone else.
Note2: If the Android OS does crash (signified by the Android loading screen, with the flashing Android logo) a factory reset is your best option. It saved me a few times when working on this process.
Note3: Note that a fresh start (factory reset phone) is best for this process, as it changes where all apps are going to be stored and used from.
Note4: Your SDcard cannot be accessed when the USB cable is plugged into your computer, so note the apps will not work/will not work well if you are connected to a PC.
Get root
In terminal:
1. su
2. cd data
3. mkdir /sdcard/data/app
4. mkdir /sdcard/data/app-private
5. mv app app2 (don't want to delete the directory terminal is running from, also kept for backup)
6. mv app-private app-private2
7. ln -s /sdcard/data/app app
8. ln -s /sdcard/data/app-private app-private
And bam! Done.
I then used adb push/pull to backup the app and app-private directories to the SDcard. (just in case, for the terminal app. And I tried this process with and without this step, so I know it isn't this messing it up)
Now Terminal Emulator runs, as well as everything else, but when I download/install a new app, my phone freezes as it goes to install it, and then crashed and goes to the Android OS loading screen forever.
I also worked on this and ran into the same problems you have...I know that there are some other folders that deal with the apps we download from android market.. One of the problems you may be having is that when installing there is an intitial setting up communication that is trying to occur between the downloaded apps, /sdcard/app, and other folders on the phone. When the sdcard/app trys to communicate back with the other party, your errors occur and you crash....I would suggest doing this again, hooking your phone up to DDMS and reproducing the crash again so that you can see what is throwing the errors...that may give you a better idea of what else needs to be done....
I would love to help in any way possible as I was working on this as well, btw, when you get stuck at the flashing android, there is no need to do a reboot, you can plug your phone into your computer and run the adb shell even though it isn't booting up. Since you can run the adb shell, you can fix the problem. Also, you could run DDMS to see what is keeping it from booting as well.
Me too!
I'm working on this as well, I will relay any progress I make, hope you will do the same.
Thanks!
Phromik said:
Now Terminal Emulator runs, as well as everything else, but when I download/install a new app, my phone freezes as it goes to install it, and then crashed and goes to the Android OS loading screen forever.
Click to expand...
Click to collapse
one question .. why are you trying to install apps to /sdcard??
This is an old thread that got bumped. This is not the way to go about getting apps to install to the sd-card.
DISCLAIMER
Proceed at your own risk. I am not responsible for ANY outcome (good or bad) as a result of YOUR actions! Even following this guide perfectly (or any other cooked ROM guide) you could (however remote the possibility) BRICK your device. IF you choose to follow this guide READ all the way through as a "dry run" until all the steps make some sense.
GATHER YOUR SUPPLIES
Phone (fully charged)
SD card (in your phone)
Computer (w/internet access)
USB cable (one that fits your phone) OR a card reader + micro SD adapter
Download these files onto your pc:
Android 1.5 base image SAPPIMG.nbh_____________________(33d958062cc02bb2cec157f68621d2ff)
To install ALT recovery flashrec _________________________(try the latest, if it fails work backward)
Alternate Recovery img recovery-RA-sapphire-v1.5.2G.img___(md5sum - 4822fd118867bb2e66a53243a408f40e)
Android 1.6 base image DRC83_base_defanged.zip__________(md5sum - 081379e9b525484bcd1ee42bd0031a4c)
CyanogenMod Rom img CyanogenMod ROM of choice________(4.2.14.1 md5sum - c2a1e549d9296d97566e86a0a1c4bc9c)
Android ring tone pack audio-resources.zip________________(md5sum - 6cbefb897e2fb3b954d19c692d5c6966)
32A users I am researching the right files/steps to get ya'll onto CM, read this page of cyanogenmod wiki in the meantime
[*]32B UK users if my method doesn't work try this post from a user on this thread
(NOTE: If any of these links 'die' Google the file name & pm me so I can update the link)
Md5sum Values
how to check md5sum in windows : MD5summer use this program to make an md5sum file & compare values
how to check md5sum in unix/linux : in terminal type 'md5sum /path/to/file.name' [enter] & compare values
Do this once the files are on your SD card to ensure no device-to-device file transfer corruption
BACK UP YOUR FILES
Before doing ANY mods you should ALWAYS backup your important files.
Connect phone to pc via USB
On the phone: pull down the notification bar & press ->USB Connected->Mount
On the pc: copy any & all files/folders you want to keep.
On the pc: Close the SD card folder on your pc.
On the phone: pull down the notification bar & press ->USB Connected->Un-mount/Turn off USB storage. Once this is done remove USB cable.
(NOTE: By the end of this guide EVERYTHING on your card will be GONE so don't skip this step!)
FORMAT SD CARD
From the home screen press Menu->Settings->SD card & phone storage->Un-mount SD card.
Once it is un-mounted press ->Format SD card.
Once it is formatted & has re-mounted go back to the home screen and press Menu->Settings->Applications->make sure 'Unknown sources' is checked.
(NOTE: if your phone is already ROOTED & running a Custom/Cooked ROM you can likely skip the SETUP section just check Amon_RA's thread for alternate install options)
SETUP
Find out what version of Android your phone has installed. From the home screen Press Menu->Settings->About phone-> scroll to Firmware Version.
(this is your Android Version)
If you're on Android 1.5 proceed to INSTALL section.
If you're on Android 1.6 re-connect phone to pc.
Copy the sappimg.nbh & place it on your SD card, then close everything & disconnect USB. (I am told this MUST be the only file on your SDcard or the validation will fail)
Turn off phone.
Boot into 'Fast Boot' like this: Press-&-Hold END/Power AND Pres-&-Hold Volume Down until the Fast Boot screen appears.
Press the trackball (action button) and wait for it to flash the sappimg.nbh
Once fully complete reboot phone & proceed to INSTALL section.
INSTALL
Connect phone to pc via USB
On the phone: pull down the notification bar & press ->USB Connected->Mount
On the pc: copy the FlashRec.apk & the Amon RA recovery.img onto your SD card.
If you don’t have a ‘file manager’ or ‘app manager’ go to the market & download one such as: ASTRO, LINDA, AppManager or the like. Then browse to your SD card & open/run the flashrec.apk to install it. (if asked what to open with choose Package Installer)
Open RecoveryFlash (flashrec) & make a backup of your current recovery.img. Flashrec just made "recovery-backup.img" on the root of your SDcard, so now rename Amon Ra's recovery to "recovery-backup.img" (choose replace when the dulpicate file name message appears) then open flashrec again & choose restore recovery. (Credit for this step goes to deb82swearingen Much easier then the orig method I was shone for using flashrec)
Once the flash is complete turn the phone off.
Boot into 'Recovery' like this: Press-&-Hold END/Power AND Pres-&-Hold Home. (this will be a black background with green text options)
Scroll down to ‘partition’ (press trackball to select)->partition SD->follow onscreen steps (HOME=confirm, VOL +/- changes partition size, any other key=cancel).
Once partitioning is complete press BACK to get to partition menu & scroll down to 'SD:ext2 to ext3’ press trackball to select (if you have a class 4 or 6 SD card you can then go for 'SD:ext3 to ext4' but don't try it on class2 cards it will cause system instability & likely FRY your SD card... if you don't know your class stop @ ext3).
go BACK until top says "Android system recovery" ->Connect phone to pc & scroll to 'USB-MS toggle'->HOME to confirm.
Copy the HTC 1.6 BASE & CyanogenMod ROM & Contacts.apk files onto your SD card then close the SD card folder on your PC & toggle USB-MS again, then disconnect from the pc.
Scroll to & select ‘wipe'->wipe data partition->CONFIRM
Scroll to & select ‘Flash update image->Apply sdcard:choose zip & select the HTC BASE file & let it complete (this will take a few min be patient). DO NOT REBOOT!
Scroll to & select ‘Flash update image->Apply sdcard:choose zip & select the CyanogenMod file & let it complete (this will take a few min be patient).
Once the flash is complete reboot phone (this will take up words of 5-10min+ be patient).
Once up & running on latest CyanogenMod connect to pc again & unzip the audio-resources.zip directly onto your SD card.
**************************Only Applies To CM 4.2.13**************************
Fixed Contacts.apk
Now that you have 4.2.13 installed it's time to fix the bug listed in Cyan's change-log. We will do this by replacing the broken Contacts app with the fixed Contacts.apk that you downloaded. If you get a pop-up asking about giving super user rights just hit the check mark to remember this answer & press 'yes'. This is UNIX & UNIX is unforgiving so pay attention to all punctuation, symbols, UPPER CASE & lower case. They are different & if you don't do it exactly it won't work. (UNIX assumes that you know what you want it to do so it will do whatever you tell it to, even if what you tell it to do breaks it.) So long as you are able to type what you see this is easy
Open Terminal Emulator & type these lines (hitting enter at the [E])
su [E]
mount -o rw,remount /system [E]
cp /sdcard/Contacts.apk /system/app/Contacts.apk [E]
mount -o ro,remount /system [E]
reboot [E]
(The reboot is precautionary but generally a good idea anytime you replace /system files.)
**************************************************************************
Themes/Modding
Now for those not fond of the plain Android theme you may enjoy this little app that has a growing movement backing it, read about what MetaMorph is here and then see the fast growing list of 'morphs/themes' available here.
Signatures
Now that you're a part of the modding community please For The Love Of MODDING take a moment to put the specs for your phone/ROM/theme/etc into your sig so that in the future if you have questions those of us who try to answer you don't have to play forum tag to get this basic info from you.
~psguardian
P.S. THANKS fhaines !!!!
fhaines spent days sifting through the forums to pick all these tidbits out of the masses of G1 ROM flashing posts & forwarded it to me so I could flash my MT3G, I want to say thank you to fhaines for his hard work. I just worked out the formatting & simplified the verbiage to as plain English as I could. Hope this helps those who are a bit timid to test the CM Rom waters (as I was).
Is it required to partition the sdcard, or is that just for Apps2SD & swap?
lupascu.marius: It's only if you want to use Apps2SD and swap.
Apps2sd and swap
Wysie said:
lupascu.marius: It's only if you want to use Apps2SD and swap.
Click to expand...
Click to collapse
Cyanogenmods newest roms run fastest with a swap and ext3 partition on the sd card. If you run it with just a fat32 and or ext2 you will most likely be running the rom a lot slower than was designed.
fhaines
fhaines said:
Cyanogenmods newest roms run fastest with a swap and ext3 partition on the sd card. If you run it with just a fat32 and or ext2 you will most likely be running the rom a lot slower than was designed.
fhaines
Click to expand...
Click to collapse
is it possible to just create an ext3/ext4 and swap only without using apps2sd? Or do i need a fat32 partition?
If I am not wrong the has to be rooted to apply cm? In which step of this tutorial does the phone gets root?
Nicely done!
A few days too late for me, unfortunately, but it's nice to know that I ended up with essentially the same procedure. My notes are quite a bit more disjointed than your instructions, however.
It'll be a good refresher once it's time to root my wife's phone, however.
Great Resource for noobs and advanced alike
I believe this should be stickied.
Damn you beat me to it. I have been looking for WEEKS on a sure fire way to root my MyTouch 3G. I tried the Relentless Rooter, the Gold Card method and everything else I could find to throw at this thing.
The steps outlined here are slightly different from what I did, but all in all, this is what worked for me, was nice, easy and worked great. The first time you Root a phone it takes a bit to get the process down, but it's not as hard as you think.
If this hasn't been stickied, it needs to be!
Looks good but I have a few questions.
I am currently running on CM 4.1.999 (1.6) and my phone is running very smoothly. I tried 4.1.9999 but it started to bog down and seriously slowed down. I've got quite a few apps and I've got the phone set up as I like it (including changing some of the icons with bettercut and that kind of stuff) I'm getting to the point where I'm a bit loathe to go through all that again, so my question is; what are the real world advantages I might enjoy if I "upgraded" to 4.2?
palexr said:
Looks good but I have a few questions.
I am currently running on CM 4.1.999 (1.6) and my phone is running very smoothly. I tried 4.1.9999 but it started to bog down and seriously slowed down. I've got quite a few apps and I've got the phone set up as I like it (including changing some of the icons with bettercut and that kind of stuff) I'm getting to the point where I'm a bit loathe to go through all that again, so my question is; what are the real world advantages I might enjoy if I "upgraded" to 4.2?
Click to expand...
Click to collapse
Have you tried CM updater? It can be downloaded from the market and should just upgrade your current rom.
Weemoney said:
Have you tried CM updater? It can be downloaded from the market and should just upgrade your current rom.
Click to expand...
Click to collapse
OK, thanks, I thought it had been switched off so to speak after the Google episode.
My main question remains though, are there any benefits? I know, I know, go and look at the thread in the Dream section but still, CM4.1.999 really does work very well on my Magic and I think it deserves representation here.
Allied to a good theme it is by far and away the best ROM for the Magic IMHO.
Im running it now and have no issues. It is very fast and reliable. I think its worth the upgrade.
Right You Are
smurf said:
If I am not wrong the has to be rooted to apply cm? In which step of this tutorial does the phone gets root?
Click to expand...
Click to collapse
You do need to be rooted to apply a CM ROM (or any other 'cooked ROM' I think), HERE is where you are officially Rooted as I understand the process.
psguardian said:
INSTALL
Connect phone to pc via USB
On the phone: pull down the notification bar & press ->USB Connected->Mount
On the pc: copy the FlashRec.apk & the Amon RA recovery.img onto your SD card.
If you don’t have a ‘file manager’ or ‘app manager’ go to the market & download one such as: ASTRO, LINDA, AppManager or the like. Then browse to your SD card & open/run the flashrec.apk to install it. (if asked what to open with choose Package Installer)
Open RecoveryFlash (flashrec) & press Backup Recovery Image.
Once it’s finished press in the text box & clear out the box, then put /sdcard/recovery-RA-dream-v1.2.3.img & press Flash Custom Recovery Image.
Once the flash is complete turn the phone off.
Boot into 'Recovery' like this: Press-&-Hold END/Power AND Pres-&-Hold Home. (this will be a black background with a screen full of options)
Scroll down to ‘part SD fat32+ext2+swap’ press trackball to select.
Once partitioning is complete scroll down to ‘then select convert ext2 to ext3’ press trackball to select.
Reboot phone.
Connect phone to pc after reboot & mount USB storage
Copy the HTC ADP 1.6 DRC83 & CyanogenMod 4.2.2 ROM files onto your SD card then disconnect from the pc & turn off phone.
Boot into 'Recovery', scroll to & select ‘nandroid backup’ & let it complete.
Scroll to & select ‘wipe data/factory reset’ & let it complete.
Scroll to & select ‘apply SD card: choose zip’ and select the HTC ADP file & let it complete (this will take a few min be patient).
Scroll to & select ‘apply SD card: choose zip’ and select the CyanogenMod file & let it complete (this will take a few min be patient).
Once the flash is complete reboot phone (this will take up words of 5min+ be patient).
Once up & running on latest CyanogenMod connect to pc again & unzip the audio-resources.zip onto your SD card.
Click to expand...
Click to collapse
fhaines said:
Cyanogenmods newest roms run fastest with a swap and ext3 partition on the sd card. If you run it with just a fat32 and or ext2 you will most likely be running the rom a lot slower than was designed.
fhaines
Click to expand...
Click to collapse
Quick question, I've followed the procedure posted on here step by step exactly and once I boot the phone up right after the android loading screen it goes to a black screen and sits there for a long time. Here's a thread I started asking for help with this, it has more info on my problem, thanks for anyone trying to help.
http://forum.xda-developers.com/showthread.php?t=578208
Things to check
lupascu.marius said:
Quick question, I've followed the procedure posted on here step by step exactly and once I boot the phone up right after the android loading screen it goes to a black screen and sits there for a long time. Here's a thread I started asking for help with this, it has more info on my problem, thanks for anyone trying to help.
http://forum.xda-developers.com/showthread.php?t=578208
Click to expand...
Click to collapse
Hey,
Couple of things to check and make sure of. You have to be on factory 1.5 before doing the upgrade to the Rooted HTC rom and Cyanogens rom, cannot do this from 1.6. Also, there is a wipe involved in the process, and if its skipped it may account for the FC's. Also there is a fix permission file you can run after installation and initial boot that may help with the FC's, its located in CM's thread in the Dream section where the rom is.
Fhaines
fhaines said:
Hey,
Couple of things to check and make sure of. You have to be on factory 1.5 before doing the upgrade to the Rooted HTC rom and Cyanogens rom, cannot do this from 1.6. Also, there is a wipe involved in the process, and if its skipped it may account for the FC's. Also there is a fix permission file you can run after installation and initial boot that may help with the FC's.
Fhaines
Click to expand...
Click to collapse
Yes, it is on the factory cupcake build when i start to try and install CM. The weird thing is i have had Cyanogenmod for a long time and have been doing upgrades and everything worked untill now. I upgraded to CM 4.2.1 and after that CM stopped working on my phone. I can confirm that 'other' rooted roms do work..so it seems like its just CM. Thanks
lupascu.marius said:
Yes, it is on the factory cupcake build when i start to try and install CM. The weird thing is i have had Cyanogenmod for a long time and have been doing upgrades and everything worked untill now. I upgraded to CM 4.2.1 and after that CM stopped working on my phone. I can confirm that 'other' rooted roms do work..so it seems like its just CM. Thanks
Click to expand...
Click to collapse
Quick update for anyone with any ideas. I finally got it to boot up and it runs great except for two things I've notices so far. When i try to add widgets nothing pops up and when i go to settings the window comes up for half a second then goes away and back to home screen. Now what I did to fix it was partition the sd card which i was told is NOT necessary. Then after i got it to work i tried again with a sdcard that was NOT partitioned and it did the same thing again, black screen no-go. So it seems like if you don't partition the sdcard on some phones the phone freezes at a black screen. Keywords being "some phones". So for anybody who knows how to fix the widget and settings problems not opening, please help me....Thanks
lupascu.marius said:
Quick update for anyone with any ideas. I finally got it to boot up and it runs great except for two things I've notices so far. When i try to add widgets nothing pops up and when i go to settings the window comes up for half a second then goes away and back to home screen. Now what I did to fix it was partition the sd card which i was told is NOT necessary. Then after i got it to work i tried again with a sdcard that was NOT partitioned and it did the same thing again, black screen no-go. So it seems like if you don't partition the sdcard on some phones the phone freezes at a black screen. Keywords being "some phones". So for anybody who knows how to fix the widget and settings problems not opening, please help me....Thanks
Click to expand...
Click to collapse
I don't think it has anything to do with SD partition type. Im running cm with a fat sd. everything's fine.
Nice lil issue...
Once it’s finished press in the text box & clear out the box, then put /sdcard/recovery-RA-dream-v1.2.3.img & press Flash Custom Recovery Image
I dont have this option when i try to flash the .img
it says Download Recovery Image and it is actually grayed out??
** PLEASE, READ THE GUIDE BEFORE FLASHING **
Flashing a device is a risky process, and you definitively have to know that your device might not boot correctly, or not boot at all. You must also notice that this method is being tested and some components of your Polaris will not working at the moment. Take into consideration that there are developers that are sharing all their work with us, but although they're really good at their job, they all have their lives. So, if something just doesn't work, please, be patient*
NAND Boot for Polaris! Made possible thanks to DZO!
This method will allow you to start Android without the need of Windows Mobile. It will just boot like if the device had a native Android OS installed onto it.
- You may see this guide really long, but it's because I tried to detail every step and I put lots of URLs to make the process easier for beginners It's not than difficult as it seems!
Step by step guide:
Needless to say that you need to have HardSPLed your device first!
1. CHOOSE YOUR ANDROID BUILD
You can install try to install any build from the Kaiser and Vogue forums. They should work for Polaris:
I personally recommend to start with Myn's Warm Donut Release 5.
You can choose it in two different screen resolutions
240x320 (my favorite) - http://download219.mediafire.com/t0lnxmijgEjg/1drm2jqwjzn/myn-WarmDonut-04-24-2010-240x320-110.zip
320x480 - http://download533.mediafire.com/ml1jxoyomIDg/miw2uzjjzjq/myn-WarmDonut-04-24-2010-320x480-160.zip
If you want more info, check its thread: http://forum.xda-developers.com/showthread.php?t=619980
Download the build. It may be a compressed file containing an androidinstall.tar.
Copy this androidinstall.tar under a folder named andboot at the top level of your SD Card. The file path should be /andboot/androidinstall.tar.
You're now ready to flash the OS loader.
2. -OPTIONAL, BUT RECOMMENDED. ERASE YOUR ROM.
To be sure that you won't have problems with the flashing, you should use a tool that executes the called Task 29 to clean the NAND memory in the device. This helps the flashing goes OK and minimizes the chance of a bad flash.*
Fortunately, there's such tool: It can be downloaded HERE (big thanks to leppa).
It's a hacked flashing tool. To make it work you will have to select a dummy .NBH file. Use the .NBH file you want, preferably a small one. You can use the one that you will download in step 3.
You it finishes the operation, your phone will NOT boot. Don't worry. This is normal. We will make it boot soon.
More info HERE: http://forum.xda-developers.com/showthread.php?p=6227425#post6227425
3. FLASH THE ANDROID OS LOADER TO NAND
You will need a .NBH in order to boot from NAND. It's usually named polaimg-panel[x]-[resolution]-[date].nbh.
I personally recommend to flash of the .NBH files by DZO dated 07-May-2010. They are listed on his site: http://it029000.massey.ac.nz/vogue/files/?C=M;O=D
Choose one according to your paneltype and resolution. Your paneltype depends on its maker. You should try from 1 to 3 to see which one works for you.
Flash the .nbh file you downloaded with your prefered tool (I used CustomRUU.exe for Windows).
To flash your device you might have to put your Polaris in bootloader mode. To enter this mode you have to do the following:
Press and hold the camera button.
Press reset while you hold the camera button. Release it (the reset button).
Hold the camera button until the colored bars screen appears.
If it doesn't work, remove the battery, wait for some seconds, put it back and try again.
When the colored screen (Hard SPL) is shown, you are ready to flash it using the flashing application (CustomRUU.exe, for example).
4. INSTALL YOUR BUILD
When you're done flashing, your device will boot. You will now attempt to install your build using the file androidinstall.tar.
You'll see lots of text lines scrolling while it boots. Now, pay close attention to the next step.
The system will prompt you to press and hold the center button of the DPad (in the middle of the jog-wheel) to start the Android Installer. It's a message like "Press x to launch the installer". Don't forget to hold it until the installer is shown!
The installer will eventually start.
A list of options should appear (in text mode). Use the jog-wheel up and down to navigate. D-pad center to select.
Choose your installation options (I selected System on NAND, Data on NAND). Don't choose any other option unless you know what you're doing.
Install it! (if it ask you to wipe the data, select yes).
Wait for the installer to finish.
The menu should appear again.
5. INSTALL THE SPECIFIC UPDATES FOR POLARIS
Due to particularities in our devices, some hardware like Wi-Fi and Bluetooth won't work properly if you don't apply some updates first.
You will need a file an androidupdate.tar to apply to the just installed system.
You can download it HERE (thanks to l1q1d).
When applied, the installer will be shown again.
You now have to select Fix permissions to avoid problems.
Don't exit the installer: soft reset your Polaris instead.
YOU ARE DONE! Your Android system will boot after some minutes.
Things that should WORK:
Phone calls: incoming/outcoming
Texting (SMS)
Data connection (GPRS/3G)
Wi-Fi
GPS
Bluetooth
Things that DON'T WORK:
USB Storage Mode
USB debugging is unstable.
Tethering
Camera (in Eclair)
Headset
Bugs/Issues:
Sometimes Wi-Fi hangs while is being disabled and prevents the device from suspending correctly (it won't sleep and the screen will turn of every time you press a button).
Data connection goes down from time to time and it won't reconnect until you go to the Modem application, disconnect, connect again and wait it to connect.
Audio Input: faulty and unusable with most of applications that use it.
* Enjoy and feel free to donate to our GREAT developers.
* I donated to our developers, and I'm from Spain. As everybody know, Spain is falling like a fainted Pokémon thanks to Zapatero (Mr. Bean II). If I can donate, how couldn't you do it?
I'm trying now.. Sorry my english...
They state that it's valid also for HARET:
if you're doing it with haret, extract basefiles to your sd, plop the androidinstall.tar into the same folder, and boot, hold down volume up just like the nand people (but don't pick nand to store the files, it won't work)
Click to expand...
Click to collapse
I've tried with the specified basefiles and plemen's Android 2.1, but I had no luck.
I noticed that when I press run from HARET and the progress bar fills up, it vibrates two times. Then, it seems that the device is hung, but after 15 seconds (or more), it boots. However, I didn't complete the rootfs-less setup process. It complaints about this:
Unable to open persistent property directory /data/property errno: 2
Click to expand...
Click to collapse
Anyone?
Wait, does this mean its totally an Android ROM? If so, COOL!
haven't tried yet ^^
Did you take the last package on sourceforge for the Eclair 2.1 Build? The files on Mediafire was corrupted.
I think there is no speed improvement with this, it's "only" an easier way to install and upgrade the system.
This is NOT "totally an Android ROM".
i can't install with this method
is there a "how to" or forum thread somewhere cause i get
sh: 2: unknown operand
losetup: /dev/block/loop1: No such file or directory
Failed
Failed to reach system.img on SD Card
Click to expand...
Click to collapse
during setup it complains "cant create folder /system cause file already exist"
i put basefiles at the root of my sd card and the vogue .tar in a folder call /andboot
all taken from here http://sourceforge.net/projects/androidhtc/
I think that you must flash a nbh that only works in vogue yet. I try to flash but it stop at 33%. I think that we must wait.
luzbel_es said:
I think that you must flash a nbh that only works in vogue yet. I try to flash but it stop at 33%. I think that we must wait.
Click to expand...
Click to collapse
Yeah, same problem. It's impossible to flash now with any package for Vogue or Kayser...
We have to wait for DZO's work to port .tar and . NBH for us...
Hi fellas:
I carried out research about the new boot up method, and it seems it will be compatible with our beloved Polaris. But it still needs some fine-tuning, first of all due to the fact that the new installer is started holding down VolUp, but this button isn't correctly recognized with the current bits.
In other words, we should wait before trying out this one. Vilord is aware of this issue.
Stay tuned!
Hi SuperJmn,
Of course I wait for ...
I look every day in the Vogue/Kaiser thread and hope we can to flash our Polaris next time.
Thanks.
Android should work much more faster after flashing... Can't wait to try this
manu33xtro said:
Hi SuperJmn,
Of course I wait for ...
I look every day in the Vogue/Kaiser thread and hope we can to flash our Polaris next time.
Thanks.
Click to expand...
Click to collapse
Hey
I have pola100 with pcar latest non-3d, Im trying my luck to get android started but with the latest files (img, rootfs, zImage) I am not able to. tried hell lot of combinations.
can you suggest me which one would I use, I downloaded some from sourceforge!
but I read that the new rootfs is for nand....
please friends guide me to right downlaods and versions for a near perfect android installation
Thanks in advance....
Niranjan
Hi! The new method is not only for NAND, but also for SD booting. It has some incompatibilities, so it's working for Vogue for the moment (Vogue owners are a bit more lucky than us in terms of development).
We are waiting for @vilord, @DZO and other authorities to fix the appropriate files.
I will contact them right after I end up writing this
Updated information for NAND boot. Thanks DZO!
Can you give us some feedback? Does it run better, smoothier than before? Or nothing about that?
it work but this resolution is not userful for me. No more speed than haret method, wifi and camera not work, system freeze some times. Do you have this problems?
How to put device in bootloader
Hello,
I've installed Android on my POLA100 (NAND method). Until now it's working fine. When I tried to put my device in bootloader mode, after installing Android, surprise... the combination (camera button pressed + stylus reset) isn't working.
If you used this: Eclair build you should download this update too: update for qvga and put androidupdate.tar from this archive on the andboot folder on your sdcard near androidinstall.tar.
After installing the system like SuperJMN said you'll have to press the power button one more after system reboot and choose update... from the menu,then quit when the menu reappear.
WIFI,Camera,Bluetooth doesn't work on this build(the only one I've tested with this new method)
Thank you SuperJMN for posting this,I hope it will remain for a long time on the front page and many thanks to DZO,VILORD,JAMEZELLE,PLEMEN and all other guys for the hard work.
Polaris
Hi,
for polaris you push power button, and boot menu works(NAND and SD).
The issue is that Wifi is not working now.
I try several builds.
So it seems not depending on the system?
Regards
How to put device in bootloader
Solved it. I put my device in bootloader by pressing the camera button + stylus reset when Android loads. I don't know if it worked because I removed my SD card and on the screen appeared "Waiting for SD card" but in that moment I've reset the device in bootloader.
After a failed OTA update, my iconia a500 stock (never rooted) bricked. Got CWM v5.0.2.3 installed through APX mode and the recovery mode starts pretty smooth when I boot with Vol DOWN + Power.
I can install every ROM (custom and stock) I could lay my hands on, ranging from 3.0.1 to 4.0.*. Also did the wipes in all imagined combinations: before installing a rom, right after installation (before first boot) and also after 1st boot attempt. Also made sure to format /data, /cache, /system and so on before every installation. Tried different SD cards and also a USB mass storage thumb drive.
The thing I just can´t explain yet, is how on every try the same thing happens, 1st boot (long one) seems to just fail and my tab gets back to that screen where you see the clock on the lower right and the pulley icon saying "Android System" on the upper left corner. After that, every boot does that and the Android initial setup screens never comes up.
Every rom I try delivers the same result, even though I get their splash logos (ephiphany, taboonay, thor) and all seems to be going OK, it always gets back to that "Android System", no error messages, nothing.
I found out that Thor rom 14.2 made the "Android System" screen touch responsive (no other did that), I can touch the clock, open the first level of settings and if I try to drill down, touching storage for an instance, it won´t load the app/menu, it gets righ back to the good old "Android System" screen.
After a custom rooted rom gets installed and I get the "Android System" screes, adb works fine and I manage to get in the tab with a shell, mount an SD card, use the ps command to see the process running and even start the bootanimation myself, so I´m assuming that android is runing OK, at least on the background. Adb also allows me to push files and install apks normally. Have some linux background myself, used the shell to browse around and checked some of the logs, nothing clear showing an error that would force my boots to terminate sooner.
Wondering if anyone experienced something like that and could point me at some direction. Am I missing something here ?? Thanks guys and great job i might add.
Still no luck ...
Hi everyone, wanted to get back and maybe share my logcat and bugreport retrieved by adb shell. If any of the more experienced members could take a look and point me to some direction, I´d really appreciate. Really i´ve tried all the methods arround here and other forums to unbrick it, it behaves and responds as if everything was OK and still fails to boot for the first time, even though, the system appears to be running ok on the backgroup the initial setup wizar never comes up and I get the "Android System" dreadfull screen.
Discovered that once in with adb shell I can run the setup wizard (calling it by prompt: am start -a android.intent.action.MAIN -n com.android.setupwizard/.SetupWizardActivity), but it only stays opened for a couple of seconds and never finishes its business, it just abends.
Not sure if this would be the proper thread to post, it would be great if someone could adivise where would be a proper place.
Thanks for your time.
Hi vortex,
Were you able to fix that? I'm having the exact same problem. :-(
I've been trying for days already.
Cheers,
So I've had a bit of bad luck mixed with poor timing. Here's the run down.
I have an Asus Transformer TF101 which was running the stock rom.
I rooted my Tablet a few weeks back without any problem. Things were great. Then, I tried to upgrade to Jelly Bean from ICS using Team EOS (I followed these 2 threads mainly, http://www.transformerforums.com/fo...ficial-faq-teameos-4-android-4-2-x-tf101.html & http://forum.xda-developers.com/showthread.php?t=2063406)
I put the ROM and all the files needed onto my micro SD card.
I booted into TWRP and followed the instructions. Things seemed to have gone great. When I rebooted, I saw the new splash Logo upon bootup and awaited it to do it's thing. It never did. I let it run for an hour and it never made it into the OS.
I rebooted, went back into TWRP with plans to redo the procedure, only now the microSD card slot is not being picked up. I tried multiple micro SDs of different sizes (1GB-32GB), I've tried inserting before boot up, inserting after bootup, inserting after bootup and then rebooting the device. No luck.
I bought a USB adapter that plugs in where the power plug goes, hoping I could run the files off a USB flash drive. or a micro SD card within a USB flash drive. No luck.
I am running Teamwin's TWRP 2.3.2.3
My backup from nandroid happens to be on my microSD card too. So I can't use it to recover the old OS either.
TL;DR: Micro-SD card stopped working after a failed attempt to flash an OS. OS and backups are on the microSD card. PC recognizes the device but won't let my access the hard drive.
Does anyone have any suggestions on what to try?
Thanks!
Well, the USB is not set up to be mounted in recovery. Keep in mind, the microSD is mounted at /sdc/ in TWRP.
You can always use ADB and push a file to the internal (/sdcard/) so you can flash if your microSD slot is dead.
Let me find a post on how to do this.
EDIT: Here is what to do if you need to use ADB:
Plug tablet to PC via USB
It should install new hardware and show 1 devices, an ADB device.
Update the driver in the Device Manager on the windows machine to the Naked Drivers
Once that is updated, I downloaded ADB from the Android SDK. You really only need three files, available here: http://db.tt/b9dQ6xzp
Unzip these files to a folder called c:\adb
Open a command prompt and type the following:
Code:
c:
cd c:\adb
adb devices
It should show a device connected. It may error out when restarting the daemon, but keep trying and see if it can find your tablet.
If you cannot get the ADB driver installed or updated, my guess is that you have a bad USB cable. Yes, it IS possible to have a bad cable for data transfer that STILL charges your tablet. I have even had that happen to me.
If you got this far, then here is what to do next:
Download your favorite ROM. If applicable, save any other files needed (GAPPs or kernel)
Save this at c:\adb\ROM.zip. Other files save accordingly like Kernel.zip and GAPPs.zip.
Next, run the following commands
Code:
adb push ROM.zip /sdcard/
Once this competes, you will need to repeat for any other files to flash like GAPPs or Kernel.
After these files have been transfered, you can install a file from the internal (/sdcard/) directory.
frederuco said:
Well, the USB is not set up to be mounted in recovery. Keep in mind, the microSD is mounted at /sdc/ in TWRP.
You can always use ADB and push a file to the internal (/sdcard/) so you can flash if your microSD slot is dead.
Let me find a post on how to do this.
EDIT: Here is what to do if you need to use ADB:
Plug tablet to PC via USB
It should install new hardware and show 1 devices, an ADB device.
Update the driver in the Device Manager on the windows machine to the Naked Drivers
Once that is updated, I downloaded ADB from the Android SDK. You really only need three files, available here: http://db.tt/b9dQ6xzp
Unzip these files to a folder called c:\adb
Open a command prompt and type the following:
Code:
c:
cd c:\adb
adb devices
It should show a device connected. It may error out when restarting the daemon, but keep trying and see if it can find your tablet.
If you cannot get the ADB driver installed or updated, my guess is that you have a bad USB cable. Yes, it IS possible to have a bad cable for data transfer that STILL charges your tablet. I have even had that happen to me.
If you got this far, then here is what to do next:
Download your favorite ROM. If applicable, save any other files needed (GAPPs or kernel)
Save this at c:\adb\ROM.zip. Other files save accordingly like Kernel.zip and GAPPs.zip.
Next, run the following commands
Code:
adb push ROM.blob /sdcard/
Once this competes, you will need to repeat for any other files to flash like GAPPs or Kernel.
After these files have been transfered, you can install a file from the internal (/sdcard/) directory.
Click to expand...
Click to collapse
Thanks so much frederuco! I will be trying this later today and will update this post as soon as I do.
I just wanted to say good luck, and we are all counting on you.
Almost there!
frederuco said:
I just wanted to say good luck, and we are all counting on you.
Click to expand...
Click to collapse
The update! I followed your instructions, while on the cmd prompt, I got no confirmation that the files were moved, but they appear to be on the device now. When I go to reinstall through TWRP, the flashing fails. I am going to do some digging around the forum to see what solutions there may be, but if you (or anyone reading) has an idea, do tell.
I will be sure to update this thread if I fix it, including the solution I found.
Try downloading the ROMs again.
Also, note that I edited my reply as I had said ROM.blob and it should be ROM.zip.
frederuco said:
Try downloading the ROMs again.
Also, note that I edited my reply as I had said ROM.blob and it should be ROM.zip.
Click to expand...
Click to collapse
I think I'm in good shape. I tried to edit my post from earlier, but I had to wait a few minutes before it would let me.
I realized the file didn't finish transferring to the tablet. Moments after my last post, I got a confirmation from cmd prompt that the first file finished. The second one just finished, and the third is still transferring I suspect. That would totally explain the failure.
db1984 said:
I think I'm in good shape. I tried to edit my post from earlier, but I had to wait a few minutes before it would let me.
I realized the file didn't finish transferring to the tablet. Moments after my last post, I got a confirmation from cmd prompt that the first file finished. The second one just finished, and the third is still transferring I suspect. That would totally explain the failure.
Click to expand...
Click to collapse
Yes, that would do it!
frederuco said:
Yes, that would do it!
Click to expand...
Click to collapse
Alright, so I got past the logo, Android upgraded all the Apps and is now "Starting apps" .. it's been here for about 10 minutes. I think I can take it from here.
The ADB push was the solution.
Waited another 15 minutes. Nothing happened (stayed at Starting apps)
Restarted device. Booted up as it should and I am now all set. Thanks again!
Now that you're using EOS can you use the microSD slot? I know moving from stock to EOS fixed my card slot issues not to mention that I'm loving the Jellybean goodness
Sent from my Nexus 7 using Xparent Purple Tapatalk 2
bsoplinger said:
Now that you're using EOS can you use the microSD slot? I know moving from stock to EOS fixed my card slot issues not to mention that I'm loving the Jellybean goodness
Sent from my Nexus 7 using Xparent Purple Tapatalk 2
Click to expand...
Click to collapse
I'm fairly certain the slot itself is broken. Haven't been able to get it to read things yet.
I'm still having some minor issues with the setup, but I know I've seen fixes to these problems when browsing this forum. Google Search/Google Now crashes 3-4 seconds after opening it. The system also reboots "randomly" (really, just when it's idle for more than 10 minutes), I also had to go into TWRP last night to get the system to power down. Long pressing power and selecting Power Off simply rebooted it.
But compared to where I was 24 hours ago (and had been stuck there for 1+ week, I really didn't want to burden people with my problem since I'm a lurker here), I really can't complain and have full confidence that I'll be able to get the kinks worked out.
At least I have an adapter for the power port, so I can plug USB sticks (or USB-microSD adapters) into the tablet still.
db1984 said:
I'm fairly certain the slot itself is broken. Haven't been able to get it to read things yet.
I'm still having some minor issues with the setup, but I know I've seen fixes to these problems when browsing this forum. Google Search/Google Now crashes 3-4 seconds after opening it. The system also reboots "randomly" (really, just when it's idle for more than 10 minutes), I also had to go into TWRP last night to get the system to power down. Long pressing power and selecting Power Off simply rebooted it.
But compared to where I was 24 hours ago (and had been stuck there for 1+ week, I really didn't want to burden people with my problem since I'm a lurker here), I really can't complain and have full confidence that I'll be able to get the kinks worked out.
At least I have an adapter for the power port, so I can plug USB sticks (or USB-microSD adapters) into the tablet still.
Click to expand...
Click to collapse
The workaround for Google Now crashing is to disable Hotword Detection in Settings - Language & Input - Voice Search (or something like that). Search the EOS thread for "Hotword" and you will find the location.
Do you have a SD in the dock? This can cause SOD and RR's.
Hmm, I guess I have never tried powering down on EOS, but I am pretty sure it works. I just put my tablet to sleep and never turn it off. I find my tablet (even undocked) will lose more power when it is off than when it is sleeping.
frederuco said:
The workaround for Google Now crashing is to disable Hotword Detection in Settings - Language & Input - Voice Search (or something like that). Search the EOS thread for "Hotword" and you will find the location.
Do you have a SD in the dock? This can cause SOD and RR's.
Hmm, I guess I have never tried powering down on EOS, but I am pretty sure it works. I just put my tablet to sleep and never turn it off. I find my tablet (even undocked) will lose more power when it is off than when it is sleeping.
Click to expand...
Click to collapse
Nope, nothing was in the dock. I actually didn't have the keyboard dock plugged in during the "crisis"- I did try getting TWRP to read a card from it once, that was about it.
I read somewhere else, that once you let the battery die on it's own, and recharge, the "never powers off" issue goes away for many people (haven't seen one specifically relating to EOS on TF101, but the other symptoms were spot on)
I'll be checking out the Google Now tweak in a bit.
I'd been running a custom kernel on my Transformer since about a week or two after I bought it at a Black Friday sale simply because it would keep running on the stock ICS ROM. Changed to KAT kernel when I moved to EOS. You might want to consider a custom kernel if you have a Transformer that suffers from the reboot issue like mine did.
Sent from my Nexus 7 using Xparent Purple Tapatalk 2
db1984 said:
-snip-
Click to expand...
Click to collapse
You may want to try doing a full format in TWRP, and using the superwipe full scripe from the ARHD thread, then formatting again, wipe cache and dalvik, push the latest EOS, KATkernel and Gapps to the device, wipe dalvik cache and cache, flash EOS, wipe dalvik cache and cache, boot into the ROM, boot back into twrp, wipe cache and dalvik, flash Gapps, wipe cache and dalvik, boot into the ROM, boot back into TWRP, wipe cache and dalvik, flash KATkernel, wipe cache and dalvik, cold-boot into the ROM.
That should set you up with the most stable your tf is going to get, it seems erroneous and like a ton of work, but I strongly believe in doing this whenever I flash a new rom setup, I've gotten to doing it in about 10 minutes now.
Just an update.
EOS's random reboots were getting pretty bad. Happened a few times while I was working on a few docs (thankfully Evernote had autosaved)
I also noticed when the screen would go off, it would eventually turn back on and attempt to reboot, getting stuck at the Asus loading splash (pre EOS logo). I ended up re-flashing with my newly gained leet adb skills (thanks frederuco ) and went with Cyanogenmod 10. I've only had 1 random reboot since and Google Now seems to work 90% of the time.
I'm sure there are some more things I can do to fine-tune it, still getting a hang of everything.
Thanks again for everyone who's helped.