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

[ROM][CWM][LTE] ICL53F Deodexed Rooted Busyboxed+Softkeys+APM/AB+ChargeFix (1/2/12)

This is just a very basic stock ROM. I deodexed the ICL53F system image from Google (Android 4.0.2) rooted it and installed busybox. I saw that no such stock ROM was available and decided to share mine.
Features
Stock 4.0.2 ICL53F
Deodexed Framework and System Apps
All APKs Zipaligned
Latest Superuser and su
Busybox Installed
Insecure boot.img (adb remount privileges)
Requirements
LTE Galaxy Nexus
Clockwork Recovery
Kernel and baseband in screenshot below (if you don't have them, look in the 2nd post for the fastboot images - flash them in bootloader prior to flashing the ROM)
Screenshot
{
"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"
}
Instructions
No need to wipe data coming from stock
Boot into Clockwork, make a backup (highly suggested)
Wipe dalvik and cache
Flash ROM
Reboot
Profit!
Some things to watch out for
The first boot will take a few minutes
Download
toro_signed_ICL53F_rooted_deodexed_bigxie_010212.zip
MD5: c1499d3f76f0b2eeeac8ab7976ffbec7 toro_signed_ICL53F_rooted_deodexed_bigxie_010212.zip
If you enjoy my work, consider buying me a beer
Donations FabDroid

Advanced Power Menu + Autobrightness Tweaks (credit he_stheone64 on XDA for GSM version)
Adds reboot and recovery options to power menu. Raises auto brightness levels slightly.
*flash this in recovery, wipe dalvik and cache
APM_AB_LTE_ICL53F.zip
57d65c60bafc7e14cec29449dfb01097 *APM_AB_LTE_ICL53F.zip
Fastboot images (optional, for those not on the latest kernel/baseband)
toro_radio_kernel_ICL53F.zip
Code:
fastboot flash boot boot.img
fastboot flash radio radio-toro-i515.ek02.img
fastboot flash radio-cdma radio-cdma-toro-i515.ek05.img
Softkeys Mod (credit to Paul O'Brien, I learned from his SystemUI.apk to make mine ;-)
Must be on a deodexed ROM to install! Install after initial boot!
Search button, hidden menu buttons on both sides (exposed when apps call for them)
softkeys_mod_ICL53F.zip
4d1713cfc93517cb5c6fa5f97d713be1 *softkeys_mod_ICL53F.zip
*flash this, no need to wipe anything

You have a quick way to revert the modded soft keys?
Sent from my Galaxy Nexus using Tapatalk

bangdrum said:
You have a quick way to revert the modded soft keys?
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I would just reflash the ROM, that will switch it back to stock.

Will this work on any of the stock zipaligned roms?
Sent from my Galaxy Nexus using Tapatalk

You can also just insert the systemui.apk from the main ROM in the update.zip of the mod (overwrite the systemui in this zip) and flash.

for some odd reason I could not get this to work. Just kept getting stuck at the goggle logo. Yes I downloaded the correct LTE version.

bangdrum said:
Will this work on any of the stock zipaligned roms?
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Not quite sure if it will, those are still odexed. For sure you'll want to delete the SystemUI.odex file if you flash this.
ihyln said:
for some odd reason I could not get this to work. Just kept getting stuck at the goggle logo. Yes I downloaded the correct LTE version.
Click to expand...
Click to collapse
A few things, did you already accept the 4.0.2 OTA prior to flashing the ROM (you need to in order to get the new kernel and baseband)? Did you wipe dalvik and cache when you flashed the ROM? Did you check the MD5SUM to make sure the file wasn't corrupted?

Is there any way to make the search key have long press abilities? Sorry for all the questions bro lol
Sent from my Galaxy Nexus using Tapatalk

bigxie said:
Not quite sure if it will, those are still odexed. For sure you'll want to delete the SystemUI.odex file if you flash this.
A few things, did you already accept the 4.0.2 OTA prior to flashing the ROM (you need to in order to get the new kernel and baseband)? Did you wipe dalvik and cache when you flashed the ROM? Did you check the MD5SUM to make sure the file wasn't corrupted?
Click to expand...
Click to collapse
MD5SUM was correct. I did take the 4.0.2 OTA but I wanted to get a deodexed rom so I gave it a try. Also wiped dalvik and cache prior to installing.

I have the kernel but my baseband is ek05/ek02 how would i change the baseband i forgot to make a backup and im not on stock

Tried this an got a bootloop.
Logcat gives me the following:
quote removed because error is gone, i was trying the wrong ROM... i am so stupid -.-
Click to expand...
Click to collapse
Maybe this can help somebody
I was coming from 4.0.1 stock ROM rooted without wipe, only cleared dalvik cache and /cache.
I am happy i did a nandroid backup
EDIT: error is gone, i was trying the wrong ROM... i am so stupid -.-

myxor said:
I was coming from 4.0.1 stock ROM rooted without wipe, only cleared dalvik cache and /cache.
I am happy i did a nandroid backup
Click to expand...
Click to collapse
The issue could be that you came from 4.0.1 instead of 4.0.2 like the OP called for. I would think that the upgrade would have gone smoother than the downgrade (like if you were on 4.0.2 trying to flash a 4.0.1 ROM) but i bet you it would fix your issues just to update first to the current build OTA or you could wipe data/cache.

Hey everyone that is coming from 4.0.1, I uploaded the new kernel and radios into the 2nd post.
You can flash them in bootloader using fastboot, then reboot right into recovery to flash the ROM.

I don't suppose that you can craft a version of the soft-key mod like Paul's that has the menu button always shown? This is the only thing I have issues with in ICS - many apps (like FBReader) don't show the menu button, which makes the app useless...
Paul's patch still causes the top and bottom bar to disappear on the LTE Nexus...

jeffreycentex said:
I don't suppose that you can craft a version of the soft-key mod like Paul's that has the menu button always shown? This is the only thing I have issues with in ICS - many apps (like FBReader) don't show the menu button, which makes the app useless...
Paul's patch still causes the top and bottom bar to disappear on the LTE Nexus...
Click to expand...
Click to collapse
My softkeys are built using the exact same mods he used in his MCR ROM.
Those menu buttons are persistent in both corners, but the three dots only show up when apps call for them.

bigxie said:
Not quite sure if it will, those are still odexed. For sure you'll want to delete the SystemUI.odex file if you flash this.
A few things, did you already accept the 4.0.2 OTA prior to flashing the ROM (you need to in order to get the new kernel and baseband)? Did you wipe dalvik and cache when you flashed the ROM? Did you check the MD5SUM to make sure the file wasn't corrupted?
Click to expand...
Click to collapse
OP i don't know why you don't have more thanks but this thread is absolutely perfect. i was looking for a stock rom that was deodexed so i could load the paul obrien mods as well as the battery display mods, thanks for your hard work.

So I have a stock 4.0.2 how do I go about getting this installed?

ihyln said:
So I have a stock 4.0.2 how do I go about getting this installed?
Click to expand...
Click to collapse
Read the OP.

bigxie said:
Fastboot images (optional, for those not on the latest kernel/baseband)
toro_radio_kernel_ICL53F.zip
Code:
fastboot flash boot boot.img
fastboot flash radio radio-toro-i515.ek02.img
fastboot flash radio-cdma radio-cdma-toro-i515.ek05.img
Softkeys Mod (credit to Paul O'Brien, I learned from his SystemUI.apk to make mine ;-)
Must be on a deodexed ROM to install! Install after initial boot!
Search button, hidden menu buttons on both sides (exposed when apps call for them)
softkeys_mod_ICL53F.zip
4d1713cfc93517cb5c6fa5f97d713be1 *softkeys_mod_ICL53F.zip
*flash this, no need to wipe anything
Click to expand...
Click to collapse
tried flashing the new baseband/kernel, flashes the first radio perfectly, but when i try and flash the radio-cdma, it sends the file to the phone, but gets stuck when writing it to the phone
*updated* both radios flash perfectly. It just takes a really long time to write the radio-cdma to the phone. thanks for your help!!!

[Q] Bricked Samsung Galaxy W (GT-i8150)

I soft-bricked my galaxy and there's no way to fix it, help! Okay, this is a what happened, I installed a custom ROM which worked out perfectly well until one day all applications started force closing for apparently no reason so I reboot and got stuck in a boot loop. I can only access download mode, recovery is out of the question. I tried to flash back to stock with Odin and it "passed" but the screen was just blank. So, I removed the USB cable hoping it will work and it got stuck in another boot loop. I tried everything that I could have think of but nothing works. It seems that I'm not the only one and is common for Galaxy W devices. Please help!

Also, in the worst case how do I send it back to Samsung? I mean, I know how to but will they fix it?

Location ?
Sent from my GT-I8150 using xda premium

dont worry , you can just flash it again. A new stock ROM would do. Its no problem.
We have a guide here on this forum. Check it out ^_^

andynroid said:
Location ?
Sent from my GT-I8150 using xda premium
Click to expand...
Click to collapse
Umm....Malaysia?
jrandroid said:
dont worry , you can just flash it again. A new stock ROM would do. Its no problem.
We have a guide here on this forum. Check it out ^_^
Click to expand...
Click to collapse
I have tried that and it does not work.

Me too I got the same problem. But flashed a stock rom and everything 's working well except data network. Sending it to Samsung centre to fix. To brick it join the Galaxy W Malaysian users group on FB I'm sure you'll find the solution to brick
Sent from my GT-I8150 using XDA

darthbii said:
Me too I got the same problem. But flashed a stock rom and everything 's working well except data network. Sending it to Samsung centre to fix. To brick it join the Galaxy W Malaysian users group on FB I'm sure you'll find the solution to brick
Sent from my GT-I8150 using XDA
Click to expand...
Click to collapse
Can you please explain what did you do exactly?

Hi
Sorry, but if you cannot go to recovery problem..
The problem is in your hardware
I already put this problem to this thread
Read carefully
To many member have re-post this problem
So your are not alone
For the others please aware this situation,
This is not problem that you can solve by flashing
Read the thread with "star" first before you posting and get confuse
Regards

Stock Gaming Rom Stable i8150XXLM8
i may have the same problem i use cynanogen mod 9 build 3 then flash to this stock gaming rom..problem start
1. 3g/wcdma not detected/no 3g icon appear/cannot download anuthing
2. reboot using clockwokr mod....but cannot reboot..its say root acces posibly lost..but SU does exist in apps

andydidacus said:
i may have the same problem i use cynanogen mod 9 build 3 then flash to this stock gaming rom..problem start
1. 3g/wcdma not detected/no 3g icon appear/cannot download anuthing
2. reboot using clockwokr mod....but cannot reboot..its say root acces posibly lost..but SU does exist in apps
Click to expand...
Click to collapse
did you full wipe before flashing stock rom?
what stock gaming rom, it is full recovery?
you may can try:
- flashing again cwm using odin,
- if succesfull, boot to cwm, format data and cache, except system
- try reboot normally.
- if failed, format everything, except your sdcard,
- flashing stock rom using odin, (better use stock rom provided for your country), use original stock rom, not modified rom ! with size more than 350mb, its contain recovery, baseand and everything you need. of course your cwm will be replaced after. you can flash again cwm after your phone boot normally.
good luck.

andydidacus said:
i may have the same problem i use cynanogen mod 9 build 3 then flash to this stock gaming rom..problem start
1. 3g/wcdma not detected/no 3g icon appear/cannot download anuthing
2. reboot using clockwokr mod....but cannot reboot..its say root acces posibly lost..but SU does exist in apps
Click to expand...
Click to collapse
In reverting back to GB 2.3.6 from CM9, you should do format /system to be able to flash successfully. Try it.

Yes i jave succesfully revert to gb rom..n finally traded it woth sgn
Sent from my GT-N7000 using xda premium

Thanks
coliv_aja said:
did you full wipe before flashing stock rom?
what stock gaming rom, it is full recovery?
you may can try:
- flashing again cwm using odin,
- if succesfull, boot to cwm, format data and cache, except system
- try reboot normally.
- if failed, format everything, except your sdcard,
- flashing stock rom using odin, (better use stock rom provided for your country), use original stock rom, not modified rom ! with size more than 350mb, its contain recovery, baseand and everything you need. of course your cwm will be replaced after. you can flash again cwm after your phone boot normally.
good luck.
Click to expand...
Click to collapse
Thanks really worked! ^

Hi! yesterday I tried to get cyanogenmod to my Samsung galaxy W. Firstly I used this tutorial to root my phone View attachment 1899558
Then I installed clockworkmod recovery with this tutorial
{
"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"
}
When I did the ''IV. Accessing ClockworkMod Recovery'' , I tried to backup my phone, but there wasn't enough space to do it, so I pressed ''reboot'' and this happens, it goes through the samsung and galaxy w logo, but after that the screen just turns black, this happens every time when I try to turn it on. I can access the clockworkmod recovery.
I have tried to ''wipe the cache partition'', ''wipe data/factory reset'' and wipe ''dalvik cache'' but it doesn't seem to work.
What should I do, I don't want cyangenmod after this haha I just want to know if there is a way to get the phone working.
Any answers would be appreciated

Eerooo said:
Hi! yesterday I tried to get cyanogenmod to my Samsung galaxy W. Firstly I used this tutorial to root my phone View attachment 1899558
Then I installed clockworkmod recovery with this tutorial View attachment 1899561
When I did the ''IV. Accessing ClockworkMod Recovery'' , I tried to backup my phone, but there wasn't enough space to do it, so I pressed ''reboot'' and this happens, it goes through the samsung and galaxy w logo, but after that the screen just turns black, this happens every time when I try to turn it on. I can access the clockworkmod recovery.
I have tried to ''wipe the cache partition'', ''wipe data/factory reset'' and wipe ''dalvik cache'' but it doesn't seem to work.
What should I do, I don't want cyangenmod after this haha I just want to know if there is a way to get the phone working.
Any answers would be appreciated
Click to expand...
Click to collapse
Some wrong sequence there :
Forgets the steps as per attachment.
In assumption the CM9 ROM.zip is in your SD Card...
Boot to CWM
Locate the CM9 ROM using and remember the location i.e. External SD etc
Now under Advance...Format all folders clean (not the folder containing the CM9 ROM)
Wipe / Format / Cache etc = the usual
Wipe Dalvik
Fix Permission
Flash the CM9 then GAPPS
Reboot...:good:
No need to back-up once you have used CM9...you will never go back to GB
If you insist on back-up just move all your treasures in your PC 1st, best to format the SD Card then move the ROM.zip to it

andynroid said:
Some wrong sequence there :
Forgets the steps as per attachment.
In assumption the CM9 ROM.zip is in your SD Card...
Boot to CWM
Locate the CM9 ROM using and remember the location i.e. External SD etc
Now under Advance...Format all folders clean (not the folder containing the CM9 ROM)
Wipe / Format / Cache etc = the usual
Wipe Dalvik
Fix Permission
Flash the CM9 then GAPPS
Reboot...:good:
No need to back-up once you have used CM9...you will never go back to GB
If you insist on back-up just move all your treasures in your PC 1st, best to format the SD Card then move the ROM.zip to it
Click to expand...
Click to collapse
Thank you so much!There is still a problem my phone recognizesmy sd card it and also tells me how much storage i have left. But when i want to use an application like the camera it says there is no sd card. What should I do?
E: Already got the problem fixed

Got another SD card to swap ?

Please Help me T.T
I just wanna go back to original Stock Rom and yesterday I Flash the firmware Malaysia with Odin.. the Odin haven't pass then my phone automatically restart and after few minutes the odin said PASS and the message there wrote ''distroy instant'' and ''Killed timer''... after that my galaxy w cannot boot.. it just stucked at the start screen wallpaper there.....
please help me... sorry for my broken english...
---------- Post added at 02:01 PM ---------- Previous post was at 01:21 PM ----------
odin wrote Close serial portal and wait until rebooting but it havent PASS and my wonder cannot start and it stucked at samsung logo....

j0rd4nkzf said:
Umm....Malaysia?
I have tried that and it does not work.
Click to expand...
Click to collapse
last time my phone cannot start too because i flash wrong file, then i send service centre at lowyat saying my phone suddenly can't be turned on (don't say ur already root or whatever can void the warranty)
Ore Sanjou!

j0rd4nkzf said:
I soft-bricked my galaxy and there's no way to fix it, help! Okay, this is a what happened, I installed a custom ROM which worked out perfectly well until one day all applications started force closing for apparently no reason so I reboot and got stuck in a boot loop. I can only access download mode, recovery is out of the question. I tried to flash back to stock with Odin and it "passed" but the screen was just blank. So, I removed the USB cable hoping it will work and it got stuck in another boot loop. I tried everything that I could have think of but nothing works. It seems that I'm not the only one and is common for Galaxy W devices. Please help!
Click to expand...
Click to collapse
u must service it in SamsungServiceCenter

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

CM 11 4.4 kitkat issue

I'm using cm9 that has the team win recovery. When I try to flash the cm 11 kitkat rom it says fail. Do i need to use a cwm recovery or is the download link bad ?

mr. ya-di-da said:
I'm using cm9 that has the team win recovery. When I try to flash the cm 11 kitkat rom it says fail. Do i need to use a cwm recovery or is the download link bad ?
Click to expand...
Click to collapse
Flash it from cwm... but after the flash completes, reboot recovery and do you're wipes ( again ) and flash kitkat from it's recovery. Then reboot.
Let it chill for a few minutes, then boot back to recovery and flash you're 4.4 gapps.
This process always worked for me on 4.3 and I'm assuming it will work on 4.4. But I've not flashed 4.4 yet. So proceed with caution.
Good luck...

I will try it when I get home from work so I can use Odin to flash a cwm recovery. Everytime I use mobile Odin to flash a recovery it bricks my phone ....why does that happen ?

mr. ya-di-da said:
I will try it when I get home from work so I can use Odin to flash a cwm recovery. Everytime I use mobile Odin to flash a recovery it bricks my phone ....why does that happen ?
Click to expand...
Click to collapse
I'm not sure about the mobile Odin issue... are you making sure the tar file for the kernel is a good download and that it is compatible with the Android version and rom you're trying to run...?
Try downloading the Directboot EL29 kernel from rwilco12's repo.. ( make sure you get the Directboot EL29 kernel and not the stock el29 kernel )
After you have it and the rom you want on you're sdcard... use mobile Odin to flash the el29 db kernel.. it should boot to recovery on it's own..
Push volume up, volume down, volume up... this enables the power button as the select button...
Do you're wipes... and flash 4.4...reboot recovery... do wipes.. ( data, cache, dalvik, and format system )...flash 4.4 again.. reboot.. settle in for a few minutes and then boot recovery and flash gapps 4.4...reboot.
Let me know how it goes... I'll stick around tonight until we get ya up and running...

It failed.. (status 7)

mr. ya-di-da said:
It failed.. (status 7)
Click to expand...
Click to collapse
Ok... I'll try to get to it tomorrow... but Thursday at the latest.

OK thx. I saw that other people where getting the same fail (status 7) let me know what u find.

Status 7 is a syntax error in the updater script... Probably missing a semicolon or something silly like that.
{
"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"
}

Not related to this issue, unsure if it would be better etiquette to make my own thread for this, but an issue I'm having with dastins CM11 ROM (12-04-13 version) is that I have two "Internal Storages" instead of one (I do not own/use a SD card)
On CM10/10.1/10.2 I had one internal storage, but on CM11 I have a 2GB internal storage and then a second internal storage (that things seem to not be installed to at all) with the remainder of my devices space.
One of the applications I used a lot on stock TouchWiz and earlier versions of CM is larger than two gigs, so on CM11 I can't even install it because it says I have insufficient storage. Is there a way I can combine the two internal storages into one, so it functions like it did on CM10.2 so I can use all of my devices space instead of only 2GB?
---------
Another question, and this one I'm probably just being blind and not seeing it, or maybe this setting is in a different location in KitKat, is my phone is set to USB mass storage instead of MTP. Normally I head over to Settings > Storage > hit the menu key and change USB connection type to MTP, but the menu key doesn't seem to do anything anymore on the Storage page. Where would I change to MTP instead of Mass Storage, or how can I just disable Mass Storage, I honestly don't care about being able to get any files on/off the device, but 90% of the time I'm charging on USB and I just don't want a full screen prompt showing up every time I touch my phone saying "Hey! It's Plugged In! Do you want to turn USB Storage on?"

You need to flash cm11 with the newest cwm... The old regular way of the"safe" recovery doesnt work... The easy way Is to download the blasphemy kernel and install it then boot back into recovery... It will be cwm 6.0.4.5... Flash the rom with this and no status 7...
Hope this helps...
Sent from my SPH-D710 using Tapatalk 2

I have an EL29 direct boot zip file that works with agats and even the newer cwms to flash back to.
I've tested it on the following recoveries and not had an issue at all:
agats (both 1.3 and 1.4), stock twiz, and the latest CWM they are useing.
I have gone to el29 direct boot with all of the above and had no issues, it goes into el29 recovery just fine.
DO keep in mind though I made this zip mainly for flashing into roms, not as a stand alone kernel, so you may have issues wif you use this as your standard go to kernel with the rom. Mst roms already have thier own kernel anyways, so that's normally not an issue, jsut so you are aware this is basically used for flashing roms not as the normal kernel.
I can host it on dev-host if anyone is interested, otherwise I won't bother.....and I ask because sometimes people just don't wanna be bothered, so I always ask......anyways let me know I will host it.
Just as a side note the steps I have done are as follows:
-reboot to recovery
-flash el29 zip file within said recovery (as I said I've tested this on all the above and it works fine)
-reboot recovery (it will be el29 now)
It should be back to the el29 recovery and you can flash from there.
Done this on hood pope (4.3), Viluminati (4.4 and 4.4.1 KitKat), cm10.1 (4.2.2) and stock Twiz rooted (not stock Twiz recovery) but agats recovery 1.3 and 1.4.
Those that don't know how to activate the power button to select what you do is toggle up > down >up > down until it says something about it being activated, you can then just use power to select your option.

kitkat 4.4.1
I rooted my device using rwilcos fl24 method although I was on a fd24 model. After root I flashed a custom recovery using Odin I believe it was agats...I then proceeded to flash a ROM cm10.1 then upgraded to cm 10.2. Now running KitKat 4.4.1 12/7 edition I believe and works like a charm...thought I had a battery problem because it wouldn't charge right it would take forever. I didn't I jus had to stop oc/uv ...BTW using the kernel that came with the rom flashed using cwm recovery from cm10 which was on jb not ICS and works fine little bugs here and there such as attempting to open incognito window fc browser the battery read when phone was off was inconsistent versus when the device is off but other then that KitKat is great if I can help anyone I'll be more then glad to I don't mind helping people that don't know I don't give attitude and noon user friendly,after all I was there once....besides all the guys who really know what thier doing are busy creating Roma and tweakimg programs to keep us happy let's make it a little easier on them like I said I don't know everything but I have some knowledge and if I'm able to point you in the right direction without wasting your time I will

easyrider77 said:
I have an EL29 direct boot zip file that works with agats and even the newer cwms to flash back to.
I've tested it on the following recoveries and not had an issue at all:
agats (both 1.3 and 1.4), stock twiz, and the latest CWM they are useing.
I have gone to el29 direct boot with all of the above and had no issues, it goes into el29 recovery just fine.
DO keep in mind though I made this zip mainly for flashing into roms, not as a stand alone kernel, so you may have issues wif you use this as your standard go to kernel with the rom. Mst roms already have thier own kernel anyways, so that's normally not an issue, jsut so you are aware this is basically used for flashing roms not as the normal kernel.
I can host it on dev-host if anyone is interested, otherwise I won't bother.....and I ask because sometimes people just don't wanna be bothered, so I always ask......anyways let me know I will host it.
Just as a side note the steps I have done are as follows:
-reboot to recovery
-flash el29 zip file within said recovery (as I said I've tested this on all the above and it works fine)
-reboot recovery (it will be el29 now)
It should be back to the el29 recovery and you can flash from there.
Done this on hood pope (4.3), Viluminati (4.4 and 4.4.1 KitKat), cm10.1 (4.2.2) and stock Twiz rooted (not stock Twiz recovery) but agats recovery 1.3 and 1.4.
Those that don't know how to activate the power button to select what you do is toggle up > down >up > down until it says something about it being activated, you can then just use power to select your option.
Click to expand...
Click to collapse
There's a tread that might use your assistance
Sent from my d710 using XDA Premium 4 mobile app

CM 4.4.1 build 2013-12-07
Hey guys...Been rocking this build for a month now with no real problems. Only a couple of things i have noticed and thought I would drop in and mention since I haven't heard about it talked about in the main thread or here yet.
1. Every once in a while I will be showing full 3g bars and wont connect to the internet (says "no connection") I have fixed this with just toggling off and then back on the Sprint Radio Toggle in the drop down window. The phone will then immediately connect after.
2. During the first 2 weeks the camcorder was working...now its just borked. Every time i try to use it, it will just freeze up (the camcorder) and then force close. Then the camera is also unresponsive after trying to use the camcorder. I have tried to clear catch and force stop but the only way to fix this is with a reboot.
SPH-D710 EL26.....flashed to Boost Mobile with working Hangouts MMS and SMS from day one (no fix)
Build; 4.4.1 2013/12/07
Everything else is just ROCK SOLID, and love this ROM.

adjday said:
2. During the first 2 weeks the camcorder was working...now its just borked. Every time i try to use it, it will just freeze up (the camcorder) and then force close. Then the camera is also unresponsive after trying to use the camcorder. I have tried to clear catch and force stop but the only way to fix this is with a reboot.
Click to expand...
Click to collapse
This Camera Fix worked to get my camcorder working perfectly. Have you tried it? http://forum.xda-developers.com/showthread.php?p=48620791&highlight=3a04f599232ee62c6b63a6e4f1d3f7d3#post48620791

You can uninstall the gallery app (using titanium backup)
Then download and install a different Kit Kat gallery app...(just search google, it's everywhere Lol)