Related
What a crazy 3 months it has been, with life in general getting in the way of development, but it's over and here is a release for everyone!
For the full list of changes please see the changelog at http://bit.ly/aH0ioL.
*Please note*
All Google apps that are available for download from the market will no longer be included in the CCRoms Google apps package, to facilitate updating the apps the way Google intends.
Also this release is FROYO, Gingerbread will most likely be our next release with this gem version's features ported to AOSP Gingerbread.
The Main Highlights:
Obsidian for the Droid X is now a fully stable build, some minor bugs might still exist, but otherwise it is rock solid.
Tanzanite for the Droid 2 is also stable build, since it is so close to the Droid X.
Emerald for the HTC Evo is also stable for all pre-2.10 and 2.02 hboot updates.
Sapphire is just as stable as ever.
Ruby has been updated to the Miui ril for better connectivity and is more stable than ever.
That's right we are now on 5 phones, Thanks for all of your support everyone!
Now for the important part, Obsidian 2.0, Ruby 2.0, Sapphire 2.0, Tanzanite 2.0 are released!
All Downloads are available under the downloads section on our wiki: http://wiki.ccroms.net
Be sure to read the wiki pages fully for known issues and install instructions for certain roms.
NOTE: Emerald has been having some kernel issues and 2.0 will be delayed slightly.
Just flashed, running very fast!!!! Thank you sniffle and CVPCS. And the post above is the official post from sniffle himself
Really awesome work. Is running very stable for me. Reboot ->Recovery works perfectly as well so there is nothing to fear for people uncomfortable without needing Koush's bootstrap app.
Love that the Nexus wallpapers are all included. Also digging all of the customization options.
Again, Thank you for your work.
EDIT: Also I should not that you should download the apps .zip file before you flash the ROM because the stock browser can't download from the site for some reason. I had to do it on my computer and transfer over. Not very difficult but it will save a couple minutes to just download it before you flash.
if you notice any bugs please post them to the bug tracker (bugs.ccroms.net)!
(be sure to check if the bug exists before posting a new one)
hope everyone likes the release!
quick question
So the Obsidian note in the op says stable, is the bug list on the wiki current? No pin point Gps, camera or cam corder correct?
sunder74 said:
So the Obsidian note in the op says stable, is the bug list on the wiki current? No pin point Gps, camera or cam corder correct?
Click to expand...
Click to collapse
yes. the wiki list is the current bug list. by "stable" we mean it doesn't reboot uncontrollably anymore. it's still in beta and has kinks to be worked out.
Could anyone be helpful and point me towards the install instructions?
Great job guys. I'm waiting until GPS and Camera are working though. Can't wait to see a Gingerbread release!
Also, you guys should get a Google Code page.
I'd like a install guide as well, I don't wanna have to SBF my phone.
I third that. Quick question besides how to install this rom...i notice that the wiki said it provides bad battery life. I have an extended battery, but if it is so bad at this time, can i sbf back to Stock? Thanks for the hard work
Sent from my DROIDX using XDA App
mhsbrian said:
I'd like a install guide as well, I don't wanna have to SBF my phone.
Click to expand...
Click to collapse
some tips...
http://wiki.ccroms.net/obsidian/releases/2.0.0
Sorry, that doesn't actually say how to install the rom originally. Just says don't use clockwork mod after its installed. Is this originally installed through cw mod then using ccroms own clockwork app? Also can you sbf back to stock if it isn't for you?
Sent from my DROIDX using XDA App
for those wondering about installation:
basic installation procedure:
Download main (and possibly gapps) zips and push to your sdcard
Use koush's bootstrap recovery to get into CW recovery
NANDROID NANDROID NANDROID!
Wipe data/cache (Factory reset)
Install core zip from sdcard (no need to manually mount /system first)
(Optionally) install gapps zip from sdcard
Reboot
once in the system, do NOT use koush's bootstrap to get into recovery. instead, simply long-press the power button to bring up the global options menu, then select "Reboot" and "Reboot Recovery"
after that, you should reboot into CW again. from here you can nandroid all you like. nandroids from koush's bootstrap will work with the provided copy of CW recovery. note however that nandroids of obsidian will NOT work with koush's bootstrap recovery, as koush's bootstrap recovery does not backup/restore the /preinstall partition.
also, this installation only edits the /system and /preinstall partitions, so SBFs still work just fine if something goes wrong.
So if we wanted to go from another rom back to an Obsidian nandroid, how would we accomplish this?
Sent from my DROIDX using XDA App
ejgilkey said:
So if we wanted to go from another rom back to an Obsidian nandroid, how would we accomplish this?
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
On obsidian.. in the reboot menu... when u hit reboot, it give u the option to flash into recovery. Dont install the bootstrapper cuz its already included in the reboot menu on obsidian.
So you'd have to flash the rom first, then restore the nandroid? Is there an advantage to this recovery compared to bootstrapper?
Sent from my DROIDX using XDA App
ejgilkey said:
So you'd have to flash the rom first, then restore the nandroid? Is there an advantage to this recovery compared to bootstrapper?
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Sorry I have no idea what u mean.
ejgilkey said:
So you'd have to flash the rom first, then restore the nandroid? Is there an advantage to this recovery compared to bootstrapper?
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Bootstrap is not a recovery, it is merely the "vehicle" that gets you into Clockwork Recovery. Basically this ROM comes equipped with its own "vehicle" to boot to Clockwork Recovery.
GMB
ejgilkey said:
So you'd have to flash the rom first, then restore the nandroid? Is there an advantage to this recovery compared to bootstrapper?
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
I think you are confused.
Reboot Recovery using whatever ROM you are on
Create Nandroid backup
Install Obsidian from .zip
Play with Obsidian
Hold down power button, press reboot, then reboot recovery
Now you are in Recovery again
Click "Restore"
If I'm running Fission (or any other rom) and want to flash a nandroid backup I created using the Obsidian recovery, I would need to first install the Obsidian .zip and then reboot into Obsidians recovery to flash back to the Obsidian nandroid. Correct?
Sent from my DROIDX using XDA App
AT&T is not supported at this time.Update:
This is a CWM zip for the official Bell GB in stock format.
Bell_GB_2.3.6.zip
(md5 d757a0c2c2bb830946956d2411d22ccd)
Bell_GB_2.3.4.zip
(md5 e23a8d0895a13d032a2f46227d2ad7b2)
Notes:
This is a stock Gobstopper like the Bell 2.2.2 one, it is rooted but not deodexed.
It includes my auto ram fixer, so if your recovery doesn't have the ram fix, it will halt and fix that for you, just reboot into CWM again and proceed.
-----------------------------------------------------------
This is a CWM zip with deodexed app and framework plus some tweaks. To be applied to the stock 2.3.4/6 Bell GB above.
Bell_GB_2.3.6_deodexed.zip
[md5 b14b0a745ecba630315fdd2cdb8643ba]
Bell_GB_2.3.4_deodexed.zip
(md5 b2c72557ce80777a8f0d695f1ab2b6ed)
Features
Deodexed app and framework (48MB free in /system)
multitouch tweak (up to 10)
screen pixel density set to 280 qHD
proximity delay set to 150
wifi channels set to 14
wifi.supplicant_scan_interval set to 90
ro.hdmi.mirror.enable set to true
busybox added back in (v1.18.5 with some things taken out) Implemented as a /system/busybox directory with the system path in /init.rc updated to have that included.
ro.secure=0 in boot.img
Includes mkbootimg and unpack binaries compiled for the phone for extracting the boot ramdisk and adding it back in on the fly during CWM recovery. So if you are using another kernel than stock these tweaks will still apply. Can also be used for kernel only CWM zips, leaving the ramdisk alone.
Talk2.apk added from Bell leak, Talk.apk renamed to Talk.apk.bak
framework-res.apk has lower brightness levels for auto display brightness, original available as framework-res.apk.bak
Fixes:
data wasn't being mounted, forgot to put userdata instead of data. It is there for deleting dalvik-cache of odexed files, if factory reset, non issue.
PATH update was always updating (sanity check)
added in unlocked ap20bl to avoid having to re-unlock via sbf if flashing in one session. You will need to reinstall a CWM recovery and re-apply ramfix as well if it doesn't include it, since the stock zip resets the boot and recovery images. Ramfix is applied to stock boot but CWM is overwritten by stock recovery.
added in ramfix instead of using cmdline.txt, issues with too large lines in the script. Will probably modify mkbootimg to read a file instead. EDIT done.
The following has been superceded by the files above.
------------------------------------------------------------------------------
This is a CWM zip for the Bell GB leak.
Requires:
Unlocked bootloader GO HERE
Unlocked CWM recovery installed (tenfar's).
Patience
Features:
Deodexed app and framework.
su and shsu preinstalled, install Superuser.apk from market for root.
Date text colour in notification dropdown fixed.
Tunes and app duplication fixed.
No bloat removed. You decide.
Includes webtop, preinstall, cdrom, cdt updates and misc other partitions.
multitouch hack
Ram fixed. (autodetects mbr:1100 and mbr:d00, stock Bell 2.3.4 kernel)
33MB free in system instead of 1MB.
Download and install
Thanks to eval- for the unlocked ap20 bl.
Thanks to michael0619 for the multitouch hack.
thanks for setting this up. had problems downloading thus me not getting back to you with my progress. Now I can look for what went wrong.
Cheers
Is this a stock bell kernel?
If so can you pull it from this and host it D: Much needed.
Try flashing the zip through CWM recovery instead.
Sent from my MB860 using XDA App
during cwm update... I get a failed once reaching Updating System.... Hopefully this can be fixed.
y2whisper said:
thanks for setting this up. had problems downloading thus me not getting back to you with my progress. Now I can look for what went wrong.
Cheers
Click to expand...
Click to collapse
Hi.
Sure thing. Use it as a base for something better, it's pretty minimal as it is.
Cheers!
Sent from my MB860 using XDA Premium App
Mossys said:
during cwm update... I get a failed once reaching Updating System.... Hopefully this can be fixed.
Click to expand...
Click to collapse
Use tenfar's unlocked CWM recovery, not rom manager. install from internal.
Internal mem needs to be mounted, and it's called internal by tenfar, probably sdcard by rom manager.
Sent from my MB860 using XDA Premium App
capercb said:
hi i amhaving problems with setup motoblur..crashes no keyboard ...
moto-fastboot flash boot-2.3.4-d00.img
moto-fastboot flash system system.img moto-fastboot -w
moto-fastboot reboot
am i missing something thanks
Click to expand...
Click to collapse
Hi,
Factory reset. Use CWM.
Cheers!
Sent from my MB860 using XDA Premium App
Can i install on mt at&t?
Inviato dal mio MB860 usando Tapatalk
acer73 said:
Can i installazione on mt at&t?
Inviato dal mio MB860 usando Tapatalk
Click to expand...
Click to collapse
That hasn't been tested. I would expect bootloader and radio issues. Soft brick likely.
Cheers!
Sent from my MB860 using XDA Premium App
Are there any issues or considerations when coming over from the OrangeFR rom?
devin_mm said:
Are there any issues or considerations when coming over from the OrangeFR rom?
Click to expand...
Click to collapse
I wouldn't think so, however if you got there via pudding, then you just installed boot and system, maybe webtop, Whatever else is on your phone before that is still there. Should all be fine with an unlocked bootloader.
This CWM has the unlocked ap20 bootloader. Thanks eval-! Main reason for that is flashing multiple zips while in a CWM recovery session. (Since if you can flash it then you are already running an unlocked bootloader and it would otherwise be pointless, writing the same bl over itself. Attn. AT&T folks, your unlocked bl would change if you flashed this, danger.)
For instance if you flash back to stock using my Bell 2.2.2 gobstopper, you can flash to this one right away without losing the unlocked bootloader, or tenfar's CWM recovery. Not that that is should be necessary, but it's an option.
Cheers!
I ran through CWM and everything was good, after the reboot I started getting a whole bunch of FC's so I flashed again wiping the data and cache first. After the reboot on my second flash I'm getting less FC's but upon boot I'm getting an FC on com.motorola.service.main, I'm getting no data connectivity I figured that this was due to an APN issue so when I try setting one up I get an FC with com.android.settings
Any Ideas?
devin_mm said:
I ran through CWM and everything was good, after the reboot I started getting a whole bunch of FC's so I flashed again wiping the data and cache first. After the reboot on my second flash I'm getting less FC's but upon boot I'm getting an FC on com.motorola.service.main, I'm getting no data connectivity I figured that this was due to an APN issue so when I try setting one up I get an FC with com.android.settings
Any Ideas?
Click to expand...
Click to collapse
Hi,
Just to clear house I would go back to 2.2.2 and try again. I don't get that error.
I should probably add in the rest of the misc partitions ala the 2.2.2 gobstopper. (Takes forever to upload for me, 3.5 hours) What I implemented here were the changes made by the OTA, so you might still have some random junk left from prior to Orange GB.
Cheers!
Thanks for the assistance, I'll just use your 2.2.2 package to go right back to stock and start from scratch using your 2.3.4 package.
Thanks so much for your awesome packages!
Ok I ran your 2.2.2 Gobstopper package and it worked great, had data and everything no FCs at all. Then I unlocked the bootloader, installed CWM, and then installed this 2.3.4 package now I'm stuck at the motoblur hello screen with no data and when I try and look at the APNs I get the settings FC I posted before, and when I try and skip registration I get com.motorola.setup FC. I'm just not having any luck maybe I should just go back to 2.2.2 and wait for an OTA.
I've currently fastboot'd + erase everything that updates in this .zip.
Testing it out now, almost done installing the zip.
Will post updates.
Failed again.. the first thing that boots up is.
Sorry!
The process com.motorola.service.main has stopped unexpectedly.
FC.
Ok good so it is not only me.
Hi,
Sorry to hear you are having problems trying to duplicate now. Are you guys seeing 1100 or d00 on the screen when flashing. And is it only at motoblur setup?
Cheers!
How can I install two ROMS (MavROM and ICS) on my D3? one in SAFE MODE and one without.
what programs to use?
I already have MAVROM installed with SAFESTRAP from hashcode, but if i disable it, i get the stock rom.
thank you.
You have to use a bootstrap to flash your nonsafe before you install safestrap
Sent from my XT860 using xda premium
can you direct me to a link to that application? all I can find is safestrap from hashcode.
i have this one: "Droid3CWBootstrap"
http://www.appbrain.com/app/droid-x-recovery-bootstrap/com.koushikdutta.droidx.bootstrap
but how can I install zip with it?
I'm sorry I didn't see your last PMs
Anyway.
1) Start in stock ROM http://forum.xda-developers.com/showthread.php?t=1336980
(Or your non-safe ROM in safestrap and then remove safestrap)
2) After root, download bootstrap (I uploaded it) http://www.mediafire.com/?3u8xhmsp3lg5yfx
3) Install the APK and open the bootstrap app. Press install recovery then reboot recovery. You're now in bootstrap, not from using vol -+ etc (from your PM)
4) Flash mavrom using their CWM Recovery instructions
5) Once you got it setup, remove bootstrap app and install safestrap http://goo.gl/1pr5T
6) Reboot into safestrap and switch to safe system. Make a backup if you want before swithing. The switch will backup your current ROM (data), which is mavrom. Once in safe-system you can now flash ICS using the instructions. This will flash ICS in a different place. When you go back to non-safe system your mavrom will be restored.
Hope it's clear now
thank you. sorry i "attacked" you with a lot of PMs. i tought you had enough
i will try it tomorrow.
bogdan_wrc said:
thank you. sorry i "attacked" you with a lot of PMs. i tought you had enough
i will try it tomorrow.
Click to expand...
Click to collapse
Np aside from the fact that I'm not on XDA all day the notification is very small - most of the time I don't see it until the next day
Will this method work with Liberty as well? I have never installed safestrap, but have bootstrap installed. I thought that I had read that safestrap does not work with Liberty ROM.
Sent from my DROID3 using XDA App
zzandrewst said:
Will this method work with Liberty as well? I have never installed safestrap, but have bootstrap installed. I thought that I had read that safestrap does not work with Liberty ROM.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Afaik hashcode fixed safestrap to work with all roms
Sent from my XT860 using xda premium
Endoroid said:
Afaik hashcode fixed safestrap to work with all roms
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
Great! I will give it a try, basically I would just install safestrap and use Liberty as my non-safe and then flash cm7 for my safe right?
Sent from my DROID3 using XDA App
zzandrewst said:
Great! I will give it a try, basically I would just install safestrap and use Liberty as my non-safe and then flash cm7 for my safe right?
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
you can't flash nonsafe with safestrap. Gotta use a bootstrap to flash your nonsafe, then install safestrap for flash safesystem. But yes, i have liberty as my nonsafe and ics as my safe
Last time i tried to install MAVROM using CWM, i got the following error:
E:signature verification failed
when updating zip from card.
Installation aborted
what to do?
I dont have the INSTALL from zip option, just UPDATE from zip.
that why i used safestrap.
but if I want to install the boot animation from RAZR, now in which location shall I do that? it used to be in /system/media folder. still there?
thank you, i managed to install both one successfully.
bogdan_wrc said:
Last time i tried to install MAVROM using CWM, i got the following error:
E:signature verification failed
when updating zip from card.
Installation aborted
Click to expand...
Click to collapse
I think thats because you tried to flash using original recovery, you said something with -+ volume buttons?
Please be careful when doing this. While you "can" run 2 custom roms at once it is not what the safestrap system is designed for. Your non-safe rom should be stock and unaltered as it is what will save you from a fastboot flash should your safe rom go bad.
Sent from my HP Touchpad using Tapatalk.
calash said:
Please be careful when doing this. While you "can" run 2 custom roms at once it is not what the safestrap system is designed for. Your non-safe rom should be stock and unaltered as it is what will save you from a fastboot flash should your safe rom go bad.
Sent from my HP Touchpad using Tapatalk.
Click to expand...
Click to collapse
Well there's no reason to have the stock rom on non-safe "in case things go bad" because you can also just use "easy unbrick" which will put your phone back to stock just as fast as switching from safe to non safe.
As said before the only reason where this would be handy is when an official OTA is released, although i heard you need to uninstall safestrap for it to work
calash said:
Please be careful when doing this. While you "can" run 2 custom roms at once it is not what the safestrap system is designed for. Your non-safe rom should be stock and unaltered as it is what will save you from a fastboot flash should your safe rom go bad.
Sent from my HP Touchpad using Tapatalk.
Click to expand...
Click to collapse
Really a fastboot flash isn't such a big deal. I've done it more times than I can count. Takes 10 minutes. Id rather have my fav rom in nonsafe so I can use safe to testing new roms and new ics builds
Sent from my XT860 using xda premium
Is this dual boot system possible for my phone ? I would like to switch froyo and cynaogenmod !
Sent from my Optimus Me using XDA App
DoubleYouPee said:
Well there's no reason to have the stock rom on non-safe "in case things go bad" because you can also just use "easy unbrick" which will put your phone back to stock just as fast as switching from safe to non safe.
As said before the only reason where this would be handy is when an official OTA is released, although i heard you need to uninstall safestrap for it to work
Click to expand...
Click to collapse
I think you miss a key point. When you boot safestrap it starts in the non-safe system no matter what you do. Depending on your mode it then moves you to a totally separate partition on the device, preventing you from doing any harm to the boot rom.
The non-safe is key for the entire system to work. Yes it can be any rom, but you do put yourself at risk of losing two installs, including all the data.
Easy unbrick may be as fast to get to stock, but to rebuild back to where you were is going to take a lot longer.
In the end I am just advising caution, not telling people what to do. It does go against what the system was designed for and people should be aware of that before jumping off the ledge.
I understand, but now I have to go back to bootstrap to do essentially the same thing
Not sure if I follow you..
If you are only working in Safe-mode Rom the worst you can do is blow that rom up. Fixing it is just a matter of restoring your last backup via Safestrap recovery.
The problem with working in non-safe rom is that you can blow up both and lose your recovery. From that point you have to do Fastboot, install bootstrap, restore non-safe backup, install SafeStrap, restore Safemode backup.
Unless I am not understanding you correctly.
With the new boot loader unlock it comes time to use a recovery other than safe strap. The easiest way to flash a custom recovery, in this case, clockwordmod recovery, is to simply download ROM Manager and use it to flash the Motorola Photon Q version of CWM Recovery. I flashed it and booted into it and haven't experienced any problems as of yet so for those looking for a custom recovery straight out of the gate, this is for you.
Sent from my MB886 using xda premium
Nice i don't know if i should try it or wait for an official one for our device. In the mean time back to my nexus 4
Sent from my MB886 using xda premium
If you really want to give it a spin you can always flash the Photon Q version otherwise I'm sure there will be an official version ported soon
Sent from my MB886 using xda premium
Dumb question...... if I uninstall ss and install cwm will I lose the current ROM im using?
Sent from my MB886 using xda app-developers app
You'll have to reinstall yes.
Sent from my JokerMATRIX HD MAXX
Dumb question part 2..... uninstall ss first and then install cwm? Also erase all ROM slots before uninstalling? Thanks!
Sent from my MB886 using xda app-developers app
Yea make sure to erase the rom slots. I forgot to and uninstalled then was missing quite a bit of space lol.
Sent from my JokerMATRIX HD MAXX
I was thinking it might be a good idea lol. Thanks!
Sent from my MB886 using xda app-developers app
it actually works. lol
freshlycutlawn said:
With the new boot loader unlock it comes time to use a recovery other than safe strap. The easiest way to flash a custom recovery, in this case, clockwordmod recovery, is to simply download ROM Manager and use it to flash the Motorola Photon Q version of CWM Recovery. I flashed it and booted into it and haven't experienced any problems as of yet so for those looking for a custom recovery straight out of the gate, this is for you.
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
Have you flashed anything with it?
I haven't actually tried yet flashing a ROM but since I'm on stock and don't want to flash white yet I haven't had the opportunity, as long as its flashing to the device it should work with no problems
Sent from my MB886 using xda premium
freshlycutlawn said:
I haven't actually tried yet flashing a ROM but since I'm on stock and don't want to flash white yet I haven't had the opportunity, as long as its flashing to the device it should work with no problems
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
So far, i have installed the cwm for the photon q like you, and made a back up through it. Im going to see if it will restore from it as well. ill keep everyone updated.:good:
:edit: I sucessfully backed up my stock JB rom, wiped everything, and restored everything back and everythings perfect... I dont know what else to try before attempting to flash using the photon CWM. any ideas?
I uses the photon q recovery to backup & restore, and haven't had any issues yet. No ROM flashing for the time being, just haven't tried it yet.
Sent from my MB886 using xda premium
I Flashes AOSPizza and was getting a bootloop, had to start the phone in DB Mode from the Fastboot menu to get it to start up, charging my battery and will be restoring original at&t firmware as soon as possible....Dont need a brick just bought this!
I'm on aosp pizza but I reverted to the stock jelly bean system. Mounted system installed the aosp ROM the Mexico firmware was giving me hell except with cm 10
Sent from my Nexus 4 using xda app-developers app
DaveNavy said:
I Flashes AOSPizza and was getting a bootloop, had to start the phone in DB Mode from the Fastboot menu to get it to start up, charging my battery and will be restoring original at&t firmware as soon as possible....Dont need a brick just bought this!
Click to expand...
Click to collapse
Did you try to go back into CWM and wipe everything again after the boot loops? That sometimes helps when it is boot looping after an install.
bconcio said:
Did you try to go back into CWM and wipe everything again after the boot loops? That sometimes helps when it is boot looping after an install.
Click to expand...
Click to collapse
I tried the same thing with cm10, i tried 3 times and got bootloops on each, in the end, at least we know the back up and restore function works well.:good:
jbatacan said:
I tried the same thing with cm10, i tried 3 times and got bootloops on each, in the end, at least we know the back up and restore function works well.:good:
Click to expand...
Click to collapse
I'm Stock Again, Restart always sent me to fastboot with a failed flash error, I could back out of it to the pizza ROM each time however I don't want to depend on my phone booting incorrectly so I used RSD and I'm stock again, I'm going to give it another try tonight.
UPDATE...Reflashed everything started over and everything works PERFECT Yippie!!! I'm very pleased!!!!
Running AOSPizza and Loving it!
DaveNavy said:
I'm Stock Again, Restart always sent me to fastboot with a failed flash error, I could back out of it to the pizza ROM each time however I don't want to depend on my phone booting incorrectly so I used RSD and I'm stock again, I'm going to give it another try tonight.
UPDATE...Reflashed everything started over and everything works PERFECT Yippie!!! I'm very pleased!!!!
Running AOSPizza and Loving it!
Click to expand...
Click to collapse
So what was your full procedure? I want to try this and try to install CM10 later.
From what I read, you installed the Photon Q CWM, installed Pizza through that, got boot loops, flashed back to stock, then installed Pizza again?
bconcio said:
So what was your full procedure? I want to try this and try to install CM10 later.
From what I read, you installed the Photon Q CWM, installed Pizza through that, got boot loops, flashed back to stock, then installed Pizza again?
Click to expand...
Click to collapse
Fastboot was kicking errors and was boot looping into fastboot with firmware flash fail, I found however I could start into AOSPizza in DB mode (Safe Mode) , so I did that, charged up the phone 100% then used RSDLite and Reflashed Stock current firmware, it however does not re-lock the bootloader as some have mentioned might be the case in other post's, from there I started up the phone,turned on usb debug, used "motochopper" to root it, then installed Rom Manager from the market, flashed clockwork to device with the Photo Q CWM , copied AOSPixxaV1.zip ( The ROM ) and GappizzaV1.zip to the Phones internal storage not on the external SD memory card, from there went to clockwork mod on my atrix opened up the program and selected to reboot into recovery, went to the mounts and storage then select Mount System then go back then install zip from sd card then choose zip from sd card, then scroll to your rom and select it and it will flash when its complete you will go back and go to reboot system now, it will ask you if you want to bypass stock recovery on boot select it and your phone will reboot into AOSPizza......Have Fun!
This is for the SGH-T879 I did not de-bloat this, if you would like it de-bloated feel free to remove all the bloat using good old Win rar. Once again this is stock UVMA1 just rooted and deodexed.
Instructions;
(If you are flashing from a CM10 Build use darkside super wipe first. if you are coming from Android 4.2 or 4.3 please use Oden to Down grade first the stock Oden flashable file can be found here
http://www.sammobile.com/firmwares/1/?model=SGH-T879&pcode=0#firmware then skip to the section of how to use this to root stock UMA1)
1)Boot to TWRP.
2)Select the install tab.
3) Select file.(Darkside Super wipe, then rom)
4) Wipe Cashe and Dalvik Cashe.
5) Reboot.
Note; This rom automatically does a factory reset (noob safety net), if you have a stock touchwiz UVLG image you can safely restore your data from a backup.
This ROM can be used to root UVMA1 upgrade. After upgrade use Odin to flash ClockWork MOD. Then from CWM flash TWRP. Reboot to recovery (you should now be in TWRP). Backup your data. Install this ROM. Wipe both cashes. Restore Data. You now have rooted UVMA1. If downgrading from Android 4.2 or 4.3 you may have use Oden to Downgrade first in order to prevent bootloop, it shouldn't brick your phone but why take the chance.
https://docs.google.com/file/d/0Bx_IbXnhPXBJc3cya2ZpeGp4eFE/edit?usp=sharing&pli=1https://docs.google.com/file/d/0Bx_IbXnhPXBJc3cya2ZpeGp4eFE/edit?usp=sharing&pli=1
PS I am not a Developer, So no need to to send me cheese. This ROM was developed by Samsung. All I did is root and deodex it that's all. Although feel free to abuse the thank you button
Also due to the huge size of this file I am still looking for a permanent hosting site this one only last 7days.
As always I am not responsible if your phone
1) explodes
2) changes the nature of Algae growth
3) bricks
4) alters the time space continuum
5) turns evil and plots to overthrow the earth
6) or any other unforeseen mishap that may befall your phone due to the fact you failed to follow directions.
Give a special thanks to srpanadero for the more perminent link!
bot42 said:
This is for the SGH-T879 I did not de-bloat this, if you would like it de-bloated feel free to remove all the bloat using good old Win rar. Once again this is stock UVMA1 just rooted and deodexed.
Instructions;
(If you are flashing from a CM10 Build use darkside super wipe first.)
1)Boot to TWRP.
2)Select the install tab.
3) Select file.(Darkside Super wipe, then rom)
4) Wipe Cashe and Dalvik Cashe.
5) Reboot.
Note; This rom automatically does a factory reset (noob safety net), if you have a stock touchwiz UVLG image you can safely restore your data from a backup.
This ROM can be used to root UVMA1 upgrade. After upgrade use Odin to flash ClockWork MOD. Then from CWM flash TWRP. Reboot to recovery (you should now be in TWRP). Backup your data. Install this ROM. Wipe both cashes. Restore Data. You now have rooted AND deodexed UVMA1!
Download is here for now.
http://www.fileconvoy.com/dfl.php?id=g127a44223460126d9993152420562bb8dbfe989e2
PS I am not a Developer, So no need to to send me cheese. This ROM was developed by Samsung. All I did is root and deodex it that's all. Although feel free to abuse the thank you button
Click to expand...
Click to collapse
will this work on note i717 ?
In theory, it can if you replace the boot image a T717 Stock ICS Boot image using 7zip or winrar.I would still be extremely careful. Your best(TO AVOID BRICKING) bet would be running this through ROM kitchen with the T717 Stock TouchWIZ ICS as you're base ROM.
Sent from my SGH-T879 using xda app-developers app
I used Jedi Leader 4 without issues I will download now to test it on my i717
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
---------- Post added at 01:56 PM ---------- Previous post was at 01:42 PM ----------
Can we use this to boot it.......
http://forum.xda-developers.com/showthread.php?t=2109977
[ROM][UVLG3]Install T-Mobile 4.0.4 on i717!
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Yes that ROM UVLG for T717 is made for your phone, so yes you can use it' you can also use the boot image from it.
Sent from my SAMSUNG-SGH-T879 using xda app-developers app
bot42 said:
Yes that ROM UVLG for T717 is made for your phone, so yes you can use it' you can also use the boot image from it.
Sent from my SAMSUNG-SGH-T879 using xda app-developers app
Click to expand...
Click to collapse
I think att i717 note users can`t use this modem/radio without mod them
I agree.
Sent from my SAMSUNG-SGH-T879 using xda app-developers app
The link is down :sly:
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Link is back up for another 7 days I'll try to find a better host in the mean time.
bot42 said:
Link is back up for another 7 days I'll try to find a better host in the mean time.
Click to expand...
Click to collapse
Thanks Downloading now :beer:
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Thanks for this man. I always find myself going back to stock when I need some stability for a while. I have been getting too many reboots with CM10 lately.
No problem. I made back in March for myself, didn't know anyone else needed it until people started asking for it.
Sent from my SGH-T879 using xda app-developers app
Thank You
bot42 said:
No problem. I made back in March for myself, didn't know anyone else needed it until people started asking for it.
Sent from my SGH-T879 using xda app-developers app
Click to expand...
Click to collapse
We need all the help we can get.
Apologies for the noob questions... Could you explain the advantages of the UVMA1 over the UVLG3?
All I want is stability, when I was running the stock UVLG3 I had issues where I had to task-kill to get ram over 100mb in order to have any audio on phone calls...
I'm running Jedi 4 now and it's great other than the calendar widget and wallpaper scaling.
If UVMA1 is better, would you mind reposting it somewhere? If it works I certainly don't mind donating a bit, I use my phone everyday and the people that make it work better deserve some compensation
Thank you,
Scott
No need to donate, you already did when you bought the phone (Samsung built it, I just rooted it) The UVMA1 build contains the latest radio for out phone and extra security features, according to Samsung and T-Mobile.
Sent from my SAMSUNG-SGH-T879 using xda app-developers app
when i try to delete boot.img winrar says archive is corrupt anyway try downloading again but link is dead
Mirror?
Cannot complete the retrieval process
The retrieval process could not be completed. The file could not be found on the server. The retention period has expired.
Click to expand...
Click to collapse
Anybody have a working download link for this?? Thx in advance
Sent from my SGH-T879 using XDA Premium 4 mobile app
bot42 said:
This is for the SGH-T879 I did not de-bloat this, if you would like it de-bloated feel free to remove all the bloat using good old Win rar. Once again this is stock UVMA1 just rooted and deodexed.
Instructions;
(If you are flashing from a CM10 Build use darkside super wipe first.)
1)Boot to TWRP.
2)Select the install tab.
3) Select file.(Darkside Super wipe, then rom)
4) Wipe Cashe and Dalvik Cashe.
5) Reboot.
Note; This rom automatically does a factory reset (noob safety net), if you have a stock touchwiz UVLG image you can safely restore your data from a backup.
This ROM can be used to root UVMA1 upgrade. After upgrade use Odin to flash ClockWork MOD. Then from CWM flash TWRP. Reboot to recovery (you should now be in TWRP). Backup your data. Install this ROM. Wipe both cashes. Restore Data. You now have rooted UVMA1.
http://www.fileconvoy.com/dfl.php?id=gae57d94b77003e4f999325280886ea07a9c1d6747
PS I am not a Developer, So no need to to send me cheese. This ROM was developed by Samsung. All I did is root and deodex it that's all. Although feel free to abuse the thank you button
Click to expand...
Click to collapse
Can I flash this through Odin as I can only get into download mode with a USB jig.
I had TWRP and a CM rom and bricked it trying to do a restore. I tried flashing the stock through Odin (3 times) but as far as I get is the Samsung logo. Everything went smoothly with Odin start to finish but got a boot-loop.
Link not working
bot42 said:
This is for the SGH-T879 I did not de-bloat this, if you would like it de-bloated feel free to remove all the bloat using good old Win rar. Once again this is stock UVMA1 just rooted and deodexed.
Instructions;
(If you are flashing from a CM10 Build use darkside super wipe first.)
1)Boot to TWRP.
2)Select the install tab.
3) Select file.(Darkside Super wipe, then rom)
4) Wipe Cashe and Dalvik Cashe.
5) Reboot.
Note; This rom automatically does a factory reset (noob safety net), if you have a stock touchwiz UVLG image you can safely restore your data from a backup.
This ROM can be used to root UVMA1 upgrade. After upgrade use Odin to flash ClockWork MOD. Then from CWM flash TWRP. Reboot to recovery (you should now be in TWRP). Backup your data. Install this ROM. Wipe both cashes. Restore Data. You now have rooted UVMA1.
http://www.fileconvoy.com/dfl.php?id=gae57d94b77003e4f999325280886ea07a9c1d6747
PS I am not a Developer, So no need to to send me cheese. This ROM was developed by Samsung. All I did is root and deodex it that's all. Although feel free to abuse the thank you button
Click to expand...
Click to collapse
Got a link that works? Thanks in advance!!!