Related
I'm just wondering what's so good about the Modaco ROMS... From what I was reading it's the best thing to ever happen to Hero but I've flashed it and it actually seems slower/laggier than my stock ROM... should this be?
My stock ROM was 2.73.XX but I can't remember the exact build number. I'm using Modaco 3.0... are there any other ROMS out there I should consider trying? I'm looking for the fastest and most responsive ROM out there. I do A LOT of multitasking so I'd like to have a ROM that can keep up.
If you did a complete data wipe/factory reset, while having the Modaco Rom, the Hero should be a lot more responsive and faster.
I like Modaco rather than stock rom because it removes some useless apps and allows for more customization. Btw, another alterative to the stock and Modaco is the [email protected] and the Clean ION Roms.
There are several different Roms, the differences is the types of apps removed/installed and the Android firmware.
i like modacos roms, because they work reliable and good. with pauls roms i am sure that he has tested them well, and i can use them as basis for my own modifications, or just can push them to my friends' heros without having them complain that something doesn't work. also in case you need support you can ask paul, he is really a nice guy.
there are some other roms, but imho mcr3.0 is by far the most evolved rom, esp. for everyday use. check the development section here for other roms, including the brandnew android 2.1 roms
Well here's the thing. I didn't wipe/factory reset before I Flashed the ROM. After flashing it went into a reboot loop, it would keep rebooting and when it got to the last boot animation, reboot again... I then did a wipe using the recovery boots wipe option and then it booted fine... Maybe I should do another wipe and flash again? It sucks though because now I've customized it back to the way I like it... I hate having to do that all over again. I guess I need to do the A2SD thing so I don't have to redownload my apps again... that was annoying when I had to do it after flashing Modaco's.... I couldn't even remember all that I had installed lol.
Anyone think reflashing might make it better?
I've been using MCR since about 2.2 so I can't speak for 3.0, but when I first flashed with 2.2 I didn't factory reset or format my SD card and it was a complete fail... apps force closing constantly, unable to recieve SMS, and other assorted weirdness.
So I factory resetted, reflashed and from that point MCR has run very smoothly and each update has gone OK (except for one where i had to format and repartition my SD card for A2SD, but didn't lose any settings).
So my advice would be that if you go to the effort of starting with a clean slate you'll get a much better user experience, which is what all us existing MCR users have...
streetdaddy is spot on. Do a clean wipe and then a rom flash.
I'm using MoDaCo 2.9. For my Hero, 3.0 ate up a lot of my phone's internal memory and kept saying I was running out of memory. The differences are minuscule and the speed improvement is about the same.
I started using Pauls ROM as soon as I got my Hero (which was a few days after release) because the stock ROM was toilet, and I've not looked back. The ROM itself is excellent and the support is first-class.
Make sure to wipe before installing. Once you've got it up and running you shouldn't have to wipe it when you upgrade next time.
Weird issue...
Doesn't matter which rom, when I'm not on stock, my phone will freeze...
I have used odin and flashed one click root, clockwork mod then installed different kernels, roms and with same result. It will freeze eventually until I pull the battery... am I doing something wrong here?
I mean, I completely wiped using Odin so I don't see the residual thing here.
And in case there are, I wiped data, cache, dalvic prior to flash or followed chefs instructions to the T.
Am I the only one that's experiencing this? (probably am T_T)
Any inputs would be appreciated.
Same here. I've found that its the custon kernels that cause it. I just flash the rom I want and then flash the stock kernel back.
Sent from my Epic 4G using the power of the Holy Spirit
Hey, thanks for writing to confirm. good to hear that I'm not the only one but sucks to be one of the few...
I have done multiple wipes, cache clearing (both cache and dalvik)
Gone fresh from di18 fresh install, rooted and unrooted (I heard that old 1 click conflicts with genius dog's kernel) I have come to conclusion that it's the under voltaging that's the culprit here... I may be wrong but what kinda grinds my gears is that why is that only you and me are having these issues?
I'm using Andromeda kernel and it seems to be stable for me.
Any ways around this ??
I just recently started having this problem. I never had it until the day I flashed bakedsnack 1.3. The ROM is wonderful besides the occasional freezing. I usually freeze up about 2 times a day and have to pull the battery. This ROM does use a custom kernel though and I was OC'd to 1.3ghz but reflashed and went to 1ghz and still freezing.
Have you tried OC kernel before? i.e. genius dog's kernel. (not dogging Genius dog or anything. I'm naming his because his kernel is most widely used and I'm dying to use it.)
Just want to try to eliminate the culprit here lol.
Also try flashing andromeda kernel and see if your problems persists because I'm having no problems however my mflops will never go over 8.5 T_T
Alright, this issue has seriously driven me insane over the last few days, and today it's gotten to the point where I'm going to do something I'll regret if somebody can't help me out. As you can tell, I'm pretty desperate.
Using Fresh 3.5.0.1, I've encountered more reboots than I can count. Whether it's checking an email or playing Asphalt, the phone frequently decides it doesn't want to cooperate and restarts itself. I decided to try to get rid of the reboots for good today with a complete wipe and new rom.
First, I made a nandroid backup, followed by a data/system wipe and cache/dalvik cache wipe. Afterward, I flashed the ZenDroid 1.1.0 kernel in case that was the issue. I then proceeded to flash CyanogenMod 7 RC1 with gapps.
That worked for all of three minutes, and then it got even worse. The phone started restarted itself when I wasn't even doing anything, up to the point where it would restart on the CM7 boot animation. I took my rage out on a nearby pillow and decided to try something else.
I downloaded the final release MIUI rom and used Calkulin's format all to wipe my phone as instructed. This time around I flashed Savage-Kernel 1.6 along with MIUI. Lo and behold, after rebooting I was finally able to swipe through the home screens again.
And then I wasn't. It started rebooting on the boot animation again. At the moment it's even worse, rebooting three seconds into the damned splash screen. I've tried keeping the battery pulled for half an hour with the HTC battery and two after market batteries. I wiped the ext partition on the micro sd card. I even physically removed the card itself. This effing phone is still rebooting on the splash screen.
I'm at the end of my wits. All I want is for my Evo to WORK, without any constant reboots or force closes that make it utterly unusable outside. If anyone could help me out with this issue, I'd be extraordinarily grateful.
Mecha2142 said:
Alright, this issue has seriously driven me insane over the last few days, and today it's gotten to the point where I'm going to do something I'll regret if somebody can't help me out. As you can tell, I'm pretty desperate.
Using Fresh 3.5.0.1, I've encountered more reboots than I can count. Whether it's checking an email or playing Asphalt, the phone frequently decides it doesn't want to cooperate and restarts itself. I decided to try to get rid of the reboots for good today with a complete wipe and new rom.
First, I made a nandroid backup, followed by a data/system wipe and cache/dalvik cache wipe. Afterward, I flashed the ZenDroid 1.1.0 kernel in case that was the issue. I then proceeded to flash CyanogenMod 7 RC1 with gapps.
That worked for all of three minutes, and then it got even worse. The phone started restarted itself when I wasn't even doing anything, up to the point where it would restart on the CM7 boot animation. I took my rage out on a nearby pillow and decided to try something else.
I downloaded the final release MIUI rom and used Calkulin's format all to wipe my phone as instructed. This time around I flashed Savage-Kernel 1.6 along with MIUI. Lo and behold, after rebooting I was finally able to swipe through the home screens again.
And then I wasn't. It started rebooting on the boot animation again. At the moment it's even worse, rebooting three seconds into the damned splash screen. I've tried keeping the battery pulled for half an hour with the HTC battery and two after market batteries. I wiped the ext partition on the micro sd card. I even physically removed the card itself. This effing phone is still rebooting on the splash screen.
I'm at the end of my wits. All I want is for my Evo to WORK, without any constant reboots or force closes that make it utterly unusable outside. If anyone could help me out with this issue, I'd be extraordinarily grateful.
Click to expand...
Click to collapse
hmm...
i don't know what kernel fresh comes with, but both of the other kernels are more aggressive ones, and i would guess your phone doesn't like them. i would try this:
Wipe twice using calk, wipe again using recovery, flash mikfroyo or stock rooted (stock kernel). If you still get reboots... unroot and take your phone back in because its a hardware problem.
I had this problem. Drove me insane. Ultimately just unrooted and got a new one from sprint. Not one reboot since I got the new one.
Sent from my PC36100 using XDA App
Well I'm still super new to the whole flashing of the ROM's. But from what you have explained the only thing I can think of is that you missed a step when you rooted your phone. Because of this that is why your phone keeps brick. You should go and check out HTC EVO Hacks (go Google it) and the guy who runs the site made a sweet video & write-up on how to root your phone. Just re-do everything and follow directions, then when your done just flash Kings Unleashed. And when you check out the HTC EVO hacks root page look for the link to the XDA root forum which has more info on how to root your HTC the proper way.
Sent from my PC36100 using XDA App
aimbdd said:
hmm...
Wipe twice using calk, wipe again using recovery, flash mikfroyo or stock rooted (stock kernel). If you still get reboots... unroot and take your phone back in because its a hardware problem.
Click to expand...
Click to collapse
Yeah, I guess I should try the stock rooted rom. If I'm only able to use that instead of any other custom rom, though, I'm going to lose it. There's something inherently frustrating about a device refusing to work for no apparent reason.
chickut123 said:
I had this problem. Drove me insane. Ultimately just unrooted and got a new one from sprint. Not one reboot since I got the new one.
Click to expand...
Click to collapse
I'm sort of hoping I won't have to do that, considering I'll likely get a refurbished unit.
Fredrow425 said:
But from what you have explained the only thing I can think of is that you missed a step when you rooted your phone. Because of this that is why your phone keeps brick. You should go and check out HTC EVO Hacks (go Google it) and the guy who runs the site made a sweet video & write-up on how to root your phone. Just re-do everything and follow directions, then when your done just flash Kings Unleashed. And when you check out the HTC EVO hacks root page look for the link to the XDA root forum which has more info on how to root your HTC the proper way.
Click to expand...
Click to collapse
I'm pretty sure that isn't the case at all. If there was an issue with the way I rooted my phone, it would have been present eight months ago when I bought it. This rebooting issue is relatively new, and it isn't bricked. I appreciate the advice, though.
It could be just a defective phone - memory isn't immortal or impervious to defects.
I'd downgrade to a Sprint ROM, and keep it stock and see how that works. You have to rule out bad hardware first, and that's the only way to do it.
I agree on all of your guys suggestions but one thing i noticed was that he said he wiped data then dalvic cache then he said he flashed the kernel then the rom. Maybe he should try and rewipe everything with calk format all then flash the rom and reboot. Then go back into recovery and flash your new kernel then reboot again and see whats up from there.
Have you tried repartitioning your SD card and formatting? I was getting random reboots on every single rom I tried, and every single kernel. Turns out my partitions somehow got messed up on my SD card and that was causing it randomly. Now I have no reboots.
akrod2as said:
Have you tried repartitioning your SD card and formatting? I was getting random reboots on every single rom I tried, and every single kernel. Turns out my partitions somehow got messed up on my SD card and that was causing it randomly. Now I have no reboots.
Click to expand...
Click to collapse
Yes, I first formatted the sd card in Windows and then partitioning it on the phone's recovery. Still no luck.
Yeah... Sprint rom or if you go through with the unrooting process (I forgot how...) then you can figure out if it is hardware.
But yeah, endless reboots are frustrating.
If Sprint rom is giving you troubles, then just return it and get a new one. It's gotta be hardware then.
Also you could try running stock rooted without any downloaded market apps. Just run what came with the phone.
You can also try stock rooted eclair 2.1
Mine started the reboot bs after the december update. Mine seems to reboot when I use it heavily even though I'm not overclocked (heats up). Before the 2.2 update, it was very fussy being outside during the summer. I would like to exchange mine for another, even though I don't use it anymore. It would be nice to have a fully functioning backup. My gf's daughter wants the evo very much. Even if I would do that, which I wouldn't, I wouldn't let someone use a possibly unstable phone. If an emergency happened, and the phone started it's rebooting bs, it would be very bad to not be able to use the phone when you need it the most.
I am guessing I would have to reactivate the evo, run it for a month or so, unroot and lock it, then take it to a service center and see if I can make it start rebooting like crazy. Maybe I will get lucky and they would give me another one. I don't care too much if it is a refurb as long as it is in good shape and works good.
Try removing the SD card and booting.
Sent from my PC36100 using XDA App
rebooting
I had this same problem with my evo. Sometimes it would be ok, but then others it wouldnt stop doing it, didnt matter what I did. It could be sitting by itself and I would hear it rebooting. Drove me mad!!!
My first evo was awesome, it was a hardware ver 3. My camera lens cracked and the gave me a refurb, hardware version 2. This is when my reboots started happening.
After 3 batteries from Sprint and two more refurbs I finally blew in front of a store full of customers telling them that either give me a NEW evo, hardware version 3 like I originally had with no problems or it was going against their wall.
I havent had one problem since.
I wasnt rooted yet so cant comment along those lines but if you take it back to stock and it still does it I recommend throwing it at one of Sprints walls. No need to do any drywall patching at your place LOL.
I hope you get it resolved as I can feel your pain!
It may not be hardware. Did you restore any apps using any back up app (Titanium Backup) after flashing the AOSP roms? If so, make sure you did NOT restore any system apps or data. This is especially important when you go from Sense to AOSP.
The test is what everyone is suggesting. Flash back to Sprint rom and see what happens.
Also, you need to flash the kernel after flashing the rom, otherwise you'll just get the kernel packaged with the rom. I usually reboot and art least try the default kernel unless I know that my phone hates it.
bigmoogle said:
It may not be hardware. Did you restore any apps using any back up app (Titanium Backup) after flashing the AOSP roms? If so, make sure you did NOT restore any system apps or data. This is especially important when you go from Sense to AOSP.
The test is what everyone is suggesting. Flash back to Sprint rom and see what happens.
Also, you need to flash the kernel after flashing the rom, otherwise you'll just get the kernel packaged with the rom. I usually reboot and art least try the default kernel unless I know that my phone hates it.
Click to expand...
Click to collapse
No, I haven't even been able to get to the stage of installing any apps before the rebooting cycle starts again. I tried installing the stock Sprint rom this morning with the stock radios and kernel and it was stable for about five minutes. It's back to rebooting again, though.
Do you guys think it's time to unroot and go to the Sprint store for an exchange?
Mecha2142 said:
No, I haven't even been able to get to the stage of installing any apps before the rebooting cycle starts again. I tried installing the stock Sprint rom this morning with the stock radios and kernel and it was stable for about five minutes. It's back to rebooting again, though.
Do you guys think it's time to unroot and go to the Sprint store for an exchange?
Click to expand...
Click to collapse
If it was me, I would take it back. I just downloaded the newest ruu and will flash it later tonight. The only thing I'm worrying about is they won't be able to reproduce the problem. I really have to be multitasking a lot and pushing the phone hard. Actually the last time it had rebooting fits was with wireless tether running. The back of the phone was warm. I put it in front of the ac vent in the car for a minute or two and that seemed to help it stop rebooting.
herbthehammer said:
If it was me, I would take it back. I just downloaded the newest ruu and will flash it later tonight. The only thing I'm worrying about is they won't be able to reproduce the problem. I really have to be multitasking a lot and pushing the phone hard. Actually the last time it had rebooting fits was with wireless tether running. The back of the phone was warm. I put it in front of the ac vent in the car for a minute or two and that seemed to help it stop rebooting.
Click to expand...
Click to collapse
Well, it looks like I'll be taking it to the store after all. I just finished unrooting my phone with the RUU, so it's as if I had never touched the software. Lo and behold, the damned thing still rebooted a minute into using the phone.
I guess that in some sick way, I can consider myself more 'fortunate' than you, seeing as how my phone doesn't even need to be used in order to begin rebooting. It's ridiculous that I have to part with my Evo because of this bs.
Mecha2142 said:
Well, it looks like I'll be taking it to the store after all. I just finished unrooting my phone with the RUU, so it's as if I had never touched the software. Lo and behold, the damned thing still rebooted a minute into using the phone.
I guess that in some sick way, I can consider myself more 'fortunate' than you, seeing as how my phone doesn't even need to be used in order to begin rebooting. It's ridiculous that I have to part with my Evo because of this bs.
Click to expand...
Click to collapse
Did you even try removing the sd card and booting the phone?
Same thing happend with my old evo it started after i install one of the first cm safe roms not nightlies not saying tyat was the cause, i tried evverything wiping unrooting botting without sd, ive been on android sice g1 and i tried everything nothing worked, ended up going to sprint and getting another refurnished it was prolly hardware issue maybe cpu overheating or something, anyways not sure why ppl are so scared of refurnished phones i believe they do a lot more tests on those phone than retail ones lol
akrod2as said:
Did you even try removing the sd card and booting the phone?
Click to expand...
Click to collapse
Yes. I've already said I tried booting the phone without the sd card several times now without success.
I've re-installed Atrix 4 times on my phone, each time doing a factory reset, clearing cache, and Dalvik cache. I've had random reboots/shutdowns on every install of Alien Build #4 and Aura 1.1.3.8. One running Atrix stock kernal, 2 using faux's kernal 0.1.6 (one non-oc, one oc), and one using faux's OC 0.1.7. Now I'm running Aura 1.1.3 Build #8 Deblurred. All with random reboots and shutdowns.
I've noticed I never get a random reboot while I'm charging, only while on battery. I've calibrated my battery several times so it's not lack of juice. Sometimes it just reboots, other times it shuts down and doesn't reboot so I have to turn on the phone, though most of the time the screen won't turn on and the phone won't shut off so I have to take out the battery to turn on the phone. I've tried uninstalling SetCPU, disabling profiles, and setting the max clock to 1000mhz. None of this helped.
On the last Alien install (now I'm running Aura) I was having even more problems but they only happened on that install:
1. I got an error when trying to boot in red: "Unrecoverable Bootloader error (0x00000004)" though I was able to turn the phone off and reboot normally.
2. I got an error about 5 times in a row while trying to boot, I forgot the exact text but something along the lines of "Unable to load radio module (0)". I had to take out the battery and try about 5 times till it would boot properly.
3. After this, I was unable to boot into Recovery through the volume buttons, I'd press down till I got the Android Recovery, then press up and it'd hang there. It works now for some reason.
I installed Alien right when I got my phone so I'm unsure if random reboots happen stock. Also my phone gets really warm when I'm using it, I look in SetCPU and the CPU temp is anywhere from 42 to 57 C. Does anyone else's phone get this hot?
I would just take it back to Best Buy and get a new one cause I have a protection plan with them, but my phone is unlocked which voids the warranty.
Does anyone know what could be causing all of these issues and how to fix them?
Thanks for the help, XDA is great!
Im by no means a expert...but I'm currently running AURA 1.1.3#8 debloat and all is well on my phone....I would recommend performing a Ti backup on ur aps and doing a factory reset to see if the problem persists....if it does I would take it back...if not reinstall through CWM wiping devalk cache then a full data wipe then install AURA and reboot all in CWM ....btw I'm running Rom Racers CWM also. Hope you can get it figured out!
JRW 28 said:
Im by no means a expert...but I'm currently running AURA 1.1.3#8 debloat and all is well on my phone....I would recommend performing a Ti backup on ur aps and doing a factory reset to see if the problem persists....if it does I would take it back...if not reinstall through CWM wiping devalk cache then a full data wipe then install AURA and reboot all in CWM ....btw I'm running Rom Racers CWM also. Hope you can get it figured out!
Click to expand...
Click to collapse
I would have just taken it in but my phone is unlocked, rooted, and using Romracers CWM so I doubt Best But will accept it. I've tried all of this. I'm going to try CM7 Beta2, if the problem still persists I don't know what to do cause Best Buy won't accept it when they see the Unlocked at the top of the bootloader. It works fine when it's charging but so far no matter what I've tried I always got reboots. Does your phone get hot? Can you check what temps you get in SetCPU? Thanks for the suggestions btw.
My phone has never gotten over 33*....Try going back to stock gingerbread and see if the problems persist there and if not then u can proceed forward.....that way you can rule out if the problem is the phone or a certain build and a bug you have picked up
Sorry I meant 39* on phone temp
I went into my settings>widow and turned it off then rebooted, seemed to work, I also would get random reboots after a fresh install. Like at least 20x. But try that. Worked for me.
Sent from my MB860 using XDA App
JRW 28 said:
My phone has never gotten over 33*....Try going back to stock gingerbread and see if the problems persist there and if not then u can proceed forward.....that way you can rule out if the problem is the phone or a certain build and a bug you have picked up
Click to expand...
Click to collapse
33? Wow, my phone never goes below 42C, it's usually around 49-50C. How do you return to stock gingerbread like the phone came with? All I've found was flashing the SBF through RDA, is there any way to do it with CWM so it's safer? Sorry for the noobiness, I'm new to the Atrix, is there a way to completely restore the phone to stock (stock gingerbread, locked bootloader, no CWM)?
Edit: I just flashed CM7 pre-beta 2, going to see how this works, hopefully it fixes my problems.
performing a data wipe/factory reset in CWM should put you completely back to stock. It wont matter that you have a UL bootloader or rooted.
Ecstacy42 said:
I've re-installed Atrix 4 times on my phone, each time doing a factory reset, clearing cache, and Dalvik cache. I've had random reboots/shutdowns on every install of Alien Build #4 and Aura 1.1.3.8. One running Atrix stock kernal, 2 using faux's kernal 0.1.6 (one non-oc, one oc), and one using faux's OC 0.1.7. Now I'm running Aura 1.1.3 Build #8 Deblurred. All with random reboots and shutdowns.
I've noticed I never get a random reboot while I'm charging, only while on battery. I've calibrated my battery several times so it's not lack of juice. Sometimes it just reboots, other times it shuts down and doesn't reboot so I have to turn on the phone, though most of the time the screen won't turn on and the phone won't shut off so I have to take out the battery to turn on the phone. I've tried uninstalling SetCPU, disabling profiles, and setting the max clock to 1000mhz. None of this helped.
On the last Alien install (now I'm running Aura) I was having even more problems but they only happened on that install:
1. I got an error when trying to boot in red: "Unrecoverable Bootloader error (0x00000004)" though I was able to turn the phone off and reboot normally.
2. I got an error about 5 times in a row while trying to boot, I forgot the exact text but something along the lines of "Unable to load radio module (0)". I had to take out the battery and try about 5 times till it would boot properly.
3. After this, I was unable to boot into Recovery through the volume buttons, I'd press down till I got the Android Recovery, then press up and it'd hang there. It works now for some reason.
I installed Alien right when I got my phone so I'm unsure if random reboots happen stock. Also my phone gets really warm when I'm using it, I look in SetCPU and the CPU temp is anywhere from 42 to 57 C. Does anyone else's phone get this hot?
I would just take it back to Best Buy and get a new one cause I have a protection plan with them, but my phone is unlocked which voids the warranty.
Does anyone know what could be causing all of these issues and how to fix them?
Thanks for the help, XDA is great!
Click to expand...
Click to collapse
Are you doing a factory data/reset wipe cache and wipe dalvik step after you install a new rom? Do the same wipe steps before and after rom flash. If you are doing this then it sounds like a hardware problem or your bl got thrashed unlocking it.
Sent from my MB860 using xda premium
Ecstacy42 said:
33? Wow, my phone never goes below 42C, it's usually around 49-50C. How do you return to stock gingerbread like the phone came with? All I've found was flashing the SBF through RDA, is there any way to do it with CWM so it's safer? Sorry for the noobiness, I'm new to the Atrix, is there a way to completely restore the phone to stock (stock gingerbread, locked bootloader, no CWM)?
Edit: I just flashed CM7 pre-beta 2, going to see how this works, hopefully it fixes my problems.
Click to expand...
Click to collapse
Go the fruitcakes thread in the developement section. Stock cwm flashable builds.
Sent from my MB860 using xda premium
JRW 28 said:
performing a data wipe/factory reset in CWM should put you completely back to stock. It wont matter that you have a UL bootloader or rooted.
Click to expand...
Click to collapse
It will only reset to the current rom defaults. If you have cm7 or alien flashed, It will revert back cm7 or alien. Doesn't effect root or bootloader. If the rom is pre rooted it stays rooted even after a full wipe.
Sent from my MB860 using xda premium
Dirtburgler said:
Are you doing a factory data/reset wipe cache and wipe dalvik step after you install a new rom? Do the same wipe steps before and after rom flash. If you are doing this then it sounds like a hardware problem or your bl got thrashed unlocking it.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
That sounds highly possible as it happens with each install and I am doing a factory reset, cache wipe, and dalvik cache wipe with each install. If ran the unlocking script again would it erase the bootloader and re-install it to fix that?
Edit: I just got another "Unrecoverable Bootloader error (0x00000004)" error, I'm going to re-run the script.
Ecstacy42 said:
That sounds highly possible as it happens with each install and I am doing a factory reset, cache wipe, and dalvik cache wipe with each install. If ran the unlocking script again would it erase the bootloader and re-install it to fix that?
Edit: I just got another "Unrecoverable Bootloader error (0x00000004)" error, I'm going to re-run the script.
Click to expand...
Click to collapse
No don't. The script doesn't update the boitloader I don't think. Did you use the ota to get gingerbread?
If the bl is fubared and your not on the legit ota you can rsd to 1.83 and start over. If you are on the ota update then all you can use is cwm(safely)
Sent from my MB860 using xda premium
when I was on Ninja SF I performed a factory reset and forgot to perform a backup and it took me back to completly stock gingerbread....sorry if I was misleading him
Dirtburgler said:
No don't. The script doesn't update the boitloader I don't think. Did you use the ota to get gingerbread?
If the bl is fubared and your not on the legit ota you can rsd to 1.83 and start over. If you are on the ota update then all you can use is cwm(safely)
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
My phone came shipped with 2.3.4 Gingerbread, I never used the OTA update. I re-ran the script and got another random reboot.
Edit: I'm flashing the official 2.3.4 SBF from here: http://forum.xda-developers.com/showthread.php?t=1125944
I'll let you all know how things went.
From what I understand ...once u are on 2.3.4 if u try to flashback to. 83 it will hard brick you...definitely flash back to stock gingerbread 2.3.4 and hopefully that will solve your problems ....good luck
I installed Aura 1.1.3 Debloat #7 two days ago and my phone rebooted by itself today. I had it in my pocket, then I took it out and it was loading. I thought I might have pushed something when moving, but maybe it is related to the rom.
Okay, I flashed 2.3.4 with pudding boot loader unlocked and Romracer CWM Recovery. I'm going to install Alien and faux's kernal, hope flashing 2.3.4 fixed this and it's not a hardware issue.
Did you experience any problems while you were on 2.3.4 or did you flash straight to alien afterwards ...hope you get your problems figured out! Make a backup of the 2.3.4 flash also so if you do experience any problems you can always flash back
JRW 28 said:
Did you experience any problems while you were on 2.3.4 or did you flash straight to alien afterwards ...hope you get your problems figured out! Make a backup of the 2.3.4 flash also so if you do experience any problems you can always flash back
Click to expand...
Click to collapse
I flashed straight to Alien when I got the phone so I'm not sure it stock Gingerbread had problems. I just flashed 2.3.4 with pudding unlocked bootloader, Romracer's CWM, and finished installing Atrix Build 4 and faux's kernal 0.1.7. I'm going to take the phone off the charger (I only get reboots and shutdowns while on battery), and start installing my apps, restoring contacts, messages, and see if I have any problems. I'm not going to install SetCPU and mess with profiles and undervolting till I know I'm good.
I'll report how it's going tomorrow morning (usually by that time I get at least 5 to 10 random reboots/shutdowns). If this doesn't fix it then I'm going to flash the stock 2.3.4 SBF so they don't know I messed around with the device and take it back to Best Buy to get a replacement.
Hey guys,
I recently tried flashing the Team Hacksung ICS port, Gummy Fascinate, and AOSPK and they all have the same issues for me. I understand that these are in an alpha state but none of the "Not Working" sections include the problems I am having. First, I cannot receive text messages but I can send them. Second, when exiting an app or the settings menu, the home screen takes five seconds to reset (all of the icons/dock are gone, only the wallpaper shows at first). Third, the launcher becomes incredibly slow after only a few minutes. I close out of all of the apps that are running using the new multitasking feature (holding the home button) but the phone remains sluggish until I reboot it. Then, it is lightning fast until I open any app. Fourth, scanning of my SD card seems to stop after a few seconds after booting. I have about 14 GB of music on my SD card and it only loads the first few artists. It does this every time I boot up so I can never see the entire library. Fifth, sometimes the app I am using will close and I am forced to wait for the home screen to reset, as I mentioned before. No error messages for force closing appears. Sixth (this is only a minor inconvenience but I want to understand why it happens), when I use SMS Backup + to restore my texts, the minute I leave the app or let the screen turn off, it returns to "Idle mode and I have to restart the entire process over again.
TL;DR I have a bunch of issues that other users don't seem to be having and they are not listed on the "Not Working" sections of the ROMs.
I would appreciate if anyone could help me come up with a solution to any one of these problems. I am looking forward to using ICS!
What method are you using to install ics based roms?
I flash back to stock EH03 and then follow these directions to the letter: http://exzacklyright.blogspot.com/2012/01/how-to-flash-ics-on-verizon-samsung.html
Those instructions are pretty good aside from the part in step 8 that suggests flashing the radio. It's already included in the EH03 package so it's just redundant, but those instructions are essentially the same as my procedure and I'm on build 6 without the issues you're experiencing (as are other people).
I'm curious if you have the same problems on other roms or is it just ICS? Have you ever messed around with overclocking and maybe got a bit aggressive? I know that if you're not careful and know what you're doing with the new overclocking and voltage control that are a part of glitch v14 you could certainly damage your phone. If it's just ICS roms and you've never messed with OC, I'm not really sure why you'd be running into those issues.
smokinbeanbean1992 said:
I flash back to stock EH03 and then follow these directions to the letter: http://exzacklyright.blogspot.com/2012/01/how-to-flash-ics-on-verizon-samsung.html
Click to expand...
Click to collapse
have you tried a different sd card?
I only have these problems on ICS. I don't flash EH03 everytime like it suggests in the instructions. My last SD card was fried by CM7 so this SD card is brand new and I'm pretty sure it's a class 10, so speed shouldn't be an issue. Could it really be the SD card that's causing these problems?
Sent from my SCH-I500 using XDA App
Also, I have messed around with glitch v14 and overclocking to attempt to alleviate the sluggishness and I used to use v12 and v13 with CM7 before with no issues. V14 did not help at all so I'm on the stock CM9 kernel and I have erased the voltage settings.
Sent from my SCH-I500 using XDA App
smokinbeanbean1992 said:
I only have these problems on ICS. I don't flash EH03 everytime like it suggests in the instructions. My last SD card was fried by CM7 so this SD card is brand new and I'm pretty sure it's a class 10, so speed shouldn't be an issue. Could it really be the SD card that's causing these problems?
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I didnt say it was the sd card, just simply asked if you have tried another...relax grasshoppa. If you dont follow instructions expect stuff not to work right.
Not sure if it will make a difference, but I ODIN and repartitioned to stock verizon DL09.. then CWM, wipe, build two, wipe, gummyfassy...
I have run into some strange issues when I reverted to another stock verizon package other than DL09 before flashing custom roms.. so out of superstitions sake, I always default to DL09.
elarson006 said:
Not sure if it will make a difference, but I ODIN and repartitioned to stock verizon DL09.. then CWM, wipe, build two, wipe, gummyfassy...
I have run into some strange issues when I reverted to another stock verizon package other than DL09 before flashing custom roms.. so out of superstitions sake, I always default to DL09.
Click to expand...
Click to collapse
I use to have to do the same thing when I was on the stock sd card. Pretty sure the op did not odin back to stock anything going by his last post. I agree tho it wouldnt hurt to try stock ed05 or dl09, but dl09 should no longer be necessary.
I wasn't angry or anything, I was just wondering if the SD could be a problem. I always flash back to the stock EH03 ROM before flashing ICS or CM7 but do you think I should go all the way back to DL09?
Sent from my SCH-I500 using XDA App
I don't think it would harm anything to go to a more previous version. Make sure you repartition using the .pit file when flashing in ODIN if coming from MTD rom
Every time i tried all the ICSs I odined to EH03 as my starting point, then odined CWM4 fixed for CM7, then I flashed ICS Hacksung 3 first......Reboot...Reboot into recovery, Flash ICS 6 [or what ever new flavor you would like] then flash Gapps 7.1....Reboot.... Enjoy
Start from scratch and you will be good to go.
Droidstyles is the man when it comes to guides!
Ok, so at what point do you personally wipe data/cache/dalvik? I flash to stock, flash CWM fixed, wipe all three, install THS build 2, reboot, wipe all three, flash ICS rom of choice, flash all three, install gapps 7.1, and reboot.
Sent from my SCH-I500 using XDA App
usually before you flash a full rom:
Odin EH03
LET THE PHONE BOOT
pop battery
Odin CWM4 for CM7
[three finger salute]
Wipe the three
Flash THS 3
Let Phone boot, then reboot to recovery using the power button [DO NOT 3 finger!!!!]
Wipe the three
Flash THS 6 [or any of the others, you dont need to flash all three just which ever your end game is, i recommend THS 6 not 6.1 for starters]
*No need to wipe or reboot in between these two*
Flash Gapps 7.1
Then reboot and enjoy
Ok I'll give that sequence a shot. Thanks for your help everyone!
Well I don't know what it was but my phone is working flawlessly now. Thanks again everyone!
There is a thanks button for this...
Ah yes, I forgot about that
smokinbeanbean1992 said:
Ah yes, I forgot about that
Click to expand...
Click to collapse
Pretty sure your issue came from wiping the 3 after you flashed ics.
Should go like this
after flashing build 2
Wipe the 3
Flash your choice ROM
Flash gapps
Reboot
Sent from my SCH-I500 using xda premium