Related
After installing Gingerth3ory and loving it, my friend then applied the speedtweak and i believe its in an undervolted setting that is causing the phone to powercycle. The phone cant go into recovery to reflash the rom to get rid of the tweak because the P50IMG.zip is still on the SD card, so HBOOT is trying to constantly update that. Is there any way to get rid of the tweak so he can boot up the phone?
Pull the SD card and delete the PG05IMG.zip either with another device or card reader
If you're bootlooping and you have the PG05IMG.zip radio file on your sdcard, the first thing you will need to do is get it off. Use an adapter so you can remove the file using a computer or place the sdcard in another phone and remove it that way. Either way, you need to get that file off to get to recovery to fix your bootloops.
Okay he was just able to get the PC to recognize the sd card and pulled the zip. If he reinstalls the rom will that negate the settings of the speedtweak?
Ch0s3n0n3 said:
Okay he was just able to get the PC to recognize the sd card and pulled the zip. If he reinstalls the rom will that negate the settings of the speedtweak?
Click to expand...
Click to collapse
It would help if we knew what the "speedtweak" you are speaking of actually is. Either way, he can flash the rom then try to boot. If it doesn't boot then boot back into recovery and wipe data/cache. Flashing just the rom will probably work though if they were just clock/voltage related tweaks.
Absolute_Zero said:
It would help if we knew what the "speedtweak" you are speaking of actually is. Either way, he can flash the rom then try to boot. If it doesn't boot then boot back into recovery and wipe data/cache. Flashing just the rom will probably work though if they were just clock/voltage related tweaks.
Click to expand...
Click to collapse
Sorry it was Script Fusion, and yes it was a undervolt and overclock tweak. I had him reflash and it seems all is well. I also told him to delete the Script zip until he reads further and learns about it. I really appreciate your help as I am fluent in Droid X not Thunderbolt lol.
Bad timing (almost a pun)
So far I'm having zero luck getting out of the boot loop. Tried hboot w/ the ROM as PG05IMG.zip in the root; no go. Tried wiping cash/data/dalvik in CWR; no go. Tried reflashing the ROM via CWR; reboots before it can complete the operation. Anything else I can try? I guess there's no way to get to the init.d file to wipe the changes made by speedtweak?
Tried the "Normal" setting in speedtweak and that's what started everything.
ProfEngr said:
So far I'm having zero luck getting out of the boot loop. Tried hboot w/ the ROM as PG05IMG.zip in the root; no go. Tried wiping cash/data/dalvik in CWR; no go. Tried reflashing the ROM via CWR; reboots before it can complete the operation. Anything else I can try? I guess there's no way to get to the init.d file to wipe the changes made by speedtweak?
Tried the "Normal" setting in speedtweak and that's what started everything.
Click to expand...
Click to collapse
bootloader flashing isn't for the rom. It needs to be flashed in CWR as you later tried. At this point, the only thing you should be naming PG05IMG.zip, placing on your sdcard, and flashing is a radio (if you need to upgrade). But even then, you should have a booting rom first (not mandatory but encouraged).
You are able to make it to recovery, wipe data/cache, and flash a rom? At what point does the flash fail and is there an error reason stated? If you're in recovery the only thing that should be "preventing" the rom from flashing is the rom itself. The speedtweak files should already be gone before the rom even starts flashing since at that point /data, /cache, and /system have already been wiped.
You could try manually wiping each of those partitions multiple times (which never made complete sense to me) or download another rom or another copy of the current rom and try flashing it.
I got help from an IRC chat. Reloaded the 'upgrade' PG05IMG from the Tbolt root thread via hboot. That got me back online to where I could reflash.
Just for reference though, it was rebooting itself about 30sec into the ROM flash after the ROM notes/info scrolled on the screen.
ProfEngr said:
I got help from an IRC chat. Reloaded the 'upgrade' PG05IMG from the Tbolt root thread via hboot. That got me back online to where I could reflash.
Just for reference though, it was rebooting itself about 30sec into the ROM flash after the ROM notes/info scrolled on the screen.
Click to expand...
Click to collapse
That is weird. A tweak script that forces you to reflash firmware from the bootloader to fix it? Hmm, I suppose I should look up what this SpeadTweak script actually does for future reference. Either way, glad you got it fixed.
Absolute_Zero said:
That is weird. A tweak script that forces you to reflash firmware from the bootloader to fix it? Hmm, I suppose I should look up what this SpeadTweak script actually does for future reference. Either way, glad you got it fixed.
Click to expand...
Click to collapse
No.. Speedtweak.sh is built into imoseyons kernels and it allows you to control your kernel frequencies and governor. You don't have to install via hboot to remove it, all you need to do is flash a new kernel, even one that has Speedtweak.sh would be fine because you need to activate it manually through terminal.
I'm not sure why the OP was rebooting in recovery, that's what all of the phones that were reported as bricks were doing, but they were also rebooting in hboot which the OP wasn't. Obviously it wasn't a brick, but the Speedtweak script doesn't need to be removed via hboot, and it's just weird that the OP was rebooting in recovery.
Sent from my ThunderBolt using XDA Premium App
joshnichols189 said:
No.. Speedtweak.sh is built into imoseyons kernels and it allows you to control your kernel frequencies and governor. You don't have to install via hboot to remove it, all you need to do is flash a new kernel, even one that has Speedtweak.sh would be fine because you need to activate it manually through terminal.
I'm not sure why the OP was rebooting in recovery, that's what all of the phones that were reported as bricks were doing, but they were also rebooting in hboot which the OP wasn't. Obviously it wasn't a brick, but the Speedtweak script doesn't need to be removed via hboot, and it's just weird that the OP was rebooting in recovery.
Sent from my ThunderBolt using XDA Premium App
Click to expand...
Click to collapse
If I understand your terminology, I need to make a clarification.
The phone was stuck in a loop that would make it as far as the 1st HTC boot screen, buzz, hang, then restart the sequence. I was only able to wipe in CWR. It would reboot shortly after starting a ROM flash. hboot still worked as normal.
I'll look into how to flash just a kernel in case this happens again (HOPE NOT!!!)
For another discussion... After I got things sorted and reflashed the MR2 radio, CWR gives me an error when trying to format /system during Nandroid restore of any of my previous backups.
joshnichols189 said:
No.. Speedtweak.sh is built into imoseyons kernels and it allows you to control your kernel frequencies and governor. You don't have to install via hboot to remove it, all you need to do is flash a new kernel, even one that has Speedtweak.sh would be fine because you need to activate it manually through terminal.
I'm not sure why the OP was rebooting in recovery, that's what all of the phones that were reported as bricks were doing, but they were also rebooting in hboot which the OP wasn't. Obviously it wasn't a brick, but the Speedtweak script doesn't need to be removed via hboot, and it's just weird that the OP was rebooting in recovery.
Sent from my ThunderBolt using XDA Premium App
Click to expand...
Click to collapse
It was my understanding from their posts that they couldn't even flash anything. If it's the kernel itself or even init or bash scripts then flashing the rom clearly would fix that but it does little good if your phone reboots before you can even flash something.
Still not clear on what caused the problems of the two users here but the common denominator was that SpeadTweak script which as I said, someone would need to review to determine what may be causing the problem.
Absolute_Zero said:
It was my understanding from their posts that they couldn't even flash anything. If it's the kernel itself or even init or bash scripts then flashing the rom clearly would fix that but it does little good if your phone reboots before you can even flash something.
Still not clear on what caused the problems of the two users here but the common denominator was that SpeadTweak script which as I said, someone would need to review to determine what may be causing the problem.
Click to expand...
Click to collapse
I'm by no means saying you're wrong or anything, I was just letting you know what the speedtweak.sh script was since you had mentioned you weren't completely sure. I'm also unsure as to what was amiss with their phones, I just noted that the people who had bricked their phones (via one way or another), were rebooting in recovery, and that's the only time I had heard of rebooting in recovery. Obviously his hboot was fine, it's just very strange that recovery was rebooting because from my understanding recovery uses a completely different kernel than the main ROM.
Nice(?) to know I have a few people scratching their heads over this. Probably won't work, but I'll try to keep out of trouble on this until someone posts what's up.
That sounds like the boot loop issue that people were having before the MR2 radio came out, doesn't it?
loonatik78 said:
That sounds like the boot loop issue that people were having before the MR2 radio came out, doesn't it?
Click to expand...
Click to collapse
If don't know what issue you mean, there was a bricking issue but this isn't a brick
Sent from my Transformer TF101 using XDA Premium App
joshnichols189 said:
If don't know what issue you mean, there was a bricking issue but this isn't a brick
Sent from my Transformer TF101 using XDA Premium App
Click to expand...
Click to collapse
What they were calling a brick really wasn't much of a brick by definition A) because all it did was boot loop, and B) it was recoverable.
I rooted my buddies phone for him pretty much so he could use wifi tether. Told him to make a nandroid before he does anything. He said he did. He called me this am and said he tried to flash an ics ROM from Scott's site and now his phone won't boot past the HTC screen. He said he tried to retire the backup but it didn't work nor did a factory reset.
Can I just get him to flash a GB based ROM and get him back to square one or must I get an ics ROM loaded up since he already tried to get that on there?
Can I just have him load the stock ruu for GB? Where can I locate that?
He might have forgot the pg98img?? I know it happened to me when i first had ics
What did you do to fix the problem? He has never flashed anything so he probably forgot something. Just trying to figure out what I need to do to fix his phone when I see him later tonight.
1967ls2 said:
What did you do to fix the problem? He has never flashed anything so he probably forgot something. Just trying to figure out what I need to do to fix his phone when I see him later tonight.
Click to expand...
Click to collapse
Countless threads on this...even the rom threads tell you what to do...
Sent from my ADR6425LVW using XDA App
nosympathy said:
Countless threads on this...even the rom threads tell you what to do...
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
Thanks for all the help, really appreciate it
Your "friend" (lol, j/k) should be able to do a battery pull, get back into recovery and then just start the process of flashing a new ROM again. Have him wipe the cache and dalvik cache first. I don't know why the nand won't restore, maybe he didn't make it properly?
Is he using Amon Ra? CWM was known to be buggy on this phone, don't know if that has been addressed. If he's using CWM then maybe he should switch to Amon Ra. iirc it can also restore a nand made in CWM.
feralicious said:
Your "friend" (lol, j/k) should be able to do a battery pull, get back into recovery and then just start the process of flashing a new ROM again. Have him wipe the cache and dalvik cache first. I don't know why the nand won't restore, maybe he didn't make it properly?
Is he using Amon Ra? CWM was known to be buggy on this phone, don't know if that has been addressed. If he's using CWM then maybe he should switch to Amon Ra. iirc it can also restore a nand made in CWM.
Click to expand...
Click to collapse
Thanks for the reply. My rezound is running smoothly! My buddy should have hit me up before trying to flash anything but he didn't. I'm running Amom but when I tried to install it on his phone it wouldn't take so I installed cwm. He said he made a backup but it won't restore. I will try to install Amon again on his phone and see if I can get his back up to work. I have a nand on my phone off the stock ROM. Do you think I can use my sd card in his phone and try to restore that or is it phone specific? I wouldn't think it is though
I don't know about restoring someone else's nand.
Also, if he gets a mainver error check out this thread:
http://forum.xda-developers.com/showthread.php?t=1459347
But if you flash in fastboot you don't have to worry about mainver, it will flash no problem.
You can find out what mainver the phone is on in fastboot using the following command:
fastboot getvar all
i know there are many tpics similar but i cant find a straight answer or working link..
basically i flashed a rom and this rom ws working fine until it started to reboot everytime i chargd the phone then it would boot loop for like 30min and finaly go in to the rom.. ive tried to access the recovery to switch roms but it just bootloops.. onlything i can go is to bootloader.. i was looking for a stock rooted
P0g5?? file to flash in bootloader but all i can find is mr2 and its in multiupload which is not working for me.. can anyone please give me a working link or answer... and the last option i would hate to do is completely restore to stock and root allover again.. i want to restore to stock rooted/s-off.. not stock rooted/s-on.. please help anyone....
Can u download a new recovery, rename, then flash in hboot possibly?
Sent from my ADR6400L using XDA
I had an issue kinda similar like this and ended up having to flash the RUU through the bootloader. It is the stock firmware 605.19, and I had to reroot. It's a pain I know but it works
Sent from my ADR6400L using xda premium
dizzyman1180 said:
I had an issue kinda similar like this and ended up having to flash the RUU through the bootloader. It is the stock firmware 605.19, and I had to reroot. It's a pain I know but it works
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
I to had to this at one point and it does work. I would first try to flash cwm in fastboot though. Sometimes that works.
Sent from my ADR6400L using Tapatalk 2
My friend's phone tried to pull an OTA while he had CWM recovery installed, and it started boot looping. Had to download the stock recovery, name is PG05IMG.zip in the root of the SDCard, and force the phone to boot to the bootloader and install it. Once it did, the phone started up, rebooted itself, and installed the OTA fine. Sounds like yours may be trying to do something similar?
If so rooted phones need caches cleared for the ota to work.
Sent from my ADR6400L using Tapatalk 2
From my understanding, Rooted can still take OTA, but you have to have stock recovery to do it (as I witnessed earlier). You will lose root, and will have to re-flash recovery to TWRP, CWMR, or whatever your normal choice is, and then re-apply the su.zip, but otherwise easy as pie.
Tiezane said:
My friend's phone tried to pull an OTA while he had CWM recovery installed, and it started boot looping. Had to download the stock recovery, name is PG05IMG.zip in the root of the SDCard, and force the phone to boot to the bootloader and install it. Once it did, the phone started up, rebooted itself, and installed the OTA fine. Sounds like yours may be trying to do something similar?
Click to expand...
Click to collapse
Do you by chance have a working link to the stock recovery? I have been trying to find one without success.
Sent from my ADR6400L using xda premium
I won't be home to later, I'll get it to you then, but I'm piety sure I found it through thunderboltforums.com
Sent from my ADR6400L using XDA
Tiezane said:
I won't be home to later, I'll get it to you then, but I'm piety sure I found it through thunderboltforums.com
Sent from my ADR6400L using XDA
Click to expand...
Click to collapse
I would appreciate that. Thank you
Sent from my ADR6400L using xda premium
dizzyman1180 said:
I would appreciate that. Thank you
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
Stock recovery PG05IMG.zip http://dl.dropbox.com/u/61129367/PG05IMG-Stock-Recovery.zip
Hello, first of all I would like to thank everyone who has posted in this thread to try and help out. I just started having a very similar problem- I'm rooted and running stock, but apparently my phone accepted an OTA and I'm stuck in a bootloop as well.
I got into CWM recovery and downloaded the stock recovery PG05IMG.zip, but it won't install. It just aborts every time I try to install it. I'm a noob at this stuff and not very good at dealing with these sorts of things and I've been having a panic attack for the past hour, so if anyone could help me as soon as possible I would really appreciate it.
I'm really scared of making things worse than they already are. I just want a working phone.
trter10 said:
Stock recovery PG05IMG.zip http://dl.dropbox.com/u/61129367/PG05IMG-Stock-Recovery.zip
Click to expand...
Click to collapse
Much appreciated my friend.
Sent from my ADR6400L using xda premium
pull battery, wait a minute, turn on phone
when in bootloader screen,
volume down, select reboot
back to white screen, select recovery ( i had to do this twice)
hold volume up and power when black screen appears
choose the bottom option (wipe cache i believe)
choose reboot
phone should be good aftter this
( idont own a thunderbolt, but i had to fix this for a nother phone, called tech support and this worked)
hope this helps - hopefully saves someone from ruu'ing and wiping their phone
Thank you for posting the file, life got in the way yesterday. Hope that fixes your situation!
Sent from my ADR6400L using XDA
webermn15 said:
Hello, first of all I would like to thank everyone who has posted in this thread to try and help out. I just started having a very similar problem- I'm rooted and running stock, but apparently my phone accepted an OTA and I'm stuck in a bootloop as well.
I got into CWM recovery and downloaded the stock recovery PG05IMG.zip, but it won't install. It just aborts every time I try to install it. I'm a noob at this stuff and not very good at dealing with these sorts of things and I've been having a panic attack for the past hour, so if anyone could help me as soon as possible I would really appreciate it.
I'm really scared of making things worse than they already are. I just want a working phone.
Click to expand...
Click to collapse
The zip won't work in CWM because it's not designed for use with CWM. It's designed for use in Fastboot. Should be on the root of your sd card. From off, if I'm correct (like this with other HTC devices), hold volume down and power to boot into fastboot. This will allow it to flash the stock recovery.
dlamber7 said:
The zip won't work in CWM because it's not designed for use with CWM. It's designed for use in Fastboot. Should be on the root of your sd card. From off, if I'm correct (like this with other HTC devices), hold volume down and power to boot into fastboot. This will allow it to flash the stock recovery.
Click to expand...
Click to collapse
Right. I also have a recovery zip that installs the stock recovery if anyone wants it?
It can be found here: http://dl.dropbox.com/u/61129367/OTARestoreAndRecovery.zip
(warning: I have tested it and it works but it did cause me a bootloop, and im assuming this is becuase im on a different rom - - - so not responsible for any damages)
HELP
My battery went tits up the other day so I had to purchase a new battery.....Ended up with HTC extended battery.(all verizon had in stock). When I put the battery in and powered on it just pops up with the HTC screen....couple secs go by the phone vibrates....HTC again......I can get the phone into bootloader.....but for the life of me can only get fastboot to work.....I have tried pushing cwm through that as well as the img above with no luck.....The Hboot only shows my device as android 1.0 and is unrecognized.I have reloaded drivers and everything I know how....Someone please help
Windows 7 64 bit ultimate
Rooted Thunderbolt running Thunderstick
BaD TacTics said:
My battery went tits up the other day so I had to purchase a new battery.....Ended up with HTC extended battery.(all verizon had in stock). When I put the battery in and powered on it just pops up with the HTC screen....couple secs go by the phone vibrates....HTC again......I can get the phone into bootloader.....but for the life of me can only get fastboot to work.....I have tried pushing cwm through that as well as the img above with no luck.....The Hboot only shows my device as android 1.0 and is unrecognized.I have reloaded drivers and everything I know how....Someone please help
Windows 7 64 bit ultimate
Rooted Thunderbolt running Thunderstick
Click to expand...
Click to collapse
Have you tried an ruu?
Sent from my ADR6400L using Tapatalk 2
Hello everyone. Im trying to install CS 3.0 on my phone and its stuck at the cyanogen mod boot screen. I have wipe, wipe and rewiped and still the same results. I was on ICS RUU and everything was ok. Any ideas of what i can try?
clmowers said:
Hello everyone. Im trying to install CS 3.0 on my phone and its stuck at the cyanogen mod boot screen. I have wipe, wipe and rewiped and still the same results. I was on ICS RUU and everything was ok. Any ideas of what i can try?
Click to expand...
Click to collapse
S-ON? S-OFF? If you're S-On make sure you're selecting the option in Aroma installer for S-On that will write PH98IMG to SD for installation.
clmowers said:
Hello everyone. Im trying to install CS 3.0 on my phone and its stuck at the cyanogen mod boot screen. I have wipe, wipe and rewiped and still the same results. I was on ICS RUU and everything was ok. Any ideas of what i can try?
Click to expand...
Click to collapse
Can you get a logcat of it?
For me, it kept saying that all the system services were dying.
Sent from my HTC Rezound using Tapatalk 2
@clmowers
Try a rom flash without gapps after data/system wipe. Won't need to reflash your boot.img.
fo0you said:
S-ON? S-OFF? If you're S-On make sure you're selecting the option in Aroma installer for S-On that will write PH98IMG to SD for installation.
Click to expand...
Click to collapse
What the OP is experiencing isn't a boot.img issue.
Snuzzo said:
@clmowers
Try a rom flash without gapps after data/system wipe. Won't need to reflash your boot.img.
What the OP is experiencing isn't a boot.img issue.
Click to expand...
Click to collapse
I was also having a similar issue.
Interestingly, it would only happen after I restored my apps in System Tuner (coming from cm10).
First all the system processes would force close, and after a reboot, a logcat said that all the processes were dying.
Sent from my HTC Rezound using Tapatalk 2
Yeah see, I don't ever restore system apps and never have a problem with any rom/kernel combination.
clmowers said:
Hello everyone. Im trying to install CS 3.0 on my phone and its stuck at the cyanogen mod boot screen. I have wipe, wipe and rewiped and still the same results. I was on ICS RUU and everything was ok. Any ideas of what i can try?
Click to expand...
Click to collapse
sounds like you are s=on and didnt pull the boot.img and flash with adb?
synisterwolf said:
sounds like you are s=on and didnt pull the boot.img and flash with adb?
Click to expand...
Click to collapse
Wouldn't get to the boot ani if the boot.img wasn't flashed.
He was probably having a similar issue as mine.
Sent from my HTC Rezound using Tapatalk 2
You know i was having the same problem with an earlier version of counter shrike but i was on GB Firmware. I installed it without the GB Patch accidentally and it worked fine! Dunno if this will help.
Hey all sorry for the delay in response. Never got the notification. What the problem was is I am s-on and I wasn't removing the boot.img from the ROM. Once I did that and flashed it. It booted
Sent from my Rezound using Tapatalk 2
I've had this 4-5 times now, with various ROMs, tried CM10.1, 10.2 most recently. Basically the phone randomly stops booting, I can get to the recovery fine, but booting to system gets stuck on the Galaxy S4 Logo screen. Tried dalvik / cache wipes, permission fix, nothing helps.
Firstly, unless I completely wipe data (full wipe including /data/media), I can't seem to be able to install a new ROM. If I dirty flash everything works fine, but if I do a factory reset, I will get stuck on the logo at boot. Then even after I have successfully installed a ROM, I will sometimes randomly get stuck on reboots, and nothing but another full wipe will fix this. Is this an issue with the TWRP recovery? or is my internal memory fudged and getting corrupt ?
edit: See my post here for details on what I've found so far, I may have fixed the problem but needs more testing http://forum.xda-developers.com/showthread.php?t=2397438&page=2
TWRP!!!!
SellswordShev said:
I've had this 4-5 times now, with various ROMs, tried CM10.1, 10.2 most recently. Basically the phone randomly stops booting, I can get to the recovery fine, but booting to system gets stuck on the Galaxy S4 Logo screen. Tried dalvik / cache wipes, permission fix, nothing helps.
Firstly, unless I completely wipe data (full wipe including /data/media), I can't seem to be able to install a new ROM. If I dirty flash everything works fine, but if I do a factory reset, I will get stuck on the logo at boot. Then even after I have successfully installed a ROM, I will sometimes randomly get stuck on reboots, and nothing but another full wipe will fix this. Is this an issue with the TWRP recovery? or is my internal memory fudged and getting corrupt ?
Click to expand...
Click to collapse
I'm having the same [email protected]#$%^& problem!!!! you're using TWRP aren't you?
i finished reading your post after I was done and saw that you ARE using TWRP...
thepianoman77 said:
I'm having the same [email protected]#$%^& problem!!!! you're using TWRP aren't you?
i finished reading your post after I was done and saw that you ARE using TWRP...
Click to expand...
Click to collapse
yep I was on TWRP 2.5.0.2, I just read that its got some stability problems with /data, just flashed v2.6 hopefully this fixes it
SellswordShev said:
yep I was on TWRP 2.5.0.2, I just read that its got some stability problems with /data, just flashed v2.6 hopefully this fixes it
Click to expand...
Click to collapse
oh dude.... I was on v2.6... I think we have an issue.
That is why I use cwm. Been using it for 3+ years on 4 different devices. Never have I had one problem with it.
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
That is why I use cwm. Been using it for 3+ years on 4 different devices. Never have I had one problem with it.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
i had a very bad experience with CWM... never using it again man.... no way.
thepianoman77 said:
i had a very bad experience with CWM... never using it again man.... no way.
Click to expand...
Click to collapse
Lol ok :thumbup:
Sent from my SCH-I545 using Tapatalk 2
I've been using TWRP too. I panicked last night when I couldn't boot at all. I couldn't even get to recovery. I then tried the no wipe odin without luck. I finally got the stock odin image to work but I've been having serious issues with booting on this phone since I got it this weekend and it could be TWRP I suppose. I was using it on my note 2 with no issues. Very strange. I'm back to stock and running fine now.
Sent from my SCH-I545 using xda premium
Still having odd issues with TWRP after updating to 2.6, getting stuck on boot as before, and sometimes flashing a ROM will just fail and the data partition becomes read only, and I can't push anything to it till I reformat /data.
Going to try CWM today, really hope this is just a recovery issue. Are there any tests to check the health of on board memory? I am really hoping I don't have bad hardware here.
Im having the same issue just made a thread fir it guess I will delete since I found this. Hope someone figures it out. What root/ recovery method did you all use. Was it the auto script?
Sent from my SCH-I545 using xda premium
ruffneckZeVo said:
Im having the same issue just made a thread fir it guess I will delete since I found this. Hope someone figures it out. What root/ recovery method did you all use. Was it the auto script?
Sent from my SCH-I545 using xda premium
Click to expand...
Click to collapse
Root / recovery methods will be the same for everyone, regardless of what guide / thread you followed, in the end you will have a loki-patched recovery and kernel, as thats the only way to run unsigned images on these phones. Whats relevant here is which recovery and kernel you are using, as these are the only 2 things that could effect errors in the boot logo state (aka freezes before the ROM boot animations kick in). Ive been looking through various ROM threads of people reporting this issue and its pretty widespread, and usually is linked to recoveries rather than ROMs. If you can post your recovery + ROM here that would be helpful. Here is what I've done so far:
I was initially on TWRP 2.5.0.2, which had possible bugs that could corrupt /data, leading to failed flashes, and being unable to read/write from /data entirely (including /sdcard). After switching to 2.6.0.0 I was still getting stuck on the boot animation. (All of this running the CM10.2 ROM with the stock kernel here http://forum.xda-developers.com/showthread.php?t=2384470). Note I did not do a full wipe after switching to 2.6.0.0, so that recovery MAY still be ok if someone wants to test it out.
I am now running CWM (official installed off ROM Manager). After flashing this I did a full re-format (/system, /data (including /data/media), etc.). And so far I haven't had any problems, going to do some more fiddling / flashing tonight to try and see if its really fixed, but I know for sure that atleast the reboot bug is gone.
So my advice is to flash the official CWM recovery, do a full re-format using that recovery, and then re-install your ROM.
I had that same /data issue with TWRP. It worked perfect for a few months and then suddenly it happened. I enjoyed TWRP for the 10 minute backups and restores, but i'd rather put up with CWM's 30 minute backup and restores if that will mean it wont happen again. Currently running PhilZ Touch Recovery and its been perfect so far!
Monkz said:
I had that same /data issue with TWRP. It worked perfect for a few months and then suddenly it happened. I enjoyed TWRP for the 10 minute backups and restores, but i'd rather put up with CWM's 30 minute backup and restores if that will mean it wont happen again. Currently running PhilZ Touch Recovery and its been perfect so far!
Click to expand...
Click to collapse
Have you tried any 4.3 ROMs with the PhilZ recovery? There seem to be some issues there. Still that recovery may be a good solution for those on 4.2 having this problem. I'm gonna try and loki patch the official CWM touch tonight if I don't run into this bug again, using the volume buttons is so bloody painful lol.
SellswordShev said:
Have you tried any 4.3 ROMs with the PhilZ recovery? There seem to be some issues there. Still that recovery may be a good solution for those on 4.2 having this problem. I'm gonna try and loki patch the official CWM touch tonight if I don't run into this bug again, using the volume buttons is so bloody painful lol.
Click to expand...
Click to collapse
None of my ROMs are 4.3, but i know the one i'm using is soon to be updated, so i will know if it works or not when it gets updated to 4.3. But no issues on 4.2.2 ROMS as of yet with PhilZ.
Monkz said:
None of my ROMs are 4.3, but i know the one i'm using is soon to be updated, so i will know if it works or not when it gets updated to 4.3. But no issues on 4.2.2 ROMS as of yet with PhilZ.
Click to expand...
Click to collapse
is PhilZ a recovery?
thepianoman77 said:
is PhilZ a recovery?
Click to expand...
Click to collapse
Yes its a custom build of CWM maintained by an xda dev here http://forum.xda-developers.com/showthread.php?t=2322675
Im still having the issue with philz. Everything was fine for the first 4-5 weeks. Now about every 3rd reboot or if battery dies I have to wipe data and nandroid. Im running stock with several tweaks. Going to try and odin restore to stock re root snd install cwm tonight and see if that helps will report back
Sent from my SCH-I545 using xda premium
Alright, I'm almost 99% sure this problem is gone after I switched to the official CWM. I've tried everything from restoring nandroids to flashing TWiz / AOSP 4.2 and 4.3 ROMs, everything boots and reboots and /data is no longer getting corrupt. I also loki patched the official CWM touch recovery (the one on their site is not patched), and flashed + used it successfully. Its pretty simple to do this, just follow the guide here: https://github.com/djrbliss/loki and use this recovery: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.3.2-jfltevzw.img
The only issue I've been having is that when I reboot to recovery, it sometimes gets stuck and I have to do a battery pull and go back into recovery.
Sent from my SCH-I545 using Tapatalk 4
I'm having the same issue on TWRP 2.6. Tried with multiple ROMs. Everytime I reboot I have to format /Data. So frustrating. I will try CWM now.