Related
ok, i have a rooted phone, jf 1.42 rc33, hard spl. last week, i upgraded the firmware to the jf mod for the applications on the sd card. it worked for, oh, two-three days, then i changed the theme. after i changed the theme, i restarted the phone (after i restarted once previously and it worked) and it got stuck at the android logo, then would blank out, and go back to the android logo, and just loop itself. so i figured i would redo the whole thing, and i installed the rc33 again, worked completely fine. i installed the theme by itself without installing the modded rc33 for apps on the sd card, and it did it again? so i figured ok, i will try one more time. here's what gets me... installed the rc33 (cleanly, again), then the SD mod, rebooted, it was all fine. i installed a few applications from the market like usual, rebooted out of curiosity, and it did that same thing. i rebooted, and then it just got stuck on the initial boot loader screen (which i edited to my liking). now from here, it seems that i can install the regular jf 1.42 rc33, all is good. i install a theme, all is good. now if i apply the update.zip for the SD mod, and reboot, without installing any applications, it reboots fine the first time. after that, it does that reboot loop thing (correct me what it is? ). now if i redo the system, apply theme, download minimum one app from the market, THEN apply the SD mod, it does that reboot thing right off the bat after i reboot the g1.
so overall, to me, this would be a problem with moving the apps to the SD card? i was thinking something may be causing this to happen, like a bad app from the market. but i noticed it is any app. it also seems that most of the time, the theme is messing up the process? well apparently not, because the last time i tried to mess around with it WITHOUT a theme update, it still did it. i have performed full wipes, then full updates starting out fresh with the jf 1.42 rc33. still no go. seems i cant win at all. if anyone is experiencing anything like this, please help me. i cant do anything i want now. i cant even apply themes without anything messing up.
corp769 said:
ok, i have a rooted phone, jf 1.42 rc33, hard spl. last week, i upgraded the firmware to the jf mod for the applications on the sd card. it worked for, oh, two-three days, then i changed the theme. after i changed the theme, i restarted the phone (after i restarted once previously and it worked) and it got stuck at the android logo, then would blank out, and go back to the android logo, and just loop itself. so i figured i would redo the whole thing, and i installed the rc33 again, worked completely fine. i installed the theme by itself without installing the modded rc33 for apps on the sd card, and it did it again? so i figured ok, i will try one more time. here's what gets me... installed the rc33 (cleanly, again), then the SD mod, rebooted, it was all fine. i installed a few applications from the market like usual, rebooted out of curiosity, and it did that same thing. i rebooted, and then it just got stuck on the initial boot loader screen (which i edited to my liking). now from here, it seems that i can install the regular jf 1.42 rc33, all is good. i install a theme, all is good. now if i apply the update.zip for the SD mod, and reboot, without installing any applications, it reboots fine the first time. after that, it does that reboot loop thing (correct me what it is? ). now if i redo the system, apply theme, download minimum one app from the market, THEN apply the SD mod, it does that reboot thing right off the bat after i reboot the g1.
so overall, to me, this would be a problem with moving the apps to the SD card? i was thinking something may be causing this to happen, like a bad app from the market. but i noticed it is any app. it also seems that most of the time, the theme is messing up the process? well apparently not, because the last time i tried to mess around with it WITHOUT a theme update, it still did it. i have performed full wipes, then full updates starting out fresh with the jf 1.42 rc33. still no go. seems i cant win at all. if anyone is experiencing anything like this, please help me. i cant do anything i want now. i cant even apply themes without anything messing up.
Click to expand...
Click to collapse
Okay... after reading through this briefly you may have either messed up the apps to sd process OR it could be your theme. I use Fadetoblue and don't have any problems. You may want to try removing some of the stock ringtones because once RC33 first came out everyone had a difficult time with themes because of either the compression or they needed the RC33 Lite version. This version is nothing more then the standard RC33 with the stock ringtones and notifications removed.
You can attempt to remove them youself and then try installing your theme.
To do this just use adb shell and remove them. You can also "pull" them first if want to have a backup. In adb shell type "cd /system/media/audio/ringtones". Now you are in the ringtones folder, now type "ls" and then a list of all the ringtones will display. Once you know the name of the one you want to delete just type "rm filename.ogg" and thats it.
You may also need to do a wipe first at nandbackup (alt w) and then do your update.
Bottom line (in order)
-Try to install your theme FIRST. If this is successful then you should have no problems doing apps to sd.
-If you can't... do a wipe and try again.
-If still unsuccessful update to RC33L and try your theme.
I can't think of any reason why any of these won't work.
Btw... if you're phone seems to get stuck at the flashing android LEAVE IT ALONE for a few minutes. Many people get impatient and end up pulling the battery prematurely thinking it got stuck. Sometimes it takes a while after a reboot for all of your changes to take effect. Give it about 5 minutes or so.
If you're having issues with getting your apps to sd then use the tips here.
Keep us updated.
after u update to the sd mod, did u run copy.sh app in the terminal emulator. after doin that update with the theme. no need to wipe. worked for me with carbon glow and grey graffiti theme with no problem
killacoz53... of course i ran the copy.sh script. i only copied the apps tho, not the data. im not trying to go too far with this
and as far as everything else, i just woke up, and i got another 40 minutes before i gotta get ready for work. im gonna try to install the lite version of see if it works. btw, im trying to use the fadetoblue version also....
corp769 said:
killacoz53... of course i ran the copy.sh script. i only copied the apps tho, not the data. im not trying to go too far with this
and as far as everything else, i just woke up, and i got another 40 minutes before i gotta get ready for work. im gonna try to install the lite version of see if it works. btw, im trying to use the fadetoblue version also....
Click to expand...
Click to collapse
Ok. Try to theme it first if you havne't done the apps to sd. We need to know if you can at least put on the theme. If not then it has nothing to do wtih the apps to sd and we can tackle one problem at a time.
I came here only to say, binary100100 you really have a nice avatar, i would be great a G1 wallpaper with it
unrafa said:
I came here only to say, binary100100 you really have a nice avatar, i would be great a G1 wallpaper with it
Click to expand...
Click to collapse
LOL. I just googled a binary avatar and that was one of the first images that came up. I like it too.
ok, i figured i will start all over; i reformatted the micro sd card (4 GB). i gave the ext2 partition only 1 GB, since this is more than plenty for what i am using it for. i did a full wipe, then installed the standard jf 1.42 rc33 firmware. all was good. i then installed the modded sd app firmware (same version) and all is good. i am about to apply the theme right now, BEFORE i run the copy.sh script. i will give you a heads up later on or tomorrow what all happens because i need to get to bed. hopefully whatever i'm doing will fix something. btw, i reformatted the sd card because when i ran the terminal, i noticed that before when i formatted the ext2 partition only, some of the data was still there..... therefore, maybe this had something to do with it? i am guessing it possibly did cause the actual applications were not physically installed on the phone, as i completely redid it.
alright, i pretty much got it. i have no clue whatsoever what the hell happened, maybe you brought me some good luck or something greg, but it looks like everything is good. im running the sd mod with jf 1.42 rc33, and the fade to blue theme installed. after that, i ran the copy script, restarted the phone to make sure, and it worked. on my way to install an app and reboot it, just to make sure. i wont reply until after work later on though, so hopefully it stands up for now
corp769 said:
alright, i pretty much got it. i have no clue whatsoever what the hell happened, maybe you brought me some good luck or something greg, but it looks like everything is good. im running the sd mod with jf 1.42 rc33, and the fade to blue theme installed. after that, i ran the copy script, restarted the phone to make sure, and it worked. on my way to install an app and reboot it, just to make sure. i wont reply until after work later on though, so hopefully it stands up for now
Click to expand...
Click to collapse
Sounds great! Based on my pesonal experience I found it easiest to install the theme first and then the apps to sd. I did have some minor issues with that but I think it was because I was attempting to use paragon though an adapter. as soon as I tried to partition it though the phone everything worked out fine.
i'm sure that everything should be working out for you as long as you were able to successfully install your theme.
advice? nandbackup your device before you make any changes. that way you can simply restore by fastboot should something go wrong.
just out of curiousity... how large was the partition that you tried previously? it is rumored that an ext2 partition has issues with anything over 2gig. but nobody should need that much space... yet.
at first i was trying it with a 1.5 GB partition, now im using a one gig. besides that, two things. last night, phone was all good. i plugged the f*cker in, and when i had to enter the line password thing to get in, it seemed like the touch interface was going crazy. i wasnt even touching it and there was lines going everywhere and nuts and stuff. LOL sounds funny, but i had to wipe the phone and start over again also, i noticed that all the purchased applications in the market (the ones i bought) i couldnt download, they all failed, along with two or three other free applications. the big one was power manager, i cant find the paid version anywhere so if you know anything about any of this, let me know man. my main concern is the system going crazy. i swear only the weird sh*t happens to me.....
ok the apps thing i figured out after doing some research. i was being blocked out. once i got home and hooked up to my wireless box, voila, i was all in like a tongue in.....yea, you get the picture. it works. but im still curious about why my phone went berserk and acted like it got high off some acid or something. lmao... i got a few beers in me, its all good. anyway, if anyone could help troubleshoot that, it would be awesome. and btw, im starting to think of a few programs i could whip up in a few weeks and test out, kinda like a modified bluez stack or something and try to see if i can force send files to my other phone. just a thought i had. im always experimenting with everything.
On every haykuro build that I install, no matter what, it will either get stuck on the G1 screen or android/htc screen during boot after a restart.
I have reflashed my phone to RC29, re rooted, re installed JFRC33, and then tried updating from there 3 times and still I get the same problem.
It is really pissing me off now because it makes no sense that it won't work for me but it does for everyone else.
here is a log of the phone during the hanging G1 screen
http://pastebin.com/f58ba7818
haykuro said it is the new build.prop that is causing my problems but why would it only affect me and no one else?
If anyone has any idea of what is wrong, please suggest what to do.
JUST FYI
Yes, I did wipe before installs
Yes, I have completely reflashed my phone to RC29 and then re-rooted
Yes, I have checked the MD5 sums of all the files I use
It's unbelievable annoying.
Thanks in advance to anyone that can help.
Wait a little linger!
k when flashing to the haykuro builds the first couple time it takes a little to boot. your not waiting long enough. I almost took my battery out to start over again when bam the htc boot screen appeared. Trust me re root your phone from RC29 and add the 5.02h build and you will be all set I promise. you don't have to add Jf 1.42 RC33 build first. Once you get all set then update the radio. Hope I helped!
Well I waited well over 3 hours before and it was still hanging. and the output from the log looks like the build.prop is causing it to crash.. but I don't know why. I have flashed the recovery.img and I know that I am using test keys.
Payne IV said:
On every haykuro build that I install, no matter what, it will either get stuck on the G1 screen or android/htc screen during boot after a restart.
I have reflashed my phone to RC29, re rooted, re installed JFRC33, and then tried updating from there 3 times and still I get the same problem.
It is really pissing me off now because it makes no sense that it won't work for me but it does for everyone else.
here is a log of the phone during the hanging G1 screen
http://pastebin.com/f58ba7818
haykuro said it is the new build.prop that is causing my problems but why would it only affect me and no one else?
If anyone has any idea of what is wrong, please suggest what to do.
JUST FYI
Yes, I did wipe before installs
Yes, I have completely reflashed my phone to RC29 and then re-rooted
Yes, I have checked the MD5 sums of all the files I use
It's unbelievable annoying.
Thanks in advance to anyone that can help.
Click to expand...
Click to collapse
Don't know if this will help but, have you tried completely reformatting your sdcard and trying again, or preferably trying a different card? I have problems flashing when using my 8gb card, yet the 1gb card that came with the phone works fine..
Payne IV said:
On every haykuro build that I install, no matter what, it will either get stuck on the G1 screen or android/htc screen during boot after a restart.
I have reflashed my phone to RC29, re rooted, re installed JFRC33, and then tried updating from there 3 times and still I get the same problem.
It is really pissing me off now because it makes no sense that it won't work for me but it does for everyone else.
here is a log of the phone during the hanging G1 screen
http://pastebin.com/f58ba7818
haykuro said it is the new build.prop that is causing my problems but why would it only affect me and no one else?
If anyone has any idea of what is wrong, please suggest what to do.
JUST FYI
Yes, I did wipe before installs
Yes, I have completely reflashed my phone to RC29 and then re-rooted
Yes, I have checked the MD5 sums of all the files I use
It's unbelievable annoying.
Thanks in advance to anyone that can help.
Click to expand...
Click to collapse
you probly have a low class memory card and they are slow So it may take a while.....like the post above says swich cards and yull be alrite
Well I'm not using apps-to-sd.. would the sd card still affect it? I'm able to install the port fine and set it up, but after it reboots is when it gets stuck on the G1 screen.
yess it would because it is updating the system from the card
I tried again with my freshley formatted 1 GB card that came with the phone and still I get the hanging G1 screen.
I really don't think it has to do with the SD card, I think that it's something else.
bump.. anyonee?
have u updated to the new SPL and radio images that are on his site?
My devphone hangs for me on the Android startup. Now I can't do anything other than fastboot.
Bootloader: 0.95.3000
Baseband: 2.22.19.23
I can't even recover to any of my previously working firmwares because my baseband version isn't 1.22.14.11. I'm stuck!
Fixed the problem with an Alt-W wipe at the recovery console.
Yes I have updated the radio and the SPL but still the problem persists. I did a complete re isntallation of DREAIMG.nbh with the 1 GB card that came with the phone (after I formatted the card) and then rooted, isntalled the modified recovery.img, then I installed 5.0.2 again, and I still got the same result.
I really don't understand.
I really wish someone knew how to fix this I miss those soft keyboards.
I'm not a noob.
Here's the situation.
I was experimenting with themes with Haykuro's 5.0.3H apps to sd and I ended up with a looping HTC screen. I did a wipe and tried to perform the update again. Same. I tried a fastboot restore... stuck at android for over an hour.
Tried fastboot flash update.zip and I get
"writing 'update' ... FAILED (remote: partition does not exist)
I tried putting RC33 1.42 on a blank SDCARD and applying update... and it's stuck at the boot screen.
EDIT::: I got 502Hr3 GlossSuite back on there that I made... but the appstosd wasn't working and made my phone loop at the "htc" boot up.
03:00AM Just downloaded Partition Manager 9 and will try to reformat/repartition my sdcard and start appstosd over from scratch.
Did I just paperweight my G1?
08:00 4/21/09 FIXED!!!
Binary100100 said:
Right... so here's the story as well as I can remember it.
I made a theme for 5.0.2H AppsToSD GlossSuite and flashed it. Made 3 calls with it and then did a backup with nandroid. Then, being proud of my achievement, posted my work and it was downloaded over 20 times.
I decided (for some reason that I can not explain... maybe lack of sleep after working on this for so long) that I'll go back to RC33. Flashed the RC33 Apps to SD rom and radio back and used RC33 and then used the apps to sd app for the apps to sd. I had RC33 installed and working for about 2 hours while I tried to cook up a few more changes (launcher... clock... etc). Then wiped and tried flashing back to the new rom. Everything worked. Flashed the new radio. Everything worked. Followed the instructions for apps to sd for haykuro builds... rebooted... looping HTC boot screen.
I tried a wipe... looping.
Tried a nandroid restore with several of the backups that I made.
Stuck at the splash screen and I left it there for over an hour.
I got impatient and pulled the battery and tried another flash from a different backup. Same. Both were RC33. So I tried with the Haykuro backups... same.
I moved RC33appstosd.zip to the root of my sdcard and renamed it update.zip.
Flashed... looping Android screen. Tried a fresh 128mb sdcard with update.zip. Same.
I tried recovery fastboot flash update.zip and got "writing 'update' ... FAILED (remote: partition does not exist)
Then made my first post up above.
Did "fastboot erase system -w" from korndub's suggestion.
Then fastboot flash my .img's. I got the looping Android again.
I was about to give up when I downloaded the REGULAR RC33 to my sdcard, renamed it update.zip, updated and it FINALLY booted up. It was at this point I was finally able to see a homescreen.... so I figured it had to be something with the apps to sd.
But now there was another problem... I would get android.phone (or whatever) force close error everytime I would get a call. I couldn't place calls either. Several people were experiencing the same problem that flashed my rom and needed help. But if it was a problem with the rom then why was I experiencing it on RC33? Plus... I made a calls when I had in installed on my phone at the beginning. It was very strange. But I had the problem with RC33.
So I tried to repartition my card with Paragon Partition Magic 9 and it could not repartition my card! I tried to just repartition it in Windows (XP) and it worked. I tried Partition Magic again... still gave me errors and wouldn't let me do it! So it must be a problem with my SDCARD. I decided to give a very old program that i had stored in a box a try called Copy Commander 9 (I'll gladly remove the file upon request... just pm me... I just want to help out anyone that has issues with the paritioning process. This is a trial version but you can boot from CD and fix your partitions).
I booted from CD and it fixed my partition problem right away!
I did a fastboot erase system -w in recovery to wipe and reflashed RC33 and the phone was working again. Calls and all. Not taking any chances... updated (in this order)
RC33 > RC33 Apps2SD > RC33 Apps2SD Gloss Suite
I'm scared to go back to 5.0.2H Apps2SD now.
Sooooo... with all of that said... where the hell did I go wrong? I backup with nandroid everytime before I wipe and update. I boot up to confirm they are working... mount the sdcard so I can rename the files to the firmware, time, and date of the backups. And yes I wipe everytime I flash a update.zip
I'm still convinced that it was the apps to sd and/or the partition... but how would that explain the force closes for calls on RC33???
Anyway... feel free to comment but fyi I'm good now (or at least I feel like trying Haykuro's build again)
Click to expand...
Click to collapse
you dont fastboot flash update.zip....
try this...
fastboot erase system -w
then flash the system image back.
fastboot flash system system.img
fastboot reboot
korndub said:
you dont fastboot flash update.zip....
try this...
fastboot erase system -w
then flash the system image back.
fastboot flash system system.img
fastboot reboot
Click to expand...
Click to collapse
sending 'system' (70038 KB)... OKAY
writing 'system' ... OKAY
7:55 PM
8:05 PM still hanging at my splash screen.
NOTE: I've already tried flashing my nandroid backups (userdata.img, system,img, boot,img) and had no luck.
Trying again...
fastboot erase system -w
erasing 'system'... OKAY
erasing "userdata'... OKAY
erasing 'cache'... OKAY
8:06PM
fastboot flash system system.img
sending 'system' (70038 KB)... OKAY
writing 'system'... OKAY
8:08PM
It boots up to flashing android and loops.
Looks like your gonna have to start back at RC29 re-root and start all over.
yep..may be the only way to get it working...start fresh at rc29 re-root and re-update
jjjackson56 said:
Looks like your gonna have to start back at RC29 re-root and start all over.
Click to expand...
Click to collapse
if u can access the bootloader there is always hope as so i have heard in the forums
i dont know mcuh about it
but from the countless threads i read while in class and not listening to my professors...if u can access the bootloader there is always hope. just flash the dreaimg.nbh file and start all over...better than a looping phone...
and for now
i would suggest dont expirement with themes because the rom is already unstable as it is in the background...it may look like it works flawlessly but u must rmr this a port form a magic phone...
hope this helps :-D
I had this happen to me this weekend. I just re-applied a known working update.zip from recovery and it solved my problem. I went thru 10 nandroid backups before I tried that too
I've had this happen a couple times while developing my theme for RC33. Just flash DREAIMG.nbh and start from scratch.
TheDudeOfLife said:
I had this happen to me this weekend. I just re-applied a known working update.zip from recovery and it solved my problem. I went thru 10 nandroid backups before I tried that too
Click to expand...
Click to collapse
Well... I eventually got it working again... kinda. But I think it is a problem with my /system/sd or my ext2 partition because when I try to move my apps to sd (btw... there are already several on there) it loops at the htc screen. So I am downloading Partition Manager 9 now and I'm going to try to repartition/format my sdcard and see if that corrects the problem. Luckily I backed ALL of my apk's to my sdcard earlier that day. It's strange though because the only thing that I can think of that messed it up was the appstosd app that I used. It worked at first... I did a backup (even labled it)... rebooted... then it started looping. So... I'm going to start Apps to SD from scratch and that should fix my problem.
But why is it that when I tried to flash BACK to RC33 it was being pissy at me? I don't even know if I'll be able to flash back now.
When i went to the haykurus from the jf rc9 version it stood solid still at the htc for a good 15mins, then suddenly WHAM woke up and asked for pin code.. When i had completed the "setup" i tried a call + menu + hangup reboot.. And it worked like normal in boot, took no mere than a few seconds.. So first time can be LONG, funny thing is, its not always like that, tried a few versions of the haykuro, sometimes its only hanging for a 5 mins, other 10..
FIXED
Right... so here's the story as well as I can remember it.
I made a theme for 5.0.2H AppsToSD GlossSuite and flashed it. Made 3 calls with it and then did a backup with nandroid. Then, being proud of my achievement, posted my work and it was downloaded over 20 times.
I decided (for some reason that I can not explain... maybe lack of sleep after working on this for so long) that I'll go back to RC33. Flashed the RC33 Apps to SD rom and radio back and used RC33 and then used the apps to sd app for the apps to sd. I had RC33 installed and working for about 2 hours while I tried to cook up a few more changes (launcher... clock... etc). Then wiped and tried flashing back to the new rom. Everything worked. Flashed the new radio. Everything worked. Followed the instructions for apps to sd for haykuro builds... rebooted... looping HTC boot screen.
I tried a wipe... looping.
Tried a nandroid restore with several of the backups that I made.
Stuck at the splash screen and I left it there for over an hour.
I got impatient and pulled the battery and tried another flash from a different backup. Same. Both were RC33. So I tried with the Haykuro backups... same.
I moved RC33appstosd.zip to the root of my sdcard and renamed it update.zip.
Flashed... looping Android screen. Tried a fresh 128mb sdcard with update.zip. Same.
I tried recovery fastboot flash update.zip and got "writing 'update' ... FAILED (remote: partition does not exist)
Then made my first post up above.
Did "fastboot erase system -w" from korndub's suggestion.
Then fastboot flash my .img's. I got the looping Android again.
I was about to give up when I downloaded the REGULAR RC33 to my sdcard, renamed it update.zip, updated and it FINALLY booted up. It was at this point I was finally able to see a homescreen.... so I figured it had to be something with the apps to sd.
But now there was another problem... I would get android.phone (or whatever) force close error everytime I would get a call. I couldn't place calls either. Several people were experiencing the same problem that flashed my rom and needed help. But if it was a problem with the rom then why was I experiencing it on RC33? Plus... I made a calls when I had in installed on my phone at the beginning. It was very strange. But I had the problem with RC33.
So I tried to repartition my card with Paragon Partition Magic 9 and it could not repartition my card! I tried to just repartition it in Windows (XP) and it worked. I tried Partition Magic again... still gave me errors and wouldn't let me do it! So it must be a problem with my SDCARD. I decided to give a very old program that i had stored in a box a try called Copy Commander 9 (I'll gladly remove the file upon request... just pm me... I just want to help out anyone that has issues with the paritioning process. This is a trial version but you can boot from CD and fix your partitions).
I booted from CD and it fixed my partition problem right away!
I did a fastboot erase system -w in recovery to wipe and reflashed RC33 and the phone was working again. Calls and all. Not taking any chances... updated (in this order)
RC33 > RC33 Apps2SD > RC33 Apps2SD Gloss Suite
I'm scared to go back to 5.0.2H Apps2SD now.
Sooooo... with all of that said... where the hell did I go wrong? I backup with nandroid everytime before I wipe and update. I boot up to confirm they are working... mount the sdcard so I can rename the files to the firmware, time, and date of the backups. And yes I wipe everytime I flash a update.zip
I'm still convinced that it was the apps to sd and/or the partition... but how would that explain the force closes for calls on RC33???
Anyway... feel free to comment but fyi I'm good now (or at least I feel like trying Haykuro's build again)
I do know that there is some kind of a bug in the phone.android.com thing in about every build there is, including official ones, and I don't think it has become completely resolved.
I have gotten it when I lock onto a carrier, then restart my phone in an area where that carrier has no signal. Others have had it when ending a call, as in your case. Others have reported it when they've changed providers.
Sometimes, a new sim fixes it, and sometimes it doesn't.
I know I didn't give any real answers here, but thought I would give you a heads up that it isn't unknown. I was just lucky enough to find something that was a solution for me.
When I called tech support, (T-Mo), and told them what fixed it for me, they were very glad to have one solution to at least try, because they do get this issue, and often times, they end up sending a new phone, because they don't know how to fix it.
kathi17 said:
I do know that there is some kind of a bug in the phone.android.com thing in about every build there is, including official ones, and I don't think it has become completely resolved.
I have gotten it when I lock onto a carrier, then restart my phone in an area where that carrier has no signal. Others have had it when ending a call, as in your case. Others have reported it when they've changed providers.
Sometimes, a new sim fixes it, and sometimes it doesn't.
I know I didn't give any real answers here, but thought I would give you a heads up that it isn't unknown. I was just lucky enough to find something that was a solution for me.
When I called tech support, (T-Mo), and told them what fixed it for me, they were very glad to have one solution to at least try, because they do get this issue, and often times, they end up sending a new phone, because they don't know how to fix it.
Click to expand...
Click to collapse
well... i suppose it could make sense because my sim card needs to be replaced. the poor thing has played musical phones for about 7 years now. LOL.
make sure card is formatted correct "FAT32" ifso reformat anyway! then try again. if propblem persist\. re flash "dreaim.nbh" rc29
but now I cant get superuser to work with advance taskmanager. I follow some tutorials on how to upgrade to 1.5. I backup my phone first, then flashed the update. Then I flashed the new radio and lastly I flashed my backup onto the phone again. I dont get it.. what did I did wrong and it's there a way to fix it???
TIA
What kind of backup?
You flashed back a nandroid backup? This woul be fail I guess.
Don't work... please leave some more infos.
I wiped, installed JF's ADP 1.5, installed Advanced Taskmanager and this works fine.
[email protected] said:
but now I cant get superuser to work with advance taskmanager. I follow some tutorials on how to upgrade to 1.5. I backup my phone first, then flashed the update. Then I flashed the new radio and lastly I flashed my backup onto the phone again. I dont get it.. what did I did wrong and it's there a way to fix it???
TIA
Click to expand...
Click to collapse
LOL "I follow some tutorials" I hope it was more then "some"... anyway, you back you up phone just in case there is an issue when you flash the update and you can go to your backup to get you phone back up again if there was an issue... you don't flash your backup after you flash the update...
Do your backup, flash the radio, flash the update keep your backup in a safe place... hope that helps
peace
ahh darn. That's what I did wrong. For some reason I thought te backup was to install al the apps again. Darn it... So what do I do now?? how can I fix it. Also, one last thing. After the radio update, everybody who I call tells me that my voice has an echo?? This didnt happen before 1.5 and the new radio?? Is there a way top fix it??? TIA
You have to do a wipe after flashing everything to fix su problem.
Hey guys so I'm pretty tech savvy and i know my way around this phone but something weird's been happening. I had CM 4.2 on my Mytouch3G. I tried applying a theme which made it not boot up anymore(bootloop).
I did make a nandroid backup before but when i tried restoring with it, it keeps getting stuck at the green mt3g screen or at the second loading screen. I've tried flashing the rom again but gets stuck at the same place. If I just install the htc 1.6 update it works fine. But when I go to apply the CM 4.2 update it gets stuck again. I have wiped a million times, and fixed ext system also a bunch of times. I have also unrooted also by applying sappimg.nbh and starting over. Rooted, tried again, but nothing, still getting stuck at the loading screen. I have gotten it a couple times to go all the way to the home screen but i get com.android.phone force close.
Also i've tried going from stock htc 1.6 to CM 4.1.99 and up, not just straight to CM 4.2 so i don't know what to do.
Any help appreciated!
I seem to be having this problem as well.
Phone just freezes at MT3g loading screen.
4.1.9.2 seems to load fine, however 4.2.1 flashes properly, but phone just sits at green loading screen.
charkosh said:
I seem to be having this problem as well.
Phone just freezes at MT3g loading screen.
4.1.9.2 seems to load fine, however 4.2.1 flashes properly, but phone just sits at green loading screen.
Click to expand...
Click to collapse
Maybe a mytouch issue? Hopefully we can get some help.
lupascu.marius said:
Maybe a mytouch issue? Hopefully we can get some help.
Click to expand...
Click to collapse
You didnt say the steps you took to flash it. Did you do the step by step instructions on Cyan's OP? You cant just flash it like a normal ROM you have to do what he says on his post. I followed the steps and my MT3G works fine with it.
bluecluenj said:
You didnt say the steps you took to flash it. Did you do the step by step instructions on Cyan's OP? You cant just flash it like a normal ROM you have to do what he says on his post. I followed the steps and my MT3G works fine with it.
Click to expand...
Click to collapse
But i did say the steps...i first flashed the htc recovery image like it CM said to do. I even said in the post that i already had cm 4.2 on my phone but had to reflash after a theme froze my phone at the boot screen. I know its a different install process compared to any other rom.
Make sure you wipe before applying rom
Mr Bill Florida said:
Make sure you wipe before applying rom
Click to expand...
Click to collapse
Do people even take time to read the original post, or do they just blurt out things that sound helpful? I said towards the middle of the post that i've wiped a million times and also tried fixing ext filesystem. I appreciate anyone trying to help but please read my post carefully!
I have the same problem guys, but oly with 4.2.3.1
http://forum.xda-developers.com/showpost.php?p=4851283&postcount=3677
i HAD a similar problem when i went to 4.1.999 the first time but i fixed it.
i prefer amon ra's recovery 1.2.3g. i wiped the file system AND cache. then i did the 1.6 update followed immediately with the CM update. i rebooted and let it load up completely, then rebooted into recovery again and applied the new theme.
i actually went through the process a couple times before it worked flawlessly. it may have been a different problem though, since i was getting past the mytouch splash and about 10 seconds into the android splash before it would freeze.
jayzusfk said:
i HAD a similar problem when i went to 4.1.999 the first time but i fixed it.
i prefer amon ra's recovery 1.2.3g. i wiped the file system AND cache. then i did the 1.6 update followed immediately with the CM update. i rebooted and let it load up completely, then rebooted into recovery again and applied the new theme.
i actually went through the process a couple times before it worked flawlessly. it may have been a different problem though, since i was getting past the mytouch splash and about 10 seconds into the android splash before it would freeze.
Click to expand...
Click to collapse
Thats a good idea...i'll try amon ra's recovery image and see if there's different results. Will post back soon.
lupascu.marius said:
Thats a good idea...i'll try amon ra's recovery image and see if there's different results. Will post back soon.
Click to expand...
Click to collapse
So i tried everything from scratch but with amon ra's rec image this time. It gets passed the first boot screen and right after the second android screen it goes straight to a black screen. Have tried a few variations of installing and same thing happens everytime...This blows, i'm so stuck.
lupascu.marius said:
So i tried everything from scratch but with amon ra's rec image this time. It gets passed the first boot screen and right after the second android screen it goes straight to a black screen. Have tried a few variations of installing and same thing happens everytime...This blows, i'm so stuck.
Click to expand...
Click to collapse
Quick update for anyone with any ideas. I finally got it to boot up and it runs great except for two things I've notices so far. When i try to add widgets nothing pops up and when i go to settings the window comes up for half a second then goes away and back to home screen. Now what I did to fix it was partition the sd card which i was told is NOT necessary. Then after i got it to work i tried again with a sdcard that was NOT partitioned and it did the same thing again, black screen no-go. So it seems like if you don't partition the sdcard on some phones the phone freezes at a black screen. Keywords being "some phones". So for anybody who knows how to fix the widget and settings problems not opening, please help me....Thanks
lupascu.marius said:
But i did say the steps...i first flashed the htc recovery image like it CM said to do. I even said in the post that i already had cm 4.2 on my phone but had to reflash after a theme froze my phone at the boot screen. I know its a different install process compared to any other rom.
Click to expand...
Click to collapse
Actually if you have an MT3G I believe you don't flash the 1.6 recovery image, but flash the 1.6 ADP rom. That is what I did since I was already rooted but with AmonRa's donut rom, but wanted to give Cy a shot, and I had no problems flashing this HTC ADP 1.6 DRC83 , then reboot manually but while rebooting I pushed home fast while it was rebooting to get me to the recovery screen, then I just flashed Cy's 4.2.2 then I went to the market and downloaded his Cyanogen updater and checked for an update, then found the update 4.2.3.1 and downloaded that straight to my phone and then choose to reboot and it automatically installed 4.2.3.1 straight to my MT3G with no problems at all.
From Cyanogen:
Download: Android 1.6 Recovery Image. (This isn’t like a typical "recovery" image we know -- it’s simply HTCs version of an update.zip.)
* Magic32A and Magic32B users only: Download this HTC_ADP_1.6_DRC83_rooted_base.zip
lupascu.marius said:
Quick update for anyone with any ideas. I finally got it to boot up and it runs great except for two things I've notices so far. When i try to add widgets nothing pops up and when i go to settings the window comes up for half a second then goes away and back to home screen. Now what I did to fix it was partition the sd card which i was told is NOT necessary. Then after i got it to work i tried again with a sdcard that was NOT partitioned and it did the same thing again, black screen no-go. So it seems like if you don't partition the sdcard on some phones the phone freezes at a black screen. Keywords being "some phones". So for anybody who knows how to fix the widget and settings problems not opening, please help me....Thanks
Click to expand...
Click to collapse
I would go ahead and put Cy's latest back on your sd card, and also download the HTC_1.6_ADP rom if you have a MT3G (Magic 32B) or a Magic 32A and put that on your sd card. WIPE WIPE WIPE - I always wipe three times, and wipe cache also, then flash the 1.6 ADP rom then reboot but while it is rebooting hold down home to get back to recovery screen then apply Cy's on top of the 1.6 ADP rom.
I went ahead and just put Cy's 4.2.2 (instead of 4.2.3.1) on my sd card along with the HTC 1.6 ADP Rom and flashed the HTC 1.6 ADP rom first, then rebooted manually from the recovery screen, then quickly hold down home while rebooting to get back to recovery screen and applied any zip Cy4.2.2. Then when I signed in went to market to download Cyanogen Updater and set that up and then checked for updates and it found 4.2.3.1. I dowloaded that from my phone and then it was automatic from there, just asked if I wanted to reboot and apply and I said yes. Up and running with no problems so far....
mavsfan said:
I would go ahead and put Cy's latest back on your sd card, and also download the HTC_1.6_ADP rom if you have a MT3G (Magic 32B) or a Magic 32A and put that on your sd card. WIPE WIPE WIPE - I always wipe three times, and wipe cache also, then flash the 1.6 ADP rom then reboot but while it is rebooting hold down home to get back to recovery screen then apply Cy's on top of the 1.6 ADP rom.
I went ahead and just put Cy's 4.2.2 (instead of 4.2.3.1) on my sd card along with the HTC 1.6 ADP Rom and flashed the HTC 1.6 ADP rom first, then rebooted manually from the recovery screen, then quickly hold down home while rebooting to get back to recovery screen and applied any zip Cy4.2.2. Then when I signed in went to market to download Cyanogen Updater and set that up and then checked for updates and it found 4.2.3.1. I dowloaded that from my phone and then it was automatic from there, just asked if I wanted to reboot and apply and I said yes. Up and running with no problems so far....
Click to expand...
Click to collapse
That is the exact process i run thru. Sorry for the confusion, the reason i said htc recovery 1.6 is because thats what htc calls it. So i do have the htc 1.6 adp.....and i do wipe a lot also
This is probably a dumb question as I assume you would have mentioned it, but are there themes involved in any of your troubles or are you staying with stock 4.2.3.1? I only ask because I was having the same issue with the SECOND android splash crashing because I had tried to install a theme before booting into Cyanogen at least once.
I also don't think you should reboot after installing the 1.6 base like mavsfan was suggesting, though I'm not sure if it's related to your issues.
Try booting it up without an sdcard inserted. If it works that means it's your card. Card issues are very hard to diagnose and even harder to solve (other than reformat).
jayzusfk said:
This is probably a dumb question as I assume you would have mentioned it, but are there themes involved in any of your troubles or are you staying with stock 4.2.3.1? I only ask because I was having the same issue with the SECOND android splash crashing because I had tried to install a theme before booting into Cyanogen at least once.
I also don't think you should reboot after installing the 1.6 base like mavsfan was suggesting, though I'm not sure if it's related to your issues.
Click to expand...
Click to collapse
The problem i have is with the stock 4.2.3.1 not the themes...and i've also tried without rebooting after installing the 1.6 base and just go straight to applying the CM update
pascanu said:
Try booting it up without an sdcard inserted. If it works that means it's your card. Card issues are very hard to diagnose and even harder to solve (other than reformat).
Click to expand...
Click to collapse
Hey thanks for your suggestion, i have tried that, I've reformatted, I've tried different SD cards and nothing changed. I'm pretty sure the sd cards are good...
[SOLVED]Finally...
So for anyone having similar issues, here's what i did to finally get this working.
Apparently with Cyanogen's newest ROM's you HAVE to partition your sdcard, so the Rom will run on certain phones. I don't know if its all phones because there's only a few people that i've heard to have this problem. So here's the steps:
Things you will need(all these can be found in this forum)
1. Phone+sdcard
2. sappimg.nbh
3. FlashRecovery.apk
5. AmonRa's recovery image(has more options than CM's RecImg)
6. Htc ADP 1.6 stock donut rom
7. CM 4.2.3+
8. A theme(optional)(check out the Eclair 2.0 theme)
Starting from scratch
1. a. Put sappimg.nbh on sd card and turn the phone off.
b. Turn phone on by holding VOLUME DOWN+POWER
c. Apply the stock sapphire image and boot up to home screen.
2. a. Now put FlashRec.apk and AmonRa's recovery image on sdcard.
b. Install a file manager like Astro and install FlashRec.apk
c. Now open it and click Backup Recovery Image.
d. Now erase whats in the box and type /sdcard/name.of.recoveryimage.img
e. Yes you do have to type .img after the recovery image name.
f. Then click flash.
3. a. Now put the HTC ADP 1.6 Rom and CM 4.2.3+ Rom on the sdcard.
b. Reboot into recovery by holding HOME+POWER.
c. Now partition your sdcard by selecting it from the menu(the one that says +swap)
d. Now convert ext2 to ext3. After that I did:
4. a. Wipe, format ext3, wipe
b. Flash HTC ADP 1.6
c. Wipe, format ext3, wipe again.
d. Flash CM 4.2.3+
e. Wipe, format ext3, wipe one more time
f. Reboot, now it should work, give it some time to boot up.
Adding the theme
1. Make a nandroid backup before starting to save you the hassle.
2. Put your theme.zip on sdcard and reboot in recovery again.
3. Choose apply any zip and choose the theme from the list.
4. Reboot once its done and enjoy.
If anyone has any questions about anything here go ahead and reply or PM me. Have a good one guys, hope this helps anyone.
Oh and if you guys see any mistakes let me know so i can fix it, its pretty late right now