Related
seems this is not the latest ota? regardless is a pretty good rom up to you =).
Changelog:
v1.0.a
removed libui.so with tp wake, made the rom bootloop
Features
Rooted
Deodexed
Zip Aligned
Busybox included
Rom Manager
Dsp Manager
Wifi Calling(Tmobile include's this by default)
ScreenShots
Download Link
http://android-maisters.ddns.net/downloads/Vision-Aosp-Stock/Vision-Aosp-Stock-v1.0.zip
Click to expand...
Click to collapse
Patch to fix boot loops
http://android-maisters.ddns.net/downloads/Vision-Aosp-Stock/Vision-Aosp-tock-v1.0.a-patch.zip
Thanks to:
Cyanogenmod for dsp manager app/libs
rodraf for posting ota in tmobiel forums.
This looks fun =] Thanks Siulmagic
And this is different than virtous g lite? Were not even sure this is the official ota version yet I thought. Reports were that officia ota is 2.15.xxx.3 Thanks for the effort regardless of what the outcome is, ur roms are always nice!
Sent from my HTC Vision using XDA Premium App
Double post
xsteven77x said:
And this is different than virtous g lite? Were not even sure this is the official ota version yet I thought.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
not sure dunno what virtuos g lite is using as base. and yes this is the official update.
omggggg, i was gunna make this.
great work siul!! amazing as always =) better than i would have done anyway
interesting release...
this isn't based on the official ota, though?
Build: 2.15.531.3 <-- that is the official release build. this is 2.13.
maybe I'm wrong?
i guess no dutch language but i will try it hope it is better as cyan cheers
pmcqueen said:
interesting release...
this isn't based on the official ota, though?
Build: 2.15.531.3 <-- that is the official release build. this is 2.13.
maybe I'm wrong?
Click to expand...
Click to collapse
that's what the guy in forum said, and that's the version in the build.prop, blame tmobile =P
Tried installing this through recovery. First time over the leaked t-mobile GB without any wipes and it just boot looped. So went back to recovery. Wiped everything. Did a clean install of this zip. I still just get boot loop. Having to do a restore.
mike102871 said:
Tried installing this through recovery. First time over the leaked t-mobile GB without any wipes and it just boot looped. So went back to recovery. Wiped everything. Did a clean install of this zip. I still just get boot loop. Having to do a restore.
Click to expand...
Click to collapse
same here v_v
SmartBrother90 said:
same here v_v
Click to expand...
Click to collapse
Wrought Ro Scooby.
mike102871 said:
Tried installing this through recovery. First time over the leaked t-mobile GB without any wipes and it just boot looped. So went back to recovery. Wiped everything. Did a clean install of this zip. I still just get boot loop. Having to do a restore.
Click to expand...
Click to collapse
Same here. I wiped and installed three times, but still got a boot loop.
let me flash the rom see whats wrong.
i know whats wrong guys its a quick fix, you guys whant a flashable patch? or the whole rom?
siulmagic said:
i know whats wrong guys its a quick fix, you guys whant a flashable patch? Or the whole rom?
Click to expand...
Click to collapse
patchhhhhh!!!!
SmartBrother90 said:
patchhhhhh!!!!
Click to expand...
Click to collapse
whatever works, not too picky as we havent really been able to boot it, its not a big deal to flash a new version
siulmagic said:
that's what the guy in forum said, and that's the version in the build.prop, blame tmobile =P
Click to expand...
Click to collapse
(EDIT for further clarification: Check the PC10IMG.zip from May's size and that leaked build's size that was posted on the T-Mo community. Same size, down to the byte.)
This is incorrect information, and the wrong build altogether. The 2.13.531.8 build is what is in that post on the new T-Mobile community. That is the last leaked build from May, which was put on handsets mistakenly that were sent out as refurbs. 2.15.531.3, yesterday's build, is going to most likely be a "patch" style of update.zip, which will have the differences to be applied to the current software on the phone, thereby making it a smaller sized update, but won't have the complete set of files for the OS. So in tthe end, there is not yet a solid structure to build a nnew ROM on top of. No offense, siulmagic, but this is the same as the last one. Dig through more of the files and you will see exact matches. From what I saw, the newest build has the updated Google Music icon from the new Google Music Beta enabled app. Also, I believe the new Market is built in. Your images above, show the old Google Music icon. Either way, the build that was posted in the forums was just a re-post of the leaked build from May, since the T-Mobile forums were completely re-done, and some people there know nothing about visiting the XDA forums.
flamingblue8z said:
This is incorrect information, and the wrong build altogether. The 2.13.531.8 build is what is in that post on the new T-Mobile community. That is the last leaked build from May, which was put on handsets mistakenly that were sent out as refurbs. 2.15.531.3, yesterday's build, is going to most likely be a "patch" style of update.zip, which will have the differences to be applied to the current software on the phone, thereby making it a smaller sized update, but won't have the complete set of files for the OS. So in tthe end, there is not yet a solid structure to build a nnew ROM on top of. No offense, siulmagic, but this is the same as the last one. Dig through more of the files and you will see exact matches. From what I saw, the newest build has the updated Google Music icon from the new Google Music Beta enabled app. Also, I believe the new Market is built in. Your images above, show the old Google Music icon. Either way, the build that was posted in the forums was just a re-post of the leaked build from May, since the T-Mobile forums were completely re-done, and some people there know nothing about visiting the XDA forums.
Click to expand...
Click to collapse
iv already removed anything stating its an ota in op, i made a mistake , it happens to the best of us, regardless its a pretty good and fast rom, so iv decided to leave it.
siulmagic said:
i know whats wrong guys its a quick fix, you guys whant a flashable patch? or the whole rom?
Click to expand...
Click to collapse
Doesn't matter here! Just wanna get this ROM booted and see what it's got.
No more support for this rom
Something new the Toro+ is coming up in the world
Sent from my Galaxy Nexus using xda premium
Man I really like the look of this ROM. I'm just now getting started with it and I look forward to reporting back after a bit of use. Thanks for bringing this to the Toroplus OP, nice work.
I'll be installing this soon while im in my manager's meeting lol.
Sent from my Galaxy Nexus using Tapatalk 2
justen7723 said:
I'll be installing this soon while im in my manager's meeting lol.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Hey Bro, you're going to be pissed if you haven't modded the updater-script to change the two instances of "maguro" to "toroplus" b/c you'll get an error in CWM if you haven't made this modification.
Below is a link to the ROM in which I made the necessary changes to the updater-script to make the ROM flashable in CWM. The changes to the updater-script are simply changing two instances of "maguro" to "toroplus", and I've flashed the same file that I'm linking to and I'm running this ROM right now.
CLICK HERE to Download ROM w/ corrected updater-script (deleted "maguro", replaced it with "toroplus")
MoSeriouS said:
Hey Bro, you're going to be pissed if you haven't modded the updater-script to change the two instances of "maguro" to "toroplus" b/c you'll get an error in CWM if you haven't made this modification. I'll post a link in a short bit of the ROM with the correct updater-script so that the ROM can be flashed in CWM. Other than that you should be good to go..
Click to expand...
Click to collapse
THANKS!!! I'm on TWRP 2.1.2 (don't think it matters) I'll just hold off for now.
Sent from my Galaxy Nexus using Tapatalk 2
Thanks will try!
Sent from my Galaxy Nexus using Tapatalk 2
MoSeriouS said:
Hey Bro, you're going to be pissed if you haven't modded the updater-script to change the two instances of "maguro" to "toroplus" b/c you'll get an error in CWM if you haven't made this modification.
Below is a link to the ROM in which I made the necessary changes to the updater-script to make the ROM flashable in CWM. The changes to the updater-script are simply changing two instances of "maguro" to "toroplus", and I've flashed the same file that I'm linking to and I'm running this ROM right now.
CLICK HERE to Download ROM w/ corrected updater-script (deleted "maguro", replaced it with "toroplus")
Click to expand...
Click to collapse
UPDATE:
Ok, well the version of the ROM that I made with the modified updater-script (see post above) flashed fine, but I think that maybe the OP needs to make additional changes to make data/3G work on our device. I cannot get a data connection for the life of me, and I've never had this issue before with any other build for this device. When I go into Settings>More I cannot choose between LTE/CDMA and CDMA, and when I go into Settings>About Phone it says my Baseband Version is "Unknown" and pretty much everything else says Maguro (instead of "Toroplus?). Can someone with more knowledge than I inform me what files I can copy from Toroplus AOKP 40 and replace in this ROM so that I can get data working yo? Thanks.
sorry,i posted in the wrong section
this rom is for maguro
MoSeriouS said:
UPDATE:
Ok, well the version of the ROM that I made with the modified updater-script (see post above) flashed fine, but I think that maybe the OP needs to make additional changes to make data/3G work on our device. I cannot get a data connection for the life of me, and I've never had this issue before with any other build for this device. When I go into Settings>More I cannot choose between LTE/CDMA and CDMA, and when I go into Settings>About Phone it says my Baseband Version is "Unknown" and pretty much everything else says Maguro (instead of "Toroplus?). Can someone with more knowledge than I inform me what files I can copy from Toroplus AOKP 40 and replace in this ROM so that I can get data working yo? Thanks.
Click to expand...
Click to collapse
I don't think there are big differences between maguro and toro,you can download both files to compare them
MoSeriouS said:
Hey Bro, you're going to be pissed if you haven't modded the updater-script to change the two instances of "maguro" to "toroplus" b/c you'll get an error in CWM if you haven't made this modification.
Below is a link to the ROM in which I made the necessary changes to the updater-script to make the ROM flashable in CWM. The changes to the updater-script are simply changing two instances of "maguro" to "toroplus", and I've flashed the same file that I'm linking to and I'm running this ROM right now.
CLICK HERE to Download ROM w/ corrected updater-script (deleted "maguro", replaced it with "toroplus")
Click to expand...
Click to collapse
Avoid doing that. It is more likely that the ROM is not for you. Only do it if you are 100% sure that the Dev made an oversight in the script which is much less likely than having the wrong ROM for your phone. You keep doing this and you might get a brick soon.
Etoy's theme is the default theme?
The title / ROM name doesn't seem appropriate, if you ask me
Please consider switching to JB ics is over.
Verstuurd van mijn Galaxy Nexus met Tapatalk
Formhault said:
The title / ROM name doesn't seem appropriate, if you ask me
Click to expand...
Click to collapse
what do you mean?do you have another suggestion?
costygsm2 said:
what do you mean?
Click to expand...
Click to collapse
It's not clean - it's got TouchWiz things in it .
Oh and I agree with schukje. ICS is pretty much dead. We'll only get one more ICS AOKP build, then we're all going to the jellybeans stores .
Anyway, nice ROM. Let's hope you stick around until JB is out and bring us some of that goodness as well.
Formhault said:
The title / ROM name doesn't seem appropriate, if you ask me
Click to expand...
Click to collapse
I agree its not officially tied to AOKP at all
schukje said:
Please consider switching to JB ics is over.
Verstuurd van mijn Galaxy Nexus met Tapatalk
Click to expand...
Click to collapse
and thats not true, till AOSP releases tjhe code and everyone starts DEVn with JB , ICS is still the dominate OS for this device
---------- Post added at 11:00 AM ---------- Previous post was at 10:58 AM ----------
so the consensus is this ROM is pretty good? Im curious
Yep very true... That's what I am waiting for, the ROM's to switch to JellyBean things to be officially released. JB to me is not out yet and how people are putting these ROM's out and claiming to be JB without AOSP having released the source is to scary for me to try on my phone so I'm avoiding anything stating it's JB. For now it's ICS for me though I am running franco's 200 ics kernel which is running pretty good.
nicknowsky said:
I agree its not officially tied to AOKP at all
and thats not true, till AOSP releases tjhe code and everyone starts DEVn with JB , ICS is still the dominate OS for this device
---------- Post added at 11:00 AM ---------- Previous post was at 10:58 AM ----------
so the consensus is this ROM is pretty good? Im curious
Click to expand...
Click to collapse
Hi is this ROM for maguro? The GSM model?
Thanks
dan96815 said:
Hi is this ROM for maguro? The GSM model?
Thanks
Click to expand...
Click to collapse
Yes, it is
The GSM (Maguro) CM10 Nightlies are up. Made this thread for CM10 discussion.
Post bellow your questions and issues you are having with your device.
Download link is bellow
GSM Galaxy Nexus download link: http://get.cm/?device=maguro&type=nightly
To avoid conflicts and confusion each device has their own thread.
Verizon Galaxy Nexus CM10 discussion thread: http://forum.xda-developers.com/showthread.php?t=1840343
Sprint Galaxy Nexus CM10 discussion thread: http://forum.xda-developers.com/showthread.php?p=30393923
Latest Google Apps: http://goo.im/gapps/gapps-jb-20120726-signed.zip
anyone installed it yet?
Can you just flash over Rafael Salas' CM10 build without wiping anything, seeing that he's the official CM GNex maintainer and all?
Quick advice, a discussion about the three versions will be a mess.
We should create a post to each variant.
JMMO
CM10 for the toro is now available!
cyberon said:
Quick advice, a discussion about the three versions will be a mess.
We should create a post to each variant.
JMMO
Click to expand...
Click to collapse
this would be a very good idea and highly suggested.
For anyone who downloads the Verizon version please post your thoughts. I'm still running the preview build and wondering if it's worth installing or not. For me the Preview build has been near perfect.
Sent from my Galaxy Nexus using XDA Premium
gcantrell said:
For anyone who downloads the Verizon version please post your thoughts. I'm still running the preview build and wondering if it's worth installing or not. For me the Preview build has been near perfect.
Sent from my Galaxy Nexus using XDA Premium
Click to expand...
Click to collapse
It seems to be the same as the other CM10 variants I've tried. I have only been running it for about an hour though.
Sent from my Galaxy Nexus using xda app-developers app
Status 7
Tried flashing the nightly with CWM 6.0.1.0 Touch and ended up with a Status 7 error regarding the
assert(getprop("ro.product.device") == "toro" || getprop("ro.build.product") == "toro");
line in the updater-script. Had to flash to the non-touch version to get the release to install. Has anyone else seen this?
Edit: I suppose I should mention that I'm running the VzW Galaxy Nexus
android-nub said:
Tried flashing the nightly with CWM 6.0.1.0 Touch and ended up with a Status 7 error regarding the
assert(getprop("ro.product.device") == "toro" || getprop("ro.build.product") == "toro");
line in the updater-script. Had to flash to the non-touch version to get the release to install. Has anyone else seen this?
Edit: I suppose I should mention that I'm running the VzW Galaxy Nexus
Click to expand...
Click to collapse
This has happened in the past. The touch recovery has, at times, caused problems flashing ROMs. I never had the issue, but others had made note of it.
Sent from my Galaxy Nexus using xda app-developers app
Google now is missing?
Sent from my Galaxy Nexus using xda app-developers app
Perhaps someone can post a list of the differences between stock and CM10?
patruns said:
Perhaps someone can post a list of the differences between stock and CM10?
Click to expand...
Click to collapse
Yeah, I would like to know that to. I wan't to use CM10 for it's features, but now since JB I've become used to stock, with some additional apps that I missed since CM.
It would be great to know if there is anything from stock that are missing, and from there then get rid of all the extra apps I've installed since I went from CM to stock.
/Söder
soder said:
Yeah, I would like to know that to. I wan't to use CM10 for it's features, but now since JB I've become used to stock, with some additional apps that I missed since CM.
It would be great to know if there is anything from stock that are missing, and from there then get rid of all the extra apps I've installed since I went from CM to stock.
/Söder
Click to expand...
Click to collapse
It's basically JB + most, if not all the improvements from CM9.
TheSobadef said:
It's basically JB + most, if not all the improvements from CM9.
Click to expand...
Click to collapse
How about voice mail from the phone app?
TheSobadef said:
It's basically JB + most, if not all the improvements from CM9.
Click to expand...
Click to collapse
All features from CM9 already merged, and nothing from stock JB is broken?
/Söder
jzero88 said:
Google now is missing?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
works fine on my Toroplus.
android-nub said:
Tried flashing the nightly with CWM 6.0.1.0 Touch and ended up with a Status 7 error regarding the
assert(getprop("ro.product.device") == "toro" || getprop("ro.build.product") == "toro");
line in the updater-script. Had to flash to the non-touch version to get the release to install. Has anyone else seen this?
Edit: I suppose I should mention that I'm running the VzW Galaxy Nexus
Click to expand...
Click to collapse
I flashed it this morning from CWM touch and had no issues. Maybe it was just a fluke.
Also on Toro.
Sent from my Galaxy Nexus using xda app-developers app
To avoid conflicts and confusion, I have created separate threads for each device. This way the conversation won't be confusing and new readers of the thread won't have to ask answered questions. I've decided to turn this into the GSM (Maguro) thread. Sorry about the inconvenience guys.
Links to Verizon and Sprint threads in the Original Post.
Please give thanks to madmack!!
I did nothing to help with this, just bringing it to the people of this forums that want it.
It has working A2DP by pulling some stuff from the 12-26-12 build and implementing them into 1-15-13 and might have some broken features. If anyone finds any broken features then let me know and I'll ad them to this post.
VoIP calling is borked (video chats)
Call Echo is possible to return
His post with the download link, give him a thanks
http://forum.xda-developers.com/showpost.php?p=36804356&postcount=10721
Here are some posts confirming
http://forum.xda-developers.com/showpost.php?p=36842057&postcount=10754
http://forum.xda-developers.com/showpost.php?p=36831201&postcount=10740
(Joe Dirt Voice) DAAANNGG I thought you people would love this haha. Oh well.
mt3g said:
(Joe Dirt Voice) DAAANNGG I thought you people would love this haha. Oh well.
Click to expand...
Click to collapse
Holy crap this is heroic. I'll bet people haven't really noticed... I know I don't look at the general section terribly often but glad I did today. Downloading now. A thousand thanks to you.
No worries. I know people want it cause I posted that I had the old build of 10.1 with working BT and my PM box got flooded with hits.
Report back for folks.
Sent from my SGH-T999 using xda premium
Hey thanks I was wondering when this would show up thanks downloading now
bad ass Baked sg3
mt3g said:
No worries. I know people want it cause I posted that I had the old build of 10.1 with working BT and my PM box got flooded with hits.
Report back for folks.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
A2DP definitely works as expected. Audio is busted in g+ hangouts (think this got fixed in the caf audio stuff that happened in later nightlies). But that's a decent tradeoff. Haven't seen any other issues other than the ones everyone knows about from the regular nightlies- occasional flicker, lag after some games, etc.
How do you install this? Since its ATT, I get an error with CWM6 on my TMO S3.
Is there a version out there for the SGH-T999 (d2tmo)? I'm guessing since this is the d2att version it won't work on the SGH-T999, right? Thanks for fixing this issue.
I've flashed about 7 different att ROMs on my phone without editing anything before flashing. They work fine after unless trying to use something T-Mobile specific, like T-Mobile voicemail. I didn't fix it just brought to t999s attention.
Sent from my SGH-T999 using xda premium
mt3g said:
I've flashed about 7 different att ROMs on my phone without editing anything before flashing. They work fine after unless trying to use something T-Mobile specific, like T-Mobile voicemail. I didn't fix it just brought to t999s attention.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Thank you, this helps. I have the latest experimental build of 10.1, do you know if I will have to wipe my phone or can I just flash it over the existing 10.1 build? Thank you
I would try flashing like this.
Boot into recovery
wipe system
flash A2DP working Cm-10.1 rom
Flash gapps
reboot and test, if it doesn't work then wipe.
mt3g said:
I would try flashing like this.
Boot into recovery
wipe system
flash A2DP working Cm-10.1 rom
Flash gapps
reboot and test, if it doesn't work then wipe.
Click to expand...
Click to collapse
I've installed dozens of roms over the last few years, including some AT&T ones, but this one specifically gives me an error when installing the rom. I always wipe everything when going to a new rom. I even downloaded it a 2nd time incase the first one was corrupted or something.
This isn't too important to me anymore, cause I found a 4.1.2 rom I like, that has BT and Hotspot with encryption working, which neither seem to work with any 4.2 roms. But I am curious why it wasn't working.
so madmack's patch has made it into the latest nightly correct? no need for the rom he posted, just use the latest cm10.1 nightly?
dodgefan67 said:
so madmack's patch has made it into the latest nightly correct? no need for the rom he posted, just use the latest cm10.1 nightly?
Click to expand...
Click to collapse
I looked at things merged and an a2dp commit was but seen that more then a few times added with nothing changed so I'm going with a no on that one dude.
T-Mobile SGS III
which GAPPs to use with this 10.1 fix
thanks for the link to a bluetooth solution. Which GAPPs do I use for this ROM? I am new to rooting.
I loaded a later version dated april 11 - 2013 but bluetooth and voice search is not working. Any pointers would be appreciated.
Running on Skyrocket.
very much appreciated
--------------
mt3g said:
Please give thanks to madmack!!
I did nothing to help with this, just bringing it to the people of this forums that want it.
It has working A2DP by pulling some stuff from the 12-26-12 build and implementing them into 1-15-13 and might have some broken features. If anyone finds any broken features then let me know and I'll ad them to this post.
VoIP calling is borked (video chats)
Call Echo is possible to return
His post with the download link, give him a thanks
http://forum.xda-developers.com/showpost.php?p=36804356&postcount=10721
Here are some posts confirming
http://forum.xda-developers.com/showpost.php?p=36842057&postcount=10754
http://forum.xda-developers.com/showpost.php?p=36831201&postcount=10740
Click to expand...
Click to collapse
1dufflebag said:
thanks for the link to a bluetooth solution. Which GAPPs do I use for this ROM? I am new to rooting.
I loaded a later version dated april 11 - 2013 but bluetooth and voice search is not working. Any pointers would be appreciated.
Running on Skyrocket.
very much appreciated
--------------
Click to expand...
Click to collapse
ahhh nothing says XDA like a thread being raised from the dead
ok, first off, this is for the S3, not the S2 Skyrocket as your sig says you are using
second, go to the CM download page for your device (http://get.cm/?device=skyrocket) and grab the most recent nightly or get the stable version of 10.1 for it here (http://get.cm/?device=skyrocket&type=stable) dated June 24th. those should work fine
third, go to http://goo.im/gapps and grab the first file there, dated 20130301 for 4.2.2
make sure your recovery is updated (CWM or TWRP) then flash CM first, then gapps
then go here (http://forum.xda-developers.com/forumdisplay.php?f=1399) for the AT&T Skyrocket forums
good luck!
Midnight_Rider said:
ahhh nothing says XDA like a thread being raised from the dead
ok, first off, this is for the S3, not the S2 Skyrocket as your sig says you are using
second, go to the CM download page for your device (http://get.cm/?device=skyrocket) and grab the most recent nightly or get the stable version of 10.1 for it here (http://get.cm/?device=skyrocket&type=stable) dated June 24th. those should work fine
third, go to http://goo.im/gapps and grab the first file there, dated 20130301 for 4.2.2
make sure your recovery is updated (CWM or TWRP) then flash CM first, then gapps
then go here (http://forum.xda-developers.com/forumdisplay.php?f=1399) for the AT&T Skyrocket forums
good luck!
Click to expand...
Click to collapse
---------
Thanks for the information and redirection
HELP - my ATT Galaxy S3 is bricked after flashing Liquidsmooth 2.8.
I mistakenly downloaded from the link in the ATT Galaxy Note forum, but apparently posting there to ask for help left some Note owners severely POed. I had downloaded V4.2.2 from the same Note thread and flashed it with no problem.
I see the same download link in this thread in the Galaxy S3 developers forum. For some reason, this thread was closed on July 1.
Before flashing 2.8, I wiped the data and cache, then flashed the ROM and it installed with no problem. But on reboot it didn't restart. Battery has been pulled several times, Vol+ - home - power does nothing at all.
I've tried the instructions here, but ODIN doesn't recognize the phone when I plug it in.
I know there's dozens of brick-related threads -- most of them seem to have the same answers in the midst of a lot of BS.
I've installed quite a few ROMs on my phones, and have never had this problem come up before.
Any help getting my phone back would be appreciated.
I have the same issues as others in several other brick threads. Battery out and phone plugged into desktop, the red LED comes on and the desktop dings but the phone doesn't show as a device.
I've tried all of the suggestions in this thread, even though it's for a Captivate. No joy with any.
I tried installing the driver downloaded from Samsung, but got the attached error. I got the same error when I plugged the phone in the first time after flashing 2.8.
Wondering if I'm going to have to send the phone to Mobile Tech Videos for a JTAG job??
Again, any advice would be appreciated. Hopefully, I don't PO any S3 owners.
You bricked it. Mail it out for jtag. Next time, only flash software intended for your device.
Don't
Flash
Roms
For
Different
Devices
.
mrhaley30705 said:
You bricked it. Mail it out for jtag. Next time, only flash software intended for your device.
Click to expand...
Click to collapse
Yeah, I was afraid of that.
I can assume the S3 Liquidsmooth thread was closed BECAUSE it offered a ROM (2.8) that doesn't work on the S3, even with the video with v2.2 on the S3 posted right at the top of the OP.
Liquidsmooth seems to be at the root cause of much grief for our phones. Maybe the good dev can pull it off the forum until these issues are resolved.
Sent from my SAMSUNG-SGH-I747 using xda premium
jamesc760 said:
Liquidsmooth seems to be at the root cause of much grief for our phones. Maybe the good dev can pull it off the forum until these issues are resolved.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Doubt will get reimbursed for all the money heading to MobileTechVideo
Icersman said:
Doubt will get reimbursed for all the money heading to MobileTechVideo
Click to expand...
Click to collapse
Of course you're not going to be reimbursed anything... NO ONE BUT YOU MADE YOU FLASH THE WRONG ROM. Why should anyone else pay for it...
Flashing any Rom is done at your own risk.
studacris said:
Of course you're not going to be reimbursed anything... NO ONE BUT YOU MADE YOU FLASH THE WRONG ROM. Why should anyone else pay for it...
Flashing any Rom is done at your own risk.
Click to expand...
Click to collapse
Lighten up Francis. I was being sarcastic.
I'm fully aware of the risk. I'm also fully aware that the v2.2 ROM in the OP for Liquidsmooth and the updated 2.8 ROM that was added to the OP supposedly worked in the S3. Hence my suspicion that the thread was closed -- BECAUSE 2.8 BRICKS S3s
I am sorry you flashed a rom that did not belong on your device. I really am sorry.
but your posting got me to thinking why I was unable to install v2.8. after using the search bar I found a similar issue. followed the threads and was able to update the bootloaders and have flashed successfully flashed liquid smooth v2.8. I was surprised to have found it since you claim the post was taken down. it must have just been moved. It did not brick my device by the way.
I have enjoyed the work the liquid smooth team has turned out since I got my s3 and will continue to support them.
aircooledbusses said:
I am sorry you flashed a rom that did not belong on your device. I really am sorry.
but your posting got me to thinking why I was unable to install v2.8. after using the search bar I found a similar issue. followed the threads and was able to update the bootloaders and have flashed successfully flashed liquid smooth v2.8. I was surprised to have found it since you claim the post was taken down. it must have just been moved. It did not brick my device by the way.
I have enjoyed the work the liquid smooth team has turned out since I got my s3 and will continue to support them.
Click to expand...
Click to collapse
I enjoyed v2.2 after flashing it a month or so ago. Here is the thread that I downloaded 2.2 from. The updated link to Goo in the OP sends you to a page that contains the download links for 2.7 and 2.8.
The final post by Forum Moderator Jayharper08 posted on 7/1 says simply "Closed per Mike's request."
I had downloaded 2.8 prior to the 1st, so I assumed that all was OK. I don't see anything anywhere about the need to update the bootloaders, so again I assumed that clearing data and cache before flashing would be sufficient.
I don't blame Mike or the LS team. I would like to continue using the ROM once I get my "brick" back from MobileVidTech. To that end, which thread did you download 2.8 from?
http://forum.xda-developers.com/showthread.php?t=2346973
aircooledbusses said:
http://forum.xda-developers.com/showthread.php?t=2346973
Click to expand...
Click to collapse
Thanks. I searched the S3 Dev forum for "liquid smooth 2.8" and the only reply was to my linked thread.
So, when my phone comes back I'll flash from this thread.
Sent from my A500 using xda app-developers app
OK, now that I've had the chance to look at aircool's reply on my desktop, I'm confoozed.
I'm not a noob, but can someone 'esplain (without trolling) why there are two forums:
AT&T Galaxy S III Original Android Development
Original development for the AT&T Samsung Galaxy S III
and
AT&T Galaxy S III Android Development
Android development for the AT&T Samsung Galaxy S III
In my less than expert opinion, they seem redundant.
Original development is for source built roms/kernel with the work done originally by the op.
Development is another project that has stemmed from those works (kangs)
Or roms/kernels based on a modified TouchWiz.
studacris said:
Original development is for source built roms/kernel with the work done originally by the op.
Development is another project that has stemmed from those works (kangs)
Or roms/kernels based on a modified TouchWiz.
Click to expand...
Click to collapse
Thanks for clarifying that -- I think I get it.
And I apologize for spouting off earlier in the thread. I was a little cranky about bricking the phone. Of course, at my age I'm usually cranky!