Database Develop

[Q] No more CyanogenMod 7

Hi everyone I really hope someone of you can help me with this issue
This is my coinfiguration
Nexus One, with the latest radio & HBoot installed, ClockWork recovey 3.0.0.5 and original SD as memory card (4GB)
After wiping everything from recovery and formatting the Mcard with 128MBswap & 512MBExt I am no longer able to install any CyanogenMod 7 release either nightly or stable. I did try to clear storage from bootloader and replacing the RA 2.2.1 without success. At the moment the only rom I can install is the MIUI and the stock one GRI40, all Cyanogen got stuck after the boot. Is any other way to do a kind of hard reset at the phone?
Many thanks in advance
EDIT: apologize I did post into a wrong area, MOD please move to the correct place
Thanks

Are you flashing a compatible gapps?
Also, try using a different recovery...

as i posted i did try both recovery (ra 2.2.1 & clockwork). i haven't flashed any google apps as I did flash the rom only

The Nexus One doesn't need a swap partition, try re-partitioning your card without that.
Try to download this: http://www.mediafire.com/?bxfijcp6f6bf1me
Then flash it from Amon-RA. It'll format your system partition too.

mindfrost82 thanks for the link but it seems not working, do you have another one available?
Many thanks

mindfrost82 said:
The Nexus One doesn't need a swap partition, try re-partitioning your card without that.
Try to download this: http://www.mediafire.com/?bxfijcp6f6bf1me
Then flash it from Amon-RA. It'll format your system partition too.
Click to expand...
Click to collapse
I can't tell you how many users PMed me after using that format utility to find out that when they try to flash a new ROM, they only can boot to recovery, no matter what they do. A nandroid backup with a system image or going thru a restore process involving fast boot img restores is the only fix. Just reporting what I have seen myself using that utility.

guys thanks for your effort but I gave up. I still don't understand why my N1 won't launch Cyanogen7, but for sure there is something wrong on my telephone. After installing without issue the Kang-o-rama 1.2 b3 I notice that after launching the market the main page is blank stating that there is no application available...O_O

Try this:
Install the recovery following what is said here in "Second Method (manual method)"
http://wiki.cyanogenmod.com/index.p...pdate_Guide#Second_Method_.28manual_method.29
BUT use this recovery http://mirrorbrain.cyanogenmod.com/cm/recoveries/recovery-clockwork-2.5.1.4-passion.img instead of the 3.0.0.5.
After that, flash this file
http://www.mediafire.com/?bxfijcp6f6bf1me
(it deeply wipes everything away, thank temasek for this stuff)
Then flash CM7 release and Gapps following what is said here
http://forum.cyanogenmod.com/topic/20115-cyanogenmod-7-for-nexus-one-v700-10-april-2011/
I hope this helps

I'll give a try, thanks for the tips

[Q] Able to restore to stock, but...

My boot went corrupt with CM 7.0.2. I was able to restore to stock with no problem, but everytime I attempt to install CM 7 (stable or nightly), I get a black screen except for a little white/light blue line in the upper right corner.
I use the 3.0.0.5 Recovery with the directions in the following link.
http://forum.xda-developers.com/showthread.php?t=949699
Does anyone have an idea why this happens? I do remove the SD recovery card, and insert a blank SD card before rebooting.
Any help would be much appreciated!

Use 3.0.2.8 recovery

Thanks, I'll give that a shot right quick.

NewZJ said:
Use 3.0.2.8 recovery
Click to expand...
Click to collapse
Tried it and it boots back to the black screen with the line in the upper right corner.
Here's what I did.
Made the bootable sd card, copied over lastest build of cm7 and gapps.
Installed zips.
wiped data.
switch sd cards, rebooted
also tried it w/o wiping data.
Is there anything I'm doing wrong?

Wiping cache?

NewZJ said:
Wiping cache?
Click to expand...
Click to collapse
Should I do that before or after installing the zips?

wipe system, data, cache, then flash zips

NewZJ said:
wipe system, data, cache, then flash zips
Click to expand...
Click to collapse
Just tried that, no dice. It's still going back to the same screen.

Download the cm7 again, might be corrupt

NewZJ said:
Download the cm7 again, might be corrupt
Click to expand...
Click to collapse
Just downloaded a stable release, and it works. Is there any reason why the Nightly 80 wouldn't work, even after re-downloading it?

I'm also dealing with the same issue as well. The problem started when I tried to update from nightly 76 to 77. I also tried to flash to nightly 80, but no luck. I'm flashing a stable release now.
Edit: Flashing the stable release also worked for me. However, I wasn't able to flash the latest nightly over the stable build.

