Related
Hello!
Ive got a problem aftter flashing a *.nbh for NAND android :/ It just hanged on the splash screen. No any linux logs
If you can still get bootloader, try reflashing, sometimes it fails for no apparent reason, if that still does not work, try formatting the SD, recopy the nbh, reflash again.
If all else fails, you may be one of those who cannot flash to nand, I have 2 kais130's one flashes every time, the other, about 1 in 15 times is successful.
zenity said:
If you can still get bootloader, try reflashing, sometimes it fails for no apparent reason, if that still does not work, try formatting the SD, recopy the nbh, reflash again.
If all else fails, you may be one of those who cannot flash to nand, I have 2 kais130's one flashes every time, the other, about 1 in 15 times is successful.
Click to expand...
Click to collapse
I can still get bootloader, a reflashed, today i putted new SDHC card and i try to reflash nbh. Only 1 time after flash I can see linux logs, I can to install it too, but when ill reboot phone then hangs like early :/
Ok first which Android build are you trying?
When you say reboot, are you using the reset button or pulling the battery after flashing, ( using reset can cause problems, the correct method is flash, pull battery, wait, replace battery ).
Which nbh are you trying to flash? If you had android working then you may want to go back to the nbh you used before.
zenity said:
Ok first which Android build are you trying?
When you say reboot, are you using the reset button or pulling the battery after flashing, ( using reset can cause problems, the correct method is flash, pull battery, wait, replace battery ).
Which nbh are you trying to flash? If you had android working then you may want to go back to the nbh you used before.
Click to expand...
Click to collapse
Im using kaisimg-panel1-428-12-03-10, im using a reset button not battery trick. Im using warm donut biuld. As I said i can boot android from NAND just 1 time, not anymore
Well the best nbh's for the kaiser are still the sourceforge ones at least for stability, the 20/02/2010 ones, yes there are newer ones, but they may require some pretty advanced editing of some system files before they run properly, and may not be fully compatible with the donut build.
I think it may be better to use one of these : http://sourceforge.net/projects/androidhtc/files/2010-02-20/kaisereclair/
I have the same issue with dzos latest. I posted it in the bluetooth thread as to not open any unneeded topics. The fix he posted 11-03-10 for bluetooth booted fine, this one gives me the same issue. Remember this stuff is all relatively experimental so try not to panic when using the very latest since it might not work.
Apparently there is a problem with the latest nbh's, I'd just reflash an earlier NBH, this should fix the problem.
I'm having the exact same problem. Everything seems to get installed properly but once I take out the battery to reboot it just hangs on the splash screen. I've tried several builds and reformatted the card several times... always the same result. In one of the posts I cam across it was mentioned that you first have to go in to win mobile to turn off a pin # and that can cause the system to hang if not done. I can't find the post anymore and I'm not sure what they were talking about.
kcbronc said:
I'm having the exact same problem. Everything seems to get installed properly but once I take out the battery to reboot it just hangs on the splash screen. I've tried several builds and reformatted the card several times... always the same result. In one of the posts I cam across it was mentioned that you first have to go in to win mobile to turn off a pin # and that can cause the system to hang if not done. I can't find the post anymore and I'm not sure what they were talking about.
Click to expand...
Click to collapse
Yeah I read about disabling the pin thing in Win Mo as well, but unfortunately this was after I flashed Android to NAND. Mine hangs at the splash screen as well, but if you put the KAISDIAG.nbh file in the root of your SD card, from the Hard SPL threads, the phone will boot and get to the Android installer, but will then come up with errors when choosing to install to NAND. Unfortunately, I can't even go back to Win Mo because of this.
Mods please close these thread
clemsyn said:
OK, this is from l1q1d latest 2.6.32 (10-29) and merged with dream kernel by ezterry. I used HTC Android kitchen by dsixda and with help from scooter, got me an nbh from a zimage file.
I installed my ROM with this kernel and then installed iGO, ran some GPS and wifi, restarted about 30 times (clean shutdown) and yaffs stayed intact. Reset the device 5 times after each reboot..First, second, third reset was good...Fourth reset gave me a Google Framework error..Fifth reset gave me yaffs error....Anyone interested can try it and let me know how it works in your Kaiser. BTW, edit the Kaisimg.nbh depending on your device.
I recommend acayoeme or scooters ROM.
Click to expand...
Click to collapse
Thanks for the recommendation, I will give the kernel a try with my build to personally test it and see if I can figure out a way to keep it stable enough.
aceoyame said:
Thanks for the recommendation, I will give the kernel a try with my build to personally test it and see if I can figure out a way to keep it stable enough.
Click to expand...
Click to collapse
Ur welcome, thanks for trying out my kernel My friend is currently testing out this kernel with my ROM but since your ROMs are optimized for 2.6.32, I think it's best that this kernel be tested with your roms
Yeah I just downloaded it and just copied it to the phone, will let you know how it goes.
NAND did not work with the nbh for me. SD worked though, going to test further. With NAND it just hung at the android part of the nbh and in the install menu it did not detect the NAND in it. I have a TILT with display type 2 if that narrows down perhaps a difference in the NAND that there could be.
aceoyame said:
NAND did not work with the nbh for me. SD worked though, going to test further. With NAND it just hung at the android part of the nbh and in the install menu it did not detect the NAND in it. I have a TILT with display type 2 if that narrows down perhaps a difference in the NAND that there could be.
Click to expand...
Click to collapse
I'm pretty sure he had a type 2 Tilt too. I'll ask him.
Yes, he does have a Tilt type 2
Hmm thats odd, also I noticed it seems like I can't overclock to 570 mhz with the kernel so far, seems like its a little less tolerable to cpu instabilities. Other than that though all features seem to be working and 6+ reboots later with both on SD I haven't seen any corruption yet.
aceoyame said:
Hmm thats odd, also I noticed it seems like I can't overclock to 570 mhz with the kernel so far, seems like its a little less tolerable to cpu instabilities. Other than that though all features seem to be working and 6+ reboots later with both on SD I haven't seen any corruption yet.
Click to expand...
Click to collapse
It was pretty snappy at 400 mhz...so we never did overclock and kept it at default speed. Just wondering why it won't install nand for you while we did not have any issues in his tilt.
Has anyone on a vogue or kaiser or anything else tried this yet?
I just tried NAND again and the error is a umount error, it seems like it tries to format with the wrong parameters, it gives an invalid argument error.
err seems like it is trying to unmount properly so it cant format it.
Looked a little closer at the error and it is actually saying it cannot find a flash device and that is why the sub sequent umounts are failing.
OK, got a hold of my friends Tilt...I am currently installing your Build..I'll post the dmesg and boot messages...somehow it installs with no issues on this Tilt both system and data on NAND. Currently on bootanimation.
OK booted fine...here are the files
BTW, very nice build Very fast..cant find the reason to overclock with this combo in NAND
I can't possibly think of why it isn't finding the NAND on mine. I am going to try reloading winmo and then re-loading the nbh fresh tomorrow. Thank you for the compliments, I overclock mine so high just because I have a hunger for speed, trying to make it as fast as I can, to compete with the dream and be faster even if possible.
Works fine with NAND. No problem detected yet.
Clean installation on NAND/NAND seems to install and boot just fine on a tilt screen 2
Grandelama said:
Clean installation on NAND/NAND seems to install and boot just fine on a tilt screen 2
Click to expand...
Click to collapse
Thanks for trying it...LMK how it goes for you eg. stability, adb, SD removal and insertion while running etc..
I will just install it and see how it goes. Looks good
Installed, and so far so good using scooters cyanomod. Did a boot-reboot-boot-reboot-boot-reboot stress test, and so far no yaffs errors, and no data corruption. This is using a tilt with panel 3. I'll run it for a few days and keep you posted.
matcha20 said:
Installed, and so far so good using scooters cyanomod. Did a boot-reboot-boot-reboot-boot-reboot stress test, and so far no yaffs errors, and no data corruption. This is using a tilt with panel 3. I'll run it for a few days and keep you posted.
Click to expand...
Click to collapse
I appreciate you guys trying it...I suggest you no overclocking since it is very sensitive to overclocks
I have tried this kernel today with "Scoot CyanogenMod RLS4" and "Galaxy S for AndroidonHTC 11/1" which is based on Fresh Froyo. After the setup with both builds I installed a few apps and then I made an normal reboot (switch off, switch on again). Then I got the same error with both builds:
init: untracked pid xxx
And then the phone is in a loop and does not boot. Seems, that there are yaffs errors with this kernel after the reboot?
So I think this error belongs to the kernel and not the build because these are both different builds. My installation was system and data on nand and not overclocked. Maybe someone can help?
I'm sorry that this thread is here again, still unsolved.
But I would really want to use my phone again. I've got nothing ATM.
What I've tried already:
- Every radio version wich can be downloaded for the Kaiser
- 2.6.32 and 2.6.25 Kernel - Latest 2.6.32 kernel with reboot fixes from Clamsyn
- Diffrent Android Builds like 'Fat Free Froyo', 'Not So Super Froyo', 'CM6.1 Gingerbread', 'Clemsyn's Final Froyo' and so on.
- Wi-Fi fixes
- Re-re-re-re-re-installing Android
- Re-re-re-re-re-flashing kernels and radios
The problem explained:
When using any radio/kernel/build my phone reboots every time my Wi-Fi is on.
At first when Android is freshly installed there are no problems at ass when using Wi-Fi, but after a while it starts to reboot as long as the Wi-Fi is on.
The Wi-Fi is on, I've got about 1 à 2 minutes before the phone reboots. After the reboot, the Wi-Fi restores his state from before the reboot. Now i've got about 30 seconds before it reboots again to turn off the Wi-Fi
VIDEO (CHEAP QUALITY):
http://www.youtube.com/watch?v=AlZMqB1evUE
If there's any more info on my mind I'll post it.
Hope someone's got a fix or solution for this.
Thanks
I had a similar problem, with WIFI and DATA connection, that I solved with:
this kernel http://forum.xda-developers.com/showpost.php?p=9768617&postcount=63
ROM: Scoot CyanogenMod 6.1 RLS5a
radio: 1.65.16.25
I suggest data on SD card partition for extra stability.
Millence said:
I had a similar problem, with WIFI and DATA connection, that I solved with:
this kernel http://forum.xda-developers.com/showpost.php?p=9768617&postcount=63
ROM: Scoot CyanogenMod 6.1 RLS5a
radio: 1.65.16.25
I suggest data on SD card partition for extra stability.
Click to expand...
Click to collapse
Thanks
I'll try that and let something know...
I can't seem to find out how to get the data on sdcardpartition...
i'm getting:
Could not determine filesystem size
Failed
Failed to format
blablabla
unmount: can't unmount /data: invalid argument
EDIT: Could be that i did the partition thing wrong. Trying another way ATM
EDIT: Nope doesn't work...
meh i suck
Install everything on NAND just to see if this combination works for you.
It takes a while until it starts to reboot.
Installing right now so... hoping...
Thanks a lot for even taking your time to help me
When this doesn't fix the problem I'm going to upload a small vid showing what it does. So it's easier to understand the problem. Android booted. Now install some apps and reboot and try to make it reboot again
I had a similar problem in the past.
I solved it with a complete install from the htc factory standard windows mobile rom including the radio. After the complete setup and the reboot after the setup you can try to install another radio and the android kernel and rom again.
This solved my problem. And I use the latest 1.71.09.01 radio and I have no problems with it.
Maybe this helps you.
mt1976 said:
I had a similar problem in the past.
I solved it with a complete install from the htc factory standard windows mobile rom including the radio. After the complete setup and the reboot after the setup you can try to install another radio and the android kernel and rom again.
This solved my problem. And I use the latest 1.71.09.01 radio and I have no problems with it.
Maybe this helps you.
Click to expand...
Click to collapse
I'ma try that as well. The problem now is: I have 0.00kb total memory and 0.00kb free so... can't install anything
wich radio?
EDIT: or does it come with the rom downloaded from htc website?
What's this thing I keep getting? Like I said in the previous posts, with the Failed, Failed to format
Never had that before lol'd :/
Still no luck. Keeps rebooting :/
Any other ideas???
If you have hard spl installed, then the installation ist really easy. Open the offical "Kaiser_HTC_ASIA_HK_WWE_3.34.721.2.exe" with 7zip and extract the RUU_signed.nbh to the root of your sd card. Then rename it in KAISIMG.nbh.
Manual for flashing:
http://forum.xda-developers.com/showthread.php?t=433835
---> Flashing Via MicroSD Card
Try it. And I think that you have to make the complete htc first setup process with reboot. My problems were gone after I made this complete setup with the standard htc rom. After that my kaiser was working well. So I installed another radio, kernel and android rom and all was working well after this.
Nope sorry, Tried that yesterday, Still rebooting.
I'm going to post a video wich shows it. Crappy Quality. Shot with my Nokia 3500c so... kind of... yeah...
Video will be posted in a couple of minutes
Uploaded
For anyone interested.
Hope this ever gets fixed
http://www.youtube.com/user/Syntax1993?feature=mhum
syntax1993 said:
Uploaded
For anyone interested.
Hope this ever gets fixed
http://www.youtube.com/user/Syntax1993?feature=mhum
Click to expand...
Click to collapse
Did you use BusyBox update that is in the particular thread? I found out, that it fu*ks up everything... messes the keyboard, breaks stability...
I am not using it anymore. Instead I put my apps to the androidinstall.tar file to avoid using newly installed app and it seems to be quite stable for me...
Nope no busybox used :s really ****ed up problem
srry for the language
i did have various probs with sd cards not recognised and failed to format on install.
even trying full format on win 7 and xp didnt help.
i used an sd formater from http://www.sdcard.org/consumers/formatter_3/ and select Full Erase On Format size adjustment on.
then, as if by magic ;-) , android installed. worth a try?
Trying that right now...
Thank you btw
If that works I just need to fix the Wi-Fi problem :s
Hi Everybody!
I have been using Android on my Tytn2 for a while now, but every couple of days the data gets curroupted or loss (install is on Nand). Can anyone advise if there is a stable kernal out there yet that dosnt have the data curruption issues? I dont mind the phone being slightly slower, I just dont want to keep re-installing everything every couple of days. I have tried clemsyn's kernel on #63 and the kernal downloaded by aTools so far...
I would install to the SD card but for some reason my phone keeps ejecting the SD card whenever data is written to it
thanks in advance!
Unfortunately, all of the kernels suffer from the data corruption on the NAND chip. So far the only one that doesn't have this issue is the 2.6.25 kernel, but it's so out dated now that most builds being released now barely work with that kernel. When using the 2.6.32.9 Kernel, we recommend /system on NAND and /data on SD Card partition or data.img.
Most kernels are still using the EXT2 file system setup for the sd card installations, but if you check out my kernel in my signature, it does the EXT4 file system for sd card installation which has proved to be slightly faster.
There are certain builds out there that have an issue with the SD Card mounting. Recommend either using a build by clemsyn or aceoyame which have the fixed SD Card mounting issues.
Hope this helps.
I have used quite a few ROMs, and functionality wise the Froyo ones are great and are also cracking fast, e.g. not so super froyo and scooter's CM6. However, i experienced data loss frequently and as this is my only phone i didn't really want that.
installing sys to nand and data to SD (partition or img) is a good way to stop corruption but even then i managed to corrupt my data.
after reading around a bit it's been said that the Donut builds are most stable and don't get data corrupted, i'm testing this now and fingers crossed it works well.
Thanks for the replys. At the moment, I am using the 2.6.25 kernal and im still getting data loss, is that not normal then? Mayby my Nand chip might be on the way out
If this dosnt work out, Im looking to get a Wildfire - anyone Tytn users had a play with these? Are they any good?
On that note, is there a command I can run in terminal to check the Nand? I have 2 of these phones (one has a broken screen), so I guess I could swap the bits if it is the Nand...
thefatty said:
Thanks for the replys. At the moment, I am using the 2.6.25 kernal and im still getting data loss, is that not normal then? Mayby my Nand chip might be on the way out
If this dosnt work out, Im looking to get a Wildfire - anyone Tytn users had a play with these? Are they any good?
Click to expand...
Click to collapse
Get a better phone. Personally I would go with Hero or Legend or even Motorola/LG equivalents. Wildfire is QVGA and an underdog.
2.6.25 is fully supported with dzo's Fresh Froyo variants provided you install the wifi update after installing kernel on the build. The CM builds require 2.6.32s (including the CM7 build). Correct me if I am wrong.
Hey,
First, I fixed the problem (by going into CWM and re-flashing the ROM) -- I'm opening this thread because I'm interested in understanding what happened and in how the Android system works.
So, this is what I did:
After a successful CM installation, I decided to go into CWM and clear the cache and battery stats. I did both and got permanently stuck in the CM ring afterwards (it spun for over 45 minutes before I shut down).
When I went back into CWM, it informed me that the /cache volume had an ext-4 error and was mounting read-only, so I re-formatted the partition (since it should be like having an ext-4 error in something harmless, like /tmp, on Linux). The error disappeared (was able to mount rw) but I was still stuck in the ring (heh heh heh).
I gave up, ran DarkSideWipe and then reinstalled CM10.1 -- everything's fine.
So, I'm 99.9% sure it wasn't the battery stats that got me caught in a loop. What I'm curious about is why the /cache partition might cause this sort of behavior?
I was on CWM5.-something (I've since updated to 6.0.3.1). Could it have been CWM clobbering /cache in such a way that CM (or, perhaps, any ROM) couldn't write to it anymore? Again, trying to learn Android internals.
Thanks!
Sicily1918 said:
Hey,
First, I fixed the problem (by going into CWM and re-flashing the ROM) -- I'm opening this thread because I'm interested in understanding what happened and in how the Android system works.
So, this is what I did:
After a successful CM installation, I decided to go into CWM and clear the cache and battery stats. I did both and got permanently stuck in the CM ring afterwards (it spun for over 45 minutes before I shut down).
When I went back into CWM, it informed me that the /cache volume had an ext-4 error and was mounting read-only, so I re-formatted the partition (since it should be like having an ext-4 error in something harmless, like /tmp, on Linux). The error disappeared (was able to mount rw) but I was still stuck in the ring (heh heh heh).
I gave up, ran DarkSideWipe and then reinstalled CM10.1 -- everything's fine.
So, I'm 99.9% sure it wasn't the battery stats that got me caught in a loop. What I'm curious about is why the /cache partition might cause this sort of behavior?
I was on CWM5.-something (I've since updated to 6.0.3.1). Could it have been CWM clobbering /cache in such a way that CM (or, perhaps, any ROM) couldn't write to it anymore? Again, trying to learn Android internals.
Thanks!
Click to expand...
Click to collapse
I'm not sure what caused your problem but I do know that you DON'T want to use the dark side scripts with the updated recovery or the 4.2.2 ROMs. TDJ wrote those for ICS and older recovery, they aren't compatible any more. I had to Odin to stock and start all over.
T989D
latest CM10.1 nightly
latest Uber nightly
noob41 said:
I'm not sure what caused your problem but I do know that you DON'T want to use the dark side scripts with the updated recovery or the 4.2.2 ROMs. TDJ wrote those for ICS and older recovery, they aren't compatible any more. I had to Odin to stock and start all over.
Click to expand...
Click to collapse
Wonderful... interestingly enough I had no problems Darking my phone and then running the CM installer... perhaps it's because my CWM was at 5.-whatever instead of 6?
I'll refrain from doing that to my wife's S2 tomorrow, however. I'll just clear the caches.
Thanks!
Sicily1918 said:
Hey,
First, I fixed the problem (by going into CWM and re-flashing the ROM) -- I'm opening this thread because I'm interested in understanding what happened and in how the Android system works.
So, this is what I did:
After a successful CM installation, I decided to go into CWM and clear the cache and battery stats. I did both and got permanently stuck in the CM ring afterwards (it spun for over 45 minutes before I shut down).
When I went back into CWM, it informed me that the /cache volume had an ext-4 error and was mounting read-only, so I re-formatted the partition (since it should be like having an ext-4 error in something harmless, like /tmp, on Linux). The error disappeared (was able to mount rw) but I was still stuck in the ring (heh heh heh).
I gave up, ran DarkSideWipe and then reinstalled CM10.1 -- everything's fine.
So, I'm 99.9% sure it wasn't the battery stats that got me caught in a loop. What I'm curious about is why the /cache partition might cause this sort of behavior?
I was on CWM5.-something (I've since updated to 6.0.3.1). Could it have been CWM clobbering /cache in such a way that CM (or, perhaps, any ROM) couldn't write to it anymore? Again, trying to learn Android internals.
Thanks!
Click to expand...
Click to collapse
Do yourself a favor and go get the latest twrp, its a all around better recovery, and its updated a lot more frequently so it works better with newer roms, with twrp u won't need the wipe scripts anymore here's the link for twrp 2.6
http://techerratta.com/browse/twrp2/hercules
Sent from my SGH-T989 using xda premium