** 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.
Here is my story.
I found a patch that was supposed to give me ad-hoc on my coby 7015. i don't quite remember where i got it but i believe it was in the xda forums. well i'm not sure if it wasn't written correctly, was malicious, or if i didn't read the details correctly but i tried to install it. this also may have had a part in why things went south. I first tried to use the regular recovery util to install it since the zip was called update...w/e that didn't work. i then switched to clockworld recov to install and i used the apply update from sdcard setting...didn't look at when it was installing i just rebooted and kept moving ( i was at work and pressed for time).
when i realized my wifi wasn't working anymore i tried to install it again realizing maybe it was the way i did it, so it stead of the "apply" option, i used select zip to install. still the same problem...
after all this i decided the best thing to do would be to
1. see what was updated in the file: only thing i saw other than certs was the wpa_supplicant file
2. find an original version of said file and replace it: I did this via WinVista instead of terminal for couple of reason the primary being that i couldn't remember the command to copy/paste in linux and i wasn't sure if the terminal could extract and re-zip files.
so plugged into the laptop i pulled files and tried updating first in the regular again, then in clock world with similar results and the same problem.
Ieventually tried posting a question on the linux forums because it was quickest and i usually get fast answeres, however, i was impaitent so i ended up doing the most fatal part of this. I decided to do a factory reset.
I started with the main recovery util and used the reset:
1. i still had the same problems with wifi
2.ALL my APPS (including my emulator and root access, the most important of al my apps)
I then tried the UI factory reset and got nothing.
Becoming frustrated I tried really just a freak, last ditch attempt. used the coby update found on there site and it fixed the wifi. I am now lacking Gapps and my other apps but i can now get those back cuz i have wifi....whew
I use this build
http://forum.xda-developers.com/showthread.php?t=712310
And Nand flash.
Here is the problem:
1/ I have to recalibrated the phone after reset ( not so annoy)
2/ the battery indicator is alway 99% after reset ( it's the big one)
3/ GPRS doesn't work
4/ Camera doesn't work ( it work on haret mod with this build http://forum.xda-developers.com/showthread.php?t=712310)
I'm a beginner, anybody can help me please, thanks.
You needed the 2.6.2.5 stable kernel for your Boot image. It is the only build where camera works on NAND. See the l1q1d's tutorial on creating a POLAIMG.NBH using Atools. You needed a POLAIMG.NBH composed of the stable kernel. Maybe with this boot image youll get a more accurate battery report.
Anyway to spare you the search here is my Polaris boot image with 2.6.2.5 kernel. Follow these steps:
1. Be sure to have the andboot folder still on your SDcard.
2. Download the two files below. I suggest you put these two files in one folder.
3. Connect your phone thru usb, then press down camera while pushing the reset button till 3-color boot bios appear then release reset button only. Wait till the SERIAL word becomes USB, and then run CustomRUU.exe then follow the instructions in flashing screen.
4. As soon as flashing is done, when the phone resets wait for the penguin to appear then press down the CENTER navigation button till it brings you to a Boot Screen with choices.
5. Choose the "INSTALL SYSTEM" choice. If it asks to erase data files choose YES.
6. After it is finished you'll be back to the BOOT screen. If you have updates for your ROM choose the choice "INSTALL UPDATES". Otherwise just skip this step.
7. Finally when all is done choose "FIX PERMISSIONS", then go to "EXIT" choice.
That's it you just changed your kernel. You can always change for any other "ROM" by copying over your androidinstall file within the andboot folder and follow the steps starting from number 4 only because you dont need to install the boot image again when changing roms. By the way if your setup worked and you think everything is fine after a reset, then you can always go to the BOOT screen and choose "BACKUP/DATA" so that you can always choose to "RESTORE/DATA" again if the rom fails in the middle of an operation saving you the time reinstalling apps again. You can even change to a newer POLAIMG.NBH and still restore the same data it wont matter.
POLAIMG.NBH kernel 2.6.2.5 for Pola100
CustomRUU.exe for flashing boot image thru USB
Thanks for your help.
Can you tell me which build you are using?
Does your battey show the level right?
Thanks again
i am using the Not-so-super-Froyo build from the Kaiser forum. I had been using it for over 2 months now. I occasionally get "errors" that need to restore data but its because Im an app addict. Usually end up with a bad app that would corrupt but anyway that's what I love with Android. Everything else, this build is very stable and fine.
As with the battery yes it does, though my battery wouldnt last longer than 5 hours coz i got so many working apps in the baCKground and i dont turn off Wifi and Gmail from sync. If i turn off wifi and gmail the battery would last 15 hours maximum in standby.
Edit: SOLVED
Hoping someone can roughly point me in the right direction. I'm not very savvy in flashing new ROM's, but I had success with my phone recently, so I decided to try and update my tablet and it's not going so well. It's a Samsung Galaxy Tab 10.1, model GT-P7510MA, which I believe is wifi only. I started off by following the youtube tutorial: 0eAQzxwEVjY
I did *not* make a backup, so shame on me right off the bat, but at least now I've learned this lesson.
There is no OS, but TWRP v2.2.0 is installed and I'm able to boot into it just fine. I'm able to transfer/push files via command line on my windows machine, but I did find something that seemed odd, which is that the top level directory is not named "/sdcard", instead it's just "/". When I transfer files, I have to name the the path "/" for them to show up in the top level directory. If I use "/sdcard", it looks like they upload, but I have no idea where they go. Not sure if there's any significance there, but figured I'd mention it.
The problem is that I can't seem to install any OS. I've tried Nameless 4.4.4, Clockworkmod 10.1, and AOSP 6.0. They all fail the same way, I'll type out what it says below:
--Install /aosp-6.0-p4-20151211.zip ...
Finding update package...
E:unknown volume for path [/aosp-6.0-p4-20151211.zip]
E:Can't mount '/aosp-6.0-p4-20151211.zip'
* Verifying filesystems...
* Verifying partition sizes
Error flashing zip '/aosp-6.0-p4-20151211.zip'
Another strange thing is that when I tried the aosp-6.0-p4wifi, it said that this device was a p4, which I don't think is correct, but that's why I tried the p4 version. It errors just the same. I've also tried to update TWRP, but I'm not sure you can update TWRP from within TWRP? I've tried using the file "twrp-2.8.7.-picassowifi.zip" and it errors the same as the OS'.
Edit: It's been sitting here powered on for a bit and then went to the blue teamwin screen and would flash off every five seconds or so. I figured this was maybe a screensaver? Next it powered off and on restart, all the files I've uploaded are no longer visible.
Any guidance is much appreciated.
Final edit: Kind of embarrassing...all I needed to do to find the /sdcard directory was just scroll down a little through the folders on the left (I thought it was supopsed to be the top directory). I'm pretty sure the 7510 is a wifi only version, but for some reason, none of the wifi ROM's I've tried will work. It gives an error and says my device is a p4 and not a p4wifi. Anyway, neither of the wifi/p4 Marshmallow ROM's will work, but all I had to do was wipe cache/delvic/system (I did do this several times) and factory reset (had not done this before) and install Cyanogenmod for p4 with the recommended Google Apps and all is working well.
I just got a s5 prime from eBay and was in the process of debloating via tibackup but kept getting stuck at boot screen showing warranty kernel bit. Required a restore of system and data each time to get it going again. Through arduous process of elimination I was able to narrow the culprit down to the aforementioned seemingly innocuous apk. When it's removed the phone dies.
What's even stranger is that this page seems to indicate that it's fine to remove:
http://forum.xda-developers.com/gala...oater-t3319854
I'm just curious as to why!
Sorry for digging but people need to know! I wish I saw this post earlier. I spent whole night trying to see what causing my phone to endless boot.
After few hours I see that If you remove DictDiotek it won't boot anymore. And I thought that this is uselles dictionary and everywhere people write that it's safe to remove.
GALAXY S9+ OREO
KamilKiri said:
Sorry for digging but people need to know! I wish I saw this post earlier. I spent whole night trying to see what causing my phone to endless boot.
After few hours I see that If you remove DictDiotek it won't boot anymore. And I thought that this is uselles dictionary and everywhere people write that it's safe to remove.
GALAXY S9+ OREO
Click to expand...
Click to collapse
I remove it from all my ROM builds with NO PROBLEM...
@AFFAFXP - I believe you because I've always removed it from my S7 and It worked fine. But on S9+ it's causing endless boot for me. I think that it's ROM related or something (or maybe language related)
KamilKiri said:
@AFFAFXP - I believe you because I've always removed it from my S7 and It worked fine. But on S9+ it's causing endless boot for me. I think that it's ROM related or something (or maybe language related)
Click to expand...
Click to collapse
endless boot is from some files in the /lib I believe if you look for these from a rom that worked and replace them in the rom your installing this would work in this case as well...
This link originated here >>>> https://www.tech1xpert.com/guide-to-port-roms-android/
Fixing a Bootloop
Your Port should take less than 5-8 minutes to boot. When the screen dims during boot logo, your Rom has successfully boot.But If your waiting for like 15 minutes, and boot logo is still going, YOU HAVE A BOOTLOOP. Luckily, the fix is easy!
STEP1:
Navigate to “PORT” folder. A ROM THAT BOOTS AND WORKS for you device
STEP2:
Go to lib folder inside System folder of Base Rom.= ROM That you want to install
STEP3:
Inside lib folder of PORT search for these libs:
libandroid_runtime.so
libandroid_servers.so
libmedia_jni.so
Once you find each, copy them to the lib folder of Base Rom.= The ROM you want to install -- Right-click lib folder of Base Rom, select paste, and click the box in the lower left corner. Now “Click Move and Replace”
STEP4:
All done! Now add to a zip and flash!
This HAS WORKED in my attempts on PORTS that BOOTLOOP KUDOS
The same problem happened on my device. I took it to the mechanic before I tried to get into the recovery screen. We thought there was a power problem. The mechanic probably damaged my robust device because they didn't open it properly and handed it back to me in a broken state.
By taking a second N910C device and risking it, I repeated the same process step by step and found that the problem was caused by uninstalling the program "DictDiotek.apk". I restored my backup with Recovery. And my device turned on normally. DictDiotek is not a problem if frozen. Only uninstalling the phone does not turn on.
My phone is N910C. Custom ROM 6.0.1: Ditto ROM DN6