i have installed android 2.3.3 but i found so many futures not working
so i decided to install ver2.2, i tried to get the boot menu again when do restart
but it continue to the system, i installed MAGLDR113 instead of MAGLDR111, but still ignoring enter the boot menu
please i need help>>> what i can do to reinstall another ver?
umm,are you running a NAND or SD build?.Did you change the Boot Settings in MAGLDR so that it always boot into MAGLDR?. If you have done all that, and you still experience the problems, you should falsh HSPL,Radio and MAGLDR again, This might also solve the buggy 2.3.3 build. May i also ask what Android build are you running(link?). Have you updated your build to the latest version or the newer versions?
Related
I installed MCCM GB V2.0 Gingerbread HoneyComb Sense theme [kernel tytung_r5] and for the beginning everything worked fine. But after installing some apps and rebooting, the phone app gave robotic sound and asked for force closure. I tried to reinstall, reboot several times but same problem exists. I formatted sd card with SDFormatter 2.0 completely. Still prb exists. What am I doing wrong or is this a general problem everyone having? HD2 details as follows: WM 6.5 Build 1.66, Radio 2.10.8, HSPL 2.08. I would very grateful if someone could help me out with this prb.
How did u flash your ROM ?
Did u use CWM or DFT method ?
muzap2000 said:
I installed MCCM GB V2.0 Gingerbread HoneyComb Sense theme [kernel tytung_r5] and for the beginning everything worked fine. But after installing some apps and rebooting, the phone app gave robotic sound and asked for force closure. I tried to reinstall, reboot several times but same problem exists. I formatted sd card with SDFormatter 2.0 completely. Still prb exists. What am I doing wrong or is this a general problem everyone having? HD2 details as follows: WM 6.5 Build 1.66, Radio 2.10.8, HSPL 2.08. I would very grateful if someone could help me out with this prb.
Click to expand...
Click to collapse
No, I just flashed it to sd. and another problem with my phone is I cannot flash anything radio, wm custom, etc. when i start to flash anything via active sync, RUUCustom starts bootloader on the phone, shows the progress bar (bar stays at 0% always) and it stays for approx. 2-3 minutes and gives an error "connection error" and goes to recovery stage. I remeber last time I just falshed HSPL. That's it. Since that time I can't flash anything like radio, magldr etc. That's why I flashed android to sd by just copying android folder to sd and running clrcad.exe and haret.exe. I'm a novice and don't understand much. But I have general idea. If anyone can help me to sort out above problems, I would be very grateful.
Got the same problem with that build. I heard that it's caused by some sort of memory problems, Anyway I didn't found the solution.
Could be left over data from previous build, delete data of the apps that keep crashing.(Dialer, Dialer storage), reboot, try again.
I have been running android on my HD2 all year and have never had any major problems until today.
I am currently running Typhoon CM7 v3.4.1 but I am interested in giving Hyperdroid CM7 another try. Every time I flash it I am either missing the phone app or I get a message about GApps stopping unexpectedly. I have tried both v2.1.0 and v2.0.1, I then tried MIUI.us 1.7.1 and had the same problem, no phone app installed.
I have done task29, re downloading roms, transferring them onto the phone using different methods, tried different versions of CWM (v3.0.0.5 & v3.2.0.0) and I have also tried flashing a WM6.5 rom and then coming back to Android and nothing helps.
I have also tried clean install without restoring data and with restoring data.
I have a backup of my current Typhoon v.3.4.1 and I can restore this and everything works fine.
Does anyone have any other ideas?
I'm not sure what else to try.
thanks.
Edit: If I log into my Google account straight after a fresh install on hyperdroid I get an error about acore stopping. If I don't log in straight away everything works until I log in and then I get an error about gapps framework stopping.
Edit: I managed to downgrade to Typhoon 3.4.0 while keeping user data. Can't successfully flash any other rom. I guess I will have to stick with this rom. Not such a bad thing, just need to get over my flashing addiction.
I have now tried to format the sd card which didn't help
I tried to flash a stock wm6.5 rom with the stock SPL but I couldn't get it to flash using the sd card method.
I tried clk instead of magldr and every time I get the same issue with the gapps framework.
Does anyone have any ideas?
I am guessing that there might be some corrupted data on the nand but I don't know how to check.
Hello everyone,
I've been looking for a solution for a couple of days now and just can't figure out what i'm doing wrong.
this is my first cLK flash and everything went without any problems, wiped everything, partioned SD-card, flashed ROM. - and everything looked great but i did not realize that I didn't have to enter my PIN, and I had no service either, after a reflash, that problem was fixed but WIFI wont turn on, it gets stuck on "activating"
I hope someone can help me, this ROM looks awesome i'd hate not being able to use it.
thank in advance, pi
Problem solved,
finally found a solution by seadersn
"you can use this cLK 1.4.0.1 120-5 layout. btw: 120-44 or any layout with bigger cache is not needed and therefore recommended, due to initrd.gz was designed. it's all located @ /data-partition, so bigger cache = less userdata in any case. " - http://forum.xda-developers.com/showthread.php?p=17326365&highlight=wifi+150+120#post17326365
Thanks
Hello,
I have also problems with Wi-Fi on my HTC HD2. If i press the Wi-Fi button it says enabling but it stucks..
I tried this update but it didn't work..
What to do?
Thanks..
I had the same issue when I installed 3.0.0 + 3.0.1 Hotfix.
With "installed" I mean, i used "install update package from sdcard" in CWM to update from 2.0.1.
abd shell and cat /proc/kmsg showed some problems when loading the driver module for WiFi, when i clicked "turn on WiFi".
My solution was, to update the whole toolchain:
I restarted with a full wipe, updated to cLK 1.4 (before: 1.3.3) and CWM 4.0.0.0 (before: 3.0.something) together with a fresh repartitioning, all via "HD2 Toolkit" (http://forum.xda-developers.com/showthread.php?t=1090783)
I know, it is a bit cumbersome, because you have a fresh install and need to reinstall several apps and so on...
I've been using Quarx's CyanogenMod 11.0 (KitKat 4.4.2) since its January 20 release. However, my phone starting to become slow with the time (nothing related to the build but the extensive device use & data exchanging). Today i decided to upgrade to most recent build (NIGHTLY 23/03). Of course i wiped everything before. I installed the build directly from TWRP with no big problems, however, i disliked this "new"? recovery interface (this one that shows two options (RECOVERY) and (ANDROID) and this "Press search to load the system" thing. I Would like to disable it and return to the old M logo, where i had the blue led to warn me about the recovery thing. Is this possible? I mean, take this thing out?
Now the most important. As i said, i've been on the development thread since the beginning, but i didn't found any working answer to my situation. After trying both GAPPS 4.4.2, i see a black screen on first boot with the Standard GAPPS and only a "Choose your laguage" with Minimal, after chosen i get a "Launcher stopped working".I cant add the google account without the GAPPS, as some peoples suggested to another on that topic. I remember that i read something related to install the previous working build (20/01) and then upgrade to the newer, after setting the account on the older build. But theres no january 20 on quarxs ftp, what now? HELP PLS
System + data + cache wipe, use core gapps 2-26. If you encounter issues, then again install rom after full wipe, but don't install gapps immediately. Reboot, and delete unwanted system apps to free up space, and then flash gapps and wipe cache
No easy way to backport safestrap (replacement for boot menu)
Sent from my MB526 using Tapatalk
johnaddams83 said:
I've been using Quarx's CyanogenMod 11.0 (KitKat 4.4.2) since its January 20 release. However, my phone starting to become slow with the time (nothing related to the build but the extensive device use & data exchanging). Today i decided to upgrade to most recent build (NIGHTLY 23/03). Of course i wiped everything before. I installed the build directly from TWRP with no big problems, however, i disliked this "new"? recovery interface (this one that shows two options (RECOVERY) and (ANDROID) and this "Press search to load the system" thing. I Would like to disable it and return to the old M logo, where i had the blue led to warn me about the recovery thing. Is this possible? I mean, take this thing out?
Now the most important. As i said, i've been on the development thread since the beginning, but i didn't found any working answer to my situation. After trying both GAPPS 4.4.2, i see a black screen on first boot with the Standard GAPPS and only a "Choose your laguage" with Minimal, after chosen i get a "Launcher stopped working".I cant add the google account without the GAPPS, as some peoples suggested to another on that topic. I remember that i read something related to install the previous working build (20/01) and then upgrade to the newer, after setting the account on the older build. But theres no january 20 on quarxs ftp, what now? HELP PLS
Click to expand...
Click to collapse
do not use standard gapps..system partition not big enough to store standard gapps..install core gapps
Pls help me out guys, im just a newbie. So i flashed the latest nightly CM12.1 and when it booted up, system UI has stopped appeared and i cant get rid of it. I think i didn't re-enable android debugging before flashing it. Is there any way i can enable android debugging before i flash the rom and gapps again? Pls help me out guys. I think i broke my phone.
You don't need to enable debugging, its just that latest cm12.1 build is broken, I just reflashed myself because of that systemui crash, you need to reflash too. You can use version with date 2015-04-16, and then update from the phone using cm integrated updater to version 2015-05-11, because version 2015-05-13 is broken.
Same thing happened to me this morning after I flashed the Nightly of 2015-05-13. I downloaded the Nightly with CyanDelta to reduce the download size and flashed in thorough recovery. After my device booted, I noticed my wallpaper changed and I kept getting "Unfortunately, SystemUI has stopped" error. But it kept showing up every 1-2 seconds making the device unusable. So I just flashed the Nightly of 2015-05-12 which was working and the error stopped showing. Thanks to CyanDelta that keeps a copy of the old Nightly after installing a new one.
I hope that you still have the "stable" Nightly on your device to roll back to the previous Nightly. If you have access to a computer, you might be able to download it directly from CM's website, transfer it thorough USB and flash it with Recovery. That would be the only solution I can come up with beside restoring a NANdroid Backup. But I'm no pro in Android stuff, maybe someone can come up with another solution.
ExcaliburUser said:
Pls help me out guys, im just a newbie. So i flashed the latest nightly CM12.1 and when it booted up, system UI has stopped appeared and i cant get rid of it. I think i didn't re-enable android debugging before flashing it. Is there any way i can enable android debugging before i flash the rom and gapps again? Pls help me out guys. I think i broke my phone.
Click to expand...
Click to collapse
Thanks for the info bro. :good: