Hello guys,
so I've seen others do this before, and I thought, I should be able to do that too I'm a computer geek by training, but never got very deep in Linux/Android hacking.
Anyways, I made a CWM-flashable zip out of the Odin package for the latest ICS for P7300. (PDA: P7300XXLQ6; CSC: P7300OXALQ6; "OpenAustria")
Odin package: (source sammobile)
info: http://www.sammobile.com/firmware/?page=8&view=8417
download: P7300XXLQ6_P7300OXALQ6_ATO.zip (from hotfile)
I initially flashed the Odin package on my tab, and kept all my userdata, user apps, and even my homescreens. But I came from official, odin-flashed P7310UELPB ICS for USA released 3 months ago (yes, that's wifi-only, but runs fine on P7300); so that may have an influence.
If you are concerned about the integrity of your device, I do recommend you install the Odin package, as it is straight from Samsung, so you can be assured not to suffer from the error injected by anyone else (not that I made any errors, mind you :angel: ).
CWM-flashable package: (by direct conversion from the Odin package - no modification, not rooted, nothing added/removed/altered)
downloads:
- ROM: P7300XXLQ6-ROM.fred-v01.zip (for links, see post #3)
- MODEM: P7300XXLQ6-Modem.zip https://www.sugarsync.com/pf/D6778724_7163149_619563
md5:
e16200b688b8f4e602448f76e78a7d27 P7300XXLQ6-ROM.fred-v01.zip
48f9d2b048c2416d84ecdfcea904a434 P7300XXLQ6-Modem.zip
How to install
- if coming from stock ICS or HC, I suspect only wipe /cache is needed. From any other ROM (like CM or AOSP) I suspect you need a /data wipe (warning: deletes all your application data; but not your /sdcard)
- flash from any CWM recovery (I tested only 5.1.2.6). Turn OFF signature validation, as these zips are not signed. It took about 3-5 minutes on my tab
- (ps: the updater-script was borrowed from a recent kallt_kaffe ROM, so it's pretty bog-standard Just added a few outputs to show progress)
Other info
- the Odin package also includes a newer bootloader. I don't know if it's essential to have that newer bootloader, but I can add it later.
- It may not be necessary to flash the MODEM, but I would recommend keeping the MODEM+ROM combination.
Optional additions & tweaks
- any root package should work. (Update: I recommend either v3.1.3 or 3.2 from the original developer of Superuser: http://androidsu.com/superuser/ )
- if you have rooting problems, first uninstall other root packages, including superuser/superSU updates from Market. There is an "unroot" procedure in the sticky on General forum.
- you can get voice-call mod by flashing these 2 from cwm
* P7300XXLQ6_ENABLE_VOICE_CALL.zip from suwandiapr - http://forum.xda-developers.com/showpost.php?p=35264752&postcount=36
* the I9103 modem - http://forum.xda-developers.com/attachment.php?attachmentid=1309125&d=1347032493
- if you hate the boot sound, remove/rename the /system/etc/PowerOn.ogg
- fix for system freezes: see FAQ link under "reading"
- fix for wifi: see tracid's thread linked under "reading"
- OCUV kernel: see AAccount's thread for A1 kernel (careful, some versions work only on stock, others work only on cm10/aosp versions. Use e.g. the well-tested 1.7.3; or the much less tested 1.8.3c. Read carefully his posts and know that custom kernel involves experimentation, trial&error and potential instability)
- attached to this post is a flashable zip to easily return to stock XXLQ6 kernel (or you could flash the who ROM again, if you want)
Interesting reading
A MUST: my FAQ regarding ICS issues (especially if you are first time upgrading from HoneyComb to ICS)
http://forum.xda-developers.com/showthread.php?t=1895496
tracid's thread - he had the first "stock" ICS for P7300 2 months ago (it required a heroic effort to pull the update from an OTA package, that was available on Samsung servers, but not being pushed out by Samsung). As such, his thread (and esp the first post) has lots of useful info for Stock ICS on P7300, gathered over last 2 months.
http://forum.xda-developers.com/showthread.php?p=31720406
Credits
for inspiration, for sharing, for a couple lines in the updater-scripts, for being great devs, or great modders, or for letting me think I can do this...
kallt_kaffe
tracid
suwandiapr
safariking
and others who posted info that I used to make this
Returning a favor?
PS: I use SugarSync cloud storage for sharing this file - and will keep it there as long as I can. Help me keep the file alive by creating your own SugarSync account with THIS link (we both get 500mb extra - but only if you install the app on computer or smart device): https://www.sugarsync.com/referral?rf=cw2yimm8cchga. I also spend 10 hours of my life making this conversion, most of it in the middle of the night, so that must count for something, right
Alternatively, hit thanks - it gives a warm feeling too
reserved by OP
screenshot attached, unfortunately xda resized it to 640x400
Update 2012-12-25:
I received twice the question "what is the difference between this and tracid's rom". (e.g. here
Both are stock ROMs from Samsung with no modifications. (tracid added root, busybox; but this can be easily added yourself on this ROM as well)...
tracid's ROM = ZSLP7, regional variation: Taiwan. Obtained by *manually* applying an OTA file found on sammobile, to the P7300ZSKK2 honeycomb ROM. Samsung never officially pushed out the ZSLP7 as far as we know; so it may have been an internal test build.
here = XXLQ6, regional variation: Austria; An official and distributed build, as far as we know.
Samsung is not releasing changelogs, so the actual differences are hard to find, other than the fact that different regions (have slightly different set of added application (e.g. kobo, Polaris, ...). XXLQ6 came with swype keyboard. Not sure if ZSLP7 came with that.
Most importantly, XXLQ6 has a more recent build date, and seems to be officially distributed, so one can *assume* it has more fixes.
initial hosting on sugarsync broken: files blocked because of a "Fair Usage" violation. Probably it broke the "10GB per day max download on Free accounts" limit that I was not aware about
For a limited time, you can get the files from my Adrive (no download limit, but only 10 concurrent downloads possible - links expire after 14 days) / links valid 2012-12-22 until 2013-01-05
ROM: http://www.adrive.com/public/BAMDga/P7300XXLQ6-Modem.zip
MODEM: http://www.adrive.com/public/srnfuF/P7300XXLQ6-ROM.fred-v01.zip (830 downloads until 2012-12-22)
User x24 has a mirror up -> see his post on page 3: http://forum.xda-developers.com/showpost.php?p=36135549&postcount=25
here are md5's in case anyone wants to mirror/verify.
48f9d2b048c2416d84ecdfcea904a434 P7300XXLQ6-Modem.zip
e16200b688b8f4e602448f76e78a7d27 P7300XXLQ6-ROM.fred-v01.zip
cheers, Fred.
PS: referral signup for dropbox - should you feel interested to give yourself and me an extra 500mb on dropbox: http://db.tt/g26Egj0
Thank You a lot for the upload because today is the second day that I try to download the Odin Package of this P7300XXLQ6 Rom... But without success... This Hotfile link is "out of ordrer" since 2 days...
Your "NON Odin package" is only around 400Mo and the Odin package is around 600Mo... Is it normal?
about smaller size... The odin package is poorly compressed. Also, it contains some 100mb stuff that does not get installed, at least not on my tab (these are mostly demo apk in a hidden.img - I can make them available, but as I said, they were not even installed on my tab)
Ok! Thanks! :good:
installed in on my P7300 tab just now and it's running okay. I did not do any factory reset. Just wipe cache, as stated in OP, coming from stock honeycomb. Um. But I always run into "Android is updgrading, optimising application 1/1" every reboot. is that normal?
UPDATE:
Upon installing the kk_root_ics.zip, tab won't respond after some seconds. I reflashed the rom and it responded fine again.
Optimizing apps is the message when creating the dalvik-cache for a deodexed APK. It should happen after initial install, and then again if you add apps through recovery or so. E.g. I got it (once only) after flashing root package, as this added superuser.apk.
Other than the ROM itself, what else have you flashed (the more exact, the better to diagnose)
Even if I didn't install from CWM, it always show the optimising app 1/1. I'll further check since I'm always trying to root my tab to no avail.
I tried flashing different ROOT.ZIP, including the link on OP, on CWM, and it ALWAYS hangs after some seconds after apps has been loaded. Opening an app right after boot will also end up the tab not responding.
I only flashed ROM+MODEM then reboot. Everything runs well. but whenever I flash a flashable cwm file to root the tab, that's when I experience the hang.
Update:
Tried to odin CF-Root, but failed. Got stuck on "Leave CS" thrice~ and stuck on 1/8 progress bar so I flashed the rom again.
Update 2:
I uninstalled SuperSU and Superuser from tab. I then flashed Stock Recovery (from here) via Odin. Flashed kk_root_ics.zip and booted okay. I found Superuser installed. But when I try to update binary, it says failed. I downloaded superSU, and it also failed to install the binaries.
haramizuki said:
Even if I didn't install from CWM, it always show the optimising app 1/1.
....
I tried flashing different ROOT.ZIP, including the link on OP, on CWM, and it ALWAYS hangs after some seconds after apps has been loaded. Opening an app right after boot will also end up the tab not responding.
Click to expand...
Click to collapse
See my FAQ. There's a bug in many stock Samsung ics, that mean that any application FC, leads to full OS hang. I made a fix for that....
As for the optimizing 1/1 on boot: might be a corrupted apk file on your data partition.
Full wipe/factory reset fixed it. I actually didn't have any backup because I accidentally hit the full wipe forgetting that it will wipe internal files as well. I installed rom via Odin since it's the only way coming from a full wipe. :thumbup:
Btw, Which do you prefer: Supersu or superuser?
sent from S2 running latest pa+dori ,unless stated otherwise ^^
Superuser serves me fine. I never tried superSu
not bad. So far 600 ROM downloads on the Adrive link
If you installed this successfully, let others know!
Will this work on the 7310, or will it freak out because there's no phone?
Sent from my GT-P7310 using xda app-developers app
upconvert said:
Will this work on the 7310, or will it freak out because there's no phone?
Click to expand...
Click to collapse
Until somebody tries, we don't know
However, why would you want to. There are recent enough ICS packages (e.g. on sammobile)
In theory, I somewhat expect it might work, and if it doesn't, should be easy to overwrite with p7310 ROM.
No promises, no warranty !
Sent from my HTC Desire using xda app-developers app
Was this the one you had suggested to me over on the a1 kernel thread?
Sent from my GT-P7310 using xda app-developers app
Sorry about that. Thought you had a p7300. The discussion on a1 v1.8.3 not working on stock, was with a mixed audience.
fred_be9300 said:
Sorry about that. Thought you had a p7300. The discussion on a1 v1.8.3 not working on stock, was with a mixed audience.
Click to expand...
Click to collapse
No prob, I just wanted to make sure I wasn't missing something. I really want a rom with working face unlock, so I think my only options right now are stock or the mostly stock discovery.
Sent from my LG-VM670 using xda app-developers app
If you are coming from cm10, do you need to flash modem.zip also? Also what version of cwm to use? Thanks
Sent from my GT-P7300 using xda premium
Related
I am posting this message in the developer section because I thought the developers of the various ROMs might want to know of problems that at least one user is experiencing.
The problems I have noticed include the loss of ADB access to the phone, Market freezing and doing reboots during updates and installs, and apps installed via Zips not showing in Market Downloads for updates.
It appears that the problem with the Market freezing during updates may have been caused by me doing multiple zips when in clockwork, for these tests I only did one zip each time and that corrected the problem.
I was experiencing a problem where ODIN would not recognize the phone after the DK17 ROM was loaded but I suspect that was due to going from one DK17 ROM to another because the process I followed below ODIN saw the phone each time.
The ADB not working and the zip apps not showing persist. My test plan and results for multiple ROMs are below...
My process...
- Use 3 finger salute to enter Clockwork Recovery
- Wipe 3 times
- Install from zip to [ACS] SyndicateROM 1.0.2 (Shuriken)
This ROM works well for me and does not experience any of the problems I have been having with DK15
- Reboot system and confirm proper operation
- Able to use ADB
- WiFi, 3G, and 4G working
- All Apps installed via Zip detected by Market
- Update of App (Using Google Maps) not hanging system
- Power down system
- Reboot phone into Download Mode
- Confirm Odin3 v1.61 sees the phone
- Remove battery for cold restart
- Use 3 finger salute to enter Clockwork Recovery
- Wipe 3 times
- Install from zip to desired ROM
- Reboot System
- Test ADB
- Test 4G
- Sign into Google
- Test Update of App (Google Search & Maps)
- Power down system
- Use 3 finger salute to enter Clockwork Recovery
- Install Zip of preferred apps
- Reboot System
- Check Market for Apps
- Attempt Update again
- Retest ADB
- Connect WiFi
- Test Wireless ADB
- Reboot phone into Download Mode
- Confirm Odin3 v1.61 sees the phone
- Rinse & Repeat for next ROM
The results:
[Stock Flash][Odin]Dk17 Extended 11/27/2010
-------------------------------------------------
Filename: DK17-Extended.rar
Note: Installed via ODIN and not using Clockwork
ADB - Device not found
4G - Worked (Fell asleep during download - Continued after waking back up)
Market Update - Installs worked with no problems
Zipped Apps - Not listed in market
Market Update x2 - Worked
ADB x2 - Device not found
WiFi - Worked
adbWireless - Worked
ODIN - Detected (Retest?)
[ACS] Froyo Build DK17 - Deodexed/Zipaligned/Rooted - No FC - 11/23
-------------------------------------------------
Filename: acs-dk17-signed.zip
ADB - Device not found
4G - Worked
Market Update - Worked
Zipped Apps - Not showing
Market Update x2 - Worked
ADB x2 - Device not found
WiFi - Worked
adbWireless - Worked
ODIN - Detected
Froyo Beta V1.0.2 Devsforandroid
-------------------------------------------------
Filename: Mammon_Froyo_Beta_V1.0.2.zip
ADB - Works!
4G - Works
Market Update - Worked
Zipped Apps - Did not show
Market Update x2 - Worked
ADB x2 - Worked
WiFi - Workd
adbWireless - Worked
ODIN - Detected
Froyo Beta V1.0.3 - Devsforandroid 11-27-2010
-------------------------------------------------
Filename: Mammon_Froyo_Beta_V1.0.3.zip
ADB - Device not found
4G - Works (but sleeps easy)
Market Update - Worked
Zipped Apps - Not shown in market
Market Update 2 - Worked
ADB x2 - No
WiFi - Started Freezing - Restart Cycle
adbWireless - Unable to test
ODIN - Worked
Quantum Rom v1.4 DK17
-------------------------------------------------
Filename: QuantumRomv1.4_signed.zip
ADB - Device not found
4G - Worked
Market Update - Worked
Zipped Apps - Not detected
Market Update 2 - Worked
ADB x2 - Device not found
WiFi - Worked
adbWireless - Worked
ODIN - Worked
Quantum Rom v1.5 DK17 [WarpSpeed Edition] [Updated 11/27]
-------------------------------------------------
Filename: QuantumRomv1.5.zip
ADB - Device not detected
4G - Worked
Market Update - Worked
Zipped Apps - Not listed in market
Market Update 2 - Worked
ADB x2 - Device not detected
WiFi - Worked
adbWireless - Worked
ODIN - Worked
VIPERrom [IMPact] (DK17 Kernel) 2.2
-------------------------------------------------
Filename: VIPERrom [IMPact] DK17 2.2.zip
ADB - Device not detected
4G - Worked
Market Update - Worked
Zipped Apps - Not listed in market
Market Update 2 - Worked
ADB x2 - Device not detected
WiFi - Worked
adbWireless - Worked
ODIN - Worked
This is extremely helpful.
I've experienced the Sleep issue mentioned with the two ROMs mentioned above as well the ziped apps update issue.
Thanks for putting the time in to compile this
PokrTom said:
[Stock Flash][Odin]Dk17 Extended 11/27/2010
-------------------------------------------------
Filename: DK17-Extended.rar
Note: Installed via ODIN and not using Clockwork
ADB - Device not found
4G - Worked (Fell asleep during download - Continued after waking back up)
Market Update - Installs worked with no problems
Zipped Apps - Not listed in market
Market Update x2 - Worked
ADB x2 - Device not found
WiFi - Worked
adbWireless - Worked
ODIN - Detected (Retest?)
Click to expand...
Click to collapse
Well first thing wrong is that this isn't a rom by normal standards, its an Odin flash sort like the official Releases and what you get on your phone natively.
Secondarly it's also using the same "rom" flashable as the ACS dk17 that k0nane made. Second thing wrong is there is no way to install this via clockwork.
Therefore it's not a rom, it's a stock as sprint wouldnt have given it to you more or less and shouldn't be treated as a rom but as a recovery point.
Nothing overtly special has been done with this Flash or with the ACS k0nane flashable. so therefore there is nothing to fix.
Figured i'd make this point as everyone seems to see something new on the forums and go ooo new wrong works great except....
Perhaps understanding what they are would be a touch more helpful than a biased self comparision, seeing as how i could do the exact same test and get different results because my phones is different(ie it doesnt suffer the gps bug a fair amount do)
but it is what it is....
Take it with a grain of salt and understand that your mileage may very.
PS: the market not seeing apps is a simple fixable thing that's searchable in the forum, while it can be corrected quite easily, it's not a flaw that it's missing, these are BETA not for public distro leaks.
art3mis-nyc said:
but it is what it is....
Take it with a grain of salt and understand that your mileage may very.
PS: the market not seeing apps is a simple fixable thing that's searchable in the forum, while it can be corrected quite easily, it's not a flaw that it's missing, these are BETA not for public distro leaks.
Click to expand...
Click to collapse
This.
And keep in mind that stock builds don't turn USB Debugging on by default.
Tabulating the results would get you an A+; it's kind of hard to make any sense of it right now.
...but I also strongly agree that all of this is very circumstantial. The mere fact that some people have _____ working and others do not means that whatever results you get will not always be repeatable.
Yeah... Why would you list adb device not found when you forgot to turn on usb debugging? lmao.
art3mis-nyc said:
Well first thing wrong is that this isn't a rom by normal standards, its an Odin flash sort like the official Releases and what you get on your phone natively.
Click to expand...
Click to collapse
I understood this. I included it in my testing in part, as a baseline, and also because if I had not, then if someone had been interested in the results they may have asked how it behaved for me.
Forgive me for being a Noob and providing the information I did. I thought that this was a development forum, where developer might be interested in what results some people were getting. It appears that if you are not part of the developing community then input providing results is not wanted. I will just keep my mouth shut and enjoy the fruits of their labor.
On that point, to all the developers out there who have put forth the great effort they have, I give my thanks.
PokrTom said:
I understood this. I included it in my testing in part, as a baseline, and also because if I had not, then if someone had been interested in the results they may have asked how it behaved for me.
Forgive me for being a Noob and providing the information I did. I thought that this was a development forum, where developer might be interested in what results some people were getting. It appears that if you are not part of the developing community then input providing results is not wanted. I will just keep my mouth shut and enjoy the fruits of their labor.
On that point, to all the developers out there who have put forth the great effort they have, I give my thanks.
Click to expand...
Click to collapse
It is not that "We developers are better than you." It is the fact that the tests you performed were not done properly.
For one; For adb to work, USB Debugging must be turned on. (And no it is not on in every ROM by default)
What the hell are zipped apps?
PokrTom said:
I am posting this message in the developer section because I thought the developers of the various ROMs might want to know of problems that at least one user is experiencing.
The problems I have noticed include the loss of ADB access to the phone, Market freezing and doing reboots during updates and installs, and apps installed via Zips not showing in Market Downloads for updates.
It appears that the problem with the Market freezing during updates may have been caused by me doing multiple zips when in clockwork, for these tests I only did one zip each time and that corrected the problem.
I was experiencing a problem where ODIN would not recognize the phone after the DK17 ROM was loaded but I suspect that was due to going from one DK17 ROM to another because the process I followed below ODIN saw the phone each time.
The ADB not working and the zip apps not showing persist. My test plan and results for multiple ROMs are below...
My process...
- Use 3 finger salute to enter Clockwork Recovery
- Wipe 3 times
- Install from zip to [ACS] SyndicateROM 1.0.2 (Shuriken)
This ROM works well for me and does not experience any of the problems I have been having with DK15
- Reboot system and confirm proper operation
- Able to use ADB
- WiFi, 3G, and 4G working
- All Apps installed via Zip detected by Market
- Update of App (Using Google Maps) not hanging system
- Power down system
- Reboot phone into Download Mode
- Confirm Odin3 v1.61 sees the phone
- Remove battery for cold restart
- Use 3 finger salute to enter Clockwork Recovery
- Wipe 3 times
- Install from zip to desired ROM
- Reboot System
- Test ADB
- Test 4G
- Sign into Google
- Test Update of App (Google Search & Maps)
- Power down system
- Use 3 finger salute to enter Clockwork Recovery
- Install Zip of preferred apps
- Reboot System
- Check Market for Apps
- Attempt Update again
- Retest ADB
- Connect WiFi
- Test Wireless ADB
- Reboot phone into Download Mode
- Confirm Odin3 v1.61 sees the phone
- Rinse & Repeat for next ROM
The results:
[Stock Flash][Odin]Dk17 Extended 11/27/2010
-------------------------------------------------
Filename: DK17-Extended.rar
Note: Installed via ODIN and not using Clockwork
ADB - Device not found
4G - Worked (Fell asleep during download - Continued after waking back up)
Market Update - Installs worked with no problems
Zipped Apps - Not listed in market
Market Update x2 - Worked
ADB x2 - Device not found
WiFi - Worked
adbWireless - Worked
ODIN - Detected (Retest?)
[ACS] Froyo Build DK17 - Deodexed/Zipaligned/Rooted - No FC - 11/23
-------------------------------------------------
Filename: acs-dk17-signed.zip
ADB - Device not found
4G - Worked
Market Update - Worked
Zipped Apps - Not showing
Market Update x2 - Worked
ADB x2 - Device not found
WiFi - Worked
adbWireless - Worked
ODIN - Detected
Froyo Beta V1.0.2 Devsforandroid
-------------------------------------------------
Filename: Mammon_Froyo_Beta_V1.0.2.zip
ADB - Works!
4G - Works
Market Update - Worked
Zipped Apps - Did not show
Market Update x2 - Worked
ADB x2 - Worked
WiFi - Workd
adbWireless - Worked
ODIN - Detected
Froyo Beta V1.0.3 - Devsforandroid 11-27-2010
-------------------------------------------------
Filename: Mammon_Froyo_Beta_V1.0.3.zip
ADB - Device not found
4G - Works (but sleeps easy)
Market Update - Worked
Zipped Apps - Not shown in market
Market Update 2 - Worked
ADB x2 - No
WiFi - Started Freezing - Restart Cycle
adbWireless - Unable to test
ODIN - Worked
Quantum Rom v1.4 DK17
-------------------------------------------------
Filename: QuantumRomv1.4_signed.zip
ADB - Device not found
4G - Worked
Market Update - Worked
Zipped Apps - Not detected
Market Update 2 - Worked
ADB x2 - Device not found
WiFi - Worked
adbWireless - Worked
ODIN - Worked
Quantum Rom v1.5 DK17 [WarpSpeed Edition] [Updated 11/27]
-------------------------------------------------
Filename: QuantumRomv1.5.zip
ADB - Device not detected
4G - Worked
Market Update - Worked
Zipped Apps - Not listed in market
Market Update 2 - Worked
ADB x2 - Device not detected
WiFi - Worked
adbWireless - Worked
ODIN - Worked
VIPERrom [IMPact] (DK17 Kernel) 2.2
-------------------------------------------------
Filename: VIPERrom [IMPact] DK17 2.2.zip
ADB - Device not detected
4G - Worked
Market Update - Worked
Zipped Apps - Not listed in market
Market Update 2 - Worked
ADB x2 - Device not detected
WiFi - Worked
adbWireless - Worked
ODIN - Worked
Click to expand...
Click to collapse
Your kidding right? Well for starters, if you want a Froyo build/ROM to work right, first thing you gotta do is flash DI18 FULL ROM using Odin, then re-install clockworkmod, then flash (if your goin to a DK17 ROM ) the DK17 modem, and pit. Then you boot into cwm and wipe/factory reset 3 times, then wipe cache 3 times, then factory reset once more, then wipe Dalvik, then flash DK17 ROM, let phone boot all the way until your media scanner stopes (usually about a minute or two ). Then power back off, then boot back into clockworkmod, and wipe data 3 times, then wipe cache 3 times, then wipe data once more, but this time, dont wipe Dalvik. Then re-flash DK17 ROM and let it boot all the way. And ONLY then, will you have a fully working phone with DK17. If your not wiping cache before every MOD you install, you got problems. If you restore data after install of DK17 ROM, you will prolly get problems.
Im not saying that this will GUARENTEE that you will not have any problems, but I am saying that THIS method has treated me WELL over the past year or so. If you are doing ANYTHING differently, then how do I, or any of the DEV's here, take what your saying, to be fact, meaning that their ROM's are defective? Or somethings wrong with their ROM??? Im not saying your lying, all im saying is perhaps you did/doing something wrong.... you can chew on that a while, lol..
Dameon87 said:
For one; For adb to work, USB Debugging must be turned on. (And no it is not on in every ROM by default)
Click to expand...
Click to collapse
We learn something new everyday. This was something I did not know/realize. My guess is that up until now the ROMs I had downloaded had USB Debugging on my default and so I had not connected those dots.
I had posted earlier that ADB had not been working for me with the DK17 ROMs and no one had responded that I needed to check if USB Debugging was turned on.
I now know that and will act accordingly.
Dameon87 said:
What the hell are zipped apps?
Click to expand...
Click to collapse
I placed a number of apps that I prefer to use into a Zip file, similar to the ROM files being provided, but only apps. Signed the zip, and then used clockwork to install those apps, saving me the time of downloading and installing all of them.
art3mis-nyc said:
Well first thing wrong is that this isn't a rom by normal standards, its an Odin flash sort like the official Releases and what you get on your phone natively.
Secondarly it's also using the same "rom" flashable as the ACS dk17 that k0nane made. Second thing wrong is there is no way to install this via clockwork.
Therefore it's not a rom, it's a stock as sprint wouldnt have given it to you more or less and shouldn't be treated as a rom but as a recovery point.
Nothing overtly special has been done with this Flash or with the ACS k0nane flashable. so therefore there is nothing to fix.
Figured i'd make this point as everyone seems to see something new on the forums and go ooo new wrong works great except....
Perhaps understanding what they are would be a touch more helpful than a biased self comparision, seeing as how i could do the exact same test and get different results because my phones is different(ie it doesnt suffer the gps bug a fair amount do)
but it is what it is....
Take it with a grain of salt and understand that your mileage may very.
PS: the market not seeing apps is a simple fixable thing that's searchable in the forum, while it can be corrected quite easily, it's not a flaw that it's missing, these are BETA not for public distro leaks.
Click to expand...
Click to collapse
True that!!!
PokrTom said:
We learn something new everyday. This was something I did not know/realize. My guess is that up until now the ROMs I had downloaded had USB Debugging on my default and so I had not connected those dots.
I had posted earlier that ADB had not been working for me with the DK17 ROMs and no one had responded that I needed to check if USB Debugging was turned on.
I now know that and will act accordingly.
I placed a number of apps that I prefer to use into a Zip file, similar to the ROM files being provided, but only apps. Signed the zip, and then used clockwork to install those apps, saving me the time of downloading and installing all of them.
Click to expand...
Click to collapse
If those aren't working; then you likely didn't make the zip properly. You have to have an update-script add the files either to /data/app or system/app respectively.
They also have to be in a proper format: example:
./
./META-INF
./META-INF/folders under it
./system
./system/app
./data
./data/app
And of course a properly made update-script (Copying the files to the proper directories.)
sniperkill said:
Your kidding right? Well for starters, if you want a Froyo build/ROM to work right, first thing you gotta do is flash DI18 FULL ROM using Odin, then re-install clockworkmod, then flash (if your goin to a DK17 ROM ) the DK17 modem, and pit. Then you boot into cwm and wipe/factory reset 3 times, then wipe cache 3 times, then factory reset once more, then wipe Dalvik, then flash DK17 ROM, let phone boot all the way until your media scanner stopes (usually about a minute or two ). Then power back off, then boot back into clockworkmod, and wipe data 3 times, then wipe cache 3 times, then wipe data once more, but this time, dont wipe Dalvik. Then re-flash DK17 ROM and let it boot all the way. And ONLY then, will you have a fully working phone with DK17. If your not wiping cache before every MOD you install, you got problems. If you restore data after install of DK17 ROM, you will prolly get problems.
Click to expand...
Click to collapse
Live and learn. I did post the process that I used, which did not involve all of the steps you listed above. I will follw what you recommend in the future.
sniperkill said:
Im not saying that this will GUARENTEE that you will not have any problems, but I am saying that THIS method has treated me WELL over the past year or so. If you are doing ANYTHING differently, then how do I, or any of the DEV's here, take what your saying, to be fact, meaning that their ROM's are defective? Or somethings wrong with their ROM??? Im not saying your lying, all im saying is perhaps you did/doing something wrong.... you can chew on that a while, lol..
Click to expand...
Click to collapse
Understood, which was why I listed the process I followed, that way some of what I did was there and may have shown where I may have made a mistake. Which has been pointed out to me earlier regarding turning on USB debugging. I do not expect any developer to take what I post to be a statement that their ROM is broken. I never said that anyones ROM was broken, I started the post saying that I thought the developers might want to know what one user was experiencing. I know that it could be something I did.
Dameon87 said:
If those aren't working; then you likely didn't make the zip properly. You have to have an update-script add the files either to /data/app or system/app respectively.
Click to expand...
Click to collapse
I am using an update-script and the applications themselves are being installed and are working, they just don't show up in the market as installed. Something that there must be a fix for since sniperkill referenced searching the forums for the fix, so I will do that and will hopefully find it.
PokrTom said:
Live and learn. I did post the process that I used, which did not involve all of the steps you listed above. I will follw what you recommend in the future.
Understood, which was why I listed the process I followed, that way some of what I did was there and may have shown where I may have made a mistake. Which has been pointed out to me earlier regarding turning on USB debugging. I do not expect any developer to take what I post to be a statement that their ROM is broken. I never said that anyones ROM was broken, I started the post saying that I thought the developers might want to know what one user was experiencing. I know that it could be something I did.
I am using an update-script and the applications themselves are being installed and are working, they just don't show up in the market as installed. Something that there must be a fix for since sniperkill referenced searching the forums for the fix, so I will do that and will hopefully find it.
Click to expand...
Click to collapse
Oh. That is because when installed from the market, the market sets information in the database that says it is installed. This likely will not be fixable by using a zip to flash a bunch of apps. I believe what sniper was referring to was market apps now showing up because of the fingerprint in the build.prop.
Dameon87 said:
Oh. That is because when installed from the market, the market sets information in the database that says it is installed. This likely will not be fixable by using a zip to flash a bunch of apps.
Click to expand...
Click to collapse
I looked for the apps installed via the ZIP because when I did the same think using the Syndicate ROM on 2.1 all of the apps installed via the zip file did show up in the market, so I had been looking for the same thing.
It was worth a try, I have 4 Android phones in the household (My Epic & 3 Heroes) and so I was looking for any way to make reinstalling apps easier.
Thanks to all who answered questions or pointed out where I made mistakes.
k0nane said:
This.
And keep in mind that stock builds don't turn USB Debugging on by default.
Click to expand...
Click to collapse
I'm runing the ACS buildand USB debugging is definitely not on by default. After I enabled it ADB works fine.
Good stuff though! Thanks for the useful info!
Sent from my SPH-D700 using Tapatalk
it will be in next build
pokrtom, thanks for the informative post its always good to see people giving feedback that isnt "zomg dis is teh suxz you broke wifis!!!" 950 times over.
This is the first time Ive seen someone else notice the 4g sleeping issue. I thought I was imagining it.
Any clues on what could cause it?
sniperkill said:
Your kidding right? Well for starters, if you want a Froyo build/ROM to work right, first thing you gotta do is flash DI18 FULL ROM using Odin, then re-install clockworkmod, then flash (if your goin to a DK17 ROM ) the DK17 modem, and pit.
Click to expand...
Click to collapse
If you're going to try and bash someone atleast do it right. If you're going to be flashing the dk17 modem then why the hell would you flash the di18 first? All the dk17 modem does is overwrite... so ummm nothing stays behind which means.. un-needed step. Anyways..
Why don't you people stop being assholes. He's merely trying to help out the community with his testing efforts.. yea maybe he did a few things wrong but he's new.. we all were in the same boat.
Give the new people a chance; the ones who arnt meant to be fall through the cracks.. whilst the others stand by and prosper..
agreed. although i might also say that going from rom to rom, i have noticed that i have needed to uninstall the epic drivers and reinstall them to get them to notice my phone. this is on my win7 bootcamp on my mac.
that being said, you might also do a little bit of searching and throw some other general errors in the mix, that way we can be sure and document what is a "rom" bug or a "froyo" bug. that way some of the developers will ease off your back a little bit.
for example, i havent been using sniperkills 30 step "getcha rom runnin right" method, just a simple 3f salute, wipex3, install zip, restore apps from mybackup pro (still have never gotten titanium backup working correctly on my epic) and voila call it quits. but i have noticed a constant keyboard wake every 5-10 seconds with the keyboard slid out. this is on every rom ive tried so im thinking its a froyo problem and less of a specific problem.
just saying, lets make this a project and not a "dear developer. your rom blows. love the community."
So, flashing Cyanogenmod7/MIUI on the SGS i9000 is an area covered in many, many tutorials to date. However, the vast majority of them are outdated or just downright confusing, this guide tries to make flashing CM7/MIUI as painless as possible.
DISCLAIMER: This guide is based on my personal experience in flashing CM7/MIUI and i take NO RESPONSIBILITY WHATSOEVER in whatever untoward happens to your phone and/or life if you follow this. Also, this guide is meant for the SGS I9000GT PHONE ONLY, other variants please do not follow this guide to the letter and download the appropriate files for flashing.
Edit: This guide can be used to flash MIUI roms as well, seeing as they share the same requirements of needing Froyo bootloaders.
MIUI roms available:
1.MIUI Official [MIUI.us]
2. Galnet MIUI [Galnet and team]
3. MIUI+ [Decalc and Mothatt]
4. fitMIUI [Andro!de]
5 Nothing Fancy [spasms]
Note that this is not an exhaustive list.
Okay, lets go
Now, there are 2 ways to go about flashing CM7/MIUI.
1. ROMmanager method.
-Simple, fast but thats another tutorial altogether
2. The ODIN + CWM flashing method.
- That's what this tutorials all about!
NOTE: For those who wish to pursue Method 1, rschenck has written a guide on it.
Okay, now for the tutorial.
Firstly, find out what firmware you are running. Gingerbread bootloaders are now able to run MIUI/CM7. These give better battery life and are thus encouraged.
Go to ->SETTINGS ->ABOUT PHONE and look at what Android/Firmware Version you are running. If you are on 2.3.x, please skip the conditional step, if you are 2.1.x OR 2.2.x, you have to upgrade your bootloaders to 2.3.x.
CONDITIONAL STEP: Upgrade to GB bootloaders. (FOR 2.1.X AND 2.2.X FIRMWARE VERSIONS ONLY, 2.3.X FIRMWARES PLEASE SKIP THIS SECTION.)
Go to EZboot page.
1. Go to that website and download the Gingerbread bootloaders.
2. Download Odin, if you haven't done so already.
3. If you don't have Kies, you would need Samsung Drivers, which you can easily find around this forum. I believe its a sticky somewhere.
4. Open Odin and put your phone in download mode before connecting it.
5. Set up Odin as per picture in the link provided(The gingerbread one)
6. Flash and wait for reboot!
/END OF CONDITIONAL STEP.
2. Acquiring CM7/MIUI.
CM7 users: CM7 uses the term Nightlies, which are actually so called "experimental" builds that are updated, well, nightly. Despite it being called experimental, most nightlies are actually stable for "everyday usage". So don't be scared to flash 'em!
So,
1. Download the latest(topmost) version of CM7 or the various MIUI roms. (Links above)
2. Transfer the .zip file onto your phone through ADB push or USB cable.
3. Make sure your phone is not connected to your computer or anything. You're almost there!
Third, Flashing time.
1. Boot into recovery mode using the following method.
(a) Phone off.
(b) Press in the following order: VOLUP, HOME, POWER.
2. Now you have to clean out your phone.
-Wipe CACHE
-Go into advance options, WIPE DALVIK CACHE
-Go into mounts and storage. FORMAT SYSTEM, DATA AND CACHE. (Three separate moves)
3. Go to 'Install zip from sdcard' and scroll to your CM7/MIUI .zip file.
Flash.
Wait for reboot. And. You are done.
Congratulations, you are now running CM7/MIUI.
For CM7 users: Go get GAPPs(Google Apps) for Android Market and other android apps. Stay updated by flashing updated Nightlies.
[Small expansion of guide] Flashing from MIUI
If coming from MIUI rom, and wishing to switch to CM7(or vice versa)
1. Download newest version of CM7(or MIUI, whichever the case) and place in phone.
2. Boot into recovery. Format Cache and System. Not necessary to format Data(will erase all apps) but is recommended for stability purposes. You can backup your apps using Titanium Backup or use the native backup app in MIUI.
3. Install from zip and choose the correct file. Flash it.
Done.
Please comment if this was helpful to you. And THANK if it helped you!
Credits:
codeworkx - http://twitter.com/codeworkx
coolya - http://twitter.com/dumdidum
guiper -http://twitter.com/guiperpt
-All for CM7
nitr8 - For EZboot
rschenck - For his guide
And of course, myself for writing this.
Thank you, Very useful
mrsufgi said:
Thank you, Very useful
Click to expand...
Click to collapse
Thanks glad it helped
slotteh said:
Now, there are 2 ways to go about flashing CM7.
1. ROMmanager method.
-Simpler, faster BUT requires premium version of ROMmanager(purchasable in market)
Note: Premium version not required but that's another tutorial altogether.
Click to expand...
Click to collapse
I know this is supposed to be the definitive non-confusing guide, but I started reading your guide and 10 secs into it, you've posted confusing info:
info 1 - you state this first method requires PREMIUM ROMmanager
info 2 - in the very next sentence you state 'PREMIUM version not required"
After reading the rest of your guide, I have to conclude that it's just as - if not more than - confusing as other 'user guides' found in these forums. Your guide is only suitable for people who have learned by trial and error and are already comfortable with the nuances of wiping and flashing their phone.
Experienced users like myself have done it so many times I could do it with my eyes closed now, so I already know how to avoid missteps even if given incomplete, misleading or outright contradictory instructions, which your guide is full of.
I wish I had the time to go through the errors with a fine toothed comb, but I honestly don't at the moment (@work). That said, this guide either needs a complete re-write to improve readability and logic flow, or just be removed altogether.
evilsopure said:
After reading the rest of your guide, I have to conclude that it's just as - if not more than - confusing as other 'user guides' found in these forums. Your guide is only suitable for people who have learned by trial and error and are already comfortable with the nuances of wiping and flashing their phone.
Experienced users like myself have done it so many times I could do it with my eyes closed now, so I already know how to avoid missteps even if given incomplete, misleading or outright contradictory instructions, which your guide is full of.
I wish I had the time to go through the errors with a fine toothed comb, but I honestly don't at the moment (@work). That said, this guide either needs a complete re-write to improve readability and logic flow, or just be removed altogether.
Click to expand...
Click to collapse
Alright thanks for the feedback. It's the first guide I've tried to write so I think I've messed up a lot probably. I'll definitely try to re-write it. But thanks for the criticism.
Also, you've identified one area where I'm not very clear(ROManager part) and thanks for that. Do you have other specific examples of my post which are error-filled so that I can work on them? I want this thread to work. Thanks again
Have updated and removed contradictory statements.
Is it wrong this passage ?
1. Download the latest(topmost) version at : http://insanity.rollus.net/EZbase/img/sc/ezodin.png
Lord Style said:
Is it wrong this passage ?
1. Download the latest(topmost) version at : http://insanity.rollus.net/EZbase/img/sc/ezodin.png
Click to expand...
Click to collapse
Yes it is. Thanks very much for the spot
Edit: Edited it already. Thanks again
Thanks to slotteh for this guide.
Now I have CM 7 Nigthly 15 in my phone.
Stable cm7? Not for the sgs
Sent from my GT-I9000 using XDA Premium App
Mothatt said:
Stable cm7? Not for the sgs
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Yeah i've been a little confused looking for it. I'll edit it.
slotteh said:
Yeah i've been a little confused looking for it. I'll edit it.
Click to expand...
Click to collapse
@slotteh
one more MIUI rom, you may want to update your OP
http://forum.xda-developers.com/showthread.php?t=1184066
krarvind said:
@slotteh
one more MIUI rom, you may want to update your OP
http://forum.xda-developers.com/showthread.php?t=1184066
Click to expand...
Click to collapse
Thanks will do
Updated to include GB bootloaders flashing
what recovey do i need to install cm7 as it doesn't say or how do i install with odin
Are you sure if it's safe to flash MIUI rom with GB Firmware on every single one of the roms? I'm really considering fitMIUI, any suggestions?
Thanks for a nice guide.
bootloader
How i can flash only a new bootloader without lose all data?
Revise?
This section is not clear...
"Go to ->SETTINGS ->ABOUT PHONE and look at what Android/Firmware Version you are running. If you are on 2.2.x, please skip the conditional step, if you are 2.1.x OR 2.2.x, you have to upgrade your bootloaders to 2.3.x. "
I think this is a 'contradictory' point...
Otherwise, if this was a little proof-read, could be a dang good guide.
F x
Hi sorry for all late replies, have been a little busy, you may already have gotten answers to these but still,
got-petrol said:
what recovey do i need to install cm7 as it doesn't say or how do i install with odin
Click to expand...
Click to collapse
You need Clockworkmod Recovery and unless you're coming from a stock rom, you should already have this.
In either case, onstallation of EZbase from odin has been covered pretty well here: http://forum.xda-developers.com/showthread.php?t=1089989
It's really simple to follow, just make sure you have a full battery while flashing via odin.
So you’re a N00B with a brand new Android device, and you have no idea what all this sbf, adb, bootloader talk is all about; you just want to know how to do cool stuff with your new phone and be as cool as all of us Senior Members
Well here’s a Atrix N00B Guide just for you that will hopefully be a good jumping off point for you to start exploring and getting into the world of themeing, ROMing, flashing, etc. Most of this stuff was pulled from various XDA forums, and is easy enough to find, if you just take the time to search for it, but being the nice N00B friend that I am, I thought I’d try and compile most of it one place. So here goes…
*If you can’t figure something out or need help with whatever your particular problem may be, before you go cluttering up the forums with your problem and you get blasted by Senior Members like me use the SEARCH bar at the top of each section and/or thread. I promise you, you are not the first person to have your problem, and more times than not, your problem has been answered more than once. People HATE seeing questions that were just answered one or two pages previously. SO USE THE FREAKING SEARCH BUTTON!!!
*NOTE: Most of the following links are going to be for U.S. AT&T based phones only. Sorry, but that’s what I have and that’s what I know. Most of you BELL & other international guys should find some of this useful though, and most of the links below also have a international build version now.
CLICK HERE FOR UPDATES
Lets start with some basic terminology & general understanding:
What is Root / Rooting?
Put simply, Rooting your device allows you, and/or rooted apps, to access parts of the Linux based Android software that is your OS, and that you would otherwise not be able to access. These tasks can be as simple and beneficial as backing up your system setting, or as complicated as installing custom ROMs, Kernels, etc. (more on this later).
What is a Motorola .SBF file?
SBF stands for Single Binary File, and contains a firmware image that can be installed on your device. i.e. they are more of less what you are installing on your device when you do a OTA (over the air) update; except an actual .sbf file that you download and flash on your own will most of the time not only contain the updated info. in the OTA, but also all the other “stock” info. that came with the device. That’s why when you flash a .sbf file it will return you to a stock/retail device.
What is ADB?
ADB = Android Debug Bridge. So what this basically is, is a command/terminal based interface you can run from your PC, to interact with your device and its file structure. You can PUSH (install) programs, apps, .apk files, etc. to your device, move things around, set permissions, etc. One of the primary things to remember when trying to use adb, is that you need to enable debugging on your device. In fact it’s a good idea to enable this, and leave it that way… forever! This setting can be found on your device under Settings -> Applications -> Development -> USB debugging
Here is a list of helpful adb commands:
http://android-dls.com/wiki/index.php?title=ADB
What is a ROM?
A rom is like a custom firmware image that is made by a Developer either entirely from scratch, or based off of the official firmware package. Some ROMs contain simple changes like changing icons and adding extra options to things, other more complicated ROMs can change the entire Android experience. Which one you will want to flash, will be entirely up to you. Read carefully, and make sure you understand what you are getting into before you flash.
What is a Kernel?
As a rule of thumb, if you have to ask, you probably shouldn’t be messing with this anyway. But hey, best for you to at least know what it is. A kernel is the heart of the device's OS. In simplest terms it’s a connection between your apps and your device’s hardware; i.e. the processor, RAM, etc. A custom kernel can dramatically change the way your device’s hardware performs… for the better and/or the worse.
What is a Bootloader?
The bootloader is a program code that is executed before the device OS starts up, and that instructs that device to boot “normally”. The bootloader can come locked or unlocked from the manufacture. A unlocked bootloader will allow you to install custom ROMs & Kernels (as well as some other neat things) on your device.
What is a odexed and de-odexed framework, and what is the difference between the two?
Just read this:
http://www.addictivetips.com/mobile/what-is-odex-and-deodex-in-android-complete-guide/
What is CWM Recovery (ClockWorkMod Recovery)?
CWM is a custom recovery program that allows you to backup / restore a full or partial system backup of your device. It also allows you to install flashable .zip files; which is one of the primary installation methods for custom ROMs. It also provides other neat features such as cache wiping, battery reset, and other processes. Long story short, if you are thinking about flashing custom ROMs or just want a really good backup program, incase you FUBAR your device, you need to install this.
What is Fastboot?
Again, just read these for description & helpful Commands:
http://forum.xda-developers.com/showthread.php?t=619153 [Thanks briggie108]
or
http://android-dls.com/wiki/index.php?title=Fastboot
What is all this CM7 stuff about?
CM7 stands for CyanogenMod v7. It's a very popular ROM, b/c of its built-in options, great enchantments and total removal of manufacture software; i.e. all that MotoBlur stuff on your device is gone. It is a stripped down fast and well designed ROM with a custom kernel, that allows for easy flashing of great custom themes (just check out the General Theme Section for Android on XDA). Only a small selection of Android devices have a "official" release of CM7, however almost all Android devices have a "un-official" port for it. The Atrix 4G port is currently in its pre-beta stage and is being worked on by the Atrix Dev-Team.
More info. on CM7 can be found here:
http://www.cyanogenmod.com/
And here:
http://en.wikipedia.org/wiki/CyanogenMod
The #1 rule of CyanogenMod is that you do not ask for timetables!!! You have been warned. If you choose to ignore my warning, ask away and prepare to be blasted until you cry.
Information on the current status of the Atrix 4G port of CM7, as well as a list of current bugs, can be found here:
https://code.google.com/p/atrix-dev-team/
CM7.1 Beta for the Atrix is Available Now!!!
Information, install instructions, etc. can be found here:
http://forum.xda-developers.com/showthread.php?t=1257574
CM7 Nightlies Now Available for the Atrix (a.k.a. Olympus)
*Note: Nightly builds may be unstable, and are unsuppoted by the Dev Team.
http://download.cyanogenmod.com/?device=olympus
Nightly change log can be found here:
http://cm-nightlies.appspot.com/?device=olympus
The current version of CM7 for the Atrix does not yet support the following:
- Webtop
- Fingerprint Scanner
- Pocket Detector
- Horizontal HDMI Mirroring
MY CYANOGENMOD INSTALLATION GUIDE:
http://forum.xda-developers.com/showpost.php?p=19986512&post=234
Theme Chooser Themes for CM7 (200+):
http://forum.xda-developers.com/showthread.php?t=1167075
*Please make sure to search the thread before you post an already answered question. Also, if you have the $ available, please consider a $donation$ to the Atrix Dev Team for their continued hard work (remember, this is still beta, they're still working hard at it).
ATRIX (4.5.91 FIRMWARE) HOW TOs:
Here are some How To Guides that may be helpful to new Atrix 4G owners that have just got thier phone & have the most recent firmware = 4.5.91 (Android 2.3.4). Read each How TO carefully and completely before attempting. If you are unsure of what to do, or how to do it, ask a question first. I will try a put this is a order that somewhat makes sense.
HOW TO FLASH A SBF:
WARNING: If you are on Android 2.3.4 (4.5.91) w/ a unlocked bootloader, do NOT flash back to a earlier sbf version. DOING SO WITH BRICK YOUR DEVICE!!! Use CWM Fruitcake described below instead.
SBF Hints, Tricks & Guidelines:
- Always make sure to flash with a full battery! The last thing you want to do is run out of juice in the middle of a sbf flash; that's a great way to brick your device.
- As a general rule of thumb before flashing a sbf file to your device, you should always download the sbf file to a file path on your computer with the least possible spaces (i.e. the shorter the file path to the sbf file the better). So just download it to the root drive of your computer, such as C:\.
- Also, because these sbf files are so long, this sometimes causes problems with RSD Lite (the program you use to flash the sbf to your device). So, I would suggest you change the file name to something short, like OLYFR.sbf. It doesn’t so much matter what you name the sbf file, just so long as it’s short, does not contain any spaces in the name and you do not change the .sbf file extension. This will help prevent errors when trying to flash (no, I don’t know why, it just does).
- If you are running Windows on your PC, open RSD Lite as a Administrator. Also, when you open RSD Lite, Instead of browsing for the sbf file via the normal “…” button in the program, just drag the sbf file onto the file path bar in RSD Lite. Sometimes, the sbf file will not load when you select it via the browser button in RSD Lite (again I have no idea why).
- Once your sbf file begins to flash to your device, be patient… the device will re-boot at least a couple times in the flash process. Do not get jumpy and disconnect your device until RSD Lite says you are 100% done! Doing so can cause your device to BRICK! If for some reason you have waited for an inordinate amount of time, and it does not say finished, then ask for help on the thread, before unplugging. The same goes for pulling the battery. DO NOT DO THAT!!! Pulling your battery during a sbf flash, is one sure fire way to brick your device. Only pull the battery as a last resort and only after you have asked for help.
- RSD Lite has been updated to v5.3.1, here is the download link:
http://www.mediafire.com/?zz81vf1o2y73d4n
or
http://www.datafilehost.com/download-33dce367.html
STEPS:
1) Have the correct Motorola drivers installed for your PC (i.e. x32-bit or x64-bit).
2) Download RSD Lite (Links above) & install on your PC.
3) Choose a sbf file to download and flash from Motorola Atrix Firmware Super Thread: http://forum.xda-developers.com/showthread.php?t=1125944
If you are currently running firmware 4.5.91, I suggest that you only flash back to this firmware version. Flashing back to a eariler sbf/firmware version may have unintended consequences, the most serious of which is bricking your device.
*Note: U.S. AT&T users should only flash AT&T sbfs, internationl users should only flash their particular sbf versions.
4) Read the above sbf hints, trick, etc. to help prevent RSD Lite problems/errors.
5) Open RSD Lite and load the sbf file that you downloaded.
6) Put your device in RSD Protocol Mode by powering OFF, and upon powering back ON, hold both the power button and the volume UP button. Device should now say "Entering RSD Protocol Mode."
7) Connect your device to your computer via the usb cable, and select your device by clicking/highlighting it in RSD Lite.
8) Select START in RSD Lite and let the sbf flash process fully complete before disconnecting the device from the PC. There will be several reboots and the process make take 5 - 10 minutes to complete a FULL sbf flash.
9) If you have any errors or problems as a question, prefably in the Q&A section.
*Note: After unlocking your bootloader and installing a CWM (*see below), you have the option to flash stock sbf files named "Fruitcakes" that do not require RSD Lite to flash (see information below).
HOW TO UNLOCK YOUR BOOTLOADER FOR ANDROID 2.3.4 (FIRMWARE 4.5.91):
WARNING: If you are on Android 2.3.4 (4.5.91) w/ a unlocked bootloader, do NOT flash back to a earlier sbf version. DOING SO WITH BRICK YOUR DEVICE!!!
Try the automated scrpit in this thread: http://forum.xda-developers.com/showthread.php?t=1182871
or
Try the original unlock method in the Main Pudding Thread: http://forum.xda-developers.com/showthread.php?t=1136261
*Use the instructions on this page for this method: http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader]
Directions are in the respective OP
HOW TO ROOT YOUR DEVICE ON ANDROID 2.3.4:
One Click Root For Motorola Phones Running Android 2.3.4:
http://forum.xda-developers.com/showthread.php?t=1255548
Alternative Root Methods:
Follow the instructions in this post:
forum.xda-developers.com/showpost.php?p=15872818
or
These Instructions:
http://briefmobile.com/motorola-atrix-4g-root
*Note: Many of the ROMs you may wish to install, after your boot loader is unlocked, will also include a ROOT package. Check the indiviual ROM OP to make sure though.
HOW TO INSTALL CWM RECOVERY ON 2.3.4:
CWM Options:
With 2.3.4, you now have 2 different options available for CWM Recovery. You should have a unlocked bootloader, be rooted and be on Android 2.3.4 (firmware version 4.5.91), before attempting to flash any of these. Each is described below.
Option 1: RomRacer's CWM
http://forum.xda-developers.com/showthread.php?t=1204500
- This CWM is extremely stable & has multiple features, such as the ability to choose whether to backup the webtop portion of your device, or not. It supports both ext-sd (micro sd card) and internal sd (internal storage). You can also choose from a variety of colors & supports both U.S AT&T and International users. This CWM will also be the official CWM of CM7 ported by the Atrix Dev Team.
- I personally prefer this CWM as it also works with ROM Manager (app from the market - *see details below).
*Note: If you do not have any CWM Recovery installed yet, you can use the fastboot commands in the OP (use the non .zip version to install via fastboot), or you can install via ROM Manager with the below instructions.
*Note: If you already have a different version of CWM Recovery installed, and want to switch to RomRacer's, then first check to see if a file labeled "install-recovery.sh" @ /system/etc/. If the file is there, delete it, before proceeding with the install of RomRacer's version.
Install Instructions to Use RomRacer's CWM w/ ROM Manager APP:
1) Download the ".zip" file of your color choice (make sure you choose the right version AT&T or international), and place the .zip file on the sd-card (internal storage).
2) Download ROM Manager from the Market (paid or free, it doesn't matter) and install app.
https://market.android.com/details?id=com.koushikdutta.rommanager&hl=en
3) Open ROM Manager and select "Flash ClockworkMod Recovery," making sure to select the right device (i.e. Atrix 4G). This will flash the current version of CWM to your device, which will also work (see details/limitations discussed below).
4) Now, choose "Install ROM from SD Card", and choose the .zip file that you saved on your internal storage. You should not need to delete any of the cache options. ROM Manager will reboot the device into CWM and flash the .zip automatically, and then reboot again.
5) You should now have RomRacer's custom CWM installed over the ROM Manager version. You can now select Reboot into Recovery from ROM Manager, and it should boot into CWM Recovery.
Option 2: ROM Manager's Stock CWM
https://market.android.com/details?id=com.koushikdutta.rommanager&hl=en
- For install instructions, see steps 1-3 under the RomRacer's CWM.
- Allows for easy CWM updating, as well as ROM updates that are posted by the developer on ROM Manager's servers.
- Current build much better, and allows for both internal & external sd installs/backups.
HOW TO INSTALL FRUITCAKES ON 2.3.4 (GREAT SBF/RSD ALTERNATIVE!!!):
If you have a unlocked boot loader and CWM Recovery installed, and you wish to go back to "stock" you now have a wonderful alternative called Fruitcake. The fruitcake files are essentially stock sbf files that bypass the need to use RSD Lite; they flash via CWM just like any other .zip file that you flash. This is very welcome as it eliminates the need for RSD Lite and the problems associated with it.
You can find your Fruitcake here: http://forum.xda-developers.com/showthread.php?t=1163009
WHAT DO I DO IF MY DEVICE WILL NOT FULLY BOOT??? (i.e. Boot Loop or Soft Brick):
- If you have a bootloop/softbirck after atempting to unlock your bootloader:
a) If you flashed the unlock .sbf, are you sure you booted into fastboot and issued the "fastboot oem unlock" command.
b) If you happen to have a 2.3.4 ROM saved on you device, or a Fruitcake.zip, try booting into Android Recovery and reflashing. Make sure to wipe dalvik cache, cache partition, and format data first though.
c) If you can boot into fastboot, you can fastboot flash the "stock" 2.3.4 Gingerbread .img/system files by following the instructions on this page:
http://forum.xda-developers.com/showthread.php?t=1163342
*Note: The .img files to install via fastboot are located under "Download Gingerbread Stock Images" on the download page.
- If you have bootloop/softbrick after attempting to flash a ROM or Kernel:
a) Did you download the correct version of the ROM or Kernel for your device (i.e. US AT&T vs International).
b) If you're installing a new kernel, did you flash back to the stock kernel first, before trying to flash the different kernel.
c) Are you sure you wiped the dalvik cache, cache partition & formated the data (i.e. The Big Three) before installing the ROM. For a kernel install, just wipe dalvik cache & chace partition.
*Note: If you are using the stock ROM Manager CWM version, then you need to fastboot wipe for fomating data, as this feature does not yet work on ROM Manager. Fastboot command: "fastboot -w".
d) Try re-flashing ROM, after making sure you did the above 3 correctly... still not working, you can hopefully still:
1) Flash a Fruitcake in CWM to give you a clean install. Make sure to wipe "the big 3" first.
2) Can't get into Android Recovery/CWM, try flashing the stock Gingerbread .img files via fastboot. Instructions here:
http://forum.xda-developers.com/showthread.php?t=1163342
The 2.3.4 (4.5.91 Firmware) Section:
Updated ROMs, Kernels, etc. for 2.3.4 (firmware 4.5.91) --- UPDATED 8/14/2011
So with the official release of Gingerbread 2.3.4, a host of new ROMs & Kernels have been released for the Atrix, along with various fixes and mods for those ROMs & Kernels. I'll try and cover the most common ones below, as always if you feel something needs to be added, just let me know.
*Note: Before flashing any of these make sure that you:
1) Have a unlocked boot loader:
http://forum.xda-developers.com/showthread.php?t=1136261
2) Have CWM installed
3) Understand Fastboot/moto-fastboot commands
ROMs & Kernels:
FYI:
Before installing any ROM or Kernel I suggest you do the following to help prevent error, boot-loops, etc. Also, it's a good idea to flash a new ROM or Kernel on a fully charged device:
1) Download which ever ROM or Kernel you plan on flashing and have the .zip on your device ready to flash.
2) Backup your apps (not system data), contacts, etc. Also consider making a CWM backup of your device, just in case.
3) Boot into CWM Recovery
4) Wipe Dalvik Cache (under advanced in CWM)
5) Wipe Cache Partition
6) Wipe data/factory reset
6a) If you're using ROM Manager/CWM you will need to reboot the device after step 5, and upon reboot enter fastboot mode and enter the command: "fastboot -w" or "moto-fastboot -w" if you prefer using moto-fastboot. Then type "fastboot reboot" and upon reboot make sure to enter Android Recovery again, so that you can flash the ROM/Kernel.
7) Install .zip from SD Card (choose the .zip you wish to install)
8) If you installing a radio, theme, kernel, etc. on top of a ROM, I would suggest redoing the whole wipe process again between flashes.
9) Reboot the Device
- If you get a boot loop, try entering Android recovery and re-wiping the chace and data, and perhaps try reflashing the ROM/Kernel. Or if you made a CWM backup, you can always restore that.
ROMS
Stock Gingerbread 2.3.4 (Thanks KennethPenn):
*Note: This is useful if you need to return to stock Gingerbread. Both CWM & Fastboot install available.
http://forum.xda-developers.com/showthread.php?t=1163342
Home Base ROM (by Seanzscreams):
http://forum.xda-developers.com/showthread.php?t=1242721
This is a "stock" Android base ROM, with multiple versions ranging from almost stock with only a few tweaks, to a stock feel with multiple mods, extras, etc.
ASOP Atrix ROM (by Stinebd):
http://forum.xda-developers.com/showthread.php?t=1306550
ASOP = Android Open Source Project - - in other words, it's supposed to make your device as close to a stock Google Android device as possible (i.e. like a Nexus device).
*Note: since this rom is essentially a stock Android experience, many of the Atrix's stock features will not work; like the fingerprint scanner, webtop, etc.
Alien ROM & Theme (by KennethPenn):
*Note: The ROM is separate from the theme, which can be applied afterwards if you wish.
http://forum.xda-developers.com/showthread.php?t=1186537
This is a very stable ROM, however there are a few issues with the Theme portion. The Kernel is stock 2.3.4.
Ninja ROM (by SamCripp):
http://forum.xda-developers.com/showthread.php?t=1173843
Super fast ROM, with Faux123's Kernel included.
Cherry Pie & Pie Crust (by Navalynt):
http://forum.xda-developers.com/showthread.php?t=1189497
Includes optional themes and has a separate international build version.
Aura ROM (by Diviance):
http://forum.xda-developers.com/showthread.php?t=1186990
Includes Faux's Kernel
3 versions to choose from (de-bloat, de-bloat w/ accounts, & w/ all bloat)
DarkSide ROM (by Nottach):
http://forum.xda-developers.com/showthread.php?t=1222108
Includes Faux's Kernel
Multiple Mods available to add to ROM
Theme incorporates many apps
HoneyComb ROM/Theme (by Seanzscreams):
http://forum.xda-developers.com/showthread.php?t=1206767
Based off of Alien ROM w/ a Honey Comb Theme. Different versions are available for different kernel choices.
iBlur ROM (by Marko!):
http://forum.xda-developers.com/showthread.php?t=1305015
Like the look of the iPhone... but hate the iPhone. Give this ROM a try then.
StarWars Rom/Theme (by Seanzscreams):
http://forum.xda-developers.com/showthread.php?t=1200214
Ying / Yang ROM (by Shady_lanem):
http://forum.xda-developers.com/showthread.php?t=1244852
Nice black/white ROM, with all the latest tweaks, mods, etc.
KERNELS
Faux's Kernel (over-clocked @ 1.45 GHz):
http://forum.xda-developers.com/showthread.php?t=1156040
*Note:
- Froyo version, Gingerbread version & CM7 version, each w/ multiple versions avaliable; a enchanced stock kernel @ 1 GHz that allows undervolting, profiles, etc. Also a OC kernel @ 1.3 GHz & 1.45 GHz.
- Make sure you pick the right kernel; i.e. if you are on CM7, use a CM7 kernel, if you are using a Gingerbread based ROM, use the Gingerbread kerenl.
- The overclocked 1.45 GHz kernel may cause heat issues with your battery, thus causing random reboots... suggest undervolting.
Kholk's EternityProject Kernel (over-clocked @ 1.5 GHz):
http://forum.xda-developers.com/showthread.php?t=1153003
*Note:
- Current build based off of Faux's kernel.
- Kernel may cause heat issues with your battery, thus causing random reboots... suggest undervolting.
Clemsyn's Kernel (over-clocked @ 1.4 GHz):
http://forum.xda-developers.com/showthread.php?t=1354502
*Note:
- Based off of Faux's Kernel, but includes additonal optimizations.
- AT&T and CM7 versions available @ either 1.0 GHz or 1.4 GHz.
- B/C of memory timings, this kernel may not work on your device (like mine), and you will not be able to fully boot. Make sure you have a backup kernel to flash incase this happens to you.
OTHER MODS & FIXES:
V6 SuperCharger Script
My Instructions Here: http://forum.xda-developers.com/showpost.php?p=18906120&post=201
Battery Jumping Fix:
*Note: Charge battery to 100% (overnight) & wipe battery stats in CWM (under advanced) before flashing this.
http://forum.xda-developers.com/showthread.php?t=1174349
WEBTOP on 2.3.4:
http://forum.xda-developers.com/showthread.php?t=1169457
Native Tethering MOD for 2.3.4 (included in the above ROMs):
http://forum.xda-developers.com/showthread.php?t=1160452
All Atrix 4G AT&T Radios:
http://www.multiupload.com/G8T8IGZF05
2.3.4 Ported Boot Animations:
http://forum.xda-developers.com/showthread.php?t=1162936
OTHER HELPFUL THREADS:
How To Recover From A Soft Brick:
http://forum.xda-developers.com/showthread.php?t=966405
The Same Thing As This Thread (Posted in the Dev Section), Without All The Fluff:
http://forum.xda-developers.com/showthread.php?t=972423
Theming the Atrix 4G: tools, processes, locations, etc.:
http://forum.xda-developers.com/showthread.php?t=1060199
How To Port A Theme:
http://forum.xda-developers.com/showthread.php?t=1186819
How To Theme Gingerblur / Compiling & De-compiling a Framework (This is what got me started):
XDA Thread Here: http://forum.xda-developers.com/showthread.php?t=1101138&highlight=gingerblur
How To Here: http://briefmobile.com/how-to-theme-gingerblur
List of ROOT APPS available & working on the Atrix:
http://forum.xda-developers.com/showthread.php?t=1099846
A Whole Bunch of Icon Sets (for when you're ready to start customizing):
http://forum.xda-developers.com/showthread.php?t=824656
Widget Locker Themes:
http://forum.xda-developers.com/showthread.php?t=968613&highlight=D3S-L002
How to Manually Deodex Any Atrix ROM:
http://forum.xda-developers.com/showthread.php?t=1162764
Invaluable Resource:
http://gitbrew.org/android/
Terrific Info!
Great job as usual Swiftks!! It's always nice having everything in one place. Sometimes searching XDA can be frustrating with the amount of search results. This should help everyone, not just the noobs.
Good work.. Only way to be useful is its stickied so it isn't lost
Sent from my MB860 using XDA Premium App
Great post/thread, someone should sticky this... Maybe it will help reducing all the generic questions...
Might want to add asking for cm7/miui
Sent from my MB860 using XDA Premium App
Nice thread, just what i needed, i am new to the Atrix and i need all the help i can get. Cheers Dude
What a great thread. I am well versed in rooting and flashing my nexus one, even did some minor development for it. But this is a very useful summary for the atrix, and not everything is the same between devices. For example I had no idea what an sbf file was.
I'm glad this is helping some of you. I thought of a few more details I can add to the OP when I get home today... also, I'll see about trying to get stickyfied.
Sent from my MB860 using XDA Premium App
Swiftks said:
What is Root / Rooting?
Put simply, Rooting your device allows you, and/or rooted apps, to access parts of the Linux based Android software that is your OS, and that you would otherwise not be able to access. These tasks can be as simple and beneficial as backing up your system setting, or as complicated as installing custom ROMs, Kernels, etc. (more on this later).
Click to expand...
Click to collapse
You have made a great post that will help a lot of new people out. For rooting it would be helpful to add that all rooting does is give you the equivalent of the Administrator account, like in Windows.
For your fastboot/bootloader section. I always point new people to this:
http://forum.xda-developers.com/showthread.php?t=619153
Your link is pretty good. I like the one I posted as well. It is a little advanced, but it also has some added fluff for newbies.
Also some advice while flashing in general. Never ever do a battery pull unless you are absolutely 100% sure something went wrong and the phone is frozen. Some mods take a while to install, or the progress bar might not be coded in correctly. I have made some personal mods where the progress bar screwed up. After a couple minutes of freaking out, all of a sudden cwm goes "Ding, done!" so yeah patience is key.
I second that it should be stickied....
Very well written guide. Wish this guidewould have been here when I started flashing. Will be very helpful to the newbies coming to the atrix/xda. Good job.
Sent from my MB860 using XDA Premium App
Woow i feel like dev after reading this lol ^__^
thanks!!
GreAt thread! Question, was my post the one you are talk in about for the non-market apps enabled? I posted that just recently and worked like a charm. I was surprised that it did. It is ironic how an app from app store enables non market apps..lmfao. Great work on thread.
demandarin said:
GreAt thread! Question, was my post the one you are talk in about for the non-market apps enabled? I posted that just recently and worked like a charm. I was surprised that it did. It is ironic how an app from app store enables non market apps..lmfao. Great work on thread.
Click to expand...
Click to collapse
Yeah, I think it might have been.
Am Updating the OP now with some more info.
Sent a request to Mr. Clown for a Stick, and he said they he would do it... so hopefully this thread won't get lost for future noobs.
One thing though is instead of calling it the "noobs" guide? Why not just call it beginners guide cause the new people coming here are probably not gonna have any idea wth a noob is anyway! Great guide besides that though!
Gutterball said:
One thing though is instead of calling it the "noobs" guide? Why not just call it beginners guide cause the new people coming here are probably not gonna have any idea wth a noob is anyway! Great guide besides that though!
Click to expand...
Click to collapse
Makes Sense...
I was a total noob when I picked up my Atrix back in Feb. Proceeded to mess around with things and soft-bricked it. Took me a few days to seach for all of this information and finally get it back to stock. Thanks for putting it all in one spot!!
this just just great work dude.
Can you include a brief explanation about what CWM is?
Edit: Oops... I saw that you've already done this.
yay its stickied...good job man
I rooted my S2 a few days back... there is a lot of info in the forums but spread all over the place and it took quite a long time to find the specific answers to some of the questions i had. Thus I've done a short form guide to help anyone looking to root and give them a bit of extended background and *hopefully* reduce all the copy threads/posts in the forum.
NB/ I'm no android expert. Please don't flame if something i've said is wrong. Let me know/PM me and I'll change it. This is only meant to be high level info!
1. What is rooting?
http://en.wikipedia.org/wiki/Rooting_(Android_OS)
2. What are the warranty implications?
Warranty is void BUT you can return the phone back to *stock* (standard manufacturer ship state) so, as long as you don't bone anything in the root process you can get still get warranty returns.
3. What is [recovery]/[kernel]/[rom]?
Your samsung device memory is separated into different partitions to load different parts of the software to make you device work.
http://www.villainrom.co.uk/vBwiki/index.php/Glossary_of_Android_Terms
Typically you have the kernel partition which tells the device what to load on power on), you have the system partition where your ROM (main operating system is loaded) and you have the recovery partition which allows a user to access and write to the system partition (i.e. load custom roms).
Only difference on the galaxy s2 is that the kernel partition and recovery partition linked. What this means for you is that if you change the kernel, you also change the recovery.
4. What is stock [kernel][firmware]?
http://forum.xda-developers.com/showthread.php?t=1125282
Essentially the stock kernel is the original Samsung kernel shipped on the device (split into many different variants subject to location, sub model, carrier, date etc...) and firmware essentially is the kernel with the Samsung Rom.
5. My current kernel is KG*|KF*...n, can i install any other stock kernel? What are all the different stock kernels? Can I install one over mine?
http://forum.xda-developers.com/showthread.php?t=1075278
Yes you can use any Kernel from any country as long as it is for SGS2 with the correct hardware
Check the models are the same.
6. What's the difference between Cf-Root and Clockworkmod and which do i want?
CF-Root is simply a customised version of the clockwordmod recovery. It still functions the same but cf-root has it's own app for making direct recovery calls from within android as CF-root doesn't function with Rom manager, where pure clockworkmod recovery does work with rom manager.
As far as I'm concerned, it's a question of whether you want to use Rom manager really?
7. How do I root the samsung galaxy S2?
All I will say is..ENSURE KIES IS NOT RUNNING IN SYSTEM TRAY OR TASK MANAGER. KILL THE WHOLE PROCESSS TREE IF YOU FIND IT BEFORE DOING ANY ROOTING!
CF-Root http://forum.xda-developers.com/showthread.php?t=1103399
Clockworkmod http://forum.xda-developers.com/showthread.php?t=1118693
N00b guide http://forum.xda-developers.com/showthread.php?t=1126522
You can also use the root toolbox method for some stock firmwares without having to flash the recovery:
http://forum.xda-developers.com/showthread.php?t=1319653
8. What is superoneclick and what is odin? Where do i get them?
Odin is a flash utility to allow you to push a kernel to your phone from your pc.
Superoneclick is a flash app that will root your phone from your pc.
If you don't want to use superoneclick then simply flash an unsecured kernel (i.e. CF-Root) using Odin and you'll get root already.
Look in the kernel posts and you'll find latest versions there.
9. Can i still get OTA (over the air) updates to my stock rom eventhough I've rooted?
you can update via Kies and root again. Kies wont detect if your phone is rooted or not as long as you are on Stock firmware.
10. How do i get back to stock (as if nothing has ever happened to the phone/factory ship)?
http://forum.xda-developers.com/showthread.php?t=1075278
Flashing a full stock rom and kernel (firmware) using odin will remove everything.
11. What is this yellow exclamation mark and how do I get round it?
Whenever you access the download mode, and write a new kernel, your phone will know you've changed the kernel. The exclamation mark is simply a flag for samsung to easily know whether you've messed with the kernel on returns. You can easily get rid of it by using a jig OR re-flashing the stock kernel following an initial root...then re-flashing the zimage from the CWM image. - Jig is far easier and quicker though.
http://forum.xda-developers.com/showpost.php?p=14283369&postcount=2
12. What is the custom binary download counter and how can I restore it?
A counter living in the kernel to record the number of times you've changed the kernel. Only way to remove it is to get a usb jig...
13. What is a jig and what does it do?
it's a little usb plugin from ebay then puts the phone into download mode (even if you bricked a kernel update) resets the kernel counter and removes the yellow exclamation mark.
Simply boot off the phone. Plug it in. The screen will say something like 'Erasing boot information'...then unplug it and re-boot. Very simple.
A jig is a cheap and essential piece of hardware that everyone rooting should invest in!
14. What is download mode and what is recovery mode and how do I access them?
Recovery > enter recovery with the key combination of Vol Up + Home + Power
Download > Accessible on all phones, regardless of kernel via Vol Down + Home +
http://forum.xda-developers.com/showthread.php?t=1134290
15. What is deodexed|Odexed?
http://forum.xda-developers.com/showpost.php?p=16461907&postcount=2
http://www.villainrom.co.uk/vBwiki/index.php/Glossary_of_Android_Terms
16. Once rooted I can install custom roms, but can I overwrite the kernel?
Yes, so long as the kernel is compatible with the hardware and in some cases the rom.
17. I've rooted and put CF-Root XWKF(...n)...But I want to put a different kernel on and still have the CWM recovery?
Simply flash the CF-Root over the current CF-Root. However if you are updating a major version (i.e. CWM 4 to CWM 5) just check on CF-Root's thread first.
18. I've pwned my device? What do I do now?
Get a jig to put back into download mode and then flash the original stock firmware.
19. My device is sim locked and/or full of carrier apps? How can I get rid?
To get rid of carrier branding and apps simply flash a different firmware/rom that isn't branded from a carrier. See questions 4 and 5 above for lists of the different stock firmwares.
To get rid of the sim lock you have two options:
1. Root and then use one of the apps from market place (mixed success across the boards); or,
2. Extract some data from your phone in hex code and try and calculate the unlock code yourself.
I bought mine sim free so not done any of this but a quick scan of the forums turned up these two posts which may be useful.
http://forum.xda-developers.com/showthread.php?t=1207513&referrerid=2648941
http://forum.xda-developers.com/showthread.php?t=1064978&referrerid=2648941
20. What is a 'cooked' rom?
Cooked roms are just roms that someone has made based on the stock rom with slight high level changes. They are different from developed roms such as Cyanogen or Villainrom which receive significant low level modifications and developments.
Check out the Rom kitchen project which when released in stable version will allow you to build your own rom on the fly and select all the apps etc.. you want in it: brilliant example of the benefits of Android!
http://www.romkitchen.org/beta/index.php
21. What is CSC and how do i change my ROM CSC?
CSC = consumer software customisation. The file contains the software packages specific to that region, carrier branding and also APN settings for data connection, SMS, MMS etc...
Three ways to change it (NB it will wipe your device!):
1. Flash a multiCSC ROM and that use CSC Select from Market;
2. Flash a multiCSC ROM and type *#272*Device IMEI# into the dial pad and selecting the csc of your choice;
3. Flash a ROM using ODIN, then flash the desired CSC separately using ODIN.
22. Do you just install Rom over an existing?
Some people do and 9 times out of 10 it works, however I personally boot into recovery, wipe all data/factory reset and wipe Davlik cache > then power off > boot into download mode and install the new rom as above. Best way to ensure a 100% clean install.
23. What is the best way to go from Android 2.x to Android 4.x (Ice Cream Sandwich)?
I struggled trying to get Titanium to quickly and efficiently migrate my data (I'm sure it's very possible but I didn't have the time nor inclination to work around it) therefore I just restored my apps data after manually installing the apps from the marketplace. Once you have a stable working phone on ICS future titanium backup/restores are easy as normal.
24. Titanium Backup? What's the difference in app colour?
Menu => Legend;
Green = App - with data that you should backup;
White = App - should be fine to backup;
Red = System app/service - Wouldn't backup as typically installed by default.
Other tools apps that will be helpful are Titanium Backup (from Android Marketplace https://market.android.com/details?id=com.keramidas.TitaniumBackup&hl=en) and also get a Dropbox account (for free) from Free 2GB Cloud Storage from Dropbox as Titanium can sync to Dropbox.
25. Anything else of note?
Other tools apps that will be helpful are Titanium Backup (from Android Marketplace https://market.android.com/details?id=com.keramidas.TitaniumBackup&hl=en) and also get a Dropbox account (for free) from Free 2GB Cloud Storage from Dropbox as Titanium can sync to Dropbox.
Also slightly linked, if every you want a good UK based hosting for blogs/web/dev - I couldn't recommend TsoHost enough. They are the best hosting company I've ever worked with! Unlimited sql databases and PHP setting modification! If you want 10% off all hosting packages use the code 'wibbsy' at checkout!
Would not this be better in the General section .As a sticky even though noobs dont read stickies .
Witness a very similar Guide posted long time .
http://forum.xda-developers.com/showthread.php?t=1125282
jje
I welcome suggestions on how to move it and or make it sticky?
Sent from my GT-I9100 using XDA App
wibbsy said:
I welcome suggestions on how to move it and or make it sticky?
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
PM a Mod.
jje
This was exactly what I was looking for - thanks for this! I got my Galaxy S2 about 3 hours ago and now it's all rooted and awesome thanks to this guide.
You have been great help thnx man .
---------- Post added at 05:01 AM ---------- Previous post was at 04:59 AM ----------
Can you post a step by step guide as how to debrand the S2 ?
it will be very much appreciated.
Debranding is easy... just flash a rom that isn't branded. See q. 19.
New to xda. Thanks to threadstarter, really useful information for newbies like me.
great info there . keep up the good work.
thank you very much
Thanks
Just like to say thanks for this appreciate you taking the time to write this.
Nice one
I want to flash back to stock firmware, but after download from http://forum.xda-developers.com/showthread.php?t=1075278, instead of PDA, CSC and MODEM files, there were several image files (Power ISO). What to do with them? I desperately need to download stock firmware with MSR - CSC... Any help would be so appreciated!
Thanks. I think it is nice to have all the info in one post. Makes life easier.
Sent from my GT-I9100 using Tapatalk
thanks for the info!
Thanks dude for the very useful info.
Thanks for the info. Nice to have it all in one place.
i get its. thanks for guide
Thanks! Makes much sense!
Thanks for the summary! This have helped a lot for newcomers like me
+1. Very helpful.
CAUTION TO NOT LOOSE TWRP
I read two posts that say v21, now again on V8.5, put the stock recovery back instead of twrp. This is probably a side effect of a fresh stock /system and wipe of /data.
As a preventive step, when done flashing and wiping reboot to recovery FIRST, before booting the system It will allow recovery to handle removing the recovery-from-boot.p that flashes stock recovery.
I just patched the modified V7.4.2 up to the newly released 8.3 now 8.4. 8.5, 8.7,9.0 -V9.2 Patch
New update has been made from V17 to V21 of the non prime version of R1-HD, Non prime is behind on security patch (2017-05-05)
Copied ROM from phone and made twrp install ROM from it.
* No preloader change (official updates change the preloader to block your ability to use sp flash tools for rom flashing)
* No lk.bin change __ this part is what allows you to choose boot options(boot menu when power and volume pressed together)
* No "FOTA" app Fota has now been left in to make it easier to get next update, if that ever happens.
* No opera browser
* No adds (removed in the modified 7.4.2)
* Custom boot logo (only done on v8.3, there was no interest in this so abandoned)
--Newer versions of rom left stock, Leaving mods up to user.
** while it is not necessary to do a wipe with this ROM, I still recommend it.
**Thanks:
** @vampirefo needed his patched v7.4.2 in order to apply this new 8.3 patch and again for 8.4
** @ColtonDRG OR @jasonmerc I do not remember which one made it: For the image used in the custom logo
and the modified zip is here .
Roms are rootable with SuperSU, flashed in twrp after install. Must be done in systemless mode. In order to patch system veridy in boot.img
Logo update did not work on original rom changing link to updated version
BLU rolled v8.3 back to v7.4.2 because of app compatability issues. V8.4 is there fixed release. Both 8.3 and 8.4 are modified prime roms with ads stripped
V21 is the non prime update.
Unmodified V6.1
==>NON-ROOTED-logo-not-replaced-modified-V8.3
==>Fixed Logo modified NON_ROOTED V8.3
==>>modified V8.4
==>>modified V8.5
==>>Full with Ads V8.7
==>>Full with Ads V9.0
==>>Patch For V9.2 must be flashed on top of fresh V9.0
****Run debloat ==>script to remove ads if you need/ want to, or remove from zip before flashing ****
alt. manual example: before reboot, while still in twrp. Select mount and put checkmark next to system. Then run these two commands in adb terminal
Code:
adb shell rm /system/priv-app/com.amazon.*/com.amazon.*.apk
adb shell rm /system/app/Adups*/*.apk
==>>Modified V21
** stand alone logo installs
I flashed this but I didn't get the custom boot logo.
mendelgordon said:
I flashed this but I didn't get the custom boot logo.
Click to expand...
Click to collapse
I had that happen to my second phone too.
I don't have an explanation yet.
I even made a separate update.zip , that one didn't make the logo change either. I did eventually change it with sp flash tool.
I tried with both recoveries.
and multiple /dev location formats. and for whatever reason my one phone did not accept the logo change from recovery.
And the other test phone it worked.
mendelgordon said:
I flashed this but I didn't get the custom boot logo.
Click to expand...
Click to collapse
Neither did I but it all seems to be working fine
Been using this for about a day now, likewise no custom boot logo, but that's fine. Otherwise, it's been running super well. A lot better than the previous mostly stock version did for me with the bloatware APKs removed after the install. A lot of the general idiosyncrasies of the previous version of the stock rom seem to have gone away for me. It seemed to have weird storage management issues, errors moving to SD, broken symlinks that prevent apps from moving or being reinstalled, and a lot of other little non-storage issues, but so far, none off that here.
Long story short, good work! I hope we eventually see proper 7.x roms through some of the efforts going on, but in the meanwhile, your work here has made life a little bit better on 6.
It seems that I was able to get the logo.bin to update when I applied the original update patch, but not when I used the same line in the rom install.
It is no big deal that it did not work, I was just trying to make it look different at boot time.
edit:
I think i found the problem with the logo not updating.
i used the update-binary from the official patch update. (the one that allowed the logo to change the first time)
and it changes . so since the ROM seems to install the way it is , only the logo didn't flash I put it in a separate update.zip if anyone is interested in it.
EDIT 2:
clarification.
It was not so much the binary allowing the logo to change but the format of the partition location I had been using that needed that binary.
Further test had shown me that I could have used the binary I was using but just change the partition naming line
Code:
package_extract_file("logo.bin", "/dev/block/mmcblk0p9")
the above code works with the same update-binary as rom install
But I was using
Code:
package_extract_file("logo.bin", "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo")
Taken straight from the official patch, and thats why it needed the update-binary also.
I dont know what is different in the binary other than , major size difference.
The powered by me logo was just a test file to see changes in the logo.
**logo-update is same as composite but with alt updater-binary
**composite-logo screenshot is in op
**stock logo will return to original BLU logo
mrmazak said:
It seems that I was able to get the logo.bin to update when I applied the original update patch, but not when I used the same line in the rom install.
It is no big deal that it did not work, I was just trying to make it look different at boot time.
edit:
I think i found the problem with the logo not updating.
i used the update-binary from the official patch update. (the one that allowed the logo to change the first time)
and it changes . so since the ROM seems to install the way it is , only the logo didn't flash I put it in a separate update.zip if anyone is interested in it.
EDIT 2:
clarification.
It was not so much the binary allowing the logo to change but the format of the partition location I had been using that needed that binary.
Further test had shown me that I could have used the binary I was using but just change the partition naming line
Code:
package_extract_file("logo.bin", "/dev/block/mmcblk0p9")
the above code works with the same update-binary as rom install
But I was using
Code:
package_extract_file("logo.bin", "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo")
Taken straight from the official patch, and thats why it needed the update-binary also.
I dont know what is different in the binary other than , major size difference.
The powered by me logo was just a test file to see changes in the logo.
Click to expand...
Click to collapse
Hahaha the scribbled "ME" is hilarious. Your work is awesome, I don't think anyone using this rom will have an issue with the boot image but thanks for being so helpful and explaining.
P. S. Do you have any plans with the Nougat update?
Serenitybs said:
Hahaha the scribbled "ME" is hilarious. Your work is awesome, I don't think anyone using this rom will have an issue with the boot image but thanks for being so helpful and explaining.
P. S. Do you have any plans with the Nougat update?
Click to expand...
Click to collapse
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )
linuxsociety said:
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )
Click to expand...
Click to collapse
Somebody already tried this out
linuxsociety said:
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )
Click to expand...
Click to collapse
It was just wishful thinking. I have no idea how all of this is done. All I know is @mrmazak has helped me to fall in love with my phone again with this V8.3. The 7.4.2 did seem a bit buggy for my phone but this update works beautifully and I didn't even root it. If this remains true I will be happy with this phone for awhile even on 6.0
Really confused right now.
I was browsing through the settings menus. And found in the Settings-security- menu a toggle labeled "quick boot" ( not to be confused with "fastboot") . I enabled it then rebooted to see if it booted quicker. Didn't seem to make much if any difference. So I went back to turn it back off. And it wasn't there. I checked in my other phone , it wasn't there on that one either.
Did any body see this menu item, and if so where is is it?
Edit 1:
Few more power off , power on cycles to compare times. With other phone and defiantly seems to have turned on some faster boot option.
This phone goes from off to on in 5-6 seconds other phone takes about 20.
Edit 2:
OK , I panicked for a minute.
Couldn't find the setting and thought that it was another way to block sp flash tool by preventing you from ever being fully powered off.
But the setting was in accessibility not security.
Mrmazak, first of all, thanks for the ROM, installed it yesterday. But I have a problem with SELinuxModeChanger app. First, I'm getting a security warning when installing it, then - when running it. And another message, with this app running - "can't obtain root", although SuperSU shows its status with green #, like every other app it gives root privileges to. On my other Prime phone, running 6.1 out of the box stock ROM, FM radio works just fine with SELinuxModeChanger app behaving flawlessly (no security warnings whatsoever). Any ideas?
detroitredwings said:
Mrmazak, first of all, thanks for the ROM, installed it yesterday. But I have a problem with SELinuxModeChanger app. First, I'm getting a security warning when installing it, then - when running it. And another message, with this app running - "can't obtain root", although SuperSU shows its status with green #, like every other app it gives root privileges to. On my other Prime phone, running 6.1 out of the box stock ROM, FM radio works just fine with SELinuxModeChanger app behaving flawlessly (no security warnings whatsoever). Any ideas?
Click to expand...
Click to collapse
The mode changer app is technically a security issue. I did have that warning a few times when using mode changer app from the XDA thread of the developer, then when I used the app downloaded from f-droid it worked with systemless root and didn't give the security warning.
The app downloaded from f-droid worked for me as well, many thanks!
Big thanks for getting this out, updated from previous debloated, rooted version to this modified 8.3 stock rom, rooted with SU v2.79 SR3, all is good - only App that won't show up nor install, even tried the ones off APK Mirror site - is my Dunkin Donuts App, LOL. Play Store now said it's not compatible and the APK started to install then failed - any ideas or suggestions on what to do ??
Otherwise, it's all good - I will survive without DD App, just run that from another device when I need my caffeine fix.
Letitride said:
Big thanks for getting this out, updated from previous debloated, rooted version to this modified 8.3 stock rom, rooted with SU v2.79 SR3, all is good - only App that won't show up nor install, even tried the ones off APK Mirror site - is my Dunkin Donuts App, LOL. Play Store now said it's not compatible and the APK started to install then failed - any ideas or suggestions on what to do ??
Otherwise, it's all good - I will survive without DD App, just run that from another device when I need my caffeine fix.
Click to expand...
Click to collapse
I also had an app that previously work, say is not compatible now.
Maybe has to do with apps that have links to pay accounts. And that has something to do with trustzone. (Tee1 & tee2)
Those sections I left out of the update. I will add it back in and test. Update when I do. It is also possible this problem is why Blu rolled back there update.
**EDIT**
well that didn't go well at all.
I flashed the new trustzone.bin files from the official update. Now phone no longer turns on and no longer connects to flash tool
**EDIT 2**
After much persistence and many failed attempts to get phone recognized in pc again. Finnaly got to a point that phone was cycling between "preloader" driver and "usb serial device", and with careful timing was able to start sp flash tool at just right time and the flashing back to original trustzone files seems to have recovered phone.
for the record i am not sure what steps made it work. But I was shifting back and forth between leaving phone sit on charge, then on charge with rubber band wrapped around power button, then not plugged in , and not plugged in with rubber band on power button.
Okay... persistence is key in customization, i guess! I am getting somewhere here!
mrmazak said:
The first link is needed to get phone unlocked so you can install twrp.
Click to expand...
Click to collapse
Finally got thru the steps in order (1-2-3-4) then Step (5) and sub-step 1. I can also boot to TWRP.
Now this brings me to this thread, 8.3 Stock ROM. The thread assumes one knows how to install it and I suspect this could be as easy as uploading it to a folder in the phone then booting to TWRP and INSTALLING the ZIP file? Could someone clarify the steps to install this 8.3 ROM?
Thanks!
OldSkewler said:
Okay... persistence is key in customization, i guess! I am getting somewhere here!
Finally got thru the steps in order (1-2-3-4) then Step (5) and sub-step 1. I can also boot to TWRP.
Now this brings me to this thread, 8.3 Stock ROM. The thread assumes one knows how to install it and I suspect this could be as easy as uploading it to a folder in the phone then booting to TWRP and INSTALLING the ZIP file? Could someone clarify the steps to install this 8.3 ROM?
Thanks!
Click to expand...
Click to collapse
Yes. You are correct
Either put the zip file on external sd card , put card into phone boot into recovery mode and install , or put file directly onto phone .
Many ways to do that.
Easiest is to copy to phone while phone is connected to PC.
Cam also download file from internet with your phone.
Bottom line is get zip file to the phone boot to recovery and install
Anyone else having wifi issues after upgrading? While watching videos it seems the internet cuts out. The phone says it's still connected but I have to turn wifi off and back on for anything to work. Could be my router also but it didn't seem to be doing this until I installed 8.3
mrmazak said:
Yes. You are correct
Either put the zip file on external sd card , put card into phone boot into recovery mode and install , or put file directly onto phone .
Easiest is to copy to phone while phone is connected to PC.
Bottom line is get zip file to the phone boot to recovery and install
Click to expand...
Click to collapse
Right on man! I am officially running 8.3 ROM with April 5th 2017 Security Patch Level! Geez.. it was not easy but I got this working!
MrMazak, I followed all your instructions on both links, so could you tell me what exactly I have on my phone? Is it rooted? Bootloader Unlocked? The phone seems to be working fine but I don't know what level of access I have. Honestly I don't even know exactly what the differences between all these terms are.
Also, do I have or not SU? One of the steps under the .bat I believe install it. How do I access it?
Thanks again!
---------- Post added at 10:19 PM ---------- Previous post was at 10:18 PM ----------
Weasel0 said:
Anyone else having wifi issues after upgrading? While watching videos it seems the internet cuts out. The phone says it's still connected but I have to turn wifi off and back on for anything to work. Could be my router also but it didn't seem to be doing this until I installed 8.3
Click to expand...
Click to collapse
My install is pretty fresh, couple of hours, but as far as I can tell all is working fine with Wifi, As a matter of fact this is a new device only connected with Wifi and no SIM Card.... internet works fine.