Related
Hello everyone. I haven't flashed Android to NAND yet but I'd like to try it.
I am sure this question has been asked before but I did try the search and I couldn't find it. Sorry if this has already been asked.
So, for the Kaiser, if I flash Android to NAND (ie: Polymod's most recent) how do you flash back to Windows Mobile?
I'm concerned because USB does not connect properly when Android is running with HaRET ("unrecognized USB device" using XP SP3 couldn't make heads or tails of the drivers in the SDK but then I didn't try installing the whole environment)
So I guess my question is -- even with the device unrecognized, can you still flash it back? If so, how? Is it really simple and easy?
Please let me know and point me in the right direction! Thanks!
aikeru said:
Hello everyone. I haven't flashed Android to NAND yet but I'd like to try it.
I am sure this question has been asked before but I did try the search and I couldn't find it. Sorry if this has already been asked.
So, for the Kaiser, if I flash Android to NAND (ie: Polymod's most recent) how do you flash back to Windows Mobile?
I'm concerned because USB does not connect properly when Android is running with HaRET ("unrecognized USB device" using XP SP3 couldn't make heads or tails of the drivers in the SDK but then I didn't try installing the whole environment)
So I guess my question is -- even with the device unrecognized, can you still flash it back? If so, how? Is it really simple and easy?
Please let me know and point me in the right direction! Thanks!
Click to expand...
Click to collapse
I beleive you can always follow the process here.
Your boot loader should not change when flashing so not being able to use the USB while in Android is not going to prevent your returning back to a stock ROM. I have not tested this but I'm pretty sure that you can always get back to your boot loader screen and re-flash from that point. Can someone confirm that this is the appropriate solution?
deekjx said:
I beleive you can always follow the process here.
Your boot loader should not change when flashing so not being able to use the USB while in Android is not going to prevent your returning back to a stock ROM. I have not tested this but I'm pretty sure that you can always get back to your boot loader screen and re-flash from that point. Can someone confirm that this is the appropriate solution?
Click to expand...
Click to collapse
Did anyone try this solution?
Since the bootloader is still there all you do if not able to flash via async when in android is flash via bootloader
Moved to general as not ROM Dev.
Thanks for the information, guys!! I will have to try it out over this weekend and see how it goes...
I can confirm that flashing via bootloader works fine, also flashing from SD works as well, in fact I keep a 128MB sd with a WM kaisimg.nbh on it handy just in case I need to flash a good WM rom for some reason.
Is there an Android OS with everything working on the Kaiser?
Dukenukemx said:
Is there an Android OS with everything working on the Kaiser?
Click to expand...
Click to collapse
You can see in different post of android rom what works and what doesn't works.
actually, Bluetooth and camera never works for in android 2.x build and some other apps doesn't works
I've been running Android for a few weeks now from this thread:
http://forum.xda-developers.com/showthread.php?t=614382
I've found everything to work with the exception of Bluetooth, video camera (normal camera works fine), and the barcode scanner. Also, my battery life is cut in half, but I have an extended life battery so I get a day or two out of it.
I prefer this method as you can just boot Android at will and can soft reset to go back to WinMo.
Just to let everyone know I did flash WM back just fine since I have HardSPL 3.56 and used the stylus to press the reset + camera button at the same time to get to the tri-color screen.
From there I flashed from USB without any problems.
Thanks again for all the help!
I am having problems reverting back to WM after attempting to install android to NAND. Something happened where the only way I was able to get to the android installer would be if I had the KAISDIAG.nbh file on the SD card so it would get past the tri color hard spl screen . Well as a result, I can't get into boot loader. It shows that screen for a split second, then if I do camera + power and then reset. Then I have to pull the battery. Can someone help me? It seems like it will only go into the Android bootloader, which obviously won't allow it to install a WM rom. SD flashes are my only choice because the usb port is pretty messed up. Any help would be greatly appreciated. Thanks.
The procedure for flashing WM back using SD card is much the same as flashing the Nand bootloader for Android.
First get a WM rom, copy the RUU_Signed.nbh to SD card, rename it to KAISimg.nbh, pull the battery, replace, press power and hold camera button, this should start the flash process.
Note that the SD card must be formatted FAT32, or it will not find the KAISimg.nbh.
If you prefer to flash a stock rom you will usually have to extract the RUU_Signed.nbh from the installer, just open it in winrar.
the reset in android is not working correctly. The correct way to get into bootloader is to pull the battery, wait a few minutes, rpelace the battery, press power and then press and hold camera button, do not use reset.
zenity said:
The procedure for flashing WM back using SD card is much the same as flashing the Nand bootloader for Android.
First get a WM rom, copy the RUU_Signed.nbh to SD card, rename it to KAISimg.nbh, pull the battery, replace, press power and hold camera button, this should start the flash process.
Note that the SD card must be formatted FAT32, or it will not find the KAISimg.nbh.
If you prefer to flash a stock rom you will usually have to extract the RUU_Signed.nbh from the installer, just open it in winrar.
the reset in android is not working correctly. The correct way to get into bootloader is to pull the battery, wait a few minutes, rpelace the battery, press power and then press and hold camera button, do not use reset.
Click to expand...
Click to collapse
Thanks, but unfortunately this still did not work. Have any other suggestions? I think the only way will it even do anything is if I have the KAISDIAG.nbh file on the card. It recognizes that, but then goes straight to linux. IDK what else to do. Could you be a little more clear on the procedure for getting into the bootloader? Thanks.
Ok please follow these steps carefully.
1. Format the SD card, make sure you are formatting it as FAT32, not FAT.
2. Download a Winmo Rom from somewhere handy.
3. Extract the Rom to a handy folder, find the RUU_Signed.nbh file, rename that to KAISimg.nbh
4. Copy the KAISimg.nbh file to the SD card. You should only have one file on the SD card, no folders just the NBH file.
5. pull the battery from the phone, wait at least 5 minutes.
6. Replace the battery. Press Power button, and hold down camera button, until the tri color screen appears.
7. The screen should now change to a white one, and when it's checked the nbh it will ask you to press power key again. do that.
8. Now it should flash the rom, this should take a while, 5-10 minutes, once it's finished you should get a message of success.
9. Now pull the battery again, wait 5 minutes, replace the battery, and power on, you should now boot into Winmo.
Hopefully this should solve your problems, if not then let me know which setp failed and we can work on that stage.
Finally, don't panic, take it slow, it'll all work out
Thanks, but the problem starts at number 6. I am supposed to press the power button, release it, and hold the camera button till it gets to the white screen, right? It's still stuck at the splash screen. I tried holding both and that didn't work either. Anything else I can try? I hope i'm not screwed?
If I put the battery in, boot it up, then push the camera and insert the stylus into the reset hole, it gets to the tricolor screen, then for about 0.5sec it flashes the white screen with a message saying "No image File." I know for sure the .nbh file is there.
I have experienced this before, when I tried to use an SD card that was formatted FAT, when formatting you must make sure it is formatted FAT32, the bootloader cannot read FAT formatted SD cards, even if Winmo and Android can.
I format using a card reader, and in windows it is sometimes easy to overlook the file system type, most SD cards are usually formatted FAT when they are new, and you must change the formatting, or it will just format FAT again.
zenity said:
I have experienced this before, when I tried to use an SD card that was formatted FAT, when formatting you must make sure it is formatted FAT32, the bootloader cannot read FAT formatted SD cards, even if Winmo and Android can.
I format using a card reader, and in windows it is sometimes easy to overlook the file system type, most SD cards are usually formatted FAT when they are new, and you must change the formatting, or it will just format FAT again.
Click to expand...
Click to collapse
Unfortunately, as much as I wish it was, it is not the problem. I'm on a Mac, but booted windows 7 to be make sure it was formatted to FAT 32, which it was. Is there some way I can fix permissions? Every time it runs, I keep getting the error saying that it is in read only mode. I obviously need to get it into writing mode. I don't think the fix permissions option on the installer did anything either.
The eclair build still will not install on my phone. I changed to an earlier .nbh file and now don't need the KAISDIAG.nbh file to get out of the splash screen and into the installer. When I run the install command for NAND, it says it can't mount, "no such file exists", "failed to extract." Keep in mind I haven't even gotten Android installed to NAND, just the installer itself. I can't even go back to WinMo either. It also seems like a permissions error since I believe it said the SD card is read only, but when plugged into my computer I fixed that and now it is read-write, but not on the phone. Please help because I really want to either get this working, or get back to WinMo instead of have this useless phone I currently have. Thanks.
Is there a way to enter the command line from the installer screen?
Tilt Fanatic said:
The eclair build still will not install on my phone. I changed to an earlier .nbh file and now don't need the KAISDIAG.nbh file to get out of the splash screen and into the installer. When I run the install command for NAND, it says it can't mount, "no such file exists", "failed to extract." Keep in mind I haven't even gotten Android installed to NAND, just the installer itself. I can't even go back to WinMo either. It also seems like a permissions error since I believe it said the SD card is read only, but when plugged into my computer I fixed that and now it is read-write, but not on the phone. Please help because I really want to either get this working, or get back to WinMo instead of have this useless phone I currently have. Thanks.
Is there a way to enter the command line from the installer screen?
Click to expand...
Click to collapse
Alright, I'll try and sum up your experiences. Tell us if we're missing anything;
You have the following symptoms
Linux Android-installer works
Tri-color bootloader semi-works
You cannot use the USB
You cannot install polymod's Eclair build
Now, you have mentioned a couple of things you have tried, such as
Replacing the Linux NBH with another version
Fixing permissions on the SD-card
Fixing permissions through the Android-installer
Flashing a WinMO ROM through SD card
You did mention getting other behaviours when you switched to another NBH, such as "KAISDIAG.nbh" not being required.
Now, this is a long shot coming from me, as I have had no troubles with flashing, and the fact that I can use my USB, but since your phone is pretty messed up I guess it can't hurt as a suggestion;
You can flash to other NBH's I take it, as you mentioned you did a downgrade. What I'm a bit curious about is whether you did try to flash to a WinMO rom when you had downgraded to your current NBH.
Also, you said the previous NBH required you to have "KAISDIAG.nbh" on the card to even get working. Did you try and rename a WinMO-ROM's NBH to "KAISDIAG.nbh" and flash that? Might be that the flasher is really constrictive with the file names.
EDIT: Oh, and what about trying to run other Eclair builds? Just to see if you can nail it down to this being a problem of the builds or something more bound to the actual hardware/SPL/NBH's.
I was wondering if there is a way to start haret in android? the only version I can find is for WM, so maybe is there a type of emulation layer it could be loaded to? Even better if there was an android version we could use that to reboot an SD run android and also boot into different version without having to reboot the entire phone and load wm up again (and nand android could then "haret" a diff version through sd).
Not sure you actually understand what the difference between Haret and Nand is.
Haret is, ( and always has been), a WM program, in fact it would make no sense to have it running as an android program, what Haret does is allow a WM device to run a Linux OS, that is all it does.
I think what you want is a way to dual-boot, to run different builds, which is possible, using the installer menu to choose which one to run, as well as where it is installed.
How it works is this, install your main build to nand, sys on nand, data on nand.
Then install another build, sys on SD, data on SD.
Once installed you have 2 builds, one on SD, the other on nand, to switch, you must reboot, enter installer, change the target settings to SD or nand, and quit, it should now boot from the installed version you chose,
I think you may have to have 2 ext2 partitions on SD for this to work, not sure since I never tried it, but I do remember someone posting this idea on the forum some time ago.
basically I want to boot an sd build from within an sd build. This serves a few purposes, mainly no need to boot into a different os (wm in this case) just to boot a diff version, and to allow a type of reboot on an sd build. If this can be done in script that would work also but want an android app to kick the current build out of memory and load a new one in (or the same one reloaded) instead of it being wm based. This might be something we can do with the kernel to just dump the current gui and load the other gui onto it?
edit: BTW I am using a type of boot you are explaining but instead of installer in between I have wm with different "andboot" folders.
ghghgh14702 said:
basically I want to boot an sd build from within an sd build. This serves a few purposes, mainly no need to boot into a different os (wm in this case) just to boot a diff version, and to allow a type of reboot on an sd build. If this can be done in script that would work also but want an android app to kick the current build out of memory and load a new one in (or the same one reloaded) instead of it being wm based. This might be something we can do with the kernel to just dump the current gui and load the other gui onto it?
edit: BTW I am using a type of boot you are explaining but instead of installer in between I have wm with different "andboot" folders.
Click to expand...
Click to collapse
Interesting concept, and theoretically possible, since Android itself is a shell on the Linux core, it may be possible to do this, perhaps a remount of /system and /data, then a restart of the kernel, almost certainly requires some hardcore Linux knowledge, anyone up for this?
This posthttp://forum.xda-developers.com/showthread.php?t=594077 is for the dream.
We've been able to from internal or sdcard on vogue,kaiser, polaris for ages from boot.
The only other way is to use grub 'if possible'.
I think ghghgh14702 means that directly reboot Android. NOT shut down, then boot to wm, and then run haret.
In All the builds I've tried, the reboot menus all dont work. Most reboot meuns make the phone shut down.
I'm using a polaris, running Android in the sd card, and seems dont have a recovery mode.
I found sometimes Android stucks and reboots itself when I push the volume button to adjust the system volume. It is a DIRECTLY reboot, not reboots into wm.
So I think there is some way to reboot directly. Hope sb. can find it out.
Hello,
I need some help. Install its Android OS, but after he reset my Kaiser again charged WinMo OS. My question is whether it is possible to choose which OS to load first or with any program or edit the file to indicate to launch the first Android.
Sorry for my bad english :S Use Google translator
If you have installed Android to SD card and use Haret.exe then it will always reboot to WM.
You must install to nand if you wish to boot to Android only, which will wipe WM totally and replace it with Android.
The guide stickied at the top of the forum is a good tutorial in doing this
That does bring a good point to my mind though, we could create an exe that loads at startup of wm to auto load haret and startup if the user doesn't cancel in so many seconds (like grub). I keep WM on my phone so I can easily change my droid version and also I know everything works including opening office files (actually that's the biggest sticking point for me keeping it).
Thanks for support. Today I try to flash via NAND method.
Kind Regards
Lybomir
I flash my Kaiser with latest zImage-2.6.32-froyo-09-09-10_21 from here http://it029000.massey.ac.nz/vogue/files/?C=M;O=D and my device loading Android OS very slow, and big problem is : Phone go in screensaver and I try to unlock and screeen stay only in white light, no picture, no widgets... total block. Only solution is it a use Soft reset button or remove batery
Maybe you choose the wrong panel type?
I can read in your signature Duo Boot so I guess you installed onto the SD and use Haret to run Android.
If so, you have to edit the default.txt file locate in ANDBOOT folder and modify the value following htckaiser.panel_type.
You can specify 1, 2 or 3 (most Kaisers use panel type 2)
Wrong panel type may lead to awake problems or wrong colors...
The excessive slowness may be due to a slow SD. Which class is it? Use at least class 4 SD.
---- EDIT -----
In case you already flashed to NAND, to change the panel type you have to choose the right kernel (the kaisimg file) or you can edit the one you flashed following instructions and links you can find in #4 at http://forum.xda-developers.com/showthread.php?t=680518
obviously you have to reflash the kaisimg.nbh but you don't need to flash Android again
I try with 1,2 and 3 but every time show me a this problem, and now i run HaRET and in 2 from 3 times phone block and not response only Soft reset work, and if case phone load complete Android and again in screen seaver system not respond... ;(
I flash my phone with ext2 partition on my sd card/ class 4 8 GB SDHC/ and try with system and data on sdcard an again freez white screen/
Sorry for my bad english
dlink.bg said:
I try with 1,2 and 3 but every time show me a this problem, and now i run HaRET and in 2 from 3 times phone block and not response only Soft reset work, and if case phone load complete Android and again in screen seaver system not respond... ;(
I flash my phone with ext2 partition on my sd card/ class 4 8 GB SDHC/ and try with system and data on sdcard an again freez white screen/
Sorry for my bad english
Click to expand...
Click to collapse
May you try to install a different build and see if you fall into the same problem?
BTW, just after installing, don't start playing soon with the device: initially skip all settings (touch the android, don't set google account and so on) and leave the phone quiet for at least 10-15 minutes: some builds need to copy file to the cache and playing with the device may interfere with this operation leading to unpredictable effects...
Let we know...
It is slow because you installed it on sdcard.. both partition.. if you are on nand. Try install both partition on nand partition.. and try hawks soad rls 3 as me.. its fastest build for kaiser.. and I haven't ever problem with white screen ata awake.. try it in that haws soad ion build.. you can finf it in that forun.. just find it
Sent from my HTC Kaiser Ion using XDA App
I find a solution! Later I post how find solution
Thanks on every in this thread to help me!
dlink.bg said:
I find a solution! Later I post how find solution
Thanks on every in this thread to help me!
Click to expand...
Click to collapse
You're welcome
And I'm waiting to know
Don't suppose any of you have actually seen this thread?
Gen.Y DualBOOT v1.0.6.0
Should work fine on Kaiser, certainly works fine on other devices, such as Diamond, Blackstone etc
zenity said:
Don't suppose any of you have actually seen this thread?
Gen.Y DualBOOT v1.0.6.0
Should work fine on Kaiser, certainly works fine on other devices, such as Diamond, Blackstone etc
Click to expand...
Click to collapse
Hi Zenity... Yes, know that piece of software.
But as You have to boot WinMo (Yes, I Know, not all the services need to be running but system must be loaded and started, GUI must be running and so on) in order to DualBOOT can start, I can guess it's only a partial time-save... isn't it? Did You tried it?
Have not tried it on my Kaiser, since it is Nand flashed, but I think it is what was being asked for really, a way to boot either WM, or straight into Android on SD.
I don't think it will ever be possible for both WM and Android to co-exist on nand, since there simply is not enough room on the internal memory for both.
It is a time saver on other devices I have tried it on, Diamond, Blackstone, however since neither of these devices is nand-flashable this is more what Gen-Y's dual boot was intended for.
If it was possible to run WM from SD then we might be able to truly Dual Boot, in a similar fashion to Windows/Linux on PC, but as far as I know this is not possible either.
zenity said:
Have not tried it on my Kaiser, since it is Nand flashed, but I think it is what was being asked for really, a way to boot either WM, or straight into Android on SD.
I don't think it will ever be possible for both WM and Android to co-exist on nand, since there simply is not enough room on the internal memory for both.
It is a time saver on other devices I have tried it on, Diamond, Blackstone, however since neither of these devices is nand-flashable this is more what Gen-Y's dual boot was intended for.
If it was possible to run WM from SD then we might be able to truly Dual Boot, in a similar fashion to Windows/Linux on PC, but as far as I know this is not possible either.
Click to expand...
Click to collapse
Yes, of course we haven't enough NAND to have both OSes!!!
What I was thinking to (but I'm a lot far to inspect WinMo booting sequence...) is if may be possible to wedge a sort of bootloader running BEFORE the OS loads or in the early booting process and letting we choose to boot WinMo (in NAND) of Android (on SD).
At present moment I've Android running from SD but kernel NANDed (I've got problems running out of NAND and no time to solve them so I'm using the solid build previously installed on SD) so Kaiser boots quickly... and this confirms it's possible boot SD Android without having to load WinMo or Haret. The more relevant matter I can see is that we have to find a way to wedge the bootloader without have to manual modify the WinMo ROM (virtualization is far from be considered on such devices...)
I suppose this is just a "mind exercise" (Sorry, I don't know how to correctly translate an Italian common saying...
Mind exercise describes it perfectly
Not sure why you would run out of space on nand, unless you are loading a lot of apps, and there are ways to run android that may help with that, such as apps2sd, or data on SD partition.
If you must have WM then your only choice would be using Haret.exe, and the most efficient way to dual boot we have at the moment is the Gen-Y solution, which is not ideal, but does offer at least part of what you seek.
The Android bootloader we use (tinboot.s) is not flexible enough to allow dual booting, but may have some information that may be of some use in this
tinboot thread
See what you think anyway
Sorry, I was not able to be clear... I apologize for my English...
When I said "I've got problems running out of NAND" I intended to say "I've got problems - very bad performances - when Android was running from NAND"!!!
Maybe we are a bit OT...
BTW, I was far from software developing for a long while and never developed low level software for Linux/Unix... but in the past I messed up with Z80, 65xx, 68K and x86 platforms's assembly
Recently I need to approach software developing again (but at a really different level...)
I'd like to have spare time to start again, as this world attracts me more. Maybe I'll give it a chance...
Let me understand... tinboot is actually used bootloader?
BTW, just to be clear... I don't need WinMo and I'm giving Android a chance to revive my Kaiser. I'm looking for a fast and stable build and actually I'm running VaniljEclair RLS11 (Yes, I know, I'd try your Polymod 2.1D build... )
Tinboot is the bootloader we use to get android in nand, not being a coder my understanding in limited, however I did think that thread may have useful information for anyone interested in the low level workings of out devices.
I assumed you meant running out of space on nand, lol, i see now what you mean, no need to apologise for you english, it's fine
zenity said:
--- CUT ----
however I did think that thread may have useful information for anyone interested in the low level workings of out devices.
Click to expand...
Click to collapse
And you're right... it's a useful starting point and I'll read it accurately...
Unluckly, I need a lot of spare time (and I don't, at present) to build a solid knowledge base and to start developing for Android.
yes there should be plenty of room for both oses on Nand, I still have over 90 mb on my wm6.5 nand install with come extra apps in there. So if you stripped down both oses you could easily fit them both on nand and still some space left. But then you need to have a boot loader that will be able to load both oses. I think I heard someone say somewhere they are using grub to boot android from nand, that can boot windows also with the right configuration, that would be where to start.
This is a complete package just unzip folder on sd card.
Here is original thread by neopeek
people having wifi problems check the original thread they have a fix
This is the CWM 1.9 thread wich is included in folder already
Using starfox test kernel from XDA (Rhodium only)
EDIT: per starfox dont use test kernels use his new vanilla stable kernel
GAPPS already included.
Im not a dev, just put stuff together credit goes to all authors just posting here to spread the word
DOWNLOAD
Sure, I'll bite. I've got an extra micro-sd card here. What's the worst that could happen?
It's a pretty fast build, I tried it on Neopeeks site.
It is MDPI, so the look of it isn't quite as crisp... (you can see what I mean by the notification bar 3g, etc...lower resolution basically) but I was impressed by the speed. All the animations, etc are disabled by default and I believe that's Zeam that is the default launcher... it is quite snappy out of the box.
what tweaks you did?
no tweaks just put it together
This version is the fastest thing I've tried (probably due to mdpi-gapps), but I have two major issues.
1) Wifi will sometimes refuse to turn on, saying wifi error on the check box. It must be related to tethering and hotspot settings, because after I mess with these I get an instant reboot.
2) Camera is tremendously unstable. Most of the times it crashes bringing down the entire OS or if I am lucky it will crash the camera app and refuse to start again until a reboot.
Of course there are random hiccups here and there (like most builds), but it is quite close replacing WM for every day usage.
XavierGr said:
1) Wifi will sometimes refuse to turn on, saying wifi error on the check box. It must be related to tethering and hotspot settings, because after I mess with these I get an instant reboot.
Click to expand...
Click to collapse
This is actually not that unusual... I would get this on my epic4g... which is an android phone .
If you don't mind, please use the vanilla kernel that I posted instead of the testing kernel. While I don't mind that it is being bundled, the [Test] kernel was never meant to be used for long term, and is liable to include stuff that is unstable and/or changed on my whim. The vanilla kernel contains some of the tweaks that I consider to be stable and is based on known autobuild releases+supports all devices. Thanks.
http://forum.xda-developers.com/showthread.php?t=1221499
-- Starfox
you think you can make a build with the latest rootfs, starfox's latest kernel, the led patches too?
anish88 said:
you think you can make a build with the latest rootfs, starfox's latest kernel, the led patches too?
Click to expand...
Click to collapse
There's nothing stopping you from doing that.
Including testing stuff into a public build is never a good idea. I wouldn't appreciate anything I distribute for testing to be put into a build. It's meant for testing, so anyone that installs/uses it should know full well what they're getting into. Placing it into a build circumvents that, and everyone ends up using it unknowingly.
To everybody with wi-fi issue:
I've done a small fix
http://www.multiupload.com/7NSGZQZXPC
(wich is in the first post of this thread on neopeek.com)
This will fix if your problem isn't the kernel
wifi scanning problem:
after updating wifi-nvram seems to be ok.
anyway,
fastest rom i have tried.
nekikekec said:
wifi scanning problem:
after updating wifi-nvram seems to be ok.
anyway,
fastest rom i have tried.
Click to expand...
Click to collapse
What problem did you have exactly and what do you mean by updating wifi-nvram?
I also have a wifi problem specifically with this build but can't solve it.
(Wifi works only once per boot)
after turning wifi on phone started scanning for networks. after few seconds app crashed not finding anything. i guess there is a problem with assigning mac address.
anyway, as already described, it is known problem :
here
nekikekec said:
after turning wifi on phone started scanning for networks. after few seconds app crashed not finding anything. i guess there is a problem with assigning mac address.
anyway, as already described, it is known problem :
here
Click to expand...
Click to collapse
That didn't work for me at all.
Can't get CWM working
Hey guys,
I must be doing something wrong, but don't know what.
I just can't get CWM running on my TP2. I followed all the instructions precisely, got into CWM once, even flashed the ROM from SD card, but can't do it again.
I even reflashed my device, Re did the entire SD card but just can't get in to CWM.
Upon booting Haret, I press volume down, but the screen just gets stuck there and doesn't move forward. Please help, I'm trying to flash NeoFroyo 0.1
Regards,
Nilesh
nileshvedi said:
Hey guys,
I must be doing something wrong, but don't know what.
I just can't get CWM running on my TP2. I followed all the instructions precisely, got into CWM once, even flashed the ROM from SD card, but can't do it again.
I even reflashed my device, Re did the entire SD card but just can't get in to CWM.
Upon booting Haret, I press volume down, but the screen just gets stuck there and doesn't move forward. Please help, I'm trying to flash NeoFroyo 0.1
Regards,
Nilesh
Click to expand...
Click to collapse
Did you set all your partitions as primary?
vzihome said:
Did you set all your partitions as primary?
Click to expand...
Click to collapse
Yes I did that too....
SD Card (All Partitions Primary)
Partition 1: 6.4 GB - FAT32
Partition 2: System - 300 MB - EXT2
Partition 1: Data - 300 MB - EXT2
Partition 1: Cache - 300 MB - EXT2
I put the npkboot folder with startup for RHOD100 on the SD Card (Root) and the NeoFroyo Zip also on the root.
Plus, I also put the contents of the npkboot folder on root of the phone. (Not the folder npkboot)
Run Haret from SD Card through File Explorer & press Volume Down - Result: Frozen Screen!!!
Does not enter into CWM recovery...
Are all the steps above right.
Regards,
nileshvedi said:
Plus, I also put the contents of the npkboot folder on root of the phone. (Not the folder npkboot)
Click to expand...
Click to collapse
WHY?
CWM rootfs works only in npkboot.
nileshvedi said:
Plus, I also put the contents of the npkboot folder on root of the phone. (Not the folder npkboot)
Click to expand...
Click to collapse
I'm a little confused with what you did.
Basically just unzip his folder you downloaded and then move the Entire npkboot folder to the root of ur sd card.
So there will be nothing on your sd card except the folder. Inside that folder will be everything just as you unzipped it. So for example haret would be at "Sdcard/npkboot/haret.exe". Then just switch/edit the startup.txt in the npkboot folder for your phone and boot into CWM.
You don't need to move anything outside of his npkboot folder that you unzipped.
was wondering if anyone had any thoughts on doing a Multiboot system for android kind of like the one for the Defy (here) where you boot into a rom that is a secondary bootloader with the option to either run the Nand Rom or run from an image on the SD card that simulates your Nand. would be nice to test ROMS on Devices without having to reflash to internal all the time for app and rom devs and Serial flashers alike.
i would possibly take on this task myself but every time i try to mess with code it frustrates me and makes me want to break the comp or the phone lol.been that way for years just dont have that nack or patience :fingers-crossed:
yes i would be willing to test the rom loader Rom as long as it is not a RUU i do have knowledge of linux file structure and know how to use some things in command line (can follow instructions well lol).
Not enough memory on the wfs for a double boot.
i know it doesn't have enough memory to dual boot from internal bu that is why i was suggesting a way to boot from either internal OR from IMG on SD card. like in the link i posted for the defy. maybe a recovery mod or maybe a secondary boot loader you flash like a rom that loads before everything and lets you decide where to boot from. that also would give a sandbox mode that you could mess with things and if you mess it up you can just reboot from internal and have a full working system
new thought. maybe an app that chroots a rom on top of your install. would still let you test rom in something like an on device sandbox
there is a way of doing it by using the recovery partition for the boot image you will need to have too extra partitions on your sdcard and to edit the mount points to boot the system etc from the sdcard.
hmmm. a multiboot/recovery now that sounds like an idea. hmmmmm would definateley be willing to test.