Related
Hello dear xda community.
I own a Defy+ with 2.3.6 stock Kernel and want to switch to CM7. (Do I need another Kernel?)
Which build do you prefer, I can't decide between:
7.1.0-11
Quarks nightly
Epsylon3s nightly
maniacs nightly
Basically I'm just looking for a stable AOSP/blurfree ROM, so which one is the stablest up to now?
Which of the mentioned ROMS need/work with the battery/camera patches and are there different versions of these patches around? (here and here)
Am I right that there should be no more problems than battery and camera functionality up to now?
Thank you in advance
Edit: Another question I forgot:
In the title of the 7.1.0-11 it is written "Android 2.3.7". So does this mean even though the zip doesn't contain a Kernel it does contain 2.3.7? I couldn't find a 2.3.7 kernel for the Defy+ elsewhere.
Edit 2: I found an answer concerning whether to use 7.1.0-11:
The latest nightlys are stable, don't use 7.1.0-11
Click to expand...
Click to collapse
Though thats a tough statement whenever it comes to nightlys, I assume I will trust him here.
Like I wrote to you (by PM) before, I don't own a Defy+, but I'd say go on and try the latest Defy+ nightly which is from Quarx at this time: cm72-20120308-NIGHTLY-Defy+.zip md5 checksum: 8df5562b60ded2978a38eb9ac21bdc8e .
Make a nandroid backup of your system (custom recovery / advance / backup&restore / backup all) before installing it and then see how it goes from there...
If it really doesn't boot up, you have problems with battery not fully charging, camera or other things, you can find solutions or ask again - but at least you'll have a nand to fall back on... so no risk involved.
I haven't tried that specific March 8th Defy+ nightly yet, but I bet that it is probably at 1 or 2 small fixes close to perfection and you won't regret installing it I assure you.
Just be patient at first boot and wait a good 5-6 minutes before thinking being in a bootloop and do anything crazy..
God luck.
I tried cm72-20120308-NIGHTLY-Defy+.
Wifi is not working ..
and battery yet to check..
also camera prob..
Hi AL
i reinstalled it and now wifi is working..
But the problem now is battery..
It drains off quickly.
Also i used get atleast 50% signal at my home..
but now with this, its not catching the signal at all..
Its fine at places where full signal is there..
Let me recommend CM7 WhiteRabbit Edition 1.3! Pure awesomeness + Aroma touch based installer. This means you can customize your installation (e.g. defy+ battery fix, what apps you want installed, witch wifi driver, etc)!!
Install the PLUS edition for gingerbread kernel!
hafizca said:
Hi AL
i reinstalled it and now wifi is working..
But the problem now is battery..
It drains off quickly.
Also i used get atleast 50% signal at my home..
but now with this, its not catching the signal at all..
Its fine at places where full signal is there..
Click to expand...
Click to collapse
I was using the CM7 for Defy+ 140312 build and everything worked fine for me! Also played all sorts of games like Dead Space, Shadow Gun with ease!
you should try WUIU:http://forum.xda-developers.com/showthread.php?t=1161110
works great!!!!
The whiterabbit version problem
Hey
i did download the whiterabbitplus version as i has android 2.3.6 with kernel also 2.3.6
i rooted it as mentioned using the latest superclick
i theninstalled sndinit 2.0 and attempted to enter recovery but i got the triangle with the xclamation mark so i installed clockworkmod and it got me into recovery alright
here i format cache ,data wipe,factory reset etc and say install "zip from sd card "
auroma installer starts off fine works upto letting me select the options and everything ...just when it says "click next to start " when i do ..it just says
system/mount
error(system/mount) fail or something ...
and pretends its complete and asks for reboot
after reboot i discover no changes and it just acts like a facotry reset too place and i need to configure everything again
ive tried everything on the net ..please do help ..should i flash a lower version like froyo and try again ??
Maniacs builds are great, you should check them out.
Johnny_Queste said:
you should try WUIU:http://forum.xda-developers.com/showthread.php?t=1161110
works great!!!!
Click to expand...
Click to collapse
Sag1e said:
Maniacs builds are great, you should check them out.
Click to expand...
Click to collapse
Please, guys, stop the confusion. Both of those are Froyo only.
@athenus Have you managed to flash any ROM? From those you have mentioned...
CM7.1 - Froyo only
maniac's builds - Froyo only
Epsylon's builds - there are both Froyo and Gingerbread available
Quarx's builds - both Froyo and Gingerbread available <- this should be your choice. The latest Quarx's builds is awesome and you can find it here - http://quarx2k.ru/cm7-nightly-defy+/
P.S. Quarx is currently the only developer that actually owns a DEFY+.
If you are confused still, feel free to PM me, as I can't keep with all the threads I've posted in
hafizca said:
Hi AL
i reinstalled it and now wifi is working..
But the problem now is battery..
It drains off quickly.
Also i used get atleast 50% signal at my home..
but now with this, its not catching the signal at all..
Its fine at places where full signal is there..
Click to expand...
Click to collapse
I might be wrong, but the problems you have described having make me believe that you did not use and set the Defy Baseband Switcher app properly. Am I right/wrong?
Phone carriers around the world do not all use the same radio frequencies to receive/transmit phone signal and after any first install of cm7, you have to use that included app, give it root access, select the baseband that correspond to your location/carrier and reboot. Failing to do so causes bad signal eception, high battery drain and hot phones...
I hope that it was your problem because it will make it very simple to solve for you then.
EDIT: I believe that the baseband can now simply be changed under: Device settings/Baseband selection - no more dedicated app...
Installation failure of CM7 latest Joudan-plus
I hope someone can help me please . . .
Having rooted the phone successfully, and having followed all the relevant instructions (including installing first the various utilities - Titanium, 2ndInit, etc), to upgrade my Defy+ Build 4.5.1-134_DFP-231 with the latest CM7, I copied the CM7 zip to my Defy+ then installed it using 2ndInit - success.
Then, on the reboot, the phone just hangs at the M logo.
After doing the normal recovery, and trying to install again, these messages appear:
Verifying update package
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
Can anyone suggest what I should do next to recover the situation?
Installing CM7 on Defy+
Following my previous posting, I installed the nightly Jordan plus, from the night before - the only other one available.
That installed without any error message,
However, upon normal reboot, the phone hung at the M logo.
Any ideas please?
INSPEC said:
Following my previous posting, I installed the nightly Jordan plus, from the night before - the only other one available.
That installed without any error message,
However, upon normal reboot, the phone hung at the M logo.
Any ideas please?
Click to expand...
Click to collapse
Wipe data/cache?
Sent from my ATRIX HD using XDA Free mobile app
Installing CM7 on Defy+
Thanks for the response.
Yes, I did first wipe data and cache.
And have tried repeating the installation (including wiping).
Still hung at M logo.
INSPEC said:
Thanks for the response.
Yes, I did first wipe data and cache.
And have tried repeating the installation (including wiping).
Still hung at M logo.
Click to expand...
Click to collapse
Which recovery are you using? The normal one or the one designed for bigpart?
Sent from my ATRIX HD using XDA Free mobile app
Installing CM7 on Defy+
Thanks again for response.
I am using, from the xda posting,
2ndInit Recovery Installer v2.3 [Updated: 24-April-2012]http://forum.xda-developers.com/showthread.php?p=23465603
Installin CM on Defy+
This is an update on a previous posting of mine . . .
It read:
I hope someone can help me please . . .
Having rooted the phone successfully, and having followed all the relevant instructions (including installing first the various utilities - Titanium, 2ndInit, etc), to upgrade my Defy+ Build 4.5.1-134_DFP-231 with the latest CM7, I copied the CM7 zip to my Defy+ then installed it using 2ndInit - success.
Then, on the reboot, the phone just hangs at the M logo.
After doing the normal recovery, and trying to install again, these messages appear:
Verifying update package
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
I have subsequently performed:
Wipe data/Factory reset, then
Wipe cache.
and then trying to install three different version of CM - they are, CM 7 (both of the available Jordan Plus Nightlies), and then a CM 12 from another posting here in XDA.
All three resulted in the 'signature' problem. But the filename of all three files said they were "signed".
So can someone please explain . . . ?
---------- Post added at 02:25 AM ---------- Previous post was at 01:35 AM ----------
I have now discovered the enable/disable signature check . . .
Having disabled the signature check, and repeated all of the steps in my previous posting, and wiping the Dalvik cache, the phone still hangs at the M logo on reboot.
Any suggestions please?
Installing CM on Defy+
Following on . . .
Could this be a Bootloader problem?
I see references to similar symptoms being fixed by unlocking/relocking the Bootloader.
But my understanding, from the Cyanogen Mod website, is that CM looks after this automatically . . .
Hello.
I am having some problem installing cyanogenmod on my x10i, i have tried many other roms but none will install.
i have tried every tips in xda but i still get the E: error in /sdcard/ update.zip
(status 7).
i'm desperate, i so want to install cyanogen on my mobile or any other stable and quite beautifull rom, because my stock rom is so lame, it keeps rebooting,crashing,freezing, i'm like reformating this thing every month, because it crashes.even if i install nothing on my mobile exept usefull stuffs.
My idea was if i cannot install any custom roms on my x10i, can someone who actually was able to install it help me on how it needs to be done or else make a nandroid backup of his cyanogenmod installed on his mobile and upload it somewhere for me to download it and restore it to my mobile it would be great.
Thanks everybody for your help in advance
I downloaded CM 7.1 stable for my Nook color, and when I go to install I get an assert error with a "status 7".
I've done a lot of flashing of ROMs on my DX, but I'm wondering if there's a step I'm missing. I've pretty much just done the usual routine for flashing a new ROM:
- nandroid backup
- wipe cache,system,data,dalvik cache
- flash ROM zip file
No luck for any ROM I've tried. Anyone know what I need to do to get this to work?
Go over the steps in my sig. If that's no help check out the links in it particularly eyeballer's and mrg666's.
Thanks, I'll try it out. Why don't the official CM7 and MIUI builds work?
Are there other Mirage Kangs I can try out? Any good ICS ones?
Thanks again,
Mike
Also, I'm assuming if I have CWMR already installed I don't need the boot SD, correct?
Same problem. I get
assert failed: getprop("ro.product.device") == "encore" || getprop("ro.build.product") == "encore" || getprop("ro.product.board") == "encore"
E: Error in /sdcard/download/encore_CM72_MiRaGe-06082012.zip
(Status 7)
Installation aborted.
Does this mean I have to do the SDcard boot?
In theory you could put any ROM in place of M-K you wanted but if you are wanting ICS I would install using one of those instruction threads. All I was suggesting was that you go over the basic steps I outline to make sure you weren't missing anything.
And yes, it sounds like something got corrupted and you need to start from scratch. I would at this point. I always look at it as time to flush the old and try out some new.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
So, I tried unrooting and doing a stock recovery, then using a boot-sdcard to flash any number of ROMs. I still get the same error.
At this point it seems something is fundamentally wrong. I tried several options on the flashing, nothing seems to get around this error.
Is there anything else I can do here?
Sent from my DROIDX using Tapatalk 2
mikecico said:
So, I tried unrooting and doing a stock recovery, then using a boot-sdcard to flash any number of ROMs. I still get the same error.
At this point it seems something is fundamentally wrong. I tried several options on the flashing, nothing seems to get around this error.
Is there anything else I can do here?
Sent from my DROIDX using Tapatalk 2
Click to expand...
Click to collapse
When you say you were able to do a stock recovery, what did you mean by that? Were you able to flash a stock ROM to emmc with recovery? Or did you do an 8 failed boot reset?
Also, what version of CWM are you using?
The problem you are having is the install zip cannot verify that it is flashing to the correct device. If it can't find that 'encore' in your properties it will abort. I'm not sure where that property is stored on your emmc, but the zip is not finding it.
Sent from my Nook Color running ICS and Tapatalk
leapinlar said:
When you say you were able to do a stock recovery, what did you mean by that? Were you able to flash a stock ROM to emmc with recovery? Or did you do an 8 failed boot reset?
Also, what version of CWM are you using?
Click to expand...
Click to collapse
I did a factory reset from the nook settings. Is that not sufficient?
I'm using CWM 5.x (don't have it handy to check, I can get the exact version if needed).
leapinlar said:
The problem you are having is the install zip cannot verify that it is flashing to the correct device. If it can't find that 'encore' in your properties it will abort. I'm not sure where that property is stored on your emmc, but the zip is not finding it.
Sent from my Nook Color running ICS and Tapatalk
Click to expand...
Click to collapse
What do you mean by emmc? I'm having to dig a little deeper on this one than I usually do, so I'm not familiar with all the terms.
It sounds like my root-revert wasn't as complete as I thought.
Sent from my DROIDX using Tapatalk 2
mikecico said:
I did a factory reset from the nook settings. Is that not sufficient?
Click to expand...
Click to collapse
No, you'll need to either flash the original version of your firmware or do an 8+1 reset.
mikecico said:
What do you mean by emmc?
Click to expand...
Click to collapse
Embedded Multimedia Card. The flash memory internal to the Nook Color.
Keep listening to leapinlar. Nothings broke beyond repair and he's teaching more than you in this thread.
mikecico said:
I did a factory reset from the nook settings. Is that not sufficient?
I'm using CWM 5.x (don't have it handy to check, I can get the exact version if needed).
What do you mean by emmc? I'm having to dig a little deeper on this one than I usually do, so I'm not familiar with all the terms.
It sounds like my root-revert wasn't as complete as I thought.
Sent from my DROIDX using Tapatalk 2
Click to expand...
Click to collapse
Emmc means embedded multimedia card. It is basically an SD card built into the Nook. It is where all of your internal information is stored. It is partitioned into 8 partitions to hold various kinds of information, like the system files for your ROM, and data that is specific to your installation (application settings, your login info, etc.).
When you did the factory reset it cleared the data info, but not the system info. That is good if you want your stuff off, but it does nothing to the system files (including the root files). So someone else could put their info in and yours will be gone.
Somewhere on one of those 8 partitions is info stored that tells the zip you are an encore. (It's 1, 2 or 3, I just don't know which). The zip is not finding it. That could be because one of those partitions is corrupt. Or the data could just be missing.
If you truly did a factory restore, like flashing a factory zip to emmc, then the info might come back.
OK, thanks! Looks like I've got some homework to do.
Sent from my DROIDX using Tapatalk 2
I also think I had modified some of the system info when I originally rooted this thing. It's not my device, and now the owner (much father in law) wants more than just a rooted device, he wants the full tablet experience. And I like hacking someone else's device.
Long story short, I'm learning quite a bit here, so thanks...
Sent from my DROIDX using Tapatalk 2
mikecico said:
I also think I had modified some of the system info when I originally rooted this thing. It's not my device, and now the owner (much father in law) wants more than just a rooted device, he wants the full tablet experience. And I like hacking someone else's device.
Long story short, I'm learning quite a bit here, so thanks...
Sent from my DROIDX using Tapatalk 2
Click to expand...
Click to collapse
Try looking here (post 148). It is a Stock Rom zip for 1.4.1. Try flashing that with your CWM. Use the first one. It still has an assert statement in it so it may also fail, but it is worth a try.
status 7 error
I'm on and a nook tablet and I'm trying to flash 7.2 stable, I already have CM7 Alpha on the nook which the install had gone smoothly. I tried to use rom manager which gets me to clockworkmod but I get the same error - status 7 when trying to install the cm-7.2.0-encore.zip that I downloaded from cyanogenmod.com.
I've tried downloading it a couple of times, I've tried a bootable sd card but I still get status 7 when trying to install. I've followed the install guide cyanogenmod's wiki to the letter but I cannot get past that error. Anyone have any idea what might be causing it? Right now I'm back to CM7 Alpha.
Heretic09 said:
I'm on and a nook tablet and I'm trying to flash 7.2 stable, I already have CM7 Alpha on the nook which the install had gone smoothly. I tried to use rom manager which gets me to clockworkmod but I get the same error - status 7 when trying to install the cm-7.2.0-encore.zip that I downloaded from cyanogenmod.com.
I've tried downloading it a couple of times, I've tried a bootable sd card but I still get status 7 when trying to install. I've followed the install guide cyanogenmod's wiki to the letter but I cannot get past that error. Anyone have any idea what might be causing it? Right now I'm back to CM7 Alpha.
Click to expand...
Click to collapse
It's because you are on a Nook TABLET. CM 7.2 is for a Nook COLOR. They are completely different devices. If you want to brick your Tablet, keep trying to install this!
Sent from my Nook Color running ICS and Tapatalk
mikecico said:
I also think I had modified some of the system info when I originally rooted this thing. It's not my device, and now the owner (much father in law) wants more than just a rooted device, he wants the full tablet experience. And I like hacking someone else's device.
Long story short, I'm learning quite a bit here, so thanks...
Sent from my DROIDX using Tapatalk 2
Click to expand...
Click to collapse
mikecico, are you sure you are on a nook color? They look almost identical, but the nook color has a black bezel and the nook tablet is silver. Like I said in my post above, they are different devices and that may be why the zip is rejecting the install. It's doing its job.
Sent from my Nook Color running ICS and Tapatalk
I just did a check on the model number, BNTV250. It's a tablet.
Sorry for the noise guys. I think he had told me it's a NC, and I used a NC root method successfully, so I had assumed that was correct.
Mike
So, I'm new to this forum but this isn't the first device I've ever liberated from the carrier's limitations. I've had this Glacier/MyTouch 4G since it was new. It is my primary phone until I upgrade early next year. It's long out of warranty and started giving me a few problems not long ago (which I found was a failing micro SD card).
After recovering it from that I decided to change it from the stock T-Mobile version 2.3.4 and did the firmware downgrade to root it using the gfree and visionary method.
All was successful with no problems thanks to this forum. By the way a big THANK YOU FOR THAT! :good:
I now have the engineering bootloader, and am running cyanogenmod 7.2.0 stable at present although my goal is to find a stable ICS or possibly JB ROM for it if possible.
The bootloader reads as follows:
Glacier PVT ENG S-OFF
HBOOT-0.85.2007 (PD1510000)
MICROP-0429
RADIO-26.03.02.26_M
eMMC-boot
Oct 11 2010,12:44:14
My question is, what else do I need to consider doing prior to looking at other ROMs and eventually settling for something permanently?
I'm not unhappy with cyanogenMod 7.2.0 (although I may try the newer nightly) but I would like to get to at least ICS.
I read something about updating the RADIO but am not sure if that's necessary or not. Perhaps someone could guide me based on the above info. If there is any other updates I've missed along the way on this project, pointing that out is also greatly appreciated.
I noticed immediately that the Google Play Store, etc. wasn't there when I installed cyanogenMod and got that update in, so all that is working quite well at this point.
Again, thank you forum for your excellent instructions that worked flawlessly for me on the first try and got me to this point. I have gone through and hit the thanks button on all the threads I used.
A couple things, they aren't really necessary, more of precautions.
1) Do a nandroid of your current rom
2) Before you flash the new rom, do a FULL wipe, this means data, system, cache, dalvik yada yada
3) get 4EXT recovery, it really is a time saver
Get 4ext recovery and have a pretty good sized microsd. The radio is more of an experiment on your own time thing, if you're curious to see if there are any improvements then flash away, but if you don't care, then you'll be fine on stock radio.
Oh, and make sure you have everything you need prior to flashing a ROM such as gapps and additional files like newer kernels and fixes
Sent from my LG E960
Thanks for the responses. I've been doing backup/restore using ClockworkMod Recovery and I noticed it came already installed on CyanogenMod.
I've gotten familiar with the interface so Is that one okay vs. the ones mentioned or should I switch?
As far as the Radio, I read up on it and downloaded the various ones to try so I'm fairly confident I can accomplish that if need be.
From what I read, I understand I should travel around to my usual locations and see what my signal is like, and also watch my battery life to see which works best if I decide to experiment with Radio options. Having used T-Mobile for so many years I already know all the areas I travel to and have good signal or none at all (way too many with little or none at all).
I know prior to rooting I was getting solid 4G in my home. I ran speedtest this morning and am seeing between 4622-5722kbps down and 1605kbps up. I think that's not too bad although I notice the icon fluctuates between 3G and HSPA frequently, where with the stock phone it was consistently 4G (as far as the icon displayed anyway).
I'm using an 8GB microSD card and occasionally I'm going to connect it to a computer and copy those backups off to other storage, just in case.
Icon means nothing (or actually, the stock lies and 3G/H are telling the real connection state). The connection is the same.
Jack_R1 said:
Icon means nothing (or actually, the stock lies and 3G/H are telling the real connection state). The connection is the same.
Click to expand...
Click to collapse
That's pretty much what I thought too, especially based on my speedtest results. I know from years of experience with T-Mobile that they stretch the truth on not only data speeds but also network coverage maps which like in the Pirates of the Caribbean movies are more "guidelines" than anything else.
However, since I do see that constant fluctuation between the 3G/H icons so frequently, experimenting with the different radios might be worthwhile.
Thanks for your response.
1600RoadStar said:
Thanks for the responses. I've been doing backup/restore using ClockworkMod Recovery and I noticed it came already installed on CyanogenMod.
I've gotten familiar with the interface so Is that one okay vs. the ones mentioned or should I switch?
As far as the Radio, I read up on it and downloaded the various ones to try so I'm fairly confident I can accomplish that if need be.
From what I read, I understand I should travel around to my usual locations and see what my signal is like, and also watch my battery life to see which works best if I decide to experiment with Radio options. Having used T-Mobile for so many years I already know all the areas I travel to and have good signal or none at all (way too many with little or none at all).
I know prior to rooting I was getting solid 4G in my home. I ran speedtest this morning and am seeing between 4622-5722kbps down and 1605kbps up. I think that's not too bad although I notice the icon fluctuates between 3G and HSPA frequently, where with the stock phone it was consistently 4G (as far as the icon displayed anyway).
I'm using an 8GB microSD card and occasionally I'm going to connect it to a computer and copy those backups off to other storage, just in case.
Click to expand...
Click to collapse
About recovery, i would say that you are better off switching, 4EXT gets the job done faster and its known to produce less problems when flashing the roms. Its completely optional but its highly recommended plus it only takes a couple minutes of your time.
Point taken, thank you.
Sent from my A500 using xda app-developers app
THEindian said:
About recovery, i would say that you are better off switching, 4EXT gets the job done faster and its known to produce less problems when flashing the roms. Its completely optional but its highly recommended plus it only takes a couple minutes of your time.
Click to expand...
Click to collapse
I did install and am using nandroid and I'd like to ask a question regarding using 4EXT instead of CWM recovery.
I'm now using the most recent cyanogenmod nightly and I see that like the previous version it has CWM recovery pre-installed. Looking at it in the apps list it allows uninstalling updates only, and not complete removal. Is installing 4EXT going to interfere with that or am I safe to do it because it will then be the default custom recovery? Or is there something else I'll need to accomplish to remove CWM recovery first?
Apologies for the beginner questions I'm sure these are but I haven't been able to find a thread clearly explaining this aspect.
1600RoadStar said:
I did install and am using nandroid and I'd like to ask a question regarding using 4EXT instead of CWM recovery.
I'm now using the most recent cyanogenmod nightly and I see that like the previous version it has CWM recovery pre-installed. Looking at it in the apps list it allows uninstalling updates only, and not complete removal. Is installing 4EXT going to interfere with that or am I safe to do it because it will then be the default custom recovery? Or is there something else I'll need to accomplish to remove CWM recovery first?
Apologies for the beginner questions I'm sure these are but I haven't been able to find a thread clearly explaining this aspect.
Click to expand...
Click to collapse
I'm guessing you mean ROM Manager?
CWM is the official recovery of Cyanogenmod. However, 4EXT Recovery works very well. I've had zero issues using it with ROM Manager. Never, I repeat, never install a ROM using the menu in ROM Manager. ALWAYS reboot to recovery and do it manually.
Sent from my Nexus 4 using xda app-developers app
1600RoadStar said:
However, since I do see that constant fluctuation between the 3G/H icons so frequently, experimenting with the different radios might be worthwhile.
Thanks for your response.
Click to expand...
Click to collapse
When there is a data transfer of any kind, HSPA connection is negotiated and you see H.
When the phone is idle and doesn't transmit anything, you see 3G.
Perfectly normal.
You're welcome.
1600RoadStar said:
I did install and am using nandroid and I'd like to ask a question regarding using 4EXT instead of CWM recovery.
I'm now using the most recent cyanogenmod nightly and I see that like the previous version it has CWM recovery pre-installed. Looking at it in the apps list it allows uninstalling updates only, and not complete removal. Is installing 4EXT going to interfere with that or am I safe to do it because it will then be the default custom recovery? Or is there something else I'll need to accomplish to remove CWM recovery first?
Apologies for the beginner questions I'm sure these are but I haven't been able to find a thread clearly explaining this aspect.
Click to expand...
Click to collapse
All you've got to do is install 4ext. Madmaxx made it easy to go from cwm to 4ext, all of my backups stayed intact after I made the switch a while back.
Sent from my SGH-T999 using xda app-developers app
Jack_R1 said:
When there is a data transfer of any kind, HSPA connection is negotiated and you see H.
When the phone is idle and doesn't transmit anything, you see 3G.
Perfectly normal.
You're welcome.
Click to expand...
Click to collapse
Makes sense. My plan is to leave the current radio alone. :good:
Synthetic.Nightmare said:
All you've got to do is install 4ext. Madmaxx made it easy to go from cwm to 4ext, all of my backups stayed intact after I made the switch a while back.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Awesome, thank you. I was reading about your ROM earlier today, the positive remarks of it convinced me it'll be the one I try next as I'm looking for an ICS daily driver although I'm entirely happy with my current cyanogenmod installation.
estallings15 said:
I'm guessing you mean ROM Manager?
CWM is the official recovery of Cyanogenmod. However, 4EXT Recovery works very well. I've had zero issues using it with ROM Manager. Never, I repeat, never install a ROM using the menu in ROM Manager. ALWAYS reboot to recovery and do it manually.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
That is what I meant. I'm still getting some of the names and terminology confused. I have used ROM manager to install the ROMs I've tried so far but will discontinue that.
Well, it's been a few weeks since I started on this adventure and it hasn't been a very smooth ride. I went from stock GB to CyanogenMod 7.2.0 stable to cm-7-20121007 nightly to SyNthetic_aospX to cm10.1 unofficial and back to SyNthetic_aospX which I finally settled on as my daily driver.
My goal was to get the phone to a very stable and reliable ICS or JB ROM that I could use until I upgrade in another month. During the installing of one ROM I got the dreaded
E: cant mount /cache/recovery/log
E: cant open /cache/recovery/log
E: cant mount /cache/last_log
E: cant open /cache/last_log
errors that I posted in this thread: http://forum.xda-developers.com/showthread.php?t=2063057&page=24.
After that I was able to recover it by reinstalling Froyo using PD15IMG.zip and rerooting using visionary and recovery manager to reinstall SyNthetic_aospX.
That worked well for awhile until one morning I woke up and went to take my phone off the charger and found it to be shut off and unresponsive.
I pulled the battery and got it into recovery and when rebooting got the dreaded
E: cant mount /cache/recovery/log
E: cant open /cache/recovery/log
E: cant mount /cache/last_log
E: cant open /cache/last_log
again.
I had nandroid backups but they all failed when attempting them with the same error messages as above.
Finally, after many attempts I was able to get the phone back to stock GB using the PD15IMG.zip.
The phone is back to stock except for apparently still having S=OFF
The bootloader now reads as follows:
GLACIER PVT SHIP S-OFF
HBOOT-0.89.0006
MICROP-0429
RADIO-26.13.04.19_M
eMMC-boot
Jul 15 2011, 16:45:17
Not sure what to do now, if anything. I really can't afford the time to tinker with the phone any more not knowing if I'll have additional problems with a different ROM. It is my primary phone and although I'd like root back to get rid of the unnecessary apps I don't want to risk errors or bricking.
And so the saga continues...
After awhile running the stock gingerbread once again the phone began locking up and shutting down the other day. When this began happening the first time I thought it was a bad SD card but that seems to have eliminated itself as the problem now. This time I'm thinking the battery may be the culprit.
Right before it happened I saw a message appear that said the SD card had been mounted read only. The phone was sitting untouched when it happened.
I was once again able to reinstall stock Froyo, gain root with visionary and get 4EXT recovery installed so now I'm running the debloated and rooted stock GB on it (I never lost permanent S-OFF so it was easy).
Still saw:
E: cant mount /cache/recovery/log
E: cant open /cache/recovery/log
E: cant mount /cache/last_log
E: cant open /cache/last_log
but 4EXT recovery seemed to handle it better than Recovery Manager did so eventually the custom ROM worked.
I read it thread and saw u were using cm7.2 before. For me with that version of cm7 it was not stable, kept getting signal drops. I think its due to the fact that its based on gb 2.3.7 as well is cm7.1.
If u want a rock solid cm7, then flash cm7.0.3 no problems there just doesn't have as much options as the later. I also use it with Holo launcher which is an ics/jb aosp themed launcher for gb
Cm7.0.3 is gb 2.3.3
Sent from my HTC Mytouch 4g using xda app-developers app
If you have time, you might want to get familiar with adb to root your phone using computer commands. I've read people have had better success permanently rooting their device that way.
elmagnificado said:
If you have time, you might want to get familiar with adb to root your phone using computer commands. I've read people have had better success permanently rooting their device that way.
Click to expand...
Click to collapse
That's what I did, using the gfree and visionary method which requires ADB.
(http://forum.xda-developers.com/showthread.php?t=858996)
I read how there are no stupid questions, well I'm about to test that I think. I'm a complete newblet to this sort of thing but I have an N7 2012 running like a dog on 5.1.1. So like many, many other posters here I want to make her fast again but would rather not rollback to 4.4.
So I found this: http://forum.xda-developers.com/nexus-7/development/rom-6-0-android-marshmallow-pure-aosp-t3226012
I wonder firstly, I didn't see a step on backing the current environment up in case of brickage. Is that something the author thinks anyone wanting to flash their unit should know how to do already?
And if so, are there any other steps that would be beneficial to do prior to the actual flashing that any experienced ROM alterer would do that I should as well?
Thanks guys!
I'm about to go down the same route.
I have TWRP recovery installed and am using it to backup the more or less stock setup. (except for TWRP recovery, custom kernel and SuperSU.)
I'm seeing that my backup will take 2.6 gigs though, which almost runs me out of SDCard space.
But since 5.1 is pretty much unusable I probably won't keep the backup long.
As long as your bootloader is unlocked, Nexus devices tend to be hard to brick (barring any N7 2012 specific issues.)
Consider upgrading to N7 2013 running stock Android 6.0. I have 2 for app testing and they are pretty darn nice, especially for the price. Can buy for less than $150 new now, and good bargains for used.
Thanks Mike, Question what guide did you follow to get yours rooted and the recovery stuff updated?
mikereidis said:
I'm about to go down the same route.
I have TWRP recovery installed and am using it to backup the more or less stock setup. (except for TWRP recovery, custom kernel and SuperSU.)
I'm seeing that my backup will take 2.6 gigs though, which almost runs me out of SDCard space.
But since 5.1 is pretty much unusable I probably won't keep the backup long.
As long as your bootloader is unlocked, Nexus devices tend to be hard to brick (barring any N7 2012 specific issues.)
Consider upgrading to N7 2013 running stock Android 6.0. I have 2 for app testing and they are pretty darn nice, especially for the price. Can buy for less than $150 new now, and good bargains for used.
Click to expand...
Click to collapse
Wait, I figured it out. So I've got it rooted, then pushed Cyanogenmod recovery and rebooted and got into recovery mode. First off I tried loading Cyanogenmod 12.1 which worked well. It was snappy however I could not figure how to get gapps reinstalled. Thinking maybe another rom might already have google apps I then pushed 6.0.1_r10_Grouper-MM. Booted fine but still not gapps..
So I find a website that says to push the zip to /sdcard/ then apply update from sdcard in recovery mode. However now, I'm getting errors complaining about F2FS.
E:can't open /cache/recovery/last_log
E:unknown fs_type "f2fs" for /cache
Couldn't mount /sdcard
Installation aborted
Googles not been much help yet.
7298 said:
Thanks Mike, Question what guide did you follow to get yours rooted and the recovery stuff updated?
Click to expand...
Click to collapse
7298 said:
Wait, I figured it out. So I've got it rooted, then pushed Cyanogenmod recovery and rebooted and got into recovery mode. First off I tried loading Cyanogenmod 12.1 which worked well. It was snappy however I could not figure how to get gapps reinstalled. Thinking maybe another rom might already have google apps I then pushed 6.0.1_r10_Grouper-MM. Booted fine but still not gapps..
So I find a website that says to push the zip to /sdcard/ then apply update from sdcard in recovery mode. However now, I'm getting errors complaining about F2FS.
E:can't open /cache/recovery/last_log
E:unknown fs_type "f2fs" for /cache
Couldn't mount /sdcard
Installation aborted
Googles not been much help yet.
Click to expand...
Click to collapse
I've been doing this stuff for 5 years, so I usually don't need guides, just a few hints sometimes. CM recovery these days is something I try to avoid as it mostly works only with CM. I use TWRP and flash it with adb commands like:
adb reboot bootloader
fastboot flash recovery twrp-2.8.7.0-grouper.img
I ended up flashing this Marshmallow ROM because it seems to be the most popular at this time: http://forum.xda-developers.com/nexus-7/development/android-6-aosp-grouper-t3268172
And I'm happy with it so far.
Strange thing though is that I had to flash it 3 times to get it to flash without any error.
Then I had to flash the Benzo Gapps 2 times to get that on with no error. Result is working OK so far.
Damn Mike, I shoulda waited another hour before settling on mine. I tried that 6.0.1 i linked earlier in the thread about 4 times. Three times it applied successfully with 1 seeming to lockup during the new user setup. But I tried at least 4 different gapps that all didnt work. The usual results was Google Play Services have stopped. So because the day was nearing an end and I needed it last night to read I dropped back to the Cyanogenmod 12.1, changed the theme and tossed in Open Gapps Nano http://opengapps.org/?api=5.1&variant=nano
Wound up having to load play books, play services, gmail, and chrome individually.
But it's snappier than ever (so far). I'll end up re-trying 6 very soon but this time I'm trying the one you found.
mikereidis said:
I've been doing this stuff for 5 years, so I usually don't need guides, just a few hints sometimes. CM recovery these days is something I try to avoid as it mostly works only with CM. I use TWRP and flash it with adb commands like:
adb reboot bootloader
fastboot flash recovery twrp-2.8.7.0-grouper.img
I ended up flashing this Marshmallow ROM because it seems to be the most popular at this time: http://forum.xda-developers.com/nexus-7/development/android-6-aosp-grouper-t3268172
And I'm happy with it so far.
Strange thing though is that I had to flash it 3 times to get it to flash without any error.
Then I had to flash the Benzo Gapps 2 times to get that on with no error. Result is working OK so far.
Click to expand...
Click to collapse
I tried that MM ROM it worked fine for first week, then it started to act the same as it was on 5.1.1. I used Nexus Root Toolkit to flash my nexus to stock and then flash the rom with just few clicks