Yep.
Same problem here.
The stable works, boots fine, but the nightlies won't boot.
They go into the same flashing blue line.
I tried all the advice I could find, wipe system, cache, data and tried restoring to stock, still no dice.
I am using CWM 3.0.2.8.

I'm just a different flash method (verygreen's SD install), but found that nightlies beyond 75 won't boot without installing the .32 OC kernel. There's a discussion in both cyanogenmod experimental nook forum and in the dev forum here about it.

I guess I'll just wait until they resolve the issue then. I was really wanting to see how well the deep sleep worked.

Finally got the latest nightly from today with OC kernel and gapps. Running great so far. Just waiting on market being able to download.

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

Flashes unsuccessful, need help

Hi everyone. I'm new to the touch pad, but I have a lot of experience with the Epic4G from Sprint using CWM and flashing zip files. I have preware installed in my webos, and I have CM9 installed as well.
I've spent a few days reading threads here, but haven't been able to flash anything. I think I must be missing something.
Nothing happens when I flash zip files in CWM. I reboot to recovery, flash the zip file, wipe caches, but nothing is changed when I reboot the system. Been trying to install the unofficial with the working camera, and the oc kernel.
Thanks for any help.
sent from a secret underground bunker

mjben said:
Hi everyone. I'm new to the touch pad, but I have a lot of experience with the Epic4G from Sprint using CWM and flashing zip files. I have preware installed in my webos, and I have CM9 installed as well.
I've spent a few days reading threads here, but haven't been able to flash anything. I think I must be missing something.
Nothing happens when I flash zip files in CWM. I reboot to recovery, flash the zip file, wipe caches, but nothing is changed when I reboot the system. Been trying to install the unofficial with the working camera, and the oc kernel.
Thanks for any help.
sent from a secret underground bunker
Click to expand...
Click to collapse
Did you check md5s on the zips? Also, is your recovery updated?

As soon as I post a request for help, it works. Of course. Lol.
Yeah, I'm not sure what worked this time, but since I posted previously I set manual flash override in ROM Manager and installed the CM9 unofficial preview 7, the preview 9 update, and gapps, all went. I also installed the kernel that I mentioned, but it got stuck in a boot loop after and had to do the ROM over again.
sent from a secret underground bunker

[Recovery] Unofficial TWRP 2.6.3.0 for XT901 / XT907

UNLOCKED BOOTLOADER REQUIRED
Here it is: TWRP 2.6.3.0
I've tested backing up / restore, wiping, and installing an old backup (from ver. 2.6.0.0) and all seem to work. I also included the flag "HAVE_SELINUX := true" so it should be compatible with the newer 4.3 based ROMs (needs tested).
To install:
Download and unzip file ("img" was a few bytes over the 8mb forum limit)
Code:
fastboot flash recovery XT901-XT907-TWRP-2.6.3.0-recovery.img
BUGS: I have had the screen start very dim. Sometimes restarting the recovery would fix it, otherwise go to settings / screen, and set the timeout short so it goes out. Press power to turn on and it is at full brightness.
Enjoy!!
Thanks to:
TeamWin for TWRP.
Hashcode and Dhacker for STS-Dev Team source.
Djrbliss for unlocking the bootloader & providing root in the first place.
and mattlgroff

Thank you! Just tested it briefly and it works great. Glad the recovery is finally fixed to be able to use ADB. Was unable to use any TWRPs from 2.5.0.0+ as ADB was broken in the recovery.

CM 10.2 Build removed due to errors.

jbaumert said:
OP updated with link for TWRP compiled with CM10.2 sources
Click to expand...
Click to collapse
The recovery built with the 10.2 sources seems to have an issue with mounting the internal storage and sdcard, but the 1st one built is running perfect. I made a flashable zip of the 2.6.3.0 recovery for anyone who wants to simply flash it in recovery.

@mic213, Thanks for the sanity check. Any chance you have tried backup / restore of a 4.3 build?
Sent from my XT901 using Tapatalk 4

I was able to backup with it. Still hangs at reboot.
Sent from my XT907 using Tapatalk 4

netizenmt said:
Still hangs at reboot.
Sent from my XT907 using Tapatalk 4
Click to expand...
Click to collapse
Do you mean when you reboot from TWRP? I noticed that on other builds, but didn't think much of it.

