Related
After getting request's to post this on its own thread... here's the stock, rooted & deodex'd rom that has been fixed... Superuser, HTC_IME FC's, and the updater script!
Dev's, use this as a base for your roms... If you are new to emmc partitions and updater scripts you can use this as a reference on how to properly mount, unmount and format partitions within the script. If you have anymore questions please post them on the 'Developers reference' thread located in this forum.
This rom is not going to be maintained, however i more than likely will update it as new OTA's rollout. Please only post rom development related items in this thread.
Stock--Rooted, deodexed 1.17.651.1 base rom!
thanks for this
I only wanted to add that as this is the base ROM that seemingly will be used to base other ROMS of off, that the VVM part of this ROM is broken. Uninstalling the package will not work, nor will updating to the latest version. Having to resort to Google VM.....
Not bashing by any means, just wanted to let you know, so maybe this can be fixed before it spreads to more ROMS as they are built. Only thing I found, OH, and the ROM is not R/W by default, seems its Read only.... easily fixed.
is there a reason why i get a stuts 7 error when flashing this?
cybrnook said:
I only wanted to add that as this is the base ROM that seemingly will be used to base other ROMS of off, that the VVM part of this ROM is broken. Uninstalling the package will not work, nor will updating to the latest version. Having to resort to Google VM.....
Not bashing by any means, just wanted to let you know, so maybe this can be fixed before it spreads to more ROMS as they are built. Only thing I found, OH, and the ROM is not R/W by default, seems its Read only.... easily fixed.
Click to expand...
Click to collapse
I flashed the rom to see what u were talking about... after updating VVM, it's working perfectly fine. Make sure you're on mobile network as it seems to not want to update via wifi.
As long as im correctly understanding you.... i don't know any rom that mounts file systems rw by default. You have to manually mount them via adb shell, or adb remount.. or a root app.
thetony said:
is there a reason why i get a stuts 7 error when flashing this?
Click to expand...
Click to collapse
Shouldn't be any reason, best way to help is to use these commands using adb shell right after you receive an error in recovery.
Code:
adb shell
cat /tmp/recovery.log
I have only flashed this rom using ClockworkMod 3.0, so i cannot say 100% that it works on 2.5... but so far it looks like you're the only one with an issue.
FYI: There's a guide posted on how to use ADB in this forum.
preludedrew said:
I flashed the rom to see what u were talking about... after updating VVM, it's working perfectly fine. Make sure you're on mobile network as it seems to not want to update via wifi.
Click to expand...
Click to collapse
On mobile network... :-( Flashed the ROM x2 and what I get (Over network) is a continual "Verifying your account information" when opening VMM V. T.5.1.0.48, until it times out. Then when I select settings for it, at the top its greyed out and continues to say "Please wait, verifying ......".
When I press the button to "Check for update", it says "General Failure. Please try again at a later time."
Anything I'm missing>? I have re-downloaded the ROM, as well as re-flashed 2 x to the same conclusion....
Thanks in Advance Prelude......
cybrnook said:
On mobile network... :-( Flashed the ROM x2 and what I get (Over network) is a continual "Verifying your account information" when opening VMM V. T.5.1.0.48, until it times out. Then when I select settings for it, at the top its greyed out and continues to say "Please wait, verifying ......".
When I press the button to "Check for update", it says "General Failure. Please try again at a later time."
Anything I'm missing>? I have re-downloaded the ROM, as well as re-flashed 2 x to the same conclusion....
Thanks in Advance Prelude......
Click to expand...
Click to collapse
Cybernook, sprint may be having issues where you are. I just tested it and mine updated, tho it took a reboot and had to make sure BT and WIFI were off.
After installing the rom I did the "update prl" and "update profile".
been using this rom ever since posted
no issues
works great
Apologies to you Prelude. I called sprint yesterday and they informed me they had been having VVM issue for 2 days (Up until my call). All is updated and working fine today!
Flash on........
I installed this rom but I can't get adfree to install new host updates
I get an error saying that there's no partition to install the host updates.
kbrn said:
I installed this rom but I can't get adfree to install new host updates
I get an error saying that there's no partition to install the host updates.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=935233&highlight=adfree
riggsandroid said:
http://forum.xda-developers.com/showthread.php?t=935233&highlight=adfree
Click to expand...
Click to collapse
Thanks a lot but It didn't solve my problem.
Actually I gave up on this rom for now.
For some reason the hosts file in etc/ or system/etc is a 0 file.
and will not read copy or move for nothing with root explorer or titanium.
Weird.
Thanks a lot anyway
the link to the rom is broken, gives a 404 not found error. can u pls repost, because im trying any and everything to get my phone up and running back on sprints network.
thanks
Any chance of a new base for the latest release?
CAN ANYONE point me to a WORKING LINK to the original evo shift sprint stock rom??? I can't find one anywhere on the net. Has to be a zip file too.
THANKS!!!
philipjacobs said:
CAN ANYONE point me to a WORKING LINK to the original evo shift sprint stock rom??? I can't find one anywhere on the net. Has to be a zip file too.
THANKS!!!
Click to expand...
Click to collapse
Im not sure anyone has a zip format of the shipped Froyo ROM. Good luck
*btw yelling isnt the answer*
Sent from my myTouch_4G_Slide using Tapatalk 2
philipjacobs said:
CAN ANYONE point me to a WORKING LINK to the original evo shift sprint stock rom??? I can't find one anywhere on the net. Has to be a zip file too.
THANKS!!!
Click to expand...
Click to collapse
http://shipped-roms.com/index.php?category=android&model=Speedy
try here
philipjacobs said:
CAN ANYONE point me to a WORKING LINK to the original evo shift sprint stock rom??? I can't find one anywhere on the net. Has to be a zip file too.
THANKS!!!
Click to expand...
Click to collapse
Are you looking for the RUU , or this particular Stock Rooted Rom? If you cannot find a link you could just pull the Rom from the RUU. Then run it through the Kitchen.
Download link is down
SOLVED - How to flash the Proper (Fixed) Stock Rooted Image
Description: This is 100% stock with just Superuser/su added and overwrites every partition to stock but keeps your personal data, apps, settings the same (just like the stock factory image).
Samsung Official USB Drivers - Link
ODIN v3.07 - Link
Proper Rooted Stock Image - Download or (Torrent Link) - MD5 = be4350a56e739eaf7a4184352d653a7b
1. Install USB drivers
2. Download ODIN v3.07
3. Backup your data
4. OPTIONAL: Do a factory reset (highly recommended if you have issues with your current ROM)
***WARNING: Step #4 will erase internal storage but not microSD card***
5. Download the above Proper Rooted Stock Image file and extract the tar file from inside it
6. Boot phone into ODIN mode (See here for how-to)
7. Flash the extracted tar file using ODIN v3.07
You should now have a like new condition stock image and rooted with all issues resolved.
Credit goes completely to mrRobinson for creating this image for us. Thank you sir. (Original Post) + (Details How It Was Made)
To Install Official CWM Recovery
1. After following above process, download "Rom Manager" from the Play Store
2. Open Rom Manager
3. Select "Flash ClockworkMod Recovery"
4. Select "Samsung Galaxy S3 (Verizon)" down at the bottom and let it flash
5. Once completed you can reboot to CWM by selecting "Reboot into Recovery" from Rom Manager
ORIGINAL REQUEST
After various testing, it seems many users are experiencing various issues with the rooted System.img provided by the OP in this thread. Many report findings of "Sprint related elements" as well as various keyboard issues and things not working as they should. I wish I had the knowledge myself but on behalf of the community, I'd like to request for someone with knowledge of this guide to remake the same rooted system.img as in the original but this time confirmed with using the original stock Verizon SCH-I535 image downloadable here.
I'm sure many of us here would highly appreciate this effort and we can also carry out further testing as many users reported that soon as they flash back to that stock image, their issues have disappeared and everything starts working properly.
I will quote another user in reference to this:
BungeBash said:
Just formatted back to stock until issues can be resolved. The stock image (which I'm told this root is + su) lost all Sprint instances and any strange extra options. Also the Keyboards are back to functioning. Not to be a conspiracy theorist, but I feel that the root image has more going on with it than what we are told.
Click to expand...
Click to collapse
Here's to hoping one of you knowledgeable developers are able to assist us with this request.
Click to expand...
Click to collapse
open1your1eyes0 said:
After various testing, it seems many users are experiencing various issues with the rooted System.img provided by the OP in this thread. Many report findings of "Sprint related elements" as well as various keyboard issues and things not working as they should. I wish I had the knowledge myself but on behalf of the community, I'd like to request for someone with knowledge of this guide to remake the same rooted system.img as in the original but this time confirmed with using the original stock Verizon SCH-I535 image downloadable here.
I'm sure many of us here would highly appreciate this effort and we can also carry out further testing as many users reported that soon as they flash back to that stock image, their issues have disappeared and everything starts working properly.
I will quote another user in reference to this:
Here's to hoping one of you knowledgeable developers are able to assist us with this request.
Click to expand...
Click to collapse
If you don't like it, dont flash it.
tonu42 said:
If you don't like it, dont flash it.
Click to expand...
Click to collapse
Hardly helpful for those who already flashed it... I just want it fixed, or a work around. If it's something as simple as uninstalling a few things, or replacing some databases, I'm fine with that. I just don't want to redo everything, and re-restore everything with Titanium Backup.
tonu42 said:
If you don't like it, dont flash it.
Click to expand...
Click to collapse
Not to be rude but we're not. That's why I'm making this request to remake with proper image. Because we are skeptical of the original one that was made. I PMed the OP of that thread and he claims to have used that image but in user's experience something is definitely different from stock, hence we're requesting a remake to test this.
open1your1eyes0 said:
Not to be rude but we're not. That's why I'm making this request to remake with proper image. Because we are skeptical of the original one that was made. I PMed the OP of that thread and he claims to have used that image but in user's experience something is definitely different from stock, hence we're requesting a remake to test this.
Click to expand...
Click to collapse
If you'd like, you can flash the stripped version, and I have a second zip that will restore all the stripped apps.
I did have some odd issues with SwiftKey crashing after flashing the image. Not sure if that has to do with it or not.
tonu42 said:
If you don't like it, dont flash it.
Click to expand...
Click to collapse
Useless post.
What would be useful is someone with the requisite knowledge being able to remake this exploit with the Verizon source in order to have maximum compatibility.
open1your1eyes0 said:
After various testing, it seems many users are experiencing various issues with the rooted System.img provided by the OP in this thread. Many report findings of "Sprint related elements" as well as various keyboard issues and things not working as they should. I wish I had the knowledge myself but on behalf of the community, I'd like to request for someone with knowledge of this guide to remake the same rooted system.img as in the original but this time confirmed with using the original stock Verizon SCH-I535 image downloadable here.
I'm sure many of us here would highly appreciate this effort and we can also carry out further testing as many users reported that soon as they flash back to that stock image, their issues have disappeared and everything starts working properly.
I will quote another user in reference to this:
Here's to hoping one of you knowledgeable developers are able to assist us with this request.
Click to expand...
Click to collapse
Are you talking about the system.img from invisibleks first image?
Link: http://forum.xda-developers.com/showpost.php?p=28402010&postcount=1
Or the stripped and rooted one?
Link: http://forum.xda-developers.com/showpost.php?p=28459565&postcount=1
I think the first one invisiblek made is pretty much what you are asking for. Remember, there's no SCH-I535 source code out there for people to build a system image from. These images are hacked system images from the stock image (found here: http://samsung-updates.com/device/?id=SCH-I535 ). One can't really "remake" the system image until we can fully bypass the encrypted and locked bootloader.
If you want to roll your own system image with the su binary and SuperUser you can follow the instructions here:
http://forum.xda-developers.com/showpost.php?p=27801304&postcount=1
They seem pretty straight forward.
However, I'm pretty sure that's what invisiblek did for his/her first rooted image (the one that isn't stripped).
Hope that helps. I can't do much of anything till my SGS3 arrives tomorrow.
ALQI
alquimista said:
Are you talking about the system.img from invisibleks first image?
Link: http://forum.xda-developers.com/showpost.php?p=28402010&postcount=1
Or the stripped and rooted one?
Link: http://forum.xda-developers.com/showpost.php?p=28459565&postcount=1
I think the first one invisiblek made is pretty much what you are asking for. Remember, there's no SCH-I535 source code out there for people to build a system image from. These images are hacked system images from the stock image (found here: http://samsung-updates.com/device/?id=SCH-I535 ). One can't really "remake" the system image until we can fully bypass the encrypted and locked bootloader.
If you want to roll your own system image with the su binary and SuperUser you can follow the instructions here:
http://forum.xda-developers.com/showpost.php?p=27801304&postcount=1
They seem pretty straight forward.
However, I'm pretty sure that's what invisiblek did for his/her first rooted image (the one that isn't stripped).
Hope that helps. I can't do much of anything till my SGS3 arrives tomorrow.
ALQI
Click to expand...
Click to collapse
The one in bold is what this request is about actually. Basically to remake that. Because the non-stripped rooted system.img that invisiblek is the one causing most issues for people and people have noted things in there that are not in the factory image. I tried to follow that guide myself but I must be missing something because most of those commands do not work for me. Mind you this is on a Windows PC.
I could do it, but it'd require more time than whats it worth. Sorry.
tonu42 said:
If you don't like it, dont flash it.
Click to expand...
Click to collapse
You are a WORM!!!!!!!
Sent from my Galaxy Nexus using xda app-developers app
tonu42 said:
I could do it, but it'd require more time than whats it worth. Sorry.
Click to expand...
Click to collapse
No worries. Very understandable as that guide is quite time consuming and not for everyone. Thanks for your support either way.
tonu42 said:
If you don't like it, dont flash it.
Click to expand...
Click to collapse
tonu42 said:
I could do it, but it'd require more time than whats it worth. Sorry.
Click to expand...
Click to collapse
Two completely pointless comments.
open1your1eyes0 said:
No worries. Very understandable as that guide is quite time consuming and not for everyone. Thanks for your support either way.
Click to expand...
Click to collapse
You sir are a better man than me for being so humble in response to these replies.
I'm assuming invisiblek DID in fact use the VZW image if the phone still had all the VZW nonsense in it (VZ Navigator, for example) as that would not be found in the Sprint image. Equally, if "all" he did was follow the steps in the link, then someone else doing the same is likely to produce the same result.
tonu42 said:
If you'd like, you can flash the stripped version, and I have a second zip that will restore all the stripped apps.
Click to expand...
Click to collapse
If you have these, have you posted them anywhere? That might have been a useful thing to do.
Here is all the removed apk's in a CWR zip.
http://www.mediafire.com/?6jv8wn9l5n0li9y
I actually saw that guide you posted about creating our own. I can try and whip something up tonight if I get some time. If not, tomorrow is my "Friday" at work, so I'll have time tomorrow evening for sure.
BungeBash said:
I actually saw that guide you posted about creating our own. I can try and whip something up tonight if I get some time. If not, tomorrow is my "Friday" at work, so I'll have time tomorrow evening for sure.
Click to expand...
Click to collapse
Thank you much sir. You assistance would be greatly appreciated.
Unfortunately I do not have a linux box so the guide does not work for me.
It's already been diff'd. There is no difference between the stock image and the rooted one here except for su and binaries:
http://rootzwiki.com/topic/29256-ro...erizon-galaxy-s-iii/page__st__110#entry793038
I'm guessing VZW has done more to the stock image on the phone than the stock one that is available for download, which is causing these differences.
Goose306 said:
It's already been diff'd. There is no difference between the stock image and the rooted one here except for su and binaries:
http://rootzwiki.com/topic/29256-ro...erizon-galaxy-s-iii/page__st__110#entry793038
I'm guessing VZW has done more to the stock image on the phone than the stock one that is available for download, which is causing these differences.
Click to expand...
Click to collapse
Considering I loaded the first root mod, then reverted to the image that it was created from and have 2 different setups I'd say two different files were used.
open1your1eyes0 said:
The one in bold is what this request is about actually. Basically to remake that. Because the non-stripped rooted system.img that invisiblek is the one causing most issues for people and people have noted things in there that are not in the factory image. I tried to follow that guide myself but I must be missing something because most of those commands do not work for me. Mind you this is on a Windows PC.
Click to expand...
Click to collapse
If its already been diff'd with the original, maybe the sammy-updates file ain't so good.
Hmm, I wonder if we dump the system.img from an untouched stock phone (like the one I get tomorrow), and inject that img with su, would that work out any better? I'll look into this tomorrow.
I'll also take a look at re-rolling the system.img from the sammy-updates files in the meantime.
I'll report back when and if I have a viable image.
~ALQI
alquimista said:
If its already been diff'd with the original, maybe the sammy-updates file ain't so good.
Hmm, I wonder if we dump the system.img from an untouched stock phone (like the one I get tomorrow), and inject that img with su, would that work out any better? I'll look into this tomorrow.
I'll also take a look at re-rolling the system.img from the sammy-updates files in the meantime.
I'll report back when and if I have a viable image.
~ALQI
Click to expand...
Click to collapse
According to users, flashing that sammy-update firmware got rid of all the issues and the Sprint related stuff. Just, FYI.
If anyone is up for the remake, you might want to try making it out of this one. Not sure if it's any different but it's from another well known Samsung firmware site.
Link to stock factory firmware
| ★ UPDATE.ZIP ★ | ►MF3★AT&T★MK2◄ | ★ UNBRICKED ★ METHOD ★ | ★ Jan.01.2014 ★ |
Hi guys, i got this files from someone that have a friend that work at Best Buy Samsung Experience Shop.....and because his phone won't take an OTA update so his friend hooked him up with this flashable update.zip......BEWARE !!!! I DID NOT TRY THIS YET !!!! BUT ALOT OF PEOPLE CONFIRMED THIS WORK.......U NEED TO BE ON STOCK 4.2.2 MF3 FIRMWARE WITH STOCK RECOVERY.....AND FLASH THIS UPDATE.ZIP TO UPDATE TO MK2 FIRMWARE.....OR..... ADB SIDELOAD...... SEE POST#2 FOR GUIDE ON HOW TO UPDATE......IF DOESN'T WORK YOU CAN ALWAYS GO BACK TO STOCK MF3 BY FLASHING MF3.TAR FILES BELOW...... AND IF DOES WORK USE THIS NEW SAFEROOT_METHOD TO ROOT MK2.....SO PLEASE BE CAREFUL IF U WILLING TO TRY AND HIT THANKS BUTTON IF DOES WORK..... ALSO U CAN USE THIS MF3>MK2 UPDATE.ZIP TO UNBRICKED MK2 PHONE WITH MF3-EMERGENCY.TAR INSTALLED FIRST..... SEE ATTACHED FILES BELOW AND GUIDE HOW TO FROM gtj0 THAT I EDITED ON POST#3....
IF U COMING FROM MF3 :
DOWNLOAD >>>MF3>MK2<<< HERE
md5= 7a5119f4c60bcfb26e1a7c69e0f8d9dc
IF U COMING FROM MJ9 :
DOWNLOAD >>>MJ9>MK2<<< HERE
md5= c76a83882fff76f4c718e939ddfb5333
PLEASE THANK mqlin FOR ORIGINAL DOWNLOAD LINK FOR MJ9>MK2
FLASH THIS VIA ODIN TO GET BACK TO STOCK MF3 :
MF3.TAR
md5= 6e266b0e6e4e37f763d75cdae8589e0d
ORIGINAL MF3.tar POST
NighthawkXL said:
They look legit, but it's for normal recovery mode not Odin in case anyone was trying to do that.
Here's the file tree if anyone is interested, and doesn't want to download it...
Click to expand...
Click to collapse
FILE TREE
gsmith2278 said:
Cool! Sounds great. Yeah I did it myself and went from mf3 to Mk2 then re rooted it.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
bennyboy78 said:
I was on MF3, I figured it out now. I had to Odin back to MF3 stock because I had deleted some ATT crap apps so it was causing the system to be modified. After that I just updated with this no problem
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
aaahmedaaa said:
brother you are the man 4.3 i337ucuemk2!!.thank you aloooottttt
Click to expand...
Click to collapse
Awesome.....:good:
| ★GUIDE★HOW★TO★ | ★UPDATE★ | ★Dec.30.2013★ |
| ★GUIDE★HOW★TO★ | ★UPDATE★ | ★Dec.30.2013★ |
In order for me to help u ....i need to know from which part that u don't understand.....as per XDA rules u need to READ before posting ....... STOCK phone is always recommended ......let's start with the easier way:
1. Put update.zip in your Sd Card
2. Reboot phone to recovery by power off your phone. Use combo Button ( VolUp+Home key+Power button) hold them together and when u feel vibration let go power button while still holding VolUP and Home key .....and then u would see samsung galaxy S4 black splash screen and small tiny reboot recovery..... on top left and u can let go both Vol Up and Home key......that's should bring u to android stock recovery.
3. choose apply update from external sd card.......yes to confirm ...... and reboot system when is done or it might reboot automatic.....Woollaa.....now u have 4.3 android MK2 firmware
But If doesn't work you need do these following in order for u to do adb sideload command:
4. U need Samsung USB driver install to your PC ......Install SAMSUNG KIES and plug your phone, it will install latest driver for your phone
5. Make sure u unable USB debugging mode on ur phone.....go to menu>settings>more> it should be on top of about device
( Developer options ) but if u dont have it go to about device and click build number 4/5 time....so that will unable developer options and CHECK USB DEBUGGING.
6. Make sure u have latest ADB ( Android Debugging Bridge ) version 1.0.31.... ANDROID SDK
7. Reboot to recovery>Apply Update From ADB....
8. Go to your PC>>>ADB folder>Shift+Right Click>Open Command Window Here
Code:
[B][COLOR="Red"]adb devices[/COLOR][/B]
Code:
[B][COLOR="Red"]adb sideload update.zip[/COLOR][/B]
Well u might already knew all these step.......and hopefully this will get u to start.... if not, please PM me if u need anymore help.....
Click to expand...
Click to collapse
| ★MK2 ★ UNBRICKED ★ METHOD ★ | ►AT&T★MK2★TAR◄ | ★Jan.23.2014★ |
| ★MK2 ★ UNBRICKED ★ METHOD ★ | ►AT&T★MK2★TAR◄ | ★Jan.23.2014★ |
MK2_UNBRICKED_METHOD_(HARD-BRICKED)
FOLLOW THE GUIDE FROM gtj0 THAT I EDITED BELOW, PLEASE USE MF3>MK2 UPDATE.ZIP FROM OP IF U BRICKED FROM MK2 TO GET BACK TO STOCK MK2 AND PLEASE DONT FORGET THANK HIM ALSO....
gtj0 said:
OK, If you're stuck with an incomplete flash, here are some steps you can try to get to MJ9...
These instructions assume you started with MJ6.
First, make sure you can boot into recovery. If not, download and apply the MJ6 recovery.
recovery-mj6.tar.md5
It should apply without error. If not, report the failure.
Download and extract the following files...
mf3-emergency-part-1.tar.md5.7z .....>>>>>MIRROR<<<<<.....
mf3-emergency-part-2.tar.md5.7z .....>>>>>MIRROR<<<<<.....
If you don't already have it, download the mf3-mj9 update file...
update-mf3-mj9.zip
Start Odin, connect your phone and boot into Download mode.
Flash mf3-emergency-part-1.tar.md5 which contains modem.bin, NON-HLOS.bin and system.img.ext4.
The flash of system.img.ext4 WILL FAIL at the end. That's OK.
Force Reboot the phone back into Download mode (Voldown+Home+Power) and restart Odin.
Flash mf3-emergency-part-2.tar.md5 which contains cache.img.ext4.
The flash WILL FAIL at the end. That's OK.
Force Reboot the phone back into Download mode (Voldown+Home+Power) and restart Odin.
The phone should now reboot to a black screen with the pulsing notification LED.U need to install recovery-mj6.tar.md5 or i337MK2stockRecovery.tar.md5 (also confirmed work with some users) via ODIN first if u stuck between step 6 and 7 since u are on DOWNLOADING MODE....and then force reboot to get u back to recovery if u coming from MK2 by using combo button (VolUp+Home+Power) or use this Odin Force Reboot .tar File to reboot
Reboot into recovery mode and choose apply update via adb and open your adb command from computer and use MF3>MK2 update zip files from OP .....HOPE THIS HELP......
Code:
adb sideload update.zip
I recommend sideloading instead of flashing from sdcard because the sdcard method reboots the phone whether the update was successful or not and you lose the error messages.
Reboot the phone and let it initialize.
You should now have MK2. and last step is to Hit THANK button......
Click to expand...
Click to collapse
FOR >>>>>MK2 FULL ODIN FILES<<<<<
Downloading the file seems to be the whole 728MB Rom file and not just the small file to update from MJ9 to MK2, so I'd love to know if you know if this will just update after flashed or if it wipes all your data, I just created a new thread asking for something like this and explaining why I don't want to wipe and just prefer to Update.
If someone can confirm if flashing this will just update without wiping I'd appreciate it, thanks in advance.
erasat said:
Downloading the file seems to be the whole 728MB Rom file and not just the small file to update from MF3 to MK2, so I'd love to know if you know if this will just update after flashed or if it wipes all your data, I just created a new thread asking for something like this and explaining why I don't want to wipe and just prefer to Update.
If someone can confirm if flashing this will just update without wiping I'd appreciate it, thanks in advance.
Click to expand...
Click to collapse
I definitely remember the official MK2 OTA from at&t was over 700MB when I got it, so the size seems right. Plus full TW Roms are usually >1GB anyway.
adb sideload and it should just update and not wipe, but can't confirm this myself - already on mk2.
prisonnet said:
I definitely remember the official MK2 OTA from at&t was over 700MB when I got it, so the size seems right. Plus full TW Roms are usually >1GB anyway.
adb sideload and it should just update and not wipe, but can't confirm this myself - already on mk2.
Click to expand...
Click to collapse
OK, I'm just saying that the Full MK2 that I downloaded a couple of weeks ago, the one to update from 4.2.2 to MK2 skipping MJ9 was that size, and I've read that the OTA update for the people already on MJ9 was 25 or 28MB, just a small update.
erasat said:
OK, I'm just saying that the Full MK2 that I downloaded a couple of weeks ago, the one to update from 4.2.2 to MK2 skipping MJ9 was that size, and I've read that the OTA update for the people already on MJ9 was 25 or 28MB, just a small update.
Click to expand...
Click to collapse
I think you're right, the MJ9 to MK2 was a small one but didn't you say you're on MF3 now? So this would be the file you need to get to MK2. And I'm almost positive this won't wipe data if you adb sideload, googling seems to confirm.
erasat said:
Downloading the file seems to be the whole 728MB Rom file and not just the small file to update from MF3 to MK2, so I'd love to know if you know if this will just update after flashed or if it wipes all your data, I just created a new thread asking for something like this and explaining why I don't want to wipe and just prefer to Update.
If someone can confirm if flashing this will just update without wiping I'd appreciate it, thanks in advance.
Click to expand...
Click to collapse
Seem to me it just an update patch. ....u can always back up your data... messages. ..etc using Titanium Backup. ....
SWYPED_FROM_S4_MF3_REDVENOM
prisonnet said:
I think you're right, the MJ9 to MK2 was a small one but didn't you say you're on MF3 now? So this would be the file you need to get to MK2. And I'm almost positive this won't wipe data if you adb sideload, googling seems to confirm.
Click to expand...
Click to collapse
You are right, and it was my bad, a typo, I meant that I'm at MJ9 now. I fixed my previous post now to avoid further confusion.
---------- Post added at 10:44 AM ---------- Previous post was at 10:38 AM ----------
ted77usa said:
Seem to me it just an update patch. ....u can always back up your data... messages. ..etc using Titanium Backup. ....
SWYPED_FROM_S4_MF3_REDVENOM
Click to expand...
Click to collapse
Problem is that I'm not root now, to be honest, this is a phone that is paid by my Company and I wasn't suppose to do anything with it, so when I decided to jump from 4.2.2 to 4.3 I knew that it was going to cost me the Root, but I decided that I needed to do it anyways, so for now, until further notice, I won't root.
So as you can see my phone is completely Stock, and I'm still getting the Software Interrupted error every time I try to update via OTA, so I don't see any other option but to try to sideload this update, problem is that without Titanium Backup, I will lose all my Data and I'm not willing to go though all the pain to restore all of it from scratch. So my mind is set just to do what I need to just Update without wiping.
So, if anybody try this, please, can you let us know here if you lose your data or if it just updates. Thanks a lot.
---------- Post added at 10:55 AM ---------- Previous post was at 10:44 AM ----------
OK Just to satisfy my curiosity, I downloaded the whole file again, and try to sideload it on my MJ9 phone and it immediately error out, this file seems to be the same than the other one in the other thread, it will work only only if you are on 4.2.2. So for me and anybody else trying to update from 4.3 MJ9 to MK2, it's still a no go.
erasat said:
You are right, and it was my bad, a typo, I meant that I'm at MJ9 now. I fixed my previous post now to avoid further confusion.
---------- Post added at 10:44 AM ---------- Previous post was at 10:38 AM ----------
Problem is that I'm not root now, to be honest, this is a phone that is paid by my Company and I wasn't suppose to do anything with it, so when I decided to jump from 4.2.2 to 4.3 I knew that it was going to cost me the Root, but I decided that I needed to do it anyways, so for now, until further notice, I won't root.
So as you can see my phone is completely Stock, and I'm still getting the Software Interrupted error every time I try to update via OTA, so I don't see any other option but to try to sideload this update, problem is that without Titanium Backup, I will lose all my Data and I'm not willing to go though all the pain to restore all of it from scratch. So my mind is set just to do what I need to just Update without wiping.
So, if anybody try this, please, can you let us know here if you lose your data or if it just updates. Thanks a lot.
---------- Post added at 10:55 AM ---------- Previous post was at 10:44 AM ----------
OK Just to satisfy my curiosity, I downloaded the whole file again, and try to sideload it on my MJ9 phone and it immediately error out, this file seems to be the same than the other one in the other thread, it will work only only if you are on 4.2.2. So for me and anybody else trying to update from 4.3 MJ9 to MK2, it's still a no go.
Click to expand...
Click to collapse
You could try updating through Kies...sometimes that's more reliable than OTA connections.
prisonnet said:
You could try updating through Kies...sometimes that's more reliable than OTA connections.
Click to expand...
Click to collapse
Kies3, says that the version I have (MF9) is not valid (or something like that) to do firmware updates. Original Kies, already says that my phone is not supported.
erasat said:
Kies3, says that the version I have (MF9) is not valid (or something like that) to do firmware updates. Original Kies, already says that my phone is not supported.
Click to expand...
Click to collapse
If I'm not mistaken. ... when u go to stock recovery..... the is an option for update via adb.....or something like that and u should be able to install update. Zip from there.. the only thing is I'm not sure if that would wipe your data or not but from adb sideload custom recovery it only wipe cache and dalvik cache as far I know. ...
SWYPED_FROM_S4_MF3_REDVENOM
ted77usa said:
If I'm not mistaken. ... when u go to stock recovery..... the is an option for update via adb.....or something like that and u should be able to install update. Zip from there.. the only thing is I'm not sure if that would wipe your data or not but from adb sideload custom recovery it only wipe cache and dalvik cache as far I know. ...
SWYPED_FROM_S4_MF3_REDVENOM
Click to expand...
Click to collapse
Yes, that's what it's called sideload and that's what I tried earlier but like I mentioned then, it errors out immediately, and at least you can see that it's clearly asking for 4.2.2.
One more thing, I just hanged up with AT&T, the Technical Support checked everything there and it seems that everything should be in place for me to get the update, they did something and asked me to try it again, as soon as I enter the Update Menu I saw a message saying something like DZ initialization, I have seen that just before we get the OTA, so I asked her and she told me that it was because of what she did, so I should be good to get any update available, and as soon as I tried it I got the same old Software Update Interrupted.
She told me that they will call me tomorrow with other more advanced technical Department to try to see what may be causing this.
I'll give them a quick look over, but I wouldn't jump on the bandwagon using these until somebody more versed then me confirms it's legit.
They look legit, but it's for normal recovery mode not Odin in case anyone was trying to do that.
Here's the file tree if anyone is interested, and doesn't want to download it...
http://pastebin.com/21vA9MMV
NighthawkXL said:
I'll give them a quick look over, but I wouldn't jump on the bandwagon using these until somebody more versed then me confirms it's legit.
They look legit, but it's for normal recovery mode not Odin in case anyone was trying to do that.
Here's the file tree if anyone is interested, and doesn't want to download it...
http://pastebin.com/21vA9MMV
Click to expand...
Click to collapse
OP Updated with File Tree ......great job bro......:good:
ted77usa said:
OP Updated with File Tree ......great job bro......:good:
Click to expand...
Click to collapse
Mind you, I haven't a 4.3 device to test this on... so although it looks legit (as in the file structure is correct) we still need someone to guinea pig it.
NighthawkXL said:
Mind you, I haven't a 4.3 device to test this on... so although it looks legit (as in the file structure is correct) we still need someone to guinea pig it.
Click to expand...
Click to collapse
I thought u need to be on 4.2.2 in order this to work. .... checking security for 4.2.2 before flashing. ..... according to erasat.
erasat said:
Yes, that's what it's called sideload and that's what I tried earlier but like I mentioned then, it errors out immediately, and at least you can see that it's clearly asking for 4.2.2.
Click to expand...
Click to collapse
SWYPED_FROM_S4_MF3_REDVENOM
ted77usa said:
I thought u need to be on 4.2.2 in order this to work. .... checking security for 4.2.2 before flashing. ..... according to erasat.
Click to expand...
Click to collapse
Yeah your right, I'm not thinking properly... kept forgetting these are the update files, not restore files. Though I assume they could be turned into Odin files given the right person.
For those of you with my same issue, updated to mj9 and getting errors while trying to update to Mk2, . Please follow my other thread at http://forum.xda-developers.com/showthread.php?t=2573637 and look for the link on post #3, finally found the update file and I'm already at MK2.
NighthawkXL said:
Yeah your right, I'm not thinking properly... kept forgetting these are the update files, not restore files. Though I assume they could be turned into Odin files given the right person.
Click to expand...
Click to collapse
What would it take to do this? Anything already started to make this happen?
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Does anyone know where I can get just the stock bootloader image to flash via TWRP?
Long story short I F'd up my bootloader and now Odin will not flash a stock BL file do to a version mismatch and to make matters worse I can't find a way to restore to stock baseband so my network isn't working. If someone can share a backup that'd be super
EDIT: Forgot to specify I need it from a TMobile variant (J700T) for firmware APK6 or APK3 (Odin doesn't seem to want to flash the stock BL from my Odin ROMs perhaps because there is a version mismatch in the phone?)
NullaVisus said:
Does anyone know where I can get just the stock bootloader image to flash via TWRP?
Long story short I F'd up my bootloader and now Odin will not flash a stock BL file do to a version mismatch and to make matters worse I can't find a way to restore to stock baseband so my network isn't working. If someone can share a backup that'd be super
EDIT: Forgot to specify I need it from a TMobile variant (J700T) for firmware APK6 or APK3 (Odin doesn't seem to want to flash the stock BL from my Odin ROMs perhaps because there is a version mismatch in the phone?)
Click to expand...
Click to collapse
download latest stock rom at sammy..
Already tried. Looks like I am officially a victim of a partial brick (Odin wont flash BL because it thinks I'm downgrading and I have no Baseband/network) I'll try and see what I can do through TWRP since I can still flash that through Download mode. I made no backups myself but would restoring another TWRP backup solve it perhaps?
NullaVisus said:
Already tried. Looks like I am officially a victim of a partial brick (Odin wont flash BL because it thinks I'm downgrading and I have no Baseband/network) I'll try and see what I can do through TWRP since I can still flash that through Download mode. I made no backups myself but would restoring another TWRP backup solve it perhaps?
Click to expand...
Click to collapse
try flash custom rom after that flash stock rom..
khaisttj92 said:
try flash custom rom after that flash stock rom..
Click to expand...
Click to collapse
No dice my dude. However, I did find something else
Turns out when I check the bootloader version it reads J700T1UVU3AQC3. Sure enough there was a baseband update and security update a few days ago and my device must've installed it while I was asleep. This would explain why my baseband is broken AND why Odin doesn't want me to flash the APK6 Bootloader.
So there's good news and bad news. The good news is there is hope but the bad news is I am currently at the mercy of whenever someone decides to upload this firmware on the internet (if anyone does that is)
NullaVisus said:
No dice my dude. However, I did find something else
Turns out when I check the bootloader version it reads J700T1UVU3AQC3. Sure enough there was a baseband update and security update a few days ago and my device must've installed it while I was asleep. This would explain why my baseband is broken AND why Odin doesn't want me to flash the APK6 Bootloader.
So there's good news and bad news. The good news is there is hope but the bad news is I am currently at the mercy of whenever someone decides to upload this firmware on the internet (if anyone does that is)
Click to expand...
Click to collapse
sorry dude i cant help u because im using f variant..
khaisttj92 said:
sorry dude i cant help u because im using f variant..
Click to expand...
Click to collapse
Thanks anyways my dude
NullaVisus said:
Thanks anyways my dude
Click to expand...
Click to collapse
your welcome..
NullaVisus said:
No dice my dude. However, I did find something else
Turns out when I check the bootloader version it reads J700T1UVU3AQC3. Sure enough there was a baseband update and security update a few days ago and my device must've installed it while I was asleep. This would explain why my baseband is broken AND why Odin doesn't want me to flash the APK6 Bootloader.
So there's good news and bad news. The good news is there is hope but the bad news is I am currently at the mercy of whenever someone decides to upload this firmware on the internet (if anyone does that is)
Click to expand...
Click to collapse
You are lucky because you at least have a functioning bootloader and a working TWRP. You are unlucky because AQC3 firmware is not available publicly yet. In any case, bootloader cannot be flashed in TWRP as far as I know. Your only option is to get your missing ACQ3 partitions from someone else's back up. IF you have messed up your EFS partition though you are out of luck.
So exactly what partitions do you need? I may be able to give you those partitions if I have a personal backup of those from the past. Right now I have modified so many things that a current copy of my partitions will probably do you more harm than good.
najoor said:
You are lucky because you at least have a functioning bootloader and a working TWRP. You are unlucky because AQC3 firmware is not available publicly yet. In any case, bootloader cannot be flashed in TWRP as far as I know. Your only option is to get your missing ACQ3 partitions from someone else's back up. IF you have messed up your EFS partition though you are out of luck.
So exactly what partitions do you need? I may be able to give you those partitions if I have a personal backup of those from the past. Right now I have modified so many things that a current copy of my partitions will probably do you more harm than good.
Click to expand...
Click to collapse
As far as I know I just need a main system.img backup
Edit; to specify, if I was flashing with Odin it would be what I would put in the AP slot
The phone in its current state is extremely slow and buggy. My intuition tells me that the older Android version does NOT like the new fiirmware (The bootloader is also where the firmware/device config info is stored IIRC)
NullaVisus said:
As far as I know I just need a main system.img backup
Edit; to specify, if I was flashing with Odin it would be what I would put in the AP slot
The phone in its current state is extremely slow and buggy. My intuition tells me that the older Android version does NOT like the new fiirmware (The bootloader is also where the firmware/device config info is stored IIRC)
Click to expand...
Click to collapse
I can give you a system image but you will have to flash it in TWRP.
najoor said:
I can give you a system image but you will have to flash it in TWRP.
Click to expand...
Click to collapse
Thats fine. I already know how
NullaVisus said:
Thats fine. I already know how
Click to expand...
Click to collapse
Well lucky me Ive got a similar situation though I reflashed with a 3-part HOME file from sammobile to unroot/unTWRP, but did so not realizing the darn BL wasnt included. Lucky for me my build versions matched, so Odin flashed flawlessly, the device boots as if it were brand new, stock recovery and all, everything functions/boots as it should, splash, factory setup, TMobile network works fine etc - only problem is both SafetyNet tests fail, so Google wont let me use use Android Pay and every other payment app that hooks into their API shuts me out. I also noticed a lightning-fast error right before going into the bootloader if you boot from the stock recovery (its so fast I need to capture the log to see what it is).
Any suggestions on where to find a BL to go with my J700T & assuming I find one, any nuances I should be aware of when flashing so as to avoid a potential brick situation?
FYI I flashed with the below from sammobile (and yes I was already at AQF1).
J700TUVS3AQF1_J700TTMB3AQF1_J700TUVS3AQF1_HOME.tar
rawkahn said:
Well lucky me Ive got a similar situation though I reflashed with a 3-part HOME file from sammobile to unroot/unTWRP, but did so not realizing the darn BL wasnt included. Lucky for me my build versions matched, so Odin flashed flawlessly, the device boots as if it were brand new, stock recovery and all, everything functions/boots as it should, splash, factory setup, TMobile network works fine etc - only problem is both SafetyNet tests fail, so Google wont let me use use Android Pay and every other payment app that hooks into their API shuts me out. I also noticed a lightning-fast error right before going into the bootloader if you boot from the stock recovery (its so fast I need to capture the log to see what it is).
Any suggestions on where to find a BL to go with my J700T & assuming I find one, any nuances I should be aware of when flashing so as to avoid a potential brick situation?
FYI I flashed with the below from sammobile (and yes I was already at AQF1).
J700TUVS3AQF1_J700TTMB3AQF1_J700TUVS3AQF1_HOME.tar
Click to expand...
Click to collapse
The bootloader is always included with the firmware and is most certainly included with the firmware you posted.
Safetynet probably fails because you need to factory reset.
Hey everyone, I managed to download the OTA update bin file from FOTA server for the S8 Unlocked (US Version). If anyone is interested in testing and post the update I will leave the link to the OTA bin file. I am actually working on it as well. I am assuming it should be flashable as long as you have latest Nougat 7.0 for the unlocked S8 or if you have installed Unlocked firmware in your Carrier branded Galaxy S8. I will be doing some test as well but I need some rest before I start working on it again. Will keep you all posted and hope some of you guys would like to do some test with it. I am pretty sure we will figure out how to flash it.
As far as I know from last year you could flash update.zip file which was extracted from the Verizon S7 Edge. Since its unlocked firmware/OTA file I would assume it will be doable.
Normally you will have to keep the file in your sdCard and go to recovery mode and apply update from SD card but we will definitely have to do some testing if that doesn't work out.
Link for the OTA update bin file: https://mega.nz/#F!k6IjlJoC!VJJ3gyVaF8ofphE1fZvD8A
EDIT: found a way to download whole firmware will post sometime after midnight once I get off from work.
we cant flash .bin files. Doesnt work. We already tried.
thank you! I would love to know how to flash this if possible?
badboy47 said:
thank you! I would love to know how to flash this if possible?
Click to expand...
Click to collapse
1 possible way might be to extract the content of bin with 7zip. then compress it with 7zip as a zip file. name it the same name. put on sdcard and reboot to recovery. then apply update from sdcard and prey to what ever god you like that it works.
trying to help.
MrSteelX said:
1 possible way might be to extract the content of bin with 7zip. then compress it with 7zip as a zip file. name it the same name. put on sdcard and reboot to recovery. then apply update from sdcard and prey to what ever god you like that it works.
trying to help.
Click to expand...
Click to collapse
Nope is not working there are two errors 1st is e.footer is wrong and 2nd is signature verification failed
If someone has a Snapdragon S8 with bootloader unlocked and TWRP, maybe you can sideload it by disabling signature verification?
When flashing updates via stock recovery create a folder call FOTA in SD card and place file there rename it update.zip just make sure you don't end up with update.zip.zip
tlopez1973 said:
When flashing updates via stock recovery create a folder call FOTA in SD card and place file there rename it update.zip just make sure you don't end up with update.zip.zip
Click to expand...
Click to collapse
No, an error is displayed. Nothing is set.
55andrey55 said:
No, an error is displayed. Nothing is set.
Click to expand...
Click to collapse
what's the error you got?
MishaalRahman said:
If someone has a Snapdragon S8 with bootloader unlocked and TWRP, maybe you can sideload it by disabling signature verification?
Click to expand...
Click to collapse
Only snapdragons that have bootloader unlock is the Chinese edition and loading that would probably brick them or best casensrio perma lock their bootloader
Cameron581 said:
Only snapdragons that have bootloader unlock is the Chinese edition and loading that would probably brick them or best casensrio perma lock their bootloader
Click to expand...
Click to collapse
It wouldn't do either of those. It would just fail.
suyash1629 said:
what's the error you got?
Click to expand...
Click to collapse
Just went live in the US man through the Samsung plus app and I got in. Only 10k spots
Stevieboy02008 said:
Just went live in the US man through the Samsung plus app and I got in. Only 10k spots
Click to expand...
Click to collapse
Yup I saw it just went live. I reverted back to Nougat and was trying to get the OTA update.zip file. And noticed that it just went live. For some reason it did not detect that I was already registered and asked me to registered again. I wonder if everyone who did it by bypassing server has to register again to claim their actual spot for later updates.
suyash1629 said:
Yup I saw it just went live. I reverted back to Nougat and was trying to get the OTA update.zip file. And noticed that it just went live. For some reason it did not detect that I was already registered and asked me to registered again. I wonder if everyone who did it by bypassing server has to register again to claim their actual spot for later updates.
Click to expand...
Click to collapse
Don't know and don't care. It's downloading officially now brother and I'm a happy camper lol once it download I will do factory reset and have it fresh
Does anyone know if we can use SamPWND root method but without clearing cache? I am assuming I can do that by not flashing CSC which contains the cache partition.
I am trying to grab update.zip from cache partition.
Turns out my assumption of update.zip file being stored in /cache were wrong its actually stored in /data/fota folder. I guess we are out of luck here. I was thinking what is that converts .bin file to .zip file instantly after downloading onto Galaxy S8. I don't see any other way beside renaming and adding signature (though it already has the signature from Samsung.
suyash1629 said:
Turns out my assumption of update.zip file being stored in /cache were wrong its actually stored in /data/fota folder. I guess we are out of luck here. I was thinking what is that converts .bin file to .zip file instantly after downloading onto Galaxy S8. I don't see any other way beside renaming and adding signature (though it already has the signature from Samsung.
Click to expand...
Click to collapse
Well I have a question for you brother.
I just officially download and installed it. But wanted to do a fresh start basically a factory reset and download everything from scratch. If I do the factory reset would it kick me out of beta and take me back to 7.0 or just take me back to 7.0 or will start with 8.0?
Stevieboy02008 said:
Well I have a question for you brother.
I just officially download and installed it. But wanted to do a fresh start basically a factory reset and download everything from scratch. If I do the factory reset would it kick me out of beta and take me back to 7.0 or just take me back to 7.0 or will start with 8.0?
Click to expand...
Click to collapse
factory reset will stay on 8.0
Would it kick me out of the beta program though. That's the most important thing for me ?
---------- Post added at 08:34 PM ---------- Previous post was at 08:03 PM ----------
cam30era said:
factory reset will stay on 8.0
Click to expand...
Click to collapse
Please advice on my earlier question brother.
You guys think FlashFire could flash it?