Related
My brother got tired of all the bloatware on his G2x with 2.3.3 OTA, so I proceeded to try to flash a custom ROM. Did the process of NVFlash, but with some unexpected results:
1) As I'm lead to believe, I should see an orange "ANDROID" show up when holding volume down and power. But instead I get a green "ANDROID" with a bunch of Android icons like messaging.
2) When it gets past the screen I mentioned, it does go into CWM Recovery but as soon as I let go of a button to navigate, the phone shuts off. Sometimes it stays on if, while still holding down volume and power, I press volume up, release down, then release power. Even then, it sometimes still shuts off.
3) When trying to flash a rooted ROM (CyanogenMod 7.1, after doing a data wipe/factory reset), I get an error message and the installation aborts.
Was able to restore the 2.3.3. OTA because I had backed up, but any ideas?
I am no expert but I would start over from scrach. Rinse and Repeat. it sounds like it did not install right.
Are you sure you flashed the CWM for the G2X? If you flashed the wrong recovery all kinds of problems, such as you described, could occur. Good thing you had the backup.
mojorisin7178 said:
I am no expert but I would start over from scrach. Rinse and Repeat. it sounds like it did not install right.
Click to expand...
Click to collapse
Would you recommend I reflash CWM straight up, or the stock recovery through NVFlash before trying again? I'd assume I should follow all the same steps as if I was trying to flash CWM, but instead of clicking on CWM, click stock recovery instead.
jboxer said:
Are you sure you flashed the CWM for the G2X? If you flashed the wrong recovery all kinds of problems, such as you described, could occur. Good thing you had the backup.
Click to expand...
Click to collapse
Positive. I downloaded the necessary files and followed all the steps from here:
http://forum.xda-developers.com/showthread.php?t=1056847
Again I am no expert but that sounds like a good idea i would say you it cant hurt. I think you will have to reflash cwm but you have to do that anyway so I would say it is the best way to start clean.
Got CWM Recovery to work. It still shows the green ANDROID with the icons, but I no longer have to struggle to keep it from shutting off. I was able to flash xboarder's tweaked Gingerbread ROM, but still unable to flash CyanogenMod 7.1. I did a factory/wipe data, wiped cache, and dalvik cache. Still get an error message upon trying to install.
when i first did the nvflash my phone was getting shut off when it got to the recovery and then i let go of the power button. Until i realized that you are supposed to let go of the power/volume button when the word android appears and all those icons u mentioned, yeah i get the same screen. i had no problems flashing 3 builds of cm7 and xboarder's rom 2 times.
Not sure what's going on with the CM 7.1RC but I was able to flash the latest EaglesBlood ROM this mornibg and he's really enjoying it so far. Thanks for all the help!
Sent from my HTC Glacier using XDA App
The green android with the icons is just a different splash screen in the newer version of cwm.
lcambriz said:
Not sure what's going on with the CM 7.1RC but I was able to flash the latest EaglesBlood ROM this mornibg and he's really enjoying it so far. Thanks for all the help!
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Could've been a bad download. Sometimes you just gotta download the file again and it'll flash no issues.
But I'd go for the latest CM7 nightly. They are leaps and bounds ahead of where they were with RC1.
I figured that might be the problem. Eaglesbood seems to be working really well for him, so I think he'll just stick with that. My bro is more of the "If it isn't broken, don't fix it" type, whereas I'm more inclined to try the latest. I'm tempted to try the nightlies myself on my Glacier, if they really are better than RC1.
Sent from my HTC Glacier using XDA Premium
On my 4th G2x. Same problems as the others. Reboots on its on, sleep of death. In fact this morning I was talking on phone and it shut down. I had to remove battery and reboot.
I called Customer Service that has always been super nice. This time they said, oh, since this is your 4th and this one just in 6 days I can't help you I have to send you to Tech. The Tech guy basically said "known software problem, sending replacement won't do any good. Can't give you different phone. Maybe it is your SD card and apps you have loaded. He actually told me Facebook app could cause it to shut down. Said to reset to factory, remove SD card and use it for 3 days with no apps. After 3 days if all is well then start adding apps. I asked what if it has problems during the 3 days? He said, 'there is nothing we can do. I will report this to LG and they will send out an update. I don't know when but they will update the software".
WTH?! So I am done. I will do the root. Now i just need to read all these great threads to figure out how and which version! Wish i could just pay one of you to do it for me!
Thanks for letting me rant.
I've been running stock since August with no issues but I really wanted the LG Camera app so I installed CWR and flashed the WeaponX rom with no issues. Everything works and it's even smoother then stock Gingerbread. Just follow the directions to the T and the process should take less than fifteen minutes if you have all your files ready to go.
Enjoy!
seangprice said:
I've been running stock since August with no issues but I really wanted the LG Camera app so I installed CWR and flashed the WeaponX rom with no issues. Everything works and it's even smoother then stock Gingerbread. Just follow the directions to the T and the process should take less than fifteen minutes if you have all your files ready to go.
Enjoy!
Click to expand...
Click to collapse
Thanks! Which directions did you follow? There are a number of threads here.
The directions are a bit confusing as they reference other threads and then have comments stating this step is now obsolete. etc. Seems like I first need to get the ROM Manger?
https://market.android.com/details?id=com.koushikdutta.rommanager.license&feature=search_result
Correct?
i followed this http://forum.xda-developers.com/showthread.php?t=1060715 and was fine. this was my first root as well.
http://forum.xda-developers.com/showthread.php?t=1056847
I used this method to NvFlash and install Clockwork recovery which is the basic software you need in order to flash ROMs. You do not need ROM Manager. Once you've done the NvFlash and installed CWR you can copy your ROMs to the SD card or phone storage and flash through Clockwork Recovery. Make sure you backup your stock install through CWR prior to flashing anything new so you can return the phone to a usable state.
As always follow the directions verbatim, some steps take time as well. Also make sure your battery is 100% charged... If it dies during any portion of the process bad things can happen.
I had all of those issues until I flashed cm7... then the issues became very minimal... I once had 8 reboots in a day on stock rom, during phone calls and everything... You are definitely taking a step in the right direction
P.S. my wife has completely stock phone on stock rom and has Facebook app with no issues, she just got lucky I guess
To OP: do you have 2.2 or 2.3 installed as your stock rom... read carefully there are different instructions for both
Never use ROM Manager. Even if it worked perfectly on our phone I still would never recommend it. I've seen it cause more harm than good.
Anyways, you don't even technically need root to flash a ROM.
Just NVFlash CWM. After that you can upgrade to the latest CWM via ADB. Then flash your desired ROM. I suggest CM7.
yeah, you know ROM manager... now forget it. Use NVflash and clockwork
I got myself in trouble!
I followed instructions and all went well. I installed the GB, no problems. No I was brave so I thought I would try the Cyanogen mod. It too installed fine. I don't like it. Now i can't get rid of it! I tried reinstalling the GB and the cyanogen won't go away! i tried restore to factory, but it won't go away!!
Please lend me your advice on how to remove Cyanogen mod!
donbeth said:
I got myself in trouble!
I followed instructions and all went well. I installed the GB, no problems. No I was brave so I thought I would try the Cyanogen mod. It too installed fine. I don't like it. Now i can't get rid of it! I tried reinstalling the GB and the cyanogen won't go away! i tried restore to factory, but it won't go away!!
Please lend me your advice on how to remove Cyanogen mod!
Click to expand...
Click to collapse
Then just wipe and flash a new ROM.
Make sure you wipe data, cache, dalvik then format system before flashing new ROM.
Clearly I am a dunce.
I uninstalled the driver on pc. Did a reinstall. Flashed ROM again. Installed GB zip. rebooted and the dang Cyanogen MOD is still there!
I even went over all steps again, this time flashing back to stock. Still Cyanogen MOD is boots up
donbeth said:
Clearly I am a dunce.
I uninstalled the driver on pc. Did a reinstall. Flashed ROM again. Installed GB zip. rebooted and the dang Cyanogen MOD is still there!
I even went over all steps again, this time flashing back to stock. Still Cyanogen MOD is boots up
Click to expand...
Click to collapse
Yes yes you are when you flash a new rom wipe data wipe cache wipe dalvik and wipe system
Sent from my LG-P999 using XDA App
i remember, I followed this video.
http://theunlockr.com/2011/05/03/how-to-load-a-custom-rom-on-the-t-mobile-g2x/
to install a new rom
remember: (once you've copied the zip on sd card, power the phone to enter into clockwork and steps)
1. back up and restore
2. wipe data/ factory reset
3. install zip from sd card
so far, it hasn't failed me
you can skip the first one, but shouldn't
Just download Weapon if you want to go back to stock. Its Stock with a few needed tweaks and fixes. Very stable and no issues.
G2x - 2.3.7 CM7
Transformer - 3.2 Revolver OC/UV
The reboot issue were in all my G2X(3). Only rom that fixed that was Weapon G2X. Running a custom rom is the way to go with this phone, otherwise you'll go through 100 replacements with same issues.
Today I did an exchange for my brother's line which he has the G2X and the rep told me I could get a brown color G2X because they no longer carry original color or a Sensation. (Not sure what he was talking about brown color because I thought all G2X were the same color other than the white floating around)
So I decided to just get the Sensation, I know it's got issues of it's own, but will give it a shot because I want the G2X to just be a memory of the past.
This phone could have been a beast, but will never live to it's full potential.
Good luck and if you need to exchange again and you don't mind getting a Sensation I would suggest bringing that up to the rep.
Hercules Hercules!!
I'm a little confused...I've been using ROM Manager just fine...?
Neejay said:
I'm a little confused...I've been using ROM Manager just fine...?
Click to expand...
Click to collapse
If you screw up and can't boot up, ROM manager cannot get you into recovery. Only an NV flashed clockworkmod recovery will boot up in the event of a boot loop.
Sent from my LG-P999 using xda premium
Neejay said:
I'm a little confused...I've been using ROM Manager just fine...?
Click to expand...
Click to collapse
You don't have recovery with Rom Manager, yeah it flashes all the roms but if you get into a bootloop or worse then you are SOL.
Hercules Hercules!!
Neejay said:
I'm a little confused...I've been using ROM Manager just fine...?
Click to expand...
Click to collapse
Rom manager works just fine. However, like previously said, you just need to NVFlash first for safety reasons.
From a complete stock G2x, NVFlash, Nandroid Backup, and flash a previously downloaded rom (Weapon or CM7 or MIUI or Eaglesblood or any of the other wonderful roms). Custom roms have root so THEN you can go to town with Rom Manager.
I use Rom Manager as my primary flashing service because it not only downloads them, but will automatically reboot into recovery, perform your desired wipe options, and flash. With CM7 it will automatically check for the latest GAPPS and flash it too in one fowl swoop.
Just have to NVFlash first.
I NVFlashed my neighbors G2x the day he got it and, while he didn't want to try custom roms just yet, we did a Nandroid Backup just for laughs. Now he's running MIUI.
Re: [BeanStalk][1.179] Phone freezes after call
I am currently running Beanstalk 1.179. I've noticed with this build, and with at least one prior build I can't recall, that after an incoming phone call of at least a few minutes, the caller hangs up, and shortly after, my phone freezes. I'm all cases that I've noticed it, I've answered the phone while it was locked, and it returns to the lock screen before freezing. I've got the lock screen configured to use a password.
I can't recall anyone else mentioning this previously, so I thought I'd mention it. If it's not happening to anyone else, I'll assume it's my own problem.
Sent from my SGH-I997 using xda app-developers app
bretcb said:
I am currently running Beanstalk 1.179. I've noticed with this build, and with at least one prior build I can't recall, that after an incoming phone call of at least a few minutes, the caller hangs up, and shortly after, my phone freezes. I'm all cases that I've noticed it, I've answered the phone while it was locked, and it returns to the lock screen before freezing. I've got the lock screen configured to use a password.
I can't recall anyone else mentioning this previously, so I thought I'd mention it. If it's not happening to anyone else, I'll assume it's my own problem.
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
prolly bad flash..wipe it all and flashed the rom and gapps again
if that doesn't work, go back to gb stock and start over
qkster said:
prolly bad flash..wipe it all and flashed the rom and gapps again
if that doesn't work, go back to gb stock and start over
Click to expand...
Click to collapse
Thank you for the idea. I was just going over in my mind the ROMs that I have installed since I purchased the phone with an early version of scott.hart.bti's ParanoidAndroid already installed, and while I did not experience the issue with any of the ParanoidAndroid versions I installed, I believe I did also experience it while I was running Unofficial CM10 briefly between PA and BeanStalk. Perhaps the problem is indeed my own device, or something more deeply in the build source than with the build(s) themselves.
FWIW, in almost all instances when I installed a ROM, I always followed the entire procedure recommended by scott.hart.bti, including wiping the dalvik cache, as I did with my most recent install of Beanstalk 1.179.
bretcb said:
Thank you for the idea. I was just going over in my mind the ROMs that I have installed since I purchased the phone with an early version of scott.hart.bti's ParanoidAndroid already installed, and while I did not experience the issue with any of the ParanoidAndroid versions I installed, I believe I did also experience it while I was running Unofficial CM10 briefly between PA and BeanStalk. Perhaps the problem is indeed my own device, or something more deeply in the build source than with the build(s) themselves.
FWIW, in almost all instances when I installed a ROM, I always followed the entire procedure recommended by scott.hart.bti, including wiping the dalvik cache, as I did with my most recent install of Beanstalk 1.179.
Click to expand...
Click to collapse
as you become more familiar with flashing a rom and the principles, you will find that the cook book process may help but some times you may have to deviate from it to make it work.
ex: sometimes you may have to flash cm9 twice to get into the boot screen ..or flashing cm10 twice or reboot twice..or wipe a few extra time.
from my own experience, you have noticed something not working correctly..(sd not recognized, calls being dropped, app FC's and no one else had the same) you may need to start over...back to gb stock via heimdall or odin and work your way up.
the more i had screwed up and had to go back, there more i learned each time.
qkster said:
as you become more familiar with flashing a rom and the principles, you will find that the cook book process may help but some times you may have to deviate from it to make it work.
ex: sometimes you may have to flash cm9 twice to get into the boot screen ..or flashing cm10 twice or reboot twice..or wipe a few extra time.
from my own experience, you have noticed something not working correctly..(sd not recognized, calls being dropped, app FC's and no one else had the same) you may need to start over...back to gb stock via heimdall or odin and work your way up.
the more i had screwed up and had to go back, there more i learned each time.
Click to expand...
Click to collapse
Interesting. I remember that it took me forever to build up the courage to update ParanoidAndroid the first time, and scott.hart.bti's clear and complete cook book process certainly helped get me there. I have broken one of the Beanstalk ROMs once, too, and had to look up how to boot into CWM from power off to reflash.
I'm curious why going back to stock would make a difference. It seems to me that if I a doing a complete flash, wiping everything, than it shouldn't matter if it's a stock ROM or a new ROM. I'd be more nervous about breaking something if I going back to stock, since is a more complete and drastic change.
bretcb said:
Interesting. I remember that it took me forever to build up the courage to update ParanoidAndroid the first time, and scott.hart.bti's clear and complete cook book process certainly helped get me there. I have broken one of the Beanstalk ROMs once, too, and had to look up how to boot into CWM from power off to reflash.
I'm curious why going back to stock would make a difference. It seems to me that if I a doing a complete flash, wiping everything, than it shouldn't matter if it's a stock ROM or a new ROM. I'd be more nervous about breaking something if I going back to stock, since is a more complete and drastic change.
Click to expand...
Click to collapse
yeah...for the most part, while in cwm, factory reset, wipe system, data, cache, dalvik and then flashing a new rom work very well.
occasionally, for what ever reason that i'm not sure, going back to stock..changing file system back to rfs and then changing back to ext4 may be needed to fix certain problems...not common and not routine practice, but is needed...at least imo
OK, fair enough. I will read up more on going back to stock so I'm not unfamiliar with it. Which tool do you prefer?
For completeness of troubleshooting info for anyone else who may be reading, I received a phone call yesterday while the lock screen was disabled, and the phone still froze after the caller hung up. I received another call today, and made sure I hung up first, and no freeze, my phone was fine.
Sent from my SGH-I997 using xda app-developers app
bretcb said:
I will read up more on going back to stock..
Which tool do you prefer?
Click to expand...
Click to collapse
Everyone has their own prefs...I prefer heimdall. It doesn't matter. Whatever it takes to get the job done. You prolly should buy a usb jig too.
http://forum.xda-developers.com/showthread.php?t=1437548
How can I switch to Stock ICS Rom OR to another Custom Rom from CM10.1 ?
Cyanogenmod is awesome, but I want to switch back to stock, or possibly on another sense based rom if I like one. How can I do this?
EDIT: Question has been answered, thanks to all who supported me on this thread.
Just flash the ROM you want in recovery like you did when you flashed cm 10.1
Here's stock ICS with improvements: http://forum.xda-developers.com/showthread.php?p=14191938
You can try jellybean with sense 4+ from viper s: http://forum.xda-developers.com/showthread.php?p=39819473
Sent from my HTC Sensation
And don't forget to make a backup
Thanks, I will look into them.
What will happen if I try to restore a nandroid which was made in Stock, while I am on another ROM?
usman farhat said:
Thanks, I will look into them.
What will happen if I try to restore a nandroid which was made in Stock, while I am on another ROM?
Click to expand...
Click to collapse
it will replace your current rom with the one from the nandroid
but before restore always a full wipe first
rzr86 said:
it will replace your current rom with the one from the nandroid
but before restore always a full wipe first
Click to expand...
Click to collapse
Ok, so I have a nandroid backup which I did in Stock firmware. If I go to recovery and do full wipe followed by restoring the backup, I will get stock ROM with all the apps that were installed at the time of making backup, right? Same can be done in to switch to CM rom?
usman farhat said:
Ok, so I have a nandroid backup which I did in Stock firmware. If I go to recovery and do full wipe followed by restoring the backup, I will get stock ROM with all the apps that were installed at the time of making backup, right? Same can be done in to switch to CM rom?
Click to expand...
Click to collapse
that's why it is called nandroid backup
because it backups everything
and yes
full wipe first
restore nandroid
done
edit:the same with cm too
rzr86 said:
that's why it is called nandroid backup
because it backups everything
and yes
full wipe first
restore nandroid
done
edit:the same with cm too
Click to expand...
Click to collapse
wow it's easier than I thought. and really thanks for your quick replies, thanks button will be pressed after the comment are posted.
I am also running CM 10.1 and because of some hardware issues want to revert to the STOCK ROM (not any custom one similar to it). Problem is, i did not create a nandroid backup of it. How do I go about it now?
PS my phone is HBOOT 1.29
Reboot recovery
Format all partitions except SD card.
Flash ROM.
Reboot
You can also do an RUU. Look here and do step 2.4 to find your executable ruu: http://forum.xda-developers.com/showthread.php?p=26541170
Sent from my HTC Sensation
AndroidSupporter318 said:
Reboot recovery
Format all partitions except SD card.
Flash ROM.
Reboot
You can also do an RUU. Look here and do step 2.4 to find your executable ruu: http://forum.xda-developers.com/showthread.php?p=26541170
Sent from my HTC Sensation
Click to expand...
Click to collapse
Thanks for the quick reply, but can you tell me where to get the stock ROM too? Is it available on the HTC website? I have searched other posts but there seems to be no link for HBOOT 1.29
Here's arhd 7.2, a modified and improved version of stock: http://forum.xda-developers.com/showthread.php?p=14191938
Hboot version doesn't really matter. It's just the way the phone boots up.
If you want to revert to complete stock, no modifications, no improvements, then I would run the .exe ruu file from your computer. Here's the links for the .exe files: http://www.shipped-roms.com/index.php?category=android&model=Pyramid
Make sure you download the right ruu (XE or 4g) for your phone and the right country/carrier for it.
Sent from my HTC Sensation
AndroidSupporter318 said:
Here's arhd 7.2, a modified and improved version of stock: http://forum.xda-developers.com/showthread.php?p=14191938
Hboot version doesn't really matter. It's just the way the phone boots up.
If you want to revert to complete stock, no modifications, no improvements, then I would run the .exe ruu file from your computer. Here's the links for the .exe files: http://www.shipped-roms.com/index.php?category=android&model=Pyramid
Make sure you download the right ruu (XE or 4g) for your phone and the right country/carrier for it.
Sent from my HTC Sensation
Click to expand...
Click to collapse
Thank you! Fingers crossed it solves the issues, the hardware keys sometimes stop working and the screen automatically starts behaving like i'm multitouching
Good luck and I hope it solved the problem!
Sent from my HTC Sensation
Omer Humayun said:
Thank you! Fingers crossed it solves the issues, the hardware keys sometimes stop working and the screen automatically starts behaving like i'm multitouching
Click to expand...
Click to collapse
Does this happen while charging?
usman farhat said:
Does this happen while charging?
Click to expand...
Click to collapse
It has happened both when I'm charging and when it's not plugged into anything. It happens worst, and most often when the phone heats up, which is a big issue with CM. Part of the reason i wanna switch back to Stock ROM is to prevent any permanent damage to the internals with this frequent overheating. The battery stays cool, mind you.
My personal laptop's motherboard got fried yesterday so i'm just gonna wait until my exams end in a couple of weeks, and then get a new one and change the phone's ROM. I promise to update you guys on what happens
Omer Humayun said:
It has happened both when I'm charging and when it's not plugged into anything. It happens worst, and most often when the phone heats up, which is a big issue with CM. Part of the reason i wanna switch back to Stock ROM is to prevent any permanent damage to the internals with this frequent overheating. The battery stays cool, mind you.
My personal laptop's motherboard got fried yesterday so i'm just gonna wait until my exams end in a couple of weeks, and then get a new one and change the phone's ROM. I promise to update you guys on what happens
Click to expand...
Click to collapse
I had mentioned charger because i have a China charger and when my phone is charging and i lay it on a flat surface it touches itself everywhere whenever i touch somewhere. this happens to me due to incompatible charger. however i still charge with that charger. well this is my problem, yours is different.
I am not sure but I think there must be prominent links on Google containing stock roms. I have never searched for android but Nokia used to have dedicated softwares and websites for this.
And a free advice: if you want sense then try viper s Rom with sense 4.1 and android ics. (the one with jb doesn't have a working camera). I am using this and sense 4.1 is really good.
it is laggy though.
i've been using CWM recovery and CM nightlies. they've been just fine. today i restored a two day old backup, as i didn't care for the current nightly.
now the phone black screens after the samsung splash.
i've tried:
factory reset
wipe dalvick/cache
restoring other backups
flashing other nightlies
and the phone will boot for the first time, but if i select 'reboot' or 'power down' on the next boot it's only a samsung splash, then black screen (no cm splash, no response from buttons input), and will not boot again.
what's the problem ?
ohgood said:
i've been using CWM recovery and CM nightlies. they've been just fine. today i restored a two day old backup, as i didn't care for the current nightly.
now the phone black screens after the samsung splash.
i've tried:
factory reset
wipe dalvick/cache
restoring other backups
flashing other nightlies
and the phone will boot for the first time, but if i select 'reboot' or 'power down' on the next boot it's only a samsung splash, then black screen (no cm splash, no response from buttons input), and will not boot again.
what's the problem ?
Click to expand...
Click to collapse
Happens once in a while when you flash over a back up.
Try making a clean flash.
Sent from my Carbonized SAMSUNG-SGH-T769 using Tapatalk Pro
Somcom3X said:
Happens once in a while when you flash over a back up.
Try making a clean flash.
Sent from my Carbonized SAMSUNG-SGH-T769 using Tapatalk Pro
Click to expand...
Click to collapse
i've done that. right now, i've wiped everything, and then flashed a nightly, and it will not reboot !
it will only boot the -one- time directly after flashing a new rom. any reboot attempts after that means it freezes, or fails, with a black screen directly after the samsung splash.
what have i missed ?
ohgood said:
i've done that. right now, i've wiped everything, and then flashed a nightly, and it will not reboot !
it will only boot the -one- time directly after flashing a new rom. any reboot attempts after that means it freezes, or fails, with a black screen directly after the samsung splash.
what have i missed ?
Click to expand...
Click to collapse
Try installing Samsung firmware via Odin. Root it and try again. Wouldn't hurt to try.
Sent from my Carbonized SAMSUNG-SGH-T769 using Tapatalk Pro
Somcom3X said:
Try installing Samsung firmware via Odin. Root it and try again. Wouldn't hurt to try.
Sent from my Carbonized SAMSUNG-SGH-T769 using Tapatalk Pro
Click to expand...
Click to collapse
could you point me to a specific samsung firmware, or is there only one ?
ohgood said:
could you point me to a specific samsung firmware, or is there only one ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=24660137
Make sure repartition is always unchecked in Odin
Sent from my Carbonized SAMSUNG-SGH-T769 using Tapatalk Pro
ohgood said:
could you point me to a specific samsung firmware, or is there only one ?
Click to expand...
Click to collapse
Check out this post from the brick fix thread.
http://forum.xda-developers.com/showpost.php?p=44626072&postcount=117
The full fix thread
http://forum.xda-developers.com/showthread.php?t=1591601
Sniped lol
i've wiped everything. flashed back to stock via odin, rooted, just like always.
i've even wiped in between.
after the FIRST clean boot, there is no rebooting. all it does is continue to hang after the samsung splash. no cyanogenmod, no stock rom, no nothing, nothing will boot the SECOND TIME.
i really don't understand this.
i'm using CWM recovery 5.5.0.4, cm-nightly 10-05, and it just don't think it's going to work properly again. it's a real shame, cause i really like the size, weight, and speed of this phone. but if it won't boot, i can't use it.
if anyone has any tips, i'll try them. at this point i really don't mind destroying it, and it might make me feel better to do so.
i meant to add, it doesn't matter if i use a backup, flash a fresh new rom, or use stock. the first boot works fine, but all boots after that wether from powering down or selecting 'reboot' fail.
maybe this part will help -
if i wipe the phone completely, it will boot. let's call this boot 1.
i can setup the phone, or change nothing in settings, doesn't appear to matter, and choose 'power down' or 'reboot'. let's call this reboot 1.
the next time i power on the phone, black screen. no CM splash, nothing. i guess we'll call this hang 1 ?
ideas ?
ohgood said:
i've wiped everything. flashed back to stock via odin, rooted, just like always.
i've even wiped in between.
after the FIRST clean boot, there is no rebooting. all it does is continue to hang after the samsung splash. no cyanogenmod, no stock rom, no nothing, nothing will boot the SECOND TIME.
i really don't understand this.
i'm using CWM recovery 5.5.0.4, cm-nightly 10-05, and it just don't think it's going to work properly again. it's a real shame, cause i really like the size, weight, and speed of this phone. but if it won't boot, i can't use it.
if anyone has any tips, i'll try them. at this point i really don't mind destroying it, and it might make me feel better to do so.
.
i meant to add, it doesn't matter if i use a backup, flash a fresh new rom, or use stock. the first boot works fine, but all boots after that wether from powering down or selecting 'reboot' fail.
Click to expand...
Click to collapse
The October nightlies are cm10.2 right? Your using the old recovery, that's the issue. And there are newer nightlies.
New recoveries
http://forum.xda-developers.com/showthread.php?t=2475802
Cm thread
http://forum.xda-developers.com/showthread.php?t=2459198
Romman0 said:
The October nightlies are cm10.2 right? Your using the old recovery, that's the issue. And there are newer nightlies.
New recoveries
http://forum.xda-developers.com/showthread.php?t=2475802
Cm thread
http://forum.xda-developers.com/showthread.php?t=2459198
Click to expand...
Click to collapse
yes, they're fairly recent nightlies. i skipped back to the 10-5 nightly as i thought that might ahve been part of the problem. since you're pointing to my recovery being an older version, i'll update it. thanks for the clue stick !
Romman0 said:
The October nightlies are cm10.2 right? Your using the old recovery, that's the issue. And there are newer nightlies.
New recoveries
http://forum.xda-developers.com/showthread.php?t=2475802
Cm thread
http://forum.xda-developers.com/showthread.php?t=2459198
Click to expand...
Click to collapse
hey thank you for that. i've removed the old cwm recovery, flashed new, lots of other flashes, and it finally works again. now to dig up a non-corrupted backup and hopefully be back to working.
thanks button was used
well, after all of that i'm going to roll with cm-10.0, cwm 6.xomething, so i can have a working compass on oruxmaps.
i won't be updating until 10.x begins to support compass functions again.
see yall then !
ohgood said:
well, after all of that i'm going to roll with cm-10.0, cwm 6.xomething, so i can have a working compass on oruxmaps.
i won't be updating until 10.x begins to support compass functions again.
see yall then !
Click to expand...
Click to collapse
Make sure you use the latest cm10 nightly, as the old stable one is a lot less "stable" than the name suggests, and is lacking features
Romman0 said:
Make sure you use the latest cm10 nightly, as the old stable one is a lot less "stable" than the name suggests, and is lacking features
Click to expand...
Click to collapse
thanks for the tip !
i finally got all the corrupted files (or whatever was causing problems) rm'd from both the phone and sdcard.
as of yesterday i had CM-10.o + CWM 6.0.3.8 and gapps 2012-8 (i think) working nicely on the phone. backed up a nandroid of all of it two times, and restored them to make sure restores were working. yes, everything fine.
as of today, i have CM-10.2 (latest nightly) + CMW 6.0.3.8 and gapps (current) working nicely on the phone. backed CURRENT up nandroid on sdcard, and restored a few times to make sure. yes, working fine.
seems it was
A) corrupted files/filessystems
and/or
B) too old a clockworkmod recovery
C) unstable CM version( s )
but now all is fine. thanks to all that helped !