Database Develop

[Q][Still not Solved] Nexus one getting buggy with 7.1 mod

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!!

ICS(Leaks) and CWM

First off, let me make this clear very clear(prerequisite) I do not want to hear the word "safestrap", or any variation. I apologize for sounding arrogant , but I am not interesting in wasting my disk space(no offense against the quality work of Hashcode) or dual booting a ROM. I noticed some interesting issues with CWM recovery both the default that comes with Bionic Bootstrapper(4.x.x.x), and ROM Manager(5.x.x.x) in regards to any ICS leaks. So here is the situation, after installing the .232 leak using the "stock recovery option" it went smoothly without any issues, as well as rooting with motofail for ICS. The problems start when I first attempt to install any ROM(AOKP, CM, liquidsmooth etc etc) using 4.x.x.x CWM it appears to install correctly(even booting the ROM up and everything) but when I reboot the phone will continue to boot directly into CWM, and using the reboot option only to boot loop.(I have done the standard Wipe System/Factory reset, Wipe Cache, Wipe Dalvik Cache prior to installing any ROM). Finally, when I attempt to install an updated CWM 5.x.x.x via ROM Manager, it appears to install, but forcing the device to reboot in to recovery does not work, even the two button solute(PWR+VOL UP) as used in the second stage to force CWM to boot into the menu(worked in 4.x.x.x) it is as if it is not corretly installed.. Both CWM installs are clean, and no previous 1st/2nd stage boot loaders are installed, I would like to rule out me being a dumbf*** and it being a case of error on my part. Like I said before please do not mention "SAFESTRAP" as an option, unless it can flash over current baseline install's, having the safe option(noob proof) is not an option. If anyone can assist me with the installation or even a solution to getting CWM recovery to work after installing the ICS leaks it would be greatly appreciated. Thanks again!!! Also I have tested CWM 5.x.x.x install from .905 based roms and it works flawlessly.

CWM Recovery Boot Loop. Help!

Hi Everyone,
I have a GT-N7000 - it's been working great since I bought it 9 months ago. I was running RocketRom on it for months. I've been using RR 11 (I didn't like 12) and haven't had a problem with it. The CWM that comes with it appears to be 6.0.1.2 and I kept the stock kernel (OneNote??). Lately, my sms messages were being sent sporadically and I kept getting this same SMS pop-up over and over (every time I sent an SMS). I know it's probably a carrier issue but I thought I would boot into recovery and wipe the cache and Dalvik. I've done this several times in the past without problems.
I first wiped the cache, then I did Dalvik. For Dalvik, I got the error E:\ unavailable (I recall seeing this in the past). I select "Reboot" and the phone booted back into CWM. I've tried removing the battery and same thing.
I ended up trying to flash back to the pre-rooted GB using Odin. The flash completes and the phone reboots but, yep you guess it, CWM comes up. It's the same version. So apparently this is not being updated by Odin??? I read somewhere that this is a CW bug that does not clear a flag to boot back into Android but the fix seems overly complex and worries me (I'm not afraid of doing it if it will fix it).
I'm entertaining the idea of using Kies to do a "Firmware Upgrade" which looks like it will install the latest ICS. It successfully downloads the new firmware then asks me to connect the phone. Before I do this, I wanted to check here to see if this is my only (best) option. Or if I should try something else? Also, Kies says system and data will be initialized so will my sms logs, photos, etc be deleted as well? Not a huge issue since I save the photos to the external sd. I just want to know if the USB storage will be wiped too.
[EDIT] I wanted to add that I TRIED to install Abyss from CWM and it hangs. Same ting with installing RR again. It appears that the file system is locked or something. Pretty much nothing works in CWM. I even tried mounting the various partitions then installing Abyss. It just hangs on "installing." I suspect the problem occured when I wiped the cache or Dalvik. I just don't know what
I appreciate any input.
Thanks!

dont use abyss... try other like hydracore or speedmod 3-15

Im a noob and im afraid i may have this also..

Try to download Philz kernel for your built number, and flash the philz zip file from recovery.
or if can't flash from recovery, try to download the ODIN file for philz kernel (TAR file).
It should re-injected the CWM.
Sent from the corner of this rounded earth.

[Q] Help Needed With Restore

I hope someone can help me.
I just got my GT-N7000 back from Samsung after a repair to the audio socket. The phone was rooted but Samsung returned the phone to the stock JB 4.1.2 ROM. All was working as it should when I got it back.
Now, I wish to re-root the phone and restore my choice of custom ROM - Ultimate _N7000_XXLT4_JB_4.1.2. v6.0 with all my apps and data. This is the ROM I've been using ever since it was published without issue.
I have managed to re-root the phone with the PhilZ Touch 5 recovery + safe kernel and CWM Base Version v6.0.3.7 which I think is the version I was using before. This part of the procedure appears to have worked correctly and I can now boot into the PhilZ Touch 5 recovery without any issue.
However, after restoring the backup I made prior to the audio jack problem and rebooting, he phone hangs after a few initial swipes through the screens ie I can no longer swipe screens or start apps and the phone is non-responsive. All I can do then is remove the battery. No errors are being reported during the Restore and I've taken care to Wipe data/Factory reset, Wipe Cache Partition and then Advanced >Wipe Dalvik Partion.
I tried the Restore several times but the result is the same. One thing that may be related is that my lockscreen image is not the one I was using when I did the backup. Nor is it the stock image of the book and quill pen that the stock ROM uses (it's a picture of a kid leaping into the air with a big bunch of balloons which I've never seen before). This could mean that something isn't being wiped properly.
Any advice from the experts would be most welcome as I'm out of my depth.
Trevor

Did you check in Philz recovery if the restore of Preload partition is enabled..?

nokiamodeln91 said:
Did you check in Philz recovery if the restore of Preload partition is enabled..?
Click to expand...
Click to collapse
Thanks for the reply. No, I didn't know to check that but will do so in future. I have never encountered that setting before. Is it usually enabled by default?
I think the trouble was that at least one of my backup files was corrupt. I tried an earlier one and this one seemed to have fewer problems so concluded that this was the source of trouble.
In the end, I downloaded a fresh copy of the Ultimate ROM I was using which got the phone fully working again and then let Google download all my apps automatically. So I'm out of trouble now.
Thanks again.
Trevor

Custom roms and stuck on splash/boot animation (SOLVED)

Hello!, my device is GT-i9305 and i seem to have a problem of some sort. (I have had three devices before this and installed lots of custom roms, but never have i encountered something like this)
Whenever i try to install a custom rom (omnirom/pacrom/cyanegenmod) i get stuck in the splash/boot screen animation, but when i flash back to stock rom (4.4.4) using odin it loads up and everything works like its supposed to.
I have tried using TWRP and CWM-recovery. (With CWM i can get omnirom to boot, but i wont be able to dial or use mobile-data etc. (Seems like my efs files or something are missing) and i also get some error message about androidcore or somethinglikethat.
Most common fixes for this in the forums are to wipe dalvic and cache after installing. Which i have done + some other odd "fixes" i found.
I am really baffled. Whats wrong?

Did you flash TWRP 2.8.7.0? That recovery is buggy and does not work. You have to stay on 2.8.5.0 for the moment. There are people already trying to fix the faulty recovery. CWM won't get any updates anymore. It does still work but you might come across some ROMs which won't work with CWM.
To start all over again with no issues: flash 4.4.4 Stock, install TWRP 2.8.5.0 and you're good to go

Thankyouthankyouthankyou
That totaly fixed it! Thank you sooooo much, no more sleepless nights because of this.