So like the title says I have been out of the ROM game for a little bit. Every couple of months I check in and see whats new and flash something else.
I was on the Jelly Beans ROM (Build 16 I think) and Android 4.1. I did some searching last night as was going to try flashing Gummy ROM…bad idea. I am guessing I needed something prior to jumping up to a 4.4 base. I booted to recovery and wiped everything and tried to flash with no luck. So the phone would not boot and I could only get into recovery and download mode. I did not have my micro SD adapter in order to get jelly beans back on it to flash so I ended up having to use odin to flash a stock rooted 4.1 image. Finally got everything back up and running but I still want to try some of the 4.4 ROMs. So what exactly do I need first in order to flash one? (Modem maybe)…if you know for sure why that happened and what I need to do please let me know. Thanks!
My Current "About Phone" Info...
Android Version - 4.1.2
Baseband version - I535VRBMB1
Jelly Beans - Build 20
P.S. I have tried doing the research and nothing I have found has been clear but one thing I came across is the official 4.3 update was bad news and broke the root methods? So should I stay away from 4.3 ROMs and is the old root method blocked in 4.4 as well or is that a different case since it wasn't actually released for our phone. If that makes sense lol
aholeinthewor1d said:
So like the title says I have been out of the ROM game for a little bit. Every couple of months I check in and see whats new and flash something else.
I was on the Jelly Beans ROM (Build 16 I think) and Android 4.1. I did some searching last night as was going to try flashing Gummy ROM…bad idea. I am guessing I needed something prior to jumping up to a 4.4 base. I booted to recovery and wiped everything and tried to flash with no luck. So the phone would not boot and I could only get into recovery and download mode. I did not have my micro SD adapter in order to get jelly beans back on it to flash so I ended up having to use odin to flash a stock rooted 4.1 image. Finally got everything back up and running but I still want to try some of the 4.4 ROMs. So what exactly do I need first in order to flash one? (Modem maybe)…if you know for sure why that happened and what I need to do please let me know. Thanks!
P.S. I have tried doing the research and nothing I have found has been clear but one thing I came across is the official 4.3 update was bad news and broke the root methods? So should I stay away from 4.3 ROMs and is the old root method blocked in 4.4 as well or is that a different case since it wasn't actually released for our phone. If that makes sense lol
Click to expand...
Click to collapse
Can't tell you exactly why that happened, but it shouldve worked.
You're right though, stay away from the stock Ota 4.3 update. I'm happy you read first because so many people don't. My guess is your firmware was a little too old. Try to flash the mf1 firmware aio and then try gummy.
To be clear, you can still use any custom rom, even the 4.3 ones, just stay away from the stock rom or anything having to do with 4.3 ML1 firmware
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Can't tell you exactly why that happened, but it shouldve worked.
You're right though, stay away from the stock Ota 4.3 update. I'm happy you read first because so many people don't. My guess is your firmware was a little too old. Try to flash the mf1 firmware aio and then try gummy.
To be clear, you can still use any custom rom, even the 4.3 ones, just stay away from the stock rom or anything having to do with 4.3 ML1 firmware
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the quick reply. What do you mean try to flash the MF1 firmware...does that mean a 4.2 ROM?
I think I saw the new jellyBeans/alliance ROM was 4.3...or maybe it was something else..either way it would be ok to flash the 4.3 ROM? and if I wanted I could go back to a 4.1 Rom then..
aholeinthewor1d said:
Thanks for the quick reply. What do you mean try to flash the MF1 firmware...does that mean a 4.2 ROM?
I think I saw the new jellyBeans/alliance ROM was 4.3...or maybe it was something else..either way it would be ok to flash the 4.3 ROM? and if I wanted I could go back to a 4.1 Rom then..
Click to expand...
Click to collapse
Yes you can interchange between both of them if you want to.
So go here, read all of the details, and just follow his recommendation:
http://forum.xda-developers.com/showthread.php?t=1788313
Also don't double post, modify your post in the development section and put "wrong section, mod please delete".
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Yes you can interchange between both of them if you want to.
So go here, read all of the details, and just follow his recommendation:
http://forum.xda-developers.com/showthread.php?t=1788313
Also don't double post, modify your post in the development section and put "wrong section, mod please delete".
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
The reason I have so confused is cause of the link you sent. I read that before and it says..
"You should NOT flash the I535VRUCML1 firmware (or any subsequent releases for that matter). You will brick. This is what vzw/samsung did on the first OTA for the Galaxy S4. They changed the keys they sign the firmware with. This prevents us from 'mis-matching' our firmware like we've been doing all along. We've been leaving aboot (VRUAME6, the african-canadian sock-monkey leaked bootloader) alone and updating everything else. Since they're signing with different keys now, doing this will brick your device. If you update the ENTIRE bootchain (including aboot) you shouldn't brick, but will be stuck with a locked bootloader and any attempt to downgrade (via dd, etc) will brick you as well."
Like i said I have been out for a while and lost track of what firmwares came out and the order of them and which I need to be on to flash a 4.4 ROM. Someone else told me the only reason my first flash failed was because my recovery was older
***EDIT****
Ignore that entire thing I just realized you said to stay away from ML1 and that MF1 is ok..opps
aholeinthewor1d said:
The reason I have so confused is cause of the link you sent. I read that before and it says..
"You should NOT flash the I535VRUCML1 firmware (or any subsequent releases for that matter). You will brick. This is what vzw/samsung did on the first OTA for the Galaxy S4. They changed the keys they sign the firmware with. This prevents us from 'mis-matching' our firmware like we've been doing all along. We've been leaving aboot (VRUAME6, the african-canadian sock-monkey leaked bootloader) alone and updating everything else. Since they're signing with different keys now, doing this will brick your device. If you update the ENTIRE bootchain (including aboot) you shouldn't brick, but will be stuck with a locked bootloader and any attempt to downgrade (via dd, etc) will brick you as well."
Like i said I have been out for a while and lost track of what firmwares came out and the order of them and which I need to be on to flash a 4.4 ROM. Someone else told me the only reason my first flash failed was because my recovery was older
Click to expand...
Click to collapse
I see, that actually makes perfect sense.
I think I read you were on the mb1 firmware, that's new enough to not cause problems.
Basically you can't get the ml1 firmware from that thread I linked you. The only ml1 file available is the modem, and that's perfectly safe to flash.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
I see, that actually makes perfect sense.
I think I read you were on the mb1 firmware, that's new enough to not cause problems.
Basically you can't get the ml1 firmware from that thread I linked you. The only ml1 file available is the modem, and that's perfectly safe to flash.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I think I am getting it... I am on MB1...next was MF1....and then ML1. As long as I have a new recovery I can flash any MF1 based ROM right over MB1...and then I can flash the ML1 modem ONLY. If that is correct let me know..also does it matter if I do MF1 ROM or ML1 modem first?
again just wanted to say thanks for the help I appreciate it
aholeinthewor1d said:
I think I am getting it... I am on MB1...next was MF1....and then ML1. As long as I have a new recovery I can flash any MF1 based ROM right over MB1...and then I can flash the ML1 modem ONLY. If that is correct let me know..also does it matter if I do MF1 ROM or ML1 modem first?
again just wanted to say thanks for the help I appreciate it
Click to expand...
Click to collapse
You're close, firmware is completely independent from rom. You can flash any 4.3, 4.4, or 4.1 rom without changing your firmware.
Right now you can flash mf1 aio package, then ml1 modem, or just flash the ml1 modem over your current mb1 firmware.
Basically you aren't required to be on a specific rom build in order to use a specific modem.
Edit: I think you have the right idea, flash any rom you want, then the mf1 aio package, then the ml1 modem. Your firmware sequence is correct.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
You're close, firmware is completely independent from rom. You can flash any 4.3, 4.4, or 4.1 rom without changing your firmware.
Right now you can flash mf1 aio package, then ml1 modem, or just flash the ml1 modem over your current mb1 firmware.
Basically you aren't required to be on a specific rom build in order to use a specific modem.
Edit: I think you have the right idea, flash any rom you want, then the mf1 aio package, then the ml1 modem. Your firmware sequence is correct.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
ah ok...idk why I was thinking the firmware was what the ROMs were based from....so either way ML1 firmware sucks and I stay away...I guess my last questions are...what would be an advantage of going to the MF1 firmware...
and I always used clockworkmod recovery...do you know the option available now? and maybe some features of each
Related
Hi guys.
So I am very new to the Verizon Galaxy S3, and I didn't see this question anywhere that I looked in this section so forgive me anyways if it has been posted before.
After flashing the cm10 nightly from 2012-10-05 (October 5) I got the unauthorized software notice and I can't get it to go away.
Does anybody know how to reset it?
Help is much appreciated.
Thanks.
--Sam
You will have to Odin back to stock and start over. That message means you did not unlock your bootloader.
apacseven said:
You will have to Odin back to stock and start over. That message means you did not unlock your bootloader.
Click to expand...
Click to collapse
I did unlock my bootloader. But now that I can't tether it might be a while to download the 1.2GB file. Thanks man!
If you used ez unlock, there is a chance u had the version that wasnt unlocking properly. That message def comes from flashing custom kernel and a secure aboot in my experience. I think the version everyone said for sure works was 1.2.
apacseven said:
If you used ez unlock, there is a chance u had the version that wasnt unlocking properly. That message def comes from flashing custom kernel and a secure aboot in my experience. I think the version everyone said for sure works was 1.2.
Click to expand...
Click to collapse
I had to use 1.1 cause 1.2 wouldn't open on my phone. :/
Yep, the dreaded triangle. I had use EZ Unlock v1.4 and it screwed me. Use v1.2 or v1.0 I had to Odin back to stock and start from there. All is running well now.
This was how I got it back to stock (rooted). I had to use that special tip in the grey box to work for mine.
I remember when I had this happen to me. I was a total noob at flashing when I got my S3. Tried to install some rom with custom kernel and kept getting this at reboot. Didn't know anything about unlocking bootloader
A month later and I'm a pro... Well maybe not a pro, but no more triangle of death!
At the time, though, I nearly **** my pants lol.
Sent from my SCH-I535 using xda app-developers app
That happened to me, I thought sh#%, I gotta go to Verizon and act stupid. I Messed with it for a few minutes and figured it out. Then odined it back. You learn fast thanks to the geniuses in these forums.
Sent from my SCH-I535 using xda app-developers app
Sorry for posting on an old thread but I though a link to Ez Unlocker V1.2 would be nice for anyone else having this problem. http://forum.xda-developers.com/showthread.php?p=31819403
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Had this happen to me last weekend. I thought my boot loader was unlocked but it turned out the superuser app I flashed (which I thought was an updated one) didn't have the thing to unlock the boot loader. Basically I just rooted and assumed I had it unlocked... Then flashed MOAR and after aroma froze 5 times and finally got the whole way through i met mr triangle. Haha
Sent from my SCH-I535 using xda app-developers app
Download the official software update from somewhere online and flash it in Odin. Just make sure you download it for Verizon
Sent from my SCH-I535 using xda app-developers app
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
No longer works after Verizon 4.3 OTA
ThePatelBros said:
Download the official software update from somewhere online and flash it in Odin. Just make sure you download it for Verizon
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
This process no longer appears to work after Verizon OTA'd the official 4.3 update. I tried to flash back to stock following the steps here:
http://forum.xda-developers.com/showthread.php?t=1840030
However I'm unable to flash the VRALEC bootchain successfully. I'm wondering if Verizon had a little extra magic in that update.
johncase142 said:
This process no longer appears to work after Verizon OTA'd the official 4.3 update. I tried to flash back to stock following the steps here:
http://forum.xda-developers.com/showthread.php?t=1840030
However I'm unable to flash the VRALEC bootchain successfully. I'm wondering if Verizon had a little extra magic in that update.
Click to expand...
Click to collapse
Don't flash anything in Odin. Once on TW 4.3, you're permanently on TW 4.3 because of Knox bootloader. You have the potential to brick your device if you flash anything in Odin.
SlimSnoopOS said:
Don't flash anything in Odin. Once on TW 4.3, you're permanently on TW 4.3 because of Knox bootloader. You have the potential to brick your device if you flash anything in Odin.
Click to expand...
Click to collapse
I have already tried the original 4.0.4 ROM and am getting the yellow unauthorized triangle. Any idea how to make this thing boot again?
johncase142 said:
I have already tried the original 4.0.4 ROM and am getting the yellow unauthorized triangle. Any idea how to make this thing boot again?
Click to expand...
Click to collapse
After which step did you see this yellow triangle? Could you be very specific? Did the ICS tar flash successfully? Cuz from what I understand with 4.3 on other carrier's S3, once you're on TW 4.3 you can't downgrade. I want to tell you to flash VRBMF1 jellybean stock firmware since you've already flashed ICS firmware with no hard brick.
SlimSnoopOS said:
After which step did you see this yellow triangle? Could you be very specific? Did the ICS tar flash successfully? Cuz from what I understand with 4.3 on other carrier's S3, once you're on TW 4.3 you can't downgrade. I want to tell you to flash VRBMF1 jellybean stock firmware since you've already flashed ICS firmware with no hard brick.
Click to expand...
Click to collapse
I tried flashing the VRALEC bootchain first, and it took, but then threw the yellow triangle. After that I tried loading VRALF2 stock firmware and it did not give any errors. I tried again with VRALEC bootchain with no success. Then tried VRALF2 bootchain and VRBMD3 bootchain. I can boot into stock recovery and Odin, but that's all.
johncase142 said:
I have already tried the original 4.0.4 ROM and am getting the yellow unauthorized triangle. Any idea how to make this thing boot again?
Click to expand...
Click to collapse
We don't know. That means bootloader is locked. It would have to be Odin again. If got that with stock tar could be brick. If try to unlock may get hard brick. You kinda past the point of no return. Can try to Odin another newer one like MF1 and see what happens. It is saying the kernel is not compatible. Can't clear that message anyway without another stock Odin. Can't unlock with that message anyway. It's too late.
Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
prdog1 said:
We don't know. That means bootloader is locked. It would have to be Odin again. If got that with stock tar could be brick. If try to unlock may get hard brick. You kinda past the point of no return. Can try to Odin another newer one like MF1 and see what happens. It is saying the kernel is not compatible. Can't clear that message anyway without another stock Odin. Can't unlock with that message anyway. It's too late.
Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
Ok, I'm already downloading MF1 on my really slow Internet connection. It may be done by sunrise.
Every time I try to do the over the air update from ICS to JB on my AT&T Skyrocket when the phone restarts I get stuck at the TWRP bootloader (from when I rooted it). When I tell it to restart and the phone boots it tells me the update was unsuccessful. What am I doing wrong? More importantly, will I have to restore the original bootloader to update? If that's the case where can I find it? Will I have to backup everything and then just restore it to factory defaults?
If you're updating stock roms over the air, you have to be on stock, unrooted, with the stock recovery. However, that being said, there is no official JB rom for the skyrocket either through ota or through Kies. It's likely that it is reading that there is a minor update for ICS available. If you really want it, there is a thread for it somewhere around here. I believe that there may even be a flashable zip there.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
bps119 said:
If you're updating stock roms over the air, you have to be on stock, unrooted, with the stock recovery. However, that being said, there is no official JB rom for the skyrocket either through ota or through Kies. It's likely that it is reading that there is a minor update for ICS available. If you really want it, there is a thread for it somewhere around here. I believe that there may even be a flashable zip there.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
That's what I was afraid of. I can't find the original, and to be honest I forgot how to do it it's been so long since I've messed with it. On the other hand, if it's not JB then I'm not too worried about it and will let it ride until it is available. For my edification, do you know where I could find the proper stock recovery?
Check out the stickies. A member by the username of Vincom has a few with some really good info contained within them. In one of them, there is a link for Samsungs downloads page where you can find all the stock Odin flashable tars. Those will bring you back to 100% stock with recovery.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
The gt-i9005 has a leaked fireware of 4.4. I hope that we get in the next two or there months!
http://forum.xda-developers.com/showthread.php?t=2465713
Sent from my SGH-I337 using xda premium
killer5000 said:
The gt-i9005 has a leaked fireware of 4.4. I hope that we get in the next two or there months!
http://forum.xda-developers.com/showthread.php?t=2465713
Sent from my SGH-I337 using xda premium
Click to expand...
Click to collapse
I just downloaded
Has anyone tried unzipping it and rezipping without the bootloader, etc and tried flashing it rather than using odin and replacing the bootloader everything? I am working on that as we speak, just wondering if someone has done it already and what their experience was as far as what worked. I imagine there will be some issues with wifi or what not.
neo4uo said:
I just downloaded
Has anyone tried unzipping it and rezipping without the bootloader, etc and tried flashing it rather than using odin and replacing the bootloader everything? I am working on that as we speak, just wondering if someone has done it already and what their experience was as far as what worked. I imagine there will be some issues with wifi or what not.
Click to expand...
Click to collapse
If you're on i337 you cannot flash it through Odin, not authorized... I have been tinkering with putting together a zip to flash via recovery...but I'm a novice and couldn't get past the boot animation with sound...
ZPaul2Fresh8 said:
If you're on i337 you cannot flash it through Odin, not authorized... I have been tinkering with putting together a zip to flash via recovery...but I'm a novice and couldn't get past the boot animation with sound...
Click to expand...
Click to collapse
I was working on it the other day and just got to busy. There is a rom already in the I9505 thread...
http://forum.xda-developers.com/showthread.php?t=2555569
The only catch is from what I have read that the Wifi will not work unless you odin the leak first. For some reason it seems that you have to have the new leaked bootloader. I have talked to a couple of the people that made a zip flash keeping the bootloader we are on, but no wifi. I stopped working on making a zip after I found that out. I have thought about using odin to flash the leak then flashing the Rom from the link above, but am not sure if I would be able to go back to the roms that I am running on the old bootloader. I am just going to wait until some people that knows what they are are doing picks the leak apart more. Anywho if you are interested goto that thread above and do some reading. I personally am just going to stay away until we know more about the new bootloader. I know that the leak can be rooted though because chainfire released an update specifically for the 4.4.2 leak.
neo4uo said:
I was working on it the other day and just got to busy. There is a rom already in the I9505 thread...
http://forum.xda-developers.com/showthread.php?t=2555569
The only catch is from what I have read that the Wifi will not work unless you odin the leak first. For some reason it seems that you have to have the new leaked bootloader. I have talked to a couple of the people that made a zip flash keeping the bootloader we are on, but no wifi. I stopped working on making a zip after I found that out. I have thought about using odin to flash the leak then flashing the Rom from the link above, but am not sure if I would be able to go back to the roms that I am running on the old bootloader. I am just going to wait until some people that knows what they are are doing picks the leak apart more. Anywho if you are interested goto that thread above and do some reading. I personally am just going to stay away until we know more about the new bootloader. I know that the leak can be rooted though because chainfire released an update specifically for the 4.4.2 leak.
Click to expand...
Click to collapse
I did try flashing with Odin a day ago, I'm assuming since the Download Mode has "No authorization" it's due to the locked bootloader we have. About 10% into the flash it fails with an authorization error... I'm going to look into that thread to see if I can learn more...trial and error is a great learning tool for me
Downloading now to try it out. The updated link for that referenced rom is http://forum.xda-developers.com/showthread.php?t=2372286...
ZPaul2Fresh8 said:
I did try flashing with Odin a day ago, I'm assuming since the Download Mode has "No authorization" it's due to the locked bootloader we have. About 10% into the flash it fails with an authorization error... I'm going to look into that thread to see if I can learn more...trial and error is a great learning tool for me
Downloading now to try it out. The updated link for that referenced rom is http://forum.xda-developers.com/showthread.php?t=2372286...
Click to expand...
Click to collapse
Let us know, or pm and let me know how it goes
known bugs
Hi so far after using for the last two days I notice when holding the home button for open apps what ever you press will always open the last app used and not what you have selected!
Andy the native Samsung e mail app continuously tells me about e mails I've viewed
That is all so far!
what kernel are you using?
neo4uo said:
Let us know, or pm and let me know how it goes
Click to expand...
Click to collapse
Well after hours of farting around with their build and mine, I pretty much lost interest with the ROM now. Their build definitely has WiFi broken. I'm not sure if it's kernel related or not.
I think I'm with you on waiting for this to improve before using. Besides CM11 with Google Experience Launcher is looking and feeling great this past month...
Here is a like to Echoe13_4.4.2Deodex_12JAN2013.zip it works but you need to loki patch it and wifi don't work.
http://www.androidfilehost.com/?fid=23311191640113279
hello my friends somebody have one solution for the problem of wifi in rom stock o custom deodex of echoe in 4.4.2... And please can explainme what is the loky patch...? tks for your help and sorry for my english..!
Loki only has to be flashed on the At&t variant of the S4 after installing a zip that was not an At&t rom. The WiFi issue I believe is from not updating the bootloader via OTA and possibly kernel tweaks as well but it will get there. We have great devs for this device.
Sent from my SGH-I337 using XDA Premium HD app
scalamusical said:
hello my friends somebody have one solution for the problem of wifi in rom stock o custom deodex of echoe in 4.4.2... And please can explainme what is the loky patch...? tks for your help and sorry for my english..!
Click to expand...
Click to collapse
You need a kernel made from the 4.4.2 source code which has not been released yet for the wifi.
For loki patch on att, download loki-doki, put it on your SD, go to recovery, flash rom,flash loki doki. If you are using a rom made for att chances are the kernel will already be patched.
C13v3r0n3 said:
You need a kernel made from the 4.4.2 source code which has not been released yet for the wifi.
For loki patch on att, download loki-doki, put it on your SD, go to recovery, flash rom,flash loki doki. If you are using a rom made for att chances are the kernel will already be patched.
Click to expand...
Click to collapse
what kernel were you guys using on the echoe roms? I couldn't get past the boot screen and it hung using the i337m Canadian variant which should be the same as their TMO version minus the leaked bootloader.
There is a new NA5 leak out. I am in the I337 and have tried the NA1 leak Roms Indies Omega and Echoe and I always hang up on the boot menu. Guess we will have to wait for the official and the Kernel info for it to work for us.
rfb813 said:
There is a new NA5 leak out. I am in the I337 and have tried the NA1 leak Roms Indies Omega and Echoe and I always hang up on the boot menu. Guess we will have to wait for the official and the Kernel info for it to work for us.
Click to expand...
Click to collapse
You give me a few hrs, at work right now. I will have this running for att the NA5 base...so stay tuned....
TheAxman said:
You give me a few hrs, at work right now. I will have this running for att the NA5 base...so stay tuned....
Click to expand...
Click to collapse
I didn't know there was a nlthread on this on my native device. I Have been posting on the Tmobile thread since the leak first came out.
I also unpacked both Leaks and repacked only their respective boot, system and cache files and successfully flashed via Odin. the cool part was that I didn't lose root and only needed to add the new supersu. I had a titanium backup zip which I also flashed.
the problems are as follows
1. No WiFi. attempting to flash KT kernel bricked it. had to start all over
2. Security settings caused a FC. so couldn't enable installation from unknown sources.
3. Restoring user apps using Titanium backup (after freezing all Knox apps) worked. but adding any system apps caused a bad series of forced closures
so unless u have got an unlimited data plan, this is just something to play around with for now it would seem
AFAIK I337M devices share the same hardware with I9505 ones; so can I flash I9505XXUFNA5 onto my I337m?
guerouig said:
AFAIK I337M devices share the same hardware with I9505 ones; so can I flash I9505XXUFNA5 onto my I337m?
Click to expand...
Click to collapse
The bootloader would block odin from accepting the full package. The best u can do is pick n choose parts to flas like i did. And you'll end up with a similar scenario
But you could use this modified version and search for Magical unicorn kernel and see
http://forum.xda-developers.com/showthread.php?t=2608134
@gangsta101: so what bits did you chose to flash? is AP and CP and exclude BL and CSC for instance?
I have read through multiple posts but I am still slightly confused. So I have a Samsung Galaxy S3 running VRUCNC1. I have read that it is unrootable and that using ODIN to downgrade is the only option, but I have also read that downgrading will brick your phone. Could someone assist me with this?
Trevon75 said:
I have read through multiple posts but I am still slightly confused. So I have a Samsung Galaxy S3 running VRUCNC1. I have read that it is unrootable and that using ODIN to downgrade is the only option, but I have also read that downgrading will brick your phone. Could someone assist me with this?
Click to expand...
Click to collapse
Once your phone has taken either 4.3 OTA (VRUCML1 or VRUCNC1), downgrading to 4.1.2 will result in a hard brick. You can only switch between VRUMCL1 and VRUCNC1, the phone will essentially not boot on any other firmware. Downgrade to VRUCML1 then root via Saferoot. It is safe to do this.
Users with unlocked bootloaders (aka people who did not take either 4.3 OTA) can switch to ICS or JB 4.1.2 via Odin without fail or issue. We can do so, unless somehow we end up taking either 4.3 ota.
SlimSnoopOS said:
Once your phone has taken either 4.3 OTA (VRUCML1 or VRUCNC1), downgrading to 4.1.2 will result in a hard brick. You can only switch between VRUMCL1 and VRUCNC1, the phone will essentially not boot on any other firmware. Downgrade to VRUCML1 then root via Saferoot. It is safe to do this.
Users with unlocked bootloaders (aka people who did not take either 4.3 OTA) can switch to ICS or JB 4.1.2 via Odin without fail or issue. We can do so, unless somehow we end up taking either 4.3 ota.
Click to expand...
Click to collapse
Thank you! I apologize for the late response, but you explained this perfectly for me. I was able to downgrade and root, install safestrap, and even flash a ROM. However, I have only gotten one ROM to flash correctly. Is there another step I have missed? I have only gotten CleanROM 8.1 to flash correctly while everything else flashes but does not boot. I really appreciate the help!
Trevon75 said:
Thank you! I apologize for the late response, but you explained this perfectly for me. I was able to downgrade and root, install safestrap, and even flash a ROM. However, I have only gotten one ROM to flash correctly. Is there another step I have missed? I have only gotten CleanROM 8.1 to flash correctly while everything else flashes but does not boot. I really appreciate the help!
Click to expand...
Click to collapse
Unsure why it won't flash any other roms try this thread it's a good starting point
http://forum.xda-developers.com/showthread.php?t=2639337
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
WARNING: I am posting this for development purposes only (and for those of you already on the new locked bootloader)!
If you have an unlocked bootloader or are still on MF1 firmware, DO NOT flash this in ODIN or you will be permanently locked down to the new bootloader with no way of going back!
Those of you who know how to work with this file feel free to use it as you see fit. Otherwise, consider yourself warned!
Download: http://www.androidfilehost.com/?fid=23501681358553154
First!
Hairiest chest?
Can't wait till you guys crack this open for us unlocked folks!
i need to send my phone back into verizon. if i odin this i will be cool right?
Cannot wait for baseband update, hopefully it will be pulled separate soon.
So what does no-wipe mean?
Currently I am on NC1. If I want to odin to NE1 with fresh start, will this no-wipe affect in anyway?
You couldn't just flash the system and kernel partitions?
Sent from my GT-P5110 using Tapatalk 2
ruokuo said:
So what does no-wipe mean?
Currently I am on NC1. If I want to odin to NE1 with fresh start, will this no-wipe affect in anyway?
Click to expand...
Click to collapse
Means it is exactly the same as OTA. Does not wipe data. No difference flashing it and letting Verizon update it except Odin will unroot for you. Must unroot or hide root to take OTA.
kuronosan said:
You couldn't just flash the system and kernel partitions?
Sent from my GT-P5110 using Tapatalk 2
Click to expand...
Click to collapse
Won't boot with 4.3 firmware. It all or nothing for now or we would already have it fixed in dump thread.
Worked like a charm! Now I'll wait and see how to root this baby. I already had the locked bootloader so figured I didn't have anything to lose. Thanks!
gherman222 said:
Worked like a charm! Now I'll wait and see how to root this baby. I already had the locked bootloader so figured I didn't have anything to lose. Thanks!
Click to expand...
Click to collapse
Towelroot works.
Is there a version of this with an unlocked bootloader? I currently am running my S3 rooted and unlocked with 4.1.2. Do I need to run a ROM instead - and if so is there one that is stock 4.4.2 with an unlocked bootloader?
v1ncent said:
Is there a version of this with an unlocked bootloader? I currently am running my S3 rooted and unlocked with 4.1.2. Do I need to run a ROM instead - and if so is there one that is stock 4.4.2 with an unlocked bootloader?
Click to expand...
Click to collapse
They are currently at Work our beloved developers trying to bring us a rooted touch wiz version for those with unlocked bootloader in tact and the very first of it's kind I might add. Do not flash this if your bootloader is of value and be patient as the very best of the best of developers are collaborating to bring it to us.
Sent from my SCH-I535 using XDA Free mobile app
MIKEYSAKZ said:
They are currently at Work our beloved developers trying to bring us a rooted touch wiz version for those with unlocked bootloader in tact and the very first of it's kind I might add. Do not flash this if your bootloader is of value and be patient as the very best of the best of developers are collaborating to bring it to us.
Click to expand...
Click to collapse
Thanks - I have patience and definitely planning on waiting. That's why I still have an unlocked bootloader
prdog1 said:
Means it is exactly the same as OTA. Does not wipe data. No difference flashing it and letting Verizon update it except Odin will unroot for you. Must unroot or hide root to take OTA.
Won't boot with 4.3 firmware. It all or nothing for now or we would already have it fixed in dump thread.
Click to expand...
Click to collapse
Hello, how can i load in this firmware another modem like VRLHD, or there is some other way to install modem ?
P.s i have issue with sms/mms/i-net cuz of stock modem.
leroyinc said:
Hello, how can i load in this firmware another modem like VRLHD, or there is some other way to install modem ?
P.s i have issue with sms/mms/i-net cuz of stock modem.
Click to expand...
Click to collapse
Sounds like you borked your radios. Or your APN is missing. Only thing can do is run that tar. Can try running Verizon Software Updater in repair mode. It will wipe and then flash tar. If don't fix have to get new device from Verizon.
prdog1 said:
Sounds like you borked your radios. Or your APN is missing. Only thing can do is run that tar. Can try running Verizon Software Updater in repair mode. It will wipe and then flash tar. If don't fix have to get new device from Verizon.
Click to expand...
Click to collapse
hmm, i can't ask for new phone cuz im from another country, everything works on 4.2, but whe i updated to 4.3 i done with my phone
but what about Software Updater in repair mode, where is this ?
---------- Post added at 11:29 PM ---------- Previous post was at 11:01 PM ----------
prdog1 said:
Sounds like you borked your radios. Or your APN is missing. Only thing can do is run that tar. Can try running Verizon Software Updater in repair mode. It will wipe and then flash tar. If don't fix have to get new device from Verizon.
Click to expand...
Click to collapse
mms works, didnt know why wont work sms
leroyinc said:
hmm, i can't ask for new phone cuz im from another country, everything works on 4.2, but whe i updated to 4.3 i done with my phone
but what about Software Updater in repair mode, where is this ?
---------- Post added at 11:29 PM ---------- Previous post was at 11:01 PM ----------
mms works, didnt know why wont work sms
Click to expand...
Click to collapse
Make sure you are in Global mode before try any of this. If go with Software updater it is going to update you to 4.4.2. Not sure if can stop after repair or not. If that 4.3 tar in odin don't fix this is about only option I know of. Since bootloader is locked cannot use the fixes we have for this problem.
http://www.verizonwireless.com/support/devices/knowledge_base.html/80200/
open1your1eyes0 said:
WARNING: I am posting this for development purposes only (and for those of you already on the new locked bootloader)!
If you have an unlocked bootloader or are still on MF1 firmware, DO NOT flash this in ODIN or you will be permanently locked down to the new bootloader with no way of going back!
Those of you who know how to work with this file feel free to use it as you see fit. Otherwise, consider yourself warned!
Download: http://www.androidfilehost.com/?fid=23501681358553154
Click to expand...
Click to collapse
Is it safe to flash the modem only, in recovery, with existing mf1 firmware?
Thanks.
Sent from my SCH-I535 using XDA Free mobile app
I am on MF1 rooted and unlocked but I have had the phone since it's release and have no interest in installing AOSP ROMs. I do need root because I have to be able to use root explorer or similar so I can edit the "keys" system files to disable the "WAKE" function of the home key. I keep my phone in my back pocket and it constantly turns on if the home key has wake enabled.
Before I flash this I wanted to confirm that flashing this No-Wipe Factory Image with Odin, I can root with Towelroot and install Root Explorer? Would I also be able to install TW based ROMs like a new Clean Rom if Scott gets one figured out? Would I also be able to create nandroids using Clockwork or TWRP?
Lastly, Since my most recent install of CR 8.2 my phone's behavior has been a bit sketchy (random reboots, laggy, etc). I assume if I flash this stock image it should return my phone to whatever level of performance "stock" yields, without any of my current, likely self imposed, performance issues?
I have never had a phone this long and expect I'll get a new one whenever there really is a "next big thing", but I don't think we're there yet.
Thanks in advance.
Going back to stock
So, if I want to go back to stock, this is the way?
I'm on beanstalked / MF1 rooted and unlocked of course. But I'd like to get the phone back to stock condition so I can sell it here soon.