Hi
I have a problem with my battery. Maybe it's raddled but there's something what's wondered me. In battery stats, I have "System Android" 2 times. I just reflash CM but it didn't change anything. I don't know why.
I can't flash the last build of CM11 (janice) from temporary CWM and TWRP (from CoCoRe kernel). So I flashed the last build from reovery (CWM) from April 2015 build. It may be the reason? I wiped all before and after every flash.
Related
Greetings fellowmen!!
Recently i thought of rooting my nexus 1. So i did some research and found out that the easiest way to do it was by unlocking the bootloader installing a custom recovery (I did Amon Ra) and then wiping the data\factory settings and flashing the cm 7.1 zip. So i did all the above and there you go....I had an n1 running cm 7.1 smoothly but then after a few hours it starts to piss me of. The problem is that whenever i lock the homescreen with the power button and wake it up again it just displays the main homescreen and does nothing i cannot navigate to the left or right homescreen cannot open app drawer in short it just hung up there doing nothing. I had to take out the battery atleast 15 times. I rebooted my device and it kept on giving me the same problem.
So then i reflashed cm 7.1 by wiping the data and factory settings and installing it again. But still it gave me the same problem. So then i thought of flashing 7.0.3 version instead and surprisingly that works like a charm. So is it the mod thats buggy or is it my phone.
One more question. I have the stock 2.3.4 gingerbread rom which i got from here!!
Code:
http://forum.xda-developers.com/showthread.php?t=1061648
This one in particular-
GRK39F OTA (stock vanilla - odexed, unrooted):
MD5: 35C8B4B9FD22DD4CA19C5D026E74411D
So to install this rom do i have to install it the same way i did cm by wiping data/factory settings and then installing flash from zip or is there any other way to do it ?
Thanks in advance for taking out valuable time and reading my long problem!!
I am running the latest version of CM 7.1 that was released within the last week or so without any issues. Got it from here. http://download.cyanogenmod.com/?type=stable&device=passion
Before that I was running the RC for 7.1. One thing to try it wiping multiple times before flashing. I assume you are running Amon RA 2.2.1, which is the latest. I have never had a problem with that recovery, however I flashed my ROM with this recovery. So far I think I like it better than Clockwork and Amon.
http://forum.xda-developers.com/showthread.php?t=1291970
As for installing other ROMs yes you do flash them the same way you flashed CM.
So are you saying that it was the recovery that was causing the problem?
Yes I am using the latest Amon Ra 2.2.1 version.
I also got the rom from that link.
And can you explain whats the difference between all these recoveries?
Thanks for replying!
I am not saying it is the recovery, I highly doubt that is the problem. I was just comparing differences. There does not seem to be much difference in the recoveries for what you are trying to do. The recovery I am running is a fairly new one that I just wanted to test out. I do think I like it better than the others.
First thing I would do is wipe 3, 4 or 5 times before flashing. I have had rare occasions where a single wipe would not do it for me. Also have you verified the Checksum of the CM download? Does recovery say it installed successfully? I have also had error installing a ROM in recovery but then had the phone still load the ROM.
Yes i did check the md5 checksums and they match perfectly. Though i did wipe it out only one time so maybe that could be the problem. I think i should get clockworkmod and wipe it through that and then flash cm 7.1. Amon RA doesnt really give us the option of wiping the system partition. right?
Correct Amon Ra does not have an option to format system partition. It's recommend you also wipe system when coming from a different ROM.
Try this file by temasek's, format-signed.zip
http://www.mediafire.com/?8vbd13b440coxx6
just flash it in recovery and it will clean everything, now you can flash CM7.1 again
Are you sure you can't wipe the system with Amon? I remember having that option, but it's been several months since I have used that recovery. Kind of makes me want to flash it to find out.
Before flashing a different ROM I always wipe system, cache and dalvik cache. It is definitely important to wipe the system before flashing a new ROM. I'm sure that is where your problem lies.
No, ClockworkMod has it, but Amon_RA doesn't. Supposedly it is in the works for the next version, but that was a long time ago when I heard that (probably back when v3 for clockworkmod came out).
I did a nandroid backup and flashed the format zip file and then flashed cm 7.1 and its giving me the same problem!!
I had to restore and go back to 7.0.3
Why is this happening
Edit: I also wiped the dalvik cache and factory reset it also but still it just freezes!!
Any advise?
Have you tried downloading the file again maybe form another location I doubt this is the problem but sometimes it's something you don't expect.
You could try from here http://wiki.cyanogenmod.com/index.php?title=Latest_Version
But how does it matter I checked the md5 checksum and it matches!!
Why not stay on CM7.0.3 theres not much difference between the 2
if you dont want to i suggest to try to flash Clockwork recovery and do a full wipe then reflash CM7.1
But still I want to see how 7.1 is!
The main point here is to upgrade and not taking the alternative of staying at the older version!
Please guys any help would be appreciated!!
Doesn't CM7 need clockworkmod 3.x?? Try to flash CWM3.x over Amon if you can get your hands on the flashable zip or if you can get into a working rom, use romManager to switch from amon.
thealphamale05 said:
Doesn't CM7 need clockworkmod 3.x?? Try to flash CWM3.x over Amon if you can get your hands on the flashable zip or if you can get into a working rom, use romManager to switch from amon.
Click to expand...
Click to collapse
Make no different if you use amon Ra or CWM. I would definitely stay away from cwm 3.x or higher if you're using sd-ext
Looks like Ill have to stay with 7.0.3 there doesnt seem to be a solution!!
Hi,
Today i have rooted my LG (V20N), and installed CyanogenMod (7).
But after some time, aprox. 1 hour, it reboots automatically in recovery mode (CWM).
Any suggestions?
Thanks.
I'm noticed that on #68 (or #69...) build, but on #70 and latest this was not observed. Maybe, it's broken ROM file or unsuccessfully flashed? Try to do full wipe with /system and flash other build. Because of this I remove touch recovery)))
90amper said:
I'm noticed that on #68 (or #69...) build, but on #70 and latest this was not observed. Maybe, it's broken ROM file or unsuccessfully flashed? Try to do full wipe with /system and flash other build. Because of this I remove touch recovery)))
Click to expand...
Click to collapse
I followed this tutorial http://forum.xda-developers.com/showthread.php?t=1487105, to root and install CM7. It was all fine, but yet has lag and restart automatically in recovery. I will t try another rom then.
Thanks
Hello world,
i need help.
i got the P7310 16 GB. my Tab is a US-refurbished unit sold in the UK.
I tried to upgrade from my stock 4.0.4. (got it via KIES for 2 months now) to CM10 (latest build, here in this forum). installed the latest cwm 5.5.0.4, I did the root, installed superuser, got the root permission. restarted. wiped cache, did the factory/data reset. installed CM10 build in cwm, than the googleapps for 4.1.2. RESTART: after the GalaxyTab 8.9 writing disappeared my screen stays black. for more than 20 minutes.
the last day i tried almost everything. wiped dalvik cache, diffrent procedures. tried different kernels (with a1 kernel 1.7.2 i got the bootscreen of CM10, but it was frozen. and i was not able to reproduce it). i also tried AOSP ROM, but it showed the same issues.
BUT: a stock based ROM from this forum based on ICS worked flawlessly
maybe it got something like a bootloader lock? well, now i got the stock 4.0.4. again (took the UK Version for P7310) and used a PIT file to repartion the whole tab and get a 100% clean installation, with root & a1 1.7.2 Kernel & cwm 5.5.0.4
What should I try next?
TroubleCame said:
Hello world,
i need help.
i got the P7310 16 GB. my Tab is a US-refurbished unit sold in the UK.
I tried to upgrade from my stock 4.0.4. (got it via KIES for 2 months now) to CM10 (latest build, here in this forum). installed the latest cwm 5.5.0.4, I did the root, installed superuser, got the root permission. restarted. wiped cache, did the factory/data reset. installed CM10 build in cwm, than the googleapps for 4.1.2. RESTART: after the GalaxyTab 8.9 writing disappeared my screen stays black. for more than 20 minutes.
the last day i tried almost everything. wiped dalvik cache, diffrent procedures. tried different kernels (with a1 kernel 1.7.2 i got the bootscreen of CM10, but it was frozen. and i was not able to reproduce it). i also tried AOSP ROM, but it showed the same issues.
BUT: a stock based ROM from this forum based on ICS worked flawlessly
maybe it got something like a bootloader lock? well, now i got the stock 4.0.4. again (took the UK Version for P7310) and used a PIT file to repartion the whole tab and get a 100% clean installation, with root & a1 1.7.2 Kernel & cwm 5.5.0.4
What should I try next?
Click to expand...
Click to collapse
Try it to install with cwm 6.0.0.8
http://www.mediafire.com/?b2pbv065k51zqy6
Install this recovery in the cwm 5.5.0.4 and after that go to advanced---> reboot recovery and install the rom with the new cwm 6.0.0.8
I had installed LiquidSmooth ROM on my Samsung Galaxy Note GTN7000 a while ago. I run Philz Touch recovery version 6.0.0.1 .
When I tried flashing CM11 , I got an error something like set_metadata_recursive .. .
I googled it up, and found that I need to update my recovery. SO, i downloaded the latest version of CWM from their website and tried flashing it through the recovery. And it is resulting in a sudden shut down and then in a bootloop when switching on .
What wrong am I doing? How can I rectify this?
Flash Raw Kernek r5:
http://forum.xda-developers.com/showthread.php?t=2397000
On our device the recovery is incorporated into the kernel, never flash a recovery or kernel that isn't meant for our device.
Once you have flashed that, reboot to recovery and perform a full wipe. Then proceed with the installation of CM.
Hopefully someone can help me with this issue.
I have a problem whereby my phone will go into a bootloop every time I reboot the phone. The only solution I have found so far is to boot back into recovery and wipe cache/dalvik cache however this is fairly time consuming as I have over 205 apps for which the cache needs to be built every time.
I had thought that the problem was to do with the latest update to Amplify and I was able to reboot successfully after downgrading but the problem has since surfaced so I am back to square one.
I am currently on SkyDragon v4 (Lollipop Rom) with latest Elemental kernel and also latest TWRP recovery. Is there anyway I can access a boot log and see what issue might be causing this bootloop (I feel it may be an app).
burgess_boy said:
Hopefully someone can help me with this issue.
I have a problem whereby my phone will go into a bootloop every time I reboot the phone. The only solution I have found so far is to boot back into recovery and wipe cache/dalvik cache however this is fairly time consuming as I have over 205 apps for which the cache needs to be built every time.
I had thought that the problem was to do with the latest update to Amplify and I was able to reboot successfully after downgrading but the problem has since surfaced so I am back to square one.
I am currently on SkyDragon v4 (Lollipop Rom) with latest Elemental kernel and also latest TWRP recovery. Is there anyway I can access a boot log and see what issue might be causing this bootloop (I feel it may be an app).
Click to expand...
Click to collapse
whats your firmware version?
alray said:
whats your firmware version?
Click to expand...
Click to collapse
Have just updated to the latest firmware, was reluctant to do so as didn't think that would be the issue. After updating I still have the same issue.
I have found the culprit though, it would appear that a module in my xposed library is to blame as I have just disabled xposed on boot and it booted straight to the home screen.