Recovery Tools is a free app on Google Play. Simply download the Recovery IMG. file from this post, and then open the Recovery Tools app. Grant it root, and now you can simply flash the img. file from the app without having to go into fastboot or compress the file into a flash able zip. Once recovery is flashed phone will reboot into whichever recovery is the most recently flashed. About as basic and straight forward as can be.
---------- Post added at 09:34 PM ---------- Previous post was at 09:22 PM ----------
The recovery file works great, only bug after about 4 days of use would be the dim menu screen in recovery. Still very readable even when bug pops up. Thanks for the great upload

Thanks. I could never get 4.3 to reboot past the initial boot after install, and now it finally does.

scottocs said:
Thanks. I could never get 4.3 to reboot past the initial boot after install, and now it finally does.
Edit....ehh maybe. Still working on it.
Click to expand...
Click to collapse
just make sure everything is wiped and that you are using 4.3 Gapps, also look up the SuperSU 1.65 update, some people have had trouble keeping root when rebooting into 4.3. Flash 4.3 ROM then GAPPS followed by SuperSU update, I would suggest running 4.3 on TWRP 2.5 or 2,6 first. Once your able to run 4.3 on one of those, then good ahead and try flashing 2.6.3. If anything on your phone is 4.2 and trying to load onto 4.3 it will never make it far past the boot screen.

