Related
First of all, this is not my work. I only compiled it.
This is the usual ClockworkMod recovery, compiled from the CM7 sources with additions/modifications by j_r0dd. What I've done is only to compile it for the Nexus One. For details, check out the link to j_r0dd's original thread for the Nexus S.
The credits go to Koush for the recovery itself and to j_r0dd for the modifications. I've only tested it quickly on my Nexus One, and it seems to work.
j_r0dd said:
This is based on the latest CM7 source which I modified for myself. I take no credit for the recovery whatsoever, but I will take all the blame for my mods . We all know this is Koush's hard work. Just some things were driving me crazy personally. First was the confirmation menu. I really got sick of scrolling through all those "No"s just to flash something, so i changed it for me personally and just thought I would share. I also created a proper wipe menu. I got sick of some wipes in the main menu and the rest in the "advanced" menu. I made this more Amon_RA like. See the attached screenshot for my changes. That change has led to a few others by me. flash with fastboot or flash_image. THESE ARE NOT IN ROM MANAGER. Also if you have an issue with this take it up with me NOT Koush.
Click to expand...
Click to collapse
Original Nexus S thread with changelog here.
Download:
recovery-clockwork-5.0.2.7.111102-j_r0dd_mod-passion.zip
(old) recovery-clockwork-5.0.2.7.111027-j_r0dd_mod-passion.zip
Change log:
02-Nov-2011 (v5.0.2.7):
Merged 5.0.2.7 sources from CM7 repo again (some bugfixes)
Added option to wipe cache partition and dalvik cache at the same time
27-Oct-2011 (v5.0.2.7):
Merged 5.0.2.7 sources from CM7 repo (support for internal/external sdcard in backup/restore)
07-Oct-2011 (v5.0.2.6):
Rearranged wipe menu to avoid accidental factory wipes
Added "Reboot Bootloader"
Moved SD Card partitioning into a function of its own for both int/ext SD card
Merged 5.0.2.6 sources from CM7 repo
Added a menu choice of ext2/ext3/ext4 when partitioning SD card
25-Sep-2011 (v5.0.2.3):
Updated to j_r0dd's 5.0.2.3 version. Currently no changes made by myself.
17-Jun-2011 (v4.0.0.5):
Moved the "Wipe data/factory reset" to the bottom of the wipe menu to reduce the risk of accidental factory wipes.
19-Jun-2011 (v4.0.0.5):
Added "Reboot bootloader" option in advanced menu.
Added the ext4 modifications kindly supplied by roalex. Needs testing. Please make a proper nandroid backup with a proven working recovery version before trying this.
20-Jun-2011 (v4.0.0.5):
Added "Show log" in the advanced menu. This can help when reporting errors here. Use it.
21-Jun-2011 (v4.0.0.5.z110621):
Reverted and correctly added roalex's ext4 additions.
Modified recovery.fstab for ext4 support on some devices.
23-Jun-2011 (v4.0.0.5.z110623):
Removed NULL ext3 in recovery.fstab to hopefully get ext4 working properly.
06-Jul-2011 (v4.0.0.5.z110706):
Added "Advanced backup". Now you can backup/restore individual partitions.
Some other commits from other devs in github
Changed file limit from 10000 to 50000 in unyaffs. Should help when restoring large data partitions fails.
17-Jul-2011 (v4.0.1.0.110717):
Rebased completely on j_r0dd's 4.0.1.0 source and removed roalex's ext4 additions, as it wasn't working for everyone. Now trying with the original ext4 support which is included in CWM.
20-Jul-2011 (v4.0.1.4.110720):
Bug fixes
Disclaimer
These recoveries are compiled using the latest commits from koush, j_r0dd and others. That means they haven't been thoroughly tested and might have minor/major issues. I take no responsibility for any damages this thing might cause, but most things should work as intended. If you want something guaranteed to work, I think you should stick with one of the older versions.
Source code available here.
Thanks for compiling and posting this update here. I hope it works better than 3.0.0.5
If you're testing it, let me know if it works.
Sent from my Nexus S using Tapatalk
did anyone test this, does it resolve the damaged sd-ext partition in 3.0.0.5 one ??
gwassef said:
did anyone test this, does it resolve the damaged sd-ext partition in 3.0.0.5 one ??
Click to expand...
Click to collapse
Not using sd-ext on my N1, so I don't know. But 3.0.0.5 never damaged it back when I was using sd-ext.
Sent from my Nexus S using Tapatalk
I got it damaged 2 times, I thought it was my S2E app, but when i sent them they told me remove the 3.0.0.5 as it is known with this issue, install an older version. Since i installed the release before this one, i have no problems at all.
zyonee said:
Not using sd-ext on my N1, so I don't know. But 3.0.0.5 never damaged it back when I was using sd-ext.
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
zyonee said:
If you're testing it, let me know if it works.
Click to expand...
Click to collapse
So far I tested backing up, restoring, wiping and flashing all seemed to work fine.
Can't tell anything about compatibility to SD-ext, but a compiled version of CWM 3.0.24 from the Blandroid ROM showed no problems with SD-ext. I guess this one won't make problems either.
Need to test if ROMManager is still fully functional with this version.
Kelvino9 said:
So far I tested backing up, restoring, wiping and flashing all seemed to work fine.
Can't tell anything about compatibility to SD-ext, but a compiled version of CWM 3.0.24 from the Blandroid ROM showed no problems with SD-ext. I guess this one won't make problems either.
Need to test if ROMManager is still fully functional with this version.
Click to expand...
Click to collapse
Should work, but you'll need to try it.
For some reason, ROM manager doesn't work for me. It downloads the rom, asks me if i want gapps, wipe /etc, then it reboots but NOT in recovery, and if i select Recovery, doesn't work. (goes back to original screen)... any ideas..?
joesatri said:
For some reason, ROM manager doesn't work for me. It downloads the rom, asks me if i want gapps, wipe /etc, then it reboots but NOT in recovery, and if i select Recovery, doesn't work. (goes back to original screen)... any ideas..?
Click to expand...
Click to collapse
Is the recovery properly flashed? Works well on my NS
Sent from my Nexus S using Tapatalk
sorry, blonde moment :L
Installed this recovery in my N1, works great. Maybe stupid question...Is there any way to make recoverys font bigger....There is so many space, but the font is so small...
Spakainz said:
Installed this recovery in my N1, works great. Maybe stupid question...Is there any way to make recoverys font bigger....There is so many space, but the font is so small...
Click to expand...
Click to collapse
You'll have to ask koush or the other devs about that. I only compiled from source. I'm not that skilled at modding this kind of code...
Sent from my Nexus S using Tapatalk
This recovery works well for me. Flashed using fastboot.
I also used this recovery to reformat the sd-ext partition and now my nandroid backups complete without freezing (they would freeze on the sd-ext backups last time requiring a battery pull).
Thanks for compiling and sharing this!
-D
Kelvino9 said:
So far I tested backing up, restoring, wiping and flashing all seemed to work fine.
Can't tell anything about compatibility to SD-ext, but a compiled version of CWM 3.0.24 from the Blandroid ROM showed no problems with SD-ext. I guess this one won't make problems either.
Need to test if ROMManager is still fully functional with this version.
Click to expand...
Click to collapse
restoring doesn't work with sd-ext (1GB ext4 in my case): it's always aborting during restoring data! no cache and sd-ext restoring and no "restore completed" CWM message but jumping back to the CWM main menu.
it's the same with the other CWM3.2.0.1 for Nexus One.
:-(
This Corrupts EXT partition!
This recovery corrupts EXT partition while the 2.4.0.1 doesn't restore!!! I'm staying away from clockwork recoveries from now on! I'm sick and tried of restoring corrupt ext partitions!
sir*mez said:
This recovery corrupts EXT partition while the 2.4.0.1 doesn't restore!!! I'm staying away from clockwork recoveries from now on! I'm sick and tried of restoring corrupt ext partitions!
Click to expand...
Click to collapse
So it's safe if not using sd-ext. Sorry I can't help solve the problems...
Sent from my Nexus S using Tapatalk
accuphase said:
restoring doesn't work with sd-ext (1GB ext4 in my case): it's always aborting during restoring data! no cache and sd-ext restoring and no "restore completed" CWM message but jumping back to the CWM main menu.
it's the same with the other CWM3.2.0.1 for Nexus One.
:-(
Click to expand...
Click to collapse
Yes, now having the same problem with sd-ext backups too.
zyonee said:
Only available in standard orange, I actually can't be bothered to find out how to make different color variants.
Click to expand...
Click to collapse
Aww
But still, thanks for bringing it over to the N1.
Updated OP to version 4.0.0.0.
Has anyone discovered what's the problem with restoring nanodroid backups with romracer's Recovery?
I see many of us have the same problem, restore work almost fine, it restores the operational system, but does not restore accounts and applications...
Edit:
New information:
I created two new backups as i am trying different ROMs.
I created one for CM7 and tested the restore, everything works perfectly! All apps and accounts...
Also created one for nCrust, this one have the same problem as i reported, the system is there, but it lacks all applications and accounts...
I also noticed that the nanodroid file is 0 bytes for the cases where the error occurs, and 1kb in the case where it worked fine.
Thanks
BTW, i am not using Rom Manager...
I'm not having an issue at all. Did you use romracer's CWM to backup?
Sent from my MB860 using Tapatalk
I used it to backup and restore and it restored everything; apps and accounts included.
LordOfTheSnatch said:
I'm not having an issue at all. Did you use romracer's CWM to backup?
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
Yes, i did!
I flashed the last romracer's CWM yesterday, and created the backup next...
There are other users with this problem as well, but i can't find a fix for that anywhere...
luizffgarcia said:
Yes, i did!
I flashed the last romracer's CWM yesterday, and created the backup next...
There are other users with this problem as well, but i can't find a fix for that anywhere...
Click to expand...
Click to collapse
Did you backup webtop (optional)? And upon selecting restore, are you trying to restore webtop?
luizffgarcia said:
Has anyone discovered what's the problem with restoring nanodroid backups with romracer's Recovery?
I see many of us have the same problem, restore work almost fine, it restores the operational system, but does not restore accounts and applications...
Thanks
Click to expand...
Click to collapse
I have backed up and restored twice already with no problems...what issues are you running into?
Swiftks said:
Did you backup webtop (optional)? And upon selecting restore, are you trying to restore webtop?
Click to expand...
Click to collapse
I did not selected webtop when created the backup, and did not selected the webtop upon restore.
I was actualy trying to restore everything i had installed, but i don't use webtop that much, so i decided not to include it...
gpagador said:
I have backed up and restored twice already with no problems...what issues are you running into?
Click to expand...
Click to collapse
The issue is that when i restore the backup, i get a clean Gingerbread, without any of my previously installed applications or accounts!
you aren't doing a wipe cycle after the restore are you?
diedemus said:
you aren't doing a wipe cycle after the restore are you?
Click to expand...
Click to collapse
LOL!!
No
New information:
I created two new backups as i am trying different ROMs.
I created one for CM7 and tested the restore, everything works perfectly! All apps and accounts...
Also created one for nCrust, this one have the same problem as i reported, the system is there, but it lacks all applications and accounts...
I also noticed that the nanodroid file is 0 bytes for the cases where the error occurs, and 1kb in the case where it worked fine.
Any suggestions?
Any ideas? Noone experiencing this issue??
luizffgarcia said:
Also created one for nCrust, this one have the same problem as i reported, the system is there, but it lacks all applications and accounts...
I also noticed that the nanodroid file is 0 bytes for the cases where the error occurs, and 1kb in the case where it worked fine.
Any suggestions?
Click to expand...
Click to collapse
I'm also running piCRUST (v0.7) and romracer's CWM recovery 3.2. I will try this and report back the results.
P.S. would help us if you gave ROM, kernel, and recovery versions, etc. Thanks...
i just now did a backup and restore from within romracer's v3.2 recovery and all my post-piCRUST install tweaks are still in place. WiFi even came right back up with my WPA2 connection as it was before I rebooted for the test.
Of course, if the recovery actually did nothing at all then this behavior is expected.
Seriously, this part of the recovery is probably lifted wholesale from the codebase before romracer got involved, with the exception of being able to choose the external SD card for backup storage. That's what I did this first time. Now for another test, but this time I will backup to the internal card.
BRB...
---------------
No problems either with a backup and restore to/from the internal SD card. I just stepped through the recovery menu and chose all the defaults except for the webtop part.
Looking forward to your report of installed versions OP. When you boot into the recovery the very first line should say:
"CWM-based Recovery v4.0.1.4-atrix3.2"
Is this what you see?
luizffgarcia said:
There are other users with this problem as well, but i can't find a fix for that anywhere...
Click to expand...
Click to collapse
I haven't seen a lot of complaints about this myself, but up until now I've only been monitoring romracer's original post in the dev section. Can you point us to another thread where this is mentioned?
Not doubting you, I'd just like to see if there's some pertinent info about this issue that we're missing. Thanks...
Also, if you are choosing an Advanced Restore, please tell us exactly what options you are selecting, as they are described in the recovery menu itself (e.g. not "accounts", etc.). Thanks again...
anyone else having this happen?
makes backups ok but wont restore anything freezes at the white htc screen
You need to run your backups and recovery from within CWM. See Absolute_Zero's thread in the Development section for more info (last post).
Happened to me yesterday.
I thought I had corrupted my backups ...
Its not working for me no matter what i try any ideas?
Same problem here, just had to restore and couldnt. backups always made directly from recovery.
There are a lot of reports on this recently
http://forum.xda-developers.com/showthread.php?t=1179386
Visit the above link and revert back to an older recovery if you have backup from recovery pre-5.x, if not flash a rom from scratch. It will load up, just did it myself.
CWR 5.0.1.0 seems to work fine as I've said. I've restored backups from CWR4 which someone suspected to be the problem. It's not as I just did it with 3 different older backups to confirm and subsequently restored to my present backup all using RomManager (since that was more than likely what most users with problems were using).
I will continue testing a few scenarios but as of right now, I can't reproduce the problem. I'm not saying it doesn't exist. I just can't reproduce it without more details.
If you're still having problems AND you've updated to the latest RomManager (4.4.0.5 at this time) AND confirmed you've flashed the lastest CWR (5.0.1.0 at this time) then pastebin your /sdcard/clockworkmod/report.log for someone to look at.
Edit:
I suppose I should mention (although it should be clear) that if you restore a backup you no longer have the updated version of RM so you will need to update it again before it will work with your current recovery.
as far as i can tell gb sense roms with the 3.0 sense seem to be the common issue as far as not restoreing. and it is definitly a known issue... something about a ext3 or ext4 partion or some crap.....
Perhaps it's just backups of Sense-based roms in general. I haven't run Sense since 2hrs after I bought the thing so all the backups I was trying that worked perfectly fine were all aosp. This makes the most "sense" of anything I've heard so far. It may have something to do with the partition format being included in the images now so CWR5 restores older backups without that detail. I have a hard time believing koush wouldn't have included some way to handle those though.
I went back to my old recovery
Sent from my tbolt running ShiftTh3ory AOSP
It seems to be the ext4 not supported
i will also add that backups made on 5x recoveries will restore on 4x as long as its not from a ext4.
i hope that makes some kinda sense to somebody but these are the facts.
So it seems that the ext4 is just not supported on the 5x recovery. I just hope they are working on it and are aware of it
Yes, after several restore attempts of a couple sense roms using 5.0.1.0 I hang at the splash screen.
So today I installed 2 roms from scratch after not being able to restore prior backups created with with 4.x. After each fresh install today I booted into recovery and performed a backup using 5.0.1.0 (RM says that is the version installed).
Recovery will NOT restore the fresh 5.x backups either. Backup and restore were of sense roms.
Just successfully performed a restore of an aosp based rom while writing this post.
Can you see if ext4 partitions can be mounted in adb shell in recovery?
Also, are sense roms ext3 or ext4? What is the exact error?
Can someone pull a /tmp/recovery.log after a failed restore and pastebin it?
I believe I just fixed this in 5.0.2.1. Let me know.
Koush said:
I believe I just fixed this in 5.0.2.1. Let me know.
Click to expand...
Click to collapse
Koush,
The backups in 5.0.2.1 have the Cache, Data and System img files in zip format which is not the format of my other backup's made with the older versions of CWM.
Do you expect 5.0.2.1 to be able to restore the older backups or just ones made in 5.0.2.1?
Yes the last version fixed the mounting issue 5.0.2.1 is what you want!
Thanks Koush
Older backups restore just fine. Happy Days
Hello all, greetings from your friendly neighborhood newb! In following the edicts set forth by the XDA PTB, I was attempting to solve on my own a minor problem with my gallery when I encountered a much more serious problem that seems to be getting progressively worse with every action I take. I don't dare try anything else on my own. I've tried Google searches with "xda i777..." in front to no avail. I apologize if the answer if it there and I just haven't found it. Thanks in advance to anyone who helps me.
I'm on AOKP/N.E.A.K./UCPLC5
A few days ago, I noticed the gallery icon on my home screen wasn't working, but I was still able to access the gallery through appsorganizer, which is the primary way I access apps, so I wasn't concerned. Then I couldn't play downloaded videos, etc. Long story short, my phone won't play downloaded, streaming, or previously recorded videos in the gallery, browser, skyfire, YouTube, it third-party apps. So I
-switched launchers to test gallery (icon on desktop was there, but said "app not found.")
-reflashed gapps.zip
-factory reset/wipe cache then flash gapps.zip
-restore nandroid backup, soft bricked phone
-tried to restore more recent backups, found one that worked on the third try (got a couple "error while restoring /system")
-gallery opened, videos played, pics weren't there ("no external storage found")
-restored most recent nandroid to make sure pics weren't gone (in retrospect, plugging it into the computer or using a file manager would have been better method)
-tried to restore previous nandroid, and got
Checking MD5 sums...
Erasing boot image before restore...
Restoring boot image...
System.img not found. Skipping restore of /system
Data.img not found. Skipping restore of /data.
Android_secure not found. Skipping restore of /sdcard/android_secure.
Cache.img not found. Skipping restore of /cache
-restored latest nandroid, and started searching the heck out of Google until the worrywart part of my brain demanded that I post on xda RIGHT THIS SECOND!! (The same portion of my brain keeps whispering "super bug.")
It may or may not be worth noting that I was on UCKK7 before I flashed AOKP.
Thank you to anyone who helps me. I've grown rather fond of my i777 over the past few weeks and I really hope it isn't too badly damaged.
Sent from my SGH-I777 using Tapatalk 2
pendragonia said:
Hello all, greetings from your friendly neighborhood newb! In following the edicts set forth by the XDA PTB, I was attempting to solve on my own a minor problem with my gallery when I encountered a much more serious problem that seems to be getting progressively worse with every action I take. I don't dare try anything else on my own. I've tried Google searches with "xda i777..." in front to no avail. I apologize if the answer if it there and I just haven't found it. Thanks in advance to anyone who helps me.
I'm on AOKP/N.E.A.K./UCPLC5
A few days ago, I noticed the gallery icon on my home screen wasn't working, but I was still able to access the gallery through appsorganizer, which is the primary way I access apps, so I wasn't concerned. Then I couldn't play downloaded videos, etc. Long story short, my phone won't play downloaded, streaming, or previously recorded videos in the gallery, browser, skyfire, YouTube, it third-party apps. So I
-switched launchers to test gallery (icon on desktop was there, but said "app not found.")
-reflashed gapps.zip
-factory reset/wipe cache then flash gapps.zip
-restore nandroid backup, soft bricked phone
-tried to restore more recent backups, found one that worked on the third try (got a couple "error while restoring /system")
-gallery opened, videos played, pics weren't there ("no external storage found")
-restored most recent nandroid to make sure pics weren't gone (in retrospect, plugging it into the computer or using a file manager would have been better method)
-tried to restore previous nandroid, and got
Checking MD5 sums...
Erasing boot image before restore...
Restoring boot image...
System.img not found. Skipping restore of /system
Data.img not found. Skipping restore of /data.
Android_secure not found. Skipping restore of /sdcard/android_secure.
Cache.img not found. Skipping restore of /cache
-restored latest nandroid, and started searching the heck out of Google until the worrywart part of my brain demanded that I post on xda RIGHT THIS SECOND!! (The same portion of my brain keeps whispering "super bug.")
It may or may not be worth noting that I was on UCKK7 before I flashed AOKP.
Thank you to anyone who helps me. I've grown rather fond of my i777 over the past few weeks and I really hope it isn't too badly damaged.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
dont think you can restore a GB nandroid from ICS. flash back to GB, then try your nandroid.
Or possibly the file got messed up?
MotoMudder77 said:
dont think you can restore a GB nandroid from ICS. flash back to GB, then try your nandroid.
Or possibly the file got messed up?
Click to expand...
Click to collapse
I'm pretty sure you can, but I also applaud this guy for the amount of detail he put in his post. Even though I don't have an answer for him he did everything he should have before posting.
Sent from my SGH-I777 using Tapatalk 2
Nick281051 said:
I'm pretty sure you can, but I also applaud this guy for the amount of detail he put in his post. Even though I don't have an answer for him he did everything he should have before posting.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
yea I wasnt sure on that one. but would make sense as different kernals, different recovery.
Always best to use the same recovery/kernal to restore, as you did the backup with.
Nick you beat me to it. This guy wins the award for best "help me" thread ever!
Good luck bro! You came to the right place.
Clay
Sent from my PINK GS2 using xda app
MotoMudder77 said:
yea I wasnt sure on that one. but would make sense as different kernals, different recovery.
Always best to use the same recovery/kernal to restore, as you did the backup with.
Click to expand...
Click to collapse
Hmm...I have tried several different kernels, all were ICS-based. I wouldn't even know which one to flash for which nandroid. I'll keep that in mind for future reference though.
Sent from my SGH-I777 using Tapatalk 2
pendragonia said:
Hmm...I have tried several different kernels, all were ICS-based. I wouldn't even know which one to flash for which nandroid. I'll keep that in mind for future reference though.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
for future reference? you give up?
If your nandroid is from a GB kernel, then flash a GB kernel, just need the kernel, boot into recovery and attempt to restore.
Thats what I would do to narrow down the backup being messed up.
I believe this may be a problem with touch recovery nandroids versus non touch. I remember reading about that somewhere, anyone confirm?
Sent from my SAMSUNG-SGH-I777 using Tapatalk 2
I'm not the developer but kitkat nightly is out.
ROM download: http://download.cyanogenmod.org/?type=nightly
gapps download: http://wiki.cyanogenmod.org/w/Gapps
Change log: http://changelog.bbqdroid.org/#/t0lte/next
You might experience problem with twrp so it might be better to use CWM.
Also I believe it'll be a full wipe installing the ROM the first time. Good luck.
ps. if the cm dev wants to create a new thread for this ROM, please do so and I'll ask a moderator to close/delete this one.
here are the results of my trials earlier today. ROM is working nicely now. at least on the apps I've tried it on. Still using dalvik though.
-------------------------
some tips (all my testing was done using official CWM 6.0.4.1):
1. Definitely do not use TWRP unless there's an update to 2.6.3.7. (seems TWRP could work if one use the modified version. see message below. I haven't tested this myself.)
2. using CWM and exFAT is a hit and miss. A fresh install and the ROM can't see sdcard. The only time the sdcard was detected was after a nandroid restore.. Since all the files in my SDcard is < 4GB, I can use FAT32.
3. nandroid restore = no mobile connection for me. this was fixed by reflashing the even if it's the same nightly (example: say I made a nandroid backup of 17-Dec nightly ROM. due to having messed up stuff, I decided to restore my backup. as said above, this will result in no mobile connection. but if I reflashed the zip file for 17-Dec nightly, this will fix the problem)
4. the hangouts included in the gapps (See link above to CM wiki) resulted in FCs when trying to make a video call. this was fixed by uninstalling hangouts using titanium and reinstalling it via the playstore.
5. I believe all official recoveries need updating to support 4.4 properly.
---------------------------------------------------------------------------
original message is below. you can see the problems I've encountered during testing.
just flashed the nightly for t0lte using TWRP 2.6.3.7 and somehow it can't see my SIM. Will be flashing again using latest CWM (6.0.4.1 as of now).
initial observations:
1. NTFS work on SD cards
2. 2 launchers are present (launcher and launcher3)
3. looks better than Jb (it could be placebo effect because kitkat is new)
update: definitely use CWM at least for t0lte. ROM has recognized my SIM.
update2: been playing around with the ROM and when I tried to access my NTFS-formatted SDcard, it cannot see. I had no problems at all with my SDcard using TWRP. I can even browse the folders inside it using file manager. I also had a problem with the built-in hangouts and video chat. I'm getting FCs.
update3: restoring from CWM nandroid backup = no cellular/mobile connect. Can't even call anyone.
update4: update to update3. I did lose cellular/mobile connectivity (phone can't find sim) BUT it can recognize my NTFS-formatted sdcard now!
update5: removing hangouts via titanium and then reinstalling the playstore version, I can make a video call.
update6: restore from nandroid (which gives me a working NTFS-formatted sdcard) and then reflashed the ROM. I got mobile signal but no sdcard. I guess I can always format it at as FAT32 which I'm doing now.
mrjayviper said:
update3: restoring from CWM nandroid backup = no cellular/mobile connect. Can't even call anyone.
update4: update to update3. I did lose cellular/mobile connectivity (phone can't find sim) BUT it can recognize my NTFS-formatted sdcard now!
Click to expand...
Click to collapse
Keep us posted. Would love to know how to sort out the data connection/sim issues before I flash.
Cheers.
Sheikx800 said:
Keep us posted. Would love to know how to sort out the data connection/sim issues before I flash.
Cheers.
Click to expand...
Click to collapse
gave up on making an NTFS-formatted sdcard work on a new flash. I'm formatting my sdcard now to FAT32. It'll probably be fixed down the road.
and I think flashing the ROM after restoring from nandroid backup will bring back mobile signal. At least that's my conclusion. But I do get a signal only if I use CWM.
Yea twrp 2.3.6.7 is buggy. Look for twrp 2.3.6.1, it's modified and will work with cellular signal. Keep us posted.
The modded twrp is linked on one of the last pages in the beanstalk thread iirc
Sent from my GT-N7105 using XDA Premium 4 mobile app
updated 2nd post to give some tips on how to install ROM properly. seems to be working nicely now. That said, I don't have much app/games installed on my phone compared to my tablet (50-60 apps on the phone compared to 90+ on the tablet. mostly games).
a sample list of apps installed on phone are dashclock, lightflow, dynamicnotifications, various messaging. various Google apps and 1 game.
Installed with latest CWM and Data works great, no issues with Calls / LTE etc.
ROM seems really good so far, using Google's OK Google is fun but does tend to drain the battery faster, that said I will switch to a different kernel as I miss Viper so will most likely go with Devil, hopefully it helps with the battery.
I've never had an issue with CWM, I upgraded to the latest version using ROM Manager.
My tip for flashing is to always wipe perform a full wipe plus Cache, Davlik and System before flashing and Cache, Davlik after.
Miss some features / tweaks from other Roms but I know that CM is the best stock experience out there so no problems there.
IMO no issues running as a daily driver.
Proximity sensor not working. Is it just me or...?
Tapatalk-kal küldve az én GT-N7105-el
I had problems to are you running any other kernels or are you on the stock one?
Sent from my GT-N7105 using XDA Premium 4 mobile app
CWM 6.0.3.1 Touch (I think!) doesn't work, got bad flash error 7 (I think!) every time.
ROM manager update to 6.0.4.1 to non-touch* worked like a charm.
(*because I'm both tight and lazy)
---------- Post added at 10:14 PM ---------- Previous post was at 10:04 PM ----------
richyy74 said:
Proximity sensor not working. Is it just me or...?
Click to expand...
Click to collapse
Definitely not working on a clean install, with a few apps installed.
According to a test app the light sensor is responding but the prox is not.
Camera app is buggy, useless in fact. 3rd party camera is fine temporary replacement.
Facebook edit post doesn't allow cursor placement, facebook app 4.4 problem I assume.
Is anyone able to successfully set the DPI to another value in build.prop? Mine always defaults to 320 after each reboot.
Update:
I seem to be able to edit/save build.prop changes fine in 12/07/13 nightly.
Had the same flash error 7 corruption had boot loop into recovery and had to use a nand backup to get back. Did a clean install, and the process went well. Only issues so far are my Microsd can't be seen. And can't manage to get the 'Ok google' stuff working. A few random crashes but overall working well so far.
So would love some help with the Microsd issue as this is quite important?
Sent from my GT-N7105 using Tapatalk
leebag said:
Had the same flash error 7 corruption had boot loop into recovery and had to use a nand backup to get back. Did a clean install, and the process went well. Only issues so far are my Microsd can't be seen. And can't manage to get the 'Ok google' stuff working. A few random crashes but overall working well so far.
So would love some help with the Microsd issue as this is quite important?
Sent from my GT-N7105 using Tapatalk
Click to expand...
Click to collapse
my NTFS-formatted sdcard can be seen when I use TWRP 2.6.3.7. not so with CWM 6.0.4.1.
I'm running the modified TWRP mentioned in page1 but my sdcard is still FAT32. I'll format my sdcard and see if it works.
I'm going back to CWM. just noticed all sorts of problems on my phone running the modified TWRP. :/ sucks!
No radio signal when flashing with TWRP 2.6.3.7. Flash again with CWM 6.0.4.1 radio is back. No problem with the external SD card (FAT32).
AkiraBBQ said:
No radio signal when flashing with TWRP 2.6.3.7. Flash again with CWM 6.0.4.1 radio is back. No problem with the external SD card (FAT32).
Click to expand...
Click to collapse
@mrjayviper Wasn't twrp 2.6.3.7 a bugged and accidental upload?
(At least people kept telling me a short while ago. )
Try the modded twrp 2.6.3.1 been linked a few days ago in the beanstalk tread
Sent from my GT-N7105 using XDA Premium 4 mobile app
Updated to the latest nightly and running Agni kernel and all running well.
Battery life is great, loving this ROM so far!
is anyone been able to successfully make a video call on hangouts? it's been FCing on me. using cwm and twrp.
I just tried the PA full gapps and no luck with that. thanks