So I think I may have messed up my firmware. I odin'd it with a shady tar and ever since then my recovery randomly reboots when I choose zips to install. My Bluetooth isn't working, it won't even enable. I flashed the stock tar from sammobile and then rooted that,now im running cm10.1. Bluetooth is the only thing that hasn't worked yet but has anyone else had this issue?
Bluetooth issues is a known bug with 4.2 and 4.1 based roms.
Yeah but those are issues with the sound and how lo the volume is. i fixed the bluetooth issue by going into recovery and wiping cache/dalvik and re-installing 10.1 then fixing permissions which i figured it might but i added that info just in case. I re-installed my recovery from goomanager app and im still having issues with it which i hope isn't contributed to firmware.
rangercaptain said:
Bluetooth issues is a known bug with 4.2 and 4.1 based roms.
Click to expand...
Click to collapse
Issues can mean 100's of things.
Be specific.
you are seeing random reboots in the firmware ? Or when you access Recovery ?
RR's in the 4.2 firmware are expected, as we use an uber-modified ICS kernel to run JB.
If recovery is causing a reboot condition, you have a dirty recovery partition, or the recovery image itself is damaged. Either way, a new recovery file should be flashed to test. And I suggest TWRP, directly from the TWRP site. Note: Version 2.4.2.0 caused a recovery reboot condition for me. I reverted to 2.4.1.0 and the condition went away.
Good luck Sir.....g
Yeah I tried the flashing of a new recovery from twerp site and that's when the issue started. Also, if you read the list and comments you would have seen the exact Bluetooth issue and the issue I thought may be my firmware. If you had the same issue with tarp 2.4.2 than it must be that and not the firmware because I wiped all possible partitions and reinstalled everything from scratch the other day.
gregsarg said:
Issues can mean 100's of things.
Be specific.
you are seeing random reboots in the firmware ? Or when you access Recovery ?
RR's in the 4.2 firmware are expected, as we use an uber-modified ICS kernel to run JB.
If recovery is causing a reboot condition, you have a dirty recovery partition, or the recovery image itself is damaged. Either way, a new recovery file should be flashed to test. And I suggest TWRP, directly from the TWRP site. Note: Version 2.4.2.0 caused a recovery reboot condition for me. I reverted to 2.4.1.0 and the condition went away.
Good luck Sir.....g
Click to expand...
Click to collapse
Update
I went to twrp site today and downloaded and installed twrp 2.4.3 and it fixed the random recovery reboots but when the screen shuts off i cant bring it back up, it just stays black. Im not sure if its still installing the ROM or what but i just hold down the button and reboot into recovery again. I have to constantly move my finger around the screen to keep it awake.
Atrix2destroyer said:
Yeah I tried the flashing of a new recovery from twerp site and that's when the issue started. Also, if you read the list and comments you would have seen the exact Bluetooth issue and the issue I thought may be my firmware. If you had the same issue with tarp 2.4.2 than it must be that and not the firmware because I wiped all possible partitions and reinstalled everything from scratch the other day.
Click to expand...
Click to collapse
Yes, I saw your issues....as you stated a bluetooth error....(ROM related, not recovery).
I also saw your recovery issue, and said to flash TWRP 2.4.1.0...
Then you flashed 2.4.3.0 and are still having issues. Did you flash 2.4.1.0 ?? because if you did, your recovery issues would be gone.
And if you flash a ROM with known bluetooth issues like CM 10.1, then you will have bluetooth issues.....g
Related
Ohai!
I have a Galaxy Player 5.0 USA (YP-G70), and a few days ago I installed Entropy512's kernel via the `dd` method. Everything worked nicely, until I decided to boot into ClockworkMod Recovery by holding the volume up key while booting. It booted into the recovery menu, and everything worked nice, but when I hit 'reboot' or 'shutdown', it booted right back into recovery (after seeing the SAMSUNG screen for about 5 seconds).
I've done pretty much everything I can think of. I've reflashed the kernel, flashed CM7 and CM9, and I tried flashing a stock ROM that I found. Flashing the kernel from the stock ROM causes my device to instead go into "Android System Recovery" rather than ClockworkMod Recovery, but I'm able to get back into CWM by flashing Entropy's kernel with heimdall.
I'm capable of getting root access with `adb shell`. I've wiped almost everything on the device (used the 'wipe data/factory reset' option and 'wipe cache partition' option) but still continues to boot into CWM recovery.
I'm not too interested in simply fixing the device so it's back to stock, as I *really* want CM9. I have a Droid X to keep me busy for now, so I found that my Galaxy Player has been just sitting there, collecting dust. If I can get it to run CM9, I'd have more use for it.
I apologize if I left out some important information. Any help would be appreciated!
Thanks in advance,
- Ben
Just an update, I tried an exitrecovery.zip, which did not help. I also extracted the exitrecovery.sh from the zip and executed the one command it had inside it manually in a root shell. Still stuck. Is my device bricked in some form? I'm pretty sure there is some bootflag that tells it to boot into recovery, even if everything is fine.
I would suggest to go ahead and flash CM9, because your problem may be caused by formatting/corrupting /system (the kernel has nothing to load, so it drops you into recovery).
Once you flash cm9, however, do not flash Entropy's kernel again.
Sent from my YP-G70
East gsstert
Mevordel said:
I would suggest to go ahead and flash CM9, because your problem may be caused by formatting/corrupting /system (the kernel has nothing to load, so it drops you into recovery).
Once you flash cm9, however, do not flash Entropy's kernel again.
Sent from my YP-G70
Click to expand...
Click to collapse
Thanks for the reply. I actually ended up trying so, and CM7 as well, to no avail. I also tried flashing stock, as I said in the post (I think, maybe I forgot to mention it) and it failed. (I used heimdall to flash stock)
I ended up giving up and replacing the device since it was under warranty, but I regret doing such as I *really* wanted to know why this happened in the first place. I'm anxious to get CM9 on it. Should I just put the device into download mode and use heimdall to flash CM9?
No. The safest way (and easiest, IMO) I think is to root it while on stock, install Entropy's kernel (extract the zip and dd it), and use CWM to wipe your device and install CM9, plus back up stock if you want to.
Sent from my 5.0 US with ICS
Mevordel said:
No. The safest way (and easiest, IMO) I think is to root it while on stock, install Entropy's kernel (extract the zip and dd it), and use CWM to wipe your device and install CM9, plus back up stock if you want to.
Sent from my 5.0 US with ICS
Click to expand...
Click to collapse
Apologies for the late reply.
That is what I did last time. I actually got stuck in CWM before even trying to flash CM9 or anything. I just booted into recovery, and then instantly clicked on 'reboot'.
Hmmm... that's really interesting. Although I still have no idea why it would have this problem (I've never had it on Entropy's kernel - which version are you using?), I think I know what the problem is. When you tell android to "reboot recovery", it puts a file in the boot partition that the kernel sees after the reboot and tells it to enter recovery mode. Logically, that file gets deleted so the system boots normally next time. It seems that in your case that failed to happen. But I still am wondering why...
Sent from my 5.0 US with ICS
Mevordel said:
Hmmm... that's really interesting. Although I still have no idea why it would have this problem (I've never had it on Entropy's kernel - which version are you using?), I think I know what the problem is. When you tell android to "reboot recovery", it puts a file in the boot partition that the kernel sees after the reboot and tells it to enter recovery mode. Logically, that file gets deleted so the system boots normally next time. It seems that in your case that failed to happen. But I still am wondering why...
Sent from my 5.0 US with ICS
Click to expand...
Click to collapse
Yeah, seems to be probably what happened. I actually ended up trying again on the new Galaxy Player, and things went swimmingly. I am now happily running CM9 on this device. However, I am scared to even think about booting into recovery again. (I only went into recovery to flash the kernel, and wipe the data partition)
I've read a couple other posts were people have had a similar problem... So I'm just starting this thread for FYI..
When I downloaded and flashed the latest TWRP2 my phone would no longer boot or enter recovery... The phone would simply bootloop. I was lucky enough that I could get the phone into download mode and I was able to ODIN a previous version of TWRP...specifically 2.4.4.0 and then the phone booted again and recovery worked. I've also seen issues with TWRP 2.4.3.0 and some ROM installs which go to black screen during install....forced to hold power to reboot phone and then rom boots...
So if you get the bootloop after installing the latest TWRP, simply use ODIN 3.7 and grab a tar file of either CWM or older TWRP and install to fix.
Cheers
had the same issue.
Well, I'm not seeing a recovery.log so they can have actual information on what's wrong. I'll be doing that today at work.
I cant get anything above 2.4.1.0 to work for me....g
bhaskell said:
I've read a couple other posts were people have had a similar problem... So I'm just starting this thread for FYI..
When I downloaded and flashed the latest TWRP2 my phone would no longer boot or enter recovery... The phone would simply bootloop. I was lucky enough that I could get the phone into download mode and I was able to ODIN a previous version of TWRP...specifically 2.4.4.0 and then the phone booted again and recovery worked. I've also seen issues with TWRP 2.4.3.0 and some ROM installs which go to black screen during install....forced to hold power to reboot phone and then rom boots...
So if you get the bootloop after installing the latest TWRP, simply use ODIN 3.7 and grab a tar file of either CWM or older TWRP and install to fix.
Cheers
Click to expand...
Click to collapse
Same issue here. had to revert to 2.4.4.0
I have been running the same build of CM11 since February with few issues. However for the past couple of weeks my phone has been randomly freezing but no harm was done as a battery pull / reboot would simply fix the issue until the next occurrence.
This morning a freeze occurred during normal use of my phone but after rebooting it would always hang on the CM loading screen. I booted into recovery and flashed an old version of CM10 successfully and everything seemed to be working.
This evening I attempted to flash a new build of CM11 however something went wrong during the data wipe I performed before installation of the new ROM. Since that point I cannot flash any ROM because my phone will always freeze after about 30 seconds of being booted inside recovery mode.
Download mode seems to work perfectly and I have successfully flashed CWM 6.0.3.2 and CWM 6.0.4.7 but both still freeze after about 30 seconds of being booted into them.
Has anyone had this issue or can offer help?
Sounds like nand memory has bad blocks. Try flashing a full stock rom with Odin.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Sounds like nand memory has bad blocks. Try flashing a full stock rom with Odin.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
You could well be right about it being a NAND issue, I guess time will tell if I continue getting random freezes.
I flashed a full stock ROM according to your suggestion and ended up with a non-functioning ROM but a functional stock recovery. I then did a factory reset from within the stock recovery which seemed to work. I also formatted my external SD card just in case. I then flashed a custom recovery via Odin and it was fully functional.
Now happily running CM11 again!
I had little issue moving up to 4.0.4 so I don't have to worry about the EMMC erase bug, but I'm realizing I have no way to get up further.
Everything seems to require CWM or a version of TWRP that has no compatible kernels with 4.0.4 best I can do is Siydah and like 6.0.1.2 and looks like CWM but its rather sparse on the details.
Final edit, I found a much better solution.
It does not seem as though you can flash a upgraded kernel from the CWM interface itself and reboot reliably failed on multiple kernels.
Solution
Download mobile Odin
Download the 4.4 ROM of your choice (compatable)
Gapps too stick them all somewhere you can find them (i just leave em in downloads)
Download and flash CWM 6.0.4.4 for Kitkat i777.. no clue where I found it wasn't on XDA though.
Turn the phone off (if you reboot and don't reboot too recovery you get a loop)
Boot to recovery (if you get in a loop here pull the battery THEN boot to recovery)
Now you'll notice your not on your old version of CWM anymore.
Install your ROM and Gapps.
Boot to rom
Boot back to recovery Now your once again on a different version of CWM.
I strongly advise cleaning everything up and installing it again I had some issue until I did.
GL to anyone who finds this thread. If there seems to be a need I could rewrite it with a better title.
TheEgonSpengler said:
I had little issue moving up to 4.0.4 so I don't have to worry about the EMMC erase bug, but I'm realizing I have no way to get up further.
Everything seems to require CWM or a version of TWRP that has no compatible kernels with 4.0.4 best I can do is Siydah and like 6.0.1.2 and looks like CWM but its rather sparse on the details.
Final edit, I found a much better solution.
It does not seem as though you can flash a upgraded kernel from the CWM interface itself and reboot reliably failed on multiple kernels.
Solution
Download mobile Odin
Download the 4.4 ROM of your choice (compatable)
Gapps too stick them all somewhere you can find them (i just leave em in downloads)
Download and flash CWM 6.0.4.4 for Kitkat i777.. no clue where I found it wasn't on XDA though.
Turn the phone off (if you reboot and don't reboot too recovery you get a loop)
Boot to recovery (if you get in a loop here pull the battery THEN boot to recovery)
Now you'll notice your not on your old version of CWM anymore.
Install your ROM and Gapps.
Boot to rom
Boot back to recovery Now your once again on a different version of CWM.
I strongly advise cleaning everything up and installing it again I had some issue until I did.
GL to anyone who finds this thread. If there seems to be a need I could rewrite it with a better title.
Click to expand...
Click to collapse
Always remember that when you flash a ROM, that you typically get the Recovery that is tied to the Kernel contained in that ROM. So, you flashed the Kernel, got Recovery A, then you flashed the ROM and got Recovery B. A KK Kernel can be flashed independent of a KK ROM, and will add different/additional/improved functionality, depending on the dev, but it also contains it's own Recovery in most cases.
desteele said:
Always remember that when you flash a ROM, that you typically get the Recovery that is tied to the Kernel contained in that ROM. So, you flashed the Kernel, got Recovery A, then you flashed the ROM and got Recovery B. A KK Kernel can be flashed independent of a KK ROM, and will add different/additional/improved functionality, depending on the dev, but it also contains it's own Recovery in most cases.
Click to expand...
Click to collapse
"Everything seems to require CWM or a version of TWRP that has no compatible kernels with 4.0.4 best I can do is Siydah and like 6.0.1.2 and looks like CWM but its rather sparse on the details. "
Yes I know, thanks for the advice.
TheEgonSpengler said:
"Everything seems to require CWM or a version of TWRP that has no compatible kernels with 4.0.4 best I can do is Siydah and like 6.0.1.2 and looks like CWM but its rather sparse on the details. "
Yes I know, thanks for the advice.
Click to expand...
Click to collapse
Oh, sorry...sounded like you expected to find the latest recoveries on JB kernels. My bad.
desteele said:
Oh, sorry...sounded like you expected to find the latest recoveries on JB kernels. My bad.
Click to expand...
Click to collapse
Nah, you just can't install the latest ROM with an older recovery.
So if you want to go up you have to do the little dance I described above. (Yes I know certain walkthroughs indicate you can do the first step in recovery, I simply found that to not be true and gained me only bootloops and the joys of reflashing stock then reinstalling a updated-er version so I could try again.)
wil this work in my situation
Quick question.. am on:
android 4.1.2
Shostock v 3.0.2
my cwm v6.0.2.7.
I want to move for a slimmer kitkat rom..
Hello I was having problems in backing up data in nandroid using cwm recovery. Some nice guy suggested me to change my recovery so I did.
Now i have messed up real bad, i flashed a philz recovery which I had used in a stock based rom and the backup was successful but then the phone couldn't boot up. So i restored the boot patrition from a previously made backup. This way i successfully booted up my phone and got previous recovery. So far so good. Now i knew that the problem is in recovery. I also had a raw kernel file which I had used to flash the cm11 rom so i flashed that kernel. But then i restated device to find out that i have now lost root access. I tried flashing super su via raw kernels twrp recovery but I saw no effect despite it being flashed. I cannot flash the recovery because the curreny twrp recovery crashes when i try to flash that.
Current situation is that I am getting constant unlimited, system process is crashed, errors and I can see no signal from mobile operator. Wifi is working fine.
Please help me, my phone is almost unusable with this error but I have access to all the apps, functions etc. in case you can suggest me to use it.
UPDATE:
Tried to flash a latest version of cm11 and now booted up correctly. root checker says I am rooted.
got latest cwm as well
Now I need to take backup to see if the initial problem is there or not.
As the issue highlighted in this thread is solved, I will mark this as solved and will reply to future problems (related to not being able to backup /data) in the following thread:
http://forum.xda-developers.com/android/help/cwms-nandroid-backup-fails-to-backup-t2899038