Edited because I started rambling and couldn't delete.
Long story short, I have been having issues wiping, installing, and recovering.
I was flashing from a 4.3 ROM to another 4.3 ROM and decided it would be a good idea to wipe internal. Messed me up good.
I went back to 4.2 finally fixed booting issue on getting stuck at boot image. (Wasn't even making it to the boot animation.) I'll wipe everything except internal like I did before and go from 4.2 to 4.3. Last time I did this I didn't have issues.

motoroid7 said:
I'm not sure what I did, but some ROMs suggest that you wipe internal memory. I did this but now I have the issue after installing a ROM and booting it up... playing with it, if I then go to reboot the phone at all I just get stuck on my boot image (not the animation.) This happens on regardless of what ROM I've installed.
I also now can't go back to my backups. They fail on restoring. [Most recent backup was made on 2.5.0.0, previous to that 2.3.2.3]
How do I fix my phone? I'm wondering if I need to fxz back to a rooted stock ROM to fix what's going on?
Click to expand...
Click to collapse
This happened to me on TWRP too. When I went to restore, it say that it failed. However, I decided to boot into system anyway. TWRP gave me a warning that no OS was installed but I went ahead and rebooted. It booted into my backed up ROM just fine but it needed to be set up, like I just had flashed it. Basically, the restore process restored everything but my data. I did a barebones set up then booted back into recovery and went to restore the same exact ROM. This time, I got my complete ROM, just as I had saved it. This is kind of a long process, but it's better than having to FXZ or using a utility to go back to stock.

RikRong said:
This happened to me on TWRP too. When I went to restore, it say that it failed. However, I decided to boot into system anyway. TWRP gave me a warning that no OS was installed but I went ahead and rebooted. It booted into my backed up ROM just fine but it needed to be set up, like I just had flashed it. Basically, the restore process restored everything but my data. I did a barebones set up then booted back into recovery and went to restore the same exact ROM. This time, I got my complete ROM, just as I had saved it. This is kind of a long process, but it's better than having to FXZ or using a utility to go back to stock.
Click to expand...
Click to collapse
It's too bad I can't seem to locate the delete button on these posts, I'll go ahead and edit it. I was finally able to flash LiquidSmooth v2.9 (Android 4.2). It finally booted up, I just went back in and flashed gapps. It restarted fine. The real test is going to see if I go to hit a regular reboot and it boots up normally again. If that's the case I'm fixed. I would like to flash back to SlimROM that I had, but it seems that's going to probably be difficult without it messing up again. Not sure what to do if it does again. I won't be wiping internal memory anymore. I didn't have issues going from 4.2 to 4.3 when I didn't do it.
Any idea why I get a funky e:error: unknown media 'datamedia' error all the time in TWRP? I've had that error since like v2.3.x.x

motoroid7 said:
It's too bad I can't seem to locate the delete button on these posts, I'll go ahead and edit it. I was finally able to flash LiquidSmooth v2.9 (Android 4.2). It finally booted up, I just went back in and flashed gapps. It restarted fine. The real test is going to see if I go to hit a regular reboot and it boots up normally again. If that's the case I'm fixed. I would like to flash back to SlimROM that I had, but it seems that's going to probably be difficult without it messing up again. Not sure what to do if it does again. I won't be wiping internal memory anymore. I didn't have issues going from 4.2 to 4.3 when I didn't do it.
Any idea why I get a funky e:error: unknown media 'datamedia' error all the time in TWRP? I've had that error since like v2.3.x.x
Click to expand...
Click to collapse
Not 100% sure, but i believe that when you wiped your internal memory on 4.3 you deleted the ROOT. SuperSU seems to be having issues with
carrying over root on 4.3 to some peoples devices, Ive had to flash SuperSU update 1.65 from recovery otherwise when ROM boots up I get stuck in a cycle of SU Binary update/reboot. Also make sure that in Developer Options in your custom ROM, that Root Access is set to APPS and ADB and the same in SuperSU - APPS/ADB. Now to clarify I may be merging two unrelated issues together. If so, my bad lol.. But from my experience running PaCMan 4.3 since August, and now running TWRPS 2.6.3 since OP , 4.3 ROOT will not revert back to 4.2 unless Recovery is included in the backup. One final suggestion, try flashing the boot.img from 4.2 before flashing your 4.2 restore. I was able to revert back to 4.1 restores when I upgraded to 4.2 but while running 4.2 I deleted the Root Data from Internal Storage, I strongly suggest looking up arrrghhhs Sept. 15th Kernal for XT 926 which runs the same for XT 907. It damn near all the way current with CM 10.2 merges, should make running which ever 4.3 ROM you want much easier. If you want to run a 4.2 Rom , look up arrrghhhs 10.1 kernal version.
Arrrghhhs xt926/907 kernal

Kyles1329 said:
Not 100% sure, but i believe that when you wiped your internal memory on 4.3 you deleted the ROOT. SuperSU seems to be having issues with
carrying over root on 4.3 to some peoples devices, Ive had to flash SuperSU update 1.65 from recovery otherwise when ROM boots up I get stuck in a cycle of SU Binary update/reboot. Also make sure that in Developer Options in your custom ROM, that Root Access is set to APPS and ADB and the same in SuperSU - APPS/ADB. Now to clarify I may be merging two unrelated issues together. If so, my bad lol.. But from my experience running PaCMan 4.3 since August, and now running TWRPS 2.6.3 since OP , 4.3 ROOT will not revert back to 4.2 unless Recovery is included in the backup. One final suggestion, try flashing the boot.img from 4.2 before flashing your 4.2 restore. I was able to revert back to 4.1 restores when I upgraded to 4.2 but while running 4.2 I deleted the Root Data from Internal Storage, I strongly suggest looking up arrrghhhs Sept. 15th Kernal for XT 926 which runs the same for XT 907. It damn near all the way current with CM 10.2 merges, should make running which ever 4.3 ROM you want much easier. If you want to run a 4.2 Rom , look up arrrghhhs 10.1 kernal version.
Arrrghhhs xt926/907 kernal
Click to expand...
Click to collapse
To piggy back on general advice: I found I was having all sorts of problems going from 4.2 to 4.3. What finally did the trick was I wiped Dalvik, System, Cache AND I formatted data. The formatting was what did the trick.

When you wipe in twrp 2.5+ the recovery does not delete data/cache from internal (system) unless user mounts system prior to wipe. Wiping system cache, data, and dalvik cache is a full system wipe. Recommended if switching ROM rather than flashing nightly. This way no files from a AOKP ROM stick around and try to associate with your new CM based ROM.
Sent from my XT907 using Tapatalk 2

Thanks for the advice guys.
I was finally able to successfully getting my phone to work again last night (very early in the AM). It's very strange. I actually had 0 issues going from LiquidSmooth v2.9 to LiquidSmooth v3.0 (4.2 to 4.3). Though it was from the same dev could be part of it. It wasn't until I tried flashing from SlimROM/4.3 to CM10.2 nightly (where I wiped internal memory requiring me to type "yes".) Another thing is strange is even though it was saying I lost root in TWRP, I'm not sure that I ever did, unless TWRP just re-installed it when I reboot recovery automatically... because I finally told it no when asked if I wanted to re-install root? Then I was finally able to get LiquidSmooth v2.9 bootable and stable.
Again, thanks for all the help guys. I just wish I had a little bit understanding what I all did to finally get it to boot up. It was pretty early in the morning... going on 5/6AM. So I was pretty tired doing all of this. I just knew I couldn't let my phone not be up and running by morning.

I did a backup last night, flashed a 4.3 ROM which had reboot issues, and then restored with this version. I had zero issues, unlike when I was trying to restore with the previous version. Thank-you for your work.

It works with the xt902 too. Thanks!

What's the difference between the link in the first post and the one in the fourth? One of the is broken? Which one has been built with the CM10.2 sources?
I'm using a CM10.2 ROM... Which one should I peek?
Thanks!