Some details:
HD2 512.
Typhoon 3.5.6.
MAGLDR 1.13.
Recovery 4.0.0.0.
Some things I know:
CM7 takes a while to load anyway.
I believe having lots of media (I have 7GB MP3's) can lengthen boot times. (~Theory is crapped all over with my SGS2 but some people have mentioned this fact).
The problem here is not at the loading stage where the bootanim kicks in, it's the stage before with the static logo after GO GO GO.
My SGS2 literally loads and is ready to use in 10 seconds to OS and 30 seconds to functionality after media scan/widgets etc.
So what's my HD2 doing at the static logo screen? It basically doubles the entire loading time but from my little knowledge, nothing actually happens until the bootanimation? I don't like waiting up to 2 minutes to be using my phone.
I hear CLK has a faster boot option. In anyone's opinion, have they sorted data out enough to come away from MAGLDR?
Thanks in anticipation of any responses.
dkl_uk said:
Some details:
HD2 512.
Typhoon 3.5.6.
MAGLDR 1.13.
Recovery 4.0.0.0.
Some things I know:
CM7 takes a while to load anyway.
I believe having lots of media (I have 7GB MP3's) can lengthen boot times. (~Theory is crapped all over with my SGS2 but some people have mentioned this fact).
The problem here is not at the loading stage where the bootanim kicks in, it's the stage before with the static logo after GO GO GO.
My SGS2 literally loads and is ready to use in 10 seconds to OS and 30 seconds to functionality after media scan/widgets etc.
So what's my HD2 doing at the static logo screen? It basically doubles the entire loading time but from my little knowledge, nothing actually happens until the bootanimation? I don't like waiting up to 2 minutes to be using my phone.
I hear CLK has a faster boot option. In anyone's opinion, have they sorted data out enough to come away from MAGLDR?
Thanks in anticipation of any responses.
Click to expand...
Click to collapse
Don't remember stuck with GO GO GO for long in my Mag days. I am now on cLK, and from the second boot onward, my phone is usable within 45 seconds - this is with a lot of apps, most of with run all the time right from boot.
I am using MAGLDR with Tytung's Nexus HD2 v2.9 build and it takes about 45-50 seconds to load. Much faster than when I was using Cmylxgo's TMOUS Froyo build which took a little over 2 minutes to load for comparison.
ph03n!x said:
Don't remember stuck with GO GO GO for long in my Mag days. I am now on cLK, and from the second boot onward, my phone is usable within 45 seconds - this is with a lot of apps, most of with run all the time right from boot.
Click to expand...
Click to collapse
It's not stuck at GO GO GO, it's stuck at the static boot image for a while, then the animated boot logo begins. Maybe it's the fact the phone looks like it's doing nothing while it's showing the static boot logo but like I mentioned above the SGS has the same amount of media and also it has the same apps as the HD2 and it's usable in under 30 seconds.
Thanks for the response anyway.
dkl_uk said:
It's not stuck at GO GO GO, it's stuck at the static boot image for a while, then the animated boot logo begins. Maybe it's the fact the phone looks like it's doing nothing while it's showing the static boot logo but like I mentioned above the SGS has the same amount of media and also it has the same apps as the HD2 and it's usable in under 30 seconds.
Thanks for the response anyway.
Click to expand...
Click to collapse
If you want to experiment, try Tytung's Mag kernel - get it from his thread and flash it. Mind you, ensure it also has the wifi drivers (bcm4329.ko), else wifi may not work. In my experience, Tytung's implementation of his Kernel boot faster.
Also, CWM 4.0.0.0 is not supposed to be stable (has something with backup/ recovery). Get the latest, or go with 3.2.0.0
I had the same problem when I was using that rom.
I tried to find the prob using logcat, and I saw a lot of errors being thrown at me, and also quite a few a2sd zipalign's, so I removed a2sd scripts from init.d, it started booting faster; but I still had the other errors.
ph03n!x said:
If you want to experiment, try Tytung's Mag kernel - get it from his thread and flash it. Mind you, ensure it also has the wifi drivers (bcm4329.ko), else wifi may not work. In my experience, Tytung's implementation of his Kernel boot faster.
Also, CWM 4.0.0.0 is not supposed to be stable (has something with backup/ recovery). Get the latest, or go with 3.2.0.0
Click to expand...
Click to collapse
Thanks for the heads up. I obtained that version of CWM through the HD2 Toolkit, and so far I haven't had any issues using it for the last few months.
Assuming I find the Kernel you've pointed me to, would it not be in CWM flashable mode and therefore i'd just be overwriting the zImage and not actually flashing a new ROM - therefore keeping my current /system (and bcm4329.ko)? Apologies if that was literally the most noob statement you've ever seen.
Moon2 said:
I had the same problem when I was using that rom.
I tried to find the prob using logcat, and I saw a lot of errors being thrown at me, and also quite a few a2sd zipalign's, so I removed a2sd scripts from init.d, it started booting faster; but I still had the other errors.
Click to expand...
Click to collapse
I actually have live logcat bootanimation and I am pretty sure i've seen a lot of errors too. It goes too fast to debug anything, and i've not taken the next step which is of course to do what you did and actually read the logcat, but these errors take milliseconds during the boot phase and I don't believe it's this bit that is the issue - it's the bit where the static logo shows and I don't truly know what the phone is doing at that stage.
Thanks for your helps also guys
dkl_uk said:
Thanks for the heads up. I obtained that version of CWM through the HD2 Toolkit, and so far I haven't had any issues using it for the last few months.
Assuming I find the Kernel you've pointed me to, would it not be in CWM flashable mode and therefore i'd just be overwriting the zImage and not actually flashing a new ROM - therefore keeping my current /system (and bcm4329.ko)? Apologies if that was literally the most noob statement you've ever seen.
Click to expand...
Click to collapse
The Mag and the cLK version of the kernel are here- use the one that says 2.3.4 only, even if you or on 2.3.5
I use this in cLK, and know for sure that the required Wifi drivers are in it. Note that the cLK version has cedesmith's data wrapper b5, but the b4 wrapper works better for me. This is in case you choose cLK, and are having data issues after flashing the kernel.
http://forum.xda-developers.com/showpost.php?p=10429937&postcount=3
ph03n!x said:
The Mag and the cLK version of the kernel are here- use the one that says 2.3.4 only, even if you or on 2.3.5
I use this in cLK, and know for sure that the required Wifi drivers are in it. Note that the cLK version has cedesmith's data wrapper b5, but the b4 wrapper works better for me. This is in case you choose cLK, and are having data issues after flashing the kernel.
http://forum.xda-developers.com/showpost.php?p=10429937&postcount=3
Click to expand...
Click to collapse
That's literally the post I came across once I did a search based on what you'd already told me. Thanks for confirming further.
Timed my boot - was 35secs on the watch and 33secs according to logcat. To put things in perspective, I have trillian (5 accounts), gtalk, gmail, 3 email accounts, google+, current widget, CallRecorder, CSipSimple, ClockSync, DSP Manager, Easy Filter, Swype and Where's My Droid loading at boot - in addition to whatever Android loads (Maps, Calendar, Settings...)
dkl_uk said:
Thanks for the heads up. I obtained that version of CWM through the HD2 Toolkit, and so far I haven't had any issues using it for the last few months.
Assuming I find the Kernel you've pointed me to, would it not be in CWM flashable mode and therefore i'd just be overwriting the zImage and not actually flashing a new ROM - therefore keeping my current /system (and bcm4329.ko)? Apologies if that was literally the most noob statement you've ever seen.
I actually have live logcat bootanimation and I am pretty sure i've seen a lot of errors too. It goes too fast to debug anything, and i've not taken the next step which is of course to do what you did and actually read the logcat, but these errors take milliseconds during the boot phase and I don't believe it's this bit that is the issue - it's the bit where the static logo shows and I don't truly know what the phone is doing at that stage.
Thanks for your helps also guys
Click to expand...
Click to collapse
You have to use the following command to get logcat to make a file of it.
adb logcat > anyfilename.txt
ph03n!x said:
Timed my boot - was 35secs on the watch and 33secs according to logcat. To put things in perspective, I have trillian (5 accounts), gtalk, gmail, 3 email accounts, google+, current widget, CallRecorder, CSipSimple, ClockSync, DSP Manager, Easy Filter, Swype and Where's My Droid loading at boot - in addition to whatever Android loads (Maps, Calendar, Settings...)
Click to expand...
Click to collapse
At what point are you timing this boot from? Power on? GO GO GO? Splash screen?
If I were to time my boot from the animated boot screen then i'd say possibly 30 seconds too, it's just that for another 30 seconds it's sat on the static boot animation.
Also my launcher screen takes an awful amount of time to parse. You can definitely tell the HD2 is ageing when you compare it with the SGS2. I know it's in a class of its own but still, i'm beginning to lose faith in the longevity of my HD2.
I am on the same boat, I use aMAGLDR 1.13 + MIUI Rom and the boot process is very very slow.
I just timed it:
1. From T-mobile Stick together to go go go: 9 secs.
2. A static splash screen, black background and green HTC logo: 1min 52 secs.
3. From MIUI globe animation kicked in to locked screen: 29 secs.
So basically I have no idea why step 2 takes such a long time. Is there anyway to see any error msg during this stage?
I tried to remove SIM card and/or SD card, it is about the same, so I guess there is something happening in the NAND...
Thanks!
Related
I need help with the HD2 jumping to kernel i have tried different builds and roms and nothing fixes it!
I have this crap as well. Have tried startup files..etc, nothing seems to help.
I'm using the latest Energy cookie rom and the newest (TMOUS) radio as well.
I have to re-boot like 2-3 times before I get past the 'Jumping to kernel...'
If someone knows whats causing this and how to avoid it, let us know.
I cant even install it ive tried everything ive found on here with no luck.
Having same issue here.. havent even managed to boot once.
Always stuck at "Jumping to Kernel"
Tried reading as much as i can, renaming startup.txt .. booting as fast as winmo opens or waiting... nothing.
Please if some1 can help it would be much appreciated..
Thanks
same problem here. I just got my hd2 and have been using froyosense v2 pretty much with no problems until this morning when I tried booting android. I'm going to tried formatting later on when I have some time.
formatting my sd card didn't help, i still had the same issue. i wasn't using any loaders so i decided to install one. i installed this one mskip_Android_Loader_V4.1.cab and used the option to soft reset and boot android and now i was able to boot into android.
[edit]
btw, here's where i got it from [APP] Android Loader v4.1 for HD2
Thanks ill be sure to try that out and see how it works.
I've been using the bootloader as well for some time now and still get the 'Jumping to kernel...' on/off. Its unpredictable..sometimes it'll boot 2-3 times in a row no issues, other times It would freeze once, other times it would freeze twice in a row...
I'm lost just as much as all of you.
I'm using a T-Mobile HD2 / HSPL 3 / Radio 2.12.50.2 / Energy Cookie ROM / Bangsters Android v1.2a
Ya that bootloader didnt do the trick. I still havent even gotten it to boot one time!
Edit:Just found somethin. When i tried to boot it told me kernel relocated to 0x11808000 which i noticed was different from the startup text line
"set ramaddr 0x11800000"
So I changed that to "ramaddr 0x11808000" and i got it to boot past the kernel thing but it eventually just rebooted the phone.
I think there is one more edit to the line
"set ramsize 0x1e400000" that will make it work ill try to figure it out.
i've been using android exclusively, but i noticed that if i don't boot into android quickly right after a reset i get stuck in the jumping to kernel. from what i've read this what supposedly fixed in the latest kernel. i'm now using mattc 1.7 as is, not sure if maybe i should've upgraded something, but i'm fine with having to boot into android quickly.
Erk3452 said:
Ya that bootloader didnt do the trick. I still havent even gotten it to boot one time!
Edit:Just found somethin. When i tried to boot it told me kernel relocated to 0x11808000 which i noticed was different from the startup text line
"set ramaddr 0x11800000"
So I changed that to "ramaddr 0x11808000" and i got it to boot past the kernel thing but it eventually just rebooted the phone.
I think there is one more edit to the line
"set ramsize 0x1e400000" that will make it work ill try to figure it out.
Click to expand...
Click to collapse
wolfpack612 said:
i've been using android exclusively, but i noticed that if i don't boot into android quickly right after a reset i get stuck in the jumping to kernel. from what i've read this what supposedly fixed in the latest kernel. i'm now using mattc 1.7 as is, not sure if maybe i should've upgraded something, but i'm fine with having to boot into android quickly.
Click to expand...
Click to collapse
Correct. Every time I want to boot into Android, I usually do it on a fresh Windows boot. If I've been using Windows for some time, I usually do a reboot and then immediately load Android; since I've been doing this, never had the recurrence of 'jumping to kernel...'
I have resolved the problem using only the latest version of official rom by HTC without HSPL or anything else
Have had Android working and booting fine for the week, battery went flat last night , now android wont boot, goes to the grnn HTC icon n then stops, I have waited half an hour still with nothing, as ive said its not the first time its been booted. I have searched on here but they all seem to be new installs that are having problems. Any idea ?
TommyHD2 said:
Have had Android working and booting fine for the week, battery went flat last night , now android wont boot, goes to the grnn HTC icon n then stops, I have waited half an hour still with nothing, as ive said its not the first time its been booted. I have searched on here but they all seem to be new installs that are having problems. Any idea ?
Click to expand...
Click to collapse
I am getting same issue. Android was very nice, fast boot and so on. But since tomorrow, when booting to Android it stays on startup screen with green htc.
TommyHD2 said:
Have had Android working and booting fine for the week, battery went flat last night , now android wont boot, goes to the grnn HTC icon n then stops, I have waited half an hour still with nothing, as ive said its not the first time its been booted. I have searched on here but they all seem to be new installs that are having problems. Any idea ?
Click to expand...
Click to collapse
Sounds like possible data corruption if system did not shutoff gracefully. Not a good idea to let low battery shut off system... you should shut it off manually. I have had this happen on WM where the phone get into a weird state and data get corrupted.
I would backup the data.img file, let Android create a new one to see if it boots properly. Then restore the original data.img file and see if it boots with that one.
hidnface said:
I am getting same issue. Android was very nice, fast boot and so on. But since tomorrow, when booting to Android it stays on startup screen with green htc.
Click to expand...
Click to collapse
Which build are you using?
Same Here!
Battery went flat, tried booting android a few times but didnt succeed. So rebooted the phone to find..
The android boot screen repeats itself. Over and over. Was fine yesterday.
Going to try backing up the data.img and restoring it after it rebuilds as mentioned above.
UPDATE :
After backing up the data.img file, and letting it rebuild, one hour later, still not booted.. So restarted the phone, put the old data.img back, started up haret.exe, and its now stuck on the Green HTC logo.. and isnt moving.. at all.
This isnt my first boot.. usually it boots within a couple of minutes.
jmmmmm said:
Which build are you using?
Click to expand...
Click to collapse
Latest Android build. FroyoStone version3.2
Android not rebooting after flat battery
Hi TommyHD2,
I have just had the same problem, actually a couple of times. What I did was to delete all the new entries that had been made on my micro SD card and only leaving the original 8 files that are in the FroyoStone 3.2.7z Android folder and of course I did not delete the media folder that is also included in the build. Well twice now I have done this with a successful reboot of Android whilst not losing any of the settings that I had made ie. Wallpaper, shortcuts etc even apps (unless they are on the card).....Obviously this will now be a case of trial and error to establish which of the deleted files it is that cause a conflict in the reboot. I am also new to this but reading this someone may be able to idntify the problem easily. Other than that it runs superb....EVERYTHING works....well battery drain but I think that is even solved now thanks to XDA.....I will let you know in about four hours
Good luck
HTC HD2
Radio - 2.15.50
FroyoStone 3.2.7z
scirroco said:
................
FroyoStone 3.2.7z
Click to expand...
Click to collapse
.7z is the file extension (like .rar, .zip, .doc) and not the version.
Froyostone version confusion
HI Hidnface,
I don't know what sort of smile that is ....sarcastic or friendly but thanks all the same. Bit dumb of me but then I am still learning.
By the way I found that when you boot into Anroid you are left with a folder calle Android_Secure....I dont know what thois does but this is the one I delete to enable successful reboot.
Thanks mate.
have you guys tryed doing a logcat of it booting? whats it erroring at? is it looping?
search adb logcat. android is verry easy to debug since you can watch processes in a comand line...
hi all, just got my hands on a htc hd2 and iv loaded [BUILD][19.12.10]-=MDJ FroYo HD v.4.6=-[FRG83D][kernel:MDJ S8.0] onto it no problem, got it running great, only thing is when i switch the phone off and back on it loads windows mobile again, then i have to run the android files again and let it install itself again, in the mean time losing all my settings, iv read theres a way to autoboot android on startup but cant really find anything about it, is this possible, and if so could someone run me through how to do it, wouldnt mind if it was just to reboot the android firmware, but when im losing all my settings and apps its no good, any help on this much appreciated as im still a newbie really to this phone.
When you boot up android from SD card, the first boot usually takes 10-15 minutes (varies from build to build). During this first startup, a new file in your android folder is created called 'data.img'. This is the file which your android build uses to store all the settings/apps/customisation etc.
When you restart your phone, before you boot into android, look in your android folder for 'data.img'. If it is missing then the android startup will take 10-15 minutes again, but if it is present it should only take 2-3 minutes. If it takes 10-15 minutes every time then you probably want to re-download the build and try again.
Also, dual-booting options are available, but check to see if this works first.
Sent from my HTC HD2 using XDA App
thanks mate, i noticed when i reloaded it again after switching off that my settings and apps were still there, which is good, but now id like to be able to boot straight into android, is that at all possible, im sure i read something earlier about it, but i cant find it again, would be cracking if i could load android on boot up!
big-hol said:
thanks mate, i noticed when i reloaded it again after switching off that my settings and apps were still there, which is good, but now id like to be able to boot straight into android, is that at all possible, im sure i read something earlier about it, but i cant find it again, would be cracking if i could load android on boot up!
Click to expand...
Click to collapse
here's how to boot android from the start:
http://forum.xda-developers.com/showthread.php?t=893948
dan138zig said:
here's how to boot android from the start:
http://forum.xda-developers.com/showthread.php?t=893948
Click to expand...
Click to collapse
cheers mate i'll have a look at that, i'll report back soon!
okay
i have the same problem
Mc-Checker said:
i have the same problem
Click to expand...
Click to collapse
try installing MAGLDR, it deletes WinMo en it has the option to install Android and WP7 in NAND, and it can load Android from SD
http://forum.xda-developers.com/showthread.php?t=893948
But the best of all: it has Tetris included
Ok I'm having some trouble getting American Android installed. I downloaded the android folder and transferred it to the sd card folder on my phone I then ran the clrcad followed by the haret and it looks like its going well but then it stays stuck in a grey screen that says "Powered by AmeriCan Android". How do I fix this?
On my phone, I just pulled battery and started over. 1st boot is usually longer. My problem is trying to get nand going.
Ok but did you get the grey screen of death like I mentioned above?
Master099 said:
Ok but did you get the grey screen of death like I mentioned above?
Click to expand...
Click to collapse
It's not SOD, it's just custom replacement of the first boot logo (normally it's green HTC on black background) done by ACA team. dabza is right - pull the battery and start over, if it does not help try again or search the ACA thread for clues.
Also - be aware that depending on your card speed, the first boot can take up to 15 minutes (maybe longer).
Anyway, good choice, it's a great ROM, hope it works for you.
p107r0 said:
It's not SOD, it's just custom replacement of the first boot logo (normally it's green HTC on black background) done by ACA team. dabza is right - pull the battery and start over, if it does not help try again or search the ACA thread for clues.
Also - be aware that depending on your card speed, the first boot can take up to 15 minutes (maybe longer).
Anyway, good choice, it's a great ROM, hope it works for you.
Click to expand...
Click to collapse
I second that. took me about 25 minutes on first boot.
was also having same prob,try this.
while in winmo file explorer look for fle on sd card called ANDROID .delete it,then try try clrcad and then haret..works for me..
Master099 said:
Ok I'm having some trouble getting American Android installed. I downloaded the android folder and transferred it to the sd card folder on my phone I then ran the clrcad followed by the haret and it looks like its going well but then it stays stuck in a grey screen that says "Powered by AmeriCan Android". How do I fix this?
Click to expand...
Click to collapse
It's not stuck. First boot always takes 15+ minutes while it builds a 1gb data.img file, all subsequent boots are much faster.
Just put the phone down and come back in 20 minutes.
NAND is very simple, easiest approach will be to get all the files u need before doing anything, u need like 6 files
Radio ROM
MAGLADR
Clockwork Rec MOD
some toehr file that manipulated ur ROM size
actually rom.........5 files
its worth it, my HD2 isawesome with the Nexus rom on it
abdalla21 said:
NAND is very simple, easiest approach will be to get all the files u need before doing anything, u need like 6 files
Radio ROM
MAGLADR
Clockwork Rec MOD
some toehr file that manipulated ur ROM size
actually rom.........5 files
its worth it, my HD2 isawesome with the Nexus rom on it
Click to expand...
Click to collapse
Honestly ACA on SD is better than any nand build I've used. It's really a great ROM
Sent from my HTC HD2 using XDA App
Master099 said:
Ok I'm having some trouble getting American Android installed. I downloaded the android folder and transferred it to the sd card folder on my phone I then ran the clrcad followed by the haret and it looks like its going well but then it stays stuck in a grey screen that says "Powered by AmeriCan Android". How do I fix this?
Click to expand...
Click to collapse
first i try ACA also stuck on Powered by AmeriCan Android.
after that , i formatted sd card with sd panasonic formatter and everything run smoothly.
I stayed now for 35 mins with no response.
me 45 minuutes and still grey screen nothing more.. COOL!
Master099 said:
Ok I'm having some trouble getting American Android installed. I downloaded the android folder and transferred it to the sd card folder on my phone I then ran the clrcad followed by the haret and it looks like its going well but then it stays stuck in a grey screen that says "Powered by AmeriCan Android". How do I fix this?
Click to expand...
Click to collapse
My problem is my mobile stuck after grey screen, it was working fine till tonight after automatic updating some of my application which it regular updating my phone went off and when i restart it after grey screen android sign keep flashing and nothing happens after that, i am running gingerbread 2.3.7, i have done soft reset but not works for me any suggestion from you guys
Did anyone get a fix for this? I have been trying to install but it just gets stuck on the grey screen. I have tried with a 8gb and 16gb....first 2 times I let it sit for 3hrs and nothing, 3rd time I left it over night woke up this morning and still nothing.
@lalabrowneyes Any more than half an hour means it almost certainly won't boot. Give us some more information. What ROM are you on? Radio version? Do other builds work? Etc.
Sent from my HTC HD2 using XDA
Sorry I forgot to add all that stuff....
Rom Elegancia CHT2 V 2.0
Radio 2.15.50.14
Android build that I have been using since last yr is one from MCCM..... I have tried to install others Nexus HD2, Boxmax runny HTC but when I press haret I get this message " failure to load file android etc....
UPDATE
I got it to work and everything seems to be working fine...... but I'm trying to download Instagram and I just get Your device is not compatible
Hi guys!
I took a HD2 by a friend that have installed Cyano on it, but sometimes it freeze and i have to remove the battery, so i tried some other ROMs installing CWM and flashing ROMs by the recovery.
Now I have these problems: a lot of times MAGLDR stucks after loading the ROM when says GO GO GO.
When the system could load it freeze after some using, sometimes after 5 min sometimes after 5 hrs.
The CWM I installed is 400MB, it's good for this ROM [Jan 10/01/2015][KK 4.4.4][ LiquidSmooth][Official] Kernel 3.0.101 [ION]? Or it could be this the problem?
I tried many times to start from the beginning of the porting process (HSPL, task29, MAGLDR, recovery, ROM), but nothing, it doesn't work..
Thank you for help!!
(Sorry for my bad english)
beast33 said:
Hi guys!
I took a HD2 by a friend that have installed Cyano on it, but sometimes it freeze and i have to remove the battery, so i tried some other ROMs installing CWM and flashing ROMs by the recovery.
Now I have these problems: a lot of times MAGLDR stucks after loading the ROM when says GO GO GO.
When the system could load it freeze after some using, sometimes after 5 min sometimes after 5 hrs.
The CWM I installed is 400MB, it's good for this ROM [Jan 10/01/2015][KK 4.4.4][ LiquidSmooth][Official] Kernel 3.0.101 [ION]? Or it could be this the problem?
I tried many times to start from the beginning of the porting process (HSPL, task29, MAGLDR, recovery, ROM), but nothing, it doesn't work..
Thank you for help!!
(Sorry for my bad english)
Click to expand...
Click to collapse
try using a system partition of 380 MB , also try to change recovery to ext4
EvilMegaDroid said:
try using a system partition of 380 MB , also try to change recovery to ext4
Click to expand...
Click to collapse
To use a 380 mb recovery can I change the space value from 400 to 380 in flash.cfg?
What do you mean with try to change recovery to ext4? I made a partition on my SD about 2GB ext4..
Thank you!
beast33 said:
To use a 380 mb recovery can I change the space value from 400 to 380 in flash.cfg?
What do you mean with try to change recovery to ext4? I made a partition on my SD about 2GB ext4..
Thank you!
Click to expand...
Click to collapse
hmm yes you can do that , about the recovery grab a SD version of ext4 and run it from sdcard as a second recovery to try it out , or you can download a nand version and replace it with recovery.img
EvilMegaDroid said:
hmm yes you can do that , about the recovery grab a SD version of ext4 and run it from sdcard as a second recovery to try it out , or you can download a nand version and replace it with recovery.img
Click to expand...
Click to collapse
Hi, I've tried your suggestions and it worked for one day and a half, then it freeze again. And after, when i managed to turn the device on after a lot of time it's stucks on GO GO GO, it freeze again after android lockscreen or a bit after, once one time it worked but without sim. It could be the SIM the problem? It is a 4g sim, but i think not.
Thank's you a lot!
hmm well i don't think its a sim problem , why don't you try to install the rom in nativesd and see if it works that way , check the nativesd instructions for more info how to do it
good point about nativeSD, it would eliminate nand bad blocks from the equation.
beast33, try getting a dmesg;
when stuck on magldr gogogo, push the red reset button under battery cover (don't pull battery)
go to magdr 10 services > dmesg to sd
on your sdcard look for file dmesg.txt and post it here.
to see if you have bad blocks and where they are.
Robbie P said:
good point about nativeSD, it would eliminate nand bad blocks from the equation.
beast33, try getting a dmesg;
when stuck on magldr gogogo, push the red reset button under battery cover (don't pull battery)
go to magdr 10 services > dmesg to sd
on your sdcard look for file dmesg.txt and post it here.
to see if you have bad blocks and where they are.
Click to expand...
Click to collapse
With nativeSD it's normal that the boot is longer than nand?
Now it seems working, it freeze only one time, but it stucks on GOGOGO more times than nand...
Attached there is the dmesg.txt file when the phone boot normally, I post the file also when it stucks on GOGOGO to see the difference.
Thank's a lot because this phone is very good even though is quite old and i love to use it like principal device!!
EDIT 04.02.15
Yesterday night i tried to stree a little the device and while installing WA it freeze and doesn't boot anymore, it always stucks on GOGOGO... I don't know what to do anymore, it's possibly that something inside is brocken?
Another little question: wich light and fast rom do you suggest for a every day use (possibly with italian language)?
END EDIT
beast33 said:
With nativeSD it's normal that the boot is longer than nand?
Now it seems working, it freeze only one time, but it stucks on GOGOGO more times than nand...
Attached there is the dmesg.txt file when the phone boot normally, I post the file also when it stucks on GOGOGO to see the difference.
Thank's a lot because this phone is very good even though is quite old and i love to use it like principal device!!
EDIT 04.02.15
Yesterday night i tried to stree a little the device and while installing WA it freeze and doesn't boot anymore, it always stucks on GOGOGO... I don't know what to do anymore, it's possibly that something inside is brocken?
Another little question: wich light and fast rom do you suggest for a every day use (possibly with italian language)?
END EDIT
Click to expand...
Click to collapse
I can't see any attachments
It does not sound good for the phone, but let us see what the dmesg(s) tell us.:fingers-crossed:
Sorry I forgot to post it
This is when the phone boot normally, when it freeze and not boot i post the other one!
It's normal that now with NativeSD the phone seems a lot slower than nand? (SD class 10)
beast33 said:
Sorry I forgot to post it
This is when the phone boot normally, when it freeze and not boot i post the other one!
Click to expand...
Click to collapse
No worries.
That one didn't work. It sometimes happens, especially if there was a long delay between pressing the reset button and getting the dmesg. Good luck with getting another one.
Robbie P said:
No worries.
That one didn't work. It sometimes happens, especially if there was a long delay between pressing the reset button and getting the dmesg. Good luck with getting another one.
Click to expand...
Click to collapse
This one work?
It's normal that now with nativeSD the phone is a lot slower than nand?
well it depends on what rom your using and also sdcard class , for example a class 10 sdcard is way faster than a class 4 sdcard , also what do you mean by slow , UI lag ? if that it happens to me too and maybe (i don't really know) its cuz your acessing data on the sdcard in the same time
beast33 said:
This one work?
It's normal that now with nativeSD the phone is a lot slower than nand?
Click to expand...
Click to collapse
It is better, I can see it is -pixelfreak-'s compiled 3.0.101 kernel, so assume the rom is liquidsmooth KK, but the dmesg stops before the nand bad blocks are listed (if there are any). I can't see anything causing reboots, others may know better. Try again
Robbie P said:
It is better, I can see it is -pixelfreak-'s compiled 3.0.101 kernel, so assume the rom is liquidsmooth KK, but the dmesg stops before the nand bad blocks are listed (if there are any). I can't see anything causing reboots, others may know better. Try again
Click to expand...
Click to collapse
Yes the rom is Liquidsmooth, do you suggest another lighter?
I can make dmseg also when the system boot normally? Or only when it stucks on GOGOGO?
Thank you for your patience!
beast33 said:
Yes the rom is Liquidsmooth, do you suggest another lighter?
I can make dmseg also when the system boot normally? Or only when it stucks on GOGOGO?
Thank you for your patience!
Click to expand...
Click to collapse
a dmesg after normal boot should show your nand bad blocks, if any, so would be good.
a dmesg immediately after it gets stuck on gogogo might show why it gets stuck, so would be good too
Robbie P said:
a dmesg after normal boot should show your nand bad blocks, if any, so would be good.
a dmesg immediately after it gets stuck on gogogo might show why it gets stuck, so would be good too
Click to expand...
Click to collapse
A little question: to make the dmesg after normal boot i have to boot magldr, make dmseg and then boot nativesd, right?
beast33 said:
A little question: to make the dmesg after normal boot i have to boot magldr, make dmseg and then boot nativesd, right?
Click to expand...
Click to collapse
Only difference is after a normal boot, you don't need to use the reset button, just switch off normally, then get your dmesg (dmesg to sd).
reset button gets you out of the hanging bit without removing battery, and thus the dmesg is still in memory when you use magldr to put it on the sdcard.
Not sure why you need to boot nativeSD after you put the dmesg onto sdcard, unless you are using usb to get the dmesg.txt onto pc and therefore onto xda, or are posting it using android via tapatalk. Note that unless you rename dmesg.txt, it will be overwritten the next time you put a dmesg to sd.
Robbie P said:
Only difference is after a normal boot, you don't need to use the reset button, just switch off normally, then get your dmesg (dmesg to sd).
reset button gets you out of the hanging bit without removing battery, and thus the dmesg is still in memory when you use magldr to put it on the sdcard.
Not sure why you need to boot nativeSD after you put the dmesg onto sdcard, unless you are using usb to get the dmesg.txt onto pc and therefore onto xda, or are posting it using android via tapatalk. Note that unless you rename dmesg.txt, it will be overwritten the next time you put a dmesg to sd.
Click to expand...
Click to collapse
This dmesg is after stuck on GOGOGO i hope it could help!