Develop Bugs

MIUI and CM7 Running on Motorola Bravo! [Signal fix in post 2]

MIUI and CyanogenMod7 on the Motorola Bravo!!!
Anything you do to YOUR phone is YOUR fault, not mine.
MIUI and CM7 are already pre-rooted and pre-overclocked (to 1ghz) though you can still use BandroidX's overclock app​
Directions to install MIUI:​
You need to be on the stock rom before you install anything. Use this SBF, then root it with superoneclick
A nandroid installation is the only way for you to install
This installation might lead you to a bootloop, I'm working on a fix (you can still flash an sbf though)​
1. Sbf to 2.2.1
2. Root and enable non-market apps with superoneclick
3. Download and install bandroidx's custom recovery app
4. Bootstrap recovery
5. Boot into the recovery and wipe data/cache and dalvik cache (advanced>wipe dalvik cache)
6. Select restore backup
7. Select MIUI_1.7.22_nandroid
8. Confirm
9. Reboot and enjoy!!
FYI, no need to do the signal fix because it is already implemented​
Note: When/if you boot into bootmenu after installing MIUI and select recovery> custom recovery, it will bring you to 2 choices: latest recovery and stable recovery. These recoveries are Motorola Defy recoveries but they still work on the Bravo. You can make backups and you can restore and install .zips. Some things might be broken since it is a Defy recovery. There is no way to boot into BandroidX’s recovery.​
BUT, BEFORE YOU DO ANYTHING, these are the problems (which are very minimal considering this wasn't even developed for the Bravo):​
1. No working camera/camcorder
2. Signal is very poor when you manage to get one. It doesn't have a signal for 99% of the time, but when it gets a signal, it's only 1 bar.<--- FIXED go to post #2
3. That's all I could gather, if there is anything else, don't hesitate in commenting!
Links/downloads:​
nandroid download version number 1.7.22 (7/22/11)
2ndInit (below)
Thanks to:​
All the credit for the actual ROMs goes to the Defy developers (don't know specifics) who made the 2ndInit, MIUI and CM7 Roms.
abhi897 for answering some of my questions
Note: I will NOT be releasing any actual roms (yet). All I will be releasing are fixes for the Defy ROM running on the Bravo (camera fix, signal fix, and any other problems)​
Check out the proof:​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CyanogenMod7 on the Motorola Bravo​
Again, all credit goes to the Defy developers (except for the fixes posted here)
To install, you have to restore a CM7 nandroid backup. Otherwise you will have problems.​
This is assuming you are on stock Bravo 2.2. If not, use THIS sbf, then root it with superoneclick
The nandroid installation method does NOT have GAPPs installed already, but the signal fix was implemented​
1. Extract THIS nandroid to /sdcard/clockworkmod/backup/
2. Make sure you have BandroidX's recovery bootstrapper installed and working
3. Make a Titanium backup (you need this to restore your apps)
4. Reboot into BandroidX's Recovery
5. Make a backup (for yourself)
6. Wipe data/factory reset/dalvik cache
7. Restore the CM7 nandroid backup you downloaded
8. Wipe cache in stock recovery
9. Reboot and enjoy!
Attention: reboot before you install GAPPs​
Note: When/if you boot into bootmenu after installing CM7 and select recovery> custom recovery, it will bring you to 2 choices: latest recovery and stable recovery. These recoveries are Motorola Defy recoveries but they still work on the Bravo. You can make backups and you can restore and install .zips. Some things might be broken since it is a Defy recovery. There is no way to boot into BandroidX’s recovery.​
(to bypass activation screen, just touch 4 corners of the popup)​
Problems:​1. No working camera (even 3rd party apps)
2. Capacitive touch buttons are mapped wrong (aka the buttons are "shifted to the left") This is how it acts:<-- Fixed in nandroid update
3. Signal is also bad <-- Fixed in post #2
Thanks to:​​
The same people above​
Proof:​

Fixes for MIUI and CM7 Running on Bravo
Signal Issue Fix:​Works on MIUI and CM7​1. Download the .zip file below and put it on your phone
2. Extract
3. In root explorer, delete all the files in /etc/motorola/bp_nvm_default/
4. Copy the extracted files into /etc/motorola/bp_nvm_default/
5. Set permissions on ALL the files to "rw-r--r--" or you will bootloop! In the end, the permissions should look like this:
6. Reboot and enjoy a signal
I will try to create an flashable .zip to remove the hassle of changing all the permissions​

That's awesome, and good work on doing the testing so far, but I'm going to wait until there is something more solid so I can actually use those features on my phone as they are.

If you want to return back to your regular rom (BravoX, stock bravo 2.2), I suggest wipe data/cache, sbf, then restore your backup

Props for giving this a shot jorgonv have u tried modifying your apn settings to see if that would improve the reception? Gonna give this a go when I get home from work tonight thanks

MCFarmfresh said:
Props for giving this a shot jorgonv have u tried modifying your apn settings to see if that would improve the reception? Gonna give this a go when I get home from work tonight thanks
Click to expand...
Click to collapse
I copied the exact apn settings from what I had before and it didn't help. it probably has to do with the differing frequencies in the radios between the defy and bravo

Hopefully bandroidx will come to the rescue and get a working camera and good signal on this. The only thing I can think for the signal problems is that we need a compatible radio (the Defy CM7 is for tmobile). This is bad though because I haven't seen any SBF flashable radios for the Bravo yet...

BravoMotorola said:
Hopefully bandroidx will come to the rescue and get a working camera and good signal on this. The only thing I can think for the signal problems is that we need a compatible radio (the Defy CM7 is for tmobile). This is bad though because I haven't seen any SBF flashable radios for the Bravo yet...
Click to expand...
Click to collapse
Yeah, hopefully. But I am trying to fix the signal problem to make the phone actually usable. Wish me luck!
UPDATE: Fixed signal problem!!!! suggested by abhi897
Works on MIUI (tested), not tested on CM. I'm 99% sure it will work with CM though.
Put the zipped files in /etc/motorola/bp_nvm_default/
WITH PERMISSIONS on all of them set to: rw-r--r--
Set permissions or you WILL bootloop!
Will try to create update.zip tomorrow

jorgonv said:
Yeah, hopefully. But I am trying to fix the signal problem to make the phone actually usable. Wish me luck!
UPDATE: Fixed signal problem!!!! suggested by abhi897
Works on MIUI (tested), not tested on CM. I'm 99% sure it will work with CM though.
Put the zipped files in /etc/motorola/bp_nvm_default/
WITH PERMISSIONS on all of them set to: rw-r--r--
Set permissions or you WILL bootloop!
Will try to create update.zip tomorrow
Click to expand...
Click to collapse
Dude!!! you Jorg are the man! I have been going non stop since I got off and haven't had any time to play with this but out is definitely getting done as soon as I find the time. I will try out with CM to confirm it is working. Will report back

MCFarmfresh said:
Dude!!! you Jorg are the man! I have been going non stop since I got off and haven't had any time to play with this but out is definitely getting done as soon as I find the time. I will try out with CM to confirm it is working. Will report back
Click to expand...
Click to collapse
Thank you!

Could you make us a backup in titanium? Would that even work?

ripin150 said:
Could make us a backup in titanium? Would that even work?
Click to expand...
Click to collapse
You can make your backup with titanium, which I recommend also because that is way you will get your apps back. I haven't tried restoring my BravoX rom data, but I kind of have a feeling that it'll bootloop.

jorgonv said:
You can make your backup with titanium, but can you flash the rom with the recovery you have?
Click to expand...
Click to collapse
For some reason, I cant install cm7 or miui with the instructions in this thread. But would it install from a backup, without having to do the sndinit and all that?

ripin150 said:
For some reason, I cant install cm7 or miui with the instructions in this thread. But would it install from a backup, without having to do the sndinit and all that?
Click to expand...
Click to collapse
I'll redo the instructions in the morning because people have been having some problems. You can probably install from a backup, I'll try to post one tomorrow.

Very Good with my post...^^!

Did you try score Benchmark in MIUI or CM7 on Bravo...I want to see that score...^^ ...1GHz CPU Process is working...!

AlexzOzO said:
Did you try score Benchmark in MIUI or CM7 on Bravo...I want to see that score...^^ ...1GHz CPU Process is working...!
Click to expand...
Click to collapse
MIUI Quadrant Benchmark Scores:
The rom is pre-overclocked to 1ghz
1ghz, 58 VSEL: very good graphics! fast read and write speed
1.2044
2.2226
3.2227
4.2360
1.2ghz, 60 VSEL: Faster!
(1.2ghz, 58 VSEL rebooted my phone)
1.2238
2.2577
3.2734
4.2741

jorgonv said:
Yeah, hopefully. But I am trying to fix the signal problem to make the phone actually usable. Wish me luck!
UPDATE: Fixed signal problem!!!! suggested by abhi897
Works on MIUI (tested), not tested on CM. I'm 99% sure it will work with CM though.
Put the zipped files in /etc/motorola/bp_nvm_default/
WITH PERMISSIONS on all of them set to: rw-r--r--
Set permissions or you WILL bootloop!
Will try to create update.zip tomorrow
Click to expand...
Click to collapse
Heck yea!! Good going! I can live without the camera for CM7...but hopefully we or I when I get home can find a solution for that too! Maybe if we copied some parts of the build prop in the camera area from the 2.2 stock bravo files to the CM7 bravo and recompiled the camera apk from the 2.2 stock bravo to 2.3 and moved that over as well we could get it working. I just wonder all it is in the system files that has to do with the camera...

BravoMotorola said:
Heck yea!! Good going! I can live without the camera for CM7...but hopefully we or I when I get home can find a solution for that too! Maybe if we copied some parts of the build prop in the camera area from the 2.2 stock bravo files to the CM7 bravo and recompiled the camera apk from the 2.2 stock bravo to 2.3 and moved that over as well we could get it working. I just wonder all it is in the system files that has to do with the camera...
Click to expand...
Click to collapse
The build.prop modification is a good idea, I'll look into that today.
The blur camera has been ported, ill look into that too
But, I do think all we need to do is replace some simple lib.so's or something. I already tried to replace some libs, but it just bootlooped for me

Very well...It's great for my article to have Recovery Bravo free that you have made ​​a very exciting topic Bravo ... Bravo Try to develop for ... The ones you've done for a long time now I have to Bravo make more ...^^!

Defy 2.2 Re-Release Upgrade to CM7 - Multiple Queries - Plz Help

Hi Friends,
Plz bear with by silly questions and help me (by answering the following queries or redirecting to the threads where i can find appropriate answers. I know these have been discussed earlier in many threads but as a newbie to android, i am a bit confused and would like some specific help here)
I just bought a new Defy in India. It has a green lens with SOC module. It is running on 2.2 Re-Release version exactly as mentioned here
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I want to upgrade to CM7 keeping downgrade ability to stock 2.2 in case i need to go to warranty. I tried to grab some info on this from existing posts and understood a bit but still a bit confused. (just that I dont want to get things wrong)
- Which version/build of CM7 is the latest and stable? Plz provide the link.
- What exactly I need to do to be able to downgrade to official 2.2 stock in order to get warranty in future. Plz explain this stepwise.
I went through the Defy Beginner's Guide. It helped but got confused regarding the following points:
- SBFs, Fixed SBFs, NanDroid Backup, CG versions (All related to make sure I can downgrade to stock 2.2 in future for warranty). Which option is suitable for me? Full SBF / Fixed SBF with Nandroid backup. What exactly I need to check/verify regarding CG versions?
Plz help me.

You will be able to go back to your previous firmware as long as you don't flash the full leaked gingerbread sbf. If you follow the CM7 faq/guide you won't have a problem. I am on 2208 nightly and have no issues. You can follow the guide and replace the rc1 by the nightly as it is a "boot" nightly. If you would like to try later nightlys, you have to flash latest boot first and next wipe cache and dalvic cache and then instal the nightly. Along as you don't flash another boot, the boot image stays the same. You only need to flash it ones, not with every nightly.
Sent from my MB525

Defy 2.2 Re-Release Upgrade to CM7
1.Download superoneclick 1.9.5
2.In your mobile. Settings->Applications->Development(check USB debugging on)
3.Connect your phone to PC. Open superoneclick ->Click ROOT. Thats it your phone is rooted.
4.Restart your mobile.
5.Download 2nd init from android market. install the 2nd init recovery. It will ask the superuser permission Accept it.
6.Uncheck the USB debugging from Settings->Applications->Development and restart the phone now.
7.It will go in to bootmenu select normal boot at now.
8.After mobile booted copy the cm7 rc1 or nightly(whatever you downloaded) zip file to root of your SD card.
9.Restart the phone it will go in to boot menu or you can press vol - button when you see the blue led light.
10.Now go to recovery -> Custom recovery -> Wipe data/factory and Wipe cache -> Install zip file from sd card(select the zip file you copied to sd card) thats it. (Some times after install zip file from sd card goback and WIPE cache only to avoid some instability in fresh ROM)
11.After installation completed reboot the phone now it will go to the boot menu or press vol - button when blue led flash at booting. Make 2nd init as a default boot. thats it. You are in 2.3.5 gingerbread. I recommend CM7 nightly boot-179-4. it is more stable and having less bugs. defycm7.tanguy.tk/cm7-110822-1650-BOOT179-4-Jordan.zip[/url]
To downgrade to Stock rom it is very simple.
1.Download RSD lite and Motorola usb drivers to flash SBF file.
2.Download Stock froyo SBF for your region(Search xda forum)
3.Check USB debugging on your phone and connect to the pc and wait until all motorola drivers install.
4.Open RSD lite(right click and open as a administrator). It will show connected. Now select the sbf file you located on the system and click start and wait till it completes 100% process. thats it. it will flash your phone to stock froyo and it will automatically restart and boot.
Note: Some times when rebooting after RSD lite flash your phone stuck in bootloop(M logo or it continously loading in Android menu). It is better to go to stock recovery(Hold the vol - button and then power button and then release it. you will get android logo with exclamatory symbol. Press vol - and vol + button at the same time to get in to stock recovery). Select wipe data/factory and wipe cache.
*But i would recommend this method before you flashing the full stock sbf.

labsin said:
You will be able to go back to your previous firmware as long as you don't flash the full leaked gingerbread sbf. If you follow the CM7 faq/guide you won't have a problem. I am on 2208 nightly and have no issues. You can follow the guide and replace the rc1 by the nightly as it is a "boot" nightly. If you would like to try later nightlys, you have to flash latest boot first and next wipe cache and dalvic cache and then instal the nightly. Along as you don't flash another boot, the boot image stays the same. You only need to flash it ones, not with every nightly.
Sent from my MB525
Click to expand...
Click to collapse
watz the diff b/w boot179 and nightly?
Also,how to install a boot??

The boot also change the boot.img and the modules. Boot contains things like wifi and kernel, these are taken from official sbfs. At first the were working with base roms for CM7 but with RC1 they included these so everyone will have the same experience. Later boot were for testing if some problems were still present. Latest seems to be better on wifi.
Edit: instal them just the same. If its the first time on cm wipe all in custom recovery, this will erase all apps, for update wipe cache/dalvic, and instal.
Sent from my MB525

but what if I directly flash nightly without rc1, then my boot of the current stock won't be replaced with cm7 properly working,huh??
OR
even the nightlies replace my current boot but the diff is just that boot179 is the latest one??

Only nightlys with boot in there name and the rc1 replace them. yes, if you install a normal nightly, your current boot will be kept. If you want to try the latest nightly, it is best to install the boot. If you com from the 17x(or way you just said) you don't have to do this.
Vinodh3 guide is very good. I would also suggest that nightly.
Sent from my MB525

My first and so far only CM7 installation on my defy was 110822 boot179 nightly.
I started off on vodafone uk 2.2.2 (179-4) firmware. I did not flash another sbf.
I rooted using super1click 2.1. This was the most difficult part, getting hold of motorola adb drivers.
Once rooted, I installed sndinitdefy 1.4_2. Copied the cm7 zip and gapps zips to my SD card. Rebooted a couple of times to make sure all was well.
Then in boot loader I wiped data, cache, dalvik cache, etc. Then applied the cm7 zip. Let it finish installation and boot, then once it was up and running in CM7, I rebooted and installed the gapp zip.
All going great here on that basis.

Guys, I read this topic as well as other ones but I remain confused about ROM versions I can install.
The thing is I was running stock 2.2.2 in my Defy and I got a CM7 RC1 on it. And now my system info says I'm running 2.3.4. Am I still able to go back to stock 2.2.2 as I haven't flashed any other SBF than stock one?
The other thing is: if I'd like to get a newer, nightly version of CM7 to get some minor bugs fixed, what version exactly can I get? Can I download the latest nightly build from 29th August, "cm7-110828-1034-NIGHTLY-Jordan.zip"? Will it work? Do I have to do a WIPE or I can install it with my current CM7 "as is"?
The amount of information I've read is so tremendous that I'm lost in everything. Please help

2908 is a bad one. Many bugs. Try 2208 or before 2908. No data wipe is needed. But do wipe cache and dalvic in advanced. Yes you can downgrade with ease. Only thing you should avoid is to flash the full ginger sbf from motorola. They are work around if you did won't to try that. If so, check greenginger(or something)
Sent from my MB525

i need to send my defy for warranty so i needed to downgrade from cm7 to stock froyo!
therefore, i wanna know will flashing full sbf remove everything such as root, 2ndinit etc??
and i just have to disable usb debugging before flashing full sbf or do i have to do something more??do i have to wipe cache nd data in stock recovery before flashing full sbf or later??
plzz tell me all the steps!!

NOOB: Rooting and Kernal for Galaxy Nexus

Anyone willing to give some time to write up on what I should do?
I heard that the best combination is bigxie's rom along with franco's kernel.
How do I go about doing this? Do I need to backup my kernel, firmware etc?
I really appreciate the help and am willing to reward anyone who can take me through this step-by-step.

Read the stickied post in GSM (or) CDMA Development forum that tells you how to get started.
CDMA: Verizon
GSM: Not verizon? SIM card? You have GSM.
Best combination is whatever ROM that is 4.0.3 with the features that YOU want.
AOKP or Bigxie + Franco Kernel

zephiK said:
Read the stickied post in GSM (or) CDMA Development forum that tells you how to get started.
CDMA: Verizon
GSM: Not verizon? SIM card? You have GSM.
Best combination is whatever ROM that is 4.0.3 with the features that YOU want.
AOKP or Bigxie + Franco Kernel
Click to expand...
Click to collapse
I'm GSM.
What would you recommend? AOKP or Bigxie?

BrandonPrice31 said:
I'm GSM.
What would you recommend? AOKP or Bigxie?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1392310
I personally use the old school method with fastboot oem unlock rather than that to root. But I think that one might be easier for you to use.
I personally use AOKP + Franco's Kernel.

zephiK said:
http://forum.xda-developers.com/showthread.php?t=1392310
I personally use the old school method with fastboot oem unlock rather than that to root. But I think that one might be easier for you to use.
I personally use AOKP + Franco's Kernel.
Click to expand...
Click to collapse
Will that tool backup my current state?

BrandonPrice31 said:
Will that tool backup my current state?
Click to expand...
Click to collapse
Backup as in what? Your apps, data? Probably not.
Unlocking the bootloader will do a complete wipe of your phone. So backup whatever you need that is important or you'll lose it.

zephiK said:
Backup as in what? Your apps, data? Probably not.
Unlocking the bootloader will do a complete wipe of your phone. So backup whatever you need that is important or you'll lose it.
Click to expand...
Click to collapse
Precisely, my apps, data.... I presume that's backed up by my Google account and is synced automatically correct?
What is a kernel?

BrandonPrice31 said:
Precisely, my apps, data.... I presume that's backed up by my Google account and is synced automatically correct?
What is a kernel?
Click to expand...
Click to collapse
Your apps, data are not backed up. At most it'll go to the Android Market and redownload all of them. But after you've rooted you can successfully back up all of this stuff using a handy tool named Titanium Backup. I recommend getting the pro version or you can use MyBackUp. Which does the same thing but I've never tried it.
Also, I believe "fastboot oem unlock" (unlocking bootloader) wipes your sdcard as well, so backup any important pictures or whatever you need before doing this.
Kernel: http://en.wikipedia.org/wiki/Android_(operating_system)#Design

zephiK said:
Your apps, data are not backed up. At most it'll go to the Android Market and redownload all of them. But after you've rooted you can successfully back up all of this stuff using a handy tool named Titanium Backup. I recommend getting the pro version or you can use MyBackUp. Which does the same thing but I've never tried it.
Also, I believe "fastboot oem unlock" (unlocking bootloader) wipes your sdcard as well, so backup any important pictures or whatever you need before doing this.
Perfect! In that tool it shows me, theres different options. Should I rename Restore Files and Flash CWM Recovery?
How do I get 4.0.3? I'm on 4.0.1 right now?
Do I download Release 2.1 AOKP GSM B15.zip?
Click to expand...
Click to collapse

BrandonPrice31 said:
Perfect! In that tool it shows me, theres different options. Should I rename Restore Files and Flash CWM Recovery?
How do I get 4.0.3? I'm on 4.0.1 right now?
Do I download Release 2.1 AOKP GSM B15.zip?
Click to expand...
Click to collapse
To get 4.0.3, yeah.. you need to download either:
- AOKP Milestone 2 [Have to get it from Rootzwiki.. as latest on XDA is build 15]
- Bigxie's Build 8
(Select one of them that you'd like to use)
and Franco Kernel.. it'll improve your battery life // performance.
You just need to unlock bootloader, flash clockwork recovery

zephiK said:
To get 4.0.3, yeah.. you need to download either:
- AOKP Milestone 2 [Have to get it from Rootzwiki.. as latest on XDA is build 15]
- Bigxie's Build 8
(Select one of them that you'd like to use)
and Franco Kernel.. it'll improve your battery life // performance.
You just need to unlock bootloader, flash clockwork recovery
Click to expand...
Click to collapse
Can you link me to AOKP?
If I do AOKP means I don't need Bigxies right?

BrandonPrice31 said:
Can you link me to AOKP?
If I do AOKP means I don't need Bigxies right?
Click to expand...
Click to collapse
AOKP: http://rootzwiki.com/topic/11455-rom-android-open-kang-project-maguro-milestone-2/
Franco Kernel: http://forum.xda-developers.com/showthread.php?t=1367341
And yes that is correct.
Basically once you have Clockwork Recovery up and running (black background, tealish colors).. although I don't think the link that I gave you installs Clockwork Recovery Touch Enabled (which is really cool). Basically use the volume buttons and go into:
install zip from sdcard
select
choose AOKP (this will flash it)
select again
choose franco kernel (this will flash it-- you have to do this in order)
wipe: factory, cache, (you can find these on the main menu), go into advanced and wipe dalvik cache too.. then hit go back then reboot system!
congrats you will be on 4.0.3 with a custom kernel.

zephiK said:
AOKP: http://rootzwiki.com/topic/11455-rom-android-open-kang-project-maguro-milestone-2/
Franco Kernel: http://forum.xda-developers.com/showthread.php?t=1367341
And yes that is correct.
Basically once you have Clockwork Recovery up and running (black background, tealish colors).. although I don't think the link that I gave you installs Clockwork Recovery Touch Enabled (which is really cool). Basically use the volume buttons and go into:
install zip from sdcard
select
choose AOKP (this will flash it)
select again
choose franco kernel (this will flash it-- you have to do this in order)
wipe: factory, cache, (you can find these on the main menu), go into advanced and wipe dalvik cache too.. then hit go back then reboot system!
congrats you will be on 4.0.3 with a custom kernel.
Click to expand...
Click to collapse
So to sumarize I'm going to be using AOKP Milestone 2 with Franco's Kernal, correct? Will I be able to do this all with that tool you provided? Are you sure I should not rename the Restore Files nor glash the CWM?

BrandonPrice31 said:
So to sumarize I'm going to be using AOKP Milestone 2 with Franco's Kernal, correct? Will I be able to do this all with that tool you provided? Are you sure I should not rename the Restore Files nor glash the CWM?
Click to expand...
Click to collapse
Yes that is correct. And it is kernel not kernal (doesn't bother me but other people might. I don't know what that tool would be restoring as you don't have any nandroid backups present or any backups at all.
To restore something, something needs to be present to "restore."

zephiK said:
Yes that is correct. And it is kernel not kernal (doesn't bother me but other people might. I don't know what that tool would be restoring as you don't have any nandroid backups present or any backups at all.
To restore something, something needs to be present to "restore."
Click to expand...
Click to collapse
I just installed Titanium backup on my non-rooted phone.. Can't find the application? How do I get to it?

BrandonPrice31 said:
I just installed Titanium backup on my non-rooted phone.. Can't find the application? How do I get to it?
Click to expand...
Click to collapse
App won't work on a non-rooted device. To be rooted, you need to unlock your bootloader. Unlocking your bootloader will fully wipe your phone as I mentioned previously.
1. Backup any important files off your device. You cannot backup apps/data. By this step I mean important files such as pictures, documents, whatever.
2. Unlock bootloader
3. Flash Clockwork Recovery
4. Flash ROM, Kernel [also wipe]
5. Reboot
6. You're on 4.0.3

zephiK said:
App won't work on a non-rooted device. To be rooted, you need to unlock your bootloader. Unlocking your bootloader will fully wipe your phone as I mentioned previously.
Click to expand...
Click to collapse
Oh, I don't care..... My applications are synced with my account anyway.. Don't really lose much haha!
Alright, waiting till' my phone is fully charged then going to give it a go. PM for compensation

zephiK said:
App won't work on a non-rooted device. To be rooted, you need to unlock your bootloader. Unlocking your bootloader will fully wipe your phone as I mentioned previously.
1. Backup any important files off your device. You cannot backup apps/data. By this step I mean important files such as pictures, documents, whatever.
2. Unlock bootloader
3. Flash Clockwork Recovery
4. Flash ROM, Kernel [also wipe]
5. Reboot
6. You're on 4.0.3
Click to expand...
Click to collapse
Just to verify, that application unlocks, and flashes my clockwork recovery for me, correct?

BrandonPrice31 said:
Oh, I don't care..... My applications are synced with my account anyway.. Don't really lose much haha!
Alright, waiting till' my phone is fully charged then going to give it a go. PM for compensation
Click to expand...
Click to collapse
You don't really need to wait for your phone to be charged, it'll charge while your phones plugged in your USB
@Post above: Yes that is correct. You'd want to do numbers: 1 & 4
Then go to 17.... boot into Android, it'll tell you to put your Google information etc etc.. skip all of it, and what you want to do now is get to the homescreens. When you're in the home screen, drag the zip of AOKP and the kernel onto the root of your sdcard (main folder). Then you can use that tool again and go to 16 (or if you manually want to... turn the phone off then hold volume up and down + power [all three] then that'll bring you to fastboot mode, press the volume rocker until you see "Recovery" when it's there.. press on the power button and it'll bring you to a screen looking like this,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Basically once you have Clockwork Recovery up and running (black background, tealish colors).. although I don't think the link that I gave you installs Clockwork Recovery Touch Enabled (which is really cool). Basically use the volume buttons and go into:
install zip from sdcard
select
choose AOKP (this will flash it)
select again
choose franco kernel (this will flash it-- you have to do this in order)
wipe: factory, cache, (you can find these on the main menu), go into advanced and wipe dalvik cache too.. then hit go back then reboot system!

zephiK said:
You don't really need to wait for your phone to be charged, it'll charge while your phones plugged in your USB
@Post above: Yes that is correct. You'd want to do numbers: 1 & 4
After doing those then go to 16... when in fastboot mode, press the volume rocker until you see "Recovery" when it's there.. press on the power button and it'll bring you to a screen looking like this,
Click to expand...
Click to collapse
Can I root for the sake of rooting? So I can get rooted applications etc?

Factory Images 4.1.2 (JZO54K) "takju" (GSM/HSPA+) (with Google Wallet)

it's up guys
https://developers.google.com/android/nexus/images#takjujzo54k

since I haven't gotten the OTA update yet can I just flash "system.img" in fastboot to update from 4.1.1. to 4.1.2. and call it a day ?

Nice! And so I'm tempted to switch to takju once again...
I probably will switch over the weekend if the yakju OTA hasn't come out by then.

Thanks for posting!

Interesting Google provided a windows batch file for flashing.
In other news my usb port is messed up so I'm going to have to wait for the OTA

Currently unlocked and on Yakju. If I flash to Takju, will I lose all the data?

I'm 99% sure that you will loose all user data.

NexusDro said:
Currently unlocked and on Yakju. If I flash to Takju, will I lose all the data?
Click to expand...
Click to collapse
Maybe, but maybe not.
Assuming you have all you apps and app data backuped up in /sdcard using Titanium Backup, do the following:
Flash the boot and system images only, reboot into CWM, wipe cache and dalvik cache, and then reboot.
If you end up with a bootloop or it doesn't boot, just reboot into CWM and wipe data, and it will reboot. Then restore you apps and app data via TB (after flashing a superuser zip of course).
EDIT: I've never seen any say they've tried it, so maybe you can help all of us out.

Thanks! Mine's not root so no titanium backup for me. Since I'm currently out of town until this weekend, I'll wait for the OTA and see what happens.

efrant said:
Maybe, but maybe not.
Assuming you have all you apps and app data backuped up in /sdcard using Titanium Backup, do the following:
Flash the boot and system images only, reboot into CWM, wipe cache and dalvik cache, and then reboot.
If you end up with a bootloop or it doesn't boot, just reboot into CWM and wipe data, and it will reboot. Then restore you apps and app data via TB (after flashing a superuser zip of course).
EDIT: I've never seen any say they've tried it, so maybe you can help all of us out.
Click to expand...
Click to collapse
Nonsense,
I was on yakju rooted with the bootloader unlocked, of course. Then I followed your AWESOME guide without backing up ANYTHING and it worked!
I only skipped step 10 (flash userdata.img) and rebooted just fine. It took a while because of the dalvik cache rebuild.
After that I booted in CWM (without flashing it) and applied the SuperUser .zip and gained root again.
Everything's fine. No data loos at all!
Cheers!

Interesting to note that they seem to have 4.1.2 completely superceding 4.1.1, that is to say, they're removing the 4.1.1 builds once a 4.1.2 build is up for a particular device.

osm0sis said:
Interesting to note that they seem to have 4.1.2 completely superceding 4.1.1, that is to say, they're removing the 4.1.1 builds once a 4.1.2 build is up for a particular device.
Click to expand...
Click to collapse
For the Nexus 7, it is a requirement since newer Nexus 7 variants will apparently not run on 4.1.1. So I think they are not going to keep the links up for 4.1.1 because of that.

Can anyone post the Build.prop form takju 4.1.2

3rdstring said:
Can anyone post the Build.prop form takju 4.1.2
Click to expand...
Click to collapse

El Daddy said:
Interesting Google provided a windows batch file for flashing.
In other news my usb port is messed up so I'm going to have to wait for the OTA
Click to expand...
Click to collapse
It's easy to make a batch file, I personally made one for my n7 and gnex.
Will the next nexus have a longer screen?

5 hours to download from Google. Anyone have a mirror?

No OTA's yet?
Sent from my Galaxy Nexus using xda app-developers app

el_charlie said:
Nonsense,
I was on yakju rooted with the bootloader unlocked, of course. Then I followed your AWESOME guide without backing up ANYTHING and it worked!
I only skipped step 10 (flash userdata.img) and rebooted just fine. It took a while because of the dalvik cache rebuild.
After that I booted in CWM (without flashing it) and applied the SuperUser .zip and gained root again.
Everything's fine. No data loos at all!
Cheers!
Click to expand...
Click to collapse
You dirty-flashed yakju to takju, and no problems? Congratulations to you and efrant!

segv11 said:
You dirty-flashed yakju to takju, and no problems? Congratulations to you and efrant!
Click to expand...
Click to collapse
Not a single one!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks to efrant for such amazing guide.
Cheers!
Sent from my Galaxy Nexus using xda premium

Sorry for the noob question but what tool did u guys use to flash some portions of the factory image? Mobile odin, odin or gnexus toolkit? Thank you
Can someone please provide a noob proof tutorial to flash an unlocked and rooted "yakju", thank you again.
Sent from my Nexus Prime JB 4.1.1

[Q] Flashing My i8160 Ace 2 to 4.4 Kitkat

Hi guys, i just updated my Ace 2 from 2.3.6 GB to 4.1.2 JB through Samsung Kies. After the update process, i used the "root.zip" (err, just saw it while searching from the forum) in order for it to be rooted. I also downloaded gooManager, Root Browser, ROM manager, Greenify, Titanium. Also removed unnecessary apps using Root Browser ( saw list of bloated apps on Ace 2 also in this forum). It is my first time rooting my droid and I want to obtain knowledge in order to maximize my droid's capabilities.
So here's my questions (so far):
1. Why is it my Recovery Mode is looking like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
instead of looking like this:
since because i wanted to flash it but when I see some tutorials, their recovery mode has a ROM Manager logo which made me hesitated on flashing.
2. What can you recommend on me , a newbie , about flashing tips in order to flash my Ace 2 into 4.4 kitkat?
Source : http://forum.xda-developers.com/showthread.php?t=2524905
3. Can someone tell me how to flash proper because im confused on flashing through recov mode and using Odin
4. Lastly, if i factory reset my 4.1.2 JB through recov. mode, will it revert my droid into 2.3.6 GB ? will it remove the root?
since i also saw some tutorials flashing by factory reset in recov. mode then installing from SD Card also in recov. mode
Please help me clear my mind on flashing Thank you !

So here's my questions (so far):
1. Why is it my Recovery Mode is looking like this:
instead of looking like this:
since because i wanted to flash it but when I see some tutorials, their recovery mode has a ROM Manager logo which made me hesitated on flashing.
1- because thats CWM, never use rom manager. Search forum for cwm 6 by shaaan
EDIT: temp cwm 6 http://forum.xda-developers.com/showthread.php?t=2141395
2. What can you recommend on me , a newbie , about flashing tips in order to flash my Ace 2 into 4.4 kitkat?
Source : http://forum.xda-developers.com/showthread.php?t=2524905
2- thats a theme, no kitkat yet
3. Can someone tell me how to flash proper because im confused on flashing through recov mode and using Odin
3- follow instructions in first post of EVERY rom thread, you should be safe
4. Lastly, if i factory reset my 4.1.2 JB through recov. mode, will it revert my droid into 2.3.6 GB ? will it remove the root?
since i also saw some tutorials flashing by factory reset in recov. mode then installing from SD Card also in recov. mode
4-
-no
-no
-dont follow those tuts, follow our ace 2 ones, to revert to 2.3 search forum for the thread, its late here ill try to link the thread for you
Sent from my GT-I8160 using Tapatalk

Try to download it again and as it says, it is for Android 4.3.

nairb310 said:
1. Why is it my Recovery Mode is looking like this instead of looking like this:
4. Lastly, if i factory reset my 4.1.2 JB through recov. mode, will it revert my droid into 2.3.6 GB ? will it remove the root?
since i also saw some tutorials flashing by factory reset in recov. mode then installing from SD Card also in recov. mode
Please help me clear my mind on flashing Thank you !
Click to expand...
Click to collapse
1: In the Ace 2, recovery comes from the kernel. You can temporarily load "cwm6.zip" to upgrade until the next reboot "Android system recovery 3E" into CWM 6.0.2, and once you install another kernel with a modified recovery (CM10.2 contains CWM 6.0.3 for example) it will always load in place of the stock one.
4: Factory reset means deleting everything under /data (the system memory in which apps are installed by default), /cache and .android_secure (apps moved to SD or USB storage), the OS and all system applications will persist. You will technically stay rooted, but SuperSU will only remain if it was installed as a system app.
To switch between 2.x and 4.x you must flash and repartition with a complete 3-part firmware (with PIT, CODE/PDA and CSC files), like LK4 or MB4. After that you can install an OS of the same generation using Odin/Heimdall (for tar files) or CWM (for zips).
Most stock-derivate firmwares recommend a base version but it's usually optional; AOSP roms (Cyanogen, AOKP and the like) don't care at all.

Ryccardo said:
1: In the Ace 2, recovery comes from the kernel. You can temporarily load "cwm6.zip" to upgrade until the next reboot "Android system recovery 3E" into CWM 6.0.2, and once you install another kernel with a modified recovery (CM10.2 contains CWM 6.0.3 for example) it will always load in place of the stock one.
4: Factory reset means deleting everything under /data (the system memory in which apps are installed by default), /cache and .android_secure (apps moved to SD or USB storage), the OS and all system applications will persist. You will technically stay rooted, but SuperSU will only remain if it was installed as a system app.
To switch between 2.x and 4.x you must flash and repartition with a complete 3-part firmware (with PIT, CODE/PDA and CSC files), like LK4 or MB4. After that you can install an OS of the same generation using Odin/Heimdall (for tar files) or CWM (for zips).
Most stock-derivate firmwares recommend a base version but it's usually optional; AOSP roms (Cyanogen, AOKP and the like) don't care at all.
Click to expand...
Click to collapse
Thank you for your reply but i cant understand some of the term you are saying XD So basically on 1. recovery kernel can be upgraded ? and my kernel i think is old ? so that is why my recov mode is not looking like ROM manager logo?
so also i can flash using ROM manager or Recovery mode with my current system ?

Flash temp cwm 6 zip in stock recovery(will be called update.zip, i added link). Dont use rom manager
Sent from my iPhone

nairb310 said:
Thank you for your reply but i cant understand some of the term you are saying XD So basically on 1. recovery kernel can be upgraded ? and my kernel i think is old ? so that is why my recov mode is not looking like ROM manager logo?
so also i can flash using ROM manager or Recovery mode with my current system ?
Click to expand...
Click to collapse
The same kernel that runs "the full Android experience" also contains the recovery that boots with up+home+power. Some kernels have the "Android system recovery 3E" (which can be temporarily upgraded to CWM with cwm6.zip), others have CWM directly.
Basically, if you have a Cyanogen ROM installed, it will have CWM preinstalled. For everything else keep the temporary CWM in you external storage.
(All this ignores Gingerbread kernels, but let's keep matters simple as you're probably using JB)